Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 2 665 | labels stringlengths 4 554 | body stringlengths 3 235k | index stringclasses 6 values | text_combine stringlengths 96 235k | label stringclasses 2 values | text stringlengths 96 196k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8,915 | 7,733,579,728 | IssuesEvent | 2018-05-26 13:36:40 | pytest-dev/pytest | https://api.github.com/repos/pytest-dev/pytest | closed | Change to src/ layout? | type: infrastructure | Our [docs](https://docs.pytest.org/en/latest/goodpractices.html?highlight=use%20a%20src%20layout%20#choosing-a-test-layout-import-rules) recommend using `src` layout for Python projects in general.
Following tox (https://github.com/tox-dev/tox/issues/826) and the discussion over https://github.com/pypa/python-packaging-user-guide/issues/320, should we follow the `src` layout as well? | 1.0 | Change to src/ layout? - Our [docs](https://docs.pytest.org/en/latest/goodpractices.html?highlight=use%20a%20src%20layout%20#choosing-a-test-layout-import-rules) recommend using `src` layout for Python projects in general.
Following tox (https://github.com/tox-dev/tox/issues/826) and the discussion over https://github.com/pypa/python-packaging-user-guide/issues/320, should we follow the `src` layout as well? | infrastructure | change to src layout our recommend using src layout for python projects in general following tox and the discussion over should we follow the src layout as well | 1 |
8,952 | 7,746,078,022 | IssuesEvent | 2018-05-29 20:28:20 | dotnet/coreclr | https://api.github.com/repos/dotnet/coreclr | opened | [arm64/Linux] Enable 'jitnosimd' testing? | arch-arm64 area-Infrastructure | Arm64/Linux is missing the netci.groovy 'jitnosimd' testing job (`COMPlus_FeatureSIMD=0`).
It doesn't make sense (or is duplicative) for arm32. But arm64 does support SIMD, so should support this mode.
| 1.0 | [arm64/Linux] Enable 'jitnosimd' testing? - Arm64/Linux is missing the netci.groovy 'jitnosimd' testing job (`COMPlus_FeatureSIMD=0`).
It doesn't make sense (or is duplicative) for arm32. But arm64 does support SIMD, so should support this mode.
| infrastructure | enable jitnosimd testing linux is missing the netci groovy jitnosimd testing job complus featuresimd it doesn t make sense or is duplicative for but does support simd so should support this mode | 1 |
24,715 | 17,644,917,200 | IssuesEvent | 2021-08-20 03:37:43 | Samsung/thorvg | https://api.github.com/repos/Samsung/thorvg | closed | Can't compile ThorVG to WebAssembly after "build: Fixed simd options detection" | bug infrastructure | After changing a logic for neon detection ["build: Fixed simd options detection"](https://github.com/Samsung/thorvg/commit/e3eaa05548bdc9cd366e044de22fe776caa5540e), there is a problem compiling to WebAssembly
```
em++: error: Passing any of -msse, -msse2, -msse3, -mssse3, -msse4.1, -msse4.2, -mavx, -mfpu=neon flags also requires passing -msimd128!
``` | 1.0 | Can't compile ThorVG to WebAssembly after "build: Fixed simd options detection" - After changing a logic for neon detection ["build: Fixed simd options detection"](https://github.com/Samsung/thorvg/commit/e3eaa05548bdc9cd366e044de22fe776caa5540e), there is a problem compiling to WebAssembly
```
em++: error: Passing any of -msse, -msse2, -msse3, -mssse3, -msse4.1, -msse4.2, -mavx, -mfpu=neon flags also requires passing -msimd128!
``` | infrastructure | can t compile thorvg to webassembly after build fixed simd options detection after changing a logic for neon detection there is a problem compiling to webassembly em error passing any of msse mavx mfpu neon flags also requires passing | 1 |
5,382 | 5,627,636,861 | IssuesEvent | 2017-04-05 02:24:25 | archco/wise-quotes | https://api.github.com/repos/archco/wise-quotes | closed | Modify asynchronous methods based "Promise". | infrastructure | 비동기처리 method들을 promise 기반으로 바꾼다.
아래와 같이 사용하도록..
```javascript
wq.read(1).then((row) => {
console.log(row);
})
``` | 1.0 | Modify asynchronous methods based "Promise". - 비동기처리 method들을 promise 기반으로 바꾼다.
아래와 같이 사용하도록..
```javascript
wq.read(1).then((row) => {
console.log(row);
})
``` | infrastructure | modify asynchronous methods based promise 비동기처리 method들을 promise 기반으로 바꾼다 아래와 같이 사용하도록 javascript wq read then row console log row | 1 |
28,777 | 23,490,768,338 | IssuesEvent | 2022-08-17 18:29:33 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Libraries Infrastructure and Tools work planned for .NET 7 | Epic area-Infrastructure-libraries Team:Libraries | Collecting the work in Infrastructure and Tools that we aspire to complete in .NET 7
- [ ] https://github.com/dotnet/sdk/issues/17364
- [x] https://github.com/dotnet/sdk/issues/18677
- [x] https://github.com/dotnet/runtime/issues/65741 | 1.0 | Libraries Infrastructure and Tools work planned for .NET 7 - Collecting the work in Infrastructure and Tools that we aspire to complete in .NET 7
- [ ] https://github.com/dotnet/sdk/issues/17364
- [x] https://github.com/dotnet/sdk/issues/18677
- [x] https://github.com/dotnet/runtime/issues/65741 | infrastructure | libraries infrastructure and tools work planned for net collecting the work in infrastructure and tools that we aspire to complete in net | 1 |
82,985 | 23,933,931,412 | IssuesEvent | 2022-09-11 00:21:42 | apache/camel-k | https://api.github.com/repos/apache/camel-k | closed | support for multiple type of builders | area/build-system status/stale | at the moment we have a single general builder but we could need to have specialized builder for specific runtime and features, ideally the builder could be selected using a label | 1.0 | support for multiple type of builders - at the moment we have a single general builder but we could need to have specialized builder for specific runtime and features, ideally the builder could be selected using a label | non_infrastructure | support for multiple type of builders at the moment we have a single general builder but we could need to have specialized builder for specific runtime and features ideally the builder could be selected using a label | 0 |
631,098 | 20,143,986,936 | IssuesEvent | 2022-02-09 04:20:12 | brave/brave-ios | https://api.github.com/repos/brave/brave-ios | closed | [feature/webauthn] Touch key modal does not show up if the key is already plugged in | security priority/P4 sec-low QA/No release-notes/exclude Epic: WebAuthn | <!-- Have you searched for similar issues on the repository?
Before submitting this issue, please visit our wiki for common ones: https://github.com/brave/browser-ios/wiki
For more, check out our community site: https://community.brave.com/ -->
### Description:
Touch key modal should show up if the lightning key is inserted.
### Steps to Reproduce
1. Navigate to https://mdp.github.io/u2fdemo
2. Insert the lightning key
3. Register and Sign
**Actual result:** <!-- Add screenshots if needed -->
On sign the modal is not presented if the lightning key is plugged in
**Expected result:**
Touch key modal should be displayed
**Reproduces how often:** [Easily reproduced, Intermittent Issue]
Easily
**Brave Version:** <!-- Provide full details Eg: v1.4.2(17.09.08.16) -->
1.20 (20.09.11.20)
**Device details:** <!-- Model type and iOS version Eg: iPhone 6s+ (iOS 10.3.3)-->
iPhone 11 + iOS 14 | 1.0 | [feature/webauthn] Touch key modal does not show up if the key is already plugged in - <!-- Have you searched for similar issues on the repository?
Before submitting this issue, please visit our wiki for common ones: https://github.com/brave/browser-ios/wiki
For more, check out our community site: https://community.brave.com/ -->
### Description:
Touch key modal should show up if the lightning key is inserted.
### Steps to Reproduce
1. Navigate to https://mdp.github.io/u2fdemo
2. Insert the lightning key
3. Register and Sign
**Actual result:** <!-- Add screenshots if needed -->
On sign the modal is not presented if the lightning key is plugged in
**Expected result:**
Touch key modal should be displayed
**Reproduces how often:** [Easily reproduced, Intermittent Issue]
Easily
**Brave Version:** <!-- Provide full details Eg: v1.4.2(17.09.08.16) -->
1.20 (20.09.11.20)
**Device details:** <!-- Model type and iOS version Eg: iPhone 6s+ (iOS 10.3.3)-->
iPhone 11 + iOS 14 | non_infrastructure | touch key modal does not show up if the key is already plugged in have you searched for similar issues on the repository before submitting this issue please visit our wiki for common ones for more check out our community site description touch key modal should show up if the lightning key is inserted steps to reproduce navigate to insert the lightning key register and sign actual result on sign the modal is not presented if the lightning key is plugged in expected result touch key modal should be displayed reproduces how often easily brave version device details iphone ios | 0 |
10,721 | 8,694,288,942 | IssuesEvent | 2018-12-04 12:12:08 | elastic/beats | https://api.github.com/repos/elastic/beats | closed | ssl.verification_mode not working on golang module | :infrastructure Metricbeat module | - Version: 6.0.0-alpha1-SNAPSHOT
- Operating System: docker alpine
- Steps to Reproduce: enable golang module with ssl.verification_mode: none. Try to communicate via SSL to a service. Seems none is ignored and full is used failing due to self-signed!
metricbeat.yml
```
- module: golang
metricsets: ["expvar","heap"]
enabled: true
period: 10s
hosts: ["sim-service:9007"]
heap.path: "/debug/vars"
expvar:
namespace: "example"
path: "/debug/vars"
protocol: "https"
ssl.enabled: true
ssl.verification_mode: none
```
| 1.0 | ssl.verification_mode not working on golang module - - Version: 6.0.0-alpha1-SNAPSHOT
- Operating System: docker alpine
- Steps to Reproduce: enable golang module with ssl.verification_mode: none. Try to communicate via SSL to a service. Seems none is ignored and full is used failing due to self-signed!
metricbeat.yml
```
- module: golang
metricsets: ["expvar","heap"]
enabled: true
period: 10s
hosts: ["sim-service:9007"]
heap.path: "/debug/vars"
expvar:
namespace: "example"
path: "/debug/vars"
protocol: "https"
ssl.enabled: true
ssl.verification_mode: none
```
| infrastructure | ssl verification mode not working on golang module version snapshot operating system docker alpine steps to reproduce enable golang module with ssl verification mode none try to communicate via ssl to a service seems none is ignored and full is used failing due to self signed metricbeat yml module golang metricsets enabled true period hosts heap path debug vars expvar namespace example path debug vars protocol https ssl enabled true ssl verification mode none | 1 |
255,183 | 8,109,856,435 | IssuesEvent | 2018-08-14 09:01:10 | Rammelkast/AntiCheatReloaded | https://api.github.com/repos/Rammelkast/AntiCheatReloaded | closed | It seems like the plugin was blocked by some mods... | low priority | well,I downloaded this plugin from minecraft-forum in China.Then I put it in my server,but it works incorrectly and reply many errors on the console.
The error report is:
Could not pass event PlayerMoveEvent to AntiCheatReloaded v1.6.1-ALPHA
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:338) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[RegisteredListener.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:507) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:492) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:344) [nh.class:?]
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(C03PacketPlayer.java:36) [jd.class:?]
at net.minecraft.network.play.client.C03PacketPlayer$C04PacketPlayerPosition.func_148833_a(C03PacketPlayer.java:144) [je.class:?]
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:245) [ej.class:?]
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:176) [nc.class:?]
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:989) [MinecraftServer.class:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:458) [lt.class:?]
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:806) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:665) [MinecraftServer.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_171]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.rammelkast.anticheatreloaded.util.VersionUtil
at com.rammelkast.anticheatreloaded.check.combat.KillAuraCheck.doMove(KillAuraCheck.java:82) ~[?:?]
at com.rammelkast.anticheatreloaded.event.PlayerListener.onPlayerMove(PlayerListener.java:325) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_171]
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:334) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
... 13 more
[10:40:15] [Craft Scheduler Thread - 14/INFO]: [0;32;1m[[0;33;22mResidence[0;32;1m][0;37;22m [0;31;1mFailed to check for Residence update on spigot web page.[m
[10:40:16] [Server thread/ERROR]: Could not pass event PlayerMoveEvent to AntiCheatReloaded v1.6.1-ALPHA
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:338) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[RegisteredListener.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:507) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:492) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:344) [nh.class:?]
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(C03PacketPlayer.java:36) [jd.class:?]
at net.minecraft.network.play.client.C03PacketPlayer$C05PacketPlayerLook.func_148833_a(C03PacketPlayer.java:182) [jg.class:?]
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:245) [ej.class:?]
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:176) [nc.class:?]
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:989) [MinecraftServer.class:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:458) [lt.class:?]
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:806) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:665) [MinecraftServer.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_171]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.rammelkast.anticheatreloaded.util.VersionUtil
at com.rammelkast.anticheatreloaded.check.combat.KillAuraCheck.doMove(KillAuraCheck.java:82) ~[?:?]
at com.rammelkast.anticheatreloaded.event.PlayerListener.onPlayerMove(PlayerListener.java:325) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_171]
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:334) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
... 13 more
[10:40:16] [Server thread/ERROR]: Could not pass event PlayerMoveEvent to AntiCheatReloaded v1.6.1-ALPHA
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:338) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[RegisteredListener.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:507) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:492) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:344) [nh.class:?]
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(C03PacketPlayer.java:36) [jd.class:?]
at net.minecraft.network.play.client.C03PacketPlayer$C05PacketPlayerLook.func_148833_a(C03PacketPlayer.java:182) [jg.class:?]
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:245) [ej.class:?]
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:176) [nc.class:?]
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:989) [MinecraftServer.class:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:458) [lt.class:?]
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:806) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:665) [MinecraftServer.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_171]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.rammelkast.anticheatreloaded.util.VersionUtil
at com.rammelkast.anticheatreloaded.check.combat.KillAuraCheck.doMove(KillAuraCheck.java:82) ~[?:?]
at com.rammelkast.anticheatreloaded.event.PlayerListener.onPlayerMove(PlayerListener.java:325) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_171]
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:334) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
... 13 more
It's a KCauldron server ,Version: cc.uraniummc:Uranium:1710-stable-4-B15
only have Naruto-Anime mod
what should I do? | 1.0 | It seems like the plugin was blocked by some mods... - well,I downloaded this plugin from minecraft-forum in China.Then I put it in my server,but it works incorrectly and reply many errors on the console.
The error report is:
Could not pass event PlayerMoveEvent to AntiCheatReloaded v1.6.1-ALPHA
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:338) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[RegisteredListener.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:507) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:492) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:344) [nh.class:?]
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(C03PacketPlayer.java:36) [jd.class:?]
at net.minecraft.network.play.client.C03PacketPlayer$C04PacketPlayerPosition.func_148833_a(C03PacketPlayer.java:144) [je.class:?]
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:245) [ej.class:?]
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:176) [nc.class:?]
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:989) [MinecraftServer.class:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:458) [lt.class:?]
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:806) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:665) [MinecraftServer.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_171]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.rammelkast.anticheatreloaded.util.VersionUtil
at com.rammelkast.anticheatreloaded.check.combat.KillAuraCheck.doMove(KillAuraCheck.java:82) ~[?:?]
at com.rammelkast.anticheatreloaded.event.PlayerListener.onPlayerMove(PlayerListener.java:325) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_171]
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:334) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
... 13 more
[10:40:15] [Craft Scheduler Thread - 14/INFO]: [0;32;1m[[0;33;22mResidence[0;32;1m][0;37;22m [0;31;1mFailed to check for Residence update on spigot web page.[m
[10:40:16] [Server thread/ERROR]: Could not pass event PlayerMoveEvent to AntiCheatReloaded v1.6.1-ALPHA
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:338) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[RegisteredListener.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:507) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:492) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:344) [nh.class:?]
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(C03PacketPlayer.java:36) [jd.class:?]
at net.minecraft.network.play.client.C03PacketPlayer$C05PacketPlayerLook.func_148833_a(C03PacketPlayer.java:182) [jg.class:?]
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:245) [ej.class:?]
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:176) [nc.class:?]
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:989) [MinecraftServer.class:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:458) [lt.class:?]
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:806) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:665) [MinecraftServer.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_171]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.rammelkast.anticheatreloaded.util.VersionUtil
at com.rammelkast.anticheatreloaded.check.combat.KillAuraCheck.doMove(KillAuraCheck.java:82) ~[?:?]
at com.rammelkast.anticheatreloaded.event.PlayerListener.onPlayerMove(PlayerListener.java:325) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_171]
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:334) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
... 13 more
[10:40:16] [Server thread/ERROR]: Could not pass event PlayerMoveEvent to AntiCheatReloaded v1.6.1-ALPHA
org.bukkit.event.EventException
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:338) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) ~[RegisteredListener.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:507) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:492) [SimplePluginManager.class:1.7.10-R0.1-SNAPSHOT]
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:344) [nh.class:?]
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(C03PacketPlayer.java:36) [jd.class:?]
at net.minecraft.network.play.client.C03PacketPlayer$C05PacketPlayerLook.func_148833_a(C03PacketPlayer.java:182) [jg.class:?]
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:245) [ej.class:?]
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:176) [nc.class:?]
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:989) [MinecraftServer.class:?]
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:458) [lt.class:?]
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:806) [MinecraftServer.class:?]
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:665) [MinecraftServer.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_171]
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.rammelkast.anticheatreloaded.util.VersionUtil
at com.rammelkast.anticheatreloaded.check.combat.KillAuraCheck.doMove(KillAuraCheck.java:82) ~[?:?]
at com.rammelkast.anticheatreloaded.event.PlayerListener.onPlayerMove(PlayerListener.java:325) ~[?:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_171]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_171]
at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_171]
at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:334) ~[JavaPluginLoader$1.class:1.7.10-R0.1-SNAPSHOT]
... 13 more
It's a KCauldron server ,Version: cc.uraniummc:Uranium:1710-stable-4-B15
only have Naruto-Anime mod
what should I do? | non_infrastructure | it seems like the plugin was blocked by some mods well i downloaded this plugin from minecraft forum in china then i put it in my server but it works incorrectly and reply many errors on the console the error report is could not pass event playermoveevent to anticheatreloaded alpha org bukkit event eventexception at org bukkit plugin java javapluginloader execute javapluginloader java at org bukkit plugin registeredlistener callevent registeredlistener java at org bukkit plugin simplepluginmanager fireevent simplepluginmanager java at org bukkit plugin simplepluginmanager callevent simplepluginmanager java at net minecraft network nethandlerplayserver func a nethandlerplayserver java at net minecraft network play client func a java at net minecraft network play client func a java at net minecraft network networkmanager func b networkmanager java at net minecraft network networksystem func c networksystem java at net minecraft server minecraftserver func q minecraftserver java at net minecraft server dedicated dedicatedserver func q dedicatedserver java at net minecraft server minecraftserver func p minecraftserver java at net minecraft server minecraftserver run minecraftserver java at java lang thread run unknown source caused by java lang noclassdeffounderror could not initialize class com rammelkast anticheatreloaded util versionutil at com rammelkast anticheatreloaded check combat killauracheck domove killauracheck java at com rammelkast anticheatreloaded event playerlistener onplayermove playerlistener java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke unknown source at java lang reflect method invoke unknown source at org bukkit plugin java javapluginloader execute javapluginloader java more to check for residence update on spigot web page m could not pass event playermoveevent to anticheatreloaded alpha org bukkit event eventexception at org bukkit plugin java javapluginloader execute javapluginloader java at org bukkit plugin registeredlistener callevent registeredlistener java at org bukkit plugin simplepluginmanager fireevent simplepluginmanager java at org bukkit plugin simplepluginmanager callevent simplepluginmanager java at net minecraft network nethandlerplayserver func a nethandlerplayserver java at net minecraft network play client func a java at net minecraft network play client func a java at net minecraft network networkmanager func b networkmanager java at net minecraft network networksystem func c networksystem java at net minecraft server minecraftserver func q minecraftserver java at net minecraft server dedicated dedicatedserver func q dedicatedserver java at net minecraft server minecraftserver func p minecraftserver java at net minecraft server minecraftserver run minecraftserver java at java lang thread run unknown source caused by java lang noclassdeffounderror could not initialize class com rammelkast anticheatreloaded util versionutil at com rammelkast anticheatreloaded check combat killauracheck domove killauracheck java at com rammelkast anticheatreloaded event playerlistener onplayermove playerlistener java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke unknown source at java lang reflect method invoke unknown source at org bukkit plugin java javapluginloader execute javapluginloader java more could not pass event playermoveevent to anticheatreloaded alpha org bukkit event eventexception at org bukkit plugin java javapluginloader execute javapluginloader java at org bukkit plugin registeredlistener callevent registeredlistener java at org bukkit plugin simplepluginmanager fireevent simplepluginmanager java at org bukkit plugin simplepluginmanager callevent simplepluginmanager java at net minecraft network nethandlerplayserver func a nethandlerplayserver java at net minecraft network play client func a java at net minecraft network play client func a java at net minecraft network networkmanager func b networkmanager java at net minecraft network networksystem func c networksystem java at net minecraft server minecraftserver func q minecraftserver java at net minecraft server dedicated dedicatedserver func q dedicatedserver java at net minecraft server minecraftserver func p minecraftserver java at net minecraft server minecraftserver run minecraftserver java at java lang thread run unknown source caused by java lang noclassdeffounderror could not initialize class com rammelkast anticheatreloaded util versionutil at com rammelkast anticheatreloaded check combat killauracheck domove killauracheck java at com rammelkast anticheatreloaded event playerlistener onplayermove playerlistener java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke unknown source at java lang reflect method invoke unknown source at org bukkit plugin java javapluginloader execute javapluginloader java more it s a kcauldron server version cc uraniummc uranium stable only have naruto anime mod what should i do | 0 |
33,319 | 27,383,454,365 | IssuesEvent | 2023-02-28 11:40:03 | acterglobal/a3 | https://api.github.com/repos/acterglobal/a3 | opened | Fallback to Registration-Screen if GuestAccessForbidden | bug infrastructure | If run against a server without `GuestAccess` enabled (which is the most likely), we currently get a failure:
```
[2023-02-28 16:17:50.902827 +05:00] INFO [effektio::api::client] native\effektio\src\api\client.rs:516: logout error: Api(Server(ClientApi(Error { status_code: 403, body: Standard { kind: GuestAccessForbidden, message: "Guest access not allowed" } })))
```
Instead, if we notice that `GuestAccessForbidden` we should fallback to asking the user to login/register. | 1.0 | Fallback to Registration-Screen if GuestAccessForbidden - If run against a server without `GuestAccess` enabled (which is the most likely), we currently get a failure:
```
[2023-02-28 16:17:50.902827 +05:00] INFO [effektio::api::client] native\effektio\src\api\client.rs:516: logout error: Api(Server(ClientApi(Error { status_code: 403, body: Standard { kind: GuestAccessForbidden, message: "Guest access not allowed" } })))
```
Instead, if we notice that `GuestAccessForbidden` we should fallback to asking the user to login/register. | infrastructure | fallback to registration screen if guestaccessforbidden if run against a server without guestaccess enabled which is the most likely we currently get a failure info native effektio src api client rs logout error api server clientapi error status code body standard kind guestaccessforbidden message guest access not allowed instead if we notice that guestaccessforbidden we should fallback to asking the user to login register | 1 |
1,349 | 3,146,304,578 | IssuesEvent | 2015-09-14 22:14:36 | google/WebFundamentals | https://api.github.com/repos/google/WebFundamentals | opened | autogenerate the book.yaml files | P1 type-Infrastructure | per discussion, auto generate the book.yaml files so paths, titles, are always up to date
note this should work for translations too :) | 1.0 | autogenerate the book.yaml files - per discussion, auto generate the book.yaml files so paths, titles, are always up to date
note this should work for translations too :) | infrastructure | autogenerate the book yaml files per discussion auto generate the book yaml files so paths titles are always up to date note this should work for translations too | 1 |
72,873 | 7,314,276,455 | IssuesEvent | 2018-03-01 06:17:14 | fabric8io/fabric8-maven-plugin | https://api.github.com/repos/fabric8io/fabric8-maven-plugin | closed | Regression test issues | regression-test test | Regression tests are not running well on CI systems
- [x] Test behavior on Travis environment is intermittent. Sometimes tests are getting failed with some errors in f8-m-p like #1133 #111. The potential reason for test failure could be test environment infrastructure or issues with f8-m-p.
- [x] Fixed the build issue for OpenShift v3.7 #1130 as its affecting overall test behavior and performance as well | 2.0 | Regression test issues - Regression tests are not running well on CI systems
- [x] Test behavior on Travis environment is intermittent. Sometimes tests are getting failed with some errors in f8-m-p like #1133 #111. The potential reason for test failure could be test environment infrastructure or issues with f8-m-p.
- [x] Fixed the build issue for OpenShift v3.7 #1130 as its affecting overall test behavior and performance as well | non_infrastructure | regression test issues regression tests are not running well on ci systems test behavior on travis environment is intermittent sometimes tests are getting failed with some errors in m p like the potential reason for test failure could be test environment infrastructure or issues with m p fixed the build issue for openshift as its affecting overall test behavior and performance as well | 0 |
35,474 | 31,653,398,157 | IssuesEvent | 2023-09-07 01:36:48 | ArctosDB/arctos | https://api.github.com/repos/ArctosDB/arctos | closed | Feature Request - bulkloader_stage needs more control | Priority-Critical (Arctos is broken) Enhancement Infrastructure-limited Priority - Wildfire Potential | **Is your feature request related to a problem? Please describe.**
Somehow the bulkloader ended up with 2million+ mostly-blank records which took Arctos down a couple times.
**Describe what you're trying to accomplish**
Keep Arctos alive
**Describe the solution you'd like**
Infinite resources.
**Describe alternatives you've considered**
Add more requirements - nothing can get out of the table without a recognizable/keyed enteredby and guid_prefix, and requiring them here should have prevented this (perhaps at the cost of more-cryptic errors, but anyone with errors at this level probably needs focused help anyway).
I'm very up for better ideas, complicating anything at this stage will find a way to cause someone some stress, but I think what we have now isn't sustainable so I'll do something very soon unless I hear otherwise.
**Additional context**
**Priority**
fatal but rare == critical | 1.0 | Feature Request - bulkloader_stage needs more control - **Is your feature request related to a problem? Please describe.**
Somehow the bulkloader ended up with 2million+ mostly-blank records which took Arctos down a couple times.
**Describe what you're trying to accomplish**
Keep Arctos alive
**Describe the solution you'd like**
Infinite resources.
**Describe alternatives you've considered**
Add more requirements - nothing can get out of the table without a recognizable/keyed enteredby and guid_prefix, and requiring them here should have prevented this (perhaps at the cost of more-cryptic errors, but anyone with errors at this level probably needs focused help anyway).
I'm very up for better ideas, complicating anything at this stage will find a way to cause someone some stress, but I think what we have now isn't sustainable so I'll do something very soon unless I hear otherwise.
**Additional context**
**Priority**
fatal but rare == critical | infrastructure | feature request bulkloader stage needs more control is your feature request related to a problem please describe somehow the bulkloader ended up with mostly blank records which took arctos down a couple times describe what you re trying to accomplish keep arctos alive describe the solution you d like infinite resources describe alternatives you ve considered add more requirements nothing can get out of the table without a recognizable keyed enteredby and guid prefix and requiring them here should have prevented this perhaps at the cost of more cryptic errors but anyone with errors at this level probably needs focused help anyway i m very up for better ideas complicating anything at this stage will find a way to cause someone some stress but i think what we have now isn t sustainable so i ll do something very soon unless i hear otherwise additional context priority fatal but rare critical | 1 |
205,415 | 23,338,089,595 | IssuesEvent | 2022-08-09 11:49:43 | rsoreq/zaproxy | https://api.github.com/repos/rsoreq/zaproxy | closed | CVE-2020-9488 (Low) detected in log4j-1.2.17.jar - autoclosed | security vulnerability | ## CVE-2020-9488 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-1.2.17.jar</b></p></summary>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /tmp/ws-scm/zaproxy</p>
<p>Path to vulnerable library: /zap/build/distFiles/lib/log4j-1.2.17.jar,/canner/.gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.17/5af35056b4d257e4b64b9e8069c0746e8b08629f/log4j-1.2.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.17/5af35056b4d257e4b64b9e8069c0746e8b08629f/log4j-1.2.17.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.17.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rsoreq/zaproxy/commit/faf0234fff2dbd2142cc463fc90d7e58bcf20cd0">faf0234fff2dbd2142cc463fc90d7e58bcf20cd0</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>3.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.3</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2020-9488 (Low) detected in log4j-1.2.17.jar - autoclosed - ## CVE-2020-9488 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-1.2.17.jar</b></p></summary>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /tmp/ws-scm/zaproxy</p>
<p>Path to vulnerable library: /zap/build/distFiles/lib/log4j-1.2.17.jar,/canner/.gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.17/5af35056b4d257e4b64b9e8069c0746e8b08629f/log4j-1.2.17.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.17/5af35056b4d257e4b64b9e8069c0746e8b08629f/log4j-1.2.17.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.17.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rsoreq/zaproxy/commit/faf0234fff2dbd2142cc463fc90d7e58bcf20cd0">faf0234fff2dbd2142cc463fc90d7e58bcf20cd0</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>3.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.3</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_infrastructure | cve low detected in jar autoclosed cve low severity vulnerability vulnerable library jar apache path to dependency file tmp ws scm zaproxy path to vulnerable library zap build distfiles lib jar canner gradle caches modules files jar home wss scanner gradle caches modules files jar dependency hierarchy x jar vulnerable library found in head commit a href found in base branch develop vulnerability details improper validation of certificate with host mismatch in apache smtp appender this could allow an smtps connection to be intercepted by a man in the middle attack which could leak any log messages sent through that appender fixed in apache and publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ch qos check this box to open an automated fix pr | 0 |
28,728 | 23,467,542,967 | IssuesEvent | 2022-08-16 18:16:52 | coiled/coiled-runtime | https://api.github.com/repos/coiled/coiled-runtime | closed | Ignore decreases in memory usage / wall time in regression detection | bug infrastructure | Currently our regression detection will treat increases and decreases in metrics equally. However, decreases in memory usage and wall time shouldn't trigger a regression detection. See https://github.com/coiled/coiled-runtime/pull/247#issuecomment-1216830194 for some additional context.
I spoke with @ian-r-rose offline and he said he has a quick fix for this | 1.0 | Ignore decreases in memory usage / wall time in regression detection - Currently our regression detection will treat increases and decreases in metrics equally. However, decreases in memory usage and wall time shouldn't trigger a regression detection. See https://github.com/coiled/coiled-runtime/pull/247#issuecomment-1216830194 for some additional context.
I spoke with @ian-r-rose offline and he said he has a quick fix for this | infrastructure | ignore decreases in memory usage wall time in regression detection currently our regression detection will treat increases and decreases in metrics equally however decreases in memory usage and wall time shouldn t trigger a regression detection see for some additional context i spoke with ian r rose offline and he said he has a quick fix for this | 1 |
18,889 | 5,729,887,144 | IssuesEvent | 2017-04-21 07:50:20 | HGustavs/LenaSYS | https://api.github.com/repos/HGustavs/LenaSYS | opened | bug in codeviewer.js line 1043 | All bug CodeViewer | for-loop at line 1043 use "int" instead of "var" which creates a bug in codeviewer.php (unknown keyword) | 1.0 | bug in codeviewer.js line 1043 - for-loop at line 1043 use "int" instead of "var" which creates a bug in codeviewer.php (unknown keyword) | non_infrastructure | bug in codeviewer js line for loop at line use int instead of var which creates a bug in codeviewer php unknown keyword | 0 |
23,514 | 16,361,773,405 | IssuesEvent | 2021-05-14 10:35:11 | gdsbook/book | https://api.github.com/repos/gdsbook/book | closed | Cache data used from `osmnx` | infrastructure | Currently we're reading data off OSM on-the-fly via `osmnx`. It'd be good to have a cache in the repo that allows us to read them locally if connectivity is not an option, and add a note with code in the chapter that it can be read locally. | 1.0 | Cache data used from `osmnx` - Currently we're reading data off OSM on-the-fly via `osmnx`. It'd be good to have a cache in the repo that allows us to read them locally if connectivity is not an option, and add a note with code in the chapter that it can be read locally. | infrastructure | cache data used from osmnx currently we re reading data off osm on the fly via osmnx it d be good to have a cache in the repo that allows us to read them locally if connectivity is not an option and add a note with code in the chapter that it can be read locally | 1 |
13 | 2,491,325,923 | IssuesEvent | 2015-01-03 09:26:28 | Graylog2/graylog2-server | https://api.github.com/repos/Graylog2/graylog2-server | opened | Hdr versions of metrics need serialization support for metrics browser | infrastructure | Our hdr timer and histogram versions of metrics are not supported by our metrics api yet.
| 1.0 | Hdr versions of metrics need serialization support for metrics browser - Our hdr timer and histogram versions of metrics are not supported by our metrics api yet.
| infrastructure | hdr versions of metrics need serialization support for metrics browser our hdr timer and histogram versions of metrics are not supported by our metrics api yet | 1 |
12,708 | 9,932,143,861 | IssuesEvent | 2019-07-02 09:10:21 | aspnet/AspNetCore | https://api.github.com/repos/aspnet/AspNetCore | closed | Blazor VSIX regression - now contains no project templates | area-blazor area-infrastructure | The current `Microsoft.VisualStudio.BlazorExtension.vsix` coming out of CI no longer contains any project templates, so it's not very useful!
I *think* this regression was introduced in this PR: https://github.com/aspnet/AspNetCore/pull/11116. Apparently, that PR was a step towards migrating to Arcade.
I found that it can be fixed by removing the newly-introduced `'$(IsPackable)' == 'true'` condition, as I have done [in this branch](https://github.com/aspnet/AspNetCore/compare/stevesa/attempt-fix-for-blazor-vsix). The [resulting build artifact](https://dev.azure.com/dnceng/public/_build/results?buildId=245328) is correct.
However that fix on its own isn't sufficient, because then the Windows ARM build fails. I don't know how these builds interact with Nate's new `'$(IsPackable)' == 'true'` condition, or what the true fix is meant to be, so this needs to be handled by the build team.
@dougbu @JunTaoLuo Can you make whatever change is needed to fix this build regression in the way you want it to be fixed? | 1.0 | Blazor VSIX regression - now contains no project templates - The current `Microsoft.VisualStudio.BlazorExtension.vsix` coming out of CI no longer contains any project templates, so it's not very useful!
I *think* this regression was introduced in this PR: https://github.com/aspnet/AspNetCore/pull/11116. Apparently, that PR was a step towards migrating to Arcade.
I found that it can be fixed by removing the newly-introduced `'$(IsPackable)' == 'true'` condition, as I have done [in this branch](https://github.com/aspnet/AspNetCore/compare/stevesa/attempt-fix-for-blazor-vsix). The [resulting build artifact](https://dev.azure.com/dnceng/public/_build/results?buildId=245328) is correct.
However that fix on its own isn't sufficient, because then the Windows ARM build fails. I don't know how these builds interact with Nate's new `'$(IsPackable)' == 'true'` condition, or what the true fix is meant to be, so this needs to be handled by the build team.
@dougbu @JunTaoLuo Can you make whatever change is needed to fix this build regression in the way you want it to be fixed? | infrastructure | blazor vsix regression now contains no project templates the current microsoft visualstudio blazorextension vsix coming out of ci no longer contains any project templates so it s not very useful i think this regression was introduced in this pr apparently that pr was a step towards migrating to arcade i found that it can be fixed by removing the newly introduced ispackable true condition as i have done the is correct however that fix on its own isn t sufficient because then the windows arm build fails i don t know how these builds interact with nate s new ispackable true condition or what the true fix is meant to be so this needs to be handled by the build team dougbu juntaoluo can you make whatever change is needed to fix this build regression in the way you want it to be fixed | 1 |
27,105 | 27,660,106,391 | IssuesEvent | 2023-03-12 12:27:50 | EmiOnGit/warbler_grass | https://api.github.com/repos/EmiOnGit/warbler_grass | opened | Improve brushes | good first issue usability Editor | ## The Problem
The brushes currently implemented are working fine for most cases but are not optimized very good.
If you want to dig into how to improve this feel free to do so
Just pick one issue of the ones I listed and try to improve it
* On every draw event, the image is cloned, then we iterate over the pixels and
at last we swap the images. This can be improved by:
- Processing multiple draw events at once instead of one by one
- When running the image, we always have a version of the image loaded ready to be edited in memory. This would remove the cloning
* The airbrush is currently not working great. It is supposed to draw the strongest in the middle and weakens further away
- I don't know how to improve this but seems doable by trying and reading a bit about it
* Implement a redo function for brushes.
- every brush would need to have a reverse function that we can than apply to the image
- Another way would be to buffer the last 5 or so images we changed. This could be fine even though we have to be carefully with mem usage
* Implement new brushes
- feel free to suggest something | True | Improve brushes - ## The Problem
The brushes currently implemented are working fine for most cases but are not optimized very good.
If you want to dig into how to improve this feel free to do so
Just pick one issue of the ones I listed and try to improve it
* On every draw event, the image is cloned, then we iterate over the pixels and
at last we swap the images. This can be improved by:
- Processing multiple draw events at once instead of one by one
- When running the image, we always have a version of the image loaded ready to be edited in memory. This would remove the cloning
* The airbrush is currently not working great. It is supposed to draw the strongest in the middle and weakens further away
- I don't know how to improve this but seems doable by trying and reading a bit about it
* Implement a redo function for brushes.
- every brush would need to have a reverse function that we can than apply to the image
- Another way would be to buffer the last 5 or so images we changed. This could be fine even though we have to be carefully with mem usage
* Implement new brushes
- feel free to suggest something | non_infrastructure | improve brushes the problem the brushes currently implemented are working fine for most cases but are not optimized very good if you want to dig into how to improve this feel free to do so just pick one issue of the ones i listed and try to improve it on every draw event the image is cloned then we iterate over the pixels and at last we swap the images this can be improved by processing multiple draw events at once instead of one by one when running the image we always have a version of the image loaded ready to be edited in memory this would remove the cloning the airbrush is currently not working great it is supposed to draw the strongest in the middle and weakens further away i don t know how to improve this but seems doable by trying and reading a bit about it implement a redo function for brushes every brush would need to have a reverse function that we can than apply to the image another way would be to buffer the last or so images we changed this could be fine even though we have to be carefully with mem usage implement new brushes feel free to suggest something | 0 |
6,236 | 6,264,948,189 | IssuesEvent | 2017-07-16 13:16:13 | denyhosts/denyhosts | https://api.github.com/repos/denyhosts/denyhosts | opened | Use new sync server address in default configuration | infrastructure | Replace with sync.denyhosts.org:9911.
@slicer69, maybe you could have the deny.resonatingmedia.com address resolve/cname to the new sync server as well? This would make anyone with that address report to the new sync server automatically. | 1.0 | Use new sync server address in default configuration - Replace with sync.denyhosts.org:9911.
@slicer69, maybe you could have the deny.resonatingmedia.com address resolve/cname to the new sync server as well? This would make anyone with that address report to the new sync server automatically. | infrastructure | use new sync server address in default configuration replace with sync denyhosts org maybe you could have the deny resonatingmedia com address resolve cname to the new sync server as well this would make anyone with that address report to the new sync server automatically | 1 |
82,347 | 23,747,592,564 | IssuesEvent | 2022-08-31 17:22:59 | NuGet/Home | https://api.github.com/repos/NuGet/Home | closed | [Bug]: NugetSDKResolver doesn't give detailed error messages when it fails | Type:Bug Product:MSBuildSDKResolver | ### NuGet Product Used
MSBuild.exe, NuGet.exe, NuGet SDK
### Product Version
All
### Worked before?
No
### Impact
It bothers me. A fix would be nice
### Repro Steps & Context
Try to use the NugetSdkResolver but with a package it can't load. It will fail but not tell you why, making it hard to diagnose the problem.
### Verbose Logs
_No response_ | 1.0 | [Bug]: NugetSDKResolver doesn't give detailed error messages when it fails - ### NuGet Product Used
MSBuild.exe, NuGet.exe, NuGet SDK
### Product Version
All
### Worked before?
No
### Impact
It bothers me. A fix would be nice
### Repro Steps & Context
Try to use the NugetSdkResolver but with a package it can't load. It will fail but not tell you why, making it hard to diagnose the problem.
### Verbose Logs
_No response_ | non_infrastructure | nugetsdkresolver doesn t give detailed error messages when it fails nuget product used msbuild exe nuget exe nuget sdk product version all worked before no impact it bothers me a fix would be nice repro steps context try to use the nugetsdkresolver but with a package it can t load it will fail but not tell you why making it hard to diagnose the problem verbose logs no response | 0 |
21,000 | 4,652,691,645 | IssuesEvent | 2016-10-03 14:44:33 | openwhisk/openwhisk | https://api.github.com/repos/openwhisk/openwhisk | closed | remove publish attribute from actions | documentation runtime tooling usability | After some experimentation, it became clear that the `publish` attribute for actions is not needed and, worse, can lead to confusion.
For example, create a package with `--shared yes` then create an action in that package also with `--shared yes`. Running `wsk package get` shows that the action has a `publish` value of `false`. However, running `wsk action get` on the actions shows the `publish` value set to `true`.
Additionally, running `wsk action create --shared no` to create an action inside a published package does not prevent others from invoking the action - that is, the `publish` value has no effect.
Lastly... creating an action outside of a shared package with `--shared yes` does not allow others to invoke that action.
*tl;dr* The `publish` attribute for actions doesn't do anything, and should be removed.
This will affect the backend, CLI, and documentation. | 1.0 | remove publish attribute from actions - After some experimentation, it became clear that the `publish` attribute for actions is not needed and, worse, can lead to confusion.
For example, create a package with `--shared yes` then create an action in that package also with `--shared yes`. Running `wsk package get` shows that the action has a `publish` value of `false`. However, running `wsk action get` on the actions shows the `publish` value set to `true`.
Additionally, running `wsk action create --shared no` to create an action inside a published package does not prevent others from invoking the action - that is, the `publish` value has no effect.
Lastly... creating an action outside of a shared package with `--shared yes` does not allow others to invoke that action.
*tl;dr* The `publish` attribute for actions doesn't do anything, and should be removed.
This will affect the backend, CLI, and documentation. | non_infrastructure | remove publish attribute from actions after some experimentation it became clear that the publish attribute for actions is not needed and worse can lead to confusion for example create a package with shared yes then create an action in that package also with shared yes running wsk package get shows that the action has a publish value of false however running wsk action get on the actions shows the publish value set to true additionally running wsk action create shared no to create an action inside a published package does not prevent others from invoking the action that is the publish value has no effect lastly creating an action outside of a shared package with shared yes does not allow others to invoke that action tl dr the publish attribute for actions doesn t do anything and should be removed this will affect the backend cli and documentation | 0 |
7,380 | 6,928,267,124 | IssuesEvent | 2017-12-01 03:37:47 | twitter/reasonable-scala | https://api.github.com/repos/twitter/reasonable-scala | closed | Figure out the methodology for JVM benchmarks | Feature Infrastructure Performance | Over the Thanksgiving break, I've been playing with various values for JMH annotations on our benchmarks:
```scala
@BenchmarkMode(Array(SampleTime))
@OutputTimeUnit(TimeUnit.MILLISECONDS)
@Warmup(iterations = X, time = Y, timeUnit = TimeUnit.SECONDS)
@Measurement(iterations = X, time = Y, timeUnit = TimeUnit.SECONDS)
@Fork(value = Z, jvmArgs = Array("-Xms2G", "-Xmx2G"))
class HotRscTypecheck extends RscTypecheck {
@Benchmark
def run(bs: BenchmarkState): Unit = {
runImpl(bs)
}
}
```
The research question is: "Does there exist a reasonable combination of X, Y and Z that avoids a seemingly inevitable 1ms lower bound on run-to-run variance?". | 1.0 | Figure out the methodology for JVM benchmarks - Over the Thanksgiving break, I've been playing with various values for JMH annotations on our benchmarks:
```scala
@BenchmarkMode(Array(SampleTime))
@OutputTimeUnit(TimeUnit.MILLISECONDS)
@Warmup(iterations = X, time = Y, timeUnit = TimeUnit.SECONDS)
@Measurement(iterations = X, time = Y, timeUnit = TimeUnit.SECONDS)
@Fork(value = Z, jvmArgs = Array("-Xms2G", "-Xmx2G"))
class HotRscTypecheck extends RscTypecheck {
@Benchmark
def run(bs: BenchmarkState): Unit = {
runImpl(bs)
}
}
```
The research question is: "Does there exist a reasonable combination of X, Y and Z that avoids a seemingly inevitable 1ms lower bound on run-to-run variance?". | infrastructure | figure out the methodology for jvm benchmarks over the thanksgiving break i ve been playing with various values for jmh annotations on our benchmarks scala benchmarkmode array sampletime outputtimeunit timeunit milliseconds warmup iterations x time y timeunit timeunit seconds measurement iterations x time y timeunit timeunit seconds fork value z jvmargs array class hotrsctypecheck extends rsctypecheck benchmark def run bs benchmarkstate unit runimpl bs the research question is does there exist a reasonable combination of x y and z that avoids a seemingly inevitable lower bound on run to run variance | 1 |
14,805 | 18,104,598,727 | IssuesEvent | 2021-09-22 17:45:24 | googleapis/python-firestore | https://api.github.com/repos/googleapis/python-firestore | closed | Unit tests must not require credentials in environment | api: firestore type: process | Creating an actual `Client` / `AsyncClient` instance without passing in credentials raises an error.
Better practice for anything not directly testing the client is to use `mock.create_autospec` to create
a dummy client.
```bash
$ git remote -v
origin git@github.com:googleapis/python-firestore (fetch)
origin git@github.com:googleapis/python-firestore (push)
$ git log -1
commit 51c92aa45156c5462f35991f65c02dcac49aacc3 (HEAD -> main, tag: v2.3.2, origin/main)
Author: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Date: Tue Sep 14 14:53:30 2021 -0700
chore: release 2.3.2 (#441)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
$ git status
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
$ env | grep GOOGLE || echo "No Credentials"
No Credentials
$ nox -e unit-3.6
...
________________ TestScheduling.test_operation_retry_scheduling ________________
self = <tests.unit.v1.test_bulk_writer.TestScheduling testMethod=test_operation_retry_scheduling>
def test_operation_retry_scheduling(self):
now = datetime.datetime.now()
one_second_from_now = now + datetime.timedelta(seconds=1)
> db = Client()
tests/unit/v1/test_bulk_writer.py:574:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
google/cloud/firestore_v1/client.py:99: in __init__
client_options=client_options,
google/cloud/firestore_v1/base_client.py:129: in __init__
_http=None,
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/client.py:249: in __init__
_ClientProjectMixin.__init__(self, project=project)
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/client.py:201: in __init__
project = self._determine_default(project)
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/client.py:216: in _determine_default
return _determine_default_project(project)
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/_helpers.py:186: in _determine_default_project
_, project = google.auth.default()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
scopes = None, request = None, quota_project_id = None
def default(scopes=None, request=None, quota_project_id=None):
"""Gets the default credentials for the current environment.
`Application Default Credentials`_ provides an easy way to obtain
credentials to call Google APIs for server-to-server or local applications.
This function acquires credentials from the environment in the following
order:
1. If the environment variable ``GOOGLE_APPLICATION_CREDENTIALS`` is set
to the path of a valid service account JSON private key file, then it is
loaded and returned. The project ID returned is the project ID defined
in the service account file if available (some older files do not
contain project ID information).
2. If the `Google Cloud SDK`_ is installed and has application default
credentials set they are loaded and returned.
To enable application default credentials with the Cloud SDK run::
gcloud auth application-default login
If the Cloud SDK has an active project, the project ID is returned. The
active project can be set using::
gcloud config set project
3. If the application is running in the `App Engine standard environment`_
(first generation) then the credentials and project ID from the
`App Identity Service`_ are used.
4. If the application is running in `Compute Engine`_ or `Cloud Run`_ or
the `App Engine flexible environment`_ or the `App Engine standard
environment`_ (second generation) then the credentials and project ID
are obtained from the `Metadata Service`_.
5. If no credentials are found,
:class:`~google.auth.exceptions.DefaultCredentialsError` will be raised.
.. _Application Default Credentials: https://developers.google.com\
/identity/protocols/application-default-credentials
.. _Google Cloud SDK: https://cloud.google.com/sdk
.. _App Engine standard environment: https://cloud.google.com/appengine
.. _App Identity Service: https://cloud.google.com/appengine/docs/python\
/appidentity/
.. _Compute Engine: https://cloud.google.com/compute
.. _App Engine flexible environment: https://cloud.google.com\
/appengine/flexible
.. _Metadata Service: https://cloud.google.com/compute/docs\
/storing-retrieving-metadata
.. _Cloud Run: https://cloud.google.com/run
Example::
import google.auth
credentials, project_id = google.auth.default()
Args:
scopes (Sequence[str]): The list of scopes for the credentials. If
specified, the credentials will automatically be scoped if
necessary.
request (google.auth.transport.Request): An object used to make
HTTP requests. This is used to detect whether the application
is running on Compute Engine. If not specified, then it will
use the standard library http client to make requests.
quota_project_id (Optional[str]): The project ID used for
quota and billing.
Returns:
Tuple[~google.auth.credentials.Credentials, Optional[str]]:
the current environment's credentials and project ID. Project ID
may be None, which indicates that the Project ID could not be
ascertained from the environment.
Raises:
~google.auth.exceptions.DefaultCredentialsError:
If no credentials were found, or if the credentials found were
invalid.
"""
from google.auth.credentials import with_scopes_if_required
explicit_project_id = os.environ.get(
environment_vars.PROJECT, os.environ.get(environment_vars.LEGACY_PROJECT)
)
checkers = (
_get_explicit_environ_credentials,
_get_gcloud_sdk_credentials,
_get_gae_credentials,
lambda: _get_gce_credentials(request),
)
for checker in checkers:
credentials, project_id = checker()
if credentials is not None:
credentials = with_scopes_if_required(credentials, scopes)
if quota_project_id:
credentials = credentials.with_quota_project(quota_project_id)
effective_project_id = explicit_project_id or project_id
if not effective_project_id:
_LOGGER.warning(
"No project ID could be determined. Consider running "
"`gcloud config set project` or setting the %s "
"environment variable",
environment_vars.PROJECT,
)
return credentials, effective_project_id
> raise exceptions.DefaultCredentialsError(_HELP_MESSAGE)
E google.auth.exceptions.DefaultCredentialsError: Could not automatically determine credentials. Please set GOOGLE_APPLICATION_CREDENTIALS or explicitly create credentials and re-run the application. For more information, please see https://cloud.google.com/docs/authentication/getting-started
.nox/unit-3-6/lib/python3.6/site-packages/google/auth/_default.py:356: DefaultCredentialsError
=========================== short test summary info ============================
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_cannot_add_after_close
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_create_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_create_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_default_error_handler
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_delete_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_delete_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_delete_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_ensure_sending_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_flush_close_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_flush_sends_all_queued_batches
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_flush_sends_in_progress
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_handles_errors_and_successes_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_invokes_error_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_invokes_error_callbacks_successfully_multiple_retries
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_invokes_success_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_multiple_flushes
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_separates_same_document
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_separates_same_document_different_operation
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_serial_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_set_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_set_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_raises_with_bad_option
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_cannot_add_after_close
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_create_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_create_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_default_error_handler
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_delete_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_delete_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_delete_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_ensure_sending_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_flush_close_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_flush_sends_all_queued_batches
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_flush_sends_in_progress
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_handles_errors_and_successes_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_invokes_error_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_invokes_error_callbacks_successfully_multiple_retries
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_invokes_success_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_multiple_flushes
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_separates_same_document
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_separates_same_document_different_operation
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_serial_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_set_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_set_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_raises_with_bad_option
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestScheduling::test_max_in_flight_honored
FAILED tests/unit/v1/test_bulk_writer.py::TestScheduling::test_operation_retry_scheduling
============================= 52 failed in 10.50s ==============================
| 1.0 | Unit tests must not require credentials in environment - Creating an actual `Client` / `AsyncClient` instance without passing in credentials raises an error.
Better practice for anything not directly testing the client is to use `mock.create_autospec` to create
a dummy client.
```bash
$ git remote -v
origin git@github.com:googleapis/python-firestore (fetch)
origin git@github.com:googleapis/python-firestore (push)
$ git log -1
commit 51c92aa45156c5462f35991f65c02dcac49aacc3 (HEAD -> main, tag: v2.3.2, origin/main)
Author: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Date: Tue Sep 14 14:53:30 2021 -0700
chore: release 2.3.2 (#441)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
$ git status
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
$ env | grep GOOGLE || echo "No Credentials"
No Credentials
$ nox -e unit-3.6
...
________________ TestScheduling.test_operation_retry_scheduling ________________
self = <tests.unit.v1.test_bulk_writer.TestScheduling testMethod=test_operation_retry_scheduling>
def test_operation_retry_scheduling(self):
now = datetime.datetime.now()
one_second_from_now = now + datetime.timedelta(seconds=1)
> db = Client()
tests/unit/v1/test_bulk_writer.py:574:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
google/cloud/firestore_v1/client.py:99: in __init__
client_options=client_options,
google/cloud/firestore_v1/base_client.py:129: in __init__
_http=None,
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/client.py:249: in __init__
_ClientProjectMixin.__init__(self, project=project)
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/client.py:201: in __init__
project = self._determine_default(project)
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/client.py:216: in _determine_default
return _determine_default_project(project)
.nox/unit-3-6/lib/python3.6/site-packages/google/cloud/_helpers.py:186: in _determine_default_project
_, project = google.auth.default()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
scopes = None, request = None, quota_project_id = None
def default(scopes=None, request=None, quota_project_id=None):
"""Gets the default credentials for the current environment.
`Application Default Credentials`_ provides an easy way to obtain
credentials to call Google APIs for server-to-server or local applications.
This function acquires credentials from the environment in the following
order:
1. If the environment variable ``GOOGLE_APPLICATION_CREDENTIALS`` is set
to the path of a valid service account JSON private key file, then it is
loaded and returned. The project ID returned is the project ID defined
in the service account file if available (some older files do not
contain project ID information).
2. If the `Google Cloud SDK`_ is installed and has application default
credentials set they are loaded and returned.
To enable application default credentials with the Cloud SDK run::
gcloud auth application-default login
If the Cloud SDK has an active project, the project ID is returned. The
active project can be set using::
gcloud config set project
3. If the application is running in the `App Engine standard environment`_
(first generation) then the credentials and project ID from the
`App Identity Service`_ are used.
4. If the application is running in `Compute Engine`_ or `Cloud Run`_ or
the `App Engine flexible environment`_ or the `App Engine standard
environment`_ (second generation) then the credentials and project ID
are obtained from the `Metadata Service`_.
5. If no credentials are found,
:class:`~google.auth.exceptions.DefaultCredentialsError` will be raised.
.. _Application Default Credentials: https://developers.google.com\
/identity/protocols/application-default-credentials
.. _Google Cloud SDK: https://cloud.google.com/sdk
.. _App Engine standard environment: https://cloud.google.com/appengine
.. _App Identity Service: https://cloud.google.com/appengine/docs/python\
/appidentity/
.. _Compute Engine: https://cloud.google.com/compute
.. _App Engine flexible environment: https://cloud.google.com\
/appengine/flexible
.. _Metadata Service: https://cloud.google.com/compute/docs\
/storing-retrieving-metadata
.. _Cloud Run: https://cloud.google.com/run
Example::
import google.auth
credentials, project_id = google.auth.default()
Args:
scopes (Sequence[str]): The list of scopes for the credentials. If
specified, the credentials will automatically be scoped if
necessary.
request (google.auth.transport.Request): An object used to make
HTTP requests. This is used to detect whether the application
is running on Compute Engine. If not specified, then it will
use the standard library http client to make requests.
quota_project_id (Optional[str]): The project ID used for
quota and billing.
Returns:
Tuple[~google.auth.credentials.Credentials, Optional[str]]:
the current environment's credentials and project ID. Project ID
may be None, which indicates that the Project ID could not be
ascertained from the environment.
Raises:
~google.auth.exceptions.DefaultCredentialsError:
If no credentials were found, or if the credentials found were
invalid.
"""
from google.auth.credentials import with_scopes_if_required
explicit_project_id = os.environ.get(
environment_vars.PROJECT, os.environ.get(environment_vars.LEGACY_PROJECT)
)
checkers = (
_get_explicit_environ_credentials,
_get_gcloud_sdk_credentials,
_get_gae_credentials,
lambda: _get_gce_credentials(request),
)
for checker in checkers:
credentials, project_id = checker()
if credentials is not None:
credentials = with_scopes_if_required(credentials, scopes)
if quota_project_id:
credentials = credentials.with_quota_project(quota_project_id)
effective_project_id = explicit_project_id or project_id
if not effective_project_id:
_LOGGER.warning(
"No project ID could be determined. Consider running "
"`gcloud config set project` or setting the %s "
"environment variable",
environment_vars.PROJECT,
)
return credentials, effective_project_id
> raise exceptions.DefaultCredentialsError(_HELP_MESSAGE)
E google.auth.exceptions.DefaultCredentialsError: Could not automatically determine credentials. Please set GOOGLE_APPLICATION_CREDENTIALS or explicitly create credentials and re-run the application. For more information, please see https://cloud.google.com/docs/authentication/getting-started
.nox/unit-3-6/lib/python3.6/site-packages/google/auth/_default.py:356: DefaultCredentialsError
=========================== short test summary info ============================
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_cannot_add_after_close
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_create_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_create_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_default_error_handler
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_delete_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_delete_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_delete_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_ensure_sending_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_flush_close_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_flush_sends_all_queued_batches
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_flush_sends_in_progress
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_handles_errors_and_successes_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_invokes_error_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_invokes_error_callbacks_successfully_multiple_retries
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_invokes_success_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_multiple_flushes
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_separates_same_document
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_separates_same_document_different_operation
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_serial_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_set_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_set_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_raises_with_bad_option
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestSyncBulkWriter::test_update_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_cannot_add_after_close
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_create_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_create_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_default_error_handler
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_delete_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_delete_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_delete_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_ensure_sending_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_flush_close_repeatedly_callable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_flush_sends_all_queued_batches
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_flush_sends_in_progress
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_handles_errors_and_successes_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_invokes_error_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_invokes_error_callbacks_successfully_multiple_retries
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_invokes_success_callbacks_successfully
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_multiple_flushes
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_separates_same_document
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_separates_same_document_different_operation
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_serial_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_set_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_set_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_calls_send_correctly
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_raises_with_bad_option
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_retriable
FAILED tests/unit/v1/test_bulk_writer.py::TestAsyncBulkWriter::test_update_separates_batch
FAILED tests/unit/v1/test_bulk_writer.py::TestScheduling::test_max_in_flight_honored
FAILED tests/unit/v1/test_bulk_writer.py::TestScheduling::test_operation_retry_scheduling
============================= 52 failed in 10.50s ==============================
| non_infrastructure | unit tests must not require credentials in environment creating an actual client asyncclient instance without passing in credentials raises an error better practice for anything not directly testing the client is to use mock create autospec to create a dummy client bash git remote v origin git github com googleapis python firestore fetch origin git github com googleapis python firestore push git log commit head main tag origin main author release please date tue sep chore release co authored by release please git status on branch main your branch is up to date with origin main nothing to commit working tree clean env grep google echo no credentials no credentials nox e unit testscheduling test operation retry scheduling self def test operation retry scheduling self now datetime datetime now one second from now now datetime timedelta seconds db client tests unit test bulk writer py google cloud firestore client py in init client options client options google cloud firestore base client py in init http none nox unit lib site packages google cloud client py in init clientprojectmixin init self project project nox unit lib site packages google cloud client py in init project self determine default project nox unit lib site packages google cloud client py in determine default return determine default project project nox unit lib site packages google cloud helpers py in determine default project project google auth default scopes none request none quota project id none def default scopes none request none quota project id none gets the default credentials for the current environment application default credentials provides an easy way to obtain credentials to call google apis for server to server or local applications this function acquires credentials from the environment in the following order if the environment variable google application credentials is set to the path of a valid service account json private key file then it is loaded and returned the project id returned is the project id defined in the service account file if available some older files do not contain project id information if the google cloud sdk is installed and has application default credentials set they are loaded and returned to enable application default credentials with the cloud sdk run gcloud auth application default login if the cloud sdk has an active project the project id is returned the active project can be set using gcloud config set project if the application is running in the app engine standard environment first generation then the credentials and project id from the app identity service are used if the application is running in compute engine or cloud run or the app engine flexible environment or the app engine standard environment second generation then the credentials and project id are obtained from the metadata service if no credentials are found class google auth exceptions defaultcredentialserror will be raised application default credentials identity protocols application default credentials google cloud sdk app engine standard environment app identity service appidentity compute engine app engine flexible environment appengine flexible metadata service storing retrieving metadata cloud run example import google auth credentials project id google auth default args scopes sequence the list of scopes for the credentials if specified the credentials will automatically be scoped if necessary request google auth transport request an object used to make http requests this is used to detect whether the application is running on compute engine if not specified then it will use the standard library http client to make requests quota project id optional the project id used for quota and billing returns tuple the current environment s credentials and project id project id may be none which indicates that the project id could not be ascertained from the environment raises google auth exceptions defaultcredentialserror if no credentials were found or if the credentials found were invalid from google auth credentials import with scopes if required explicit project id os environ get environment vars project os environ get environment vars legacy project checkers get explicit environ credentials get gcloud sdk credentials get gae credentials lambda get gce credentials request for checker in checkers credentials project id checker if credentials is not none credentials with scopes if required credentials scopes if quota project id credentials credentials with quota project quota project id effective project id explicit project id or project id if not effective project id logger warning no project id could be determined consider running gcloud config set project or setting the s environment variable environment vars project return credentials effective project id raise exceptions defaultcredentialserror help message e google auth exceptions defaultcredentialserror could not automatically determine credentials please set google application credentials or explicitly create credentials and re run the application for more information please see nox unit lib site packages google auth default py defaultcredentialserror short test summary info failed tests unit test bulk writer py testsyncbulkwriter test cannot add after close failed tests unit test bulk writer py testsyncbulkwriter test create calls send correctly failed tests unit test bulk writer py testsyncbulkwriter test create retriable failed tests unit test bulk writer py testsyncbulkwriter test default error handler failed tests unit test bulk writer py testsyncbulkwriter test delete calls send correctly failed tests unit test bulk writer py testsyncbulkwriter test delete retriable failed tests unit test bulk writer py testsyncbulkwriter test delete separates batch failed tests unit test bulk writer py testsyncbulkwriter test ensure sending repeatedly callable failed tests unit test bulk writer py testsyncbulkwriter test flush close repeatedly callable failed tests unit test bulk writer py testsyncbulkwriter test flush sends all queued batches failed tests unit test bulk writer py testsyncbulkwriter test flush sends in progress failed tests unit test bulk writer py testsyncbulkwriter test handles errors and successes correctly failed tests unit test bulk writer py testsyncbulkwriter test invokes error callbacks successfully failed tests unit test bulk writer py testsyncbulkwriter test invokes error callbacks successfully multiple retries failed tests unit test bulk writer py testsyncbulkwriter test invokes success callbacks successfully failed tests unit test bulk writer py testsyncbulkwriter test multiple flushes failed tests unit test bulk writer py testsyncbulkwriter test separates same document failed tests unit test bulk writer py testsyncbulkwriter test separates same document different operation failed tests unit test bulk writer py testsyncbulkwriter test serial calls send correctly failed tests unit test bulk writer py testsyncbulkwriter test set calls send correctly failed tests unit test bulk writer py testsyncbulkwriter test set retriable failed tests unit test bulk writer py testsyncbulkwriter test update calls send correctly failed tests unit test bulk writer py testsyncbulkwriter test update raises with bad option failed tests unit test bulk writer py testsyncbulkwriter test update retriable failed tests unit test bulk writer py testsyncbulkwriter test update separates batch failed tests unit test bulk writer py testasyncbulkwriter test cannot add after close failed tests unit test bulk writer py testasyncbulkwriter test create calls send correctly failed tests unit test bulk writer py testasyncbulkwriter test create retriable failed tests unit test bulk writer py testasyncbulkwriter test default error handler failed tests unit test bulk writer py testasyncbulkwriter test delete calls send correctly failed tests unit test bulk writer py testasyncbulkwriter test delete retriable failed tests unit test bulk writer py testasyncbulkwriter test delete separates batch failed tests unit test bulk writer py testasyncbulkwriter test ensure sending repeatedly callable failed tests unit test bulk writer py testasyncbulkwriter test flush close repeatedly callable failed tests unit test bulk writer py testasyncbulkwriter test flush sends all queued batches failed tests unit test bulk writer py testasyncbulkwriter test flush sends in progress failed tests unit test bulk writer py testasyncbulkwriter test handles errors and successes correctly failed tests unit test bulk writer py testasyncbulkwriter test invokes error callbacks successfully failed tests unit test bulk writer py testasyncbulkwriter test invokes error callbacks successfully multiple retries failed tests unit test bulk writer py testasyncbulkwriter test invokes success callbacks successfully failed tests unit test bulk writer py testasyncbulkwriter test multiple flushes failed tests unit test bulk writer py testasyncbulkwriter test separates same document failed tests unit test bulk writer py testasyncbulkwriter test separates same document different operation failed tests unit test bulk writer py testasyncbulkwriter test serial calls send correctly failed tests unit test bulk writer py testasyncbulkwriter test set calls send correctly failed tests unit test bulk writer py testasyncbulkwriter test set retriable failed tests unit test bulk writer py testasyncbulkwriter test update calls send correctly failed tests unit test bulk writer py testasyncbulkwriter test update raises with bad option failed tests unit test bulk writer py testasyncbulkwriter test update retriable failed tests unit test bulk writer py testasyncbulkwriter test update separates batch failed tests unit test bulk writer py testscheduling test max in flight honored failed tests unit test bulk writer py testscheduling test operation retry scheduling failed in | 0 |
163,131 | 13,911,735,444 | IssuesEvent | 2020-10-20 17:49:29 | openservicemesh/osm | https://api.github.com/repos/openservicemesh/osm | closed | Document OSM ConfigMap - possible keys, values, and the effects these have | P2 documentation dynamic-config | Please document the OSM ConfigMap:
- What's the name of the ConfigMap, which namespace is it, can this be changed?
- What are the possible keys in the ConfigMap?
- What are the the possible values?
- What are the default values for omitted keys?
- What does each key/value do? What effects does it have on the OSM Controller and service mesh?
- What's an example of how to change the value for a given key?
I can imagine this being done in a tabular format. For example
| Key | possible values | default value | function |
|----|---|---|---|
| envoy_log_level | trace, debug, info, warning, warn, error, critical, off | error | Sets the verbosity of the logging of Envoys joining the OSM service mesh. |
Potential location for this document: `./docs/config.md` | 1.0 | Document OSM ConfigMap - possible keys, values, and the effects these have - Please document the OSM ConfigMap:
- What's the name of the ConfigMap, which namespace is it, can this be changed?
- What are the possible keys in the ConfigMap?
- What are the the possible values?
- What are the default values for omitted keys?
- What does each key/value do? What effects does it have on the OSM Controller and service mesh?
- What's an example of how to change the value for a given key?
I can imagine this being done in a tabular format. For example
| Key | possible values | default value | function |
|----|---|---|---|
| envoy_log_level | trace, debug, info, warning, warn, error, critical, off | error | Sets the verbosity of the logging of Envoys joining the OSM service mesh. |
Potential location for this document: `./docs/config.md` | non_infrastructure | document osm configmap possible keys values and the effects these have please document the osm configmap what s the name of the configmap which namespace is it can this be changed what are the possible keys in the configmap what are the the possible values what are the default values for omitted keys what does each key value do what effects does it have on the osm controller and service mesh what s an example of how to change the value for a given key i can imagine this being done in a tabular format for example key possible values default value function envoy log level trace debug info warning warn error critical off error sets the verbosity of the logging of envoys joining the osm service mesh potential location for this document docs config md | 0 |
586,625 | 17,593,732,457 | IssuesEvent | 2021-08-17 00:03:48 | godaddy-wordpress/coblocks | https://api.github.com/repos/godaddy-wordpress/coblocks | opened | Click to Tweet block using incorrect slug for scheduled posts | [Type] Bug [Priority] Low | ### Describe the bug:
When adding a Click to Tweet block, I should be able to set it up and it will work when the post is published. However, if you adding the block and schedule the post for some future date, the date in the URL that the block provides will still be the date on which you clicked 'schedule' and not the date that it was actually published. If you edit the post after it has been published then it will correct the URL in the tweet block, but that sort of defeats the point of scheduling a post.
This looks like the same problem causing the bug in #1663, but I can't say that with certainty.
### To reproduce:
1. Make sure your site uses the post date in the post permalinks
2. Add a 'Click to Tweet' block to a post
2. Schedule the post to be published on any future date (even the following day)
3. Once published, click the 'tweet' button in the block and you'll see the date in the URL is the date on which you created the post, not the actual publish date - this causes a broken link in the tweet
### Expected behavior:
I expect that the URL in the tweet would update to be whatever the post's URL is, rather than storing the URL in the block itself.
### Isolating the problem:
- [x] This bug happens with no other plugins activated
- [x] This bug happens with a default WordPress theme active
- [x] This bug happens **without** the Gutenberg plugin active
- [x] I can reproduce this bug consistently using the steps above
### WordPress version:
5.8 | 1.0 | Click to Tweet block using incorrect slug for scheduled posts - ### Describe the bug:
When adding a Click to Tweet block, I should be able to set it up and it will work when the post is published. However, if you adding the block and schedule the post for some future date, the date in the URL that the block provides will still be the date on which you clicked 'schedule' and not the date that it was actually published. If you edit the post after it has been published then it will correct the URL in the tweet block, but that sort of defeats the point of scheduling a post.
This looks like the same problem causing the bug in #1663, but I can't say that with certainty.
### To reproduce:
1. Make sure your site uses the post date in the post permalinks
2. Add a 'Click to Tweet' block to a post
2. Schedule the post to be published on any future date (even the following day)
3. Once published, click the 'tweet' button in the block and you'll see the date in the URL is the date on which you created the post, not the actual publish date - this causes a broken link in the tweet
### Expected behavior:
I expect that the URL in the tweet would update to be whatever the post's URL is, rather than storing the URL in the block itself.
### Isolating the problem:
- [x] This bug happens with no other plugins activated
- [x] This bug happens with a default WordPress theme active
- [x] This bug happens **without** the Gutenberg plugin active
- [x] I can reproduce this bug consistently using the steps above
### WordPress version:
5.8 | non_infrastructure | click to tweet block using incorrect slug for scheduled posts describe the bug when adding a click to tweet block i should be able to set it up and it will work when the post is published however if you adding the block and schedule the post for some future date the date in the url that the block provides will still be the date on which you clicked schedule and not the date that it was actually published if you edit the post after it has been published then it will correct the url in the tweet block but that sort of defeats the point of scheduling a post this looks like the same problem causing the bug in but i can t say that with certainty to reproduce make sure your site uses the post date in the post permalinks add a click to tweet block to a post schedule the post to be published on any future date even the following day once published click the tweet button in the block and you ll see the date in the url is the date on which you created the post not the actual publish date this causes a broken link in the tweet expected behavior i expect that the url in the tweet would update to be whatever the post s url is rather than storing the url in the block itself isolating the problem this bug happens with no other plugins activated this bug happens with a default wordpress theme active this bug happens without the gutenberg plugin active i can reproduce this bug consistently using the steps above wordpress version | 0 |
30,964 | 14,708,656,800 | IssuesEvent | 2021-01-05 00:17:15 | theCrag/website | https://api.github.com/repos/theCrag/website | closed | add routes concurrency problem? | 2: Bug fix Content editing Performance | I added to a crag in France 4 sectors. Open an "add route form" for each sector with 20 routes. Then I went on the train from work to home and filled the 4 forms with routes for each sector.
At home is send the form data (i am offline at the train) as I have done this several times before. This time i did not wait with the second form until the first form was done. More or less i send all 4 forms at once (of course with minor time delay). The result was that two forms returned with some error (unfortunately i did not notice the error message it was an SQL error and something with locking of tables). I pressed reload for both forms and the next error was that all there are already routes with the same names for all routes.
Now the state is that all routes have been added but not some parents to not know about it.
Have a look to: http://www.thecrag.com/climbing/france/baume-rousse
1 Gauche Facile Sector All Sport 17 0
2 Gauche Compétition Sector - 0 0
3 Droite Compétition Sector - 0 0
4 Droite Initiation Sector All Sport 20 0
You see that sectors 2 and 3 have no routes. If you click on the name of the sector you go to the sector page and will not see any children.
If you click on the "0" climbs you will go to the "search all routes in the node" page and you will see all routes.
Any Ideas?
Nicky
| True | add routes concurrency problem? - I added to a crag in France 4 sectors. Open an "add route form" for each sector with 20 routes. Then I went on the train from work to home and filled the 4 forms with routes for each sector.
At home is send the form data (i am offline at the train) as I have done this several times before. This time i did not wait with the second form until the first form was done. More or less i send all 4 forms at once (of course with minor time delay). The result was that two forms returned with some error (unfortunately i did not notice the error message it was an SQL error and something with locking of tables). I pressed reload for both forms and the next error was that all there are already routes with the same names for all routes.
Now the state is that all routes have been added but not some parents to not know about it.
Have a look to: http://www.thecrag.com/climbing/france/baume-rousse
1 Gauche Facile Sector All Sport 17 0
2 Gauche Compétition Sector - 0 0
3 Droite Compétition Sector - 0 0
4 Droite Initiation Sector All Sport 20 0
You see that sectors 2 and 3 have no routes. If you click on the name of the sector you go to the sector page and will not see any children.
If you click on the "0" climbs you will go to the "search all routes in the node" page and you will see all routes.
Any Ideas?
Nicky
| non_infrastructure | add routes concurrency problem i added to a crag in france sectors open an add route form for each sector with routes then i went on the train from work to home and filled the forms with routes for each sector at home is send the form data i am offline at the train as i have done this several times before this time i did not wait with the second form until the first form was done more or less i send all forms at once of course with minor time delay the result was that two forms returned with some error unfortunately i did not notice the error message it was an sql error and something with locking of tables i pressed reload for both forms and the next error was that all there are already routes with the same names for all routes now the state is that all routes have been added but not some parents to not know about it have a look to gauche facile sector all sport gauche compétition sector droite compétition sector droite initiation sector all sport you see that sectors and have no routes if you click on the name of the sector you go to the sector page and will not see any children if you click on the climbs you will go to the search all routes in the node page and you will see all routes any ideas nicky | 0 |
33,109 | 27,237,384,001 | IssuesEvent | 2023-02-21 17:19:13 | nanovms/ops | https://api.github.com/repos/nanovms/ops | closed | investigate provisioning to linode | infrastructure | i'm willing to bet this is the same as vultr && do so should be straight-forward to implement
https://github.com/nanovms/nanos/issues/682 | 1.0 | investigate provisioning to linode - i'm willing to bet this is the same as vultr && do so should be straight-forward to implement
https://github.com/nanovms/nanos/issues/682 | infrastructure | investigate provisioning to linode i m willing to bet this is the same as vultr do so should be straight forward to implement | 1 |
21,259 | 14,482,472,984 | IssuesEvent | 2020-12-10 14:01:38 | bids-standard/bids-specification | https://api.github.com/repos/bids-standard/bids-specification | closed | Migrate "Travis CI" service to "GitHub Actions" CI service | good first issue infrastructure | see https://github.com/bids-standard/bids-specification/pull/669#issuecomment-735686840 for context.
The job involved taking this file: https://github.com/bids-standard/bids-specification/blob/fb6f15c1530d60356b0d1b643c9f969ec5ccb3fc/.travis.yml#L1-L22
and migrating it to similar workflows here (creating new files): https://github.com/bids-standard/bids-specification/tree/master/.github/workflows | 1.0 | Migrate "Travis CI" service to "GitHub Actions" CI service - see https://github.com/bids-standard/bids-specification/pull/669#issuecomment-735686840 for context.
The job involved taking this file: https://github.com/bids-standard/bids-specification/blob/fb6f15c1530d60356b0d1b643c9f969ec5ccb3fc/.travis.yml#L1-L22
and migrating it to similar workflows here (creating new files): https://github.com/bids-standard/bids-specification/tree/master/.github/workflows | infrastructure | migrate travis ci service to github actions ci service see for context the job involved taking this file and migrating it to similar workflows here creating new files | 1 |
23,732 | 11,944,910,107 | IssuesEvent | 2020-04-03 04:02:18 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | How to train If data-set is more than 52Mb size | Pri2 cognitive-services/svc cxp forms-recognizer/subsvc product-question triaged | Hi ,
During training i came to know that If my train dataset folder content is more than 52 Mb size it throws error saying exceeding the limit , how can i overcome this and if not what are the other options to train large dataset.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 18818774-5076-cb76-ee9e-4ecb632b6caa
* Version Independent ID: 22d60153-50fc-024e-6249-edc796dcdf19
* Content: [Quickstart: Train a model and extract form data using the REST API with Python - Form Recognizer - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/form-recognizer/quickstarts/python-train-extract#feedback)
* Content Source: [articles/cognitive-services/form-recognizer/quickstarts/python-train-extract.md](https://github.com/Microsoft/azure-docs/blob/master/articles/cognitive-services/form-recognizer/quickstarts/python-train-extract.md)
* Service: **cognitive-services**
* Sub-service: **forms-recognizer**
* GitHub Login: @PatrickFarley
* Microsoft Alias: **pafarley** | 1.0 | How to train If data-set is more than 52Mb size - Hi ,
During training i came to know that If my train dataset folder content is more than 52 Mb size it throws error saying exceeding the limit , how can i overcome this and if not what are the other options to train large dataset.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 18818774-5076-cb76-ee9e-4ecb632b6caa
* Version Independent ID: 22d60153-50fc-024e-6249-edc796dcdf19
* Content: [Quickstart: Train a model and extract form data using the REST API with Python - Form Recognizer - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/form-recognizer/quickstarts/python-train-extract#feedback)
* Content Source: [articles/cognitive-services/form-recognizer/quickstarts/python-train-extract.md](https://github.com/Microsoft/azure-docs/blob/master/articles/cognitive-services/form-recognizer/quickstarts/python-train-extract.md)
* Service: **cognitive-services**
* Sub-service: **forms-recognizer**
* GitHub Login: @PatrickFarley
* Microsoft Alias: **pafarley** | non_infrastructure | how to train if data set is more than size hi during training i came to know that if my train dataset folder content is more than mb size it throws error saying exceeding the limit how can i overcome this and if not what are the other options to train large dataset document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service cognitive services sub service forms recognizer github login patrickfarley microsoft alias pafarley | 0 |
14,175 | 9,205,788,899 | IssuesEvent | 2019-03-08 11:39:44 | delphi-hub/delphi-management | https://api.github.com/repos/delphi-hub/delphi-management | closed | User Authentication (simple username/password login) | enhancement security | **Feature**
The current Landingpage should be replaced by a basic login mask in which the user can provide a username and password.
**Data flow scheme for Authentication**
1. The username & password should be send to a (new) authenticate endpoint of the scala play webserver.
2. On the scala play webserver a component token is added to the request and it is forwarded to the authorization endpoint of the instance registry.
3. The ir responds with a user token, which is send as a response to the client
4. The client stores the user token and appends it to every request as needed
@johannesduesing what is the lifetime of the user token and do you have a plan in place to refresh the user token?
@Ayybeeshafi will handle the extensions needed on the server side, while I will make the necessary extensions in the api service of the frontend.
@ishwaryaPaderborn if you like you could provide a design for a login page (do we already have something like this in place?)
| True | User Authentication (simple username/password login) - **Feature**
The current Landingpage should be replaced by a basic login mask in which the user can provide a username and password.
**Data flow scheme for Authentication**
1. The username & password should be send to a (new) authenticate endpoint of the scala play webserver.
2. On the scala play webserver a component token is added to the request and it is forwarded to the authorization endpoint of the instance registry.
3. The ir responds with a user token, which is send as a response to the client
4. The client stores the user token and appends it to every request as needed
@johannesduesing what is the lifetime of the user token and do you have a plan in place to refresh the user token?
@Ayybeeshafi will handle the extensions needed on the server side, while I will make the necessary extensions in the api service of the frontend.
@ishwaryaPaderborn if you like you could provide a design for a login page (do we already have something like this in place?)
| non_infrastructure | user authentication simple username password login feature the current landingpage should be replaced by a basic login mask in which the user can provide a username and password data flow scheme for authentication the username password should be send to a new authenticate endpoint of the scala play webserver on the scala play webserver a component token is added to the request and it is forwarded to the authorization endpoint of the instance registry the ir responds with a user token which is send as a response to the client the client stores the user token and appends it to every request as needed johannesduesing what is the lifetime of the user token and do you have a plan in place to refresh the user token ayybeeshafi will handle the extensions needed on the server side while i will make the necessary extensions in the api service of the frontend ishwaryapaderborn if you like you could provide a design for a login page do we already have something like this in place | 0 |
161,714 | 12,559,415,005 | IssuesEvent | 2020-06-07 18:53:02 | GTNewHorizons/GT-New-Horizons-Modpack | https://api.github.com/repos/GTNewHorizons/GT-New-Horizons-Modpack | closed | Quest 2025 not detecting items | FixedInDev Quest change need to be tested | Playing GTNH 2.0.8.3.
GT++ knowledge, id 2025, does not detect any of the four books.
Using the name remover does NOT help. | 1.0 | Quest 2025 not detecting items - Playing GTNH 2.0.8.3.
GT++ knowledge, id 2025, does not detect any of the four books.
Using the name remover does NOT help. | non_infrastructure | quest not detecting items playing gtnh gt knowledge id does not detect any of the four books using the name remover does not help | 0 |
230,429 | 7,610,118,596 | IssuesEvent | 2018-05-01 05:53:28 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | Unable to schedule new pods | component/kubernetes kind/question lifecycle/rotten priority/P2 | Suddenly Openshift is not able to schedule new pods: when a pod is deleted or when a new deployment starts. Any Idea what is causing this? Could this be handled with priority as we cannot restart any pods in our production cluster right now.
Thanks in Advanced!
##### Version
oc v1.5.0
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://mxt-ocmaster.newyse.maxxton:8443
openshift v1.5.0
kubernetes v1.5.2+43a9be4
##### Steps To Reproduce
1. Delete a pod from a replica controller
##### Current Result
- replica controller is showing 'scaling 0 to 1', but the new pod is never creating
##### Expected Result
- The replica controller is starting the new pod
##### Additional Information
```
[Note] Determining if client configuration exists for client/cluster diagnostics
Info: Successfully read a client config file at '/root/.kube/config'
Info: Using context for cluster-admin access: 'mxts-prod/mxt-ocmaster-newyse-maxxton:8443/system:admin'
[Note] Performing systemd discovery
[Note] Running diagnostic: ConfigContexts[openshift/mxt-ocmaster-newyse-maxxton:8443/system:admin]
Description: Validate client config context is complete and has connectivity
Info: For client config context 'openshift/mxt-ocmaster-newyse-maxxton:8443/system:admin':
The server URL is 'https://mxt-ocmaster.newyse.maxxton:8443'
The user authentication is 'system:admin/mxt-ocmaster-newyse-maxxton:8443'
The current project is 'openshift'
Successfully requested project list; has access to project(s):
[default kube-system logging management-infra mcms-acc mcms-prod mxts-acc mxts-prod network-diag-ns-0bb8q network-diag-ns-4xs54 ...]
[Note] Running diagnostic: DiagnosticPod
Description: Create a pod to run diagnostics from the application standpoint
Info: Output from the diagnostic pod (image openshift/origin-deployer:v1.5.0):
[Note] Running diagnostic: PodCheckAuth
Description: Check that service account credentials authenticate as expected
Info: Service account token successfully authenticated to master
Info: Service account token was authenticated by the integrated registry.
[Note] Running diagnostic: PodCheckDns
Description: Check that DNS within a pod works as expected
[Note] Summary of diagnostics execution (version v1.5.0+031cbe4):
[Note] Completed with no errors or warnings seen.
[Note] Running diagnostic: NetworkCheck
Description: Create a pod on all schedulable nodes and run network diagnostics from the application standpoint
ERROR: [DNet3001 from diagnostic NetworkCheck@openshift/origin/pkg/diagnostics/network/setup.go:62]
Failed to create network diags test pod and service: [Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-r1nl2' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-r1nl2" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-rg890' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-rg890" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-tgnjl' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-tgnjl" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-b6f7c' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-b6f7c" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-b8h1t' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-b8h1t" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-2lxd8' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-2lxd8" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-kbzc1' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-kbzc1" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-7vv9h' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-7vv9h" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-gwpld' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-gwpld" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-f0l5j' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-f0l5j" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-dwbxl' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-dwbxl" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-0b7g9' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-0b7g9" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-dngdh' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-dngdh" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-qq3kj' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-qq3kj" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-6l223' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-6l223" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-1d9jt' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-1d9jt" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-nt9jz' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-nt9jz" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-g61bg' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-g61bg" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-dtzqz' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-dtzqz" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-0xq22' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-0xq22" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-hvsjc' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-hvsjc" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-q0275' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-q0275" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-vfbzs' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-vfbzs" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-m8f1s' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-m8f1s" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-g989c' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-g989c" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-323s8' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-323s8" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-nwxg1' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-nwxg1" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-c1pfb' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-c1pfb" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-1q1jw' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-1q1jw" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-9cchz' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-9cchz" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-rjs1n' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-rjs1n" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-x25fg' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-x25fg" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-f2v11' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-f2v11" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-mdc1b' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-mdc1b" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-0vzz2' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-0vzz2" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-dh24j' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-dh24j" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-41q0n' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-41q0n" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-bzwbg' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-bzwbg" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-c7s5g' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-c7s5g" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-q471h' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-q471h" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-7rq8k' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-7rq8k" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-c5k72' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-c5k72" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-96jdk' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-96jdk" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-c2xpw' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-c2xpw" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-vb870' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-vb870" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-mvrnt' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-mvrnt" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-cw0hs' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-cw0hs" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-sk0cs' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-sk0cs" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-97vgn' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-97vgn" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-9cpzk' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-9cpzk" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-ccsw2' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-ccsw2" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-p48gl' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-p48gl" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-465n7' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-465n7" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-cg7t3' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-cg7t3" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-58xwg' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-58xwg" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-f9mhn' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-f9mhn" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-p6sxt' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-p6sxt" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-q9pmh' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-q9pmh" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-64ttr' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-64ttr" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-lbx16' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-lbx16" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-vzpdn' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-vzpdn" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-qxfpj' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-qxfpj" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-txrh4' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-txrh4" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-gx9gd' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-gx9gd" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-3xscd' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-3xscd" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-bjx2x' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-bjx2x" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-n3r6d' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-n3r6d" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-m6jhc' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-m6jhc" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created]
ERROR: [DNet2006 from diagnostic NetworkCheck@openshift/origin/pkg/diagnostics/network/run_pod.go:136]
Creating network diagnostic pod "network-diag-pod-45dx8" on node "mxt-ocinfra01.newyse.maxxton" with command "openshift infra network-diagnostic-pod -l 1" failed: pods "network-diag-pod-45dx8" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created
[Note] Skipping diagnostic: AggregatedLogging
Description: Check aggregated logging integration for proper configuration
Because: No LoggingPublicURL is defined in the master configuration
[Note] Running diagnostic: ClusterRegistry
Description: Check that there is a working Docker registry
[Note] Running diagnostic: ClusterRoleBindings
Description: Check that the default ClusterRoleBindings are present and contain the expected subjects
Info: clusterrolebinding/cluster-admins has more subjects than expected.
Use the `oadm policy reconcile-cluster-role-bindings` command to update the role binding to remove extra subjects.
Info: clusterrolebinding/cluster-admins has extra subject {User vxadm-mol }.
Info: clusterrolebinding/cluster-admins has extra subject {Group ug-vx-admin }.
Info: clusterrolebinding/cluster-admins has extra subject {Group ug-mx-openshift }.
Info: clusterrolebinding/cluster-readers has more subjects than expected.
Use the `oadm policy reconcile-cluster-role-bindings` command to update the role binding to remove extra subjects.
Info: clusterrolebinding/cluster-readers has extra subject {ServiceAccount management-infra management-admin }.
Info: clusterrolebinding/cluster-readers has extra subject {ServiceAccount default router }.
Info: clusterrolebinding/cluster-readers has extra subject {ServiceAccount openshift-infra heapster }.
Info: clusterrolebinding/self-provisioners has more subjects than expected.
Use the `oadm policy reconcile-cluster-role-bindings` command to update the role binding to remove extra subjects.
Info: clusterrolebinding/self-provisioners has extra subject {ServiceAccount management-infra management-admin }.
[Note] Running diagnostic: ClusterRoles
Description: Check that the default ClusterRoles are present and contain the expected permissions
[Note] Running diagnostic: ClusterRouterName
Description: Check there is a working router
[Note] Running diagnostic: MasterNode
Description: Check if master is also running node (for Open vSwitch)
Info: Found a node with same IP as master: mxt-ocrouter01.newyse.maxxton
[Note] Running diagnostic: MetricsApiProxy
Description: Check the integrated heapster metrics can be reached via the API proxy
[Note] Running diagnostic: NodeDefinitions
Description: Check node records on master
WARN: [DClu0003 from diagnostic NodeDefinition@openshift/origin/pkg/diagnostics/cluster/node_definitions.go:112]
Node mxt-ocmaster01.newyse.maxxton is ready but is marked Unschedulable.
This is usually set manually for administrative reasons.
An administrator can mark the node schedulable with:
oadm manage-node mxt-ocmaster01.newyse.maxxton --schedulable=true
While in this state, pods should not be scheduled to deploy on the node.
Existing pods will continue to run until completed or evacuated (see
other options for 'oadm manage-node').
WARN: [DClu0003 from diagnostic NodeDefinition@openshift/origin/pkg/diagnostics/cluster/node_definitions.go:112]
Node mxt-ocmaster02.newyse.maxxton is ready but is marked Unschedulable.
This is usually set manually for administrative reasons.
An administrator can mark the node schedulable with:
oadm manage-node mxt-ocmaster02.newyse.maxxton --schedulable=true
While in this state, pods should not be scheduled to deploy on the node.
Existing pods will continue to run until completed or evacuated (see
other options for 'oadm manage-node').
WARN: [DClu0003 from diagnostic NodeDefinition@openshift/origin/pkg/diagnostics/cluster/node_definitions.go:112]
Node mxt-ocmaster03.newyse.maxxton is ready but is marked Unschedulable.
This is usually set manually for administrative reasons.
An administrator can mark the node schedulable with:
oadm manage-node mxt-ocmaster03.newyse.maxxton --schedulable=true
While in this state, pods should not be scheduled to deploy on the node.
Existing pods will continue to run until completed or evacuated (see
other options for 'oadm manage-node').
[Note] Running diagnostic: ServiceExternalIPs
Description: Check for existing services with ExternalIPs that are disallowed by master config
[Note] Running diagnostic: AnalyzeLogs
Description: Check for recent problems in systemd service logs
Info: Checking journalctl logs for 'origin-node' service
Info: Checking journalctl logs for 'docker' service
[Note] Running diagnostic: MasterConfigCheck
Description: Check the master config file
WARN: [DH0005 from diagnostic MasterConfigCheck@openshift/origin/pkg/diagnostics/host/check_master_config.go:52]
Validation of master config file '/etc/origin/master/master-config.yaml' warned:
assetConfig.loggingPublicURL: Invalid value: "": required to view aggregated container logs in the console
oauthConfig.identityProvider[0].provider.insecure: Invalid value: true: validating passwords over an insecure connection could allow them to be intercepted
auditConfig.auditFilePath: Required value: audit can now be logged to a separate file
[Note] Running diagnostic: NodeConfigCheck
Description: Check the node config file
Info: Found a node config file: /etc/origin/node/node-config.yaml
[Note] Running diagnostic: UnitStatus
Description: Check status for related systemd units
[Note] Summary of diagnostics execution (version v1.5.0):
[Note] Warnings seen: 4
[Note] Errors seen: 2
``` | 1.0 | Unable to schedule new pods - Suddenly Openshift is not able to schedule new pods: when a pod is deleted or when a new deployment starts. Any Idea what is causing this? Could this be handled with priority as we cannot restart any pods in our production cluster right now.
Thanks in Advanced!
##### Version
oc v1.5.0
kubernetes v1.5.2+43a9be4
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://mxt-ocmaster.newyse.maxxton:8443
openshift v1.5.0
kubernetes v1.5.2+43a9be4
##### Steps To Reproduce
1. Delete a pod from a replica controller
##### Current Result
- replica controller is showing 'scaling 0 to 1', but the new pod is never creating
##### Expected Result
- The replica controller is starting the new pod
##### Additional Information
```
[Note] Determining if client configuration exists for client/cluster diagnostics
Info: Successfully read a client config file at '/root/.kube/config'
Info: Using context for cluster-admin access: 'mxts-prod/mxt-ocmaster-newyse-maxxton:8443/system:admin'
[Note] Performing systemd discovery
[Note] Running diagnostic: ConfigContexts[openshift/mxt-ocmaster-newyse-maxxton:8443/system:admin]
Description: Validate client config context is complete and has connectivity
Info: For client config context 'openshift/mxt-ocmaster-newyse-maxxton:8443/system:admin':
The server URL is 'https://mxt-ocmaster.newyse.maxxton:8443'
The user authentication is 'system:admin/mxt-ocmaster-newyse-maxxton:8443'
The current project is 'openshift'
Successfully requested project list; has access to project(s):
[default kube-system logging management-infra mcms-acc mcms-prod mxts-acc mxts-prod network-diag-ns-0bb8q network-diag-ns-4xs54 ...]
[Note] Running diagnostic: DiagnosticPod
Description: Create a pod to run diagnostics from the application standpoint
Info: Output from the diagnostic pod (image openshift/origin-deployer:v1.5.0):
[Note] Running diagnostic: PodCheckAuth
Description: Check that service account credentials authenticate as expected
Info: Service account token successfully authenticated to master
Info: Service account token was authenticated by the integrated registry.
[Note] Running diagnostic: PodCheckDns
Description: Check that DNS within a pod works as expected
[Note] Summary of diagnostics execution (version v1.5.0+031cbe4):
[Note] Completed with no errors or warnings seen.
[Note] Running diagnostic: NetworkCheck
Description: Create a pod on all schedulable nodes and run network diagnostics from the application standpoint
ERROR: [DNet3001 from diagnostic NetworkCheck@openshift/origin/pkg/diagnostics/network/setup.go:62]
Failed to create network diags test pod and service: [Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-r1nl2' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-r1nl2" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-rg890' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-rg890" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-tgnjl' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-tgnjl" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-b6f7c' on node "mxt-ocinfra01.newyse.maxxton" failed: pods "network-diag-test-pod-b6f7c" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-b8h1t' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-b8h1t" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-2lxd8' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-2lxd8" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-kbzc1' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-kbzc1" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-7vv9h' on node "mxt-ocrouter01.newyse.maxxton" failed: pods "network-diag-test-pod-7vv9h" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-gwpld' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-gwpld" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-f0l5j' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-f0l5j" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-dwbxl' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-dwbxl" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-0b7g9' on node "mxt-ocrouter02.newyse.maxxton" failed: pods "network-diag-test-pod-0b7g9" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-dngdh' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-dngdh" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-qq3kj' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-qq3kj" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-6l223' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-6l223" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-1d9jt' on node "mxt-ocrouter03.newyse.maxxton" failed: pods "network-diag-test-pod-1d9jt" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-nt9jz' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-nt9jz" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-g61bg' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-g61bg" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-dtzqz' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-dtzqz" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-0xq22' on node "mxt-ocrouter04.newyse.maxxton" failed: pods "network-diag-test-pod-0xq22" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-hvsjc' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-hvsjc" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-q0275' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-q0275" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-vfbzs' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-vfbzs" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-m8f1s' on node "mxt-ocslave01.newyse.maxxton" failed: pods "network-diag-test-pod-m8f1s" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-g989c' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-g989c" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-323s8' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-323s8" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-nwxg1' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-nwxg1" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-c1pfb' on node "mxt-ocslave02.newyse.maxxton" failed: pods "network-diag-test-pod-c1pfb" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-1q1jw' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-1q1jw" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-9cchz' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-9cchz" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-rjs1n' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-rjs1n" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-x25fg' on node "mxt-ocslave03.newyse.maxxton" failed: pods "network-diag-test-pod-x25fg" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-f2v11' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-f2v11" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-mdc1b' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-mdc1b" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-0vzz2' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-0vzz2" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-dh24j' on node "mxt-ocslave04.newyse.maxxton" failed: pods "network-diag-test-pod-dh24j" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-41q0n' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-41q0n" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-bzwbg' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-bzwbg" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-c7s5g' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-c7s5g" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-q471h' on node "mxt-ocslave05.newyse.maxxton" failed: pods "network-diag-test-pod-q471h" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-7rq8k' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-7rq8k" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-c5k72' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-c5k72" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-96jdk' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-96jdk" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-c2xpw' on node "mxt-ocslave06.newyse.maxxton" failed: pods "network-diag-test-pod-c2xpw" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-vb870' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-vb870" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-mvrnt' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-mvrnt" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-cw0hs' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-cw0hs" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-sk0cs' on node "mxt-ocslave07.newyse.maxxton" failed: pods "network-diag-test-pod-sk0cs" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-97vgn' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-97vgn" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-9cpzk' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-9cpzk" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-ccsw2' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-ccsw2" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-p48gl' on node "mxt-ocslave08.newyse.maxxton" failed: pods "network-diag-test-pod-p48gl" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-465n7' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-465n7" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-cg7t3' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-cg7t3" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-58xwg' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-58xwg" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-f9mhn' on node "mxt-ocslave09.newyse.maxxton" failed: pods "network-diag-test-pod-f9mhn" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-p6sxt' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-p6sxt" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-q9pmh' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-q9pmh" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-64ttr' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-64ttr" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-lbx16' on node "mxt-ocslave10.newyse.maxxton" failed: pods "network-diag-test-pod-lbx16" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-vzpdn' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-vzpdn" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-qxfpj' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-qxfpj" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-txrh4' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-txrh4" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-gx9gd' on node "mxt-ocslave11.newyse.maxxton" failed: pods "network-diag-test-pod-gx9gd" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-3xscd' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-3xscd" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-rtsvw/network-diag-test-pod-bjx2x' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-bjx2x" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-n3r6d' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-n3r6d" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created, Creating network diagnostic test pod 'network-diag-ns-4tw6p/network-diag-test-pod-m6jhc' on node "mxt-ocslave12.newyse.maxxton" failed: pods "network-diag-test-pod-m6jhc" is forbidden: service account network-diag-ns-4tw6p/default was not found, retry after the service account is created]
ERROR: [DNet2006 from diagnostic NetworkCheck@openshift/origin/pkg/diagnostics/network/run_pod.go:136]
Creating network diagnostic pod "network-diag-pod-45dx8" on node "mxt-ocinfra01.newyse.maxxton" with command "openshift infra network-diagnostic-pod -l 1" failed: pods "network-diag-pod-45dx8" is forbidden: service account network-diag-ns-rtsvw/default was not found, retry after the service account is created
[Note] Skipping diagnostic: AggregatedLogging
Description: Check aggregated logging integration for proper configuration
Because: No LoggingPublicURL is defined in the master configuration
[Note] Running diagnostic: ClusterRegistry
Description: Check that there is a working Docker registry
[Note] Running diagnostic: ClusterRoleBindings
Description: Check that the default ClusterRoleBindings are present and contain the expected subjects
Info: clusterrolebinding/cluster-admins has more subjects than expected.
Use the `oadm policy reconcile-cluster-role-bindings` command to update the role binding to remove extra subjects.
Info: clusterrolebinding/cluster-admins has extra subject {User vxadm-mol }.
Info: clusterrolebinding/cluster-admins has extra subject {Group ug-vx-admin }.
Info: clusterrolebinding/cluster-admins has extra subject {Group ug-mx-openshift }.
Info: clusterrolebinding/cluster-readers has more subjects than expected.
Use the `oadm policy reconcile-cluster-role-bindings` command to update the role binding to remove extra subjects.
Info: clusterrolebinding/cluster-readers has extra subject {ServiceAccount management-infra management-admin }.
Info: clusterrolebinding/cluster-readers has extra subject {ServiceAccount default router }.
Info: clusterrolebinding/cluster-readers has extra subject {ServiceAccount openshift-infra heapster }.
Info: clusterrolebinding/self-provisioners has more subjects than expected.
Use the `oadm policy reconcile-cluster-role-bindings` command to update the role binding to remove extra subjects.
Info: clusterrolebinding/self-provisioners has extra subject {ServiceAccount management-infra management-admin }.
[Note] Running diagnostic: ClusterRoles
Description: Check that the default ClusterRoles are present and contain the expected permissions
[Note] Running diagnostic: ClusterRouterName
Description: Check there is a working router
[Note] Running diagnostic: MasterNode
Description: Check if master is also running node (for Open vSwitch)
Info: Found a node with same IP as master: mxt-ocrouter01.newyse.maxxton
[Note] Running diagnostic: MetricsApiProxy
Description: Check the integrated heapster metrics can be reached via the API proxy
[Note] Running diagnostic: NodeDefinitions
Description: Check node records on master
WARN: [DClu0003 from diagnostic NodeDefinition@openshift/origin/pkg/diagnostics/cluster/node_definitions.go:112]
Node mxt-ocmaster01.newyse.maxxton is ready but is marked Unschedulable.
This is usually set manually for administrative reasons.
An administrator can mark the node schedulable with:
oadm manage-node mxt-ocmaster01.newyse.maxxton --schedulable=true
While in this state, pods should not be scheduled to deploy on the node.
Existing pods will continue to run until completed or evacuated (see
other options for 'oadm manage-node').
WARN: [DClu0003 from diagnostic NodeDefinition@openshift/origin/pkg/diagnostics/cluster/node_definitions.go:112]
Node mxt-ocmaster02.newyse.maxxton is ready but is marked Unschedulable.
This is usually set manually for administrative reasons.
An administrator can mark the node schedulable with:
oadm manage-node mxt-ocmaster02.newyse.maxxton --schedulable=true
While in this state, pods should not be scheduled to deploy on the node.
Existing pods will continue to run until completed or evacuated (see
other options for 'oadm manage-node').
WARN: [DClu0003 from diagnostic NodeDefinition@openshift/origin/pkg/diagnostics/cluster/node_definitions.go:112]
Node mxt-ocmaster03.newyse.maxxton is ready but is marked Unschedulable.
This is usually set manually for administrative reasons.
An administrator can mark the node schedulable with:
oadm manage-node mxt-ocmaster03.newyse.maxxton --schedulable=true
While in this state, pods should not be scheduled to deploy on the node.
Existing pods will continue to run until completed or evacuated (see
other options for 'oadm manage-node').
[Note] Running diagnostic: ServiceExternalIPs
Description: Check for existing services with ExternalIPs that are disallowed by master config
[Note] Running diagnostic: AnalyzeLogs
Description: Check for recent problems in systemd service logs
Info: Checking journalctl logs for 'origin-node' service
Info: Checking journalctl logs for 'docker' service
[Note] Running diagnostic: MasterConfigCheck
Description: Check the master config file
WARN: [DH0005 from diagnostic MasterConfigCheck@openshift/origin/pkg/diagnostics/host/check_master_config.go:52]
Validation of master config file '/etc/origin/master/master-config.yaml' warned:
assetConfig.loggingPublicURL: Invalid value: "": required to view aggregated container logs in the console
oauthConfig.identityProvider[0].provider.insecure: Invalid value: true: validating passwords over an insecure connection could allow them to be intercepted
auditConfig.auditFilePath: Required value: audit can now be logged to a separate file
[Note] Running diagnostic: NodeConfigCheck
Description: Check the node config file
Info: Found a node config file: /etc/origin/node/node-config.yaml
[Note] Running diagnostic: UnitStatus
Description: Check status for related systemd units
[Note] Summary of diagnostics execution (version v1.5.0):
[Note] Warnings seen: 4
[Note] Errors seen: 2
``` | non_infrastructure | unable to schedule new pods suddenly openshift is not able to schedule new pods when a pod is deleted or when a new deployment starts any idea what is causing this could this be handled with priority as we cannot restart any pods in our production cluster right now thanks in advanced version oc kubernetes features basic auth gssapi kerberos spnego server openshift kubernetes steps to reproduce delete a pod from a replica controller current result replica controller is showing scaling to but the new pod is never creating expected result the replica controller is starting the new pod additional information determining if client configuration exists for client cluster diagnostics info successfully read a client config file at root kube config info using context for cluster admin access mxts prod mxt ocmaster newyse maxxton system admin performing systemd discovery running diagnostic configcontexts description validate client config context is complete and has connectivity info for client config context openshift mxt ocmaster newyse maxxton system admin the server url is the user authentication is system admin mxt ocmaster newyse maxxton the current project is openshift successfully requested project list has access to project s running diagnostic diagnosticpod description create a pod to run diagnostics from the application standpoint info output from the diagnostic pod image openshift origin deployer running diagnostic podcheckauth description check that service account credentials authenticate as expected info service account token successfully authenticated to master info service account token was authenticated by the integrated registry running diagnostic podcheckdns description check that dns within a pod works as expected summary of diagnostics execution version completed with no errors or warnings seen running diagnostic networkcheck description create a pod on all schedulable nodes and run network diagnostics from the application standpoint error failed to create network diags test pod and service error creating network diagnostic pod network diag pod on node mxt newyse maxxton with command openshift infra network diagnostic pod l failed pods network diag pod is forbidden service account network diag ns rtsvw default was not found retry after the service account is created skipping diagnostic aggregatedlogging description check aggregated logging integration for proper configuration because no loggingpublicurl is defined in the master configuration running diagnostic clusterregistry description check that there is a working docker registry running diagnostic clusterrolebindings description check that the default clusterrolebindings are present and contain the expected subjects info clusterrolebinding cluster admins has more subjects than expected use the oadm policy reconcile cluster role bindings command to update the role binding to remove extra subjects info clusterrolebinding cluster admins has extra subject user vxadm mol info clusterrolebinding cluster admins has extra subject group ug vx admin info clusterrolebinding cluster admins has extra subject group ug mx openshift info clusterrolebinding cluster readers has more subjects than expected use the oadm policy reconcile cluster role bindings command to update the role binding to remove extra subjects info clusterrolebinding cluster readers has extra subject serviceaccount management infra management admin info clusterrolebinding cluster readers has extra subject serviceaccount default router info clusterrolebinding cluster readers has extra subject serviceaccount openshift infra heapster info clusterrolebinding self provisioners has more subjects than expected use the oadm policy reconcile cluster role bindings command to update the role binding to remove extra subjects info clusterrolebinding self provisioners has extra subject serviceaccount management infra management admin running diagnostic clusterroles description check that the default clusterroles are present and contain the expected permissions running diagnostic clusterroutername description check there is a working router running diagnostic masternode description check if master is also running node for open vswitch info found a node with same ip as master mxt newyse maxxton running diagnostic metricsapiproxy description check the integrated heapster metrics can be reached via the api proxy running diagnostic nodedefinitions description check node records on master warn node mxt newyse maxxton is ready but is marked unschedulable this is usually set manually for administrative reasons an administrator can mark the node schedulable with oadm manage node mxt newyse maxxton schedulable true while in this state pods should not be scheduled to deploy on the node existing pods will continue to run until completed or evacuated see other options for oadm manage node warn node mxt newyse maxxton is ready but is marked unschedulable this is usually set manually for administrative reasons an administrator can mark the node schedulable with oadm manage node mxt newyse maxxton schedulable true while in this state pods should not be scheduled to deploy on the node existing pods will continue to run until completed or evacuated see other options for oadm manage node warn node mxt newyse maxxton is ready but is marked unschedulable this is usually set manually for administrative reasons an administrator can mark the node schedulable with oadm manage node mxt newyse maxxton schedulable true while in this state pods should not be scheduled to deploy on the node existing pods will continue to run until completed or evacuated see other options for oadm manage node running diagnostic serviceexternalips description check for existing services with externalips that are disallowed by master config running diagnostic analyzelogs description check for recent problems in systemd service logs info checking journalctl logs for origin node service info checking journalctl logs for docker service running diagnostic masterconfigcheck description check the master config file warn validation of master config file etc origin master master config yaml warned assetconfig loggingpublicurl invalid value required to view aggregated container logs in the console oauthconfig identityprovider provider insecure invalid value true validating passwords over an insecure connection could allow them to be intercepted auditconfig auditfilepath required value audit can now be logged to a separate file running diagnostic nodeconfigcheck description check the node config file info found a node config file etc origin node node config yaml running diagnostic unitstatus description check status for related systemd units summary of diagnostics execution version warnings seen errors seen | 0 |
16,233 | 11,879,669,700 | IssuesEvent | 2020-03-27 09:14:31 | esrlabs/chipmunk | https://api.github.com/repos/esrlabs/chipmunk | closed | build basic plugin manager | infrastructure usability | needs to have
* list installed plugins
* list available plugins
* available plugins should be installable
* installed plugins should be uninstallable
| 1.0 | build basic plugin manager - needs to have
* list installed plugins
* list available plugins
* available plugins should be installable
* installed plugins should be uninstallable
| infrastructure | build basic plugin manager needs to have list installed plugins list available plugins available plugins should be installable installed plugins should be uninstallable | 1 |
118,809 | 15,366,665,011 | IssuesEvent | 2021-03-02 01:37:47 | chips-blockchain/pangea-poker | https://api.github.com/repos/chips-blockchain/pangea-poker | opened | Adding support to the player disconnections on GUI | design frontend | Now the backend is periodically sending the players active status info to the GUI, the example json structure format which uses to send this info to the GUI is as below
```
{
method: "active_player_info",
player_status: [1, 1]
}
```
Here player_status array index represents the playerid, and the value 0 means the player got disconnected and 1 means the player is in connection state. So GUI has to process this info and display it to the players.
| 1.0 | Adding support to the player disconnections on GUI - Now the backend is periodically sending the players active status info to the GUI, the example json structure format which uses to send this info to the GUI is as below
```
{
method: "active_player_info",
player_status: [1, 1]
}
```
Here player_status array index represents the playerid, and the value 0 means the player got disconnected and 1 means the player is in connection state. So GUI has to process this info and display it to the players.
| non_infrastructure | adding support to the player disconnections on gui now the backend is periodically sending the players active status info to the gui the example json structure format which uses to send this info to the gui is as below method active player info player status here player status array index represents the playerid and the value means the player got disconnected and means the player is in connection state so gui has to process this info and display it to the players | 0 |
119,225 | 17,604,736,618 | IssuesEvent | 2021-08-17 15:40:33 | Dima2021/NodeGoat | https://api.github.com/repos/Dima2021/NodeGoat | closed | WS-2020-0342 (Medium) detected in is-my-json-valid-2.15.0.tgz, is-my-json-valid-2.19.0.tgz - autoclosed | security vulnerability | ## WS-2020-0342 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>is-my-json-valid-2.15.0.tgz</b>, <b>is-my-json-valid-2.19.0.tgz</b></p></summary>
<p>
<details><summary><b>is-my-json-valid-2.15.0.tgz</b></p></summary>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.15.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>is-my-json-valid-2.19.0.tgz</b></p></summary>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.19.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.19.0.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-retire-0.3.12.tgz (Root Library)
- request-2.67.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.19.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/NodeGoat/commit/3b25a27fed9a418e332bfca71ab656c04a404f1e">3b25a27fed9a418e332bfca71ab656c04a404f1e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) vulnerability was found in is-my-json-valid before 2.20.2 via the style format.
<p>Publish Date: 2020-06-27
<p>URL: <a href=https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb>WS-2020-0342</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb">https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb</a></p>
<p>Release Date: 2020-06-27</p>
<p>Fix Resolution: is-my-json-valid - 2.20.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.2"},{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.19.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-retire:0.3.12;request:2.67.0;har-validator:2.0.6;is-my-json-valid:2.19.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0342","vulnerabilityDetails":"Regular Expression Denial of Service (ReDoS) vulnerability was found in is-my-json-valid before 2.20.2 via the style format.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | WS-2020-0342 (Medium) detected in is-my-json-valid-2.15.0.tgz, is-my-json-valid-2.19.0.tgz - autoclosed - ## WS-2020-0342 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>is-my-json-valid-2.15.0.tgz</b>, <b>is-my-json-valid-2.19.0.tgz</b></p></summary>
<p>
<details><summary><b>is-my-json-valid-2.15.0.tgz</b></p></summary>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.15.0.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/npm/node_modules/request/node_modules/har-validator/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- request-2.75.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.15.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>is-my-json-valid-2.19.0.tgz</b></p></summary>
<p>A JSONSchema validator that uses code generation to be extremely fast</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.19.0.tgz">https://registry.npmjs.org/is-my-json-valid/-/is-my-json-valid-2.19.0.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/is-my-json-valid/package.json</p>
<p>
Dependency Hierarchy:
- grunt-retire-0.3.12.tgz (Root Library)
- request-2.67.0.tgz
- har-validator-2.0.6.tgz
- :x: **is-my-json-valid-2.19.0.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/NodeGoat/commit/3b25a27fed9a418e332bfca71ab656c04a404f1e">3b25a27fed9a418e332bfca71ab656c04a404f1e</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) vulnerability was found in is-my-json-valid before 2.20.2 via the style format.
<p>Publish Date: 2020-06-27
<p>URL: <a href=https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb>WS-2020-0342</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb">https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb</a></p>
<p>Release Date: 2020-06-27</p>
<p>Fix Resolution: is-my-json-valid - 2.20.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.15.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-npm-install:0.3.1;npm:3.10.10;request:2.75.0;har-validator:2.0.6;is-my-json-valid:2.15.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.2"},{"packageType":"javascript/Node.js","packageName":"is-my-json-valid","packageVersion":"2.19.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-retire:0.3.12;request:2.67.0;har-validator:2.0.6;is-my-json-valid:2.19.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"is-my-json-valid - 2.20.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2020-0342","vulnerabilityDetails":"Regular Expression Denial of Service (ReDoS) vulnerability was found in is-my-json-valid before 2.20.2 via the style format.","vulnerabilityUrl":"https://github.com/mafintosh/is-my-json-valid/commit/c3fc04fc455d40e9b29537f8e2c73a28ce106edb","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"Low","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_infrastructure | ws medium detected in is my json valid tgz is my json valid tgz autoclosed ws medium severity vulnerability vulnerable libraries is my json valid tgz is my json valid tgz is my json valid tgz a jsonschema validator that uses code generation to be extremely fast library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules npm node modules request node modules har validator node modules is my json valid package json dependency hierarchy grunt npm install tgz root library npm tgz request tgz har validator tgz x is my json valid tgz vulnerable library is my json valid tgz a jsonschema validator that uses code generation to be extremely fast library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules is my json valid package json dependency hierarchy grunt retire tgz root library request tgz har validator tgz x is my json valid tgz vulnerable library found in head commit a href found in base branch master vulnerability details regular expression denial of service redos vulnerability was found in is my json valid before via the style format publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution is my json valid isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree grunt npm install npm request har validator is my json valid isminimumfixversionavailable true minimumfixversion is my json valid packagetype javascript node js packagename is my json valid packageversion packagefilepaths istransitivedependency true dependencytree grunt retire request har validator is my json valid isminimumfixversionavailable true minimumfixversion is my json valid basebranches vulnerabilityidentifier ws vulnerabilitydetails regular expression denial of service redos vulnerability was found in is my json valid before via the style format vulnerabilityurl | 0 |
86,755 | 24,942,241,575 | IssuesEvent | 2022-10-31 20:00:32 | aws/aws-sam-cli | https://api.github.com/repos/aws/aws-sam-cli | closed | Feature request: esbuild / metadata support in Globals | type/feature area/build stage/pm-review area/esbuild | ### Describe your idea/feature/enhancement
A nice next step for esbuild would be allowing us to set up this metadata block only once, for example via the Globals section. This would allow us to set up esbuild only once, and share its configuration across all functions. Within a single stack, most likely all code would benefit from the same build pipeline.
Currently this fails:
```
[InvalidGlobalsSectionException('Globals', "'Metadata' is not a supported property of 'Function'. Must be one of the following values - ['Handler', 'Runtime', 'CodeUri', 'DeadLetterQueue', 'Description', 'MemorySize', 'Timeout', 'VpcConfig', 'Environment', 'Tags', 'Tracing', 'KmsKeyArn', 'AutoPublishAlias', 'Layers', 'DeploymentPreference', 'PermissionsBoundary', 'ReservedConcurrentExecutions', 'ProvisionedConcurrencyConfig', 'AssumeRolePolicyDocument', 'EventInvokeConfig', 'FileSystemConfigs', 'CodeSigningConfigArn', 'Architectures', 'EphemeralStorage', 'FunctionUrlConfig']")]
```
### Proposal
Add `Metadata` to the list of properties that `Globals::Function` supports and copy/merge it into the definition of `AWS::Serverless::Function` resources.
Things to consider:
1. This will require a change to the SAM Specification, as it will expand the list of fields that can be provided via the Globals section for an AWS::Serverless::Function.
### Additional Details
N/A | 2.0 | Feature request: esbuild / metadata support in Globals - ### Describe your idea/feature/enhancement
A nice next step for esbuild would be allowing us to set up this metadata block only once, for example via the Globals section. This would allow us to set up esbuild only once, and share its configuration across all functions. Within a single stack, most likely all code would benefit from the same build pipeline.
Currently this fails:
```
[InvalidGlobalsSectionException('Globals', "'Metadata' is not a supported property of 'Function'. Must be one of the following values - ['Handler', 'Runtime', 'CodeUri', 'DeadLetterQueue', 'Description', 'MemorySize', 'Timeout', 'VpcConfig', 'Environment', 'Tags', 'Tracing', 'KmsKeyArn', 'AutoPublishAlias', 'Layers', 'DeploymentPreference', 'PermissionsBoundary', 'ReservedConcurrentExecutions', 'ProvisionedConcurrencyConfig', 'AssumeRolePolicyDocument', 'EventInvokeConfig', 'FileSystemConfigs', 'CodeSigningConfigArn', 'Architectures', 'EphemeralStorage', 'FunctionUrlConfig']")]
```
### Proposal
Add `Metadata` to the list of properties that `Globals::Function` supports and copy/merge it into the definition of `AWS::Serverless::Function` resources.
Things to consider:
1. This will require a change to the SAM Specification, as it will expand the list of fields that can be provided via the Globals section for an AWS::Serverless::Function.
### Additional Details
N/A | non_infrastructure | feature request esbuild metadata support in globals describe your idea feature enhancement a nice next step for esbuild would be allowing us to set up this metadata block only once for example via the globals section this would allow us to set up esbuild only once and share its configuration across all functions within a single stack most likely all code would benefit from the same build pipeline currently this fails proposal add metadata to the list of properties that globals function supports and copy merge it into the definition of aws serverless function resources things to consider this will require a change to the sam specification as it will expand the list of fields that can be provided via the globals section for an aws serverless function additional details n a | 0 |
55,734 | 13,669,266,590 | IssuesEvent | 2020-09-29 01:25:39 | scikit-hep/pyhf | https://api.github.com/repos/scikit-hep/pyhf | closed | Migrate from bumpversion to bump2version | build chore deployment | # Description
@dguest has brought to my attention that [`bumpversion` is no longer maintained](https://github.com/peritus/bumpversion) (as of apparently November 2019). Given this we should probably take the project's advice
> 🎬 If you want to start using `bumpversion`, you're best advised to install one of the maintained forks, e.g. ➡ @ c4urself's [`bump2version`](https://github.com/c4urself/bump2version/#installation).
given that it seems that [transferring ownership and maintainers is taking a very long time/might not happen](https://github.com/c4urself/bump2version/issues/86). | 1.0 | Migrate from bumpversion to bump2version - # Description
@dguest has brought to my attention that [`bumpversion` is no longer maintained](https://github.com/peritus/bumpversion) (as of apparently November 2019). Given this we should probably take the project's advice
> 🎬 If you want to start using `bumpversion`, you're best advised to install one of the maintained forks, e.g. ➡ @ c4urself's [`bump2version`](https://github.com/c4urself/bump2version/#installation).
given that it seems that [transferring ownership and maintainers is taking a very long time/might not happen](https://github.com/c4urself/bump2version/issues/86). | non_infrastructure | migrate from bumpversion to description dguest has brought to my attention that as of apparently november given this we should probably take the project s advice 🎬 if you want to start using bumpversion you re best advised to install one of the maintained forks e g ➡ s given that it seems that | 0 |
43,962 | 11,352,252,488 | IssuesEvent | 2020-01-24 13:14:22 | EightShapes/esds-build | https://api.github.com/repos/EightShapes/esds-build | closed | Integrate build messages with platform specific notifications | [Build] | ## Acceptance Criteria
* As a build tool user I want to see a "build failed/succeeded" message as a Mac OS or Windows notification so I don't have to check my terminal for any build issues. | 1.0 | Integrate build messages with platform specific notifications - ## Acceptance Criteria
* As a build tool user I want to see a "build failed/succeeded" message as a Mac OS or Windows notification so I don't have to check my terminal for any build issues. | non_infrastructure | integrate build messages with platform specific notifications acceptance criteria as a build tool user i want to see a build failed succeeded message as a mac os or windows notification so i don t have to check my terminal for any build issues | 0 |
24,542 | 17,379,316,231 | IssuesEvent | 2021-07-31 11:02:21 | asciidoctor/asciidoctor | https://api.github.com/repos/asciidoctor/asciidoctor | closed | Enable RuboCop to enforce a consistent code style and perform static analysis | infrastructure | I think it could be a good idea to enforce some guidelines (especially for newcomers and developers with limited knowledge of Ruby).
What do you think ? | 1.0 | Enable RuboCop to enforce a consistent code style and perform static analysis - I think it could be a good idea to enforce some guidelines (especially for newcomers and developers with limited knowledge of Ruby).
What do you think ? | infrastructure | enable rubocop to enforce a consistent code style and perform static analysis i think it could be a good idea to enforce some guidelines especially for newcomers and developers with limited knowledge of ruby what do you think | 1 |
6,277 | 6,289,409,686 | IssuesEvent | 2017-07-19 19:08:32 | LLNL/maestrowf | https://api.github.com/repos/LLNL/maestrowf | opened | Formalize a PyPi Release Process | Infrastructure Release Process | We need to formalize a release process to PyPi that will automatically compile all supported versions for both sdist and bdist. | 1.0 | Formalize a PyPi Release Process - We need to formalize a release process to PyPi that will automatically compile all supported versions for both sdist and bdist. | infrastructure | formalize a pypi release process we need to formalize a release process to pypi that will automatically compile all supported versions for both sdist and bdist | 1 |
152,311 | 19,680,557,398 | IssuesEvent | 2022-01-11 16:22:42 | jtimberlake/react-server | https://api.github.com/repos/jtimberlake/react-server | closed | WS-2018-0084 (High) detected in sshpk-1.11.0.tgz - autoclosed | security vulnerability | ## WS-2018-0084 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sshpk-1.11.0.tgz</b></p></summary>
<p>A library for finding and using SSH public keys</p>
<p>Library home page: <a href="https://registry.npmjs.org/sshpk/-/sshpk-1.11.0.tgz">https://registry.npmjs.org/sshpk/-/sshpk-1.11.0.tgz</a></p>
<p>Path to dependency file: react-server/package.json</p>
<p>Path to vulnerable library: react-server/node_modules/david/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/package.json</p>
<p>
Dependency Hierarchy:
- david-11.0.0.tgz (Root Library)
- npm-4.6.1.tgz
- request-2.81.0.tgz
- http-signature-1.1.1.tgz
- :x: **sshpk-1.11.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/react-server/commit/fc4f63cd9d7cfd34b5d6322a49f9b670bd83cb27">fc4f63cd9d7cfd34b5d6322a49f9b670bd83cb27</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions of sshpk before 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.
<p>Publish Date: 2018-04-25
<p>URL: <a href=https://github.com/joyent/node-sshpk/blob/v1.13.1/lib/formats/ssh.js#L17>WS-2018-0084</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/606">https://nodesecurity.io/advisories/606</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 1.14.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"sshpk","packageVersion":"1.11.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"david:11.0.0;npm:4.6.1;request:2.81.0;http-signature:1.1.1;sshpk:1.11.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.14.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0084","vulnerabilityDetails":"Versions of sshpk before 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.\n\n","vulnerabilityUrl":"https://github.com/joyent/node-sshpk/blob/v1.13.1/lib/formats/ssh.js#L17","cvss2Severity":"high","cvss2Score":"8.0","extraData":{}}</REMEDIATE> --> | True | WS-2018-0084 (High) detected in sshpk-1.11.0.tgz - autoclosed - ## WS-2018-0084 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sshpk-1.11.0.tgz</b></p></summary>
<p>A library for finding and using SSH public keys</p>
<p>Library home page: <a href="https://registry.npmjs.org/sshpk/-/sshpk-1.11.0.tgz">https://registry.npmjs.org/sshpk/-/sshpk-1.11.0.tgz</a></p>
<p>Path to dependency file: react-server/package.json</p>
<p>Path to vulnerable library: react-server/node_modules/david/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/sshpk/package.json</p>
<p>
Dependency Hierarchy:
- david-11.0.0.tgz (Root Library)
- npm-4.6.1.tgz
- request-2.81.0.tgz
- http-signature-1.1.1.tgz
- :x: **sshpk-1.11.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/react-server/commit/fc4f63cd9d7cfd34b5d6322a49f9b670bd83cb27">fc4f63cd9d7cfd34b5d6322a49f9b670bd83cb27</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions of sshpk before 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.
<p>Publish Date: 2018-04-25
<p>URL: <a href=https://github.com/joyent/node-sshpk/blob/v1.13.1/lib/formats/ssh.js#L17>WS-2018-0084</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/606">https://nodesecurity.io/advisories/606</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 1.14.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"sshpk","packageVersion":"1.11.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"david:11.0.0;npm:4.6.1;request:2.81.0;http-signature:1.1.1;sshpk:1.11.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"1.14.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0084","vulnerabilityDetails":"Versions of sshpk before 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys.\n\n","vulnerabilityUrl":"https://github.com/joyent/node-sshpk/blob/v1.13.1/lib/formats/ssh.js#L17","cvss2Severity":"high","cvss2Score":"8.0","extraData":{}}</REMEDIATE> --> | non_infrastructure | ws high detected in sshpk tgz autoclosed ws high severity vulnerability vulnerable library sshpk tgz a library for finding and using ssh public keys library home page a href path to dependency file react server package json path to vulnerable library react server node modules david node modules npm node modules request node modules http signature node modules sshpk package json dependency hierarchy david tgz root library npm tgz request tgz http signature tgz x sshpk tgz vulnerable library found in head commit a href found in base branch master vulnerability details versions of sshpk before are vulnerable to regular expression denial of service when parsing crafted invalid public keys publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree david npm request http signature sshpk isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier ws vulnerabilitydetails versions of sshpk before are vulnerable to regular expression denial of service when parsing crafted invalid public keys n n vulnerabilityurl | 0 |
32,906 | 27,086,009,561 | IssuesEvent | 2023-02-14 17:02:26 | GCTC-NTGC/gc-digital-talent | https://api.github.com/repos/GCTC-NTGC/gc-digital-talent | closed | Investigate how to procure and set up a subdomain | infrastructure spike interruption | ## :question: Spike Question
- What's involved in getting a subdomain to work (eg report.talent.canada.ca)? Both on the technical and administrative sides.
Timebox: 1 Jira ticket | 1.0 | Investigate how to procure and set up a subdomain - ## :question: Spike Question
- What's involved in getting a subdomain to work (eg report.talent.canada.ca)? Both on the technical and administrative sides.
Timebox: 1 Jira ticket | infrastructure | investigate how to procure and set up a subdomain question spike question what s involved in getting a subdomain to work eg report talent canada ca both on the technical and administrative sides timebox jira ticket | 1 |
112,451 | 17,089,624,340 | IssuesEvent | 2021-07-08 15:45:03 | turkdevops/atom | https://api.github.com/repos/turkdevops/atom | closed | CVE-2012-6708 (Medium) detected in jquery-1.7.2.min.js, jquery-1.7.1.min.js - autoclosed | security vulnerability | ## CVE-2012-6708 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.2.min.js</b>, <b>jquery-1.7.1.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.2.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: atom/script/vsts/node_modules/jmespath/index.html</p>
<p>Path to vulnerable library: atom/script/vsts/node_modules/jmespath/index.html,atom/node_modules/notifications/node_modules/marked/www/demo.html,atom/node_modules/settings-view/node_modules/marked/www/demo.html,atom/packages/deprecation-cop/node_modules/marked/www/demo.html,atom/node_modules/roaster/node_modules/marked/www/demo.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: /repo-with-submodules/You-Dont-Need-jQuery/node_modules/vm-browserify/example/run/index.html</p>
<p>Path to vulnerable library: atom/spec/fixtures/git/repo-with-submodules/You-Dont-Need-jQuery/node_modules/vm-browserify/example/run/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/atom/commit/0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f">0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f</a></p>
<p>Found in base branch: <b>electron-upgrade</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6708>CVE-2012-6708</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6708">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v1.9.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2012-6708 (Medium) detected in jquery-1.7.2.min.js, jquery-1.7.1.min.js - autoclosed - ## CVE-2012-6708 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.2.min.js</b>, <b>jquery-1.7.1.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.2.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: atom/script/vsts/node_modules/jmespath/index.html</p>
<p>Path to vulnerable library: atom/script/vsts/node_modules/jmespath/index.html,atom/node_modules/notifications/node_modules/marked/www/demo.html,atom/node_modules/settings-view/node_modules/marked/www/demo.html,atom/packages/deprecation-cop/node_modules/marked/www/demo.html,atom/node_modules/roaster/node_modules/marked/www/demo.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: /repo-with-submodules/You-Dont-Need-jQuery/node_modules/vm-browserify/example/run/index.html</p>
<p>Path to vulnerable library: atom/spec/fixtures/git/repo-with-submodules/You-Dont-Need-jQuery/node_modules/vm-browserify/example/run/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/atom/commit/0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f">0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f</a></p>
<p>Found in base branch: <b>electron-upgrade</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
<p>Publish Date: 2018-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6708>CVE-2012-6708</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6708">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p>
<p>Release Date: 2018-01-18</p>
<p>Fix Resolution: jQuery - v1.9.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in jquery min js jquery min js autoclosed cve medium severity vulnerability vulnerable libraries jquery min js jquery min js jquery min js javascript library for dom operations library home page a href path to dependency file atom script vsts node modules jmespath index html path to vulnerable library atom script vsts node modules jmespath index html atom node modules notifications node modules marked www demo html atom node modules settings view node modules marked www demo html atom packages deprecation cop node modules marked www demo html atom node modules roaster node modules marked www demo html dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file repo with submodules you dont need jquery node modules vm browserify example run index html path to vulnerable library atom spec fixtures git repo with submodules you dont need jquery node modules vm browserify example run index html dependency hierarchy x jquery min js vulnerable library found in head commit a href found in base branch electron upgrade vulnerability details jquery before is vulnerable to cross site scripting xss attacks the jquery strinput function does not differentiate selectors from html in a reliable fashion in vulnerable versions jquery determined whether the input was html by looking for the character anywhere in the string giving attackers more flexibility when attempting to construct a malicious payload in fixed versions jquery only deems the input to be html if it explicitly starts with the character limiting exploitability only to attackers who can control the beginning of a string which is far less common publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery step up your open source security game with whitesource | 0 |
426,979 | 12,391,193,239 | IssuesEvent | 2020-05-20 12:04:18 | StrangeLoopGames/EcoIssues | https://api.github.com/repos/StrangeLoopGames/EcoIssues | closed | [0.9.0 staging-1520] Animal: Coyote has a dumb head | Fix Version: 0.9.0.0 Priority: Medium Status: Fixed Week Task | 1.Without hunting.
2. With wooden bow.
3. Shoot a coyote's head.
4. You will deal 1.0 dmg.
Should be 2.0 dmg. | 1.0 | [0.9.0 staging-1520] Animal: Coyote has a dumb head - 1.Without hunting.
2. With wooden bow.
3. Shoot a coyote's head.
4. You will deal 1.0 dmg.
Should be 2.0 dmg. | non_infrastructure | animal coyote has a dumb head without hunting with wooden bow shoot a coyote s head you will deal dmg should be dmg | 0 |
21,336 | 16,848,290,412 | IssuesEvent | 2021-06-20 00:39:02 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Can't Change Label's Default Text Size | enhancement topic:gui usability |
**Godot version:**
3.06stable
**OS/device including version:**
windows 10 64/bit latest version
**Issue description:**
Can't change the label's default font text size without having to add a dynamicfont. Can only change the dynamic font's text size.
| True | Can't Change Label's Default Text Size -
**Godot version:**
3.06stable
**OS/device including version:**
windows 10 64/bit latest version
**Issue description:**
Can't change the label's default font text size without having to add a dynamicfont. Can only change the dynamic font's text size.
| non_infrastructure | can t change label s default text size godot version os device including version windows bit latest version issue description can t change the label s default font text size without having to add a dynamicfont can only change the dynamic font s text size | 0 |
23,368 | 16,092,883,047 | IssuesEvent | 2021-04-26 19:03:32 | uwblueprint/shoe-project | https://api.github.com/repos/uwblueprint/shoe-project | closed | Set up HTTPs for Heroku Deployment | infrastructure | - Will cost $7 to get SSL, confirm with the shoe project staff | 1.0 | Set up HTTPs for Heroku Deployment - - Will cost $7 to get SSL, confirm with the shoe project staff | infrastructure | set up https for heroku deployment will cost to get ssl confirm with the shoe project staff | 1 |
122,846 | 16,360,272,374 | IssuesEvent | 2021-05-14 08:23:13 | AzureAD/microsoft-identity-web | https://api.github.com/repos/AzureAD/microsoft-identity-web | closed | [Bug] MicrosoftGraphExtensions: GraphServiceClient is added to the DI container as the TImplementation, TImplementation, not TService, TImplementation | by design enhancement | **Which version of Microsoft Identity Web are you using?**
Microsoft.Identity.Web 1.9.2
Microsoft.Identity.Web.MicrosoftGraph 1.9.2
**Where is the issue?**
* Other (please describe)
The GraphServiceClient is added to the DI as `<GraphServiceClient,GraphServiceClient>` as seen in https://github.com/AzureAD/microsoft-identity-web/blob/master/src/Microsoft.Identity.Web.MicrosoftGraph/MicrosoftGraphExtensions.cs
In our classes implementation, we can't use `IGraphServiceClient` in our constructor directly, but rather making us having to use the factory to create our classes such as:
```csharp
services.AddScoped<IClass, Class>(sp =>
{
var client = sp.GetRequiredService<GraphServiceClient>();
return new Class(client);
});
```
Using a hard dependency on `GraphServiceClient` renders our class hard to test.
**Is this a new or an existing app?**
This is a new app
**Expected behavior**
Having our class definition such as
```csharp
public Class(IGraphServiceClient graphServiceClient)
{
...
}
```
and registered in the DI as:
```csharp
services.AddScoped<IClass, Class>();
```
should work as is.
**Actual behavior**
The DI container throws an exception saying that `IGraphServiceClient` is not registered.
**Possible solution**
Replace the DI registration in the extension file to `services.AddScope<IGraphServiceClient, GraphServiceClient>(...)` instead of `services.AddScope<GraphServiceClient, GraphServiceClient>(...)` | 1.0 | [Bug] MicrosoftGraphExtensions: GraphServiceClient is added to the DI container as the TImplementation, TImplementation, not TService, TImplementation - **Which version of Microsoft Identity Web are you using?**
Microsoft.Identity.Web 1.9.2
Microsoft.Identity.Web.MicrosoftGraph 1.9.2
**Where is the issue?**
* Other (please describe)
The GraphServiceClient is added to the DI as `<GraphServiceClient,GraphServiceClient>` as seen in https://github.com/AzureAD/microsoft-identity-web/blob/master/src/Microsoft.Identity.Web.MicrosoftGraph/MicrosoftGraphExtensions.cs
In our classes implementation, we can't use `IGraphServiceClient` in our constructor directly, but rather making us having to use the factory to create our classes such as:
```csharp
services.AddScoped<IClass, Class>(sp =>
{
var client = sp.GetRequiredService<GraphServiceClient>();
return new Class(client);
});
```
Using a hard dependency on `GraphServiceClient` renders our class hard to test.
**Is this a new or an existing app?**
This is a new app
**Expected behavior**
Having our class definition such as
```csharp
public Class(IGraphServiceClient graphServiceClient)
{
...
}
```
and registered in the DI as:
```csharp
services.AddScoped<IClass, Class>();
```
should work as is.
**Actual behavior**
The DI container throws an exception saying that `IGraphServiceClient` is not registered.
**Possible solution**
Replace the DI registration in the extension file to `services.AddScope<IGraphServiceClient, GraphServiceClient>(...)` instead of `services.AddScope<GraphServiceClient, GraphServiceClient>(...)` | non_infrastructure | microsoftgraphextensions graphserviceclient is added to the di container as the timplementation timplementation not tservice timplementation which version of microsoft identity web are you using microsoft identity web microsoft identity web microsoftgraph where is the issue other please describe the graphserviceclient is added to the di as as seen in in our classes implementation we can t use igraphserviceclient in our constructor directly but rather making us having to use the factory to create our classes such as csharp services addscoped sp var client sp getrequiredservice return new class client using a hard dependency on graphserviceclient renders our class hard to test is this a new or an existing app this is a new app expected behavior having our class definition such as csharp public class igraphserviceclient graphserviceclient and registered in the di as csharp services addscoped should work as is actual behavior the di container throws an exception saying that igraphserviceclient is not registered possible solution replace the di registration in the extension file to services addscope instead of services addscope | 0 |
595,486 | 18,067,567,959 | IssuesEvent | 2021-09-20 21:05:30 | OpenMandrivaAssociation/test2 | https://api.github.com/repos/OpenMandrivaAssociation/test2 | opened | Enabling all x86_64 repos results in urpmi removing entire operating system. (Bugzilla Bug 111) | bug high priority major | This issue was created automatically with bugzilla2github
# Bugzilla Bug 111
Date: 2013-08-28 08:03:47 +0000
From: @benbullard79
To: OpenMandriva QA <<bugs@openmandriva.org>>
CC: @robxu9, siriustheking@yahoo.com
Last updated: 2013-09-14 22:39:24 +0000
## Comment 636
Date: 2013-08-28 08:03:47 +0000
From: @benbullard79
Created attachment 42
Results of urpmi --auto-select with all x86_64 repos enabled.
> Attached file: om.2013.x86_64.repo.txt (text/plain, 34874 bytes)
> Description: Results of urpmi --auto-select with all x86_64 repos enabled.
## Comment 637
Date: 2013-08-28 08:08:48 +0000
From: @benbullard79
Description is as titled. Also there is something seriously wrong with urmpi or related that this is even possible. urpmi should not offer to remove packages that break system. Am aware that this is probably related to previous bugs. However my results seemed significant enough to report.
## Comment 642
Date: 2013-08-28 13:04:47 +0000
From: @robxu9
(In reply to comment #1)
> Description is as titled. Also there is something seriously wrong with urmpi
> or related that this is even possible. urpmi should not offer to remove
> packages that break system. Am aware that this is probably related to
> previous bugs. However my results seemed significant enough to report.
I think the repository is inconsistent right now for openmandriva2013.0...
## Comment 643
Date: 2013-08-28 13:07:40 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
I'm maybe wrong, but I can note in the attachment that you have something like a mess of versions.
Let me explain. I can see things like:
--- ATTACHMENT 42 ---
Some requested packages cannot be installed:
drakguard-0.7.7-6-omv2013.0.noarch (in order to keep drakguard-0.7.7-6-mdv2013.0.noarch)
drakx-kbd-mouse-x11-0.102-1-omv2013.0.x86_64 (in order to keep drakx-kbd-mouse-x11-0.102-1-mdv2013.0.x86_64)
[...]
--- ATTACHMENT 42 ---
So, it's trying to keep mdv2013.0 versions, avoiding to update to omv2013.0 versions. As omv2013 are the latest (and most important, they're the ACTUAL cooker, so if you want to try Cooker or Beta I suggest you that try to keep all the actual/latest packages), you'll never reach a full update, as the system seems that always try to keep the old mdv2013 versions.
I'm not a developer, but I think that it's not a good thing to keep that mix. If uninstall/reinstall is not viable (there are too many packages), maybe the best solution is reinstall from the ISO, and only add the actual repositories.
I'm testing OMV 64 bits in a box and in a VM, with all repositories enabled (I'm using Cooker repositories), 32 bits and 64 bits, and I don't have the problems you describe. Sometimes there are problem with dependencies (like bug #109), but none is as serious that a reinstallation of the system is the only solution. I had even a serious problem with grub (see bug #97) and thanks to TPG a reinstallation was not needed !
## Comment 644
Date: 2013-08-28 13:10:41 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
My situation:
------
$ urpmq --list-media active
main (ABF64-1)
main updates (ABF64-2)
restricted (ABF64-3)
restricted updates (ABF64-4)
non-free (ABF64-5)
non-free updates (ABF64-6)
contrib (ABF64-7)
contrib updates (ABF64-8)
main (ABF32-1)
main updates (ABF32-2)
restricted (ABF32-3)
restricted updates (ABF32-4)
non-free (ABF32-5)
non-free updates (ABF32-6)
contrib (ABF32-7)
contrib updates (ABF32-8)
# urpmi --auto-select
Los paquetes están actualizados
------
Translation:
Los paquetes están actualizados = All packages are updated.
I'm writing from the VBox VM, so the nVidia problem (bug #109) doesn't appear here.
## Comment 645
Date: 2013-08-28 13:11:20 +0000
From: @robxu9
(In reply to comment #3)
> I'm maybe wrong, but I can note in the attachment that you have something
> like a mess of versions.
>
> Let me explain. I can see things like:
>
> --- ATTACHMENT 42 [details] ---
> Some requested packages cannot be installed:
> drakguard-0.7.7-6-omv2013.0.noarch (in order to keep
> drakguard-0.7.7-6-mdv2013.0.noarch)
> drakx-kbd-mouse-x11-0.102-1-omv2013.0.x86_64 (in order to keep
> drakx-kbd-mouse-x11-0.102-1-mdv2013.0.x86_64)
> [...]
> --- ATTACHMENT 42 [details] ---
>
> So, it's trying to keep mdv2013.0 versions, avoiding to update to omv2013.0
> versions. As omv2013 are the latest (and most important, they're the ACTUAL
> cooker, so if you want to try Cooker or Beta I suggest you that try to keep
> all the actual/latest packages), you'll never reach a full update, as the
> system seems that always try to keep the old mdv2013 versions.
> I'm not a developer, but I think that it's not a good thing to keep that
> mix. If uninstall/reinstall is not viable (there are too many packages),
> maybe the best solution is reinstall from the ISO, and only add the actual
> repositories.
> I'm testing OMV 64 bits in a box and in a VM, with all repositories enabled
> (I'm using Cooker repositories), 32 bits and 64 bits, and I don't have the
> problems you describe. Sometimes there are problem with dependencies (like
> bug #109), but none is as serious that a reinstallation of the system is the
> only solution. I had even a serious problem with grub (see bug #97) and
> thanks to TPG a reinstallation was not needed !
^ ah, you're right there. Good catch!
This also means, though, that we did not bump releases for some new builds on abf :/
## Comment 646
Date: 2013-08-28 13:18:03 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
(In reply to comment #4)
> $ urpmq --list-media active
> main (ABF64-1)
> main updates (ABF64-2)
> restricted (ABF64-3)
> restricted updates (ABF64-4)
> non-free (ABF64-5)
> non-free updates (ABF64-6)
> contrib (ABF64-7)
> contrib updates (ABF64-8)
> main (ABF32-1)
> main updates (ABF32-2)
> restricted (ABF32-3)
> restricted updates (ABF32-4)
> non-free (ABF32-5)
> non-free updates (ABF32-6)
> contrib (ABF32-7)
> contrib updates (ABF32-8)
>
Just in case you need it:
------
$ urpmq --list-media active --list-url
main (ABF64-1) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/release
main updates (ABF64-2) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/updates
restricted (ABF64-3) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/release
restricted updates (ABF64-4) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/updates
non-free (ABF64-5) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/release
non-free updates (ABF64-6) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/updates
contrib (ABF64-7) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/release
contrib updates (ABF64-8) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/updates
main (ABF32-1) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/release
main updates (ABF32-2) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/updates
restricted (ABF32-3) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/release
restricted updates (ABF32-4) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/updates
non-free (ABF32-5) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/release
non-free updates (ABF32-6) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/updates
contrib (ABF32-7) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/release
contrib updates (ABF32-8) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/updates
------
## Comment 647
Date: 2013-08-28 13:44:55 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
(In reply to comment #5)
> This also means, though, that we did not bump releases for some new builds
> on abf :/
I don't know what to said... I installed the June 24th ISO 2 times, the last one after some break with the rpm database (now I know how to solve the problem, but in that time I was unable to fix rpm, so I reinstalled because of that). That was one month, maybe one and a half month ago. I had already some problem because system wasn't updated for several days, make me suspect about some problem with repositories. Anyway, after the reinstallation I add the new cooker repositories, so I never had the mix of versions you have now.
Note that I still have some "foreign" packages:
------
$ rpm -qa | grep mdk
lib64cap-ng0-0.7.3-1-mdk2013.0.x86_64
lib64keyutils1-1.5.5-4-mdk2013.0.x86_64
keyutils-1.5.5-4-mdk2013.0.x86_64
mdkonline-2.78-1-omv2013.0.noarch
$ rpm -qa | grep mdv2013
lib64report0-2.0.10-2-mdv2013.0.x86_64
lib64kvilib4-4.3.1-1-mdv2013.0.x86_64
ueagle-firmware-1.1-5-mdv2013.0.noarch
iwlwifi-4965-ucode-228.61.2.24-1-mdv2013.0.noarch
zd1201-firmware-0.14-4-mdv2013.0.noarch
iwlwifi-6005-ucode-18.168.6.1-1-mdv2013.0.noarch
iwlwifi-100-ucode-39.31.5.1-1-mdv2013.0.noarch
iwlwifi-1000-ucode-128.50.3.1-1-mdv2013.0.noarch
iwlwifi-agn-ucode-1.0-9-mdv2013.0.noarch
iwlwifi-6000-ucode-9.221.4.1-1-mdv2013.0.noarch
iwlwifi-6050-ucode-41.28.5.1-2-mdv2013.0.noarch
iwlwifi-6030-ucode-18.168.6.1-1-mdv2013.0.noarch
iwlwifi-3945-ucode-15.32.2.9-1-mdv2013.0.noarch
iwlwifi-5150-ucode-8.24.2.2-1-mdv2013.0.noarch
bluez-firmware-1.2-6-mdv2013.0.noarch
iwlwifi-5000-ucode-8.83.5.1-2-mdv2013.0.noarch
prism54-firmware-1.0.4.3-7-mdv2013.0.noarch
ipw2200-firmware-3.1-3-mdv2013.0.noarch
speedtouch-firmware-0.1-9-mdv2013.0.noarch
ipw2100-firmware-1.3-5-mdv2013.0.noarch
lib64gii1-1.0.2-19-mdv2013.0.x86_64
lib64ggi2-2.2.2-19-mdv2013.0.x86_64
libggi-2.2.2-19-mdv2013.0.x86_64
lib64musicbrainz5_0-5.0.1-3-mdv2013.0.x86_64
foomatic-db-4.0-2.20130115.1-mdv2013.0.noarch
lib64djvulibre21-3.5.24-4-mdv2013.0.x86_64
lib64kgapi0-0.4.3-1-mdv2013.0.x86_64
lib64selinux1-2.0.78-6-mdv2013.0.x86_64
python-selinux-2.0.78-6-mdv2013.0.x86_64
cups-drivers-magicolor5440dl-1.2.1-13-mdv2013.0.x86_64
python-reportlab-2.6-1-mdv2013.0.x86_64
gnome-doc-utils-0.20.10-4-mdv2013.0.noarch
lib64powerman0-2.3.9-3-mdv2013.0.x86_64
xl2tpd-1.3.0-2-mdv2013.0.x86_64
cups-drivers-magicolor2430dl-1.6.1-14-mdv2013.0.x86_64
vpnpptp-allde-0.3.4-3-mdv2013.0.x86_64
reiserfsprogs-3.6.21-5-mdv2013.0.x86_64
get-skype-2.2.0.35-5-mdv2013.0.x86_64
libx264_129-0.129-0.20130214.2-mdv2013.0.i586
lxsession-0.4.6.1-3-mdv2013.0.x86_64
lxterminal-0.1.11-3-mdv2013.0.x86_64
lxrandr-0.1.2-1-mdv2013.0.x86_64
unrar-4.20-2-mdv2013.0.x86_64
commons-logging-1.1.1-1-mdv2013.0.noarch
rhino-1.7-8-mdv2013.0.noarch
libreadline-java-0.8.1-3-mdv2013.0.x86_64
------
So, as you said, there ARE some problem with abf. Or at least, with packages in the actual repositories. Note that a bug is still open for that reason: bug #54.
## Comment 659
Date: 2013-08-29 17:16:04 +0000
From: @benbullard79
(In reply to comment #6)
> (In reply to comment #4)
> > $ urpmq --list-media active
> > main (ABF64-1)
> > main updates (ABF64-2)
> > restricted (ABF64-3)
> > restricted updates (ABF64-4)
> > non-free (ABF64-5)
> > non-free updates (ABF64-6)
> > contrib (ABF64-7)
> > contrib updates (ABF64-8)
> > main (ABF32-1)
> > main updates (ABF32-2)
> > restricted (ABF32-3)
> > restricted updates (ABF32-4)
> > non-free (ABF32-5)
> > non-free updates (ABF32-6)
> > contrib (ABF32-7)
> > contrib updates (ABF32-8)
> >
>
> Just in case you need it:
>
> ------
> $ urpmq --list-media active --list-url
> main (ABF64-1)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/release
> main updates (ABF64-2)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/updates
> restricted (ABF64-3)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/
> release
> restricted updates (ABF64-4)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/
> updates
> non-free (ABF64-5)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/
> release
> non-free updates (ABF64-6)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/
> updates
> contrib (ABF64-7)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/
> release
> contrib updates (ABF64-8)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/
> updates
> main (ABF32-1)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/release
> main updates (ABF32-2)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/updates
> restricted (ABF32-3)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/
> release
> restricted updates (ABF32-4)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/
> updates
> non-free (ABF32-5)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/
> release
> non-free updates (ABF32-6)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/
> updates
> contrib (ABF32-7)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/
> release
> contrib updates (ABF32-8)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/
> updates
>
> ------
Those repos are cooker. This bug is against the 2013 repos:
# urpmi.addmedia --distrib http://abf-downloads.rosalinux.ru/openmandriva2013.0/repository/x86_64/
Otherwise your point about system preferring mdv over omv packages is correct. Currently I can't try to update with all repos enabled due to this:
detecting looping forever while trying to resolve dependancies.
Aborting... Try again with '-vv --debug' options at /usr/lib/perl5/vendor_perl/5.16.3/x86_64-linux-thread-multi/URPM/Resolve.pm line 1137, <STDIN> line 10.
unlocking rpm database
unlocking urpmi database
## Comment 661
Date: 2013-08-30 05:09:49 +0000
From: @benbullard79
I just checked in my Cooker partition on the same computer and these problems do not exist there. Again this is a bug against the 2013 x86_64 repos. And I'm finding them to not be in a good state.
## Comment 838
Date: 2013-09-14 21:17:46 +0000
From: @robxu9
(In reply to comment #9)
> I just checked in my Cooker partition on the same computer and these
> problems do not exist there. Again this is a bug against the 2013 x86_64
> repos. And I'm finding them to not be in a good state.
I can no longer confirm this for the 2013.0 repos.
Granted the fluctuating state of beta, it's expected, and it's primarily one of the reasons why we say "it's beta quality".
Either way, be vigilant before saying yes to any transaction.
## Comment 840
Date: 2013-09-14 22:39:24 +0000
From: @benbullard79
(In reply to comment #10)
> (In reply to comment #9)
> > I just checked in my Cooker partition on the same computer and these
> > problems do not exist there. Again this is a bug against the 2013 x86_64
> > repos. And I'm finding them to not be in a good state.
>
> I can no longer confirm this for the 2013.0 repos.
> Granted the fluctuating state of beta, it's expected, and it's primarily one
> of the reasons why we say "it's beta quality".
>
> Either way, be vigilant before saying yes to any transaction.
Agreed. Not seeing in 2013 repos today but pay attention regardless.
| 1.0 | Enabling all x86_64 repos results in urpmi removing entire operating system. (Bugzilla Bug 111) - This issue was created automatically with bugzilla2github
# Bugzilla Bug 111
Date: 2013-08-28 08:03:47 +0000
From: @benbullard79
To: OpenMandriva QA <<bugs@openmandriva.org>>
CC: @robxu9, siriustheking@yahoo.com
Last updated: 2013-09-14 22:39:24 +0000
## Comment 636
Date: 2013-08-28 08:03:47 +0000
From: @benbullard79
Created attachment 42
Results of urpmi --auto-select with all x86_64 repos enabled.
> Attached file: om.2013.x86_64.repo.txt (text/plain, 34874 bytes)
> Description: Results of urpmi --auto-select with all x86_64 repos enabled.
## Comment 637
Date: 2013-08-28 08:08:48 +0000
From: @benbullard79
Description is as titled. Also there is something seriously wrong with urmpi or related that this is even possible. urpmi should not offer to remove packages that break system. Am aware that this is probably related to previous bugs. However my results seemed significant enough to report.
## Comment 642
Date: 2013-08-28 13:04:47 +0000
From: @robxu9
(In reply to comment #1)
> Description is as titled. Also there is something seriously wrong with urmpi
> or related that this is even possible. urpmi should not offer to remove
> packages that break system. Am aware that this is probably related to
> previous bugs. However my results seemed significant enough to report.
I think the repository is inconsistent right now for openmandriva2013.0...
## Comment 643
Date: 2013-08-28 13:07:40 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
I'm maybe wrong, but I can note in the attachment that you have something like a mess of versions.
Let me explain. I can see things like:
--- ATTACHMENT 42 ---
Some requested packages cannot be installed:
drakguard-0.7.7-6-omv2013.0.noarch (in order to keep drakguard-0.7.7-6-mdv2013.0.noarch)
drakx-kbd-mouse-x11-0.102-1-omv2013.0.x86_64 (in order to keep drakx-kbd-mouse-x11-0.102-1-mdv2013.0.x86_64)
[...]
--- ATTACHMENT 42 ---
So, it's trying to keep mdv2013.0 versions, avoiding to update to omv2013.0 versions. As omv2013 are the latest (and most important, they're the ACTUAL cooker, so if you want to try Cooker or Beta I suggest you that try to keep all the actual/latest packages), you'll never reach a full update, as the system seems that always try to keep the old mdv2013 versions.
I'm not a developer, but I think that it's not a good thing to keep that mix. If uninstall/reinstall is not viable (there are too many packages), maybe the best solution is reinstall from the ISO, and only add the actual repositories.
I'm testing OMV 64 bits in a box and in a VM, with all repositories enabled (I'm using Cooker repositories), 32 bits and 64 bits, and I don't have the problems you describe. Sometimes there are problem with dependencies (like bug #109), but none is as serious that a reinstallation of the system is the only solution. I had even a serious problem with grub (see bug #97) and thanks to TPG a reinstallation was not needed !
## Comment 644
Date: 2013-08-28 13:10:41 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
My situation:
------
$ urpmq --list-media active
main (ABF64-1)
main updates (ABF64-2)
restricted (ABF64-3)
restricted updates (ABF64-4)
non-free (ABF64-5)
non-free updates (ABF64-6)
contrib (ABF64-7)
contrib updates (ABF64-8)
main (ABF32-1)
main updates (ABF32-2)
restricted (ABF32-3)
restricted updates (ABF32-4)
non-free (ABF32-5)
non-free updates (ABF32-6)
contrib (ABF32-7)
contrib updates (ABF32-8)
# urpmi --auto-select
Los paquetes están actualizados
------
Translation:
Los paquetes están actualizados = All packages are updated.
I'm writing from the VBox VM, so the nVidia problem (bug #109) doesn't appear here.
## Comment 645
Date: 2013-08-28 13:11:20 +0000
From: @robxu9
(In reply to comment #3)
> I'm maybe wrong, but I can note in the attachment that you have something
> like a mess of versions.
>
> Let me explain. I can see things like:
>
> --- ATTACHMENT 42 [details] ---
> Some requested packages cannot be installed:
> drakguard-0.7.7-6-omv2013.0.noarch (in order to keep
> drakguard-0.7.7-6-mdv2013.0.noarch)
> drakx-kbd-mouse-x11-0.102-1-omv2013.0.x86_64 (in order to keep
> drakx-kbd-mouse-x11-0.102-1-mdv2013.0.x86_64)
> [...]
> --- ATTACHMENT 42 [details] ---
>
> So, it's trying to keep mdv2013.0 versions, avoiding to update to omv2013.0
> versions. As omv2013 are the latest (and most important, they're the ACTUAL
> cooker, so if you want to try Cooker or Beta I suggest you that try to keep
> all the actual/latest packages), you'll never reach a full update, as the
> system seems that always try to keep the old mdv2013 versions.
> I'm not a developer, but I think that it's not a good thing to keep that
> mix. If uninstall/reinstall is not viable (there are too many packages),
> maybe the best solution is reinstall from the ISO, and only add the actual
> repositories.
> I'm testing OMV 64 bits in a box and in a VM, with all repositories enabled
> (I'm using Cooker repositories), 32 bits and 64 bits, and I don't have the
> problems you describe. Sometimes there are problem with dependencies (like
> bug #109), but none is as serious that a reinstallation of the system is the
> only solution. I had even a serious problem with grub (see bug #97) and
> thanks to TPG a reinstallation was not needed !
^ ah, you're right there. Good catch!
This also means, though, that we did not bump releases for some new builds on abf :/
## Comment 646
Date: 2013-08-28 13:18:03 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
(In reply to comment #4)
> $ urpmq --list-media active
> main (ABF64-1)
> main updates (ABF64-2)
> restricted (ABF64-3)
> restricted updates (ABF64-4)
> non-free (ABF64-5)
> non-free updates (ABF64-6)
> contrib (ABF64-7)
> contrib updates (ABF64-8)
> main (ABF32-1)
> main updates (ABF32-2)
> restricted (ABF32-3)
> restricted updates (ABF32-4)
> non-free (ABF32-5)
> non-free updates (ABF32-6)
> contrib (ABF32-7)
> contrib updates (ABF32-8)
>
Just in case you need it:
------
$ urpmq --list-media active --list-url
main (ABF64-1) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/release
main updates (ABF64-2) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/updates
restricted (ABF64-3) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/release
restricted updates (ABF64-4) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/updates
non-free (ABF64-5) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/release
non-free updates (ABF64-6) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/updates
contrib (ABF64-7) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/release
contrib updates (ABF64-8) http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/updates
main (ABF32-1) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/release
main updates (ABF32-2) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/updates
restricted (ABF32-3) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/release
restricted updates (ABF32-4) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/updates
non-free (ABF32-5) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/release
non-free updates (ABF32-6) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/updates
contrib (ABF32-7) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/release
contrib updates (ABF32-8) http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/updates
------
## Comment 647
Date: 2013-08-28 13:44:55 +0000
From: Gus Ballan <<siriustheking@yahoo.com>>
(In reply to comment #5)
> This also means, though, that we did not bump releases for some new builds
> on abf :/
I don't know what to said... I installed the June 24th ISO 2 times, the last one after some break with the rpm database (now I know how to solve the problem, but in that time I was unable to fix rpm, so I reinstalled because of that). That was one month, maybe one and a half month ago. I had already some problem because system wasn't updated for several days, make me suspect about some problem with repositories. Anyway, after the reinstallation I add the new cooker repositories, so I never had the mix of versions you have now.
Note that I still have some "foreign" packages:
------
$ rpm -qa | grep mdk
lib64cap-ng0-0.7.3-1-mdk2013.0.x86_64
lib64keyutils1-1.5.5-4-mdk2013.0.x86_64
keyutils-1.5.5-4-mdk2013.0.x86_64
mdkonline-2.78-1-omv2013.0.noarch
$ rpm -qa | grep mdv2013
lib64report0-2.0.10-2-mdv2013.0.x86_64
lib64kvilib4-4.3.1-1-mdv2013.0.x86_64
ueagle-firmware-1.1-5-mdv2013.0.noarch
iwlwifi-4965-ucode-228.61.2.24-1-mdv2013.0.noarch
zd1201-firmware-0.14-4-mdv2013.0.noarch
iwlwifi-6005-ucode-18.168.6.1-1-mdv2013.0.noarch
iwlwifi-100-ucode-39.31.5.1-1-mdv2013.0.noarch
iwlwifi-1000-ucode-128.50.3.1-1-mdv2013.0.noarch
iwlwifi-agn-ucode-1.0-9-mdv2013.0.noarch
iwlwifi-6000-ucode-9.221.4.1-1-mdv2013.0.noarch
iwlwifi-6050-ucode-41.28.5.1-2-mdv2013.0.noarch
iwlwifi-6030-ucode-18.168.6.1-1-mdv2013.0.noarch
iwlwifi-3945-ucode-15.32.2.9-1-mdv2013.0.noarch
iwlwifi-5150-ucode-8.24.2.2-1-mdv2013.0.noarch
bluez-firmware-1.2-6-mdv2013.0.noarch
iwlwifi-5000-ucode-8.83.5.1-2-mdv2013.0.noarch
prism54-firmware-1.0.4.3-7-mdv2013.0.noarch
ipw2200-firmware-3.1-3-mdv2013.0.noarch
speedtouch-firmware-0.1-9-mdv2013.0.noarch
ipw2100-firmware-1.3-5-mdv2013.0.noarch
lib64gii1-1.0.2-19-mdv2013.0.x86_64
lib64ggi2-2.2.2-19-mdv2013.0.x86_64
libggi-2.2.2-19-mdv2013.0.x86_64
lib64musicbrainz5_0-5.0.1-3-mdv2013.0.x86_64
foomatic-db-4.0-2.20130115.1-mdv2013.0.noarch
lib64djvulibre21-3.5.24-4-mdv2013.0.x86_64
lib64kgapi0-0.4.3-1-mdv2013.0.x86_64
lib64selinux1-2.0.78-6-mdv2013.0.x86_64
python-selinux-2.0.78-6-mdv2013.0.x86_64
cups-drivers-magicolor5440dl-1.2.1-13-mdv2013.0.x86_64
python-reportlab-2.6-1-mdv2013.0.x86_64
gnome-doc-utils-0.20.10-4-mdv2013.0.noarch
lib64powerman0-2.3.9-3-mdv2013.0.x86_64
xl2tpd-1.3.0-2-mdv2013.0.x86_64
cups-drivers-magicolor2430dl-1.6.1-14-mdv2013.0.x86_64
vpnpptp-allde-0.3.4-3-mdv2013.0.x86_64
reiserfsprogs-3.6.21-5-mdv2013.0.x86_64
get-skype-2.2.0.35-5-mdv2013.0.x86_64
libx264_129-0.129-0.20130214.2-mdv2013.0.i586
lxsession-0.4.6.1-3-mdv2013.0.x86_64
lxterminal-0.1.11-3-mdv2013.0.x86_64
lxrandr-0.1.2-1-mdv2013.0.x86_64
unrar-4.20-2-mdv2013.0.x86_64
commons-logging-1.1.1-1-mdv2013.0.noarch
rhino-1.7-8-mdv2013.0.noarch
libreadline-java-0.8.1-3-mdv2013.0.x86_64
------
So, as you said, there ARE some problem with abf. Or at least, with packages in the actual repositories. Note that a bug is still open for that reason: bug #54.
## Comment 659
Date: 2013-08-29 17:16:04 +0000
From: @benbullard79
(In reply to comment #6)
> (In reply to comment #4)
> > $ urpmq --list-media active
> > main (ABF64-1)
> > main updates (ABF64-2)
> > restricted (ABF64-3)
> > restricted updates (ABF64-4)
> > non-free (ABF64-5)
> > non-free updates (ABF64-6)
> > contrib (ABF64-7)
> > contrib updates (ABF64-8)
> > main (ABF32-1)
> > main updates (ABF32-2)
> > restricted (ABF32-3)
> > restricted updates (ABF32-4)
> > non-free (ABF32-5)
> > non-free updates (ABF32-6)
> > contrib (ABF32-7)
> > contrib updates (ABF32-8)
> >
>
> Just in case you need it:
>
> ------
> $ urpmq --list-media active --list-url
> main (ABF64-1)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/release
> main updates (ABF64-2)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/main/updates
> restricted (ABF64-3)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/
> release
> restricted updates (ABF64-4)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/restricted/
> updates
> non-free (ABF64-5)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/
> release
> non-free updates (ABF64-6)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/non-free/
> updates
> contrib (ABF64-7)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/
> release
> contrib updates (ABF64-8)
> http://abf-downloads.rosalinux.ru/cooker/repository/x86_64/media/contrib/
> updates
> main (ABF32-1)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/release
> main updates (ABF32-2)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/main/updates
> restricted (ABF32-3)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/
> release
> restricted updates (ABF32-4)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/restricted/
> updates
> non-free (ABF32-5)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/
> release
> non-free updates (ABF32-6)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/non-free/
> updates
> contrib (ABF32-7)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/
> release
> contrib updates (ABF32-8)
> http://abf-downloads.rosalinux.ru/cooker/repository/i586/media/contrib/
> updates
>
> ------
Those repos are cooker. This bug is against the 2013 repos:
# urpmi.addmedia --distrib http://abf-downloads.rosalinux.ru/openmandriva2013.0/repository/x86_64/
Otherwise your point about system preferring mdv over omv packages is correct. Currently I can't try to update with all repos enabled due to this:
detecting looping forever while trying to resolve dependancies.
Aborting... Try again with '-vv --debug' options at /usr/lib/perl5/vendor_perl/5.16.3/x86_64-linux-thread-multi/URPM/Resolve.pm line 1137, <STDIN> line 10.
unlocking rpm database
unlocking urpmi database
## Comment 661
Date: 2013-08-30 05:09:49 +0000
From: @benbullard79
I just checked in my Cooker partition on the same computer and these problems do not exist there. Again this is a bug against the 2013 x86_64 repos. And I'm finding them to not be in a good state.
## Comment 838
Date: 2013-09-14 21:17:46 +0000
From: @robxu9
(In reply to comment #9)
> I just checked in my Cooker partition on the same computer and these
> problems do not exist there. Again this is a bug against the 2013 x86_64
> repos. And I'm finding them to not be in a good state.
I can no longer confirm this for the 2013.0 repos.
Granted the fluctuating state of beta, it's expected, and it's primarily one of the reasons why we say "it's beta quality".
Either way, be vigilant before saying yes to any transaction.
## Comment 840
Date: 2013-09-14 22:39:24 +0000
From: @benbullard79
(In reply to comment #10)
> (In reply to comment #9)
> > I just checked in my Cooker partition on the same computer and these
> > problems do not exist there. Again this is a bug against the 2013 x86_64
> > repos. And I'm finding them to not be in a good state.
>
> I can no longer confirm this for the 2013.0 repos.
> Granted the fluctuating state of beta, it's expected, and it's primarily one
> of the reasons why we say "it's beta quality".
>
> Either way, be vigilant before saying yes to any transaction.
Agreed. Not seeing in 2013 repos today but pay attention regardless.
| non_infrastructure | enabling all repos results in urpmi removing entire operating system bugzilla bug this issue was created automatically with bugzilla bug date from to openmandriva qa lt gt cc siriustheking yahoo com last updated comment date from created attachment results of urpmi auto select with all repos enabled attached file om repo txt text plain bytes description results of urpmi auto select with all repos enabled comment date from description is as titled also there is something seriously wrong with urmpi or related that this is even possible urpmi should not offer to remove packages that break system am aware that this is probably related to previous bugs however my results seemed significant enough to report comment date from in reply to comment description is as titled also there is something seriously wrong with urmpi or related that this is even possible urpmi should not offer to remove packages that break system am aware that this is probably related to previous bugs however my results seemed significant enough to report i think the repository is inconsistent right now for comment date from gus ballan lt gt i m maybe wrong but i can note in the attachment that you have something like a mess of versions let me explain i can see things like attachment some requested packages cannot be installed drakguard noarch in order to keep drakguard noarch drakx kbd mouse in order to keep drakx kbd mouse attachment so it s trying to keep versions avoiding to update to versions as are the latest and most important they re the actual cooker so if you want to try cooker or beta i suggest you that try to keep all the actual latest packages you ll never reach a full update as the system seems that always try to keep the old versions i m not a developer but i think that it s not a good thing to keep that mix if uninstall reinstall is not viable there are too many packages maybe the best solution is reinstall from the iso and only add the actual repositories i m testing omv bits in a box and in a vm with all repositories enabled i m using cooker repositories bits and bits and i don t have the problems you describe sometimes there are problem with dependencies like bug but none is as serious that a reinstallation of the system is the only solution i had even a serious problem with grub see bug and thanks to tpg a reinstallation was not needed comment date from gus ballan lt gt my situation urpmq list media active main main updates restricted restricted updates non free non free updates contrib contrib updates main main updates restricted restricted updates non free non free updates contrib contrib updates urpmi auto select los paquetes están actualizados translation los paquetes están actualizados all packages are updated i m writing from the vbox vm so the nvidia problem bug doesn t appear here comment date from in reply to comment i m maybe wrong but i can note in the attachment that you have something like a mess of versions let me explain i can see things like attachment some requested packages cannot be installed drakguard noarch in order to keep drakguard noarch drakx kbd mouse in order to keep drakx kbd mouse attachment so it s trying to keep versions avoiding to update to versions as are the latest and most important they re the actual cooker so if you want to try cooker or beta i suggest you that try to keep all the actual latest packages you ll never reach a full update as the system seems that always try to keep the old versions i m not a developer but i think that it s not a good thing to keep that mix if uninstall reinstall is not viable there are too many packages maybe the best solution is reinstall from the iso and only add the actual repositories i m testing omv bits in a box and in a vm with all repositories enabled i m using cooker repositories bits and bits and i don t have the problems you describe sometimes there are problem with dependencies like bug but none is as serious that a reinstallation of the system is the only solution i had even a serious problem with grub see bug and thanks to tpg a reinstallation was not needed ah you re right there good catch this also means though that we did not bump releases for some new builds on abf comment date from gus ballan lt gt in reply to comment urpmq list media active main main updates restricted restricted updates non free non free updates contrib contrib updates main main updates restricted restricted updates non free non free updates contrib contrib updates just in case you need it urpmq list media active list url main main updates restricted restricted updates non free non free updates contrib contrib updates main main updates restricted restricted updates non free non free updates contrib contrib updates comment date from gus ballan lt gt in reply to comment this also means though that we did not bump releases for some new builds on abf i don t know what to said i installed the june iso times the last one after some break with the rpm database now i know how to solve the problem but in that time i was unable to fix rpm so i reinstalled because of that that was one month maybe one and a half month ago i had already some problem because system wasn t updated for several days make me suspect about some problem with repositories anyway after the reinstallation i add the new cooker repositories so i never had the mix of versions you have now note that i still have some foreign packages rpm qa grep mdk keyutils mdkonline noarch rpm qa grep ueagle firmware noarch iwlwifi ucode noarch firmware noarch iwlwifi ucode noarch iwlwifi ucode noarch iwlwifi ucode noarch iwlwifi agn ucode noarch iwlwifi ucode noarch iwlwifi ucode noarch iwlwifi ucode noarch iwlwifi ucode noarch iwlwifi ucode noarch bluez firmware noarch iwlwifi ucode noarch firmware noarch firmware noarch speedtouch firmware noarch firmware noarch libggi foomatic db noarch python selinux cups drivers python reportlab gnome doc utils noarch cups drivers vpnpptp allde reiserfsprogs get skype lxsession lxterminal lxrandr unrar commons logging noarch rhino noarch libreadline java so as you said there are some problem with abf or at least with packages in the actual repositories note that a bug is still open for that reason bug comment date from in reply to comment in reply to comment urpmq list media active main main updates restricted restricted updates non free non free updates contrib contrib updates main main updates restricted restricted updates non free non free updates contrib contrib updates just in case you need it urpmq list media active list url main main updates restricted release restricted updates updates non free release non free updates updates contrib release contrib updates updates main main updates restricted release restricted updates updates non free release non free updates updates contrib release contrib updates updates those repos are cooker this bug is against the repos urpmi addmedia distrib otherwise your point about system preferring mdv over omv packages is correct currently i can t try to update with all repos enabled due to this detecting looping forever while trying to resolve dependancies aborting try again with vv debug options at usr lib vendor perl linux thread multi urpm resolve pm line line unlocking rpm database unlocking urpmi database comment date from i just checked in my cooker partition on the same computer and these problems do not exist there again this is a bug against the repos and i m finding them to not be in a good state comment date from in reply to comment i just checked in my cooker partition on the same computer and these problems do not exist there again this is a bug against the repos and i m finding them to not be in a good state i can no longer confirm this for the repos granted the fluctuating state of beta it s expected and it s primarily one of the reasons why we say it s beta quality either way be vigilant before saying yes to any transaction comment date from in reply to comment in reply to comment i just checked in my cooker partition on the same computer and these problems do not exist there again this is a bug against the repos and i m finding them to not be in a good state i can no longer confirm this for the repos granted the fluctuating state of beta it s expected and it s primarily one of the reasons why we say it s beta quality either way be vigilant before saying yes to any transaction agreed not seeing in repos today but pay attention regardless | 0 |
243,706 | 7,861,020,423 | IssuesEvent | 2018-06-21 22:07:13 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | es.m.wikipedia.org - The layout becomes blurry when the page is scrolled down/up | browser-firefox-mobile priority-normal | <!-- @browser: Firefox Mobile Nightly 62.0a1 (2018-05-20) -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 -->
<!-- @reported_with: addon-reporter-firefox -->
**URL**: https://es.m.wikipedia.org/wiki/Anexo:Pa%C3%ADses_por_%C3%ADndice_de_desarrollo_humano
**Browser / Version**: Firefox Mobile Nightly 62.0a1 (2018-05-20)
**Operating System**: Google Pixel (Android 8.1.0) - 1080 x 1920 pixels (~441 ppi pixel density)
**Tested Another Browser**: Yes
**Problem type**: Design is broken
**Description**: The layout becomes blurry when the page is scrolled down/up
**Steps to Reproduce**:
1. Navigate to https://es.m.wikipedia.org/wiki/Anexo:Pa%C3%ADses_por_%C3%ADndice_de_desarrollo_humano
2. Scroll down the page.
3. Observe the page layout.
**Expected Behavior:**
The page is fully visible.
**Actual Behavior:**
Some section of the page is blurred.
**Note:**
1. Also reproducible when scrolling up the page.
2. Reproducible on Firefox 60.0.2 Release.
3. Not reproducible on Chrome 67.0.3396.87.
4. Screenshot attached.
**Watchers:**
@softvision-sergiulogigan
@softvision-oana-arbuzov
sv; country: es
[](https://webcompat.com/uploads/2018/6/022baf2d-ccab-4390-b737-0eaafa67ffea.jpeg)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | es.m.wikipedia.org - The layout becomes blurry when the page is scrolled down/up - <!-- @browser: Firefox Mobile Nightly 62.0a1 (2018-05-20) -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 -->
<!-- @reported_with: addon-reporter-firefox -->
**URL**: https://es.m.wikipedia.org/wiki/Anexo:Pa%C3%ADses_por_%C3%ADndice_de_desarrollo_humano
**Browser / Version**: Firefox Mobile Nightly 62.0a1 (2018-05-20)
**Operating System**: Google Pixel (Android 8.1.0) - 1080 x 1920 pixels (~441 ppi pixel density)
**Tested Another Browser**: Yes
**Problem type**: Design is broken
**Description**: The layout becomes blurry when the page is scrolled down/up
**Steps to Reproduce**:
1. Navigate to https://es.m.wikipedia.org/wiki/Anexo:Pa%C3%ADses_por_%C3%ADndice_de_desarrollo_humano
2. Scroll down the page.
3. Observe the page layout.
**Expected Behavior:**
The page is fully visible.
**Actual Behavior:**
Some section of the page is blurred.
**Note:**
1. Also reproducible when scrolling up the page.
2. Reproducible on Firefox 60.0.2 Release.
3. Not reproducible on Chrome 67.0.3396.87.
4. Screenshot attached.
**Watchers:**
@softvision-sergiulogigan
@softvision-oana-arbuzov
sv; country: es
[](https://webcompat.com/uploads/2018/6/022baf2d-ccab-4390-b737-0eaafa67ffea.jpeg)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_infrastructure | es m wikipedia org the layout becomes blurry when the page is scrolled down up url browser version firefox mobile nightly operating system google pixel android x pixels ppi pixel density tested another browser yes problem type design is broken description the layout becomes blurry when the page is scrolled down up steps to reproduce navigate to scroll down the page observe the page layout expected behavior the page is fully visible actual behavior some section of the page is blurred note also reproducible when scrolling up the page reproducible on firefox release not reproducible on chrome screenshot attached watchers softvision sergiulogigan softvision oana arbuzov sv country es from with ❤️ | 0 |
11,790 | 9,422,221,355 | IssuesEvent | 2019-04-11 08:52:44 | gap-system/gap | https://api.github.com/repos/gap-system/gap | opened | Find or write a GitHub bot which handles label implication | topic: infrastructure | E.g. that bot could automatically add the `kind: bug` label to any issue to which any of the other more specific labels such `kind: bug: crash` are added.
Perhaps such a bot already exists (I have not really tried hard to find one). Alternatively, one could implement one, e.g. based on [ProBot](https://probot.github.io) which is made for just such things. One could also try to solicit help with such a thing via https://github.com/probot/ideas/issues (and also check if somebody else did so already). | 1.0 | Find or write a GitHub bot which handles label implication - E.g. that bot could automatically add the `kind: bug` label to any issue to which any of the other more specific labels such `kind: bug: crash` are added.
Perhaps such a bot already exists (I have not really tried hard to find one). Alternatively, one could implement one, e.g. based on [ProBot](https://probot.github.io) which is made for just such things. One could also try to solicit help with such a thing via https://github.com/probot/ideas/issues (and also check if somebody else did so already). | infrastructure | find or write a github bot which handles label implication e g that bot could automatically add the kind bug label to any issue to which any of the other more specific labels such kind bug crash are added perhaps such a bot already exists i have not really tried hard to find one alternatively one could implement one e g based on which is made for just such things one could also try to solicit help with such a thing via and also check if somebody else did so already | 1 |
35,653 | 31,996,324,233 | IssuesEvent | 2023-09-21 09:25:11 | ministryofjustice/data-platform | https://api.github.com/repos/ministryofjustice/data-platform | opened | Import Airflow Prod IAM Roles into Data Platform Terraform | Data Platform Core Infrastructure | This is a duplicate of this ticket - altered for production.
To help decompose https://github.com/ministryofjustice/data-platform/issues/1232 into more manageable chunks, this ticket looks to cover the IAM related architecture for Airflow, and the process of moving it from management by pulumi into terraform. The list of expected resources is:
- [ ] airflow-prod-execution-role and its associated policy
- [ ] airflow-prod-node-instance-role and its associated policy
- [ ] airflow-prod-cluster-autoscaler-role
- [ ] airflow-prod-default-pod-role
- [ ] airflow-prod-flow-log-role
For each, the resource should be defined in the Data Platform repo according to its current state (per the AWS console, as this may be disjointed with the state in pulumi code), and imported to the stack so it can be managed via terraform plan/apply. | 1.0 | Import Airflow Prod IAM Roles into Data Platform Terraform - This is a duplicate of this ticket - altered for production.
To help decompose https://github.com/ministryofjustice/data-platform/issues/1232 into more manageable chunks, this ticket looks to cover the IAM related architecture for Airflow, and the process of moving it from management by pulumi into terraform. The list of expected resources is:
- [ ] airflow-prod-execution-role and its associated policy
- [ ] airflow-prod-node-instance-role and its associated policy
- [ ] airflow-prod-cluster-autoscaler-role
- [ ] airflow-prod-default-pod-role
- [ ] airflow-prod-flow-log-role
For each, the resource should be defined in the Data Platform repo according to its current state (per the AWS console, as this may be disjointed with the state in pulumi code), and imported to the stack so it can be managed via terraform plan/apply. | infrastructure | import airflow prod iam roles into data platform terraform this is a duplicate of this ticket altered for production to help decompose into more manageable chunks this ticket looks to cover the iam related architecture for airflow and the process of moving it from management by pulumi into terraform the list of expected resources is airflow prod execution role and its associated policy airflow prod node instance role and its associated policy airflow prod cluster autoscaler role airflow prod default pod role airflow prod flow log role for each the resource should be defined in the data platform repo according to its current state per the aws console as this may be disjointed with the state in pulumi code and imported to the stack so it can be managed via terraform plan apply | 1 |
344,871 | 30,768,455,813 | IssuesEvent | 2023-07-30 15:47:58 | 4Ailen/backend | https://api.github.com/repos/4Ailen/backend | closed | refactor : MockControllerTest, BusinessTest, IntegrationControllerTest 추가 | 🧪test ⚙️refactor | <!-- Issue 작성 전에 우선 Assignees, label 지정하기 -->
## 📄 이슈 내용
<!-- 이슈 내용 요약 설명 -->
>
### TEST CODE 변경
- 현재 Business와 Converter 코드를 통해 기존의 서비스코드가 많이 줄고 변경되었습니다.
- Business 코드를 통해 서비스 코드에 단일 책임을 부여하게 되었더니, 서비스 코드가 매우 짧아졌습니다. 또한 짧아진 만큼 어려운 코드를 담고 있지않아, Business와 Controller에 집중하여 실제 동작을 확인하는 테스트코드를 작성하게되었습니다.
## ✅ 체크리스트
- [x] IntegerationControllerTest
- [x] MockControllerTest
## ➕ETC
| 1.0 | refactor : MockControllerTest, BusinessTest, IntegrationControllerTest 추가 - <!-- Issue 작성 전에 우선 Assignees, label 지정하기 -->
## 📄 이슈 내용
<!-- 이슈 내용 요약 설명 -->
>
### TEST CODE 변경
- 현재 Business와 Converter 코드를 통해 기존의 서비스코드가 많이 줄고 변경되었습니다.
- Business 코드를 통해 서비스 코드에 단일 책임을 부여하게 되었더니, 서비스 코드가 매우 짧아졌습니다. 또한 짧아진 만큼 어려운 코드를 담고 있지않아, Business와 Controller에 집중하여 실제 동작을 확인하는 테스트코드를 작성하게되었습니다.
## ✅ 체크리스트
- [x] IntegerationControllerTest
- [x] MockControllerTest
## ➕ETC
| non_infrastructure | refactor mockcontrollertest businesstest integrationcontrollertest 추가 📄 이슈 내용 test code 변경 현재 business와 converter 코드를 통해 기존의 서비스코드가 많이 줄고 변경되었습니다 business 코드를 통해 서비스 코드에 단일 책임을 부여하게 되었더니 서비스 코드가 매우 짧아졌습니다 또한 짧아진 만큼 어려운 코드를 담고 있지않아 business와 controller에 집중하여 실제 동작을 확인하는 테스트코드를 작성하게되었습니다 ✅ 체크리스트 integerationcontrollertest mockcontrollertest ➕etc | 0 |
904 | 2,998,666,351 | IssuesEvent | 2015-07-23 15:10:50 | travis-ci/travis-ci | https://api.github.com/repos/travis-ci/travis-ci | closed | Deploy a travis-wide Apt-Cacher instance | feature-request infrastructure | After several iterations discussing installation of large .deb packages (in my case Oracle-XE), @Mezzle on irc proposed that the travis infrastructure be augmented with https://help.ubuntu.com/community/Apt-Cacher-Server .
This seems particularly well suited for travis. For one it will lighten the network load for repeatedly installed packages, especially by complex projects with multiple dependencies. In addition since an apt caching proxy is not a full blown mirror, this would minimize issues of "hosting" publicly-accessible but not freely-redistributable binary .debs.
My own use case - implementing this will allow me to install/configure Oracle-XE in about 20 seconds, as opposed to 7 minutes(!) for download only. Will also effectively resolve https://github.com/travis-ci/travis-ci/issues/689 and https://github.com/travis-ci/travis-cookbooks/issues/87
@joshk, @Mezzle what do we need to do to make this happen? | 1.0 | Deploy a travis-wide Apt-Cacher instance - After several iterations discussing installation of large .deb packages (in my case Oracle-XE), @Mezzle on irc proposed that the travis infrastructure be augmented with https://help.ubuntu.com/community/Apt-Cacher-Server .
This seems particularly well suited for travis. For one it will lighten the network load for repeatedly installed packages, especially by complex projects with multiple dependencies. In addition since an apt caching proxy is not a full blown mirror, this would minimize issues of "hosting" publicly-accessible but not freely-redistributable binary .debs.
My own use case - implementing this will allow me to install/configure Oracle-XE in about 20 seconds, as opposed to 7 minutes(!) for download only. Will also effectively resolve https://github.com/travis-ci/travis-ci/issues/689 and https://github.com/travis-ci/travis-cookbooks/issues/87
@joshk, @Mezzle what do we need to do to make this happen? | infrastructure | deploy a travis wide apt cacher instance after several iterations discussing installation of large deb packages in my case oracle xe mezzle on irc proposed that the travis infrastructure be augmented with this seems particularly well suited for travis for one it will lighten the network load for repeatedly installed packages especially by complex projects with multiple dependencies in addition since an apt caching proxy is not a full blown mirror this would minimize issues of hosting publicly accessible but not freely redistributable binary debs my own use case implementing this will allow me to install configure oracle xe in about seconds as opposed to minutes for download only will also effectively resolve and joshk mezzle what do we need to do to make this happen | 1 |
28,916 | 23,604,976,082 | IssuesEvent | 2022-08-24 07:27:47 | AdguardTeam/AdguardFilters | https://api.github.com/repos/AdguardTeam/AdguardFilters | closed | Rename `whitelist.txt` to `allowlist.txt` | Infrastructure Feature Request | We should do the following:
- [x] Rename `whitelist.txt` to `allowlist.txt` everywhere
- [x] Look for the `Whitelist` term and replace it with `Allowlist` in the code | 1.0 | Rename `whitelist.txt` to `allowlist.txt` - We should do the following:
- [x] Rename `whitelist.txt` to `allowlist.txt` everywhere
- [x] Look for the `Whitelist` term and replace it with `Allowlist` in the code | infrastructure | rename whitelist txt to allowlist txt we should do the following rename whitelist txt to allowlist txt everywhere look for the whitelist term and replace it with allowlist in the code | 1 |
30,119 | 24,558,691,956 | IssuesEvent | 2022-10-12 18:09:42 | spring-projects/spring-batch | https://api.github.com/repos/spring-projects/spring-batch | closed | Deprecate throttle limit in favour of using similar features in TaskExecutor implementations | type: task in: infrastructure in: core | **[Dave Syer](https://jira.spring.io/secure/ViewProfile.jspa?name=david_syer)** opened **[BATCH-1364](https://jira.spring.io/browse/BATCH-1364?redirect=false)** and commented
---
No further details from [BATCH-1364](https://jira.spring.io/browse/BATCH-1364?redirect=false) | 1.0 | Deprecate throttle limit in favour of using similar features in TaskExecutor implementations - **[Dave Syer](https://jira.spring.io/secure/ViewProfile.jspa?name=david_syer)** opened **[BATCH-1364](https://jira.spring.io/browse/BATCH-1364?redirect=false)** and commented
---
No further details from [BATCH-1364](https://jira.spring.io/browse/BATCH-1364?redirect=false) | infrastructure | deprecate throttle limit in favour of using similar features in taskexecutor implementations opened and commented no further details from | 1 |
26,047 | 19,594,815,684 | IssuesEvent | 2022-01-05 16:38:30 | gfx-rs/wgpu | https://api.github.com/repos/gfx-rs/wgpu | closed | Run through Miri for testing | type: enhancement help wanted area: infrastructure | **Is your feature request related to a problem? Please describe.**
https://github.com/rust-lang/miri
Helps finding out UB cases in our unsafe code.
**Describe the solution you'd like**
A quick and easy way to run the tests through miri, and/or just CI jobs doing this.
Note that it's required to actually run the GPU tests in order to detect issues.
**Describe alternatives you've considered**
Not doing anything
**Additional context**
| 1.0 | Run through Miri for testing - **Is your feature request related to a problem? Please describe.**
https://github.com/rust-lang/miri
Helps finding out UB cases in our unsafe code.
**Describe the solution you'd like**
A quick and easy way to run the tests through miri, and/or just CI jobs doing this.
Note that it's required to actually run the GPU tests in order to detect issues.
**Describe alternatives you've considered**
Not doing anything
**Additional context**
| infrastructure | run through miri for testing is your feature request related to a problem please describe helps finding out ub cases in our unsafe code describe the solution you d like a quick and easy way to run the tests through miri and or just ci jobs doing this note that it s required to actually run the gpu tests in order to detect issues describe alternatives you ve considered not doing anything additional context | 1 |
13,698 | 10,426,737,080 | IssuesEvent | 2019-09-16 18:17:28 | kaitai-io/kaitai_struct | https://api.github.com/repos/kaitai-io/kaitai_struct | closed | A script setting up KSC in CI | infrastructure | ```bash
#!/usr/bin/env bash
echo "TRAVIS is $TRAVIS"
if [ "$TRAVIS" = "true" ]; then
SUDO="sudo";
else
SUDO="";
fi;
echo "SUDO is $SUDO";
$SUDO apt-get update
if ! $($SUDO apt-get -y install gnupg-curl); then
$SUDO apt-get -y install gnupg1-curl
fi;
$SUDO apt-get install -y apt-transport-https
echo "deb https://dl.bintray.com/kaitai-io/debian_unstable jessie main" | $SUDO tee /etc/apt/sources.list.d/kaitai.list
$SUDO apt-key adv --keyserver hkps://keyserver.ubuntu.com --recv 8756C4F765C9AC3CB6B85D62379CE192D401AB61
$SUDO apt-get update
$SUDO apt-get install kaitai-struct-compiler
export KAITAI_STRUCT_ROOT="/usr/share/kaitai-struct-compiler"
echo "KAITAI_STRUCT_ROOT=$KAITAI_STRUCT_ROOT" | $SUDO tee -a /etc/environment
if ! $(java -version); then
$SUDO apt-get install -y default-jre-headless;
fi;
#git clone --depth=1 https://github.com/kaitai-io/kaitai_struct_formats.git "$KAITAI_STRUCT_ROOT/formats"
ksc --help
``` | 1.0 | A script setting up KSC in CI - ```bash
#!/usr/bin/env bash
echo "TRAVIS is $TRAVIS"
if [ "$TRAVIS" = "true" ]; then
SUDO="sudo";
else
SUDO="";
fi;
echo "SUDO is $SUDO";
$SUDO apt-get update
if ! $($SUDO apt-get -y install gnupg-curl); then
$SUDO apt-get -y install gnupg1-curl
fi;
$SUDO apt-get install -y apt-transport-https
echo "deb https://dl.bintray.com/kaitai-io/debian_unstable jessie main" | $SUDO tee /etc/apt/sources.list.d/kaitai.list
$SUDO apt-key adv --keyserver hkps://keyserver.ubuntu.com --recv 8756C4F765C9AC3CB6B85D62379CE192D401AB61
$SUDO apt-get update
$SUDO apt-get install kaitai-struct-compiler
export KAITAI_STRUCT_ROOT="/usr/share/kaitai-struct-compiler"
echo "KAITAI_STRUCT_ROOT=$KAITAI_STRUCT_ROOT" | $SUDO tee -a /etc/environment
if ! $(java -version); then
$SUDO apt-get install -y default-jre-headless;
fi;
#git clone --depth=1 https://github.com/kaitai-io/kaitai_struct_formats.git "$KAITAI_STRUCT_ROOT/formats"
ksc --help
``` | infrastructure | a script setting up ksc in ci bash usr bin env bash echo travis is travis if then sudo sudo else sudo fi echo sudo is sudo sudo apt get update if sudo apt get y install gnupg curl then sudo apt get y install curl fi sudo apt get install y apt transport https echo deb jessie main sudo tee etc apt sources list d kaitai list sudo apt key adv keyserver hkps keyserver ubuntu com recv sudo apt get update sudo apt get install kaitai struct compiler export kaitai struct root usr share kaitai struct compiler echo kaitai struct root kaitai struct root sudo tee a etc environment if java version then sudo apt get install y default jre headless fi git clone depth kaitai struct root formats ksc help | 1 |
13,640 | 10,369,154,867 | IssuesEvent | 2019-09-07 23:40:15 | perl6/problem-solving | https://api.github.com/repos/perl6/problem-solving | closed | pl6anet.org will be discontinued breaking "Recent Blog Posts" on perl6.org | infrastructure | Currently the right hand side of the perl6.org website "Recent Blog Posts" is dependent on an external system "pl6anet.org" via
https://github.com/perl6/perl6.org/blob/master/fetch-recent-blog-posts.pl
This system will be closing down in about 30 days time and will need someone to work on a replacement if the "Recent Blog Posts" box is to continue.
Hosting a replacement is easy and details are at
https://github.com/stmuk/pl6anet.org
| 1.0 | pl6anet.org will be discontinued breaking "Recent Blog Posts" on perl6.org - Currently the right hand side of the perl6.org website "Recent Blog Posts" is dependent on an external system "pl6anet.org" via
https://github.com/perl6/perl6.org/blob/master/fetch-recent-blog-posts.pl
This system will be closing down in about 30 days time and will need someone to work on a replacement if the "Recent Blog Posts" box is to continue.
Hosting a replacement is easy and details are at
https://github.com/stmuk/pl6anet.org
| infrastructure | org will be discontinued breaking recent blog posts on org currently the right hand side of the org website recent blog posts is dependent on an external system org via this system will be closing down in about days time and will need someone to work on a replacement if the recent blog posts box is to continue hosting a replacement is easy and details are at | 1 |
253,704 | 19,161,957,574 | IssuesEvent | 2021-12-03 01:58:52 | khawla-k-banydomi/ActivityScheduler | https://api.github.com/repos/khawla-k-banydomi/ActivityScheduler | closed | [HU13] Modify holidays set | documentation enhancement | As a holidays-set **creator** , I want to **add** days to a set of **non-working-days** so that I can **change** and **update** holidays-set whenever I want.
### **Description:**
- I have to get the days as a specific day(single day) or (an array of days ) a range of days of the week.
- Assure that the previous mention day/days is no longer in the set of working days. | 1.0 | [HU13] Modify holidays set - As a holidays-set **creator** , I want to **add** days to a set of **non-working-days** so that I can **change** and **update** holidays-set whenever I want.
### **Description:**
- I have to get the days as a specific day(single day) or (an array of days ) a range of days of the week.
- Assure that the previous mention day/days is no longer in the set of working days. | non_infrastructure | modify holidays set as a holidays set creator i want to add days to a set of non working days so that i can change and update holidays set whenever i want description i have to get the days as a specific day single day or an array of days a range of days of the week assure that the previous mention day days is no longer in the set of working days | 0 |
16,360 | 11,942,636,354 | IssuesEvent | 2020-04-02 21:22:58 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | closed | Checkpoint graphs don't work if no option is set to 'vary by' | bug interface/infrastructure | If an .apsimx file contains multiple checkpoints set to appear on graphs, but a graph doesn't have either colour, line type or marker type set to vary by something (e.g. vary by simulation name) then only the data for the current checkpoint will appear on the graph. This is a common situation when graphing data for a single simulation. | 1.0 | Checkpoint graphs don't work if no option is set to 'vary by' - If an .apsimx file contains multiple checkpoints set to appear on graphs, but a graph doesn't have either colour, line type or marker type set to vary by something (e.g. vary by simulation name) then only the data for the current checkpoint will appear on the graph. This is a common situation when graphing data for a single simulation. | infrastructure | checkpoint graphs don t work if no option is set to vary by if an apsimx file contains multiple checkpoints set to appear on graphs but a graph doesn t have either colour line type or marker type set to vary by something e g vary by simulation name then only the data for the current checkpoint will appear on the graph this is a common situation when graphing data for a single simulation | 1 |
9,126 | 7,835,535,936 | IssuesEvent | 2018-06-17 07:33:46 | ressec/hemajoo-foundation | https://api.github.com/repos/ressec/hemajoo-foundation | closed | Customize the labels of the hemajoo-foundation repository | High Infrastructure Task | ## Purpose
Customize the labels of the repository. | 1.0 | Customize the labels of the hemajoo-foundation repository - ## Purpose
Customize the labels of the repository. | infrastructure | customize the labels of the hemajoo foundation repository purpose customize the labels of the repository | 1 |
29,589 | 24,088,714,315 | IssuesEvent | 2022-09-19 13:11:56 | spdk/spdk | https://api.github.com/repos/spdk/spdk | closed | [blockdev_nvme] Timeout while waiting for spdk_tgt to terminate | Infrastructure Intermittent Failure Patches out for review | # CI Intermittent Failure
Happened on WFP13 which doesn't seem to be stable in general. Disabled the node for the time being.
https://ci.spdk.io/results/autotest-per-patch/builds/82811/archive/nvme-phy-autotest/build.log
```
00:03:31.983 START TEST blockdev_nvme
00:03:31.983 ************************************
00:03:31.983 15:31:54 -- common/autotest_common.sh@979 -- # xtrace_enable
00:03:31.983 15:31:54 -- common/autotest_common.sh@980 -- # test/bdev/blockdev.sh nvme
00:03:31.983 * Looking for test storage...
00:03:31.983 * Found test storage at /var/jenkins/workspace/nvme-phy-autotest/spdk/test/bdev
00:03:31.983 15:31:54 -- common/autotest_common.sh@1524 -- # xtrace_enable
00:03:31.983 15:31:54 -- bdev/blockdev.sh@6 -- # source /var/jenkins/workspace/nvme-phy-autotest/spdk/test/bdev/nbd_common.sh
00:03:31.983 15:31:54 -- bdev/nbd_common.sh@1 -- # set -e
00:03:31.983 15:31:54 -- bdev/blockdev.sh@8 -- # rpc_py=rpc_cmd
00:03:31.983 15:31:54 -- bdev/blockdev.sh@9 -- # conf_file=/var/jenkins/workspace/nvme-phy-autotest/spdk/test/bdev/bdev.json
00:03:31.983 15:31:54 -- bdev/blockdev.sh@11 -- # :
00:03:31.983 15:31:54 -- bdev/blockdev.sh@451 -- # QOS_DEV_1=Malloc_0
00:03:31.983 15:31:54 -- bdev/blockdev.sh@452 -- # QOS_DEV_2=Null_1
00:03:31.983 15:31:54 -- bdev/blockdev.sh@453 -- # QOS_RUN_TIME=5
00:03:31.983 15:31:54 -- bdev/blockdev.sh@455 -- # uname -s
00:03:31.983 15:31:54 -- bdev/blockdev.sh@455 -- # '[' Linux = Linux ']'
00:03:31.983 15:31:54 -- bdev/blockdev.sh@457 -- # PRE_RESERVED_MEM=0
00:03:31.983 15:31:54 -- bdev/blockdev.sh@463 -- # test_type=nvme
00:03:31.983 15:31:54 -- bdev/blockdev.sh@464 -- # crypto_device=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@465 -- # wcs_file=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@466 -- # dek=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@467 -- # env_ctx=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@468 -- # '[' -n '' ']'
00:03:31.983 15:31:54 -- bdev/blockdev.sh@479 -- # start_spdk_tgt
00:03:31.983 15:31:54 -- bdev/blockdev.sh@32 -- # spdk_tgt_pid=22451
00:03:31.983 15:31:54 -- bdev/blockdev.sh@33 -- # trap 'killprocess "$spdk_tgt_pid"; exit 1' SIGINT SIGTERM EXIT
00:03:31.983 15:31:54 -- bdev/blockdev.sh@31 -- # /var/jenkins/workspace/nvme-phy-autotest/spdk/build/bin/spdk_tgt ''
00:03:31.983 15:31:54 -- bdev/blockdev.sh@34 -- # waitforlisten 22451
00:03:31.983 15:31:54 -- common/autotest_common.sh@726 -- # '[' -z 22451 ']'
00:03:31.983 15:31:54 -- common/autotest_common.sh@730 -- # local rpc_addr=/var/tmp/spdk.sock
00:03:31.983 15:31:54 -- common/autotest_common.sh@732 -- # echo 'Waiting for process to start up and listen on UNIX domain socket /var/tmp/spdk.sock...'
00:03:31.983 Waiting for process to start up and listen on UNIX domain socket /var/tmp/spdk.sock...
00:03:31.983 15:31:54 -- common/autotest_common.sh@734 -- # xtrace_disable
00:03:31.983 15:31:54 -- common/autotest_common.sh@14 -- # '[' '' '!=' yes ']'
00:03:31.983 15:31:54 -- common/autotest_common.sh@15 -- # PREV_BASH_OPTS=ehxBET
00:03:31.983 15:31:54 -- common/autotest_common.sh@16 -- # [[ ehxBET == *\x* ]]
00:03:31.984 15:31:54 -- common/autotest_common.sh@17 -- # XTRACE_DISABLED=yes
00:03:31.984 15:31:54 -- common/autotest_common.sh@19 -- # set +x
00:03:31.984 [2022-08-16 15:31:54.312202] Starting SPDK v22.09-pre git sha1 01df76d0f / DPDK 22.03.0 initialization...
00:03:31.984 [2022-08-16 15:31:54.312255] [ DPDK EAL parameters: [2022-08-16 15:31:54.312262] spdk_tgt [2022-08-16 15:31:54.312266] --no-shconf [2022-08-16 15:31:54.312271] -c 0x1 [2022-08-16 15:31:54.312276] --huge-unlink [2022-08-16 15:31:54.312301] --log-level=lib.eal:6 [2022-08-16 15:31:54.312307] --log-level=lib.cryptodev:5 [2022-08-16 15:31:54.312311] --log-level=user1:6 [2022-08-16 15:31:54.312316] --base-virtaddr=0x200000000000 [2022-08-16 15:31:54.312321] --match-allocations [2022-08-16 15:31:54.312325] --file-prefix=spdk_pid22451 [2022-08-16 15:31:54.312330] ]
00:03:31.984 EAL: No free 2048 kB hugepages reported on node 1
00:03:31.984 TELEMETRY: No legacy callbacks, legacy socket not created
00:03:31.984 [2022-08-16 15:31:54.371456] app.c: 586:spdk_app_start: *NOTICE*: Total cores available: 1
00:03:31.984 [2022-08-16 15:31:54.535113] reactor.c: 926:reactor_run: *NOTICE*: Reactor started on core 0
00:03:31.984 [2022-08-16 15:31:54.535231] accel_engine.c:1028:sw_accel_engine_init: *NOTICE*: Accel framework software engine initialized.
00:03:32.244 [2022-08-16 15:31:54.685271] 'OCF Core' volume operations registered
00:03:32.244 [2022-08-16 15:31:54.687900] 'SPDK_block_device' volume operations registered
00:03:32.814 15:31:55 -- common/autotest_common.sh@753 -- # xtrace_enable
00:03:32.814 15:31:55 -- common/autotest_common.sh@754 -- # (( i == 0 ))
00:03:32.814 15:31:55 -- common/autotest_common.sh@758 -- # return 0
00:03:32.814 15:31:55 -- bdev/blockdev.sh@480 -- # case "$test_type" in
00:03:32.814 15:31:55 -- bdev/blockdev.sh@485 -- # setup_nvme_conf
00:03:32.814 15:31:55 -- bdev/blockdev.sh@62 -- # local json
00:03:32.814 15:31:55 -- bdev/blockdev.sh@63 -- # mapfile -t json
00:03:32.814 15:31:55 -- bdev/blockdev.sh@63 -- # /var/jenkins/workspace/nvme-phy-autotest/spdk/scripts/gen_nvme.sh
00:03:32.814 15:31:55 -- bdev/blockdev.sh@64 -- # rpc_cmd load_subsystem_config -j ''\''{ "subsystem": "bdev", "config": [ { "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme0", "traddr":"0000:5e:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme1", "traddr":"0000:5f:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme2", "traddr":"0000:d8:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme3", "traddr":"0000:d9:00.0" } } ] }'\'''
00:03:32.814 15:31:55 -- common/autotest_common.sh@496 -- # xtrace_disable
00:03:32.814 15:31:55 -- common/autotest_common.sh@14 -- # '[' no '!=' yes ']'
00:03:32.814 15:31:55 -- common/autotest_common.sh@15 -- # PREV_BASH_OPTS=ehxBET
00:03:32.814 15:31:55 -- common/autotest_common.sh@16 -- # [[ ehxBET == *\x* ]]
00:03:32.814 15:31:55 -- common/autotest_common.sh@17 -- # XTRACE_DISABLED=yes
00:03:32.814 15:31:55 -- common/autotest_common.sh@19 -- # set +x
00:03:38.369 15:32:00 -- common/autotest_common.sh@523 -- # xtrace_enable
00:03:38.369 15:32:00 -- common/autotest_common.sh@524 -- # [[ '' == 0 ]]
00:03:38.369 15:32:00 -- common/autotest_common.sh@524 -- # trap - ERR
00:03:38.369 15:32:00 -- common/autotest_common.sh@524 -- # print_backtrace
00:03:38.369 15:32:00 -- common/autotest_common.sh@1008 -- # [[ ehxBET =~ e ]]
00:03:38.369 15:32:00 -- common/autotest_common.sh@1010 -- # args=(''\''{ "subsystem": "bdev", "config": [ { "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme0", "traddr":"0000:5e:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme1", "traddr":"0000:5f:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme2", "traddr":"0000:d8:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme3", "traddr":"0000:d9:00.0" } } ] }'\''' '-j' 'load_subsystem_config' 'nvme')
00:03:38.369 15:32:00 -- common/autotest_common.sh@1010 -- # local args
00:03:38.369 15:32:00 -- common/autotest_common.sh@1012 -- # xtrace_disable
00:03:38.369 15:32:00 -- common/autotest_common.sh@14 -- # '[' no '!=' yes ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@15 -- # PREV_BASH_OPTS=ehxBET
00:03:38.369 15:32:00 -- common/autotest_common.sh@16 -- # [[ ehxBET == *\x* ]]
00:03:38.369 15:32:00 -- common/autotest_common.sh@17 -- # XTRACE_DISABLED=yes
00:03:38.369 15:32:00 -- common/autotest_common.sh@19 -- # set +x
00:03:38.369 ========== Backtrace start: ==========
00:03:38.369
00:03:38.369 in /var/jenkins/workspace/nvme-phy-autotest/spdk/test/common/autotest_common.sh:524 -> rpc_cmd(["load_subsystem_config"],["-j"],["'{ "subsystem": "bdev", "config": [ { "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme0", "traddr":"0000:5e:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme1", "traddr":"0000:5f:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme2", "traddr":"0000:d8:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme3", "traddr":"0000:d9:00.0" } } ] }'"])
00:03:38.369 ...
00:03:38.369 519 echo "$rsp"
00:03:38.369 520 done
00:03:38.369 521
00:03:38.369 522 rc=${!status[*]}
00:03:38.369 523 xtrace_restore
00:03:38.369 => 524 [[ $rc == 0 ]]
00:03:38.369 525 }
00:03:38.369 526
00:03:38.369 527 function rpc_cmd_simple_data_json() {
00:03:38.369 528
00:03:38.369 529 local elems="$1[@]" elem
00:03:38.369 ...
00:03:38.369 in test/bdev/blockdev.sh:64 -> setup_nvme_conf([])
00:03:38.369 ...
00:03:38.369 59 }
00:03:38.369 60
00:03:38.369 61 function setup_nvme_conf() {
00:03:38.369 62 local json
00:03:38.369 63 mapfile -t json < <("$rootdir/scripts/gen_nvme.sh")
00:03:38.369 => 64 "$rpc_py" load_subsystem_config -j "'${json[*]}'"
00:03:38.369 65 }
00:03:38.369 66
00:03:38.369 67 function setup_gpt_conf() {
00:03:38.369 68 $rootdir/scripts/setup.sh reset
00:03:38.369 69 get_zoned_devs
00:03:38.369 ...
00:03:38.369 in test/bdev/blockdev.sh:485 -> main(["nvme"])
00:03:38.369 ...
00:03:38.369 480 case "$test_type" in
00:03:38.369 481 bdev)
00:03:38.369 482 setup_bdev_conf
00:03:38.369 483 ;;
00:03:38.369 484 nvme)
00:03:38.369 => 485 setup_nvme_conf
00:03:38.369 486 ;;
00:03:38.369 487 gpt)
00:03:38.369 488 setup_gpt_conf
00:03:38.369 489 ;;
00:03:38.369 490 crypto_aesni)
00:03:38.369 ...
00:03:38.369
00:03:38.369 ========== Backtrace end ==========
00:03:38.369 15:32:00 -- common/autotest_common.sh@1048 -- # xtrace_enable
00:03:38.369 15:32:00 -- common/autotest_common.sh@1049 -- # return 0
00:03:38.369 15:32:00 -- common/autotest_common.sh@1 -- # killprocess 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@832 -- # '[' -z 22451 ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@836 -- # kill -0 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@837 -- # uname
00:03:38.369 15:32:00 -- common/autotest_common.sh@837 -- # '[' Linux = Linux ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@838 -- # ps --no-headers -o comm= 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@838 -- # process_name=reactor_0
00:03:38.369 15:32:00 -- common/autotest_common.sh@842 -- # '[' reactor_0 = sudo ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@850 -- # echo 'killing process with pid 22451'
00:03:38.369 killing process with pid 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@851 -- # kill 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@856 -- # wait 22451
00:31:01.237 Cancelling nested steps due to timeout
00:31:01.241 Sending interrupt signal to process
00:31:16.288 Terminated
00:31:16.299 script returned exit code 143
``` | 1.0 | [blockdev_nvme] Timeout while waiting for spdk_tgt to terminate - # CI Intermittent Failure
Happened on WFP13 which doesn't seem to be stable in general. Disabled the node for the time being.
https://ci.spdk.io/results/autotest-per-patch/builds/82811/archive/nvme-phy-autotest/build.log
```
00:03:31.983 START TEST blockdev_nvme
00:03:31.983 ************************************
00:03:31.983 15:31:54 -- common/autotest_common.sh@979 -- # xtrace_enable
00:03:31.983 15:31:54 -- common/autotest_common.sh@980 -- # test/bdev/blockdev.sh nvme
00:03:31.983 * Looking for test storage...
00:03:31.983 * Found test storage at /var/jenkins/workspace/nvme-phy-autotest/spdk/test/bdev
00:03:31.983 15:31:54 -- common/autotest_common.sh@1524 -- # xtrace_enable
00:03:31.983 15:31:54 -- bdev/blockdev.sh@6 -- # source /var/jenkins/workspace/nvme-phy-autotest/spdk/test/bdev/nbd_common.sh
00:03:31.983 15:31:54 -- bdev/nbd_common.sh@1 -- # set -e
00:03:31.983 15:31:54 -- bdev/blockdev.sh@8 -- # rpc_py=rpc_cmd
00:03:31.983 15:31:54 -- bdev/blockdev.sh@9 -- # conf_file=/var/jenkins/workspace/nvme-phy-autotest/spdk/test/bdev/bdev.json
00:03:31.983 15:31:54 -- bdev/blockdev.sh@11 -- # :
00:03:31.983 15:31:54 -- bdev/blockdev.sh@451 -- # QOS_DEV_1=Malloc_0
00:03:31.983 15:31:54 -- bdev/blockdev.sh@452 -- # QOS_DEV_2=Null_1
00:03:31.983 15:31:54 -- bdev/blockdev.sh@453 -- # QOS_RUN_TIME=5
00:03:31.983 15:31:54 -- bdev/blockdev.sh@455 -- # uname -s
00:03:31.983 15:31:54 -- bdev/blockdev.sh@455 -- # '[' Linux = Linux ']'
00:03:31.983 15:31:54 -- bdev/blockdev.sh@457 -- # PRE_RESERVED_MEM=0
00:03:31.983 15:31:54 -- bdev/blockdev.sh@463 -- # test_type=nvme
00:03:31.983 15:31:54 -- bdev/blockdev.sh@464 -- # crypto_device=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@465 -- # wcs_file=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@466 -- # dek=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@467 -- # env_ctx=
00:03:31.983 15:31:54 -- bdev/blockdev.sh@468 -- # '[' -n '' ']'
00:03:31.983 15:31:54 -- bdev/blockdev.sh@479 -- # start_spdk_tgt
00:03:31.983 15:31:54 -- bdev/blockdev.sh@32 -- # spdk_tgt_pid=22451
00:03:31.983 15:31:54 -- bdev/blockdev.sh@33 -- # trap 'killprocess "$spdk_tgt_pid"; exit 1' SIGINT SIGTERM EXIT
00:03:31.983 15:31:54 -- bdev/blockdev.sh@31 -- # /var/jenkins/workspace/nvme-phy-autotest/spdk/build/bin/spdk_tgt ''
00:03:31.983 15:31:54 -- bdev/blockdev.sh@34 -- # waitforlisten 22451
00:03:31.983 15:31:54 -- common/autotest_common.sh@726 -- # '[' -z 22451 ']'
00:03:31.983 15:31:54 -- common/autotest_common.sh@730 -- # local rpc_addr=/var/tmp/spdk.sock
00:03:31.983 15:31:54 -- common/autotest_common.sh@732 -- # echo 'Waiting for process to start up and listen on UNIX domain socket /var/tmp/spdk.sock...'
00:03:31.983 Waiting for process to start up and listen on UNIX domain socket /var/tmp/spdk.sock...
00:03:31.983 15:31:54 -- common/autotest_common.sh@734 -- # xtrace_disable
00:03:31.983 15:31:54 -- common/autotest_common.sh@14 -- # '[' '' '!=' yes ']'
00:03:31.983 15:31:54 -- common/autotest_common.sh@15 -- # PREV_BASH_OPTS=ehxBET
00:03:31.983 15:31:54 -- common/autotest_common.sh@16 -- # [[ ehxBET == *\x* ]]
00:03:31.984 15:31:54 -- common/autotest_common.sh@17 -- # XTRACE_DISABLED=yes
00:03:31.984 15:31:54 -- common/autotest_common.sh@19 -- # set +x
00:03:31.984 [2022-08-16 15:31:54.312202] Starting SPDK v22.09-pre git sha1 01df76d0f / DPDK 22.03.0 initialization...
00:03:31.984 [2022-08-16 15:31:54.312255] [ DPDK EAL parameters: [2022-08-16 15:31:54.312262] spdk_tgt [2022-08-16 15:31:54.312266] --no-shconf [2022-08-16 15:31:54.312271] -c 0x1 [2022-08-16 15:31:54.312276] --huge-unlink [2022-08-16 15:31:54.312301] --log-level=lib.eal:6 [2022-08-16 15:31:54.312307] --log-level=lib.cryptodev:5 [2022-08-16 15:31:54.312311] --log-level=user1:6 [2022-08-16 15:31:54.312316] --base-virtaddr=0x200000000000 [2022-08-16 15:31:54.312321] --match-allocations [2022-08-16 15:31:54.312325] --file-prefix=spdk_pid22451 [2022-08-16 15:31:54.312330] ]
00:03:31.984 EAL: No free 2048 kB hugepages reported on node 1
00:03:31.984 TELEMETRY: No legacy callbacks, legacy socket not created
00:03:31.984 [2022-08-16 15:31:54.371456] app.c: 586:spdk_app_start: *NOTICE*: Total cores available: 1
00:03:31.984 [2022-08-16 15:31:54.535113] reactor.c: 926:reactor_run: *NOTICE*: Reactor started on core 0
00:03:31.984 [2022-08-16 15:31:54.535231] accel_engine.c:1028:sw_accel_engine_init: *NOTICE*: Accel framework software engine initialized.
00:03:32.244 [2022-08-16 15:31:54.685271] 'OCF Core' volume operations registered
00:03:32.244 [2022-08-16 15:31:54.687900] 'SPDK_block_device' volume operations registered
00:03:32.814 15:31:55 -- common/autotest_common.sh@753 -- # xtrace_enable
00:03:32.814 15:31:55 -- common/autotest_common.sh@754 -- # (( i == 0 ))
00:03:32.814 15:31:55 -- common/autotest_common.sh@758 -- # return 0
00:03:32.814 15:31:55 -- bdev/blockdev.sh@480 -- # case "$test_type" in
00:03:32.814 15:31:55 -- bdev/blockdev.sh@485 -- # setup_nvme_conf
00:03:32.814 15:31:55 -- bdev/blockdev.sh@62 -- # local json
00:03:32.814 15:31:55 -- bdev/blockdev.sh@63 -- # mapfile -t json
00:03:32.814 15:31:55 -- bdev/blockdev.sh@63 -- # /var/jenkins/workspace/nvme-phy-autotest/spdk/scripts/gen_nvme.sh
00:03:32.814 15:31:55 -- bdev/blockdev.sh@64 -- # rpc_cmd load_subsystem_config -j ''\''{ "subsystem": "bdev", "config": [ { "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme0", "traddr":"0000:5e:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme1", "traddr":"0000:5f:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme2", "traddr":"0000:d8:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme3", "traddr":"0000:d9:00.0" } } ] }'\'''
00:03:32.814 15:31:55 -- common/autotest_common.sh@496 -- # xtrace_disable
00:03:32.814 15:31:55 -- common/autotest_common.sh@14 -- # '[' no '!=' yes ']'
00:03:32.814 15:31:55 -- common/autotest_common.sh@15 -- # PREV_BASH_OPTS=ehxBET
00:03:32.814 15:31:55 -- common/autotest_common.sh@16 -- # [[ ehxBET == *\x* ]]
00:03:32.814 15:31:55 -- common/autotest_common.sh@17 -- # XTRACE_DISABLED=yes
00:03:32.814 15:31:55 -- common/autotest_common.sh@19 -- # set +x
00:03:38.369 15:32:00 -- common/autotest_common.sh@523 -- # xtrace_enable
00:03:38.369 15:32:00 -- common/autotest_common.sh@524 -- # [[ '' == 0 ]]
00:03:38.369 15:32:00 -- common/autotest_common.sh@524 -- # trap - ERR
00:03:38.369 15:32:00 -- common/autotest_common.sh@524 -- # print_backtrace
00:03:38.369 15:32:00 -- common/autotest_common.sh@1008 -- # [[ ehxBET =~ e ]]
00:03:38.369 15:32:00 -- common/autotest_common.sh@1010 -- # args=(''\''{ "subsystem": "bdev", "config": [ { "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme0", "traddr":"0000:5e:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme1", "traddr":"0000:5f:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme2", "traddr":"0000:d8:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme3", "traddr":"0000:d9:00.0" } } ] }'\''' '-j' 'load_subsystem_config' 'nvme')
00:03:38.369 15:32:00 -- common/autotest_common.sh@1010 -- # local args
00:03:38.369 15:32:00 -- common/autotest_common.sh@1012 -- # xtrace_disable
00:03:38.369 15:32:00 -- common/autotest_common.sh@14 -- # '[' no '!=' yes ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@15 -- # PREV_BASH_OPTS=ehxBET
00:03:38.369 15:32:00 -- common/autotest_common.sh@16 -- # [[ ehxBET == *\x* ]]
00:03:38.369 15:32:00 -- common/autotest_common.sh@17 -- # XTRACE_DISABLED=yes
00:03:38.369 15:32:00 -- common/autotest_common.sh@19 -- # set +x
00:03:38.369 ========== Backtrace start: ==========
00:03:38.369
00:03:38.369 in /var/jenkins/workspace/nvme-phy-autotest/spdk/test/common/autotest_common.sh:524 -> rpc_cmd(["load_subsystem_config"],["-j"],["'{ "subsystem": "bdev", "config": [ { "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme0", "traddr":"0000:5e:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme1", "traddr":"0000:5f:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme2", "traddr":"0000:d8:00.0" } },{ "method": "bdev_nvme_attach_controller", "params": { "trtype": "PCIe", "name":"Nvme3", "traddr":"0000:d9:00.0" } } ] }'"])
00:03:38.369 ...
00:03:38.369 519 echo "$rsp"
00:03:38.369 520 done
00:03:38.369 521
00:03:38.369 522 rc=${!status[*]}
00:03:38.369 523 xtrace_restore
00:03:38.369 => 524 [[ $rc == 0 ]]
00:03:38.369 525 }
00:03:38.369 526
00:03:38.369 527 function rpc_cmd_simple_data_json() {
00:03:38.369 528
00:03:38.369 529 local elems="$1[@]" elem
00:03:38.369 ...
00:03:38.369 in test/bdev/blockdev.sh:64 -> setup_nvme_conf([])
00:03:38.369 ...
00:03:38.369 59 }
00:03:38.369 60
00:03:38.369 61 function setup_nvme_conf() {
00:03:38.369 62 local json
00:03:38.369 63 mapfile -t json < <("$rootdir/scripts/gen_nvme.sh")
00:03:38.369 => 64 "$rpc_py" load_subsystem_config -j "'${json[*]}'"
00:03:38.369 65 }
00:03:38.369 66
00:03:38.369 67 function setup_gpt_conf() {
00:03:38.369 68 $rootdir/scripts/setup.sh reset
00:03:38.369 69 get_zoned_devs
00:03:38.369 ...
00:03:38.369 in test/bdev/blockdev.sh:485 -> main(["nvme"])
00:03:38.369 ...
00:03:38.369 480 case "$test_type" in
00:03:38.369 481 bdev)
00:03:38.369 482 setup_bdev_conf
00:03:38.369 483 ;;
00:03:38.369 484 nvme)
00:03:38.369 => 485 setup_nvme_conf
00:03:38.369 486 ;;
00:03:38.369 487 gpt)
00:03:38.369 488 setup_gpt_conf
00:03:38.369 489 ;;
00:03:38.369 490 crypto_aesni)
00:03:38.369 ...
00:03:38.369
00:03:38.369 ========== Backtrace end ==========
00:03:38.369 15:32:00 -- common/autotest_common.sh@1048 -- # xtrace_enable
00:03:38.369 15:32:00 -- common/autotest_common.sh@1049 -- # return 0
00:03:38.369 15:32:00 -- common/autotest_common.sh@1 -- # killprocess 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@832 -- # '[' -z 22451 ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@836 -- # kill -0 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@837 -- # uname
00:03:38.369 15:32:00 -- common/autotest_common.sh@837 -- # '[' Linux = Linux ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@838 -- # ps --no-headers -o comm= 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@838 -- # process_name=reactor_0
00:03:38.369 15:32:00 -- common/autotest_common.sh@842 -- # '[' reactor_0 = sudo ']'
00:03:38.369 15:32:00 -- common/autotest_common.sh@850 -- # echo 'killing process with pid 22451'
00:03:38.369 killing process with pid 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@851 -- # kill 22451
00:03:38.369 15:32:00 -- common/autotest_common.sh@856 -- # wait 22451
00:31:01.237 Cancelling nested steps due to timeout
00:31:01.241 Sending interrupt signal to process
00:31:16.288 Terminated
00:31:16.299 script returned exit code 143
``` | infrastructure | timeout while waiting for spdk tgt to terminate ci intermittent failure happened on which doesn t seem to be stable in general disabled the node for the time being start test blockdev nvme common autotest common sh xtrace enable common autotest common sh test bdev blockdev sh nvme looking for test storage found test storage at var jenkins workspace nvme phy autotest spdk test bdev common autotest common sh xtrace enable bdev blockdev sh source var jenkins workspace nvme phy autotest spdk test bdev nbd common sh bdev nbd common sh set e bdev blockdev sh rpc py rpc cmd bdev blockdev sh conf file var jenkins workspace nvme phy autotest spdk test bdev bdev json bdev blockdev sh bdev blockdev sh qos dev malloc bdev blockdev sh qos dev null bdev blockdev sh qos run time bdev blockdev sh uname s bdev blockdev sh bdev blockdev sh pre reserved mem bdev blockdev sh test type nvme bdev blockdev sh crypto device bdev blockdev sh wcs file bdev blockdev sh dek bdev blockdev sh env ctx bdev blockdev sh bdev blockdev sh start spdk tgt bdev blockdev sh spdk tgt pid bdev blockdev sh trap killprocess spdk tgt pid exit sigint sigterm exit bdev blockdev sh var jenkins workspace nvme phy autotest spdk build bin spdk tgt bdev blockdev sh waitforlisten common autotest common sh common autotest common sh local rpc addr var tmp spdk sock common autotest common sh echo waiting for process to start up and listen on unix domain socket var tmp spdk sock waiting for process to start up and listen on unix domain socket var tmp spdk sock common autotest common sh xtrace disable common autotest common sh common autotest common sh prev bash opts ehxbet common autotest common sh common autotest common sh xtrace disabled yes common autotest common sh set x starting spdk pre git dpdk initialization spdk tgt no shconf c huge unlink log level lib eal log level lib cryptodev log level base virtaddr match allocations file prefix spdk eal no free kb hugepages reported on node telemetry no legacy callbacks legacy socket not created app c spdk app start notice total cores available reactor c reactor run notice reactor started on core accel engine c sw accel engine init notice accel framework software engine initialized ocf core volume operations registered spdk block device volume operations registered common autotest common sh xtrace enable common autotest common sh i common autotest common sh return bdev blockdev sh case test type in bdev blockdev sh setup nvme conf bdev blockdev sh local json bdev blockdev sh mapfile t json bdev blockdev sh var jenkins workspace nvme phy autotest spdk scripts gen nvme sh bdev blockdev sh rpc cmd load subsystem config j subsystem bdev config common autotest common sh xtrace disable common autotest common sh common autotest common sh prev bash opts ehxbet common autotest common sh common autotest common sh xtrace disabled yes common autotest common sh set x common autotest common sh xtrace enable common autotest common sh common autotest common sh trap err common autotest common sh print backtrace common autotest common sh common autotest common sh args subsystem bdev config j load subsystem config nvme common autotest common sh local args common autotest common sh xtrace disable common autotest common sh common autotest common sh prev bash opts ehxbet common autotest common sh common autotest common sh xtrace disabled yes common autotest common sh set x backtrace start in var jenkins workspace nvme phy autotest spdk test common autotest common sh rpc cmd echo rsp done rc status xtrace restore function rpc cmd simple data json local elems elem in test bdev blockdev sh setup nvme conf function setup nvme conf local json mapfile t json rootdir scripts gen nvme sh rpc py load subsystem config j json function setup gpt conf rootdir scripts setup sh reset get zoned devs in test bdev blockdev sh main case test type in bdev setup bdev conf nvme setup nvme conf gpt setup gpt conf crypto aesni backtrace end common autotest common sh xtrace enable common autotest common sh return common autotest common sh killprocess common autotest common sh common autotest common sh kill common autotest common sh uname common autotest common sh common autotest common sh ps no headers o comm common autotest common sh process name reactor common autotest common sh common autotest common sh echo killing process with pid killing process with pid common autotest common sh kill common autotest common sh wait cancelling nested steps due to timeout sending interrupt signal to process terminated script returned exit code | 1 |
530,008 | 15,414,845,061 | IssuesEvent | 2021-03-05 01:12:02 | bloom-housing/bloom | https://api.github.com/repos/bloom-housing/bloom | closed | Partners app: a page reload wipes out login state, must sign in again | High Priority bug | After merging in #966, the page navigation is working in an SPA sort of way, but if I do a browser refresh (select the URL bar and hit enter, or press cmd-R, etc.), my login state is wiped out and I'm brought back to the Sign In page. Going back to a previously working URL just kicks me back to Sign In. | 1.0 | Partners app: a page reload wipes out login state, must sign in again - After merging in #966, the page navigation is working in an SPA sort of way, but if I do a browser refresh (select the URL bar and hit enter, or press cmd-R, etc.), my login state is wiped out and I'm brought back to the Sign In page. Going back to a previously working URL just kicks me back to Sign In. | non_infrastructure | partners app a page reload wipes out login state must sign in again after merging in the page navigation is working in an spa sort of way but if i do a browser refresh select the url bar and hit enter or press cmd r etc my login state is wiped out and i m brought back to the sign in page going back to a previously working url just kicks me back to sign in | 0 |
23,317 | 16,061,624,525 | IssuesEvent | 2021-04-23 13:21:02 | wooller/giulia-website | https://api.github.com/repos/wooller/giulia-website | opened | Set up netlify build and publish based on Stripe changes | enhancement infrastructure | If we archive a product on stripe it should automatically trigger netlify to rebuild the gatsby app. | 1.0 | Set up netlify build and publish based on Stripe changes - If we archive a product on stripe it should automatically trigger netlify to rebuild the gatsby app. | infrastructure | set up netlify build and publish based on stripe changes if we archive a product on stripe it should automatically trigger netlify to rebuild the gatsby app | 1 |
4,314 | 4,972,700,875 | IssuesEvent | 2016-12-05 22:20:33 | dotnet/wcf | https://api.github.com/repos/dotnet/wcf | closed | Use TestProperties and to parse command line arguments to configure ports | Infrastructure | Pull request https://github.com/dotnet/wcf/pull/1011 recommended using TestProperties and to parse command line arguments to configure ports for self hosted service.
We need to evaluate if it's needed to configure ports as there is a debate to use the same port IIS uses.
| 1.0 | Use TestProperties and to parse command line arguments to configure ports - Pull request https://github.com/dotnet/wcf/pull/1011 recommended using TestProperties and to parse command line arguments to configure ports for self hosted service.
We need to evaluate if it's needed to configure ports as there is a debate to use the same port IIS uses.
| infrastructure | use testproperties and to parse command line arguments to configure ports pull request recommended using testproperties and to parse command line arguments to configure ports for self hosted service we need to evaluate if it s needed to configure ports as there is a debate to use the same port iis uses | 1 |
63,566 | 3,197,002,535 | IssuesEvent | 2015-10-01 00:21:55 | fusioninventory/fusioninventory-for-glpi | https://api.github.com/repos/fusioninventory/fusioninventory-for-glpi | closed | display "SELinux..." when display page to force run agent remotely from server | Category: Communication Component: For junior contributor Component: Found in version Priority: High Status: Closed Tracker: Bug | ---
Author Name: **Piotr Kuchciak** (Piotr Kuchciak)
Original Redmine Issue: 2871, http://forge.fusioninventory.org/issues/2871
Original Date: 2015-02-06
Original Assignee: David Durieux
---
I have install GLPI 0.85.3 on Ubuntu 14.04 and when Agent check to my GLPI then i click in Fusin Agent INVENTORY NOW i have a status: SELinux problem, do 'setsebool -P httpd_can_network_connect on'
| 1.0 | display "SELinux..." when display page to force run agent remotely from server - ---
Author Name: **Piotr Kuchciak** (Piotr Kuchciak)
Original Redmine Issue: 2871, http://forge.fusioninventory.org/issues/2871
Original Date: 2015-02-06
Original Assignee: David Durieux
---
I have install GLPI 0.85.3 on Ubuntu 14.04 and when Agent check to my GLPI then i click in Fusin Agent INVENTORY NOW i have a status: SELinux problem, do 'setsebool -P httpd_can_network_connect on'
| non_infrastructure | display selinux when display page to force run agent remotely from server author name piotr kuchciak piotr kuchciak original redmine issue original date original assignee david durieux i have install glpi on ubuntu and when agent check to my glpi then i click in fusin agent inventory now i have a status selinux problem do setsebool p httpd can network connect on | 0 |
180,397 | 6,649,316,702 | IssuesEvent | 2017-09-28 12:49:52 | herbiehp/unicenta | https://api.github.com/repos/herbiehp/unicenta | closed | Fix JRE Detection Routine in Setup | 3-Medium Priority enhancement | Setup does not detect JRE 8u25 (and probably other JRE 8 versions) properly and throws an error messages. Not a good start for a new user.
To reproduce the issue:
On a clean Window 7 x64 PC
Install jre-8u25-windows-x64.exe
Check Java
_C:\Users\MMason>set path
Path=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
C:>
C:>java -version
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
C:>_
Installed unicentaopos-3.81-windows-installer.exe
Click OK
browser window opens up to http://www.java.com/en/ and
Click OK
Normal setup screen appears
| 1.0 | Fix JRE Detection Routine in Setup - Setup does not detect JRE 8u25 (and probably other JRE 8 versions) properly and throws an error messages. Not a good start for a new user.
To reproduce the issue:
On a clean Window 7 x64 PC
Install jre-8u25-windows-x64.exe
Check Java
_C:\Users\MMason>set path
Path=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
C:>
C:>java -version
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
C:>_
Installed unicentaopos-3.81-windows-installer.exe
Click OK
browser window opens up to http://www.java.com/en/ and
Click OK
Normal setup screen appears
| non_infrastructure | fix jre detection routine in setup setup does not detect jre and probably other jre versions properly and throws an error messages not a good start for a new user to reproduce the issue on a clean window pc install jre windows exe check java c users mmason set path path c programdata oracle java javapath c windows c windows c windows wbem c windows windowspowershell pathext com exe bat cmd vbs vbe js jse wsf wsh msc c c java version java version java tm se runtime environment build java hotspot tm bit server vm build mixed mode c installed unicentaopos windows installer exe click ok browser window opens up to and click ok normal setup screen appears | 0 |
8,975 | 3,813,794,323 | IssuesEvent | 2016-03-28 08:33:51 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | Invalid security token after update from joomla 3.4.8 to joomla 3.5 | No Code Attached Yet | #### Steps to reproduce the issue
Update from joomla 3.4.8 to joomla 3.5.
#### Expected result
Users can login from frontend without problems.
#### Actual result
After they try to login, users take the message:
"The most recent request was denied because it contained an invalid security token. Please refresh the page and try again."
#### System information (as much as possible)
PHP Built On Windows 8
Database Version 5.6.24
Database Collation latin1_swedish_ci
Database Connection Collation utf8mb4_general_ci
PHP Version 5.6.8
Web Server Apache/2.4.12 (Win32) OpenSSL/1.0.1l PHP/5.6.8
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.5.0 Stable [ Unicorn ] 21-March-2016 22:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
#### Additional comments
I update 4 off sites to joomla 3.5 and 2 off them have "invalid Token" issue on frontend login.
Some times users can login on frontend without issues, but if they logout and try to login again they face the same issue. Sometimes even on 3rd login/logout time, but the problem is still there.
| 1.0 | Invalid security token after update from joomla 3.4.8 to joomla 3.5 - #### Steps to reproduce the issue
Update from joomla 3.4.8 to joomla 3.5.
#### Expected result
Users can login from frontend without problems.
#### Actual result
After they try to login, users take the message:
"The most recent request was denied because it contained an invalid security token. Please refresh the page and try again."
#### System information (as much as possible)
PHP Built On Windows 8
Database Version 5.6.24
Database Collation latin1_swedish_ci
Database Connection Collation utf8mb4_general_ci
PHP Version 5.6.8
Web Server Apache/2.4.12 (Win32) OpenSSL/1.0.1l PHP/5.6.8
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.5.0 Stable [ Unicorn ] 21-March-2016 22:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
#### Additional comments
I update 4 off sites to joomla 3.5 and 2 off them have "invalid Token" issue on frontend login.
Some times users can login on frontend without issues, but if they logout and try to login again they face the same issue. Sometimes even on 3rd login/logout time, but the problem is still there.
| non_infrastructure | invalid security token after update from joomla to joomla steps to reproduce the issue update from joomla to joomla expected result users can login from frontend without problems actual result after they try to login users take the message the most recent request was denied because it contained an invalid security token please refresh the page and try again system information as much as possible php built on windows database version database collation swedish ci database connection collation general ci php version web server apache openssl php webserver to php interface joomla version joomla stable march gmt joomla platform version joomla platform stable apr gmt user agent mozilla windows nt rv gecko firefox additional comments i update off sites to joomla and off them have invalid token issue on frontend login some times users can login on frontend without issues but if they logout and try to login again they face the same issue sometimes even on login logout time but the problem is still there | 0 |
121,668 | 16,013,736,454 | IssuesEvent | 2021-04-20 13:47:44 | microsoft/WindowsTemplateStudio | https://api.github.com/repos/microsoft/WindowsTemplateStudio | closed | Need official designs for deprecation flags | Can Close Out Soon Wizard design-review | #3809 adds the ability to add "flags" to the frameworks that are being deprecated with the introduction of templates using the MVVM Toolkit.
The implemented designs are purely a placeholder.
This new UI should be reviewed and appropriately adjusted accordingly.
_This is a follow-on from #3753_ | 1.0 | Need official designs for deprecation flags - #3809 adds the ability to add "flags" to the frameworks that are being deprecated with the introduction of templates using the MVVM Toolkit.
The implemented designs are purely a placeholder.
This new UI should be reviewed and appropriately adjusted accordingly.
_This is a follow-on from #3753_ | non_infrastructure | need official designs for deprecation flags adds the ability to add flags to the frameworks that are being deprecated with the introduction of templates using the mvvm toolkit the implemented designs are purely a placeholder this new ui should be reviewed and appropriately adjusted accordingly this is a follow on from | 0 |
608,671 | 18,845,576,672 | IssuesEvent | 2021-11-11 14:37:17 | knative/docs | https://api.github.com/repos/knative/docs | closed | [1.0] Prepare Eventing | priority/high kind/eventing kind/cleanup Epic Developer guide | Eventing is preparing to become 1.0 ready. This is a parent issue to track that work.
| 1.0 | [1.0] Prepare Eventing - Eventing is preparing to become 1.0 ready. This is a parent issue to track that work.
| non_infrastructure | prepare eventing eventing is preparing to become ready this is a parent issue to track that work | 0 |
19,674 | 11,271,328,732 | IssuesEvent | 2020-01-14 12:50:07 | edgexfoundry/edgex-go | https://api.github.com/repos/edgexfoundry/edgex-go | closed | Run error of duplicate key in database | bug core-services | Hello,
I have taken the latest code and build it. When i execute make run command, my services fail with the following error logs
level=ERROR ts=2020-01-13T06:38:03.244007168Z app=edgex-support-scheduler source=init.go:63 msg="**Failed to load schedules and events E11000 duplicate key error collection: scheduler.intervalAction index: slug_1 dup key: { : null** }"**
level=INFO ts=2020-01-13T06:38:03.334310287Z app=edgex-core-data source=message.go:58 msg="Service started in: 720.293355ms"
level=INFO ts=2020-01-13T06:38:03.334690649Z app=edgex-support-scheduler source=database.go:155 msg="**Database disconnected"**
Can you please let me the cause and how can i remove the error. I have freshly installed the mongodb and instance of it is running.
| 1.0 | Run error of duplicate key in database - Hello,
I have taken the latest code and build it. When i execute make run command, my services fail with the following error logs
level=ERROR ts=2020-01-13T06:38:03.244007168Z app=edgex-support-scheduler source=init.go:63 msg="**Failed to load schedules and events E11000 duplicate key error collection: scheduler.intervalAction index: slug_1 dup key: { : null** }"**
level=INFO ts=2020-01-13T06:38:03.334310287Z app=edgex-core-data source=message.go:58 msg="Service started in: 720.293355ms"
level=INFO ts=2020-01-13T06:38:03.334690649Z app=edgex-support-scheduler source=database.go:155 msg="**Database disconnected"**
Can you please let me the cause and how can i remove the error. I have freshly installed the mongodb and instance of it is running.
| non_infrastructure | run error of duplicate key in database hello i have taken the latest code and build it when i execute make run command my services fail with the following error logs level error ts app edgex support scheduler source init go msg failed to load schedules and events duplicate key error collection scheduler intervalaction index slug dup key null level info ts app edgex core data source message go msg service started in level info ts app edgex support scheduler source database go msg database disconnected can you please let me the cause and how can i remove the error i have freshly installed the mongodb and instance of it is running | 0 |
131,351 | 10,693,141,865 | IssuesEvent | 2019-10-23 08:14:18 | a2000-erp-team/WEBERP | https://api.github.com/repos/a2000-erp-team/WEBERP | closed | PROCUREMENT-Order Processing-Supplier Bills-Invoice on PO-Additional Transaction Detail. GST amount showing wrong. | WEB ERP Testing By Katrina | Scenario:
-Enter line item in SE, 10 qty @ S$10 with 7% GST exclusive. Hence, GST is S$7.00 (S$100*7%). But GST on additional line item shows 700.
 | 1.0 | PROCUREMENT-Order Processing-Supplier Bills-Invoice on PO-Additional Transaction Detail. GST amount showing wrong. - Scenario:
-Enter line item in SE, 10 qty @ S$10 with 7% GST exclusive. Hence, GST is S$7.00 (S$100*7%). But GST on additional line item shows 700.
 | non_infrastructure | procurement order processing supplier bills invoice on po additional transaction detail gst amount showing wrong scenario enter line item in se qty s with gst exclusive hence gst is s s but gst on additional line item shows | 0 |
21,653 | 14,698,301,179 | IssuesEvent | 2021-01-04 06:06:55 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | closed | Radiation graphs in weather UI seem to be broken | bug interface/infrastructure | All radiation graphs in any validation file appear to be broken.
Graph X axis becomes nonsense, especially if the graph is changed to later years in the met file | 1.0 | Radiation graphs in weather UI seem to be broken - All radiation graphs in any validation file appear to be broken.
Graph X axis becomes nonsense, especially if the graph is changed to later years in the met file | infrastructure | radiation graphs in weather ui seem to be broken all radiation graphs in any validation file appear to be broken graph x axis becomes nonsense especially if the graph is changed to later years in the met file | 1 |
7,968 | 7,166,552,709 | IssuesEvent | 2018-01-29 17:35:01 | dotnet/coreclr | https://api.github.com/repos/dotnet/coreclr | closed | [Win/IPv6] Local build fails with server timeouts during build tools initialization | FollowingUp area-Infrastructure question | For a couple of hours I am blocked by inability to build coreclr locally. The error I am getting is as follows:
```
e:\src\ms\dotnet\coreclr>call "e:\src\ms\dotnet\coreclr\Tools\dotnetcli\dotnet.exe" restore "e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj" --source https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json --source https://api.nuget.org/v3/index.json --packages "e:\src\ms\dotnet\coreclr\Tools\."
Restoring packages for e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj...
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microbuild.core/index.json'.
An error occurred while sending the request.
The operation timed out
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microsoft.net.compilers/index.json'.
An error occurred while sending the request.
The operation timed out
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microbuild.core/index.json'.
An error occurred while sending the request.
The operation timed out
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microsoft.net.compilers/index.json'.
An error occurred while sending the request.
The operation timed out
C:\Program Files\dotnet\sdk\2.1.4\NuGet.targets(103,5): error : Failed to retrieve information about 'Microsoft.Net.Compilers' from remote source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microsoft.net.compilers/index.json'. [e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj]
C:\Program Files\dotnet\sdk\2.1.4\NuGet.targets(103,5): error : An error occurred while sending the request. [e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj]
C:\Program Files\dotnet\sdk\2.1.4\NuGet.targets(103,5): error : The operation timed out [e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj]
e:\src\ms\dotnet\coreclr>set RESTORE_PORTABLETARGETS_ERROR_LEVEL=1
ERROR: An error ocurred when running: '"e:\src\ms\dotnet\coreclr\Tools\dotnetcli\dotnet.exe" restore "e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj"'. Please check above for more details.
BUILD: Laying out dynamically generated files consumed by the native build system
BUILD: Laying out dynamically generated Event test files and etmdummy stub functions
Generating Dummy Event Headers
Generating Event Headers
BUILD: Laying out dynamically generated EventPipe Implementation
BUILD: Laying out ETW event logging interface
BUILD: Commencing build of native components for Windows_NT.x64.Checked
BUILD: Using environment: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\\..\..\VC\Auxiliary\Build\vcvarsall.bat" x86_amd64
``` | 1.0 | [Win/IPv6] Local build fails with server timeouts during build tools initialization - For a couple of hours I am blocked by inability to build coreclr locally. The error I am getting is as follows:
```
e:\src\ms\dotnet\coreclr>call "e:\src\ms\dotnet\coreclr\Tools\dotnetcli\dotnet.exe" restore "e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj" --source https://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json --source https://api.nuget.org/v3/index.json --packages "e:\src\ms\dotnet\coreclr\Tools\."
Restoring packages for e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj...
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microbuild.core/index.json'.
An error occurred while sending the request.
The operation timed out
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microsoft.net.compilers/index.json'.
An error occurred while sending the request.
The operation timed out
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microbuild.core/index.json'.
An error occurred while sending the request.
The operation timed out
Retrying 'FindPackagesByIdAsync' for source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microsoft.net.compilers/index.json'.
An error occurred while sending the request.
The operation timed out
C:\Program Files\dotnet\sdk\2.1.4\NuGet.targets(103,5): error : Failed to retrieve information about 'Microsoft.Net.Compilers' from remote source 'https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-buildtools/nuget/v3/flatcontainer/microsoft.net.compilers/index.json'. [e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj]
C:\Program Files\dotnet\sdk\2.1.4\NuGet.targets(103,5): error : An error occurred while sending the request. [e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj]
C:\Program Files\dotnet\sdk\2.1.4\NuGet.targets(103,5): error : The operation timed out [e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj]
e:\src\ms\dotnet\coreclr>set RESTORE_PORTABLETARGETS_ERROR_LEVEL=1
ERROR: An error ocurred when running: '"e:\src\ms\dotnet\coreclr\Tools\dotnetcli\dotnet.exe" restore "e:\src\ms\dotnet\coreclr\Tools\generated\project.csproj"'. Please check above for more details.
BUILD: Laying out dynamically generated files consumed by the native build system
BUILD: Laying out dynamically generated Event test files and etmdummy stub functions
Generating Dummy Event Headers
Generating Event Headers
BUILD: Laying out dynamically generated EventPipe Implementation
BUILD: Laying out ETW event logging interface
BUILD: Commencing build of native components for Windows_NT.x64.Checked
BUILD: Using environment: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\\..\..\VC\Auxiliary\Build\vcvarsall.bat" x86_amd64
``` | infrastructure | local build fails with server timeouts during build tools initialization for a couple of hours i am blocked by inability to build coreclr locally the error i am getting is as follows e src ms dotnet coreclr call e src ms dotnet coreclr tools dotnetcli dotnet exe restore e src ms dotnet coreclr tools generated project csproj source source packages e src ms dotnet coreclr tools restoring packages for e src ms dotnet coreclr tools generated project csproj retrying findpackagesbyidasync for source an error occurred while sending the request the operation timed out retrying findpackagesbyidasync for source an error occurred while sending the request the operation timed out retrying findpackagesbyidasync for source an error occurred while sending the request the operation timed out retrying findpackagesbyidasync for source an error occurred while sending the request the operation timed out c program files dotnet sdk nuget targets error failed to retrieve information about microsoft net compilers from remote source c program files dotnet sdk nuget targets error an error occurred while sending the request c program files dotnet sdk nuget targets error the operation timed out e src ms dotnet coreclr set restore portabletargets error level error an error ocurred when running e src ms dotnet coreclr tools dotnetcli dotnet exe restore e src ms dotnet coreclr tools generated project csproj please check above for more details build laying out dynamically generated files consumed by the native build system build laying out dynamically generated event test files and etmdummy stub functions generating dummy event headers generating event headers build laying out dynamically generated eventpipe implementation build laying out etw event logging interface build commencing build of native components for windows nt checked build using environment c program files microsoft visual studio community tools vc auxiliary build vcvarsall bat | 1 |
57,448 | 24,120,858,450 | IssuesEvent | 2022-09-20 18:34:21 | googleapis/nodejs-service-directory | https://api.github.com/repos/googleapis/nodejs-service-directory | closed | Service Directory Quickstart: should run quickstart.js failed | type: bug priority: p1 api: servicedirectory flakybot: issue | This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 5c897813076a08f2a2eb899cc05c71eb04ef87a6
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/40e2e2bd-b0f9-4af4-bcba-5ee2858c7b37), [Sponge](http://sponge2/40e2e2bd-b0f9-4af4-bcba-5ee2858c7b37)
status: failed
<details><summary>Test output</summary><br><pre>Unspecified AssertionError
AssertionError: Unspecified AssertionError
at Context.<anonymous> (test/quickstart.test.js:36:5)
at processImmediate (internal/timers.js:461:21)</pre></details> | 1.0 | Service Directory Quickstart: should run quickstart.js failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 5c897813076a08f2a2eb899cc05c71eb04ef87a6
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/40e2e2bd-b0f9-4af4-bcba-5ee2858c7b37), [Sponge](http://sponge2/40e2e2bd-b0f9-4af4-bcba-5ee2858c7b37)
status: failed
<details><summary>Test output</summary><br><pre>Unspecified AssertionError
AssertionError: Unspecified AssertionError
at Context.<anonymous> (test/quickstart.test.js:36:5)
at processImmediate (internal/timers.js:461:21)</pre></details> | non_infrastructure | service directory quickstart should run quickstart js failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output unspecified assertionerror assertionerror unspecified assertionerror at context test quickstart test js at processimmediate internal timers js | 0 |
23,834 | 4,996,132,337 | IssuesEvent | 2016-12-09 12:46:56 | TechnionYP5777/SmartCity-Elderly-Support | https://api.github.com/repos/TechnionYP5777/SmartCity-Elderly-Support | closed | Add a wiki page about the JavaFX library | Documentation | The wiki page will present the library, its uses and how to construct a functional GUI using the library. | 1.0 | Add a wiki page about the JavaFX library - The wiki page will present the library, its uses and how to construct a functional GUI using the library. | non_infrastructure | add a wiki page about the javafx library the wiki page will present the library its uses and how to construct a functional gui using the library | 0 |
17,008 | 12,192,764,791 | IssuesEvent | 2020-04-29 13:27:22 | ansible/galaxy_ng | https://api.github.com/repos/ansible/galaxy_ng | closed | Importer ansible tool issues in containers | area/importer area/infrastructure priority/high status/fix-released type/bug | ### Bug Report
##### SUMMARY
Running galaxy-importer under galaxy_ng setup has some issues with the container setup, resulting in importer errors, and the following needs to be resolved:
- Bump galaxy-importer version to `0.2.0` to capture role descriptions #102
- Add ansible tmp directory that is writable in container #99 #107
- Bump ansible version to `2.9.7` to avoid container `getpwuid(): uid not found` errors
| 1.0 | Importer ansible tool issues in containers - ### Bug Report
##### SUMMARY
Running galaxy-importer under galaxy_ng setup has some issues with the container setup, resulting in importer errors, and the following needs to be resolved:
- Bump galaxy-importer version to `0.2.0` to capture role descriptions #102
- Add ansible tmp directory that is writable in container #99 #107
- Bump ansible version to `2.9.7` to avoid container `getpwuid(): uid not found` errors
| infrastructure | importer ansible tool issues in containers bug report summary running galaxy importer under galaxy ng setup has some issues with the container setup resulting in importer errors and the following needs to be resolved bump galaxy importer version to to capture role descriptions add ansible tmp directory that is writable in container bump ansible version to to avoid container getpwuid uid not found errors | 1 |
53,378 | 11,045,972,264 | IssuesEvent | 2019-12-09 16:02:17 | WoodyJang/WoodyJang.github.io | https://api.github.com/repos/WoodyJang/WoodyJang.github.io | opened | leetcode-[14] 最长公共前缀 | leetcode | ```js
var longestCommonPrefix = function(strs) {
if (strs.length == 0)
return ""
for (let i = 0; i < strs[0].length;i++){
for (let j = 1; j < strs.length;j++){
if (strs[j][i] != strs[0][i])
return strs[0].slice(0, i)
}
}
return strs[0]
};
``` | 1.0 | leetcode-[14] 最长公共前缀 - ```js
var longestCommonPrefix = function(strs) {
if (strs.length == 0)
return ""
for (let i = 0; i < strs[0].length;i++){
for (let j = 1; j < strs.length;j++){
if (strs[j][i] != strs[0][i])
return strs[0].slice(0, i)
}
}
return strs[0]
};
``` | non_infrastructure | leetcode 最长公共前缀 js var longestcommonprefix function strs if strs length return for let i i strs length i for let j j strs length j if strs strs return strs slice i return strs | 0 |
31,140 | 25,358,697,319 | IssuesEvent | 2022-11-20 16:45:39 | servo/servo | https://api.github.com/repos/servo/servo | closed | Consider triggering WPT sync nightly job from servo-wpt-sync account | A-infrastructure | @jdm I found it seems it's not so easy to setup the environment to git push from `servo/servo` to `servo-wpt-sync/servo` from https://github.com/servo/servo/pull/28369.
So, I wonder if it's possible to have a repo (or just the servo repo) under `servo-wpt-sync` account; then, we setup a nightly cronjob in `servo-wpt-sync`'s repo to do this nightly sync. But, we will need a nightly branch and make it as the default branch because currently GitHub Actions only support running cronjob on **default** branch. (or, should we give `servo-wpt-sync` permission to create branches to `servo/servo`?)
Also, I'm wondering if we should create a secret for `servo-wpt-sync`'s GPG key so that we can make sure its commit is verified 🤔
If this solution sounds plausible, I think the patch of `--always-succeed` for `python/servo/testing_commands.py` in #28369 should be merged into this repo (`servo/servo`) so that we can avoid throwing exit 1 while executing the command in downstream.
_Originally posted by @CYBAI in https://github.com/servo/servo/issues/28592#issuecomment-914378537_ | 1.0 | Consider triggering WPT sync nightly job from servo-wpt-sync account - @jdm I found it seems it's not so easy to setup the environment to git push from `servo/servo` to `servo-wpt-sync/servo` from https://github.com/servo/servo/pull/28369.
So, I wonder if it's possible to have a repo (or just the servo repo) under `servo-wpt-sync` account; then, we setup a nightly cronjob in `servo-wpt-sync`'s repo to do this nightly sync. But, we will need a nightly branch and make it as the default branch because currently GitHub Actions only support running cronjob on **default** branch. (or, should we give `servo-wpt-sync` permission to create branches to `servo/servo`?)
Also, I'm wondering if we should create a secret for `servo-wpt-sync`'s GPG key so that we can make sure its commit is verified 🤔
If this solution sounds plausible, I think the patch of `--always-succeed` for `python/servo/testing_commands.py` in #28369 should be merged into this repo (`servo/servo`) so that we can avoid throwing exit 1 while executing the command in downstream.
_Originally posted by @CYBAI in https://github.com/servo/servo/issues/28592#issuecomment-914378537_ | infrastructure | consider triggering wpt sync nightly job from servo wpt sync account jdm i found it seems it s not so easy to setup the environment to git push from servo servo to servo wpt sync servo from so i wonder if it s possible to have a repo or just the servo repo under servo wpt sync account then we setup a nightly cronjob in servo wpt sync s repo to do this nightly sync but we will need a nightly branch and make it as the default branch because currently github actions only support running cronjob on default branch or should we give servo wpt sync permission to create branches to servo servo also i m wondering if we should create a secret for servo wpt sync s gpg key so that we can make sure its commit is verified 🤔 if this solution sounds plausible i think the patch of always succeed for python servo testing commands py in should be merged into this repo servo servo so that we can avoid throwing exit while executing the command in downstream originally posted by cybai in | 1 |
26,376 | 20,029,940,825 | IssuesEvent | 2022-02-02 03:40:08 | dart-lang/site-www | https://api.github.com/repos/dart-lang/site-www | closed | sitemap.xml contains a bunch of `/index` pages | enhancement infrastructure p2-medium e1-hours | ### Describe the problem
See https://dart.dev/sitemap.xml
Search for `/index<`
### Expected fix
Remove these. They redirect to the right file, but we should just give the right link in our sitemap!
Should just point to the actual file.
### Additional context
Seems we've had this issue before - https://github.com/dart-lang/site-www/issues/933 | 1.0 | sitemap.xml contains a bunch of `/index` pages - ### Describe the problem
See https://dart.dev/sitemap.xml
Search for `/index<`
### Expected fix
Remove these. They redirect to the right file, but we should just give the right link in our sitemap!
Should just point to the actual file.
### Additional context
Seems we've had this issue before - https://github.com/dart-lang/site-www/issues/933 | infrastructure | sitemap xml contains a bunch of index pages describe the problem see search for index expected fix remove these they redirect to the right file but we should just give the right link in our sitemap should just point to the actual file additional context seems we ve had this issue before | 1 |
13,677 | 10,420,220,360 | IssuesEvent | 2019-09-15 22:33:02 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | closed | Graph filters don't work | bug interface/infrastructure | The row filter in the graph is currently ignored if the graph is not under an experiment. | 1.0 | Graph filters don't work - The row filter in the graph is currently ignored if the graph is not under an experiment. | infrastructure | graph filters don t work the row filter in the graph is currently ignored if the graph is not under an experiment | 1 |
33,486 | 27,500,573,714 | IssuesEvent | 2023-03-05 16:50:59 | bootstrapworld/curriculum | https://api.github.com/repos/bootstrapworld/curriculum | closed | Need a warning to prevent duplicate workbook pages | Infrastructure | There have been a few instances where an author uses the @opt-printable directive for a workbook page, and then ALSO lists that same adoc file in workbook-pages.txt.
This results in optional pages appearing in the printed workbook, which is not what we want!
Can we have a warning appear when authors make this mistake? | 1.0 | Need a warning to prevent duplicate workbook pages - There have been a few instances where an author uses the @opt-printable directive for a workbook page, and then ALSO lists that same adoc file in workbook-pages.txt.
This results in optional pages appearing in the printed workbook, which is not what we want!
Can we have a warning appear when authors make this mistake? | infrastructure | need a warning to prevent duplicate workbook pages there have been a few instances where an author uses the opt printable directive for a workbook page and then also lists that same adoc file in workbook pages txt this results in optional pages appearing in the printed workbook which is not what we want can we have a warning appear when authors make this mistake | 1 |
33,084 | 27,212,428,699 | IssuesEvent | 2023-02-20 17:44:24 | servo/servo | https://api.github.com/repos/servo/servo | closed | Please make a release of selectors which already has cssparser 0.29 | A-infrastructure | The cssparser crate made an API break for 0.29, with the removal of the `AtRuleType` enum. `selectors` is already updated for this. Could we please have a release? I'd like to update both crates in librsvg :smiley: | 1.0 | Please make a release of selectors which already has cssparser 0.29 - The cssparser crate made an API break for 0.29, with the removal of the `AtRuleType` enum. `selectors` is already updated for this. Could we please have a release? I'd like to update both crates in librsvg :smiley: | infrastructure | please make a release of selectors which already has cssparser the cssparser crate made an api break for with the removal of the atruletype enum selectors is already updated for this could we please have a release i d like to update both crates in librsvg smiley | 1 |
25,005 | 18,024,471,621 | IssuesEvent | 2021-09-17 01:21:20 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | opened | Build failed: Validate-DotNet/main real signed, .NET 6, validation-aspnetcore-.NET 6, aspnetcore #aspnetcore-109146-.NET6 | area-infrastructure | Build [#aspnetcore-109146-.NET6](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=1367228) failed
## :x: : internal / Validate-DotNet failed
### Summary
**Finished** - Fri, 17 Sep 2021 01:21:05 GMT
**Duration** - 135 minutes
**Requested for** - DotNet Bot
**Reason** - manual
### Details
#### Validation Ring
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/123) - NugetConfigAnalysis task timed out while executing.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/169) - Git fetch failed with exit code 128, back off 7.058 seconds before retry.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/169) - Git fetch failed with exit code 128, back off 2.781 seconds before retry.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/190) - File upload failed even after retry.
#### Required Validation Ring
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Git fetch failed with exit code 128, back off 6.349 seconds before retry.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Git fetch failed with exit code 128, back off 6.979 seconds before retry.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Failed to publish telemetry data. Error A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Failed to publish telemetry data. Error A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/138) - NugetConfigAnalysis task timed out while executing.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/139) - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - (NETCORE_ENGINEERING_TELEMETRY=ReleaseStaging-Product) manifest: Invalid path D:\workspace\_work\1\a\manifests.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - (NETCORE_ENGINEERING_TELEMETRY=ReleaseStaging-Product) packages: D:\workspace\_work\1\a\signed does not have any files with file name *.nupkg.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - (NETCORE_ENGINEERING_TELEMETRY=ReleaseStaging-Product) Contract was not validated.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - PowerShell exited with code '1'.
#### Source Code Validation
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/99) - (NETCORE_ENGINEERING_TELEMETRY=Sdl) Last command failed with exit code 1.
### Changes
| 1.0 | Build failed: Validate-DotNet/main real signed, .NET 6, validation-aspnetcore-.NET 6, aspnetcore #aspnetcore-109146-.NET6 - Build [#aspnetcore-109146-.NET6](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_build/results?buildId=1367228) failed
## :x: : internal / Validate-DotNet failed
### Summary
**Finished** - Fri, 17 Sep 2021 01:21:05 GMT
**Duration** - 135 minutes
**Requested for** - DotNet Bot
**Reason** - manual
### Details
#### Validation Ring
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/123) - NugetConfigAnalysis task timed out while executing.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/169) - Git fetch failed with exit code 128, back off 7.058 seconds before retry.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/169) - Git fetch failed with exit code 128, back off 2.781 seconds before retry.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/190) - File upload failed even after retry.
#### Required Validation Ring
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Git fetch failed with exit code 128, back off 6.349 seconds before retry.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Git fetch failed with exit code 128, back off 6.979 seconds before retry.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Failed to publish telemetry data. Error A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/137) - Failed to publish telemetry data. Error A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
- :warning: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/138) - NugetConfigAnalysis task timed out while executing.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/139) - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - (NETCORE_ENGINEERING_TELEMETRY=ReleaseStaging-Product) manifest: Invalid path D:\workspace\_work\1\a\manifests.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - (NETCORE_ENGINEERING_TELEMETRY=ReleaseStaging-Product) packages: D:\workspace\_work\1\a\signed does not have any files with file name *.nupkg.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - (NETCORE_ENGINEERING_TELEMETRY=ReleaseStaging-Product) Contract was not validated.
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/140) - PowerShell exited with code '1'.
#### Source Code Validation
- :x: - [[Log]](https://dev.azure.com/dnceng/7ea9116e-9fac-403d-b258-b31fcf1bb293/_apis/build/builds/1367228/logs/99) - (NETCORE_ENGINEERING_TELEMETRY=Sdl) Last command failed with exit code 1.
### Changes
| infrastructure | build failed validate dotnet main real signed net validation aspnetcore net aspnetcore aspnetcore build failed x internal validate dotnet failed summary finished fri sep gmt duration minutes requested for dotnet bot reason manual details validation ring warning nugetconfiganalysis task timed out while executing warning git fetch failed with exit code back off seconds before retry warning git fetch failed with exit code back off seconds before retry x file upload failed even after retry required validation ring warning git fetch failed with exit code back off seconds before retry warning git fetch failed with exit code back off seconds before retry warning failed to publish telemetry data error a connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond warning failed to publish telemetry data error a connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond warning nugetconfiganalysis task timed out while executing x a connection attempt failed because the connected party did not properly respond after a period of time or established connection failed because connected host has failed to respond x netcore engineering telemetry releasestaging product manifest invalid path d workspace work a manifests x netcore engineering telemetry releasestaging product packages d workspace work a signed does not have any files with file name nupkg x netcore engineering telemetry releasestaging product contract was not validated x powershell exited with code source code validation x netcore engineering telemetry sdl last command failed with exit code changes | 1 |
43,163 | 11,167,218,084 | IssuesEvent | 2019-12-27 16:16:18 | Genymobile/scrcpy | https://api.github.com/repos/Genymobile/scrcpy | closed | Issue when running command scrcpy | build | command:
> scrcpy
output:
> INFO: scrcpy 1.12.1 <https://github.com/Genymobile/scrcpy>
/home/willfam/Desktop/scrcpy/scrcpy-se...shed. 6.0 MB/s (18802 bytes in 0.003s)
ERROR: Exception on thread Thread[main,5,main]
java.lang.NumberFormatException: For input string: "1.12.1"
at java.lang.Integer.parseInt(Integer.java:521)
at java.lang.Integer.parseInt(Integer.java:556)
at com.genymobile.scrcpy.Server.createOptions(Server.java:52)
at com.genymobile.scrcpy.Server.main(Server.java:101)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)
It states I am in scrcpy 1.12.1 instead of 1.4, is this because of a mistake in deleting previous version of scrcpy? | 1.0 | Issue when running command scrcpy - command:
> scrcpy
output:
> INFO: scrcpy 1.12.1 <https://github.com/Genymobile/scrcpy>
/home/willfam/Desktop/scrcpy/scrcpy-se...shed. 6.0 MB/s (18802 bytes in 0.003s)
ERROR: Exception on thread Thread[main,5,main]
java.lang.NumberFormatException: For input string: "1.12.1"
at java.lang.Integer.parseInt(Integer.java:521)
at java.lang.Integer.parseInt(Integer.java:556)
at com.genymobile.scrcpy.Server.createOptions(Server.java:52)
at com.genymobile.scrcpy.Server.main(Server.java:101)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:262)
It states I am in scrcpy 1.12.1 instead of 1.4, is this because of a mistake in deleting previous version of scrcpy? | non_infrastructure | issue when running command scrcpy command scrcpy output info scrcpy home willfam desktop scrcpy scrcpy se shed mb s bytes in error exception on thread thread java lang numberformatexception for input string at java lang integer parseint integer java at java lang integer parseint integer java at com genymobile scrcpy server createoptions server java at com genymobile scrcpy server main server java at com android internal os runtimeinit nativefinishinit native method at com android internal os runtimeinit main runtimeinit java it states i am in scrcpy instead of is this because of a mistake in deleting previous version of scrcpy | 0 |
155,089 | 19,765,665,955 | IssuesEvent | 2022-01-17 01:41:28 | tuanducdesign/view-book | https://api.github.com/repos/tuanducdesign/view-book | closed | CVE-2021-24033 (Medium) detected in react-dev-utils-10.2.1.tgz - autoclosed | security vulnerability | ## CVE-2021-24033 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>react-dev-utils-10.2.1.tgz</b></p></summary>
<p>webpack utilities used by Create React App</p>
<p>Library home page: <a href="https://registry.npmjs.org/react-dev-utils/-/react-dev-utils-10.2.1.tgz">https://registry.npmjs.org/react-dev-utils/-/react-dev-utils-10.2.1.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/react-dev-utils/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.3.tgz (Root Library)
- :x: **react-dev-utils-10.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tuanducdesign/view-book/commit/9ded07d0a086810334dca905dcd662e3ac24c7ba">9ded07d0a086810334dca905dcd662e3ac24c7ba</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
react-dev-utils prior to v11.0.4 exposes a function, getProcessForPort, where an input argument is concatenated into a command string to be executed. This function is typically used from react-scripts (in Create React App projects), where the usage is safe. Only when this function is manually invoked with user-provided values (ie: by custom code) is there the potential for command injection. If you're consuming it from react-scripts then this issue does not affect you.
<p>Publish Date: 2021-03-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-24033>CVE-2021-24033</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.facebook.com/security/advisories/cve-2021-24033">https://www.facebook.com/security/advisories/cve-2021-24033</a></p>
<p>Release Date: 2021-03-09</p>
<p>Fix Resolution: react-dev-utils-11.0.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-24033 (Medium) detected in react-dev-utils-10.2.1.tgz - autoclosed - ## CVE-2021-24033 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>react-dev-utils-10.2.1.tgz</b></p></summary>
<p>webpack utilities used by Create React App</p>
<p>Library home page: <a href="https://registry.npmjs.org/react-dev-utils/-/react-dev-utils-10.2.1.tgz">https://registry.npmjs.org/react-dev-utils/-/react-dev-utils-10.2.1.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/react-dev-utils/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.3.tgz (Root Library)
- :x: **react-dev-utils-10.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tuanducdesign/view-book/commit/9ded07d0a086810334dca905dcd662e3ac24c7ba">9ded07d0a086810334dca905dcd662e3ac24c7ba</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
react-dev-utils prior to v11.0.4 exposes a function, getProcessForPort, where an input argument is concatenated into a command string to be executed. This function is typically used from react-scripts (in Create React App projects), where the usage is safe. Only when this function is manually invoked with user-provided values (ie: by custom code) is there the potential for command injection. If you're consuming it from react-scripts then this issue does not affect you.
<p>Publish Date: 2021-03-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-24033>CVE-2021-24033</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.facebook.com/security/advisories/cve-2021-24033">https://www.facebook.com/security/advisories/cve-2021-24033</a></p>
<p>Release Date: 2021-03-09</p>
<p>Fix Resolution: react-dev-utils-11.0.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_infrastructure | cve medium detected in react dev utils tgz autoclosed cve medium severity vulnerability vulnerable library react dev utils tgz webpack utilities used by create react app library home page a href path to dependency file client package json path to vulnerable library client node modules react dev utils package json dependency hierarchy react scripts tgz root library x react dev utils tgz vulnerable library found in head commit a href found in base branch master vulnerability details react dev utils prior to exposes a function getprocessforport where an input argument is concatenated into a command string to be executed this function is typically used from react scripts in create react app projects where the usage is safe only when this function is manually invoked with user provided values ie by custom code is there the potential for command injection if you re consuming it from react scripts then this issue does not affect you publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution react dev utils step up your open source security game with whitesource | 0 |
27,493 | 21,786,506,708 | IssuesEvent | 2022-05-14 07:58:56 | The-Compilers/CryptoYard | https://api.github.com/repos/The-Compilers/CryptoYard | closed | Deploy skeleton on staging server | infrastructure | User story: As a developer I can see the skeleton-solution (Created in #4) running on the staging server. A frontend endpoint and a backend endpoint are accessible publicly, using HTTPS.
Depends on #4. | 1.0 | Deploy skeleton on staging server - User story: As a developer I can see the skeleton-solution (Created in #4) running on the staging server. A frontend endpoint and a backend endpoint are accessible publicly, using HTTPS.
Depends on #4. | infrastructure | deploy skeleton on staging server user story as a developer i can see the skeleton solution created in running on the staging server a frontend endpoint and a backend endpoint are accessible publicly using https depends on | 1 |
24,088 | 6,515,734,199 | IssuesEvent | 2017-08-26 19:46:39 | phw198/OutlookGoogleCalendarSync | https://api.github.com/repos/phw198/OutlookGoogleCalendarSync | closed | COM.exceptionerror | codeplex issue dormant old release unassigned | On startup received message about COM.exception error and to upload log.
Attached is the log.
Here is text from log with the error. Not sure log got attached to original
message . so uploading again.
2016-10-17 09:16:17,704 INFO 1 OutlookGoogleCalendarSync.OutlookCalendar [0] -
Starting a new instance of Outlook.
2016-10-17 09:16:17,808 ERROR 1 OutlookGoogleCalendarSync.OutlookCalendar [0]
- COM Exception encountered.
2016-10-17 09:16:17,809 ERROR 1 OutlookGoogleCalendarSync.OutlookCalendar [0]
- System.Runtime.InteropServices.COMException (0x80010001): Creating an
instance of the COM component with CLSID
{0006F03A-0000-0000-C000-000000000046} from the IClassFactory failed due to
the following error: 80010001.
at OutlookGoogleCalendarSync.OutlookCalendar.openOutlook(Application&
oApp, Boolean withSystemCall)
2016-10-17 09:16:18,415 FATAL 1 OutlookGoogleCalendarSync.Program [0] - COM
exception encountered. Please log an Issue on CodePlex and upload your
OGcalsync.log file.
2016-10-17 09:16:20,194 DEBUG 3 OutlookGoogleCalendarSync.Splash [0] -
Disposed of splash screen.
2016-10-17 09:17:06,841 INFO 1 OutlookGoogleCalendarSync.Program [0]
Work Item Details
--------------------
**Original CodePlex Issue:** [Issue 389](http://outlookgooglecalendarsync.codeplex.com/workitem/389)
**Status:** Proposed
**Reason Closed:** Unassigned
**Assigned to:** Unassigned
**Reported on:** Oct 17, 2016 at 2:24 PM
**Reported by:** RogRTC
**Updated on:** Apr 1 at 7:26 PM
**Updated by:** phw198
#### Plaintext Attachments
[CodePlex Issue #389 Plain Text Attachments](https://gist.github.com/52d7ba21c0be955ce8418c634f7c7d60) | 1.0 | COM.exceptionerror - On startup received message about COM.exception error and to upload log.
Attached is the log.
Here is text from log with the error. Not sure log got attached to original
message . so uploading again.
2016-10-17 09:16:17,704 INFO 1 OutlookGoogleCalendarSync.OutlookCalendar [0] -
Starting a new instance of Outlook.
2016-10-17 09:16:17,808 ERROR 1 OutlookGoogleCalendarSync.OutlookCalendar [0]
- COM Exception encountered.
2016-10-17 09:16:17,809 ERROR 1 OutlookGoogleCalendarSync.OutlookCalendar [0]
- System.Runtime.InteropServices.COMException (0x80010001): Creating an
instance of the COM component with CLSID
{0006F03A-0000-0000-C000-000000000046} from the IClassFactory failed due to
the following error: 80010001.
at OutlookGoogleCalendarSync.OutlookCalendar.openOutlook(Application&
oApp, Boolean withSystemCall)
2016-10-17 09:16:18,415 FATAL 1 OutlookGoogleCalendarSync.Program [0] - COM
exception encountered. Please log an Issue on CodePlex and upload your
OGcalsync.log file.
2016-10-17 09:16:20,194 DEBUG 3 OutlookGoogleCalendarSync.Splash [0] -
Disposed of splash screen.
2016-10-17 09:17:06,841 INFO 1 OutlookGoogleCalendarSync.Program [0]
Work Item Details
--------------------
**Original CodePlex Issue:** [Issue 389](http://outlookgooglecalendarsync.codeplex.com/workitem/389)
**Status:** Proposed
**Reason Closed:** Unassigned
**Assigned to:** Unassigned
**Reported on:** Oct 17, 2016 at 2:24 PM
**Reported by:** RogRTC
**Updated on:** Apr 1 at 7:26 PM
**Updated by:** phw198
#### Plaintext Attachments
[CodePlex Issue #389 Plain Text Attachments](https://gist.github.com/52d7ba21c0be955ce8418c634f7c7d60) | non_infrastructure | com exceptionerror on startup received message about com exception error and to upload log attached is the log here is text from log with the error not sure log got attached to original message so uploading again info outlookgooglecalendarsync outlookcalendar starting a new instance of outlook error outlookgooglecalendarsync outlookcalendar com exception encountered error outlookgooglecalendarsync outlookcalendar system runtime interopservices comexception creating an instance of the com component with clsid from the iclassfactory failed due to the following error at outlookgooglecalendarsync outlookcalendar openoutlook application amp oapp boolean withsystemcall fatal outlookgooglecalendarsync program com exception encountered please log an issue on codeplex and upload your ogcalsync log file debug outlookgooglecalendarsync splash disposed of splash screen info outlookgooglecalendarsync program work item details original codeplex issue status proposed reason closed unassigned assigned to unassigned reported on oct at pm reported by rogrtc updated on apr at pm updated by plaintext attachments | 0 |
54,604 | 6,397,607,314 | IssuesEvent | 2017-08-04 18:26:13 | brave/browser-ios | https://api.github.com/repos/brave/browser-ios | closed | Manual test run on iOS10 iPad for 1.4 | iPad release-notes/exclude tests | ## Per release specialty tests
- [x] Bookmarks not always displayed in left well after being added. ([#1021](https://github.com/brave/browser-ios/issues/1021))
- [x] Bookmark icons don't update when bookmark is removed. ([#1009](https://github.com/brave/browser-ios/issues/1009))
- [x] Focus is set to last tab after restart. ([#1007](https://github.com/brave/browser-ios/issues/1007))
- [x] Bookmarks doesn't load the correct site. ([#1001](https://github.com/brave/browser-ios/issues/1001))
## Installer
1. [ ] Check that installer is close to the size of last release.
2. [x] Check the Brave version in About and make sure it is EXACTLY as expected.
## Data
1. [ ] Make sure that data from the last version appears in the new version OK.
2. [ ] Test that the previous version's cookies are preserved in the next version.
## Bookmarks
1. [x] Test that creating a bookmark in the left well works
2. [x] Test that clicking a bookmark in the left well loads the bookmark
3. [x] Test that deleting a bookmark in the left well works
4. [x] Test that creating a bookmark folder works
5. [x] Test that creating a bookmark inside the created folder works
6. [x] Test that you are able to add a bookmark directly inside a bookmark folder
7. [x] Test that you are able to delete a bookmark in edit mode
8. [x] Test that you are able to delete a bookmark folder with bookmarks inside
9. [x] Test adding a bookmark domain subpaths is retained and you are successfully able to visit the domain subpath in a new tab
## Context menus
1. [x] Make sure context menu items in the URL bar work
2. [x] Make sure context menu items on content work with no selected text.
3. [x] Make sure context menu items on content work with selected text.
4. [x] Make sure context menu items on content work inside an editable control (input, textarea, or contenteditable).
5. [x] Context menu: verify you can Open in Background Tab, and Open in Private Tab
## Find on page
1. [x] Ensure search box is shown when selected via the share menu
2. [x] Test successful find
3. [x] Test forward and backward find navigation
4. [x] Test failed find shows 0 results
## Private Mode
1. [x] Create private tab, go to http://google.com, search for 'yumyums', exit private mode, go to http://google.com search box and begin typing 'yumyums' and verify that word is not in the autocomplete list
## Reader Mode
1. [x] Visit http://m.slashdot.org, open any article, verify the reader mode icon is shown in the URL bar
2. [x] Verify tapping on the reader mode icon opens the article in reader mode
3. [x] Edit reader mode settings and open different pages in reader mode and verify if the setting is retained across each article
## History
1. [x] On youtube.com, thestar.com (or any other site using push state nav), navigate the site and verify history is added. Also note if the progress bar activates and shows progress.
2. [x] Settings > Clear Private Data, and clear all. Check history is cleared, and top sites are cleared.
## Shields Settings
1. [x] Enable all switches in settings and visit a site and disable block scripts. Kill and relaunch app and verify if the site shield settings are retained
## Site hacks
1. [x] Test https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Downloads
1. [x] Test that you can save an image from a site.
## Fullscreen
1. [x] Test that entering HTML5 full screen works. And pressing restore to go back exits full screen. (youtube.com)
## Gestures
1. [x] Test zoom in / out gestures work
2. [x] Test that navigating to a different origin resets the zoom
3. [x] Swipe back and forward to navigate, verify this works as expected
## Password Managers
1. [x] Test tapping on 1Password on the slide out keyboard launches 1Password App and able to select the stored credentials
2. [x] Test tapping on bitwarden password manager in the autofill field launches the app and autofills the stored data
## Sync
1. [ ] Ensure you are able to scan the QR code and sync with laptop
2. [ ] Ensure the bookmarks from laptop shows up on the mobile after sync completes
3. [ ] Add a bookmark on mobile and check if it gets synced to the laptop
## Bravery settings
1. [x] Check that HTTPS Everywhere works by loading https://https-everywhere.badssl.com/
2. [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
3. [x] Check that block ad and unblock ad works on http://slashdot.org
4. [x] Check that toggling to blocking and allow ads works as expected.
5. [x] Test that clicking through a cert error in https://badssl.com/ works.
6. [x] Test that Safe Browsing works (http://downloadme.org/)
7. [x] Turning Safe Browsing off and shields off both disable safe browsing for http://downloadme.org/.
8. [x] Enable block script globally from settings, Visit https://brianbondy.com/, nothing should load. Tap on Shields and disable block script, page should load properly
9. [x] Test that preferences default Bravery settings take effect on pages with no site settings.
10. [x] Test that turning on fingerprinting protection in preferences shows 1 fingerprints blocked at https://browserleaks.com/canvas . Test that turning it off in the Bravery menu shows 0 fingerprints blocked.
11. [x] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/7/ when 3rd party cookies are blocked.
12. [x] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on.
## Content tests
1. [x] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Test that context menus work in the new twitter tab
2. [x] Load twitter and click on a tweet so the popup div shows. Click to dismiss and repeat with another div. Make sure it shows
3. [x] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password is auto-populated when you visit the site again.
4. [x] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works
5. [x] Test that PDF is loaded at http://www.orimi.com/pdf-test.pdf
6. [x] Test that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run)
7. [x] Test that news.google.com sites open in a new tab (due to target being _blank)
## Top sites view
1. [x] Long-press on top sites to get to deletion mode, and delete a top site (note this will stop that site from showing up again on top sites, so you may not want to do this a site you want to keep there)
## Background
1. [x] Start loading a page, background the app, wait >5 sec, then bring to front, ensure splash screen is not shown
## Session storage
1. [x] Test that tabs restore when closed, including active tab.
| 1.0 | Manual test run on iOS10 iPad for 1.4 - ## Per release specialty tests
- [x] Bookmarks not always displayed in left well after being added. ([#1021](https://github.com/brave/browser-ios/issues/1021))
- [x] Bookmark icons don't update when bookmark is removed. ([#1009](https://github.com/brave/browser-ios/issues/1009))
- [x] Focus is set to last tab after restart. ([#1007](https://github.com/brave/browser-ios/issues/1007))
- [x] Bookmarks doesn't load the correct site. ([#1001](https://github.com/brave/browser-ios/issues/1001))
## Installer
1. [ ] Check that installer is close to the size of last release.
2. [x] Check the Brave version in About and make sure it is EXACTLY as expected.
## Data
1. [ ] Make sure that data from the last version appears in the new version OK.
2. [ ] Test that the previous version's cookies are preserved in the next version.
## Bookmarks
1. [x] Test that creating a bookmark in the left well works
2. [x] Test that clicking a bookmark in the left well loads the bookmark
3. [x] Test that deleting a bookmark in the left well works
4. [x] Test that creating a bookmark folder works
5. [x] Test that creating a bookmark inside the created folder works
6. [x] Test that you are able to add a bookmark directly inside a bookmark folder
7. [x] Test that you are able to delete a bookmark in edit mode
8. [x] Test that you are able to delete a bookmark folder with bookmarks inside
9. [x] Test adding a bookmark domain subpaths is retained and you are successfully able to visit the domain subpath in a new tab
## Context menus
1. [x] Make sure context menu items in the URL bar work
2. [x] Make sure context menu items on content work with no selected text.
3. [x] Make sure context menu items on content work with selected text.
4. [x] Make sure context menu items on content work inside an editable control (input, textarea, or contenteditable).
5. [x] Context menu: verify you can Open in Background Tab, and Open in Private Tab
## Find on page
1. [x] Ensure search box is shown when selected via the share menu
2. [x] Test successful find
3. [x] Test forward and backward find navigation
4. [x] Test failed find shows 0 results
## Private Mode
1. [x] Create private tab, go to http://google.com, search for 'yumyums', exit private mode, go to http://google.com search box and begin typing 'yumyums' and verify that word is not in the autocomplete list
## Reader Mode
1. [x] Visit http://m.slashdot.org, open any article, verify the reader mode icon is shown in the URL bar
2. [x] Verify tapping on the reader mode icon opens the article in reader mode
3. [x] Edit reader mode settings and open different pages in reader mode and verify if the setting is retained across each article
## History
1. [x] On youtube.com, thestar.com (or any other site using push state nav), navigate the site and verify history is added. Also note if the progress bar activates and shows progress.
2. [x] Settings > Clear Private Data, and clear all. Check history is cleared, and top sites are cleared.
## Shields Settings
1. [x] Enable all switches in settings and visit a site and disable block scripts. Kill and relaunch app and verify if the site shield settings are retained
## Site hacks
1. [x] Test https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Downloads
1. [x] Test that you can save an image from a site.
## Fullscreen
1. [x] Test that entering HTML5 full screen works. And pressing restore to go back exits full screen. (youtube.com)
## Gestures
1. [x] Test zoom in / out gestures work
2. [x] Test that navigating to a different origin resets the zoom
3. [x] Swipe back and forward to navigate, verify this works as expected
## Password Managers
1. [x] Test tapping on 1Password on the slide out keyboard launches 1Password App and able to select the stored credentials
2. [x] Test tapping on bitwarden password manager in the autofill field launches the app and autofills the stored data
## Sync
1. [ ] Ensure you are able to scan the QR code and sync with laptop
2. [ ] Ensure the bookmarks from laptop shows up on the mobile after sync completes
3. [ ] Add a bookmark on mobile and check if it gets synced to the laptop
## Bravery settings
1. [x] Check that HTTPS Everywhere works by loading https://https-everywhere.badssl.com/
2. [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
3. [x] Check that block ad and unblock ad works on http://slashdot.org
4. [x] Check that toggling to blocking and allow ads works as expected.
5. [x] Test that clicking through a cert error in https://badssl.com/ works.
6. [x] Test that Safe Browsing works (http://downloadme.org/)
7. [x] Turning Safe Browsing off and shields off both disable safe browsing for http://downloadme.org/.
8. [x] Enable block script globally from settings, Visit https://brianbondy.com/, nothing should load. Tap on Shields and disable block script, page should load properly
9. [x] Test that preferences default Bravery settings take effect on pages with no site settings.
10. [x] Test that turning on fingerprinting protection in preferences shows 1 fingerprints blocked at https://browserleaks.com/canvas . Test that turning it off in the Bravery menu shows 0 fingerprints blocked.
11. [x] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/7/ when 3rd party cookies are blocked.
12. [x] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on.
## Content tests
1. [x] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Test that context menus work in the new twitter tab
2. [x] Load twitter and click on a tweet so the popup div shows. Click to dismiss and repeat with another div. Make sure it shows
3. [x] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password is auto-populated when you visit the site again.
4. [x] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works
5. [x] Test that PDF is loaded at http://www.orimi.com/pdf-test.pdf
6. [x] Test that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run)
7. [x] Test that news.google.com sites open in a new tab (due to target being _blank)
## Top sites view
1. [x] Long-press on top sites to get to deletion mode, and delete a top site (note this will stop that site from showing up again on top sites, so you may not want to do this a site you want to keep there)
## Background
1. [x] Start loading a page, background the app, wait >5 sec, then bring to front, ensure splash screen is not shown
## Session storage
1. [x] Test that tabs restore when closed, including active tab.
| non_infrastructure | manual test run on ipad for per release specialty tests bookmarks not always displayed in left well after being added bookmark icons don t update when bookmark is removed focus is set to last tab after restart bookmarks doesn t load the correct site installer check that installer is close to the size of last release check the brave version in about and make sure it is exactly as expected data make sure that data from the last version appears in the new version ok test that the previous version s cookies are preserved in the next version bookmarks test that creating a bookmark in the left well works test that clicking a bookmark in the left well loads the bookmark test that deleting a bookmark in the left well works test that creating a bookmark folder works test that creating a bookmark inside the created folder works test that you are able to add a bookmark directly inside a bookmark folder test that you are able to delete a bookmark in edit mode test that you are able to delete a bookmark folder with bookmarks inside test adding a bookmark domain subpaths is retained and you are successfully able to visit the domain subpath in a new tab context menus make sure context menu items in the url bar work make sure context menu items on content work with no selected text make sure context menu items on content work with selected text make sure context menu items on content work inside an editable control input textarea or contenteditable context menu verify you can open in background tab and open in private tab find on page ensure search box is shown when selected via the share menu test successful find test forward and backward find navigation test failed find shows results private mode create private tab go to search for yumyums exit private mode go to search box and begin typing yumyums and verify that word is not in the autocomplete list reader mode visit open any article verify the reader mode icon is shown in the url bar verify tapping on the reader mode icon opens the article in reader mode edit reader mode settings and open different pages in reader mode and verify if the setting is retained across each article history on youtube com thestar com or any other site using push state nav navigate the site and verify history is added also note if the progress bar activates and shows progress settings clear private data and clear all check history is cleared and top sites are cleared shields settings enable all switches in settings and visit a site and disable block scripts kill and relaunch app and verify if the site shield settings are retained site hacks test sub page loads a video and you can play it downloads test that you can save an image from a site fullscreen test that entering full screen works and pressing restore to go back exits full screen youtube com gestures test zoom in out gestures work test that navigating to a different origin resets the zoom swipe back and forward to navigate verify this works as expected password managers test tapping on on the slide out keyboard launches app and able to select the stored credentials test tapping on bitwarden password manager in the autofill field launches the app and autofills the stored data sync ensure you are able to scan the qr code and sync with laptop ensure the bookmarks from laptop shows up on the mobile after sync completes add a bookmark on mobile and check if it gets synced to the laptop bravery settings check that https everywhere works by loading turning https everywhere off and shields off both disable the redirect to check that block ad and unblock ad works on check that toggling to blocking and allow ads works as expected test that clicking through a cert error in works test that safe browsing works turning safe browsing off and shields off both disable safe browsing for enable block script globally from settings visit nothing should load tap on shields and disable block script page should load properly test that preferences default bravery settings take effect on pages with no site settings test that turning on fingerprinting protection in preferences shows fingerprints blocked at test that turning it off in the bravery menu shows fingerprints blocked test that party storage results are blank at when party cookies are blocked test that audio fingerprint is blocked at when fingerprinting protection is on content tests go to and click on the twitter icon on the top right test that context menus work in the new twitter tab load twitter and click on a tweet so the popup div shows click to dismiss and repeat with another div make sure it shows go to and make sure that the password can be saved make sure the saved password is auto populated when you visit the site again open an email on or inbox google com and click on a link make sure it works test that pdf is loaded at test that shows up as grey not red no mixed content scripts are run test that news google com sites open in a new tab due to target being blank top sites view long press on top sites to get to deletion mode and delete a top site note this will stop that site from showing up again on top sites so you may not want to do this a site you want to keep there background start loading a page background the app wait sec then bring to front ensure splash screen is not shown session storage test that tabs restore when closed including active tab | 0 |
2,790 | 3,870,807,755 | IssuesEvent | 2016-04-11 06:48:50 | timvideos/HDMI2USB-misoc-firmware | https://api.github.com/repos/timvideos/HDMI2USB-misoc-firmware | closed | Bootstrap script shouldn't do a `git pull`, should instead warn about existing checkout | level-infrastructure type-bug | Currently the bootstrap script does;
```bash
if [ -e HDMI2USB-misoc-firmware ]; then
cd HDMI2USB-misoc-firmware
git pull || exit 1
else
git clone --recurse-submodules $GIT_REPO || exit 1
cd HDMI2USB-misoc-firmware
git checkout $GIT_BRANCH || exit 1
fi
```
It should do;
```bash
if [ -e HDMI2USB-misoc-firmware ]; then
echo "Existing checkout found (see HDMI2USB-misoc-firmware directory), please remove before running."
exit 1
else
git clone --recurse-submodules $GIT_REPO || exit 1
cd HDMI2USB-misoc-firmware
git checkout $GIT_BRANCH || exit 1
fi
```
| 1.0 | Bootstrap script shouldn't do a `git pull`, should instead warn about existing checkout - Currently the bootstrap script does;
```bash
if [ -e HDMI2USB-misoc-firmware ]; then
cd HDMI2USB-misoc-firmware
git pull || exit 1
else
git clone --recurse-submodules $GIT_REPO || exit 1
cd HDMI2USB-misoc-firmware
git checkout $GIT_BRANCH || exit 1
fi
```
It should do;
```bash
if [ -e HDMI2USB-misoc-firmware ]; then
echo "Existing checkout found (see HDMI2USB-misoc-firmware directory), please remove before running."
exit 1
else
git clone --recurse-submodules $GIT_REPO || exit 1
cd HDMI2USB-misoc-firmware
git checkout $GIT_BRANCH || exit 1
fi
```
| infrastructure | bootstrap script shouldn t do a git pull should instead warn about existing checkout currently the bootstrap script does bash if then cd misoc firmware git pull exit else git clone recurse submodules git repo exit cd misoc firmware git checkout git branch exit fi it should do bash if then echo existing checkout found see misoc firmware directory please remove before running exit else git clone recurse submodules git repo exit cd misoc firmware git checkout git branch exit fi | 1 |
170,401 | 6,443,962,125 | IssuesEvent | 2017-08-12 03:21:56 | novialim/farmily | https://api.github.com/repos/novialim/farmily | closed | Some handlebar pages are not being passed the {{title}} property | bug low priority | Some handlebar pages do not have proper titles because they are not being passed a value for `title` | 1.0 | Some handlebar pages are not being passed the {{title}} property - Some handlebar pages do not have proper titles because they are not being passed a value for `title` | non_infrastructure | some handlebar pages are not being passed the title property some handlebar pages do not have proper titles because they are not being passed a value for title | 0 |
326,208 | 27,979,432,363 | IssuesEvent | 2023-03-26 00:52:27 | F4KER-X/TalentVault-SOEN-341-Project-2023 | https://api.github.com/repos/F4KER-X/TalentVault-SOEN-341-Project-2023 | opened | UAT 6.2:Update job | User Story 6 user acceptance test |
**User Acceptance Flow**
1. User chooses one the jobs to update
2. User changes some information
3. User save the job
4. Data is updated in the database | 1.0 | UAT 6.2:Update job -
**User Acceptance Flow**
1. User chooses one the jobs to update
2. User changes some information
3. User save the job
4. Data is updated in the database | non_infrastructure | uat update job user acceptance flow user chooses one the jobs to update user changes some information user save the job data is updated in the database | 0 |
138,451 | 5,341,447,503 | IssuesEvent | 2017-02-17 02:56:08 | mmisw/mmiorr | https://api.github.com/repos/mmisw/mmiorr | closed | Insert ontology annotation property for issue tracker location | enhancement ont Priority-Medium wontfix xdomes | Add an annotation property for any ontology that describes the location of the issue tracking system for that ontology. (Ideally it tracks issues only for that ontology, but if it's part of a larger project, so be it.)
The issue tracker should be a 'resolvable with proper authority' IRI -- that is, it may be an IRI that is only available to the ontology maintainers, though this is discouraged (of course :-).
Suggest calling it hasIssueTrackingLocation (hmm, thought about forcing it to be a URL, but I wasn't sure if 'URL' is still the name for a resolvable IRI).
| 1.0 | Insert ontology annotation property for issue tracker location - Add an annotation property for any ontology that describes the location of the issue tracking system for that ontology. (Ideally it tracks issues only for that ontology, but if it's part of a larger project, so be it.)
The issue tracker should be a 'resolvable with proper authority' IRI -- that is, it may be an IRI that is only available to the ontology maintainers, though this is discouraged (of course :-).
Suggest calling it hasIssueTrackingLocation (hmm, thought about forcing it to be a URL, but I wasn't sure if 'URL' is still the name for a resolvable IRI).
| non_infrastructure | insert ontology annotation property for issue tracker location add an annotation property for any ontology that describes the location of the issue tracking system for that ontology ideally it tracks issues only for that ontology but if it s part of a larger project so be it the issue tracker should be a resolvable with proper authority iri that is it may be an iri that is only available to the ontology maintainers though this is discouraged of course suggest calling it hasissuetrackinglocation hmm thought about forcing it to be a url but i wasn t sure if url is still the name for a resolvable iri | 0 |
21,263 | 14,483,786,241 | IssuesEvent | 2020-12-10 15:33:52 | govmeeting/govmeeting | https://api.github.com/repos/govmeeting/govmeeting | closed | Visual Studio typescript debugging | Infrastructure | When using Visual Studio, breakpoints cannot be set on Typescript code in "clientapp". This is a problem with VS itself. It is a result of our project having the Angular code in clientapp outside the directory structure of the Asp.Net project, "WebApp". We may need to wait for a solution from the .net core team for this to be fixed.
VS is only able to set breakpoints if "clientapp" is a sub-folder of WebApp .But this is a very limiting. Initially when we using .Net SPATemplates to generate an Angular + Asp.Net app, debugging of Typescript code worked. But the drawback was that clientapp and WebApp were very tightly bound. They were combined into one project. It was often not possible to upgrade .Net or Angular without one affecting the other.
It was decided to separate the two projects and put clientapp in it's own folder and separate project outside WebApp. But debugging of the clientapp was then broken in Visual Studio. (but not in VsCode).
See: this [Stack Overflow question.](https://stackoverflow.com/questions/57649009/vs2019-debugger-fails-after-renaming-clientapp-folder-in-dotnet-core-angular-app)
The SO question asks about "renaming" clientapp, because if we can't even rename the folder, VS definitely can't handle moving the folder. If we first solve the renaming question, we are closer to being able to move it. | 1.0 | Visual Studio typescript debugging - When using Visual Studio, breakpoints cannot be set on Typescript code in "clientapp". This is a problem with VS itself. It is a result of our project having the Angular code in clientapp outside the directory structure of the Asp.Net project, "WebApp". We may need to wait for a solution from the .net core team for this to be fixed.
VS is only able to set breakpoints if "clientapp" is a sub-folder of WebApp .But this is a very limiting. Initially when we using .Net SPATemplates to generate an Angular + Asp.Net app, debugging of Typescript code worked. But the drawback was that clientapp and WebApp were very tightly bound. They were combined into one project. It was often not possible to upgrade .Net or Angular without one affecting the other.
It was decided to separate the two projects and put clientapp in it's own folder and separate project outside WebApp. But debugging of the clientapp was then broken in Visual Studio. (but not in VsCode).
See: this [Stack Overflow question.](https://stackoverflow.com/questions/57649009/vs2019-debugger-fails-after-renaming-clientapp-folder-in-dotnet-core-angular-app)
The SO question asks about "renaming" clientapp, because if we can't even rename the folder, VS definitely can't handle moving the folder. If we first solve the renaming question, we are closer to being able to move it. | infrastructure | visual studio typescript debugging when using visual studio breakpoints cannot be set on typescript code in clientapp this is a problem with vs itself it is a result of our project having the angular code in clientapp outside the directory structure of the asp net project webapp we may need to wait for a solution from the net core team for this to be fixed vs is only able to set breakpoints if clientapp is a sub folder of webapp but this is a very limiting initially when we using net spatemplates to generate an angular asp net app debugging of typescript code worked but the drawback was that clientapp and webapp were very tightly bound they were combined into one project it was often not possible to upgrade net or angular without one affecting the other it was decided to separate the two projects and put clientapp in it s own folder and separate project outside webapp but debugging of the clientapp was then broken in visual studio but not in vscode see this the so question asks about renaming clientapp because if we can t even rename the folder vs definitely can t handle moving the folder if we first solve the renaming question we are closer to being able to move it | 1 |
215,505 | 16,675,736,545 | IssuesEvent | 2021-06-07 15:57:30 | phetsims/make-a-ten | https://api.github.com/repos/phetsims/make-a-ten | opened | CT perennial task failed | type:automated-testing | ```
make-a-ten : build
Build failed with status code 1:
Running "report-media" task
Running "clean" task
Running "build" task
Building runnable repository (make-a-ten, brands: phet)
Building brand: phet
Fatal error: Perennial task failed:
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
Full Error details:
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
Webpack build errors: [
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/BooleanProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/BooleanProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/NumberProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/NumberProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Dimension2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Dimension2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Image.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Image.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../joist/js/ScreenView.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../joist/js/ScreenView.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/joist/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery-phet/js/buttons/ResetAllButton.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery-phet/js/buttons/ResetAllButton.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Plane.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Plane.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../sun/js/ClosestDragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../sun/js/ClosestDragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/sun/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../phet-core/js/arrayRemove.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../phet-core/js/arrayRemove.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/phet-core/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/listeners/DragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/listeners/DragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Rectangle.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Rectangle.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js doesn't exist
]
Snapshot from 6/7/2021, 8:37:15 AM
``` | 1.0 | CT perennial task failed - ```
make-a-ten : build
Build failed with status code 1:
Running "report-media" task
Running "clean" task
Running "build" task
Building runnable repository (make-a-ten, brands: phet)
Building brand: phet
Fatal error: Perennial task failed:
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
Full Error details:
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
Webpack build errors: [
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/createObservableArray.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/createObservableArray.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/BooleanProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/BooleanProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/BooleanProperty.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/NumberProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/NumberProperty.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/NumberProperty.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/model'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/model)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2Property.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Dimension2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Dimension2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Dimension2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Vector2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Vector2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Image.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Image.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Image.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/Property.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Property.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../joist/js/ScreenView.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../joist/js/ScreenView.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/joist/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/joist/js/ScreenView.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery-phet/js/buttons/ResetAllButton.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery-phet/js/buttons/ResetAllButton.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery-phet/js/buttons/ResetAllButton.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Plane.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Plane.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Plane.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../sun/js/ClosestDragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../sun/js/ClosestDragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/sun/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/sun/js/ClosestDragListener.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../axon/js/Emitter.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/axon/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/axon/js/Emitter.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../dot/js/Bounds2.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/dot/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/dot/js/Bounds2.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../phet-core/js/arrayRemove.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../phet-core/js/arrayRemove.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/phet-core/js or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/phet-core/js/arrayRemove.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/listeners/DragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/listeners/DragListener.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/listeners/DragListener.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Node.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Node.js doesn't exist,
ModuleNotFoundError: Module not found: Error: Can't resolve '../../../../../scenery/js/nodes/Rectangle.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/Compilation.js:1762:28
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:732:13
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:10:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:274:22
at eval (eval at create (/data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:9:1)
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:403:22
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:117:11
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:648:24
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:802:8
at /data/share/phet/continuous-testing/ct-snapshots/1623076635488/chipper/node_modules/webpack/lib/NormalModuleFactory.js:922:5
resolve '../../../../../scenery/js/nodes/Rectangle.js' in '/data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/js/common/view'
using description file: /data/share/phet/continuous-testing/ct-snapshots/1623076635488/counting-common/package.json (relative path: ./js/common/view)
Field 'browser' doesn't contain a valid alias configuration
No description file found in /data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes or above
no extension
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js.wasm doesn't exist
as directory
/data/share/phet/continuous-testing/ct-snapshots/scenery/js/nodes/Rectangle.js doesn't exist
]
Snapshot from 6/7/2021, 8:37:15 AM
``` | non_infrastructure | ct perennial task failed make a ten build build failed with status code running report media task running clean task running build task building runnable repository make a ten brands phet building brand phet fatal error perennial task failed modulenotfounderror module not found error can t resolve axon js createobservablearray js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js full error details modulenotfounderror module not found error can t resolve axon js createobservablearray js in data share phet continuous testing ct snapshots counting common js common model webpack build errors modulenotfounderror module not found error can t resolve axon js createobservablearray js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve axon js createobservablearray js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots axon js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js createobservablearray js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js createobservablearray js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js createobservablearray js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js createobservablearray js wasm doesn t exist as directory data share phet continuous testing ct snapshots axon js createobservablearray js doesn t exist modulenotfounderror module not found error can t resolve dot js js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve dot js js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots dot js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js wasm doesn t exist as directory data share phet continuous testing ct snapshots dot js js doesn t exist modulenotfounderror module not found error can t resolve axon js booleanproperty js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve axon js booleanproperty js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots axon js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js booleanproperty js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js booleanproperty js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js booleanproperty js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js booleanproperty js wasm doesn t exist as directory data share phet continuous testing ct snapshots axon js booleanproperty js doesn t exist modulenotfounderror module not found error can t resolve axon js emitter js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve axon js emitter js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots axon js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js wasm doesn t exist as directory data share phet continuous testing ct snapshots axon js emitter js doesn t exist modulenotfounderror module not found error can t resolve axon js numberproperty js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve axon js numberproperty js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots axon js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js numberproperty js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js numberproperty js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js numberproperty js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js numberproperty js wasm doesn t exist as directory data share phet continuous testing ct snapshots axon js numberproperty js doesn t exist modulenotfounderror module not found error can t resolve dot js js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve dot js js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots dot js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js wasm doesn t exist as directory data share phet continuous testing ct snapshots dot js js doesn t exist modulenotfounderror module not found error can t resolve dot js js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve dot js js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots dot js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js wasm doesn t exist as directory data share phet continuous testing ct snapshots dot js js doesn t exist modulenotfounderror module not found error can t resolve dot js js in data share phet continuous testing ct snapshots counting common js common model at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve dot js js in data share phet continuous testing ct snapshots counting common js common model using description file data share phet continuous testing ct snapshots counting common package json relative path js common model field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots dot js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js wasm doesn t exist as directory data share phet continuous testing ct snapshots dot js js doesn t exist modulenotfounderror module not found error can t resolve dot js js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve dot js js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots dot js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js wasm doesn t exist as directory data share phet continuous testing ct snapshots dot js js doesn t exist modulenotfounderror module not found error can t resolve dot js js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve dot js js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots dot js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js wasm doesn t exist as directory data share phet continuous testing ct snapshots dot js js doesn t exist modulenotfounderror module not found error can t resolve scenery js nodes image js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery js nodes image js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery js nodes or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes image js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes image js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes image js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes image js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery js nodes image js doesn t exist modulenotfounderror module not found error can t resolve scenery js nodes node js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery js nodes node js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery js nodes or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery js nodes node js doesn t exist modulenotfounderror module not found error can t resolve axon js property js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve axon js property js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots axon js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js property js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js property js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js property js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js property js wasm doesn t exist as directory data share phet continuous testing ct snapshots axon js property js doesn t exist modulenotfounderror module not found error can t resolve joist js screenview js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve joist js screenview js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots joist js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots joist js screenview js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots joist js screenview js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots joist js screenview js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots joist js screenview js wasm doesn t exist as directory data share phet continuous testing ct snapshots joist js screenview js doesn t exist modulenotfounderror module not found error can t resolve scenery phet js buttons resetallbutton js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery phet js buttons resetallbutton js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery phet js buttons or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery phet js buttons resetallbutton js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery phet js buttons resetallbutton js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery phet js buttons resetallbutton js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery phet js buttons resetallbutton js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery phet js buttons resetallbutton js doesn t exist modulenotfounderror module not found error can t resolve scenery js nodes node js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery js nodes node js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery js nodes or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery js nodes node js doesn t exist modulenotfounderror module not found error can t resolve scenery js nodes plane js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery js nodes plane js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery js nodes or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes plane js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes plane js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes plane js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes plane js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery js nodes plane js doesn t exist modulenotfounderror module not found error can t resolve sun js closestdraglistener js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve sun js closestdraglistener js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots sun js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots sun js closestdraglistener js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots sun js closestdraglistener js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots sun js closestdraglistener js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots sun js closestdraglistener js wasm doesn t exist as directory data share phet continuous testing ct snapshots sun js closestdraglistener js doesn t exist modulenotfounderror module not found error can t resolve axon js emitter js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve axon js emitter js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots axon js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots axon js emitter js wasm doesn t exist as directory data share phet continuous testing ct snapshots axon js emitter js doesn t exist modulenotfounderror module not found error can t resolve dot js js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve dot js js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots dot js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots dot js js wasm doesn t exist as directory data share phet continuous testing ct snapshots dot js js doesn t exist modulenotfounderror module not found error can t resolve phet core js arrayremove js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve phet core js arrayremove js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots phet core js or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots phet core js arrayremove js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots phet core js arrayremove js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots phet core js arrayremove js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots phet core js arrayremove js wasm doesn t exist as directory data share phet continuous testing ct snapshots phet core js arrayremove js doesn t exist modulenotfounderror module not found error can t resolve scenery js listeners draglistener js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery js listeners draglistener js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery js listeners or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js listeners draglistener js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js listeners draglistener js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js listeners draglistener js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js listeners draglistener js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery js listeners draglistener js doesn t exist modulenotfounderror module not found error can t resolve scenery js nodes node js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery js nodes node js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery js nodes or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes node js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery js nodes node js doesn t exist modulenotfounderror module not found error can t resolve scenery js nodes rectangle js in data share phet continuous testing ct snapshots counting common js common view at data share phet continuous testing ct snapshots chipper node modules webpack lib compilation js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at eval eval at create data share phet continuous testing ct snapshots chipper node modules webpack node modules tapable lib hookcodefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js at data share phet continuous testing ct snapshots chipper node modules webpack lib normalmodulefactory js resolve scenery js nodes rectangle js in data share phet continuous testing ct snapshots counting common js common view using description file data share phet continuous testing ct snapshots counting common package json relative path js common view field browser doesn t contain a valid alias configuration no description file found in data share phet continuous testing ct snapshots scenery js nodes or above no extension field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes rectangle js doesn t exist js field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes rectangle js js doesn t exist json field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes rectangle js json doesn t exist wasm field browser doesn t contain a valid alias configuration data share phet continuous testing ct snapshots scenery js nodes rectangle js wasm doesn t exist as directory data share phet continuous testing ct snapshots scenery js nodes rectangle js doesn t exist snapshot from am | 0 |
28,917 | 23,605,660,663 | IssuesEvent | 2022-08-24 08:02:53 | arduino/arduino-ide | https://api.github.com/repos/arduino/arduino-ide | opened | Decouple the automatic translation and theme scripts from the IDE code | type: enhancement topic: infrastructure | ### Describe the request
The following npm scripts do not require IDE2/Theia dependencies to be installed:
- `"i18n:push"`,
- `"i18n:pull"`,
- "themes:pull"`, and
- "themes:generate"
But the corresponding GH Actions run `yarn` and expect all the IDE2/Theia dependencies to be installed. The current way is not just ineffective but does not make much sense.
Please create dedicated `npm` projects inside the IDE2 project for updating the themes and translations, and run them without installing IDE2.
### Describe the current behavior
See request above.
### Arduino IDE version
ca47e8a
### Operating system
N/A
### Operating system version
It's for the workflow with GH Actions
### Additional context
_No response_
### Issue checklist
- [X] I searched for previous requests in [the issue tracker](https://github.com/arduino/arduino-ide/issues?q=)
- [X] I verified the feature was still missing when using the latest [nightly build](https://github.com/arduino/arduino-ide#nightly-builds)
- [X] My request contains all necessary details | 1.0 | Decouple the automatic translation and theme scripts from the IDE code - ### Describe the request
The following npm scripts do not require IDE2/Theia dependencies to be installed:
- `"i18n:push"`,
- `"i18n:pull"`,
- "themes:pull"`, and
- "themes:generate"
But the corresponding GH Actions run `yarn` and expect all the IDE2/Theia dependencies to be installed. The current way is not just ineffective but does not make much sense.
Please create dedicated `npm` projects inside the IDE2 project for updating the themes and translations, and run them without installing IDE2.
### Describe the current behavior
See request above.
### Arduino IDE version
ca47e8a
### Operating system
N/A
### Operating system version
It's for the workflow with GH Actions
### Additional context
_No response_
### Issue checklist
- [X] I searched for previous requests in [the issue tracker](https://github.com/arduino/arduino-ide/issues?q=)
- [X] I verified the feature was still missing when using the latest [nightly build](https://github.com/arduino/arduino-ide#nightly-builds)
- [X] My request contains all necessary details | infrastructure | decouple the automatic translation and theme scripts from the ide code describe the request the following npm scripts do not require theia dependencies to be installed push pull themes pull and themes generate but the corresponding gh actions run yarn and expect all the theia dependencies to be installed the current way is not just ineffective but does not make much sense please create dedicated npm projects inside the project for updating the themes and translations and run them without installing describe the current behavior see request above arduino ide version operating system n a operating system version it s for the workflow with gh actions additional context no response issue checklist i searched for previous requests in i verified the feature was still missing when using the latest my request contains all necessary details | 1 |
33,666 | 27,696,759,089 | IssuesEvent | 2023-03-14 03:15:15 | zer0Kerbal/LaunchPack | https://api.github.com/repos/zer0Kerbal/LaunchPack | opened | Update License | issue: license type: infrastructure | # Update License
* Update License
* [ ] Updated License: {CC BY-ND 4.0}+{Assets: All Rights Reserved}
* was: {ARR}
THIS FILE: All Rights Reserved by zer0Kerbal
<!--
updateLicense v1.0.0.1
created: 17 Aug 2022
updated: 01 Nov 2022
-->
| 1.0 | Update License - # Update License
* Update License
* [ ] Updated License: {CC BY-ND 4.0}+{Assets: All Rights Reserved}
* was: {ARR}
THIS FILE: All Rights Reserved by zer0Kerbal
<!--
updateLicense v1.0.0.1
created: 17 Aug 2022
updated: 01 Nov 2022
-->
| infrastructure | update license update license update license updated license cc by nd assets all rights reserved was arr this file all rights reserved by updatelicense created aug updated nov | 1 |
112,892 | 9,604,848,148 | IssuesEvent | 2019-05-10 21:20:04 | infiniteautomation/ma-core-public | https://api.github.com/repos/infiniteautomation/ma-core-public | closed | H2 - LOB Expansion | Enhancement High Priority Item Ready for Testing | The LOB Expansion bug has been fixed in H2 but upgrading H2 is only possible by dumping the database to an SQL file and then re-importing.
Some things to note:
1. We currently use the PageStore, perhaps we want to change the MVStore since we will be exporting and re-importing anyway. At present I'm not sure what the advantages are.
2. If we do this we need to make sure that there is enough disk space to perform the upgrade on any given system.
H2 reference issues:
https://github.com/h2database/h2database/issues/1247#issuecomment-400924831
https://github.com/h2database/h2database/issues/301
Some code to show the growth:
https://github.com/infiniteautomation/h2lob-bug
| 1.0 | H2 - LOB Expansion - The LOB Expansion bug has been fixed in H2 but upgrading H2 is only possible by dumping the database to an SQL file and then re-importing.
Some things to note:
1. We currently use the PageStore, perhaps we want to change the MVStore since we will be exporting and re-importing anyway. At present I'm not sure what the advantages are.
2. If we do this we need to make sure that there is enough disk space to perform the upgrade on any given system.
H2 reference issues:
https://github.com/h2database/h2database/issues/1247#issuecomment-400924831
https://github.com/h2database/h2database/issues/301
Some code to show the growth:
https://github.com/infiniteautomation/h2lob-bug
| non_infrastructure | lob expansion the lob expansion bug has been fixed in but upgrading is only possible by dumping the database to an sql file and then re importing some things to note we currently use the pagestore perhaps we want to change the mvstore since we will be exporting and re importing anyway at present i m not sure what the advantages are if we do this we need to make sure that there is enough disk space to perform the upgrade on any given system reference issues some code to show the growth | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.