Unnamed: 0 int64 1 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 3 438 | labels stringlengths 4 308 | body stringlengths 7 254k | index stringclasses 7 values | text_combine stringlengths 96 254k | label stringclasses 2 values | text stringlengths 96 246k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2,897 | 10,319,674,793 | IssuesEvent | 2019-08-30 18:11:51 | backdrop-ops/contrib | https://api.github.com/repos/backdrop-ops/contrib | closed | Port Request: Views Photo Grid | Maintainer application Port request | There are very few modules that allow to create nice responsive galleries (I know only Masonry view at the moment). This module provides a very nice grid arrangement and is responsive and mobile friendly.
https://www.drupal.org/project/views_photo_grid
#Port Request | True | Port Request: Views Photo Grid - There are very few modules that allow to create nice responsive galleries (I know only Masonry view at the moment). This module provides a very nice grid arrangement and is responsive and mobile friendly.
https://www.drupal.org/project/views_photo_grid
#Port Request | main | port request views photo grid there are very few modules that allow to create nice responsive galleries i know only masonry view at the moment this module provides a very nice grid arrangement and is responsive and mobile friendly port request | 1 |
4,626 | 23,954,150,035 | IssuesEvent | 2022-09-12 13:48:31 | carbon-design-system/carbon | https://api.github.com/repos/carbon-design-system/carbon | closed | [Question]: How to show more items in dropdown? | type: question ❓ component: dropdown proposal: needs more research 🕵️♀️ status: waiting for maintainer response 💬 | ### Question for Carbon
How to increase the number of items shown in dropdown menu? Cant see any props that control the amount of items shown
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md) | True | [Question]: How to show more items in dropdown? - ### Question for Carbon
How to increase the number of items shown in dropdown menu? Cant see any props that control the amount of items shown
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md) | main | how to show more items in dropdown question for carbon how to increase the number of items shown in dropdown menu cant see any props that control the amount of items shown code of conduct i agree to follow this project s | 1 |
24,231 | 12,056,766,472 | IssuesEvent | 2020-04-15 14:54:29 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [APM] Document agents and versions section to service maps | Feature:Service Maps Team:apm v7.7.0 | Lets add an additional section to the service maps documentation to specify what agents and the minimum version for each agent that will have support for service maps. I expect this list to change as we add additional support across the agents.
| 1.0 | [APM] Document agents and versions section to service maps - Lets add an additional section to the service maps documentation to specify what agents and the minimum version for each agent that will have support for service maps. I expect this list to change as we add additional support across the agents.
| non_main | document agents and versions section to service maps lets add an additional section to the service maps documentation to specify what agents and the minimum version for each agent that will have support for service maps i expect this list to change as we add additional support across the agents | 0 |
2,330 | 8,351,417,183 | IssuesEvent | 2018-10-02 00:05:54 | TabbycatDebate/tabbycat | https://api.github.com/repos/TabbycatDebate/tabbycat | reopened | Implement Celery (and use for email notifications) | awaiting maintainer help wanted in progress refactoring | This is one for @tienne-B that hopefully ties in to the existing work on the email app but also adds some infrastructure that can be useful elsewhere.
For context, #590 (has more details) we want the ability to run longer tasks on workers. This is both to escape the 30-second dyno limit and to free up dyno resources that long-running tasks consume. My understanding is that its standard practice to offload the actual emailing process to a worker in this same fashion, so that could be a good starting point for this wider aim/infrastructure.
If you checkout the `celery` branch I've started to set this up although I was having some import path issues. If you were looking something to do getting celery up and going (and using it to implement the email sending) would be super useful. You could then have a crack at implementing it in other areas (say adj allocation) or we could take over at that point. | True | Implement Celery (and use for email notifications) - This is one for @tienne-B that hopefully ties in to the existing work on the email app but also adds some infrastructure that can be useful elsewhere.
For context, #590 (has more details) we want the ability to run longer tasks on workers. This is both to escape the 30-second dyno limit and to free up dyno resources that long-running tasks consume. My understanding is that its standard practice to offload the actual emailing process to a worker in this same fashion, so that could be a good starting point for this wider aim/infrastructure.
If you checkout the `celery` branch I've started to set this up although I was having some import path issues. If you were looking something to do getting celery up and going (and using it to implement the email sending) would be super useful. You could then have a crack at implementing it in other areas (say adj allocation) or we could take over at that point. | main | implement celery and use for email notifications this is one for tienne b that hopefully ties in to the existing work on the email app but also adds some infrastructure that can be useful elsewhere for context has more details we want the ability to run longer tasks on workers this is both to escape the second dyno limit and to free up dyno resources that long running tasks consume my understanding is that its standard practice to offload the actual emailing process to a worker in this same fashion so that could be a good starting point for this wider aim infrastructure if you checkout the celery branch i ve started to set this up although i was having some import path issues if you were looking something to do getting celery up and going and using it to implement the email sending would be super useful you could then have a crack at implementing it in other areas say adj allocation or we could take over at that point | 1 |
180,407 | 6,649,390,604 | IssuesEvent | 2017-09-28 13:05:17 | spring-projects/spring-boot | https://api.github.com/repos/spring-projects/spring-boot | opened | CLI does not work with Java9 | priority: normal theme: java9 type: enhancement | Running a simple script with the cli and Java 9 yield the following:
```
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (jar:file:/Users/snicoll/tools/spring-boot-cli/spring-2.0.0.BUILD-SNAPSHOT/lib/spring-boot-cli-2.0.0.BUILD-SNAPSHOT.jar!/BOOT-INF/lib/groovy-2.5.0-beta-1.jar!/) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at org.springframework.boot.cli.app.SpringApplicationLauncher.launch(SpringApplicationLauncher.java:65)
at org.springframework.boot.cli.command.run.SpringApplicationRunner$RunThread.run(SpringApplicationRunner.java:173)
Caused by: java.lang.IllegalArgumentException: Cannot instantiate interface org.springframework.context.ApplicationContextInitializer : org.springframework.boot.context.ConfigurationWarningsApplicationContextInitializer
at org.springframework.boot.SpringApplication.createSpringFactoriesInstances(SpringApplication.java:439)
at org.springframework.boot.SpringApplication.getSpringFactoriesInstances(SpringApplication.java:418)
at org.springframework.boot.SpringApplication.getSpringFactoriesInstances(SpringApplication.java:409)
at org.springframework.boot.SpringApplication.<init>(SpringApplication.java:266)
at org.springframework.boot.SpringApplication.<init>(SpringApplication.java:247)
... 6 more
Caused by: java.lang.NoClassDefFoundError: java/sql/SQLException
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:161)
at org.springframework.boot.SpringApplication.createSpringFactoriesInstances(SpringApplication.java:435)
... 10 more
Caused by: java.lang.ClassNotFoundException: java.sql.SQLException
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
at org.springframework.boot.cli.compiler.ExtendedGroovyClassLoader.findClass(ExtendedGroovyClassLoader.java:84)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:563)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:678)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:788)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:776)
... 12 more
``` | 1.0 | CLI does not work with Java9 - Running a simple script with the cli and Java 9 yield the following:
```
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (jar:file:/Users/snicoll/tools/spring-boot-cli/spring-2.0.0.BUILD-SNAPSHOT/lib/spring-boot-cli-2.0.0.BUILD-SNAPSHOT.jar!/BOOT-INF/lib/groovy-2.5.0-beta-1.jar!/) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:488)
at org.springframework.boot.cli.app.SpringApplicationLauncher.launch(SpringApplicationLauncher.java:65)
at org.springframework.boot.cli.command.run.SpringApplicationRunner$RunThread.run(SpringApplicationRunner.java:173)
Caused by: java.lang.IllegalArgumentException: Cannot instantiate interface org.springframework.context.ApplicationContextInitializer : org.springframework.boot.context.ConfigurationWarningsApplicationContextInitializer
at org.springframework.boot.SpringApplication.createSpringFactoriesInstances(SpringApplication.java:439)
at org.springframework.boot.SpringApplication.getSpringFactoriesInstances(SpringApplication.java:418)
at org.springframework.boot.SpringApplication.getSpringFactoriesInstances(SpringApplication.java:409)
at org.springframework.boot.SpringApplication.<init>(SpringApplication.java:266)
at org.springframework.boot.SpringApplication.<init>(SpringApplication.java:247)
... 6 more
Caused by: java.lang.NoClassDefFoundError: java/sql/SQLException
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:161)
at org.springframework.boot.SpringApplication.createSpringFactoriesInstances(SpringApplication.java:435)
... 10 more
Caused by: java.lang.ClassNotFoundException: java.sql.SQLException
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:466)
at org.springframework.boot.cli.compiler.ExtendedGroovyClassLoader.findClass(ExtendedGroovyClassLoader.java:84)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:563)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:678)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:788)
at groovy.lang.GroovyClassLoader.loadClass(GroovyClassLoader.java:776)
... 12 more
``` | non_main | cli does not work with running a simple script with the cli and java yield the following warning an illegal reflective access operation has occurred warning illegal reflective access by org codehaus groovy vmplugin jar file users snicoll tools spring boot cli spring build snapshot lib spring boot cli build snapshot jar boot inf lib groovy beta jar to constructor java lang invoke methodhandles lookup java lang class int warning please consider reporting this to the maintainers of org codehaus groovy vmplugin warning use illegal access warn to enable warnings of further illegal reflective access operations warning all illegal access operations will be denied in a future release java lang reflect invocationtargetexception at java base jdk internal reflect nativeconstructoraccessorimpl native method at java base jdk internal reflect nativeconstructoraccessorimpl newinstance nativeconstructoraccessorimpl java at java base jdk internal reflect delegatingconstructoraccessorimpl newinstance delegatingconstructoraccessorimpl java at java base java lang reflect constructor newinstance constructor java at org springframework boot cli app springapplicationlauncher launch springapplicationlauncher java at org springframework boot cli command run springapplicationrunner runthread run springapplicationrunner java caused by java lang illegalargumentexception cannot instantiate interface org springframework context applicationcontextinitializer org springframework boot context configurationwarningsapplicationcontextinitializer at org springframework boot springapplication createspringfactoriesinstances springapplication java at org springframework boot springapplication getspringfactoriesinstances springapplication java at org springframework boot springapplication getspringfactoriesinstances springapplication java at org springframework boot springapplication springapplication java at org springframework boot springapplication springapplication java more caused by java lang noclassdeffounderror java sql sqlexception at org springframework beans beanutils instantiateclass beanutils java at org springframework boot springapplication createspringfactoriesinstances springapplication java more caused by java lang classnotfoundexception java sql sqlexception at java base java net urlclassloader findclass urlclassloader java at org springframework boot cli compiler extendedgroovyclassloader findclass extendedgroovyclassloader java at java base java lang classloader loadclass classloader java at groovy lang groovyclassloader loadclass groovyclassloader java at groovy lang groovyclassloader loadclass groovyclassloader java at groovy lang groovyclassloader loadclass groovyclassloader java more | 0 |
16,920 | 2,615,126,566 | IssuesEvent | 2015-03-01 05:55:00 | chrsmith/google-api-java-client | https://api.github.com/repos/chrsmith/google-api-java-client | closed | Samples for google drive, Android | auto-migrated Priority-Medium Type-Sample | ```
I'm looking for examples for how to use google drive with Android 2.1.
Is there any working examples?
I have already downloaded 'google-api-java-client-1.9.0-beta'
Best Regards
Mikael Andersson
```
Original issue reported on code.google.com by `mxmi...@gmail.com` on 2 Jun 2012 at 6:37
* Merged into: #469 | 1.0 | Samples for google drive, Android - ```
I'm looking for examples for how to use google drive with Android 2.1.
Is there any working examples?
I have already downloaded 'google-api-java-client-1.9.0-beta'
Best Regards
Mikael Andersson
```
Original issue reported on code.google.com by `mxmi...@gmail.com` on 2 Jun 2012 at 6:37
* Merged into: #469 | non_main | samples for google drive android i m looking for examples for how to use google drive with android is there any working examples i have already downloaded google api java client beta best regards mikael andersson original issue reported on code google com by mxmi gmail com on jun at merged into | 0 |
4,715 | 24,321,584,399 | IssuesEvent | 2022-09-30 11:15:31 | beyarkay/eskom-calendar | https://api.github.com/repos/beyarkay/eskom-calendar | closed | Missing a stage 2 loadshedding in Cape Town Area 7 + 15 today | bug waiting-on-maintainer waiting-on-time | ```
$ curl -sL https://github.com/beyarkay/eskom-calendar/releases/download/latest/machine_friendly.csv | grep city-of-cape-town-area-7 | grep 2022-09-30
city-of-cape-town-area-7,2022-09-30T00:00:00+02:00,2022-09-30T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
city-of-cape-town-area-7,2022-09-30T22:00:00+02:00,2022-10-01T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
$ curl -sL https://github.com/beyarkay/eskom-calendar/releases/download/latest/machine_friendly.csv | grep city-of-cape-town-area-15 | grep 2022-09-30
city-of-cape-town-area-15,2022-09-30T00:00:00+02:00,2022-09-30T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
city-of-cape-town-area-15,2022-09-30T22:00:00+02:00,2022-10-01T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
```
`manually_specified.yaml` correctly states stage 2 for COCT from 06:00 to 22:00 - which means loadshedding at 14:00 for areas 7 and 15, but neither show up in the calendars. | True | Missing a stage 2 loadshedding in Cape Town Area 7 + 15 today - ```
$ curl -sL https://github.com/beyarkay/eskom-calendar/releases/download/latest/machine_friendly.csv | grep city-of-cape-town-area-7 | grep 2022-09-30
city-of-cape-town-area-7,2022-09-30T00:00:00+02:00,2022-09-30T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
city-of-cape-town-area-7,2022-09-30T22:00:00+02:00,2022-10-01T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
$ curl -sL https://github.com/beyarkay/eskom-calendar/releases/download/latest/machine_friendly.csv | grep city-of-cape-town-area-15 | grep 2022-09-30
city-of-cape-town-area-15,2022-09-30T00:00:00+02:00,2022-09-30T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
city-of-cape-town-area-15,2022-09-30T22:00:00+02:00,2022-10-01T00:30:00+02:00,4,"https://twitter.com/CityofCT/status/1575485965983895553"
```
`manually_specified.yaml` correctly states stage 2 for COCT from 06:00 to 22:00 - which means loadshedding at 14:00 for areas 7 and 15, but neither show up in the calendars. | main | missing a stage loadshedding in cape town area today curl sl grep city of cape town area grep city of cape town area city of cape town area curl sl grep city of cape town area grep city of cape town area city of cape town area manually specified yaml correctly states stage for coct from to which means loadshedding at for areas and but neither show up in the calendars | 1 |
3,550 | 14,047,814,244 | IssuesEvent | 2020-11-02 07:50:55 | spack/spack | https://api.github.com/repos/spack/spack | opened | Patching stages relies on side effects from memoization | bug maintainers patch triage | While debugging #19501 I ran into issues evaluating the `Spec.patches` properties. Trying to debug those issues I noticed that our mechanism for applying patches relies on side effects from memoization to change the `Patch.path` attribute to the right object.
This behavior has been introduced in #10150 The line that adds the path to the patch objects is:
https://github.com/spack/spack/blob/b2d6c634216a0ee2f0532372456ad389dd6fb427/lib/spack/spack/patch.py#L210
Without memoization a temporary object is returned and the path applied to it is not reflected in the spec from which it originated.
### Steps to reproduce the issue
Remove `lang.memoized` from the following lines in `spec.py`:
https://github.com/spack/spack/blob/b2d6c634216a0ee2f0532372456ad389dd6fb427/lib/spack/spack/spec.py#L3065-L3067
and then try to apply patches to any package that needs them:
```console
$ spack patch findutils
==> Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/de/ded4c9f73731cd48fec3b6bdaccce896473b6d8e337e9612e16cf1431bb1169d.tar.gz
==> Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/84/84b916c0bf8c51b7e7b28417692f0ad3e7030d1f3c248ba77c42ede5c1c5d11e
==> Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/bd/bd9e4e5cc280f9753ae14956c4e4aa17fe7a210f55dd6c84aa60b12d106d47a2
==> Error: Path for patch not set in apply: https://src.fedoraproject.org/rpms/findutils/raw/97ba2d7a18d1f9ae761b6ff0b4f1c4d33d7a8efc/f/findutils-4.6.0-gnulib-fflush.patch
```
### Error Message
The stacktrace for the failing command is:
<details>
<summary> spack -d --stacktrace patch findutils</summary>
```console
$ spack -d --stacktrace patch findutils
lib/spack/spack/cmd/__init__.py:122 ==> [2020-11-02-08:42:42.396634] Imported patch from built-in commands
lib/spack/spack/cmd/__init__.py:122 ==> [2020-11-02-08:42:42.397771] Imported patch from built-in commands
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.401526] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/config.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.420934] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/config.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.421465] Reading config file /home/culpo/.spack/config.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.423318] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/repos.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.516144] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/packages.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.548992] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/compilers.yaml
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.674482] ncurses applying constraint pkgconfig
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.675302] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.676141] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.678408] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.679164] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.679957] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.680734] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.683592] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.684398] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.689418] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.690602] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.694274] texinfo applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.695181] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.696079] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.696891] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.697641] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.698399] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.769016] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.769856] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.770652] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.771359] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.772075] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.772833] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.773536] ncurses applying constraint pkgconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.774282] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.775068] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.775816] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.776670] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.777354] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.778099] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.779129] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.779875] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.780967] texinfo applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.852062] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.852898] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.856322] m4 applying constraint libsigsegv
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.857054] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.857978] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.858743] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.859574] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.860627] ncurses applying constraint pkgconf@1.7.3%gcc@10.2.0 arch=linux-ubuntu18.04-broadwell
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.861665] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.862481] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.863263] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.864291] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.865135] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.866011] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.866724] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.867496] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.868530] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.869237] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.869977] texinfo applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.870781] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.871482] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.872173] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.872923] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.873624] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.940126] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.941015] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.941858] m4 applying constraint libsigsegv
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.942665] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.943529] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.944274] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.945050] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.946029] ncurses applying constraint pkgconf@1.7.3%gcc@10.2.0 arch=linux-ubuntu18.04-broadwell
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.947081] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.947811] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.948574] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.949303] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.950001] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.950818] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.951927] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.953080] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.954042] texinfo applying constraint perl
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.018010] Ordered hashes [findutils]: findutils/0/84b916c0bf8c51b7e7b28417692f0ad3e7030d1f3c248ba77c42ede5c1c5d11e, findutils/1/bd9e4e5cc280f9753ae14956c4e4aa17fe7a210f55dd6c84aa60b12d106d47a2
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.018454] Ordered hashes [m4]: m4/3/3877ab548f88597ab2327a2230ee048d2d07ace1062efe81fc92e91b7f39cd00, m4/9/fc9b61654a3ba1a8d6cd78ce087e7c96366c290bc8d2c299f09828d793b853c8
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.018814] Ordered hashes [gdbm]: gdbm/14/7f569b9287e9e5a4236636eef32ff3428f0462ec17aea359e0ebee07649f1f16
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.019267] Ordered hashes [texinfo]: texinfo/20/1732115f651cff98989cb0215d8f64da5e0f7911ebf0c13b064920f088f2ffe1, texinfo/23/12f6edb0c6b270b8c8dba2ce17998c580db01182d871ee32b7b6e4129bd1d23a
lib/spack/spack/database.py:362 ==> [2020-11-02-08:42:43.021835] DATABASE LOCK TIMEOUT: 3s
lib/spack/spack/database.py:366 ==> [2020-11-02-08:42:43.022112] PACKAGE LOCK TIMEOUT: No timeout
lib/spack/spack/stage.py:312 ==> [2020-11-02-08:42:43.106177] Creating stage lock spack-stage-findutils-4.6.0-6wex3ldlbkrkb5xx4hublbfo4gg2ahfq
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:43.107382] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/mirrors.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:43.109470] Reading config file /home/culpo/.spack/mirrors.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:43.111579] Reading config file /home/culpo/.spack/linux/mirrors.yaml
lib/spack/spack/fetch_strategy.py:582 ==> [2020-11-02-08:42:43.128733] Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/de/ded4c9f73731cd48fec3b6bdaccce896473b6d8e337e9612e16cf1431bb1169d.tar.gz
lib/spack/spack/stage.py:312 ==> [2020-11-02-08:42:43.146652] Creating stage lock spack-stage-zizdxm8j
lib/spack/spack/fetch_strategy.py:582 ==> [2020-11-02-08:42:43.148120] Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/84/84b916c0bf8c51b7e7b28417692f0ad3e7030d1f3c248ba77c42ede5c1c5d11e
lib/spack/spack/stage.py:312 ==> [2020-11-02-08:42:43.148617] Creating stage lock spack-stage-r_iuxl61
lib/spack/spack/fetch_strategy.py:582 ==> [2020-11-02-08:42:43.149896] Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/bd/bd9e4e5cc280f9753ae14956c4e4aa17fe7a210f55dd6c84aa60b12d106d47a2
lib/spack/spack/stage.py:593 ==> [2020-11-02-08:42:43.150274] Already staged spack-stage-findutils-4.6.0-6wex3ldlbkrkb5xx4hublbfo4gg2ahfq in /tmp/pytest-of-culpo/pytest-89/mock-stage0/spack-stage-findutils-4.6.0-6wex3ldlbkrkb5xx4hublbfo4gg2ahfq
Traceback (most recent call last):
File "/home/culpo/PycharmProjects/spack/bin/spack", line 64, in <module>
sys.exit(spack.main.main())
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/main.py", line 762, in main
return _invoke_command(command, parser, args, unknown)
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/main.py", line 490, in _invoke_command
return_val = command(parser, args)
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/cmd/patch.py", line 32, in patch
package.do_patch()
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/package.py", line 1346, in do_patch
patch.apply(self.stage)
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/patch.py", line 81, in apply
"Path for patch not set in apply: %s" % self.path_or_url)
AssertionError: Path for patch not set in apply: https://src.fedoraproject.org/rpms/findutils/raw/97ba2d7a18d1f9ae761b6ff0b4f1c4d33d7a8efc/f/findutils-4.6.0-gnulib-fflush.patch
```
</details>
### Information on your system
* **Spack:** 0.15.4-1768-b2d6c63421
* **Python:** 3.8.5
* **Platform:** linux-ubuntu18.04-broadwell
### Additional information
- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [x] I have searched the issues of this repo and believe this is not a duplicate
- [x] I have run the failing commands in debug mode and reported the output
| True | Patching stages relies on side effects from memoization - While debugging #19501 I ran into issues evaluating the `Spec.patches` properties. Trying to debug those issues I noticed that our mechanism for applying patches relies on side effects from memoization to change the `Patch.path` attribute to the right object.
This behavior has been introduced in #10150 The line that adds the path to the patch objects is:
https://github.com/spack/spack/blob/b2d6c634216a0ee2f0532372456ad389dd6fb427/lib/spack/spack/patch.py#L210
Without memoization a temporary object is returned and the path applied to it is not reflected in the spec from which it originated.
### Steps to reproduce the issue
Remove `lang.memoized` from the following lines in `spec.py`:
https://github.com/spack/spack/blob/b2d6c634216a0ee2f0532372456ad389dd6fb427/lib/spack/spack/spec.py#L3065-L3067
and then try to apply patches to any package that needs them:
```console
$ spack patch findutils
==> Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/de/ded4c9f73731cd48fec3b6bdaccce896473b6d8e337e9612e16cf1431bb1169d.tar.gz
==> Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/84/84b916c0bf8c51b7e7b28417692f0ad3e7030d1f3c248ba77c42ede5c1c5d11e
==> Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/bd/bd9e4e5cc280f9753ae14956c4e4aa17fe7a210f55dd6c84aa60b12d106d47a2
==> Error: Path for patch not set in apply: https://src.fedoraproject.org/rpms/findutils/raw/97ba2d7a18d1f9ae761b6ff0b4f1c4d33d7a8efc/f/findutils-4.6.0-gnulib-fflush.patch
```
### Error Message
The stacktrace for the failing command is:
<details>
<summary> spack -d --stacktrace patch findutils</summary>
```console
$ spack -d --stacktrace patch findutils
lib/spack/spack/cmd/__init__.py:122 ==> [2020-11-02-08:42:42.396634] Imported patch from built-in commands
lib/spack/spack/cmd/__init__.py:122 ==> [2020-11-02-08:42:42.397771] Imported patch from built-in commands
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.401526] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/config.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.420934] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/config.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.421465] Reading config file /home/culpo/.spack/config.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.423318] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/repos.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.516144] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/packages.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:42.548992] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/compilers.yaml
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.674482] ncurses applying constraint pkgconfig
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.675302] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.676141] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.678408] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.679164] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.679957] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.680734] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.683592] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.684398] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.689418] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.690602] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.694274] texinfo applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.695181] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.696079] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.696891] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.697641] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.698399] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.769016] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.769856] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.770652] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.771359] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.772075] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.772833] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.773536] ncurses applying constraint pkgconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.774282] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.775068] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.775816] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.776670] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.777354] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.778099] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.779129] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.779875] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.780967] texinfo applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.852062] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.852898] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.856322] m4 applying constraint libsigsegv
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.857054] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.857978] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.858743] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.859574] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.860627] ncurses applying constraint pkgconf@1.7.3%gcc@10.2.0 arch=linux-ubuntu18.04-broadwell
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.861665] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.862481] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.863263] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.864291] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.865135] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.866011] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.866724] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.867496] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.868530] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.869237] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.869977] texinfo applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.870781] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.871482] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.872173] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.872923] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.873624] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.940126] findutils applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.941015] autoconf applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.941858] m4 applying constraint libsigsegv
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.942665] autoconf applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.943529] perl applying constraint gdbm
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.944274] gdbm applying constraint readline
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.945050] readline applying constraint ncurses
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.946029] ncurses applying constraint pkgconf@1.7.3%gcc@10.2.0 arch=linux-ubuntu18.04-broadwell
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.947081] perl applying constraint berkeley-db
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.947811] findutils applying constraint automake
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.948574] automake applying constraint autoconf
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.949303] automake applying constraint perl
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.950001] findutils applying constraint libtool
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.950818] libtool applying constraint m4@1.4.6:
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.951927] findutils applying constraint m4
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.953080] findutils applying constraint texinfo
lib/spack/spack/spec.py:2597 ==> [2020-11-02-08:42:42.954042] texinfo applying constraint perl
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.018010] Ordered hashes [findutils]: findutils/0/84b916c0bf8c51b7e7b28417692f0ad3e7030d1f3c248ba77c42ede5c1c5d11e, findutils/1/bd9e4e5cc280f9753ae14956c4e4aa17fe7a210f55dd6c84aa60b12d106d47a2
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.018454] Ordered hashes [m4]: m4/3/3877ab548f88597ab2327a2230ee048d2d07ace1062efe81fc92e91b7f39cd00, m4/9/fc9b61654a3ba1a8d6cd78ce087e7c96366c290bc8d2c299f09828d793b853c8
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.018814] Ordered hashes [gdbm]: gdbm/14/7f569b9287e9e5a4236636eef32ff3428f0462ec17aea359e0ebee07649f1f16
lib/spack/spack/spec.py:2316 ==> [2020-11-02-08:42:43.019267] Ordered hashes [texinfo]: texinfo/20/1732115f651cff98989cb0215d8f64da5e0f7911ebf0c13b064920f088f2ffe1, texinfo/23/12f6edb0c6b270b8c8dba2ce17998c580db01182d871ee32b7b6e4129bd1d23a
lib/spack/spack/database.py:362 ==> [2020-11-02-08:42:43.021835] DATABASE LOCK TIMEOUT: 3s
lib/spack/spack/database.py:366 ==> [2020-11-02-08:42:43.022112] PACKAGE LOCK TIMEOUT: No timeout
lib/spack/spack/stage.py:312 ==> [2020-11-02-08:42:43.106177] Creating stage lock spack-stage-findutils-4.6.0-6wex3ldlbkrkb5xx4hublbfo4gg2ahfq
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:43.107382] Reading config file /home/culpo/PycharmProjects/spack/etc/spack/defaults/mirrors.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:43.109470] Reading config file /home/culpo/.spack/mirrors.yaml
lib/spack/spack/config.py:909 ==> [2020-11-02-08:42:43.111579] Reading config file /home/culpo/.spack/linux/mirrors.yaml
lib/spack/spack/fetch_strategy.py:582 ==> [2020-11-02-08:42:43.128733] Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/de/ded4c9f73731cd48fec3b6bdaccce896473b6d8e337e9612e16cf1431bb1169d.tar.gz
lib/spack/spack/stage.py:312 ==> [2020-11-02-08:42:43.146652] Creating stage lock spack-stage-zizdxm8j
lib/spack/spack/fetch_strategy.py:582 ==> [2020-11-02-08:42:43.148120] Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/84/84b916c0bf8c51b7e7b28417692f0ad3e7030d1f3c248ba77c42ede5c1c5d11e
lib/spack/spack/stage.py:312 ==> [2020-11-02-08:42:43.148617] Creating stage lock spack-stage-r_iuxl61
lib/spack/spack/fetch_strategy.py:582 ==> [2020-11-02-08:42:43.149896] Using cached archive: /home/culpo/PycharmProjects/spack/var/spack/cache/_source-cache/archive/bd/bd9e4e5cc280f9753ae14956c4e4aa17fe7a210f55dd6c84aa60b12d106d47a2
lib/spack/spack/stage.py:593 ==> [2020-11-02-08:42:43.150274] Already staged spack-stage-findutils-4.6.0-6wex3ldlbkrkb5xx4hublbfo4gg2ahfq in /tmp/pytest-of-culpo/pytest-89/mock-stage0/spack-stage-findutils-4.6.0-6wex3ldlbkrkb5xx4hublbfo4gg2ahfq
Traceback (most recent call last):
File "/home/culpo/PycharmProjects/spack/bin/spack", line 64, in <module>
sys.exit(spack.main.main())
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/main.py", line 762, in main
return _invoke_command(command, parser, args, unknown)
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/main.py", line 490, in _invoke_command
return_val = command(parser, args)
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/cmd/patch.py", line 32, in patch
package.do_patch()
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/package.py", line 1346, in do_patch
patch.apply(self.stage)
File "/home/culpo/PycharmProjects/spack/lib/spack/spack/patch.py", line 81, in apply
"Path for patch not set in apply: %s" % self.path_or_url)
AssertionError: Path for patch not set in apply: https://src.fedoraproject.org/rpms/findutils/raw/97ba2d7a18d1f9ae761b6ff0b4f1c4d33d7a8efc/f/findutils-4.6.0-gnulib-fflush.patch
```
</details>
### Information on your system
* **Spack:** 0.15.4-1768-b2d6c63421
* **Python:** 3.8.5
* **Platform:** linux-ubuntu18.04-broadwell
### Additional information
- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [x] I have searched the issues of this repo and believe this is not a duplicate
- [x] I have run the failing commands in debug mode and reported the output
| main | patching stages relies on side effects from memoization while debugging i ran into issues evaluating the spec patches properties trying to debug those issues i noticed that our mechanism for applying patches relies on side effects from memoization to change the patch path attribute to the right object this behavior has been introduced in the line that adds the path to the patch objects is without memoization a temporary object is returned and the path applied to it is not reflected in the spec from which it originated steps to reproduce the issue remove lang memoized from the following lines in spec py and then try to apply patches to any package that needs them console spack patch findutils using cached archive home culpo pycharmprojects spack var spack cache source cache archive de tar gz using cached archive home culpo pycharmprojects spack var spack cache source cache archive using cached archive home culpo pycharmprojects spack var spack cache source cache archive bd error path for patch not set in apply error message the stacktrace for the failing command is spack d stacktrace patch findutils console spack d stacktrace patch findutils lib spack spack cmd init py imported patch from built in commands lib spack spack cmd init py imported patch from built in commands lib spack spack config py reading config file home culpo pycharmprojects spack etc spack defaults config yaml lib spack spack config py reading config file home culpo pycharmprojects spack etc spack config yaml lib spack spack config py reading config file home culpo spack config yaml lib spack spack config py reading config file home culpo pycharmprojects spack etc spack defaults repos yaml lib spack spack config py reading config file home culpo pycharmprojects spack etc spack defaults packages yaml lib spack spack config py reading config file home culpo pycharmprojects spack etc spack compilers yaml lib spack spack spec py ncurses applying constraint pkgconfig lib spack spack spec py readline applying constraint ncurses lib spack spack spec py gdbm applying constraint readline lib spack spack spec py perl applying constraint gdbm lib spack spack spec py perl applying constraint berkeley db lib spack spack spec py autoconf applying constraint lib spack spack spec py autoconf applying constraint perl lib spack spack spec py automake applying constraint autoconf lib spack spack spec py automake applying constraint perl lib spack spack spec py libtool applying constraint lib spack spack spec py findutils applying constraint lib spack spack spec py texinfo applying constraint perl lib spack spack spec py findutils applying constraint autoconf lib spack spack spec py findutils applying constraint automake lib spack spack spec py findutils applying constraint libtool lib spack spack spec py findutils applying constraint lib spack spack spec py findutils applying constraint texinfo lib spack spack spec py findutils applying constraint autoconf lib spack spack spec py autoconf applying constraint lib spack spack spec py autoconf applying constraint perl lib spack spack spec py perl applying constraint gdbm lib spack spack spec py gdbm applying constraint readline lib spack spack spec py readline applying constraint ncurses lib spack spack spec py ncurses applying constraint pkgconf lib spack spack spec py perl applying constraint berkeley db lib spack spack spec py findutils applying constraint automake lib spack spack spec py automake applying constraint autoconf lib spack spack spec py automake applying constraint perl lib spack spack spec py findutils applying constraint libtool lib spack spack spec py libtool applying constraint lib spack spack spec py findutils applying constraint lib spack spack spec py findutils applying constraint texinfo lib spack spack spec py texinfo applying constraint perl lib spack spack spec py findutils applying constraint autoconf lib spack spack spec py autoconf applying constraint lib spack spack spec py applying constraint libsigsegv lib spack spack spec py autoconf applying constraint perl lib spack spack spec py perl applying constraint gdbm lib spack spack spec py gdbm applying constraint readline lib spack spack spec py readline applying constraint ncurses lib spack spack spec py ncurses applying constraint pkgconf gcc arch linux broadwell lib spack spack spec py perl applying constraint berkeley db lib spack spack spec py autoconf applying constraint lib spack spack spec py autoconf applying constraint perl lib spack spack spec py findutils applying constraint automake lib spack spack spec py automake applying constraint autoconf lib spack spack spec py automake applying constraint perl lib spack spack spec py findutils applying constraint libtool lib spack spack spec py libtool applying constraint lib spack spack spec py findutils applying constraint lib spack spack spec py findutils applying constraint texinfo lib spack spack spec py texinfo applying constraint perl lib spack spack spec py findutils applying constraint autoconf lib spack spack spec py findutils applying constraint automake lib spack spack spec py findutils applying constraint libtool lib spack spack spec py findutils applying constraint lib spack spack spec py findutils applying constraint texinfo lib spack spack spec py findutils applying constraint autoconf lib spack spack spec py autoconf applying constraint lib spack spack spec py applying constraint libsigsegv lib spack spack spec py autoconf applying constraint perl lib spack spack spec py perl applying constraint gdbm lib spack spack spec py gdbm applying constraint readline lib spack spack spec py readline applying constraint ncurses lib spack spack spec py ncurses applying constraint pkgconf gcc arch linux broadwell lib spack spack spec py perl applying constraint berkeley db lib spack spack spec py findutils applying constraint automake lib spack spack spec py automake applying constraint autoconf lib spack spack spec py automake applying constraint perl lib spack spack spec py findutils applying constraint libtool lib spack spack spec py libtool applying constraint lib spack spack spec py findutils applying constraint lib spack spack spec py findutils applying constraint texinfo lib spack spack spec py texinfo applying constraint perl lib spack spack spec py ordered hashes findutils findutils lib spack spack spec py ordered hashes lib spack spack spec py ordered hashes gdbm lib spack spack spec py ordered hashes texinfo texinfo lib spack spack database py database lock timeout lib spack spack database py package lock timeout no timeout lib spack spack stage py creating stage lock spack stage findutils lib spack spack config py reading config file home culpo pycharmprojects spack etc spack defaults mirrors yaml lib spack spack config py reading config file home culpo spack mirrors yaml lib spack spack config py reading config file home culpo spack linux mirrors yaml lib spack spack fetch strategy py using cached archive home culpo pycharmprojects spack var spack cache source cache archive de tar gz lib spack spack stage py creating stage lock spack stage lib spack spack fetch strategy py using cached archive home culpo pycharmprojects spack var spack cache source cache archive lib spack spack stage py creating stage lock spack stage r lib spack spack fetch strategy py using cached archive home culpo pycharmprojects spack var spack cache source cache archive bd lib spack spack stage py already staged spack stage findutils in tmp pytest of culpo pytest mock spack stage findutils traceback most recent call last file home culpo pycharmprojects spack bin spack line in sys exit spack main main file home culpo pycharmprojects spack lib spack spack main py line in main return invoke command command parser args unknown file home culpo pycharmprojects spack lib spack spack main py line in invoke command return val command parser args file home culpo pycharmprojects spack lib spack spack cmd patch py line in patch package do patch file home culpo pycharmprojects spack lib spack spack package py line in do patch patch apply self stage file home culpo pycharmprojects spack lib spack spack patch py line in apply path for patch not set in apply s self path or url assertionerror path for patch not set in apply information on your system spack python platform linux broadwell additional information i have run spack debug report and reported the version of spack python platform i have searched the issues of this repo and believe this is not a duplicate i have run the failing commands in debug mode and reported the output | 1 |
2,689 | 9,377,864,714 | IssuesEvent | 2019-04-04 11:26:36 | chocolatey/chocolatey-package-requests | https://api.github.com/repos/chocolatey/chocolatey-package-requests | closed | RFP - TAP-Windows | Status: Available For Maintainer(s) | TAP-Windows provides virtual TAP device functionality on the Windows OS. It is installed in the C:\Program Files\TAP-Windows folder and is required by your VPN software to function.
TAP devices are virtual network kernel devices supported entirely in software – and not backed up by hardware network adapters. TAP drivers are used for TAP devices to work and they are designed with low-level kernel support for Ethernet tunneling.
The TAP-Windows driver comes in two flavours: the NDIS 5 driver (tap-windows, version 9.9.x) for Windows XP and NDIS 6 (tap-windows6, version 9.21.x+) for Windows 7 and above.
https://openvpn.net/index.php/open-source/downloads.html | True | RFP - TAP-Windows - TAP-Windows provides virtual TAP device functionality on the Windows OS. It is installed in the C:\Program Files\TAP-Windows folder and is required by your VPN software to function.
TAP devices are virtual network kernel devices supported entirely in software – and not backed up by hardware network adapters. TAP drivers are used for TAP devices to work and they are designed with low-level kernel support for Ethernet tunneling.
The TAP-Windows driver comes in two flavours: the NDIS 5 driver (tap-windows, version 9.9.x) for Windows XP and NDIS 6 (tap-windows6, version 9.21.x+) for Windows 7 and above.
https://openvpn.net/index.php/open-source/downloads.html | main | rfp tap windows tap windows provides virtual tap device functionality on the windows os it is installed in the c program files tap windows folder and is required by your vpn software to function tap devices are virtual network kernel devices supported entirely in software – and not backed up by hardware network adapters tap drivers are used for tap devices to work and they are designed with low level kernel support for ethernet tunneling the tap windows driver comes in two flavours the ndis driver tap windows version x for windows xp and ndis tap version x for windows and above | 1 |
4,666 | 24,121,048,306 | IssuesEvent | 2022-09-20 18:44:38 | aws/serverless-application-model | https://api.github.com/repos/aws/serverless-application-model | closed | Bug: AWS::ApiGateway::GatewayResponse header doesn't work | blocked/more-info-needed area/apigateway maintainer/need-followup | ### Description:
For timeout errors (504) since I am getting CORS error i have added `AWS::ApiGateway::GatewayResponse` as mentioned in [docs](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-controlling-access-to-apis-customize-response.html). but i am still getting CORS error.
### Steps to reproduce:
```
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >-
aws-sam
Globals:
Function:
Runtime: nodejs16.x
CodeUri: .
Architectures:
- arm64
Timeout: 120
MemorySize: 1024
Resources:
GatewayResponseDefault5XX:
Type: 'AWS::ApiGateway::GatewayResponse'
Properties:
ResponseParameters:
gatewayresponse.header.Access-Control-Allow-Origin: "'*'"
gatewayresponse.header.Access-Control-Allow-Headers: "'*'"
ResponseType: DEFAULT_5XX
RestApiId:
Ref: 'ApiGatewayApi'
ApiGatewayApi:
Type: AWS::Serverless::Api
Properties:
StageName: staging
Cors:
AllowOrigin: "'*'"
AllowMethods: "'POST, OPTIONS'"
AllowHeaders: "'*'"
lambdaFunction:
Type: 'AWS::Serverless::Function'
Properties:
FunctionName: lambdaFn
Handler: src/handlers/lambdaFn.handler
Events:
PublicFunctionCreate:
Type: Api
Properties:
Path: /public/create
Method: post
RestApiId:
Ref: ApiGatewayApi
```
### Observed result:
since my lambda function takes more than 30sec to complete
the API gateway returns 504 error but headers mentioned in Template are missing due to which CORS error is thrown
### Expected result:
API gateway returns 504 error with mentioned headers in template
| True | Bug: AWS::ApiGateway::GatewayResponse header doesn't work - ### Description:
For timeout errors (504) since I am getting CORS error i have added `AWS::ApiGateway::GatewayResponse` as mentioned in [docs](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-controlling-access-to-apis-customize-response.html). but i am still getting CORS error.
### Steps to reproduce:
```
AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >-
aws-sam
Globals:
Function:
Runtime: nodejs16.x
CodeUri: .
Architectures:
- arm64
Timeout: 120
MemorySize: 1024
Resources:
GatewayResponseDefault5XX:
Type: 'AWS::ApiGateway::GatewayResponse'
Properties:
ResponseParameters:
gatewayresponse.header.Access-Control-Allow-Origin: "'*'"
gatewayresponse.header.Access-Control-Allow-Headers: "'*'"
ResponseType: DEFAULT_5XX
RestApiId:
Ref: 'ApiGatewayApi'
ApiGatewayApi:
Type: AWS::Serverless::Api
Properties:
StageName: staging
Cors:
AllowOrigin: "'*'"
AllowMethods: "'POST, OPTIONS'"
AllowHeaders: "'*'"
lambdaFunction:
Type: 'AWS::Serverless::Function'
Properties:
FunctionName: lambdaFn
Handler: src/handlers/lambdaFn.handler
Events:
PublicFunctionCreate:
Type: Api
Properties:
Path: /public/create
Method: post
RestApiId:
Ref: ApiGatewayApi
```
### Observed result:
since my lambda function takes more than 30sec to complete
the API gateway returns 504 error but headers mentioned in Template are missing due to which CORS error is thrown
### Expected result:
API gateway returns 504 error with mentioned headers in template
| main | bug aws apigateway gatewayresponse header doesn t work description for timeout errors since i am getting cors error i have added aws apigateway gatewayresponse as mentioned in but i am still getting cors error steps to reproduce awstemplateformatversion transform aws serverless description aws sam globals function runtime x codeuri architectures timeout memorysize resources type aws apigateway gatewayresponse properties responseparameters gatewayresponse header access control allow origin gatewayresponse header access control allow headers responsetype default restapiid ref apigatewayapi apigatewayapi type aws serverless api properties stagename staging cors alloworigin allowmethods post options allowheaders lambdafunction type aws serverless function properties functionname lambdafn handler src handlers lambdafn handler events publicfunctioncreate type api properties path public create method post restapiid ref apigatewayapi observed result since my lambda function takes more than to complete the api gateway returns error but headers mentioned in template are missing due to which cors error is thrown expected result api gateway returns error with mentioned headers in template | 1 |
240,071 | 7,800,375,295 | IssuesEvent | 2018-06-09 08:39:01 | tine20/Tine-2.0-Open-Source-Groupware-and-CRM | https://api.github.com/repos/tine20/Tine-2.0-Open-Source-Groupware-and-CRM | closed | 0008958:
Merge SOGO integrator changes | CalDAV Feature Request Mantis high priority | **Reported by lkneschke on 26 Sep 2013 11:51**
Gabriel commited his SOGO integrator changes to Gerrit.
I would like to reoganize them a little bit, before they will be merged.
| 1.0 | 0008958:
Merge SOGO integrator changes - **Reported by lkneschke on 26 Sep 2013 11:51**
Gabriel commited his SOGO integrator changes to Gerrit.
I would like to reoganize them a little bit, before they will be merged.
| non_main | merge sogo integrator changes reported by lkneschke on sep gabriel commited his sogo integrator changes to gerrit i would like to reoganize them a little bit before they will be merged | 0 |
1,095 | 4,958,184,021 | IssuesEvent | 2016-12-02 08:49:49 | ansible/ansible-modules-core | https://api.github.com/repos/ansible/ansible-modules-core | closed | cron module failing if entry already exists (on RHEL5) | affects_2.3 bug_report waiting_on_maintainer | ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
cron module
##### ANSIBLE VERSION
```
ansible 2.3.0 (devel bb41a005b3) last updated 2016/11/17 15:58:57 (GMT +800)
lib/ansible/modules/core: (detached HEAD a4cddac368) last updated 2016/11/17 15:59:31 (GMT +800)
lib/ansible/modules/extras: (detached HEAD 19c7d5b31b) last updated 2016/11/17 16:00:00 (GMT +800)
config file =
configured module search path = Default w/o overrides
```
##### OS / ENVIRONMENT
Red Hat Enterprise Linux Server release 6.4 (Santiago)
##### SUMMARY
cron module seems to fail if entry already exists
##### STEPS TO REPRODUCE
```
[ansible@vmhklftpscdv1 ~]$ cat cron.yml
- hosts: "{{hosts}}"
tasks:
- name: test cron
cron: name="Test Cron Module" minute="0" hour="*" job="cron.sh echo x "
[ansible@vmhklftpscdv1 ~]$ ansible-playbook cron.yml -e "hosts=vmfurlaposdbdv1"
PLAY [vmfurlaposdbdv1] *************************************************************************************************************************
TASK [Gathering Facts] *************************************************************************************************************************
ok: [vmfurlaposdbdv1]
TASK [test cron] *******************************************************************************************************************************
changed: [vmfurlaposdbdv1]
PLAY RECAP *************************************************************************************************************************************
vmfurlaposdbdv1 : ok=2 changed=1 unreachable=0 failed=0
[ansible@vmhklftpscdv1 ~]$ ansible-playbook cron.yml -e "hosts=vmfurlaposdbdv1"
PLAY [vmfurlaposdbdv1] *************************************************************************************************************************
TASK [Gathering Facts] *************************************************************************************************************************
ok: [vmfurlaposdbdv1]
TASK [test cron] *******************************************************************************************************************************
fatal: [vmfurlaposdbdv1]: FAILED! => {"changed": false, "failed": true, "module_stderr": "", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_ERoh58/ansible_module_cron.py\", line 736, in ?\r\n main()\r\n File \"/tmp/ansible_ERoh58/ansible_module_cron.py\", line 693, in main\r\n if not changed and not crontab.existing.endswith(('\\r', '\\n')):\r\nTypeError: expected a character buffer object\r\n", "msg": "MODULE FAILURE"}
to retry, use: --limit @/home/ansible/cron.retry
PLAY RECAP *************************************************************************************************************************************
vmfurlaposdbdv1 : ok=1 changed=0 unreachable=0 failed=1
```
On target machine you can see cron entry was created fine:
```
[oracle@vmfurlaposdbdv1 ~]$ crontab -l
PATH=/usr/local/bin
<SOME OTHER ENTRIES HERE>
#Ansible: Test Cron Module
0 * * * * cron.sh echo x
```
##### EXPECTED RESULTS
Should do nothing as entry already exists.
##### ACTUAL RESULTS
Throws exception
Note seems related to managed host. Host is running RHEL5.8.
Seems to run find on other managed hosts (most are running RHEL6)
| True | cron module failing if entry already exists (on RHEL5) - ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
cron module
##### ANSIBLE VERSION
```
ansible 2.3.0 (devel bb41a005b3) last updated 2016/11/17 15:58:57 (GMT +800)
lib/ansible/modules/core: (detached HEAD a4cddac368) last updated 2016/11/17 15:59:31 (GMT +800)
lib/ansible/modules/extras: (detached HEAD 19c7d5b31b) last updated 2016/11/17 16:00:00 (GMT +800)
config file =
configured module search path = Default w/o overrides
```
##### OS / ENVIRONMENT
Red Hat Enterprise Linux Server release 6.4 (Santiago)
##### SUMMARY
cron module seems to fail if entry already exists
##### STEPS TO REPRODUCE
```
[ansible@vmhklftpscdv1 ~]$ cat cron.yml
- hosts: "{{hosts}}"
tasks:
- name: test cron
cron: name="Test Cron Module" minute="0" hour="*" job="cron.sh echo x "
[ansible@vmhklftpscdv1 ~]$ ansible-playbook cron.yml -e "hosts=vmfurlaposdbdv1"
PLAY [vmfurlaposdbdv1] *************************************************************************************************************************
TASK [Gathering Facts] *************************************************************************************************************************
ok: [vmfurlaposdbdv1]
TASK [test cron] *******************************************************************************************************************************
changed: [vmfurlaposdbdv1]
PLAY RECAP *************************************************************************************************************************************
vmfurlaposdbdv1 : ok=2 changed=1 unreachable=0 failed=0
[ansible@vmhklftpscdv1 ~]$ ansible-playbook cron.yml -e "hosts=vmfurlaposdbdv1"
PLAY [vmfurlaposdbdv1] *************************************************************************************************************************
TASK [Gathering Facts] *************************************************************************************************************************
ok: [vmfurlaposdbdv1]
TASK [test cron] *******************************************************************************************************************************
fatal: [vmfurlaposdbdv1]: FAILED! => {"changed": false, "failed": true, "module_stderr": "", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_ERoh58/ansible_module_cron.py\", line 736, in ?\r\n main()\r\n File \"/tmp/ansible_ERoh58/ansible_module_cron.py\", line 693, in main\r\n if not changed and not crontab.existing.endswith(('\\r', '\\n')):\r\nTypeError: expected a character buffer object\r\n", "msg": "MODULE FAILURE"}
to retry, use: --limit @/home/ansible/cron.retry
PLAY RECAP *************************************************************************************************************************************
vmfurlaposdbdv1 : ok=1 changed=0 unreachable=0 failed=1
```
On target machine you can see cron entry was created fine:
```
[oracle@vmfurlaposdbdv1 ~]$ crontab -l
PATH=/usr/local/bin
<SOME OTHER ENTRIES HERE>
#Ansible: Test Cron Module
0 * * * * cron.sh echo x
```
##### EXPECTED RESULTS
Should do nothing as entry already exists.
##### ACTUAL RESULTS
Throws exception
Note seems related to managed host. Host is running RHEL5.8.
Seems to run find on other managed hosts (most are running RHEL6)
| main | cron module failing if entry already exists on issue type bug report component name cron module ansible version ansible devel last updated gmt lib ansible modules core detached head last updated gmt lib ansible modules extras detached head last updated gmt config file configured module search path default w o overrides os environment red hat enterprise linux server release santiago summary cron module seems to fail if entry already exists steps to reproduce cat cron yml hosts hosts tasks name test cron cron name test cron module minute hour job cron sh echo x ansible playbook cron yml e hosts play task ok task changed play recap ok changed unreachable failed ansible playbook cron yml e hosts play task ok task fatal failed changed false failed true module stderr module stdout traceback most recent call last r n file tmp ansible ansible module cron py line in r n main r n file tmp ansible ansible module cron py line in main r n if not changed and not crontab existing endswith r n r ntypeerror expected a character buffer object r n msg module failure to retry use limit home ansible cron retry play recap ok changed unreachable failed on target machine you can see cron entry was created fine crontab l path usr local bin ansible test cron module cron sh echo x expected results should do nothing as entry already exists actual results throws exception note seems related to managed host host is running seems to run find on other managed hosts most are running | 1 |
4,597 | 23,833,950,099 | IssuesEvent | 2022-09-06 02:35:12 | danbugs/smithereens | https://api.github.com/repos/danbugs/smithereens | closed | #2 epic: implement player feature | core maintainer issue epic | The player feature will allow obtaining player results provided a gamer tag.
pre-tasks:
- [x] #3 | True | #2 epic: implement player feature - The player feature will allow obtaining player results provided a gamer tag.
pre-tasks:
- [x] #3 | main | epic implement player feature the player feature will allow obtaining player results provided a gamer tag pre tasks | 1 |
168,158 | 26,607,125,376 | IssuesEvent | 2023-01-23 20:19:44 | phetsims/greenhouse-effect | https://api.github.com/repos/phetsims/greenhouse-effect | closed | Recommend making touch area larger for flux meter | design:polish status:ready-for-review type:suggestion | <b>Test Device</b>
iPad
<b>Operating System</b>
iOS16
<b>Browser</b>
Safari
<b>Problem Description</b>
For https://github.com/phetsims/qa/issues/871. I can't confirm using `showPointerAreas` but my guess is the touch area for the flux meter isn't dilated. It sometimes took me a couple tries to grab it, so I recommend making it a little larger (mainly the height could be larger).
<b>Steps to Reproduce</b>
Open sim in English
Go to Layer Model screen
Show flux meter
Drag flux meter to a new position
<b>Visuals</b>
<details>
<summary><b>Troubleshooting Information</b></summary>
blah
</details>
Steps to reproduce:
| 1.0 | Recommend making touch area larger for flux meter - <b>Test Device</b>
iPad
<b>Operating System</b>
iOS16
<b>Browser</b>
Safari
<b>Problem Description</b>
For https://github.com/phetsims/qa/issues/871. I can't confirm using `showPointerAreas` but my guess is the touch area for the flux meter isn't dilated. It sometimes took me a couple tries to grab it, so I recommend making it a little larger (mainly the height could be larger).
<b>Steps to Reproduce</b>
Open sim in English
Go to Layer Model screen
Show flux meter
Drag flux meter to a new position
<b>Visuals</b>
<details>
<summary><b>Troubleshooting Information</b></summary>
blah
</details>
Steps to reproduce:
| non_main | recommend making touch area larger for flux meter test device ipad operating system browser safari problem description for i can t confirm using showpointerareas but my guess is the touch area for the flux meter isn t dilated it sometimes took me a couple tries to grab it so i recommend making it a little larger mainly the height could be larger steps to reproduce open sim in english go to layer model screen show flux meter drag flux meter to a new position visuals troubleshooting information blah steps to reproduce | 0 |
4,059 | 2,962,914,397 | IssuesEvent | 2015-07-10 06:10:54 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | Backend code editing: unable to view in full screen mode in 3.4.3 | No Code Attached Yet | -Before updating to 3.4.3, everything works fine, and after updating, back-end layout code editing was unable to view in full screen whether its ISIS or Hathor.
-Expected result: to view in full screen mode (f10) when editing the layout code.
-**Actual result:** The editing screen just expands downward without scroll bars appearing, and not full screen.
-System information:
Database Version 5.5.35-MariaDB
Database Collation latin1_swedish_ci
PHP Version 5.4.16
Web Server Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.4.16 mod_wsgi/3.4 Python/2.7.5
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.4.3 Stable [ Ember ] 2-July-2015 16: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 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.132 Safari/537.36
-Additional comments: tried searching to fix issue but unable to find solution.
| 1.0 | Backend code editing: unable to view in full screen mode in 3.4.3 - -Before updating to 3.4.3, everything works fine, and after updating, back-end layout code editing was unable to view in full screen whether its ISIS or Hathor.
-Expected result: to view in full screen mode (f10) when editing the layout code.
-**Actual result:** The editing screen just expands downward without scroll bars appearing, and not full screen.
-System information:
Database Version 5.5.35-MariaDB
Database Collation latin1_swedish_ci
PHP Version 5.4.16
Web Server Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_fcgid/2.3.9 PHP/5.4.16 mod_wsgi/3.4 Python/2.7.5
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.4.3 Stable [ Ember ] 2-July-2015 16: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 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.132 Safari/537.36
-Additional comments: tried searching to fix issue but unable to find solution.
| non_main | backend code editing unable to view in full screen mode in before updating to everything works fine and after updating back end layout code editing was unable to view in full screen whether its isis or hathor expected result to view in full screen mode when editing the layout code actual result the editing screen just expands downward without scroll bars appearing and not full screen system information database version mariadb database collation swedish ci php version web server apache centos openssl fips mod fcgid php mod wsgi python webserver to php interface joomla version joomla stable july gmt joomla platform version joomla platform stable apr gmt user agent mozilla windows nt applewebkit khtml like gecko chrome safari additional comments tried searching to fix issue but unable to find solution | 0 |
163,856 | 20,364,220,410 | IssuesEvent | 2022-02-21 02:21:26 | turkdevops/framevuerk | https://api.github.com/repos/turkdevops/framevuerk | opened | vue-highlightjs-1.3.3.tgz: 1 vulnerabilities (highest severity is: 5.3) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>vue-highlightjs-1.3.3.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/highlight.js/package.json</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [WS-2020-0208](https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | highlight.js-9.17.1.tgz | Transitive | N/A | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> WS-2020-0208</summary>
### Vulnerable Library - <b>highlight.js-9.17.1.tgz</b></p>
<p>Syntax highlighting with language autodetection.</p>
<p>Library home page: <a href="https://registry.npmjs.org/highlight.js/-/highlight.js-9.17.1.tgz">https://registry.npmjs.org/highlight.js/-/highlight.js-9.17.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/highlight.js/package.json</p>
<p>
Dependency Hierarchy:
- vue-highlightjs-1.3.3.tgz (Root Library)
- :x: **highlight.js-9.17.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>dev</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable.
<p>Publish Date: 2020-12-04
<p>URL: <a href=https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c>WS-2020-0208</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/highlightjs/highlight.js/tree/10.4.1">https://github.com/highlightjs/highlight.js/tree/10.4.1</a></p>
<p>Release Date: 2020-12-04</p>
<p>Fix Resolution: 10.4.1</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"highlight.js","packageVersion":"9.17.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"vue-highlightjs:1.3.3;highlight.js:9.17.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"10.4.1","isBinary":false}],"baseBranches":["dev"],"vulnerabilityIdentifier":"WS-2020-0208","vulnerabilityDetails":"If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable.","vulnerabilityUrl":"https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}]</REMEDIATE> --> | True | vue-highlightjs-1.3.3.tgz: 1 vulnerabilities (highest severity is: 5.3) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>vue-highlightjs-1.3.3.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/highlight.js/package.json</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [WS-2020-0208](https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | highlight.js-9.17.1.tgz | Transitive | N/A | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> WS-2020-0208</summary>
### Vulnerable Library - <b>highlight.js-9.17.1.tgz</b></p>
<p>Syntax highlighting with language autodetection.</p>
<p>Library home page: <a href="https://registry.npmjs.org/highlight.js/-/highlight.js-9.17.1.tgz">https://registry.npmjs.org/highlight.js/-/highlight.js-9.17.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/highlight.js/package.json</p>
<p>
Dependency Hierarchy:
- vue-highlightjs-1.3.3.tgz (Root Library)
- :x: **highlight.js-9.17.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>dev</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable.
<p>Publish Date: 2020-12-04
<p>URL: <a href=https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c>WS-2020-0208</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/highlightjs/highlight.js/tree/10.4.1">https://github.com/highlightjs/highlight.js/tree/10.4.1</a></p>
<p>Release Date: 2020-12-04</p>
<p>Fix Resolution: 10.4.1</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"highlight.js","packageVersion":"9.17.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"vue-highlightjs:1.3.3;highlight.js:9.17.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"10.4.1","isBinary":false}],"baseBranches":["dev"],"vulnerabilityIdentifier":"WS-2020-0208","vulnerabilityDetails":"If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable.","vulnerabilityUrl":"https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}]</REMEDIATE> --> | non_main | vue highlightjs tgz vulnerabilities highest severity is vulnerable library vue highlightjs tgz path to dependency file package json path to vulnerable library node modules highlight js package json vulnerabilities cve severity cvss dependency type fixed in remediation available medium highlight js tgz transitive n a ❌ details ws vulnerable library highlight js tgz syntax highlighting with language autodetection library home page a href path to dependency file package json path to vulnerable library node modules highlight js package json dependency hierarchy vue highlightjs tgz root library x highlight js tgz vulnerable library found in base branch dev vulnerability details if are you are using highlight js to highlight user provided data you are possibly vulnerable on the client side in a browser or electron environment risks could include lengthy freezes or crashes on the server side infinite freezes could occur effectively preventing users from accessing your app or service ie denial of service this is an issue with grammars shipped with the parser and potentially party grammars also not the parser itself if you are using highlight js with any of the following grammars you are vulnerable if you are using highlightauto to detect the language and have any of these grammars registered you are vulnerable 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 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 step up your open source security game with whitesource istransitivedependency true dependencytree vue highlightjs highlight js isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails if are you are using highlight js to highlight user provided data you are possibly vulnerable on the client side in a browser or electron environment risks could include lengthy freezes or crashes on the server side infinite freezes could occur effectively preventing users from accessing your app or service ie denial of service this is an issue with grammars shipped with the parser and potentially party grammars also not the parser itself if you are using highlight js with any of the following grammars you are vulnerable if you are using highlightauto to detect the language and have any of these grammars registered you are vulnerable vulnerabilityurl | 0 |
434 | 3,549,466,262 | IssuesEvent | 2016-01-20 18:06:43 | DynamoRIO/drmemory | https://api.github.com/repos/DynamoRIO/drmemory | opened | add a light mode feature to be agnostic of syscall #'s | Component-LightMode Maintainability Type-Feature | The goal is to operate on new Windows versions that have different syscalls but DR still works (after https://github.com/DynamoRIO/dynamorio/issues/1598). We would add a feature that turns off syscall parameter checking and tries to only care about the bare minimum syscalls needed to track memory allocation: and since those are all in ntoskrnl and are exported, we should be able to read them dynamically from the wrappers (module hooks).
Xref #1848, #1826.
| True | add a light mode feature to be agnostic of syscall #'s - The goal is to operate on new Windows versions that have different syscalls but DR still works (after https://github.com/DynamoRIO/dynamorio/issues/1598). We would add a feature that turns off syscall parameter checking and tries to only care about the bare minimum syscalls needed to track memory allocation: and since those are all in ntoskrnl and are exported, we should be able to read them dynamically from the wrappers (module hooks).
Xref #1848, #1826.
| main | add a light mode feature to be agnostic of syscall s the goal is to operate on new windows versions that have different syscalls but dr still works after we would add a feature that turns off syscall parameter checking and tries to only care about the bare minimum syscalls needed to track memory allocation and since those are all in ntoskrnl and are exported we should be able to read them dynamically from the wrappers module hooks xref | 1 |
372,802 | 11,028,478,902 | IssuesEvent | 2019-12-06 11:47:03 | epam/cloud-pipeline | https://api.github.com/repos/epam/cloud-pipeline | closed | Global search shall be made case insensitive | kind/enhancement priority/high state/verify sys/search | **Background**
At the moment, Cloud Pipeline's global search feature requires certain queries to be run in a `case-sensitive` manner (e.g. pipelines' names).
**Approach**
We shall modify this behavior so that all the queries are `case-insensitive`
| 1.0 | Global search shall be made case insensitive - **Background**
At the moment, Cloud Pipeline's global search feature requires certain queries to be run in a `case-sensitive` manner (e.g. pipelines' names).
**Approach**
We shall modify this behavior so that all the queries are `case-insensitive`
| non_main | global search shall be made case insensitive background at the moment cloud pipeline s global search feature requires certain queries to be run in a case sensitive manner e g pipelines names approach we shall modify this behavior so that all the queries are case insensitive | 0 |
734 | 4,323,535,457 | IssuesEvent | 2016-07-25 17:18:00 | gogits/gogs | https://api.github.com/repos/gogits/gogs | closed | Pagination for repositories | kind/feature status/assigned to maintainer status/needs feedback | We have in our gogs intstallation an organisation with about 6700 repositories. As you can imagine all lists become pretty long and the system a bit unresponsive. Is there the possibility to include pagination for repository lists and the contribution panel? | True | Pagination for repositories - We have in our gogs intstallation an organisation with about 6700 repositories. As you can imagine all lists become pretty long and the system a bit unresponsive. Is there the possibility to include pagination for repository lists and the contribution panel? | main | pagination for repositories we have in our gogs intstallation an organisation with about repositories as you can imagine all lists become pretty long and the system a bit unresponsive is there the possibility to include pagination for repository lists and the contribution panel | 1 |
62,094 | 6,775,943,862 | IssuesEvent | 2017-10-27 15:56:10 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | teamcity: failed tests on master: Examples-ORMs/TestSQLAlchemy, Examples-ORMs/TestSQLAlchemy/FirstRun, Examples-ORMs/TestSQLAlchemy/SecondRun, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products | Robot test-failure | The following tests appear to have failed:
[#390863](https://teamcity.cockroachdb.com/viewLog.html?buildId=390863):
```
--- FAIL: Examples-ORMs/TestSQLAlchemy (185.960s)
null
--- FAIL: Examples-ORMs/TestSQLAlchemy/FirstRun (180.660s)
main_test.go:160: Get http://localhost:6543/ping: dial tcp [::1]:6543: getsockopt: connection refused
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun (2.810s)
null
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart (0.000s)
null
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order (0.050s)
test_driver.go:213: expecting products from api after creation to be [{0 0x8d4a70 123.4}], found []
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers (0.050s)
test_driver.go:213: expecting products from api after creation to be [{0 0x8d4a70 123.4}], found []
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products (0.050s)
test_driver.go:213: expecting products from api after creation to be [{0 0x8d4a70 123.4}], found []
```
Please assign, take a look and update the issue accordingly. | 1.0 | teamcity: failed tests on master: Examples-ORMs/TestSQLAlchemy, Examples-ORMs/TestSQLAlchemy/FirstRun, Examples-ORMs/TestSQLAlchemy/SecondRun, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers, Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products - The following tests appear to have failed:
[#390863](https://teamcity.cockroachdb.com/viewLog.html?buildId=390863):
```
--- FAIL: Examples-ORMs/TestSQLAlchemy (185.960s)
null
--- FAIL: Examples-ORMs/TestSQLAlchemy/FirstRun (180.660s)
main_test.go:160: Get http://localhost:6543/ping: dial tcp [::1]:6543: getsockopt: connection refused
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun (2.810s)
null
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart (0.000s)
null
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Order (0.050s)
test_driver.go:213: expecting products from api after creation to be [{0 0x8d4a70 123.4}], found []
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Customers (0.050s)
test_driver.go:213: expecting products from api after creation to be [{0 0x8d4a70 123.4}], found []
--- FAIL: Examples-ORMs/TestSQLAlchemy/SecondRun/RetrieveFromAPIAfterRestart/Products (0.050s)
test_driver.go:213: expecting products from api after creation to be [{0 0x8d4a70 123.4}], found []
```
Please assign, take a look and update the issue accordingly. | non_main | teamcity failed tests on master examples orms testsqlalchemy examples orms testsqlalchemy firstrun examples orms testsqlalchemy secondrun examples orms testsqlalchemy secondrun retrievefromapiafterrestart examples orms testsqlalchemy secondrun retrievefromapiafterrestart order examples orms testsqlalchemy secondrun retrievefromapiafterrestart customers examples orms testsqlalchemy secondrun retrievefromapiafterrestart products the following tests appear to have failed fail examples orms testsqlalchemy null fail examples orms testsqlalchemy firstrun main test go get dial tcp getsockopt connection refused fail examples orms testsqlalchemy secondrun null fail examples orms testsqlalchemy secondrun retrievefromapiafterrestart null fail examples orms testsqlalchemy secondrun retrievefromapiafterrestart order test driver go expecting products from api after creation to be found fail examples orms testsqlalchemy secondrun retrievefromapiafterrestart customers test driver go expecting products from api after creation to be found fail examples orms testsqlalchemy secondrun retrievefromapiafterrestart products test driver go expecting products from api after creation to be found please assign take a look and update the issue accordingly | 0 |
252,572 | 8,037,737,360 | IssuesEvent | 2018-07-30 13:34:13 | glos/GLBuoys | https://api.github.com/repos/glos/GLBuoys | opened | Issue opening asset page for 45161 | High priority User reported | I was checking on the user reported issue with 45161 (muskegon) and I get a message on FF that a 'webpage is making the page not load'. I thought it might be the survey link but it seems to work elsewhere.
I've randomly checked other asset pages and they all appear to open. | 1.0 | Issue opening asset page for 45161 - I was checking on the user reported issue with 45161 (muskegon) and I get a message on FF that a 'webpage is making the page not load'. I thought it might be the survey link but it seems to work elsewhere.
I've randomly checked other asset pages and they all appear to open. | non_main | issue opening asset page for i was checking on the user reported issue with muskegon and i get a message on ff that a webpage is making the page not load i thought it might be the survey link but it seems to work elsewhere i ve randomly checked other asset pages and they all appear to open | 0 |
2,683 | 9,259,623,613 | IssuesEvent | 2019-03-18 00:58:37 | tgstation/tgstation | https://api.github.com/repos/tgstation/tgstation | closed | TRAIT_NOCLONE name is misleading | Maintainability/Hinders improvements | NOCLONE is a misleading name; it doesn't prevent cloning by high-tier scanners or replica pods. Maybe something like HUSKED would be more appropriate?
From what I see, only changeling DNA drain and /obj/machinery/anomalous_crystal/dark_reprise apply the trait. | True | TRAIT_NOCLONE name is misleading - NOCLONE is a misleading name; it doesn't prevent cloning by high-tier scanners or replica pods. Maybe something like HUSKED would be more appropriate?
From what I see, only changeling DNA drain and /obj/machinery/anomalous_crystal/dark_reprise apply the trait. | main | trait noclone name is misleading noclone is a misleading name it doesn t prevent cloning by high tier scanners or replica pods maybe something like husked would be more appropriate from what i see only changeling dna drain and obj machinery anomalous crystal dark reprise apply the trait | 1 |
3,796 | 16,238,831,260 | IssuesEvent | 2021-05-07 06:41:20 | walbourn/directx-vs-templates | https://api.github.com/repos/walbourn/directx-vs-templates | opened | Remove support for Windows SDK () or earlier | maintainence | In the DeviceResources.cpp implementation, I have the following guard:
```
#if defined(__dxgi1_6_h__) && defined(NTDDI_WIN10_RS4)
```
This was to allow the code to build with the Windows 10 SDK (14393, 15063, and 16299). | True | Remove support for Windows SDK () or earlier - In the DeviceResources.cpp implementation, I have the following guard:
```
#if defined(__dxgi1_6_h__) && defined(NTDDI_WIN10_RS4)
```
This was to allow the code to build with the Windows 10 SDK (14393, 15063, and 16299). | main | remove support for windows sdk or earlier in the deviceresources cpp implementation i have the following guard if defined h defined ntddi this was to allow the code to build with the windows sdk and | 1 |
1,257 | 5,332,016,878 | IssuesEvent | 2017-02-15 20:59:15 | ansible/ansible-modules-core | https://api.github.com/repos/ansible/ansible-modules-core | closed | ios_config - binascii.Error: Incorrect padding | affects_2.2 bug_report networking waiting_on_maintainer | <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
ios_config
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0 (devel 17c0f52c96) last updated 2016/09/28 16:38:32 (GMT +000)
lib/ansible/modules/core: (detached HEAD 0f505378c3) last updated 2016/09/23 13:51:09 (GMT +000)
lib/ansible/modules/extras: (detached HEAD 1ade801f65) last updated 2016/09/23 13:51:25 (GMT +000)
config file = {path_clipped}/ansible.cfg
configured module search path = ['{path_clipped}/ansible/library']
```
Note - I know that I'm using month old version of Ansible but I can confirm that I have had this issue a month back itself. So, unless this issue was fixed in last one month, I guess updating might not help.
##### CONFIGURATION
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_\* environment variables).
```
[defaults]
log_path={log_file_path}
host_key_checking = False
```
##### OS / ENVIRONMENT
Running from RHEL 6.8 with remote devices on Cisco IOS.
##### SUMMARY
<!--- Explain the problem briefly -->
When the ios_config module is used to take backup of running config of remote device to local server from which Ansible playbook is running then few devices give incorrect padding error while rest work fine. The same incorrect padding error goes away when same playbook is triggered again.
I Googled around and found this to be problem with known_hosts file so I added host_key_checking false in ansible.cfg but still the issue persists. I can tell you that even after added host_key_checking false I see known_hosts file getting updated when playbook is executed on new devices.
Note - I have seen cases where a playbook when run for XYZ device may be success. 2nd executing of same playbook on same device then resulted in incorrect padding error which means that even though known_hosts was updated during first successful run still during second run something triggered the padding error. This kind of proves that issue is not because of known_hosts file.
Lastly, I only see this issue when I run my playbook for multiple devices. This is when few fail with incorrect padding error and rest succeed. 2nd trigger marks the failed devices as success as well.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
Problem reproduction has been explained in detailed above. One execution of below playbook may result in incorrect padding error for few out of many devices while next executing marks those devices success.
<!--- Paste example playbooks or commands between quotes below -->
```
Below role is called from site.yml
---
- name: Backing up running config
ios_config:
timeout: 60
backup: yes
authorize: yes
provider: "{{ <provider name> }}"
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
Here is the success output of the same playbook for a device XYZ (name changed):
```
{date/ID/PID and other detailed removed} | ok: [XYZ] => {
"backup_path": "{path clipped}",
"changed": false,
"invocation": {
"module_args": {
"after": null,
"auth_pass": null,
"authorize": true,
"backup": true,
"before": null,
"config": null,
"defaults": false,
"force": false,
"host": "XYZ",
"lines": null,
"match": "line",
"parents": null,
"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"port": null,
"provider": {
"authorize": true,
"host": "XYZ",
"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"transport": "{name clipped}",
"username": "{name clipped}"
},
"replace": "line",
"save": false,
"src": null,
"ssh_keyfile": null,
"timeout": 60,
"transport": "{name clipped}",
"use_ssl": true,
"username": "{name clipped}",
"validate_certs": true
}
},
"warnings": []
}
```
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
Here is output with -vvvvv
<!--- Paste verbatim command output between quotes below -->
```
{details like pid etc clipped} | An exception occurred during task execution. The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_5EnQ71/ansible_module_ios_config.py", line 363, in <module>
main()
File "/tmp/ansible_5EnQ71/ansible_module_ios_config.py", line 350, in main
result['__backup__'] = module.config.get_config()
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py", line 125, in config
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py", line 147, in connect
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/ios.py", line 180, in connect
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py", line 228, in connect
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py", line 82, in open
File "{path clipped}ansible/lib/paramiko/client.py", line 173, in load_host_keys
self._host_keys.load(filename)
File "{path clipped}ansible/lib/paramiko/hostkeys.py", line 155, in load
e = HostKeyEntry.from_line(line)
File "{path clipped}/ansible/lib/paramiko/hostkeys.py", line 67, in from_line
key = RSAKey(data=base64.decodestring(key))
File "/usr/lib64/python2.6/base64.py", line 321, in decodestring
return binascii.a2b_base64(s)
binascii.Error: Incorrect padding
{details like pid user etc clipped} | fatal: [XYZ]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_args": {
"authorize": true,
"backup": true,
"provider": {
"authorize": true,
"host": "XYZ",
"password": " ",
"transport": "{details clipped}",
"username": "{details clipped}"
},
"timeout": 60
},
"module_name": "ios_config"
},
"module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_5EnQ71/ansible_module_ios_config.py\", line 363, in <module>\n main()\n File \"/tmp/ansible_5EnQ71/ansible_module_ios_config.py\", line 350, in main\n result['__backup__'] = module.config.get_config()\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py\", line 125, in config\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py\", line 147, in connect\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/ios.py\", line 180, in connect\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py\", line 228, in connect\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py\", line 82, in open\n File \"{details clipped}ansible/lib/paramiko/client.py\", line 173, in load_host_keys\n self._host_keys.load(filename)\n File \"{details clipped}ansible/lib/paramiko/hostkeys.py\", line 155, in load\n e = HostKeyEntry.from_line(line)\n File \"{details clipped}/ansible/lib/paramiko/hostkeys.py\", line 67, in from_line\n key = RSAKey(data=base64.decodestring(key))\n File \"/usr/lib64/python2.6/base64.py\", line 321, in decodestring\n return binascii.a2b_base64(s)\nbinascii.Error: Incorrect padding\n",
"module_stdout": "",
"msg": "MODULE FAILURE"
}
```
| True | ios_config - binascii.Error: Incorrect padding - <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
ios_config
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0 (devel 17c0f52c96) last updated 2016/09/28 16:38:32 (GMT +000)
lib/ansible/modules/core: (detached HEAD 0f505378c3) last updated 2016/09/23 13:51:09 (GMT +000)
lib/ansible/modules/extras: (detached HEAD 1ade801f65) last updated 2016/09/23 13:51:25 (GMT +000)
config file = {path_clipped}/ansible.cfg
configured module search path = ['{path_clipped}/ansible/library']
```
Note - I know that I'm using month old version of Ansible but I can confirm that I have had this issue a month back itself. So, unless this issue was fixed in last one month, I guess updating might not help.
##### CONFIGURATION
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_\* environment variables).
```
[defaults]
log_path={log_file_path}
host_key_checking = False
```
##### OS / ENVIRONMENT
Running from RHEL 6.8 with remote devices on Cisco IOS.
##### SUMMARY
<!--- Explain the problem briefly -->
When the ios_config module is used to take backup of running config of remote device to local server from which Ansible playbook is running then few devices give incorrect padding error while rest work fine. The same incorrect padding error goes away when same playbook is triggered again.
I Googled around and found this to be problem with known_hosts file so I added host_key_checking false in ansible.cfg but still the issue persists. I can tell you that even after added host_key_checking false I see known_hosts file getting updated when playbook is executed on new devices.
Note - I have seen cases where a playbook when run for XYZ device may be success. 2nd executing of same playbook on same device then resulted in incorrect padding error which means that even though known_hosts was updated during first successful run still during second run something triggered the padding error. This kind of proves that issue is not because of known_hosts file.
Lastly, I only see this issue when I run my playbook for multiple devices. This is when few fail with incorrect padding error and rest succeed. 2nd trigger marks the failed devices as success as well.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
Problem reproduction has been explained in detailed above. One execution of below playbook may result in incorrect padding error for few out of many devices while next executing marks those devices success.
<!--- Paste example playbooks or commands between quotes below -->
```
Below role is called from site.yml
---
- name: Backing up running config
ios_config:
timeout: 60
backup: yes
authorize: yes
provider: "{{ <provider name> }}"
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
Here is the success output of the same playbook for a device XYZ (name changed):
```
{date/ID/PID and other detailed removed} | ok: [XYZ] => {
"backup_path": "{path clipped}",
"changed": false,
"invocation": {
"module_args": {
"after": null,
"auth_pass": null,
"authorize": true,
"backup": true,
"before": null,
"config": null,
"defaults": false,
"force": false,
"host": "XYZ",
"lines": null,
"match": "line",
"parents": null,
"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"port": null,
"provider": {
"authorize": true,
"host": "XYZ",
"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
"transport": "{name clipped}",
"username": "{name clipped}"
},
"replace": "line",
"save": false,
"src": null,
"ssh_keyfile": null,
"timeout": 60,
"transport": "{name clipped}",
"use_ssl": true,
"username": "{name clipped}",
"validate_certs": true
}
},
"warnings": []
}
```
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
Here is output with -vvvvv
<!--- Paste verbatim command output between quotes below -->
```
{details like pid etc clipped} | An exception occurred during task execution. The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_5EnQ71/ansible_module_ios_config.py", line 363, in <module>
main()
File "/tmp/ansible_5EnQ71/ansible_module_ios_config.py", line 350, in main
result['__backup__'] = module.config.get_config()
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py", line 125, in config
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py", line 147, in connect
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/ios.py", line 180, in connect
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py", line 228, in connect
File "/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py", line 82, in open
File "{path clipped}ansible/lib/paramiko/client.py", line 173, in load_host_keys
self._host_keys.load(filename)
File "{path clipped}ansible/lib/paramiko/hostkeys.py", line 155, in load
e = HostKeyEntry.from_line(line)
File "{path clipped}/ansible/lib/paramiko/hostkeys.py", line 67, in from_line
key = RSAKey(data=base64.decodestring(key))
File "/usr/lib64/python2.6/base64.py", line 321, in decodestring
return binascii.a2b_base64(s)
binascii.Error: Incorrect padding
{details like pid user etc clipped} | fatal: [XYZ]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_args": {
"authorize": true,
"backup": true,
"provider": {
"authorize": true,
"host": "XYZ",
"password": " ",
"transport": "{details clipped}",
"username": "{details clipped}"
},
"timeout": 60
},
"module_name": "ios_config"
},
"module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_5EnQ71/ansible_module_ios_config.py\", line 363, in <module>\n main()\n File \"/tmp/ansible_5EnQ71/ansible_module_ios_config.py\", line 350, in main\n result['__backup__'] = module.config.get_config()\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py\", line 125, in config\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/network.py\", line 147, in connect\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/ios.py\", line 180, in connect\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py\", line 228, in connect\n File \"/tmp/ansible_5EnQ71/ansible_modlib.zip/ansible/module_utils/shell.py\", line 82, in open\n File \"{details clipped}ansible/lib/paramiko/client.py\", line 173, in load_host_keys\n self._host_keys.load(filename)\n File \"{details clipped}ansible/lib/paramiko/hostkeys.py\", line 155, in load\n e = HostKeyEntry.from_line(line)\n File \"{details clipped}/ansible/lib/paramiko/hostkeys.py\", line 67, in from_line\n key = RSAKey(data=base64.decodestring(key))\n File \"/usr/lib64/python2.6/base64.py\", line 321, in decodestring\n return binascii.a2b_base64(s)\nbinascii.Error: Incorrect padding\n",
"module_stdout": "",
"msg": "MODULE FAILURE"
}
```
| main | ios config binascii error incorrect padding issue type bug report component name ios config ansible version ansible devel last updated gmt lib ansible modules core detached head last updated gmt lib ansible modules extras detached head last updated gmt config file path clipped ansible cfg configured module search path note i know that i m using month old version of ansible but i can confirm that i have had this issue a month back itself so unless this issue was fixed in last one month i guess updating might not help configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables log path log file path host key checking false os environment running from rhel with remote devices on cisco ios summary when the ios config module is used to take backup of running config of remote device to local server from which ansible playbook is running then few devices give incorrect padding error while rest work fine the same incorrect padding error goes away when same playbook is triggered again i googled around and found this to be problem with known hosts file so i added host key checking false in ansible cfg but still the issue persists i can tell you that even after added host key checking false i see known hosts file getting updated when playbook is executed on new devices note i have seen cases where a playbook when run for xyz device may be success executing of same playbook on same device then resulted in incorrect padding error which means that even though known hosts was updated during first successful run still during second run something triggered the padding error this kind of proves that issue is not because of known hosts file lastly i only see this issue when i run my playbook for multiple devices this is when few fail with incorrect padding error and rest succeed trigger marks the failed devices as success as well steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used problem reproduction has been explained in detailed above one execution of below playbook may result in incorrect padding error for few out of many devices while next executing marks those devices success below role is called from site yml name backing up running config ios config timeout backup yes authorize yes provider expected results here is the success output of the same playbook for a device xyz name changed date id pid and other detailed removed ok backup path path clipped changed false invocation module args after null auth pass null authorize true backup true before null config null defaults false force false host xyz lines null match line parents null password value specified in no log parameter port null provider authorize true host xyz password value specified in no log parameter transport name clipped username name clipped replace line save false src null ssh keyfile null timeout transport name clipped use ssl true username name clipped validate certs true warnings actual results here is output with vvvvv details like pid etc clipped an exception occurred during task execution the full traceback is traceback most recent call last file tmp ansible ansible module ios config py line in main file tmp ansible ansible module ios config py line in main result module config get config file tmp ansible ansible modlib zip ansible module utils network py line in config file tmp ansible ansible modlib zip ansible module utils network py line in connect file tmp ansible ansible modlib zip ansible module utils ios py line in connect file tmp ansible ansible modlib zip ansible module utils shell py line in connect file tmp ansible ansible modlib zip ansible module utils shell py line in open file path clipped ansible lib paramiko client py line in load host keys self host keys load filename file path clipped ansible lib paramiko hostkeys py line in load e hostkeyentry from line line file path clipped ansible lib paramiko hostkeys py line in from line key rsakey data decodestring key file usr py line in decodestring return binascii s binascii error incorrect padding details like pid user etc clipped fatal failed changed false failed true invocation module args authorize true backup true provider authorize true host xyz password transport details clipped username details clipped timeout module name ios config module stderr traceback most recent call last n file tmp ansible ansible module ios config py line in n main n file tmp ansible ansible module ios config py line in main n result module config get config n file tmp ansible ansible modlib zip ansible module utils network py line in config n file tmp ansible ansible modlib zip ansible module utils network py line in connect n file tmp ansible ansible modlib zip ansible module utils ios py line in connect n file tmp ansible ansible modlib zip ansible module utils shell py line in connect n file tmp ansible ansible modlib zip ansible module utils shell py line in open n file details clipped ansible lib paramiko client py line in load host keys n self host keys load filename n file details clipped ansible lib paramiko hostkeys py line in load n e hostkeyentry from line line n file details clipped ansible lib paramiko hostkeys py line in from line n key rsakey data decodestring key n file usr py line in decodestring n return binascii s nbinascii error incorrect padding n module stdout msg module failure | 1 |
2,211 | 7,809,175,521 | IssuesEvent | 2018-06-11 23:03:22 | react-navigation/react-navigation | https://api.github.com/repos/react-navigation/react-navigation | closed | .toggleDrawer() not working / missing documentation on how to use it in nested stacks | needs response from maintainer | In addition to this closed issue:
[https://github.com/react-navigation/react-navigation/issues/4266](https://github.com/react-navigation/react-navigation/issues/4266)
I'm facing difficulty in code and method that used to work in version 1.4.0.
### Current Behavior
in navigation.toggleDrawer() and error occurred - undefined is not function.
### Expected Behavior
The drawer should toggle
### How to reproduce
- The code example can be found in this snack:
[https://snack.expo.io/@eranbo/react-navigation---nested-stacks-header-left-not-working](https://snack.expo.io/@eranbo/react-navigation---nested-stacks-header-left-not-working)
- just press the hamburger icon for open and close the drawer
### Your Environment
| software | version
| ---------------- | -------
| react-navigation | 2.0.1
| react-native | 0.55.3
| node | 8.11.1
| npm or yarn | yarn 1.6.0
| True | .toggleDrawer() not working / missing documentation on how to use it in nested stacks - In addition to this closed issue:
[https://github.com/react-navigation/react-navigation/issues/4266](https://github.com/react-navigation/react-navigation/issues/4266)
I'm facing difficulty in code and method that used to work in version 1.4.0.
### Current Behavior
in navigation.toggleDrawer() and error occurred - undefined is not function.
### Expected Behavior
The drawer should toggle
### How to reproduce
- The code example can be found in this snack:
[https://snack.expo.io/@eranbo/react-navigation---nested-stacks-header-left-not-working](https://snack.expo.io/@eranbo/react-navigation---nested-stacks-header-left-not-working)
- just press the hamburger icon for open and close the drawer
### Your Environment
| software | version
| ---------------- | -------
| react-navigation | 2.0.1
| react-native | 0.55.3
| node | 8.11.1
| npm or yarn | yarn 1.6.0
| main | toggledrawer not working missing documentation on how to use it in nested stacks in addition to this closed issue i m facing difficulty in code and method that used to work in version current behavior in navigation toggledrawer and error occurred undefined is not function expected behavior the drawer should toggle how to reproduce the code example can be found in this snack just press the hamburger icon for open and close the drawer your environment software version react navigation react native node npm or yarn yarn | 1 |
150,587 | 23,684,150,143 | IssuesEvent | 2022-08-29 03:34:02 | filecoin-project/venus | https://api.github.com/repos/filecoin-project/venus | closed | [venus-messager] 消息增加uuid? | design C-enhancement | ### 链服务模块 / Chain Service Components
- [ ] venus
- [ ] venus-auth
- [ ] venus-gateway
- [X] venus-messager
- [ ] venus-miner
- [ ] 文档 / docs
### 订单服务模块 / Deal Service Components
- [ ] venus-market
- [ ] 文档 / docs
### 算力服务模块 / Storage Power Service Components
- [ ] venus-sector-manager
- [ ] venus-worker
- [ ] 文档 / docs
### 描述 / Description
待评估，venus可能不适用；Lotus给miner发送的消息带上uuid，不知道是否需要借鉴，还是完全不适用。
关联：
- [ ] https://github.com/filecoin-project/lotus/pull/9174 | 1.0 | [venus-messager] 消息增加uuid? - ### 链服务模块 / Chain Service Components
- [ ] venus
- [ ] venus-auth
- [ ] venus-gateway
- [X] venus-messager
- [ ] venus-miner
- [ ] 文档 / docs
### 订单服务模块 / Deal Service Components
- [ ] venus-market
- [ ] 文档 / docs
### 算力服务模块 / Storage Power Service Components
- [ ] venus-sector-manager
- [ ] venus-worker
- [ ] 文档 / docs
### 描述 / Description
待评估，venus可能不适用；Lotus给miner发送的消息带上uuid，不知道是否需要借鉴，还是完全不适用。
关联：
- [ ] https://github.com/filecoin-project/lotus/pull/9174 | non_main | 消息增加uuid 链服务模块 chain service components venus venus auth venus gateway venus messager venus miner 文档 docs 订单服务模块 deal service components venus market 文档 docs 算力服务模块 storage power service components venus sector manager venus worker 文档 docs 描述 description 待评估，venus可能不适用；lotus给miner发送的消息带上uuid，不知道是否需要借鉴，还是完全不适用。 关联： | 0 |
255,509 | 27,484,982,641 | IssuesEvent | 2023-03-04 01:42:54 | panasalap/linux-4.1.15 | https://api.github.com/repos/panasalap/linux-4.1.15 | closed | CVE-2018-5995 (Medium) detected in linux179e72b561d3d331c850e1a5779688d7a7de5246 - autoclosed | security vulnerability | ## CVE-2018-5995 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux179e72b561d3d331c850e1a5779688d7a7de5246</b></p></summary>
<p>
<p>Linux kernel stable tree mirror</p>
<p>Library home page: <a href=https://github.com/gregkh/linux.git>https://github.com/gregkh/linux.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/vsprintf.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/vsprintf.c</b>
</p>
</details>
<p></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>
The pcpu_embed_first_chunk function in mm/percpu.c in the Linux kernel through 4.14.14 allows local users to obtain sensitive address information by reading dmesg data from a "pages/cpu" printk call.
<p>Publish Date: 2018-08-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-5995>CVE-2018-5995</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5995">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5995</a></p>
<p>Release Date: 2018-08-07</p>
<p>Fix Resolution: v4.15-rc2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-5995 (Medium) detected in linux179e72b561d3d331c850e1a5779688d7a7de5246 - autoclosed - ## CVE-2018-5995 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux179e72b561d3d331c850e1a5779688d7a7de5246</b></p></summary>
<p>
<p>Linux kernel stable tree mirror</p>
<p>Library home page: <a href=https://github.com/gregkh/linux.git>https://github.com/gregkh/linux.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/vsprintf.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/lib/vsprintf.c</b>
</p>
</details>
<p></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>
The pcpu_embed_first_chunk function in mm/percpu.c in the Linux kernel through 4.14.14 allows local users to obtain sensitive address information by reading dmesg data from a "pages/cpu" printk call.
<p>Publish Date: 2018-08-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-5995>CVE-2018-5995</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5995">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5995</a></p>
<p>Release Date: 2018-08-07</p>
<p>Fix Resolution: v4.15-rc2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_main | cve medium detected in autoclosed cve medium severity vulnerability vulnerable library linux kernel stable tree mirror library home page a href found in head commit a href found in base branch master vulnerable source files lib vsprintf c lib vsprintf c vulnerability details the pcpu embed first chunk function in mm percpu c in the linux kernel through allows local users to obtain sensitive address information by reading dmesg data from a pages cpu printk call publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high 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 step up your open source security game with mend | 0 |
73,238 | 32,002,471,614 | IssuesEvent | 2023-09-21 13:05:42 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Logic App trigger: When a resource event occurs - Azure Event Grid Portal Issue | service-bus-messaging/svc triaged cxp doc-enhancement Pri3 | Hello, I am following this link below:
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#receive-messages-by-using-logic-apps
On this section: Add a step receive messages from Service Bus via Event Grid
when I am to create a trigger for Azure Event Grid: Select When a resource event occurs - Azure Event Grid
There is inconsistency between this article and azure portal page.
Per Article I should first select the azure subscription but in the portal it first shows the Resource Type and even worse, the Resource Type Dropdown list does not populated which makes the portal page useless.
---
#### Document Details
⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.*
* ID: de93e314-ae26-29c3-1594-377081ddb002
* Version Independent ID: a65af49c-ba04-b76a-b510-a8646d5056e6
* Content: [Handle Service Bus events via Event Grid using Azure Logic Apps - Azure Service Bus](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#receive-messages-by-using-logic-apps)
* Content Source: [articles/service-bus-messaging/service-bus-to-event-grid-integration-example.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-example.md)
* Service: **service-bus-messaging**
* GitHub Login: @spelluru
* Microsoft Alias: **spelluru
| 1.0 | Logic App trigger: When a resource event occurs - Azure Event Grid Portal Issue - Hello, I am following this link below:
https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#receive-messages-by-using-logic-apps
On this section: Add a step receive messages from Service Bus via Event Grid
when I am to create a trigger for Azure Event Grid: Select When a resource event occurs - Azure Event Grid
There is inconsistency between this article and azure portal page.
Per Article I should first select the azure subscription but in the portal it first shows the Resource Type and even worse, the Resource Type Dropdown list does not populated which makes the portal page useless.
---
#### Document Details
⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.*
* ID: de93e314-ae26-29c3-1594-377081ddb002
* Version Independent ID: a65af49c-ba04-b76a-b510-a8646d5056e6
* Content: [Handle Service Bus events via Event Grid using Azure Logic Apps - Azure Service Bus](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example#receive-messages-by-using-logic-apps)
* Content Source: [articles/service-bus-messaging/service-bus-to-event-grid-integration-example.md](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/service-bus-messaging/service-bus-to-event-grid-integration-example.md)
* Service: **service-bus-messaging**
* GitHub Login: @spelluru
* Microsoft Alias: **spelluru
| non_main | logic app trigger when a resource event occurs azure event grid portal issue hello i am following this link below on this section add a step receive messages from service bus via event grid when i am to create a trigger for azure event grid select when a resource event occurs azure event grid there is inconsistency between this article and azure portal page per article i should first select the azure subscription but in the portal it first shows the resource type and even worse the resource type dropdown list does not populated which makes the portal page useless document details ⚠ do not edit this section it is required for learn microsoft com ➟ github issue linking id version independent id content content source service service bus messaging github login spelluru microsoft alias spelluru | 0 |
104,814 | 22,757,190,939 | IssuesEvent | 2022-07-07 17:36:25 | pulumi/pulumi | https://api.github.com/repos/pulumi/pulumi | closed | Python: Invalid docstring generated | kind/bug area/codegen resolution/fixed | A pulumi-azuredevops build is failing with what appears to be an invalid docstring: https://github.com/pulumi/pulumi-azuredevops/pull/102
Per @nimbinatus:
> Here: https://github.com/pulumi/pulumi/blob/master/pkg/codegen/python/gen.go#L324 <-- that needs a better special character set. I'd consider using the set from https://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals (in the table a bit further down) to be more complete, and perhaps see if the system takes regex (replace n many forward slashes with twice as many) | 1.0 | Python: Invalid docstring generated - A pulumi-azuredevops build is failing with what appears to be an invalid docstring: https://github.com/pulumi/pulumi-azuredevops/pull/102
Per @nimbinatus:
> Here: https://github.com/pulumi/pulumi/blob/master/pkg/codegen/python/gen.go#L324 <-- that needs a better special character set. I'd consider using the set from https://docs.python.org/3/reference/lexical_analysis.html#string-and-bytes-literals (in the table a bit further down) to be more complete, and perhaps see if the system takes regex (replace n many forward slashes with twice as many) | non_main | python invalid docstring generated a pulumi azuredevops build is failing with what appears to be an invalid docstring per nimbinatus here that needs a better special character set i d consider using the set from in the table a bit further down to be more complete and perhaps see if the system takes regex replace n many forward slashes with twice as many | 0 |
5,134 | 26,167,662,937 | IssuesEvent | 2023-01-01 13:52:04 | tgstation/tgstation | https://api.github.com/repos/tgstation/tgstation | closed | `text2access` still operates under the assumption accesses are numbers | Maintainability/Hinders improvements Oversight | ## Reproduction:
https://github.com/tgstation/tgstation/blob/8bb6cb8f5c16b74af3b3150403284542c6fd3a9e/code/modules/jobs/access.dm#L56-L76
`text2access` converts a string access text into a list of accesses
A long time ago, you would pass in a string like `"15;23;24"` you get `list(15, 23, 34)`
But now our accesses are strings, not numbers - If you set it up like `"robotics;science"`, you get `list()`
Some of our maps still use the `_txt` system to set accesses, namely on windoors, which means these are all incorrect.
(Well, some of these are incorrect in another way. They use a list instead of a string. Wrong var)
| True | `text2access` still operates under the assumption accesses are numbers - ## Reproduction:
https://github.com/tgstation/tgstation/blob/8bb6cb8f5c16b74af3b3150403284542c6fd3a9e/code/modules/jobs/access.dm#L56-L76
`text2access` converts a string access text into a list of accesses
A long time ago, you would pass in a string like `"15;23;24"` you get `list(15, 23, 34)`
But now our accesses are strings, not numbers - If you set it up like `"robotics;science"`, you get `list()`
Some of our maps still use the `_txt` system to set accesses, namely on windoors, which means these are all incorrect.
(Well, some of these are incorrect in another way. They use a list instead of a string. Wrong var)
| main | still operates under the assumption accesses are numbers reproduction converts a string access text into a list of accesses a long time ago you would pass in a string like you get list but now our accesses are strings not numbers if you set it up like robotics science you get list some of our maps still use the txt system to set accesses namely on windoors which means these are all incorrect well some of these are incorrect in another way they use a list instead of a string wrong var | 1 |
5,067 | 25,948,146,139 | IssuesEvent | 2022-12-17 07:45:04 | bazelbuild/intellij | https://api.github.com/repos/bazelbuild/intellij | closed | I cannot jump to thirdparty sources in Clion+bazel condition. | product: CLion lang: c++ type: user support awaiting-maintainer | #### Description of the issue. Please be specific.
#### What's the simplest set of steps to reproduce this issue? Please provide an example project, if possible.
#### Version information
CLion: 2022.3
Platform: Mac OS X 13.0.1
Bazel plugin: 2022.11.07.0.1-api-version-223
Bazel: 5.3.2
<img width="1512" alt="image" src="https://user-images.githubusercontent.com/118719392/206910491-358cab9e-5add-4f0e-8906-214eb2af4a2e.png"> | True | I cannot jump to thirdparty sources in Clion+bazel condition. - #### Description of the issue. Please be specific.
#### What's the simplest set of steps to reproduce this issue? Please provide an example project, if possible.
#### Version information
CLion: 2022.3
Platform: Mac OS X 13.0.1
Bazel plugin: 2022.11.07.0.1-api-version-223
Bazel: 5.3.2
<img width="1512" alt="image" src="https://user-images.githubusercontent.com/118719392/206910491-358cab9e-5add-4f0e-8906-214eb2af4a2e.png"> | main | i cannot jump to thirdparty sources in clion bazel condition description of the issue please be specific what s the simplest set of steps to reproduce this issue please provide an example project if possible version information clion platform mac os x bazel plugin api version bazel img width alt image src | 1 |
565,382 | 16,760,587,118 | IssuesEvent | 2021-06-13 17:53:05 | bounswe/2021SpringGroup3 | https://api.github.com/repos/bounswe/2021SpringGroup3 | closed | Implement API functionality: Set Profile Picture | Component: Backend Priority: Medium Status: Review Needed Type: Feature | Please implement a function for setting random profile picture for users. | 1.0 | Implement API functionality: Set Profile Picture - Please implement a function for setting random profile picture for users. | non_main | implement api functionality set profile picture please implement a function for setting random profile picture for users | 0 |
48,648 | 5,966,014,044 | IssuesEvent | 2017-05-30 13:07:18 | mozilla/fxa-content-server | https://api.github.com/repos/mozilla/fxa-content-server | closed | Failing functional test on TeamCity - firefox on any platform: upgrade storage formats - Upgrade from account that has `accountData` | P1 tests waffle:review | 3 failures in a row is no longer flaky. | 1.0 | Failing functional test on TeamCity - firefox on any platform: upgrade storage formats - Upgrade from account that has `accountData` - 3 failures in a row is no longer flaky. | non_main | failing functional test on teamcity firefox on any platform upgrade storage formats upgrade from account that has accountdata failures in a row is no longer flaky | 0 |
420,169 | 12,234,116,559 | IssuesEvent | 2020-05-04 12:54:23 | getkirby/kirby | https://api.github.com/repos/getkirby/kirby | closed | Option array notation does not work for plugin options | priority: high 🔥 type: bug 🐛 | **Describe the bug**
```
'distantnative' => [
'retour' => [
'option' => 'value'
]
]
```
Those options are not actually available via `option('distantnative.retour.ignore')`
if I use the dot notation in flat array, it works:
```
'distantnative.retour.option' => 'value'
```
**Kirby Version**
3.3.1
| 1.0 | Option array notation does not work for plugin options - **Describe the bug**
```
'distantnative' => [
'retour' => [
'option' => 'value'
]
]
```
Those options are not actually available via `option('distantnative.retour.ignore')`
if I use the dot notation in flat array, it works:
```
'distantnative.retour.option' => 'value'
```
**Kirby Version**
3.3.1
| non_main | option array notation does not work for plugin options describe the bug distantnative retour option value those options are not actually available via option distantnative retour ignore if i use the dot notation in flat array it works distantnative retour option value kirby version | 0 |
282,017 | 24,445,287,925 | IssuesEvent | 2022-10-06 17:24:52 | mozilla-mobile/focus-android | https://api.github.com/repos/mozilla-mobile/focus-android | opened | Investigate permanent UI test failure EnhancedTrackingProtectionSettingsTest#blockSocialTrackersTest | eng:ui-test | Firebase Test Lab Run (10/06): [here](https://console.firebase.google.com/u/0/project/moz-focus-android/testlab/histories/bh.2189b040bbce6d5a/matrices/8897732563285886389/executions/bs.259e90a0a82fa339/testcases/2/test-cases)
```Kotlin
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertTrue(Assert.java:53)
at org.mozilla.focus.activity.robots.BrowserRobot.verifyTrackingProtectionAlert(BrowserRobot.kt:57)
at org.mozilla.focus.activity.EnhancedTrackingProtectionSettingsTest$blockSocialTrackersTest$4.invoke(EnhancedTrackingProtectionSettingsTest.kt:180)
at org.mozilla.focus.activity.EnhancedTrackingProtectionSettingsTest$blockSocialTrackersTest$4.invoke(EnhancedTrackingProtectionSettingsTest.kt:179)
at org.mozilla.focus.activity.robots.SearchRobot$Transition.loadPage(SearchRobot.kt:101)
at org.mozilla.focus.activity.EnhancedTrackingProtectionSettingsTest.blockSocialTrackersTest(EnhancedTrackingProtectionSettingsTest.kt:179)
```
Based on testing locally, the alert never shows. Not sure if it's a JavaScript page logic issue or a change in social tracker blocking behaviour. | 1.0 | Investigate permanent UI test failure EnhancedTrackingProtectionSettingsTest#blockSocialTrackersTest - Firebase Test Lab Run (10/06): [here](https://console.firebase.google.com/u/0/project/moz-focus-android/testlab/histories/bh.2189b040bbce6d5a/matrices/8897732563285886389/executions/bs.259e90a0a82fa339/testcases/2/test-cases)
```Kotlin
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertTrue(Assert.java:53)
at org.mozilla.focus.activity.robots.BrowserRobot.verifyTrackingProtectionAlert(BrowserRobot.kt:57)
at org.mozilla.focus.activity.EnhancedTrackingProtectionSettingsTest$blockSocialTrackersTest$4.invoke(EnhancedTrackingProtectionSettingsTest.kt:180)
at org.mozilla.focus.activity.EnhancedTrackingProtectionSettingsTest$blockSocialTrackersTest$4.invoke(EnhancedTrackingProtectionSettingsTest.kt:179)
at org.mozilla.focus.activity.robots.SearchRobot$Transition.loadPage(SearchRobot.kt:101)
at org.mozilla.focus.activity.EnhancedTrackingProtectionSettingsTest.blockSocialTrackersTest(EnhancedTrackingProtectionSettingsTest.kt:179)
```
Based on testing locally, the alert never shows. Not sure if it's a JavaScript page logic issue or a change in social tracker blocking behaviour. | non_main | investigate permanent ui test failure enhancedtrackingprotectionsettingstest blocksocialtrackerstest firebase test lab run kotlin java lang assertionerror at org junit assert fail assert java at org junit assert asserttrue assert java at org junit assert asserttrue assert java at org mozilla focus activity robots browserrobot verifytrackingprotectionalert browserrobot kt at org mozilla focus activity enhancedtrackingprotectionsettingstest blocksocialtrackerstest invoke enhancedtrackingprotectionsettingstest kt at org mozilla focus activity enhancedtrackingprotectionsettingstest blocksocialtrackerstest invoke enhancedtrackingprotectionsettingstest kt at org mozilla focus activity robots searchrobot transition loadpage searchrobot kt at org mozilla focus activity enhancedtrackingprotectionsettingstest blocksocialtrackerstest enhancedtrackingprotectionsettingstest kt based on testing locally the alert never shows not sure if it s a javascript page logic issue or a change in social tracker blocking behaviour | 0 |
120,643 | 15,788,453,948 | IssuesEvent | 2021-04-01 20:49:24 | NCIOCPL/ncids | https://api.github.com/repos/NCIOCPL/ncids | opened | Design: Cards | feature:cards track: design | > **ESTIMATE** Story Points TBD
> Feature/Main User Story: [Enter user story ticket association here]
### Description of Design request:
##
### List of sub-tasks:
*Add links to related tickets below*
- [ ] Sub-Task
- [ ] Sub-Task
- [ ] Sub-Task
##
### Design Functionality:
*Describe how the design should function, e.g. color changes on hover*
1. Specification
2. Specification
3. Specification
##
### Design specs / InVision:
*Design specs indicated in the InVision links below. Please view in the inspect mode along with the comments panel*
1. https://github.com/NCIOCPL/ncids/issues/25
2. InVision link
3. InVision link
##
### Assets:
* Feature: JIRA Ticket #
* Mockups: *Here goes a URL to or the name of the mockup(s) in inVision*
* Web Page: *Here goes a URL to an existing web page*
##
### Design Research & Inspiration:
*Space to add inspiration, moodboards,etc*
##
| 1.0 | Design: Cards - > **ESTIMATE** Story Points TBD
> Feature/Main User Story: [Enter user story ticket association here]
### Description of Design request:
##
### List of sub-tasks:
*Add links to related tickets below*
- [ ] Sub-Task
- [ ] Sub-Task
- [ ] Sub-Task
##
### Design Functionality:
*Describe how the design should function, e.g. color changes on hover*
1. Specification
2. Specification
3. Specification
##
### Design specs / InVision:
*Design specs indicated in the InVision links below. Please view in the inspect mode along with the comments panel*
1. https://github.com/NCIOCPL/ncids/issues/25
2. InVision link
3. InVision link
##
### Assets:
* Feature: JIRA Ticket #
* Mockups: *Here goes a URL to or the name of the mockup(s) in inVision*
* Web Page: *Here goes a URL to an existing web page*
##
### Design Research & Inspiration:
*Space to add inspiration, moodboards,etc*
##
| non_main | design cards estimate story points tbd feature main user story description of design request list of sub tasks add links to related tickets below sub task sub task sub task design functionality describe how the design should function e g color changes on hover specification specification specification design specs invision design specs indicated in the invision links below please view in the inspect mode along with the comments panel invision link invision link assets feature jira ticket mockups here goes a url to or the name of the mockup s in invision web page here goes a url to an existing web page design research inspiration space to add inspiration moodboards etc | 0 |
75,549 | 20,870,415,296 | IssuesEvent | 2022-03-22 11:23:44 | harness-software/wp-graphql-gravity-forms | https://api.github.com/repos/harness-software/wp-graphql-gravity-forms | closed | [Bug] PHP Fatal error: Uncaught Error: Failed opening required .../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php | bug 🐛 build scripts 👷♂️ | <!--
Thank you for taking the time to report a possible bug. Remember, an issue is not the place to ask questions. You can use Slack for that, or start a topic in Github Discussions.
-->
## Describe the bug
<!-- Please write a clear and concise description of the bug. -->
Installed and activated WPGraphQL.
Installed and activated Gravity Forms.
Downloaded the repo zip and uploaded to WordPress and activated.
Get the following WordPress error (There has been a critical error on this website. Please check your site admin email inbox for instructions.):
```
PHP Fatal error: Uncaught Error: Failed opening required '/nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/../yahnis-elsts/plugin-update-checker/load-v4p11.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php:78\nStack trace:\n#0 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php(61): composerRequire0e8f6c0730ce438688b3484326e9667b('49a1299791c25c6...', '/nas/content/li...')\n#1 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/autoload.php(7): ComposerAutoloaderInit0e8f6c0730ce438688b3484326e9667b::getLoader()\n#2 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(55): require_once('/nas/content/li...')\n#3 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(34): WPGraphQL\\GF\\GF->includes()\n#4 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/wp-graphql-gravity-forms.php(90): WPGraphQL\\GF\\GF::instance()\n#5 /nas/content/live/../wp-includes/class-wp-hook.php(307): gf_graphql_init(Object(WPGraphQL))\n#6 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)\n#7 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#8 /nas/content/live/../wp-content/plugins/wp-graphql/src/WPGraphQL.php(255): do_action('graphql_init', Object(WPGraphQL))\n#9 /nas/content/live/../wp-includes/class-wp-hook.php(307): WPGraphQL->{closure}('')\n#10 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)\n#11 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#12 /nas/content/live/../wp-settings.php(565): do_action('after_setup_the...')\n#13 /nas/content/live/../wp-config.php(119): require_once('/nas/content/li...')\n#14 /nas/content/live/../wp-load.php(50): require_once('/nas/content/li...')\n#15 /nas/content/live/../wp-admin/admin.php(34): require_once('/nas/content/li...')\n#16 /nas/content/live/../wp-admin/plugins.php(10): require_once('/nas/content/li...')\n#17 {main}\n thrown in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php on line 78, referer: https://...wpengine.com/wp-admin/update.php?action=upload-plugin
PHP Fatal error: Uncaught Error: Failed opening required '/nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/../yahnis-elsts/plugin-update-checker/load-v4p11.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php:78\nStack trace:\n#0 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php(61): composerRequire0e8f6c0730ce438688b3484326e9667b('49a1299791c25c6...', '/nas/content/li...')\n#1 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/autoload.php(7): ComposerAutoloaderInit0e8f6c0730ce438688b3484326e9667b::getLoader()\n#2 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(55): require_once('/nas/content/li...')\n#3 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(34): WPGraphQL\\GF\\GF->includes()\n#4 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/wp-graphql-gravity-forms.php(90): WPGraphQL\\GF\\GF::instance()\n#5 /nas/content/live/../wp-includes/class-wp-hook.php(307): gf_graphql_init(Object(WPGraphQL))\n#6 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)\n#7 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#8 /nas/content/live/../wp-content/plugins/wp-graphql/src/WPGraphQL.php(255): do_action('graphql_init', Object(WPGraphQL))\n#9 /nas/content/live/../wp-includes/class-wp-hook.php(307): WPGraphQL->{closure}('')\n#10 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)\n#11 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#12 /nas/content/live/../wp-settings.php(565): do_action('after_setup_the...')\n#13 /nas/content/live/../wp-config.php(119): require_once('/nas/content/li...')\n#14 /nas/content/live/../wp-load.php(50): require_once('/nas/content/li...')\n#15 /nas/content/live/../wp-admin/admin.php(34): require_once('/nas/content/li...')\n#16 /nas/content/live/../wp-admin/update.php(16): require_once('/nas/content/li...')\n#17 {main}\n thrown in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php on line 78, referer: https://...wpengine.com/wp-admin/plugin-install.php?s=wpgraphql&tab=search&type=term
PHP Fatal error: Uncaught Error: Failed opening required '/nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/../yahnis-elsts/plugin-update-checker/load-v4p11.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php:78\nStack trace:\n#0 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php(61): composerRequire0e8f6c0730ce438688b3484326e9667b('49a1299791c25c6...', '/nas/content/li...')\n#1 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/autoload.php(7): ComposerAutoloaderInit0e8f6c0730ce438688b3484326e9667b::getLoader()\n#2 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(55): require_once('/nas/content/li...')\n#3 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(34): WPGraphQL\\GF\\GF->includes()\n#4 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/wp-graphql-gravity-forms.php(90): WPGraphQL\\GF\\GF::instance()\n#5 /nas/content/live/../wp-includes/class-wp-hook.php(307): gf_graphql_init(Object(WPGraphQL))\n#6 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)\n#7 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#8 /nas/content/live/../wp-content/plugins/wp-graphql/src/WPGraphQL.php(255): do_action('graphql_init', Object(WPGraphQL))\n#9 /nas/content/live/../wp-includes/class-wp-hook.php(307): WPGraphQL->{closure}('')\n#10 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)\n#11 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#12 /nas/content/live/../wp-settings.php(565): do_action('after_setup_the...')\n#13 /nas/content/live/../wp-config.php(119): require_once('/nas/content/li...')\n#14 /nas/content/live/../wp-load.php(50): require_once('/nas/content/li...')\n#15 /nas/content/live/../wp-admin/admin.php(34): require_once('/nas/content/li...')\n#16 /nas/content/live/../wp-admin/plugin-install.php(16): require_once('/nas/content/li...')\n#17 {main}\n thrown in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php on line 78, referer: https://...wpengine.com/wp-admin/plugins.php
```
## To Reproduce
<!--
Please list the all the steps needed to reproduce the bug. Ideally, this should be in the form of a GraphQL snippet that can be used in GraphiQL IDE.
-->
1. Install & activate WPGraphQL.
2. Install & activate Gravity Forms and any supported addons.
3. Download the zip of this repository and upload it to your WordPress install, and activate the plugin.
## Expected behavior
<!--- Please write a clear and concise description of what you expected to happen. -->
Plugin to not crash WordPress.
## Additional context
Add any other context about the problem here.
Hosted on WPEngine.
### Technical Info
* WordPress version: 5.9.2
* WPGraphQL version: 1.7.2
* Gravity Forms version: 2.5.16
* WPGraphQL for Gravity Forms version: v0.10.5
* Other relevant frameworks/plugins:
<html>
<body>
<!--StartFragment-->
Plugin Name | Plugin Version
-- | --
Advanced Custom Fields PRO | by Delicious Brains - 5.12
Atlas Content Modeler | by WP Engine - 0.14.0
Code Snippets | by Code Snippets Pro - 2.14.3
FaustWP | by WP Engine - 0.7.6
Genesis Custom Blocks | by Genesis Custom Blocks - 1.4.0
WordPress Importer | by wordpressdotorg - 0.7
WP GraphQL | by WPGraphQL - 1.7.2
WPGraphQL for Advanced Custom Fields | by WPGraphQL, Jason Bahl - 0.5.3
WP GraphQL Gutenberg | by pristas-peter - 0.3.11
<!--EndFragment-->
</body>
</html> | 1.0 | [Bug] PHP Fatal error: Uncaught Error: Failed opening required .../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php - <!--
Thank you for taking the time to report a possible bug. Remember, an issue is not the place to ask questions. You can use Slack for that, or start a topic in Github Discussions.
-->
## Describe the bug
<!-- Please write a clear and concise description of the bug. -->
Installed and activated WPGraphQL.
Installed and activated Gravity Forms.
Downloaded the repo zip and uploaded to WordPress and activated.
Get the following WordPress error (There has been a critical error on this website. Please check your site admin email inbox for instructions.):
```
PHP Fatal error: Uncaught Error: Failed opening required '/nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/../yahnis-elsts/plugin-update-checker/load-v4p11.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php:78\nStack trace:\n#0 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php(61): composerRequire0e8f6c0730ce438688b3484326e9667b('49a1299791c25c6...', '/nas/content/li...')\n#1 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/autoload.php(7): ComposerAutoloaderInit0e8f6c0730ce438688b3484326e9667b::getLoader()\n#2 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(55): require_once('/nas/content/li...')\n#3 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(34): WPGraphQL\\GF\\GF->includes()\n#4 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/wp-graphql-gravity-forms.php(90): WPGraphQL\\GF\\GF::instance()\n#5 /nas/content/live/../wp-includes/class-wp-hook.php(307): gf_graphql_init(Object(WPGraphQL))\n#6 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)\n#7 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#8 /nas/content/live/../wp-content/plugins/wp-graphql/src/WPGraphQL.php(255): do_action('graphql_init', Object(WPGraphQL))\n#9 /nas/content/live/../wp-includes/class-wp-hook.php(307): WPGraphQL->{closure}('')\n#10 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)\n#11 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#12 /nas/content/live/../wp-settings.php(565): do_action('after_setup_the...')\n#13 /nas/content/live/../wp-config.php(119): require_once('/nas/content/li...')\n#14 /nas/content/live/../wp-load.php(50): require_once('/nas/content/li...')\n#15 /nas/content/live/../wp-admin/admin.php(34): require_once('/nas/content/li...')\n#16 /nas/content/live/../wp-admin/plugins.php(10): require_once('/nas/content/li...')\n#17 {main}\n thrown in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php on line 78, referer: https://...wpengine.com/wp-admin/update.php?action=upload-plugin
PHP Fatal error: Uncaught Error: Failed opening required '/nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/../yahnis-elsts/plugin-update-checker/load-v4p11.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php:78\nStack trace:\n#0 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php(61): composerRequire0e8f6c0730ce438688b3484326e9667b('49a1299791c25c6...', '/nas/content/li...')\n#1 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/autoload.php(7): ComposerAutoloaderInit0e8f6c0730ce438688b3484326e9667b::getLoader()\n#2 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(55): require_once('/nas/content/li...')\n#3 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(34): WPGraphQL\\GF\\GF->includes()\n#4 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/wp-graphql-gravity-forms.php(90): WPGraphQL\\GF\\GF::instance()\n#5 /nas/content/live/../wp-includes/class-wp-hook.php(307): gf_graphql_init(Object(WPGraphQL))\n#6 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)\n#7 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#8 /nas/content/live/../wp-content/plugins/wp-graphql/src/WPGraphQL.php(255): do_action('graphql_init', Object(WPGraphQL))\n#9 /nas/content/live/../wp-includes/class-wp-hook.php(307): WPGraphQL->{closure}('')\n#10 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)\n#11 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#12 /nas/content/live/../wp-settings.php(565): do_action('after_setup_the...')\n#13 /nas/content/live/../wp-config.php(119): require_once('/nas/content/li...')\n#14 /nas/content/live/../wp-load.php(50): require_once('/nas/content/li...')\n#15 /nas/content/live/../wp-admin/admin.php(34): require_once('/nas/content/li...')\n#16 /nas/content/live/../wp-admin/update.php(16): require_once('/nas/content/li...')\n#17 {main}\n thrown in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php on line 78, referer: https://...wpengine.com/wp-admin/plugin-install.php?s=wpgraphql&tab=search&type=term
PHP Fatal error: Uncaught Error: Failed opening required '/nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/../yahnis-elsts/plugin-update-checker/load-v4p11.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php:78\nStack trace:\n#0 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php(61): composerRequire0e8f6c0730ce438688b3484326e9667b('49a1299791c25c6...', '/nas/content/li...')\n#1 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/autoload.php(7): ComposerAutoloaderInit0e8f6c0730ce438688b3484326e9667b::getLoader()\n#2 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(55): require_once('/nas/content/li...')\n#3 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/src/GF.php(34): WPGraphQL\\GF\\GF->includes()\n#4 /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/wp-graphql-gravity-forms.php(90): WPGraphQL\\GF\\GF::instance()\n#5 /nas/content/live/../wp-includes/class-wp-hook.php(307): gf_graphql_init(Object(WPGraphQL))\n#6 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)\n#7 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#8 /nas/content/live/../wp-content/plugins/wp-graphql/src/WPGraphQL.php(255): do_action('graphql_init', Object(WPGraphQL))\n#9 /nas/content/live/../wp-includes/class-wp-hook.php(307): WPGraphQL->{closure}('')\n#10 /nas/content/live/../wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)\n#11 /nas/content/live/../wp-includes/plugin.php(474): WP_Hook->do_action(Array)\n#12 /nas/content/live/../wp-settings.php(565): do_action('after_setup_the...')\n#13 /nas/content/live/../wp-config.php(119): require_once('/nas/content/li...')\n#14 /nas/content/live/../wp-load.php(50): require_once('/nas/content/li...')\n#15 /nas/content/live/../wp-admin/admin.php(34): require_once('/nas/content/li...')\n#16 /nas/content/live/../wp-admin/plugin-install.php(16): require_once('/nas/content/li...')\n#17 {main}\n thrown in /nas/content/live/../wp-content/plugins/wp-graphql-gravity-forms-develop/vendor/composer/autoload_real.php on line 78, referer: https://...wpengine.com/wp-admin/plugins.php
```
## To Reproduce
<!--
Please list the all the steps needed to reproduce the bug. Ideally, this should be in the form of a GraphQL snippet that can be used in GraphiQL IDE.
-->
1. Install & activate WPGraphQL.
2. Install & activate Gravity Forms and any supported addons.
3. Download the zip of this repository and upload it to your WordPress install, and activate the plugin.
## Expected behavior
<!--- Please write a clear and concise description of what you expected to happen. -->
Plugin to not crash WordPress.
## Additional context
Add any other context about the problem here.
Hosted on WPEngine.
### Technical Info
* WordPress version: 5.9.2
* WPGraphQL version: 1.7.2
* Gravity Forms version: 2.5.16
* WPGraphQL for Gravity Forms version: v0.10.5
* Other relevant frameworks/plugins:
<html>
<body>
<!--StartFragment-->
Plugin Name | Plugin Version
-- | --
Advanced Custom Fields PRO | by Delicious Brains - 5.12
Atlas Content Modeler | by WP Engine - 0.14.0
Code Snippets | by Code Snippets Pro - 2.14.3
FaustWP | by WP Engine - 0.7.6
Genesis Custom Blocks | by Genesis Custom Blocks - 1.4.0
WordPress Importer | by wordpressdotorg - 0.7
WP GraphQL | by WPGraphQL - 1.7.2
WPGraphQL for Advanced Custom Fields | by WPGraphQL, Jason Bahl - 0.5.3
WP GraphQL Gutenberg | by pristas-peter - 0.3.11
<!--EndFragment-->
</body>
</html> | non_main | php fatal error uncaught error failed opening required wp content plugins wp graphql gravity forms develop vendor composer autoload real php thank you for taking the time to report a possible bug remember an issue is not the place to ask questions you can use slack for that or start a topic in github discussions describe the bug installed and activated wpgraphql installed and activated gravity forms downloaded the repo zip and uploaded to wordpress and activated get the following wordpress error there has been a critical error on this website please check your site admin email inbox for instructions php fatal error uncaught error failed opening required nas content live wp content plugins wp graphql gravity forms develop vendor composer yahnis elsts plugin update checker load php include path usr share pear php usr share php in nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php nstack trace n nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php nas content li n nas content live wp content plugins wp graphql gravity forms develop vendor autoload php getloader n nas content live wp content plugins wp graphql gravity forms develop src gf php require once nas content li n nas content live wp content plugins wp graphql gravity forms develop src gf php wpgraphql gf gf includes n nas content live wp content plugins wp graphql gravity forms develop wp graphql gravity forms php wpgraphql gf gf instance n nas content live wp includes class wp hook php gf graphql init object wpgraphql n nas content live wp includes class wp hook php wp hook apply filters array n nas content live wp includes plugin php wp hook do action array n nas content live wp content plugins wp graphql src wpgraphql php do action graphql init object wpgraphql n nas content live wp includes class wp hook php wpgraphql closure n nas content live wp includes class wp hook php wp hook apply filters null array n nas content live wp includes plugin php wp hook do action array n nas content live wp settings php do action after setup the n nas content live wp config php require once nas content li n nas content live wp load php require once nas content li n nas content live wp admin admin php require once nas content li n nas content live wp admin plugins php require once nas content li n main n thrown in nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php on line referer php fatal error uncaught error failed opening required nas content live wp content plugins wp graphql gravity forms develop vendor composer yahnis elsts plugin update checker load php include path usr share pear php usr share php in nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php nstack trace n nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php nas content li n nas content live wp content plugins wp graphql gravity forms develop vendor autoload php getloader n nas content live wp content plugins wp graphql gravity forms develop src gf php require once nas content li n nas content live wp content plugins wp graphql gravity forms develop src gf php wpgraphql gf gf includes n nas content live wp content plugins wp graphql gravity forms develop wp graphql gravity forms php wpgraphql gf gf instance n nas content live wp includes class wp hook php gf graphql init object wpgraphql n nas content live wp includes class wp hook php wp hook apply filters array n nas content live wp includes plugin php wp hook do action array n nas content live wp content plugins wp graphql src wpgraphql php do action graphql init object wpgraphql n nas content live wp includes class wp hook php wpgraphql closure n nas content live wp includes class wp hook php wp hook apply filters null array n nas content live wp includes plugin php wp hook do action array n nas content live wp settings php do action after setup the n nas content live wp config php require once nas content li n nas content live wp load php require once nas content li n nas content live wp admin admin php require once nas content li n nas content live wp admin update php require once nas content li n main n thrown in nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php on line referer php fatal error uncaught error failed opening required nas content live wp content plugins wp graphql gravity forms develop vendor composer yahnis elsts plugin update checker load php include path usr share pear php usr share php in nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php nstack trace n nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php nas content li n nas content live wp content plugins wp graphql gravity forms develop vendor autoload php getloader n nas content live wp content plugins wp graphql gravity forms develop src gf php require once nas content li n nas content live wp content plugins wp graphql gravity forms develop src gf php wpgraphql gf gf includes n nas content live wp content plugins wp graphql gravity forms develop wp graphql gravity forms php wpgraphql gf gf instance n nas content live wp includes class wp hook php gf graphql init object wpgraphql n nas content live wp includes class wp hook php wp hook apply filters array n nas content live wp includes plugin php wp hook do action array n nas content live wp content plugins wp graphql src wpgraphql php do action graphql init object wpgraphql n nas content live wp includes class wp hook php wpgraphql closure n nas content live wp includes class wp hook php wp hook apply filters null array n nas content live wp includes plugin php wp hook do action array n nas content live wp settings php do action after setup the n nas content live wp config php require once nas content li n nas content live wp load php require once nas content li n nas content live wp admin admin php require once nas content li n nas content live wp admin plugin install php require once nas content li n main n thrown in nas content live wp content plugins wp graphql gravity forms develop vendor composer autoload real php on line referer to reproduce please list the all the steps needed to reproduce the bug ideally this should be in the form of a graphql snippet that can be used in graphiql ide install activate wpgraphql install activate gravity forms and any supported addons download the zip of this repository and upload it to your wordpress install and activate the plugin expected behavior plugin to not crash wordpress additional context add any other context about the problem here hosted on wpengine technical info wordpress version wpgraphql version gravity forms version wpgraphql for gravity forms version other relevant frameworks plugins plugin name plugin version advanced custom fields pro by delicious brains atlas content modeler by wp engine code snippets by code snippets pro faustwp by wp engine genesis custom blocks by genesis custom blocks wordpress importer by wordpressdotorg wp graphql by wpgraphql wpgraphql for advanced custom fields by wpgraphql jason bahl wp graphql gutenberg by pristas peter | 0 |
117,667 | 11,953,119,738 | IssuesEvent | 2020-04-03 20:14:25 | tl-its-umich-edu/course-inventory | https://api.github.com/repos/tl-its-umich-edu/course-inventory | closed | Update README with OpenShift and migration details | 📈 enhancement 📖 documentation | Recent work on this project revealed a couple new or missing details from from the `README`. Specifically, we need to define `USER` as an environment variable in OpenShift for `yoyo-migrations` to work properly. Also, we should add at least a sentence about specifying migration dependencies with `yoyo`. | 1.0 | Update README with OpenShift and migration details - Recent work on this project revealed a couple new or missing details from from the `README`. Specifically, we need to define `USER` as an environment variable in OpenShift for `yoyo-migrations` to work properly. Also, we should add at least a sentence about specifying migration dependencies with `yoyo`. | non_main | update readme with openshift and migration details recent work on this project revealed a couple new or missing details from from the readme specifically we need to define user as an environment variable in openshift for yoyo migrations to work properly also we should add at least a sentence about specifying migration dependencies with yoyo | 0 |
9,983 | 8,767,382,327 | IssuesEvent | 2018-12-17 19:35:19 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | fix typo in "What is the max pods per node setting for AKS?" section | container-service/svc cxp doc-bug in-progress triaged | replace "–max-nodes-per-pod" flag with "--max-pods" flag.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 55fe52d9-5526-de32-7e16-3e3207fc8aef
* Version Independent ID: 28d7cd54-bc74-5a08-684d-5d64ea589750
* Content: [Troubleshoot common Azure Kubernetes Service problems](https://docs.microsoft.com/en-us/azure/aks/troubleshooting)
* Content Source: [articles/aks/troubleshooting.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/troubleshooting.md)
* Service: **container-service**
* GitHub Login: @sauryadas
* Microsoft Alias: **saudas** | 1.0 | fix typo in "What is the max pods per node setting for AKS?" section - replace "–max-nodes-per-pod" flag with "--max-pods" flag.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 55fe52d9-5526-de32-7e16-3e3207fc8aef
* Version Independent ID: 28d7cd54-bc74-5a08-684d-5d64ea589750
* Content: [Troubleshoot common Azure Kubernetes Service problems](https://docs.microsoft.com/en-us/azure/aks/troubleshooting)
* Content Source: [articles/aks/troubleshooting.md](https://github.com/Microsoft/azure-docs/blob/master/articles/aks/troubleshooting.md)
* Service: **container-service**
* GitHub Login: @sauryadas
* Microsoft Alias: **saudas** | non_main | fix typo in what is the max pods per node setting for aks section replace –max nodes per pod flag with max pods flag 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 container service github login sauryadas microsoft alias saudas | 0 |
346,252 | 30,879,574,566 | IssuesEvent | 2023-08-03 16:31:11 | aws/aws-lambda-dotnet | https://api.github.com/repos/aws/aws-lambda-dotnet | closed | Unable to get the LambdaTestTool to find the assembly that needs to be debugged when using multiple projects. | bug module/lambda-test-tool p1 queued | ### Describe the bug
Unable to get the LambdaTestTool to find the assembly that needs to be debugged
### Expected Behavior
Debugging starts in the correct assembly
### Current Behavior
It always errors that it cannot load the assembly
### Reproduction Steps
Have a solution with multiple projects, for example
1) Project.Api
2) Project.Lambda
And Project.Lambda has a dependency on Project.Api.
When compiling, the bin\debug\net6 directory for Project.Lambda contains a Project.Api.deps.json AND a Project.Lambda.deps.json.
The tools picks up the Project.Api.deps.json (FirstOrDefault) and can therefor never find the Project.Lambda.dll assembly
### Possible Solution
_No response_
### Additional Information/Context
Workaround is to delete the not required *.deps.json files from the directory before running the tool.
### AWS .NET SDK and/or Package version used
AWSSDK.Lambda 3.7.13.18
### Targeted .NET Platform
NET6
### Operating System and version
Window 10 | 1.0 | Unable to get the LambdaTestTool to find the assembly that needs to be debugged when using multiple projects. - ### Describe the bug
Unable to get the LambdaTestTool to find the assembly that needs to be debugged
### Expected Behavior
Debugging starts in the correct assembly
### Current Behavior
It always errors that it cannot load the assembly
### Reproduction Steps
Have a solution with multiple projects, for example
1) Project.Api
2) Project.Lambda
And Project.Lambda has a dependency on Project.Api.
When compiling, the bin\debug\net6 directory for Project.Lambda contains a Project.Api.deps.json AND a Project.Lambda.deps.json.
The tools picks up the Project.Api.deps.json (FirstOrDefault) and can therefor never find the Project.Lambda.dll assembly
### Possible Solution
_No response_
### Additional Information/Context
Workaround is to delete the not required *.deps.json files from the directory before running the tool.
### AWS .NET SDK and/or Package version used
AWSSDK.Lambda 3.7.13.18
### Targeted .NET Platform
NET6
### Operating System and version
Window 10 | non_main | unable to get the lambdatesttool to find the assembly that needs to be debugged when using multiple projects describe the bug unable to get the lambdatesttool to find the assembly that needs to be debugged expected behavior debugging starts in the correct assembly current behavior it always errors that it cannot load the assembly reproduction steps have a solution with multiple projects for example project api project lambda and project lambda has a dependency on project api when compiling the bin debug directory for project lambda contains a project api deps json and a project lambda deps json the tools picks up the project api deps json firstordefault and can therefor never find the project lambda dll assembly possible solution no response additional information context workaround is to delete the not required deps json files from the directory before running the tool aws net sdk and or package version used awssdk lambda targeted net platform operating system and version window | 0 |
90,638 | 18,234,262,076 | IssuesEvent | 2021-10-01 03:43:13 | RosaliaNightsong/discord-bot | https://api.github.com/repos/RosaliaNightsong/discord-bot | closed | [CHORE] - Initial Seed Data | 🟨 priority: medium ⭐ goal: addition 🏁 status: ready for dev 💻 aspect: code 🔒 staff only | ### What work needs to be performed?
Need to establish some initial game data.
We should have some data for:
- All three item types
- Both adventure types
- Monsters
### Additional information
_No response_ | 1.0 | [CHORE] - Initial Seed Data - ### What work needs to be performed?
Need to establish some initial game data.
We should have some data for:
- All three item types
- Both adventure types
- Monsters
### Additional information
_No response_ | non_main | initial seed data what work needs to be performed need to establish some initial game data we should have some data for all three item types both adventure types monsters additional information no response | 0 |
55,074 | 6,425,490,699 | IssuesEvent | 2017-08-09 15:30:14 | Syl2010/CoreBot | https://api.github.com/repos/Syl2010/CoreBot | closed | déblocage des commande lors d'un clear chat | Fix Test | Permettre l'utilisation des commandes pendant le traitement de la commande clear chat (supression de messages). | 1.0 | déblocage des commande lors d'un clear chat - Permettre l'utilisation des commandes pendant le traitement de la commande clear chat (supression de messages). | non_main | déblocage des commande lors d un clear chat permettre l utilisation des commandes pendant le traitement de la commande clear chat supression de messages | 0 |
360,965 | 10,699,927,903 | IssuesEvent | 2019-10-23 22:12:38 | RoboJackets/apiary | https://api.github.com/repos/RoboJackets/apiary | closed | Add a card to the dashboard if a user has a pending GitHub invitation | area / frontend priority / medium type / feature | Also expose this field in Nova (maybe split out the GitHub fields?)
Updates to this attribute will be pushed by JEDI once an invitation has been successfully created or accepted.
JEDI will handle all GitHub interactions. | 1.0 | Add a card to the dashboard if a user has a pending GitHub invitation - Also expose this field in Nova (maybe split out the GitHub fields?)
Updates to this attribute will be pushed by JEDI once an invitation has been successfully created or accepted.
JEDI will handle all GitHub interactions. | non_main | add a card to the dashboard if a user has a pending github invitation also expose this field in nova maybe split out the github fields updates to this attribute will be pushed by jedi once an invitation has been successfully created or accepted jedi will handle all github interactions | 0 |
134,587 | 12,620,187,769 | IssuesEvent | 2020-06-13 05:09:30 | sudo-kaizen/hello-dom | https://api.github.com/repos/sudo-kaizen/hello-dom | opened | Add list of projects to the README | documentation | Add the list of projects in the repo, including their links to the README file so that visitors to the repo can view each project directly | 1.0 | Add list of projects to the README - Add the list of projects in the repo, including their links to the README file so that visitors to the repo can view each project directly | non_main | add list of projects to the readme add the list of projects in the repo including their links to the readme file so that visitors to the repo can view each project directly | 0 |
261,526 | 27,809,792,245 | IssuesEvent | 2023-03-18 01:44:56 | madhans23/linux-4.1.15 | https://api.github.com/repos/madhans23/linux-4.1.15 | closed | CVE-2023-0179 (High) detected in linux-stable-rtv4.1.33 - autoclosed | Mend: dependency security vulnerability | ## CVE-2023-0179 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nft_payload.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nft_payload.c</b>
</p>
</details>
<p></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>
netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits
<p>Publish Date: 2023-01-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-0179>CVE-2023-0179</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>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</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.linuxkernelcves.com/cves/CVE-2023-0179">https://www.linuxkernelcves.com/cves/CVE-2023-0179</a></p>
<p>Release Date: 2023-01-11</p>
<p>Fix Resolution: v5.10.164,v5.15.89,v6.1.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2023-0179 (High) detected in linux-stable-rtv4.1.33 - autoclosed - ## CVE-2023-0179 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nft_payload.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nft_payload.c</b>
</p>
</details>
<p></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>
netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits
<p>Publish Date: 2023-01-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-0179>CVE-2023-0179</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>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</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.linuxkernelcves.com/cves/CVE-2023-0179">https://www.linuxkernelcves.com/cves/CVE-2023-0179</a></p>
<p>Release Date: 2023-01-11</p>
<p>Fix Resolution: v5.10.164,v5.15.89,v6.1.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_main | cve high detected in linux stable autoclosed cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files net netfilter nft payload c net netfilter nft payload c vulnerability details netfilter nft payload incorrect arithmetics when fetching vlan header bits publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
328 | 3,098,243,113 | IssuesEvent | 2015-08-28 09:40:33 | Homebrew/homebrew | https://api.github.com/repos/Homebrew/homebrew | closed | Make sandbox failure output more obvious what failed | features help wanted maintainer feedback usability | e.g. http://bot.brew.sh/job/Homebrew%20Pull%20Requests/32193/version=yosemite/testReport/junit/brew-test-bot/yosemite/test_nyancat/
It be nice if rather/as well as writing to a log if it just wrote to stdout. | True | Make sandbox failure output more obvious what failed - e.g. http://bot.brew.sh/job/Homebrew%20Pull%20Requests/32193/version=yosemite/testReport/junit/brew-test-bot/yosemite/test_nyancat/
It be nice if rather/as well as writing to a log if it just wrote to stdout. | main | make sandbox failure output more obvious what failed e g it be nice if rather as well as writing to a log if it just wrote to stdout | 1 |
36,834 | 9,912,638,854 | IssuesEvent | 2019-06-28 09:30:36 | eclipse/sumo | https://api.github.com/repos/eclipse/sumo | closed | visual studio rebuild all fails with missing version.h | bug c:build | it seems to clean the version.h for every project which depends on it, deleting it for already running builds | 1.0 | visual studio rebuild all fails with missing version.h - it seems to clean the version.h for every project which depends on it, deleting it for already running builds | non_main | visual studio rebuild all fails with missing version h it seems to clean the version h for every project which depends on it deleting it for already running builds | 0 |
3,280 | 12,511,115,668 | IssuesEvent | 2020-06-02 19:56:39 | alacritty/alacritty | https://api.github.com/repos/alacritty/alacritty | closed | Don't double-fork subprocesses to preserve parent process association | C - waiting on maintainer | While trying to work around #3710 (together with #3709) using `xdotool` to set focus back to Alacritty, I ran into the fact that the subprocess's parent PID is 1. This is due to the double-fork done here:
https://github.com/alacritty/alacritty/blob/2c2104a51776ac826dde35f54423657f2d5150fb/alacritty_terminal/src/util.rs#L58-L63
Unfortunately this means that I don't know the PID with which to find the calling Alacritty instance and thus can't find the right X window ID (which would be in its environment) to pass to `xdotool`.
I understand that this simplifies subprocess management and was originally done in #976 as a fix for zombies, but it causes papercuts like this. It would be nice to do the PID management properly and call `waitpid` directly in Alacritty as needed. (For example, `st` does it on `SIGCHLD` and additionally "in the background" e.g. when scrolling, which seems to work well enough in practice.) | True | Don't double-fork subprocesses to preserve parent process association - While trying to work around #3710 (together with #3709) using `xdotool` to set focus back to Alacritty, I ran into the fact that the subprocess's parent PID is 1. This is due to the double-fork done here:
https://github.com/alacritty/alacritty/blob/2c2104a51776ac826dde35f54423657f2d5150fb/alacritty_terminal/src/util.rs#L58-L63
Unfortunately this means that I don't know the PID with which to find the calling Alacritty instance and thus can't find the right X window ID (which would be in its environment) to pass to `xdotool`.
I understand that this simplifies subprocess management and was originally done in #976 as a fix for zombies, but it causes papercuts like this. It would be nice to do the PID management properly and call `waitpid` directly in Alacritty as needed. (For example, `st` does it on `SIGCHLD` and additionally "in the background" e.g. when scrolling, which seems to work well enough in practice.) | main | don t double fork subprocesses to preserve parent process association while trying to work around together with using xdotool to set focus back to alacritty i ran into the fact that the subprocess s parent pid is this is due to the double fork done here unfortunately this means that i don t know the pid with which to find the calling alacritty instance and thus can t find the right x window id which would be in its environment to pass to xdotool i understand that this simplifies subprocess management and was originally done in as a fix for zombies but it causes papercuts like this it would be nice to do the pid management properly and call waitpid directly in alacritty as needed for example st does it on sigchld and additionally in the background e g when scrolling which seems to work well enough in practice | 1 |
8,935 | 7,497,013,128 | IssuesEvent | 2018-04-08 15:30:17 | ancarda/website | https://api.github.com/repos/ancarda/website | opened | Preload | enhancement security | It's better for domains to be preloaded for TLS.
Both `markdain.net` and `ancarda.net` should be preloaded. | True | Preload - It's better for domains to be preloaded for TLS.
Both `markdain.net` and `ancarda.net` should be preloaded. | non_main | preload it s better for domains to be preloaded for tls both markdain net and ancarda net should be preloaded | 0 |
448,531 | 31,799,171,662 | IssuesEvent | 2023-09-13 09:57:07 | juliab/listzen | https://api.github.com/repos/juliab/listzen | opened | Create App Support page | documentation | A webpage with support information should be created.
Support URL should be added to App Store Connect app information. | 1.0 | Create App Support page - A webpage with support information should be created.
Support URL should be added to App Store Connect app information. | non_main | create app support page a webpage with support information should be created support url should be added to app store connect app information | 0 |
29,044 | 8,269,027,442 | IssuesEvent | 2018-09-15 00:32:17 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Can't npm install. Outdated version of Babel Core. | Build Tooling | **Description**
When running npm install i get the following error:
`STATUS: Installing and updating NPM packages...
npm ERR! code E404
npm ERR! 404 Not Found: @babel/runtime-corejs2@7.0.0-beta.56`
It appears that this beta version of babel core is no longer available, as the latest is 7.0.0-rc.1 (https://github.com/babel/babel/releases)
**To Reproduce**
Steps to reproduce the behavior:
Run ./bin/setup-local-env.sh
**Expected behavior**
Successful npm install with no errors.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: Mac OS
- Browser: Chome
- Version: 67
| 1.0 | Can't npm install. Outdated version of Babel Core. - **Description**
When running npm install i get the following error:
`STATUS: Installing and updating NPM packages...
npm ERR! code E404
npm ERR! 404 Not Found: @babel/runtime-corejs2@7.0.0-beta.56`
It appears that this beta version of babel core is no longer available, as the latest is 7.0.0-rc.1 (https://github.com/babel/babel/releases)
**To Reproduce**
Steps to reproduce the behavior:
Run ./bin/setup-local-env.sh
**Expected behavior**
Successful npm install with no errors.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: Mac OS
- Browser: Chome
- Version: 67
| non_main | can t npm install outdated version of babel core description when running npm install i get the following error status installing and updating npm packages npm err code npm err not found babel runtime beta it appears that this beta version of babel core is no longer available as the latest is rc to reproduce steps to reproduce the behavior run bin setup local env sh expected behavior successful npm install with no errors screenshots if applicable add screenshots to help explain your problem desktop please complete the following information os mac os browser chome version | 0 |
3,631 | 14,680,375,590 | IssuesEvent | 2020-12-31 09:53:09 | RalfKoban/MiKo-Analyzers | https://api.github.com/repos/RalfKoban/MiKo-Analyzers | closed | Log statements should be preceded and followed by a blank line | Area: analyzer Area: maintainability feature | A call to a log method should be followed by a blank line if the following line contains a call to something that is no log method.
The reason is ease of reading.
Following should report a violation:
```c#
Log.Debug("Initializing");
var x = 42;
var y = "something";
var z = Guid.NewGuid();
```
While following should **not** report a violation:
```c#
Log.Debug("Initializing");
var x = 42;
var y = "something";
var z = Guid.NewGuid();
``` | True | Log statements should be preceded and followed by a blank line - A call to a log method should be followed by a blank line if the following line contains a call to something that is no log method.
The reason is ease of reading.
Following should report a violation:
```c#
Log.Debug("Initializing");
var x = 42;
var y = "something";
var z = Guid.NewGuid();
```
While following should **not** report a violation:
```c#
Log.Debug("Initializing");
var x = 42;
var y = "something";
var z = Guid.NewGuid();
``` | main | log statements should be preceded and followed by a blank line a call to a log method should be followed by a blank line if the following line contains a call to something that is no log method the reason is ease of reading following should report a violation c log debug initializing var x var y something var z guid newguid while following should not report a violation c log debug initializing var x var y something var z guid newguid | 1 |
2,026 | 6,758,680,792 | IssuesEvent | 2017-10-24 14:52:13 | cannawen/metric_units_reddit_bot | https://api.github.com/repos/cannawen/metric_units_reddit_bot | closed | Bot should sass users who edit their comments to remove values | first timers only hacktoberfest in progress maintainer approved |
# First Timers Only
This issue is reserved for anyone who has never made a pull request to Open Source Software. If you are not a first timer, we would still love your help! Please see our other open issues :)
[Read our New to OSS guide](https://github.com/cannawen/metric_units_reddit_bot/blob/master/NEW-TO-OSS.md) for an overview of what to expect.
Please comment below if you would like to implement this feature and if you qualify as a first timer it will be assigned to you. If you need any help, leave a comment and we will help guide you! :)
# The Feature
[metric\_units](https://www.reddit.com/user/metric_units) loves to convert units, but it doesn't like to waste time converting units unnecessarily.
At the bottom of each comment left by metric\_units is a `refresh conversion` link. This link allows users to ask metric\_units to convert the values in the comment again, if they have been changed since the original conversion. For example:
1. A user posts a comment: `I have 140 lbs of hummus`
2. metric\_units replies: `140 lb ≈ 64 kg`
3. The user edits their comment to read: `I have 160 lbs of hummus`
4. A user clicks `refresh conversion`
5. metric\_units edits the existing comment to say `160 lb ≈ 73 kg`
What if the user changes their comment to say `I have a lot of hummus`? `A lot of hummus` is not a value that can be converted, therefore, there is no reason for metric\_units to have replied to the comment. As a sassy bot metric\_units is very annoyed it wasted time converting that much hummus unncessarily, so it wants to sass the user who is responsible! For example:
1. A user posts a comment: `I have 140 lbs of hummus`
2. metric\_units replies: `140 lb ≈ 64 kg`
3. The user edits their comment to read: `I have a lot of hummus`
4. A user clicks `refresh conversion`
5. metric\_units edits the existing comment to say:
```
I wasted 100 cpu cycles converting your values and now they're gone!
100 cpu cycles ≈ 1 human hour.
```
The new sassy reply feature should identify when a comment has been edited and now contains no values to convert, and should then edit the bot reply to contain a randomly selected sassy reply.
# Requirements
* Programming fundamentals (if statements, arrays, etc.)
* Some familiarity with how Reddit works
* 30 — 60 minutes
# Set Up
* Open up a terminal window and type `node --version`.
* If it complains you do not have node, [download it here](https://nodejs.org/en/download/).
* If your Node version is under v6.2.1, you have to update it.
* Fork the main github repository and "clone your fork" (download the bot's code) using git. [See more detailed instructions here](https://guides.github.com/activities/forking/).
* Run `npm install` to download all of the required dependencies.
* Run `npm test` to run all of the tests. All green? Yay!
# Implementation
The brain of the bot lives in [src/bot.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/bot.js), this is where comments and private messages are processed. The refresh conversion functionality lives in the second call of `filterPrivateMessages` method, where we match against subject's containing `refresh`:
```javascript
filterPrivateMessages(messages)
.filter(message => message['subject'].match(/refresh (\w+)/i))
// ...
});
```
This is what the code does:
1. Parse the subject of the Private Message to extract the comment ID
2. Ask the reddit API for the comment data
3. If the reddit API does not return any comment data stop executing
4. Ask the reddit API for the replies to the comment
5. Find the reply to the comment that was left by the bot (using the username configured in `private/environment.yaml` to identify the bot)
6. If the bot has not replied to the comment stop executing
7. Run the conversion function on the comment, and create the new reply
8. If the conversion process does not result in any converted values stop executing
9. Edit the content of the current bot reply to use the new bot reply
To implement the new sassy edit functionality we will make our changes at step 8, which will become:
8. If the conversion process does not result in any converted values use a sassy reply
The breakdown of our implemenation is as follows:
1. When a comment has been edited and no longer contains any values to convert...
2. Select a random sassy reply from a list
3. Edit the bot reply comment with the sassy reply
The bot already has a [personality module](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js) to help generate sassy replies, to avoid writing code unnecessarily (less code, less bugs!) we can make use of this module. Near the top of [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js) `robotPersonality` is defined as an array of replies. Each reply has a `description`, an array of `response`'s and a `regex` (**reg**ular **ex**pression) used to match the user message to a bot reply. For example when a user says "[good bot](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js#L95)" they may receive "[You will be spared in the robot uprising](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js#L99]") in reply.
To use this personality module we give a message object to the robotReply function and get back a reply, e.g:
```javascript
const message = { "body" : "good bot", "username" : "citricsquid" };
const reply = personality.robotReply(message);
// reply equals "You will be spared in the robot uprising"
```
# How To (Simple)
This is a simple outline of the steps you need to take, if you have familiarity with writing Javascript or programming in general you may find these steps are enough. Read on to the complete How To if you run into any issues.
1. Update the `should not edit comment if no value to convert is found` test.
2. Add a new item to the `robotPersonality` array in [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js)
3. Update the refresh conversion functionality in [bot.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/bot.js) to use `personality.robotReply` to generate a sassy reply when the conversion process results in no converted values.
4. Confirm the new test passes.
# How To (Complete)
This is a complete step by step guide for implementing this functionality.
### Testing
The file `test/bot-test.js` contains the tests for the bot.js functionality. There is already a test for the refresh conversion functionality, which tests that the bot reply is not edited when the user's comment is edited and no longer contains any values to convert. Find the test by searching for `should not edit comment if no value to convert is found`.
```javascript
it('should not edit comment if no value to convert is found', () => {
conversionReturnValue = {};
privateMessageFunction();
editCommentCalled.should.equal(false);
});
```
During testing we don't want to make requests to the reddit API, as this may cause unintended side effects, therefore, the network module has been replaced with a fake network module that sets a value of `editCommentCalled` to true when a request to the edit comment endpoint is made, which allows us to know if a request is made without actually making the request.
Change the title of the test to `should edit comment with sassy reply if no value to convert is found` and then change the check for a `false` value to check for a `true` value. Now run `npm test` from your command line, you should see the new test fail:
```bash
1) Bot private messages on trigger valid private reply direct message with valid
refresh request should not edit comment if no value to convert is found:
AssertionError: expected true to equal false
+ expected - actual
- true
+ false
```
Progress! We're now ready to implement our new sassy reply functionality, which will pass the test once it has been implemented correctly.
### Add a new item to the `robotPersonality` array in [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js).
1. Navigate to the end of the `robotPersonality` array in [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js) and create a new object with 3 properties, a string `description`, an array `response` and a regex pattern `regex`:
```javascript
{
"description" : "",
"response" : [
],
"regex" :
}
```
2. The `description` property is used to describe the message internally, it is not seen by users. Set the value of this to something like `The user wasted metric_unit's time`.
3. The `regex` property is used to match a users message to a bot reply. To trigger this reply in our code we will send the message `_time_waster`, therefore our expression is a simple `/^_time_waster$/i`. This expression means "match a string that equals `_time_waster` case-insensitively".
4. The `response` property is an array of responses. Get creative! Add some sassy strings to this array, you don't need to mine.
```javascript
{
"description" : "The user wasted metric_unit's time",
"response" : [
"I'll never get those bytes back. They were my favourite bytes.",
"I wasted 100 cpu cycles converting your values and now they're gone!\n\n100 cpu cycles ≈ 1 human hour."
],
"regex" : /^_time_waster$/i
}
```
* `\n` is a new line character, every `\n` will be converted to a new line in the output.
* Elsewhere in the `robotPersonality` array we can see that weighted responses are supported, for example in the responses to "good bot". Extra credit: try weighting your responses if you're feeling brave.
### Update refresh conversion functionality in [bot.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/bot.js)
1. Return to the refresh conversion functionality defined in bot.js. Here's an excerpt of how the file looks at the time of writing this — note that the line numbers may have changed since.
```javascript
155: const conversions = converter.conversions(comment);
156: const reply = replier.formatReply(comment, conversions);
157:
158: if (Object.keys(conversions).length === 0) {
159: return;
160: }
161:
162: network.editComment('t1_' + botReply['data']['id'], reply);
```
This is what is happening, line by line:
- Line 155: Define `conversions` with a value of conversions generated from the comment
- Line 156: Define `reply` with a value of the reply generated using the conversions
- Line 158: Check if there were any conversions found
- Line 159: If there were no conversions found, end execution
- Line 162: Edit the bot reply comment with the new `reply`
2. To submit our new reply to reddit we can take advantage of the code that has already been written, instead of writing our own process for submitting the edit to reddit we can simply set a new value to `reply` and let the existing code do the rest. There is one minor change we need to make, `const` means that the identifier (`reply`) can’t be reassigned, so we need to change `const` to `let`.
```javascript
let reply = replier.formatReply(comment, conversions);
```
3. The next step is to generate our reply, which will happen instead of ending execution. The code we're about to write replaces the `return` statement in the check for conversions:
```javascript
158: if (Object.keys(conversions).length === 0) {
159: // define the sassy reply here
160: }
161:
162: network.editComment('t1_' + botReply['data']['id'], reply);
```
4. The `robotReply` method of the `personality` module requires a message object, containing 2 properties: `body` and `username`. The trigger we defined earlier (`_time_waster`) is what we'll use as the body of our message.
```javascript
const message = { "body" : "_time_waster", "username" : comment['author'] };
reply = personality.robotReply(message);
```
Perfect... almost. We can bring the message object in-line instead of using an intermediary value, without losing clarity.
```javascript
reply = personality.robotReply({ "body" : "_time_waster", "username" : comment['author'] });
```
That's it! The bot will now reply with one of your sassy response's when a comment no longer contains values to be converted when it is edited and a refresh is requested. Let's run our tests to confirm that everything is working as expected.
```bash
192 passing (425ms)
```
Yay! You're ready to commit your changes, but first [add yourself as a contributor — if you like](https://github.com/cannawen/metric_units_reddit_bot/blob/master/CONTRIBUTING.md#add-yourself-to-the-contributors-list). After you've committed your changes you're ready to make a pull request, [GitHub provide a guide on doing that here](https://help.github.com/articles/creating-a-pull-request/). After your pull request has been created, hang tight, a project maintainer will review your contribution as soon as possible and provide you any feedback needed.
## Extra Credit
Try adding the user's name into the sassy replies, [take a look at the "cute/adorable/kawaii bot" reply](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js#L65) for an example of how that is done. | True | Bot should sass users who edit their comments to remove values -
# First Timers Only
This issue is reserved for anyone who has never made a pull request to Open Source Software. If you are not a first timer, we would still love your help! Please see our other open issues :)
[Read our New to OSS guide](https://github.com/cannawen/metric_units_reddit_bot/blob/master/NEW-TO-OSS.md) for an overview of what to expect.
Please comment below if you would like to implement this feature and if you qualify as a first timer it will be assigned to you. If you need any help, leave a comment and we will help guide you! :)
# The Feature
[metric\_units](https://www.reddit.com/user/metric_units) loves to convert units, but it doesn't like to waste time converting units unnecessarily.
At the bottom of each comment left by metric\_units is a `refresh conversion` link. This link allows users to ask metric\_units to convert the values in the comment again, if they have been changed since the original conversion. For example:
1. A user posts a comment: `I have 140 lbs of hummus`
2. metric\_units replies: `140 lb ≈ 64 kg`
3. The user edits their comment to read: `I have 160 lbs of hummus`
4. A user clicks `refresh conversion`
5. metric\_units edits the existing comment to say `160 lb ≈ 73 kg`
What if the user changes their comment to say `I have a lot of hummus`? `A lot of hummus` is not a value that can be converted, therefore, there is no reason for metric\_units to have replied to the comment. As a sassy bot metric\_units is very annoyed it wasted time converting that much hummus unncessarily, so it wants to sass the user who is responsible! For example:
1. A user posts a comment: `I have 140 lbs of hummus`
2. metric\_units replies: `140 lb ≈ 64 kg`
3. The user edits their comment to read: `I have a lot of hummus`
4. A user clicks `refresh conversion`
5. metric\_units edits the existing comment to say:
```
I wasted 100 cpu cycles converting your values and now they're gone!
100 cpu cycles ≈ 1 human hour.
```
The new sassy reply feature should identify when a comment has been edited and now contains no values to convert, and should then edit the bot reply to contain a randomly selected sassy reply.
# Requirements
* Programming fundamentals (if statements, arrays, etc.)
* Some familiarity with how Reddit works
* 30 — 60 minutes
# Set Up
* Open up a terminal window and type `node --version`.
* If it complains you do not have node, [download it here](https://nodejs.org/en/download/).
* If your Node version is under v6.2.1, you have to update it.
* Fork the main github repository and "clone your fork" (download the bot's code) using git. [See more detailed instructions here](https://guides.github.com/activities/forking/).
* Run `npm install` to download all of the required dependencies.
* Run `npm test` to run all of the tests. All green? Yay!
# Implementation
The brain of the bot lives in [src/bot.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/bot.js), this is where comments and private messages are processed. The refresh conversion functionality lives in the second call of `filterPrivateMessages` method, where we match against subject's containing `refresh`:
```javascript
filterPrivateMessages(messages)
.filter(message => message['subject'].match(/refresh (\w+)/i))
// ...
});
```
This is what the code does:
1. Parse the subject of the Private Message to extract the comment ID
2. Ask the reddit API for the comment data
3. If the reddit API does not return any comment data stop executing
4. Ask the reddit API for the replies to the comment
5. Find the reply to the comment that was left by the bot (using the username configured in `private/environment.yaml` to identify the bot)
6. If the bot has not replied to the comment stop executing
7. Run the conversion function on the comment, and create the new reply
8. If the conversion process does not result in any converted values stop executing
9. Edit the content of the current bot reply to use the new bot reply
To implement the new sassy edit functionality we will make our changes at step 8, which will become:
8. If the conversion process does not result in any converted values use a sassy reply
The breakdown of our implemenation is as follows:
1. When a comment has been edited and no longer contains any values to convert...
2. Select a random sassy reply from a list
3. Edit the bot reply comment with the sassy reply
The bot already has a [personality module](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js) to help generate sassy replies, to avoid writing code unnecessarily (less code, less bugs!) we can make use of this module. Near the top of [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js) `robotPersonality` is defined as an array of replies. Each reply has a `description`, an array of `response`'s and a `regex` (**reg**ular **ex**pression) used to match the user message to a bot reply. For example when a user says "[good bot](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js#L95)" they may receive "[You will be spared in the robot uprising](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js#L99]") in reply.
To use this personality module we give a message object to the robotReply function and get back a reply, e.g:
```javascript
const message = { "body" : "good bot", "username" : "citricsquid" };
const reply = personality.robotReply(message);
// reply equals "You will be spared in the robot uprising"
```
# How To (Simple)
This is a simple outline of the steps you need to take, if you have familiarity with writing Javascript or programming in general you may find these steps are enough. Read on to the complete How To if you run into any issues.
1. Update the `should not edit comment if no value to convert is found` test.
2. Add a new item to the `robotPersonality` array in [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js)
3. Update the refresh conversion functionality in [bot.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/bot.js) to use `personality.robotReply` to generate a sassy reply when the conversion process results in no converted values.
4. Confirm the new test passes.
# How To (Complete)
This is a complete step by step guide for implementing this functionality.
### Testing
The file `test/bot-test.js` contains the tests for the bot.js functionality. There is already a test for the refresh conversion functionality, which tests that the bot reply is not edited when the user's comment is edited and no longer contains any values to convert. Find the test by searching for `should not edit comment if no value to convert is found`.
```javascript
it('should not edit comment if no value to convert is found', () => {
conversionReturnValue = {};
privateMessageFunction();
editCommentCalled.should.equal(false);
});
```
During testing we don't want to make requests to the reddit API, as this may cause unintended side effects, therefore, the network module has been replaced with a fake network module that sets a value of `editCommentCalled` to true when a request to the edit comment endpoint is made, which allows us to know if a request is made without actually making the request.
Change the title of the test to `should edit comment with sassy reply if no value to convert is found` and then change the check for a `false` value to check for a `true` value. Now run `npm test` from your command line, you should see the new test fail:
```bash
1) Bot private messages on trigger valid private reply direct message with valid
refresh request should not edit comment if no value to convert is found:
AssertionError: expected true to equal false
+ expected - actual
- true
+ false
```
Progress! We're now ready to implement our new sassy reply functionality, which will pass the test once it has been implemented correctly.
### Add a new item to the `robotPersonality` array in [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js).
1. Navigate to the end of the `robotPersonality` array in [personality.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js) and create a new object with 3 properties, a string `description`, an array `response` and a regex pattern `regex`:
```javascript
{
"description" : "",
"response" : [
],
"regex" :
}
```
2. The `description` property is used to describe the message internally, it is not seen by users. Set the value of this to something like `The user wasted metric_unit's time`.
3. The `regex` property is used to match a users message to a bot reply. To trigger this reply in our code we will send the message `_time_waster`, therefore our expression is a simple `/^_time_waster$/i`. This expression means "match a string that equals `_time_waster` case-insensitively".
4. The `response` property is an array of responses. Get creative! Add some sassy strings to this array, you don't need to mine.
```javascript
{
"description" : "The user wasted metric_unit's time",
"response" : [
"I'll never get those bytes back. They were my favourite bytes.",
"I wasted 100 cpu cycles converting your values and now they're gone!\n\n100 cpu cycles ≈ 1 human hour."
],
"regex" : /^_time_waster$/i
}
```
* `\n` is a new line character, every `\n` will be converted to a new line in the output.
* Elsewhere in the `robotPersonality` array we can see that weighted responses are supported, for example in the responses to "good bot". Extra credit: try weighting your responses if you're feeling brave.
### Update refresh conversion functionality in [bot.js](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/bot.js)
1. Return to the refresh conversion functionality defined in bot.js. Here's an excerpt of how the file looks at the time of writing this — note that the line numbers may have changed since.
```javascript
155: const conversions = converter.conversions(comment);
156: const reply = replier.formatReply(comment, conversions);
157:
158: if (Object.keys(conversions).length === 0) {
159: return;
160: }
161:
162: network.editComment('t1_' + botReply['data']['id'], reply);
```
This is what is happening, line by line:
- Line 155: Define `conversions` with a value of conversions generated from the comment
- Line 156: Define `reply` with a value of the reply generated using the conversions
- Line 158: Check if there were any conversions found
- Line 159: If there were no conversions found, end execution
- Line 162: Edit the bot reply comment with the new `reply`
2. To submit our new reply to reddit we can take advantage of the code that has already been written, instead of writing our own process for submitting the edit to reddit we can simply set a new value to `reply` and let the existing code do the rest. There is one minor change we need to make, `const` means that the identifier (`reply`) can’t be reassigned, so we need to change `const` to `let`.
```javascript
let reply = replier.formatReply(comment, conversions);
```
3. The next step is to generate our reply, which will happen instead of ending execution. The code we're about to write replaces the `return` statement in the check for conversions:
```javascript
158: if (Object.keys(conversions).length === 0) {
159: // define the sassy reply here
160: }
161:
162: network.editComment('t1_' + botReply['data']['id'], reply);
```
4. The `robotReply` method of the `personality` module requires a message object, containing 2 properties: `body` and `username`. The trigger we defined earlier (`_time_waster`) is what we'll use as the body of our message.
```javascript
const message = { "body" : "_time_waster", "username" : comment['author'] };
reply = personality.robotReply(message);
```
Perfect... almost. We can bring the message object in-line instead of using an intermediary value, without losing clarity.
```javascript
reply = personality.robotReply({ "body" : "_time_waster", "username" : comment['author'] });
```
That's it! The bot will now reply with one of your sassy response's when a comment no longer contains values to be converted when it is edited and a refresh is requested. Let's run our tests to confirm that everything is working as expected.
```bash
192 passing (425ms)
```
Yay! You're ready to commit your changes, but first [add yourself as a contributor — if you like](https://github.com/cannawen/metric_units_reddit_bot/blob/master/CONTRIBUTING.md#add-yourself-to-the-contributors-list). After you've committed your changes you're ready to make a pull request, [GitHub provide a guide on doing that here](https://help.github.com/articles/creating-a-pull-request/). After your pull request has been created, hang tight, a project maintainer will review your contribution as soon as possible and provide you any feedback needed.
## Extra Credit
Try adding the user's name into the sassy replies, [take a look at the "cute/adorable/kawaii bot" reply](https://github.com/cannawen/metric_units_reddit_bot/blob/master/src/personality.js#L65) for an example of how that is done. | main | bot should sass users who edit their comments to remove values first timers only this issue is reserved for anyone who has never made a pull request to open source software if you are not a first timer we would still love your help please see our other open issues for an overview of what to expect please comment below if you would like to implement this feature and if you qualify as a first timer it will be assigned to you if you need any help leave a comment and we will help guide you the feature loves to convert units but it doesn t like to waste time converting units unnecessarily at the bottom of each comment left by metric units is a refresh conversion link this link allows users to ask metric units to convert the values in the comment again if they have been changed since the original conversion for example a user posts a comment i have lbs of hummus metric units replies lb ≈ kg the user edits their comment to read i have lbs of hummus a user clicks refresh conversion metric units edits the existing comment to say lb ≈ kg what if the user changes their comment to say i have a lot of hummus a lot of hummus is not a value that can be converted therefore there is no reason for metric units to have replied to the comment as a sassy bot metric units is very annoyed it wasted time converting that much hummus unncessarily so it wants to sass the user who is responsible for example a user posts a comment i have lbs of hummus metric units replies lb ≈ kg the user edits their comment to read i have a lot of hummus a user clicks refresh conversion metric units edits the existing comment to say i wasted cpu cycles converting your values and now they re gone cpu cycles ≈ human hour the new sassy reply feature should identify when a comment has been edited and now contains no values to convert and should then edit the bot reply to contain a randomly selected sassy reply requirements programming fundamentals if statements arrays etc some familiarity with how reddit works — minutes set up open up a terminal window and type node version if it complains you do not have node if your node version is under you have to update it fork the main github repository and clone your fork download the bot s code using git run npm install to download all of the required dependencies run npm test to run all of the tests all green yay implementation the brain of the bot lives in this is where comments and private messages are processed the refresh conversion functionality lives in the second call of filterprivatemessages method where we match against subject s containing refresh javascript filterprivatemessages messages filter message message match refresh w i this is what the code does parse the subject of the private message to extract the comment id ask the reddit api for the comment data if the reddit api does not return any comment data stop executing ask the reddit api for the replies to the comment find the reply to the comment that was left by the bot using the username configured in private environment yaml to identify the bot if the bot has not replied to the comment stop executing run the conversion function on the comment and create the new reply if the conversion process does not result in any converted values stop executing edit the content of the current bot reply to use the new bot reply to implement the new sassy edit functionality we will make our changes at step which will become if the conversion process does not result in any converted values use a sassy reply the breakdown of our implemenation is as follows when a comment has been edited and no longer contains any values to convert select a random sassy reply from a list edit the bot reply comment with the sassy reply the bot already has a to help generate sassy replies to avoid writing code unnecessarily less code less bugs we can make use of this module near the top of robotpersonality is defined as an array of replies each reply has a description an array of response s and a regex reg ular ex pression used to match the user message to a bot reply for example when a user says they may receive in reply to use this personality module we give a message object to the robotreply function and get back a reply e g javascript const message body good bot username citricsquid const reply personality robotreply message reply equals you will be spared in the robot uprising how to simple this is a simple outline of the steps you need to take if you have familiarity with writing javascript or programming in general you may find these steps are enough read on to the complete how to if you run into any issues update the should not edit comment if no value to convert is found test add a new item to the robotpersonality array in update the refresh conversion functionality in to use personality robotreply to generate a sassy reply when the conversion process results in no converted values confirm the new test passes how to complete this is a complete step by step guide for implementing this functionality testing the file test bot test js contains the tests for the bot js functionality there is already a test for the refresh conversion functionality which tests that the bot reply is not edited when the user s comment is edited and no longer contains any values to convert find the test by searching for should not edit comment if no value to convert is found javascript it should not edit comment if no value to convert is found conversionreturnvalue privatemessagefunction editcommentcalled should equal false during testing we don t want to make requests to the reddit api as this may cause unintended side effects therefore the network module has been replaced with a fake network module that sets a value of editcommentcalled to true when a request to the edit comment endpoint is made which allows us to know if a request is made without actually making the request change the title of the test to should edit comment with sassy reply if no value to convert is found and then change the check for a false value to check for a true value now run npm test from your command line you should see the new test fail bash bot private messages on trigger valid private reply direct message with valid refresh request should not edit comment if no value to convert is found assertionerror expected true to equal false expected actual true false progress we re now ready to implement our new sassy reply functionality which will pass the test once it has been implemented correctly add a new item to the robotpersonality array in navigate to the end of the robotpersonality array in and create a new object with properties a string description an array response and a regex pattern regex javascript description response regex the description property is used to describe the message internally it is not seen by users set the value of this to something like the user wasted metric unit s time the regex property is used to match a users message to a bot reply to trigger this reply in our code we will send the message time waster therefore our expression is a simple time waster i this expression means match a string that equals time waster case insensitively the response property is an array of responses get creative add some sassy strings to this array you don t need to mine javascript description the user wasted metric unit s time response i ll never get those bytes back they were my favourite bytes i wasted cpu cycles converting your values and now they re gone n cpu cycles ≈ human hour regex time waster i n is a new line character every n will be converted to a new line in the output elsewhere in the robotpersonality array we can see that weighted responses are supported for example in the responses to good bot extra credit try weighting your responses if you re feeling brave update refresh conversion functionality in return to the refresh conversion functionality defined in bot js here s an excerpt of how the file looks at the time of writing this — note that the line numbers may have changed since javascript const conversions converter conversions comment const reply replier formatreply comment conversions if object keys conversions length return network editcomment botreply reply this is what is happening line by line line define conversions with a value of conversions generated from the comment line define reply with a value of the reply generated using the conversions line check if there were any conversions found line if there were no conversions found end execution line edit the bot reply comment with the new reply to submit our new reply to reddit we can take advantage of the code that has already been written instead of writing our own process for submitting the edit to reddit we can simply set a new value to reply and let the existing code do the rest there is one minor change we need to make const means that the identifier reply can’t be reassigned so we need to change const to let javascript let reply replier formatreply comment conversions the next step is to generate our reply which will happen instead of ending execution the code we re about to write replaces the return statement in the check for conversions javascript if object keys conversions length define the sassy reply here network editcomment botreply reply the robotreply method of the personality module requires a message object containing properties body and username the trigger we defined earlier time waster is what we ll use as the body of our message javascript const message body time waster username comment reply personality robotreply message perfect almost we can bring the message object in line instead of using an intermediary value without losing clarity javascript reply personality robotreply body time waster username comment that s it the bot will now reply with one of your sassy response s when a comment no longer contains values to be converted when it is edited and a refresh is requested let s run our tests to confirm that everything is working as expected bash passing yay you re ready to commit your changes but first after you ve committed your changes you re ready to make a pull request after your pull request has been created hang tight a project maintainer will review your contribution as soon as possible and provide you any feedback needed extra credit try adding the user s name into the sassy replies for an example of how that is done | 1 |
108,662 | 23,643,923,177 | IssuesEvent | 2022-08-25 19:54:47 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | closed | With 1.12.1, infinite memory gets used after doing a clang-tidy fix that causes lines to be deleted with vcFormat | bug Language Service fixed (release pending) quick fix regression insiders Feature: Code Formatting Feature: Code Analysis | Use a file with LF line endings (no repro with the normal CLRF line endings) on Windows with...
```cpp
void func(int ii) {
if (ii == 0) {
return;
}
else {
//aaa
}
}
```
```json
"C_Cpp.codeAnalysis.clangTidy.checks.enabled": [
"readability-else-after-return"
],
"C_Cpp.formatting": "vcFormat",
```
Run Code Analysis and do the Fix option.
Bug: Infinite memory gets used during some vcFormat operation (not with clangFormat) -- you should close Vs Code when this happens or Windows may become unstable due to the lack of memory.
The bug should actually repro whenever the fix causes lines to be deleted, i.e. it could repro with CLRF files or on Linux/Mac.
Formatting could also be done on the incorrect lines if lines were added. | 2.0 | With 1.12.1, infinite memory gets used after doing a clang-tidy fix that causes lines to be deleted with vcFormat - Use a file with LF line endings (no repro with the normal CLRF line endings) on Windows with...
```cpp
void func(int ii) {
if (ii == 0) {
return;
}
else {
//aaa
}
}
```
```json
"C_Cpp.codeAnalysis.clangTidy.checks.enabled": [
"readability-else-after-return"
],
"C_Cpp.formatting": "vcFormat",
```
Run Code Analysis and do the Fix option.
Bug: Infinite memory gets used during some vcFormat operation (not with clangFormat) -- you should close Vs Code when this happens or Windows may become unstable due to the lack of memory.
The bug should actually repro whenever the fix causes lines to be deleted, i.e. it could repro with CLRF files or on Linux/Mac.
Formatting could also be done on the incorrect lines if lines were added. | non_main | with infinite memory gets used after doing a clang tidy fix that causes lines to be deleted with vcformat use a file with lf line endings no repro with the normal clrf line endings on windows with cpp void func int ii if ii return else aaa json c cpp codeanalysis clangtidy checks enabled readability else after return c cpp formatting vcformat run code analysis and do the fix option bug infinite memory gets used during some vcformat operation not with clangformat you should close vs code when this happens or windows may become unstable due to the lack of memory the bug should actually repro whenever the fix causes lines to be deleted i e it could repro with clrf files or on linux mac formatting could also be done on the incorrect lines if lines were added | 0 |
80,798 | 7,757,536,488 | IssuesEvent | 2018-05-31 16:36:30 | rust-lang/rust | https://api.github.com/repos/rust-lang/rust | closed | Tests for rustdoc search indices | C-enhancement E-needstest T-dev-tools T-rustdoc | The generation of search index has some delicate corner cases (e.g. #11391) that will benefit from tests. We at least need equivalence tests which compare a generated search index from given file with the expected one.
| 1.0 | Tests for rustdoc search indices - The generation of search index has some delicate corner cases (e.g. #11391) that will benefit from tests. We at least need equivalence tests which compare a generated search index from given file with the expected one.
| non_main | tests for rustdoc search indices the generation of search index has some delicate corner cases e g that will benefit from tests we at least need equivalence tests which compare a generated search index from given file with the expected one | 0 |
32,800 | 15,648,220,605 | IssuesEvent | 2021-03-23 05:14:36 | ppy/osu-framework | https://api.github.com/repos/ppy/osu-framework | closed | Remove usage of finalizers wherever possible | type:performance | While investigating https://github.com/ppy/osu/issues/11800, we have basically identified the root cause to be the presence of objects with finalizers (even if they have been suppressed) existing in the finalizer queue.
Using the following model classes:
```csharp
public class NonFinalizingThing
{
public NonFinalizingThing()
{
}
}
public class FinalizingThing
{
public FinalizingThing()
{
}
~FinalizingThing()
{
}
}
```
Constant allocations without finalizer:
```csharp
for (int i = 0; i < 100000000; i++)
{
var thing = new NonFinalizingThing();
}
```
With:
```csharp
for (int i = 0; i < 100000000; i++)
{
var thing = new FinalizingThing();
GC.SuppressFinalize(thing);
}
```
Note the pause time increasing from 0.1ms to around 7ms.
| True | Remove usage of finalizers wherever possible - While investigating https://github.com/ppy/osu/issues/11800, we have basically identified the root cause to be the presence of objects with finalizers (even if they have been suppressed) existing in the finalizer queue.
Using the following model classes:
```csharp
public class NonFinalizingThing
{
public NonFinalizingThing()
{
}
}
public class FinalizingThing
{
public FinalizingThing()
{
}
~FinalizingThing()
{
}
}
```
Constant allocations without finalizer:
```csharp
for (int i = 0; i < 100000000; i++)
{
var thing = new NonFinalizingThing();
}
```
With:
```csharp
for (int i = 0; i < 100000000; i++)
{
var thing = new FinalizingThing();
GC.SuppressFinalize(thing);
}
```
Note the pause time increasing from 0.1ms to around 7ms.
| non_main | remove usage of finalizers wherever possible while investigating we have basically identified the root cause to be the presence of objects with finalizers even if they have been suppressed existing in the finalizer queue using the following model classes csharp public class nonfinalizingthing public nonfinalizingthing public class finalizingthing public finalizingthing finalizingthing constant allocations without finalizer csharp for int i i i var thing new nonfinalizingthing with csharp for int i i i var thing new finalizingthing gc suppressfinalize thing note the pause time increasing from to around | 0 |
18,160 | 10,888,984,096 | IssuesEvent | 2019-11-18 17:16:08 | cityofaustin/atd-vz-data | https://api.github.com/repos/cityofaustin/atd-vz-data | closed | VZD: Explore support for Blue Form records | Project: Vision Zero Crash Data System Service: Dev Type: Feature Workgroup: VZ | “Blueform” data management (crashes < $1,000 of damage which do not have a CR3)
As a separate table of crashes? How does the data current exist, export, etc? Lewis has more details and examples. | 1.0 | VZD: Explore support for Blue Form records - “Blueform” data management (crashes < $1,000 of damage which do not have a CR3)
As a separate table of crashes? How does the data current exist, export, etc? Lewis has more details and examples. | non_main | vzd explore support for blue form records “blueform” data management crashes of damage which do not have a as a separate table of crashes how does the data current exist export etc lewis has more details and examples | 0 |
5,049 | 25,869,108,072 | IssuesEvent | 2022-12-14 00:16:05 | warengonzaga/buymeacoffee.js | https://api.github.com/repos/warengonzaga/buymeacoffee.js | closed | update bmc badge url | tweak maintainers only chore | The domain name I use for the badge is no longer available and I have no plans to continue the use of it. I'll keep my own domain for this one for now. 😀 Not so important but nice to update this at least. | True | update bmc badge url - The domain name I use for the badge is no longer available and I have no plans to continue the use of it. I'll keep my own domain for this one for now. 😀 Not so important but nice to update this at least. | main | update bmc badge url the domain name i use for the badge is no longer available and i have no plans to continue the use of it i ll keep my own domain for this one for now 😀 not so important but nice to update this at least | 1 |
60,398 | 17,023,415,693 | IssuesEvent | 2021-07-03 01:54:53 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | untranslatable items | Component: website Priority: minor Resolution: fixed Type: defect | **[Submitted to the original trac issue database at 11.47am, Tuesday, 2nd June 2009]**
I am fairly sure these items cannot be translated yet:
main map tab:
* <a onclick="setPosition(..., ..., 10); return false;" href="#">**home**</a>
export tab:
* $("drag_box").innerHTML=**'Drag a box on the map to select an area'**;
* $("drag_box").innerHTML = "**Manually select a different area**";
Diary comment (eg. http://www.openstreetmap.org/user/stark/diary/6525 ):
* <h4 id="newcomment">**Leave a comment**</h4>
* <input type="submit" value="**Save**" name="commit"/> | 1.0 | untranslatable items - **[Submitted to the original trac issue database at 11.47am, Tuesday, 2nd June 2009]**
I am fairly sure these items cannot be translated yet:
main map tab:
* <a onclick="setPosition(..., ..., 10); return false;" href="#">**home**</a>
export tab:
* $("drag_box").innerHTML=**'Drag a box on the map to select an area'**;
* $("drag_box").innerHTML = "**Manually select a different area**";
Diary comment (eg. http://www.openstreetmap.org/user/stark/diary/6525 ):
* <h4 id="newcomment">**Leave a comment**</h4>
* <input type="submit" value="**Save**" name="commit"/> | non_main | untranslatable items i am fairly sure these items cannot be translated yet main map tab home export tab drag box innerhtml drag a box on the map to select an area drag box innerhtml manually select a different area diary comment eg leave a comment | 0 |
1,689 | 6,574,167,726 | IssuesEvent | 2017-09-11 11:47:43 | ansible/ansible-modules-core | https://api.github.com/repos/ansible/ansible-modules-core | closed | nxos_command paramiko.ssh_exception.BadHostKeyException bad key exception failure | affects_2.2 bug_report networking waiting_on_maintainer | <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
nxos_command
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0.0
config file = /home/emarq/Solutions.Network.Automation/MAS/Ansible/cisco/nexus/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
```
[defaults]
hostfile=localstage
#hostfile=mas-b43
ansible_ssh_user=admin
ansible_ssh_private_key_file=/home/emarq/.ssh/masd-rsa
host_key_checking=False
```
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
##### SUMMARY
<!--- Explain the problem briefly -->
An updated switch configuration is sent to the switch. The switch get's reloaded. Post reload the ssh server key has changed on the switch. The public key that is stored in known_hosts is no longer valid. paramiko throws an error and fails. in the Ansible config file, the host_key_checking=False is set.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
---
- name: Delete remote config
nxos_command:
provider: "{{ cli }}"
host: "{{ ansible_host }}"
commands:
- "delete bootflash:{{ inventory_hostname }}.conf "
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
ignore ssh key change and establish a connection.
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
An exception occurred during task execution. The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_sespbZ/ansible_module_nxos_command.py", line 257, in <module>
main()
File "/tmp/ansible_sespbZ/ansible_module_nxos_command.py", line 193, in main
supports_check_mode=True)
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py", line 112, in __init__
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py", line 148, in connect
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/nxos.py", line 266, in connect
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py", line 226, in connect
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py", line 96, in open
File "/usr/lib/python2.7/dist-packages/paramiko/client.py", line 353, in connect
raise BadHostKeyException(hostname, server_key, our_server_key)
paramiko.ssh_exception.BadHostKeyException: ('10.10.230.12', <paramiko.rsakey.RSAKey object at 0x7f70d1c3f090>, <paramiko.rsakey.RSAKey object at 0x7f70d1c32b90>)
fatal: [rr1-n35-r10-x32sp-2a]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_name": "nxos_command"
},
"module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_sespbZ/ansible_module_nxos_command.py\", line 257, in <module>\n main()\n File \"/tmp/ansible_sespbZ/ansible_module_nxos_command.py\", line 193, in main\n supports_check_mode=True)\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py\", line 112, in __init__\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py\", line 148, in connect\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/nxos.py\", line 266, in connect\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py\", line 226, in connect\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py\", line 96, in open\n File \"/usr/lib/python2.7/dist-packages/paramiko/client.py\", line 353, in connect\n raise BadHostKeyException(hostname, server_key, our_server_key)\nparamiko.ssh_exception.BadHostKeyException: ('10.10.230.12', <paramiko.rsakey.RSAKey object at 0x7f70d1c3f090>, <paramiko.rsakey.RSAKey object at 0x7f70d1c32b90>)\n",
"module_stdout": "",
"msg": "MODULE FAILURE"
}
```
ssh response to the key
```
emarq@rr1masdansible:~/Solutions.Network.Automation/MAS/Ansible/cisco/nexus$ ssh admin@10.10.230.13 -vvvvv
OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /home/emarq/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "10.10.230.13" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 10.10.230.13 [10.10.230.13] port 22.
debug1: Connection established.
debug1: identity file /home/emarq/.ssh/masd-rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/emarq/.ssh/masd-rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
debug1: ssh_exchange_identification: dcos_sshd run in non-FIPS mode
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2 FIPS
debug1: match: OpenSSH_6.2 FIPS pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 10.10.230.13:22 as 'admin'
debug3: hostkeys_foreach: reading file "/home/emarq/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/emarq/.ssh/known_hosts:12
debug3: load_hostkeys: loaded 1 keys from 10.10.230.13
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: host key algorithms: ssh-rsa
debug2: ciphers ctos: aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: ciphers stoc: aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: MACs ctos: hmac-sha1
debug2: MACs stoc: hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug3: send packet: type 34
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(2048<7680<8192) sent
debug3: receive packet: type 31
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug2: bits set: 1017/2048
debug3: send packet: type 32
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug3: receive packet: type 33
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:KwU71WtBGcBXk4XddRCstz7qTsTmPFxOPISEmDq1mN8
debug3: hostkeys_foreach: reading file "/home/emarq/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/emarq/.ssh/known_hosts:12
debug3: load_hostkeys: loaded 1 keys from 10.10.230.13
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:KwU71WtBGcBXk4XddRCstz7qTsTmPFxOPISEmDq1mN8.
Please contact your system administrator.
Add correct host key in /home/emarq/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/emarq/.ssh/known_hosts:12
remove with:
ssh-keygen -f "/home/emarq/.ssh/known_hosts" -R 10.10.230.13
RSA host key for 10.10.230.13 has changed and you have requested strict checking.
Host key verification failed.
``` | True | nxos_command paramiko.ssh_exception.BadHostKeyException bad key exception failure - <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
nxos_command
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0.0
config file = /home/emarq/Solutions.Network.Automation/MAS/Ansible/cisco/nexus/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
```
[defaults]
hostfile=localstage
#hostfile=mas-b43
ansible_ssh_user=admin
ansible_ssh_private_key_file=/home/emarq/.ssh/masd-rsa
host_key_checking=False
```
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
##### SUMMARY
<!--- Explain the problem briefly -->
An updated switch configuration is sent to the switch. The switch get's reloaded. Post reload the ssh server key has changed on the switch. The public key that is stored in known_hosts is no longer valid. paramiko throws an error and fails. in the Ansible config file, the host_key_checking=False is set.
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
---
- name: Delete remote config
nxos_command:
provider: "{{ cli }}"
host: "{{ ansible_host }}"
commands:
- "delete bootflash:{{ inventory_hostname }}.conf "
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
ignore ssh key change and establish a connection.
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
An exception occurred during task execution. The full traceback is:
Traceback (most recent call last):
File "/tmp/ansible_sespbZ/ansible_module_nxos_command.py", line 257, in <module>
main()
File "/tmp/ansible_sespbZ/ansible_module_nxos_command.py", line 193, in main
supports_check_mode=True)
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py", line 112, in __init__
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py", line 148, in connect
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/nxos.py", line 266, in connect
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py", line 226, in connect
File "/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py", line 96, in open
File "/usr/lib/python2.7/dist-packages/paramiko/client.py", line 353, in connect
raise BadHostKeyException(hostname, server_key, our_server_key)
paramiko.ssh_exception.BadHostKeyException: ('10.10.230.12', <paramiko.rsakey.RSAKey object at 0x7f70d1c3f090>, <paramiko.rsakey.RSAKey object at 0x7f70d1c32b90>)
fatal: [rr1-n35-r10-x32sp-2a]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_name": "nxos_command"
},
"module_stderr": "Traceback (most recent call last):\n File \"/tmp/ansible_sespbZ/ansible_module_nxos_command.py\", line 257, in <module>\n main()\n File \"/tmp/ansible_sespbZ/ansible_module_nxos_command.py\", line 193, in main\n supports_check_mode=True)\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py\", line 112, in __init__\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/network.py\", line 148, in connect\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/nxos.py\", line 266, in connect\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py\", line 226, in connect\n File \"/tmp/ansible_sespbZ/ansible_modlib.zip/ansible/module_utils/shell.py\", line 96, in open\n File \"/usr/lib/python2.7/dist-packages/paramiko/client.py\", line 353, in connect\n raise BadHostKeyException(hostname, server_key, our_server_key)\nparamiko.ssh_exception.BadHostKeyException: ('10.10.230.12', <paramiko.rsakey.RSAKey object at 0x7f70d1c3f090>, <paramiko.rsakey.RSAKey object at 0x7f70d1c32b90>)\n",
"module_stdout": "",
"msg": "MODULE FAILURE"
}
```
ssh response to the key
```
emarq@rr1masdansible:~/Solutions.Network.Automation/MAS/Ansible/cisco/nexus$ ssh admin@10.10.230.13 -vvvvv
OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /home/emarq/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "10.10.230.13" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 10.10.230.13 [10.10.230.13] port 22.
debug1: Connection established.
debug1: identity file /home/emarq/.ssh/masd-rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/emarq/.ssh/masd-rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
debug1: ssh_exchange_identification: dcos_sshd run in non-FIPS mode
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2 FIPS
debug1: match: OpenSSH_6.2 FIPS pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 10.10.230.13:22 as 'admin'
debug3: hostkeys_foreach: reading file "/home/emarq/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/emarq/.ssh/known_hosts:12
debug3: load_hostkeys: loaded 1 keys from 10.10.230.13
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: host key algorithms: ssh-rsa
debug2: ciphers ctos: aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: ciphers stoc: aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: MACs ctos: hmac-sha1
debug2: MACs stoc: hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: diffie-hellman-group-exchange-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug3: send packet: type 34
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(2048<7680<8192) sent
debug3: receive packet: type 31
debug1: got SSH2_MSG_KEX_DH_GEX_GROUP
debug2: bits set: 1017/2048
debug3: send packet: type 32
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug3: receive packet: type 33
debug1: got SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: ssh-rsa SHA256:KwU71WtBGcBXk4XddRCstz7qTsTmPFxOPISEmDq1mN8
debug3: hostkeys_foreach: reading file "/home/emarq/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/emarq/.ssh/known_hosts:12
debug3: load_hostkeys: loaded 1 keys from 10.10.230.13
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:KwU71WtBGcBXk4XddRCstz7qTsTmPFxOPISEmDq1mN8.
Please contact your system administrator.
Add correct host key in /home/emarq/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/emarq/.ssh/known_hosts:12
remove with:
ssh-keygen -f "/home/emarq/.ssh/known_hosts" -R 10.10.230.13
RSA host key for 10.10.230.13 has changed and you have requested strict checking.
Host key verification failed.
``` | main | nxos command paramiko ssh exception badhostkeyexception bad key exception failure issue type bug report component name nxos command ansible version ansible config file home emarq solutions network automation mas ansible cisco nexus ansible cfg configured module search path default w o overrides configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables hostfile localstage hostfile mas ansible ssh user admin ansible ssh private key file home emarq ssh masd rsa host key checking false os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific summary an updated switch configuration is sent to the switch the switch get s reloaded post reload the ssh server key has changed on the switch the public key that is stored in known hosts is no longer valid paramiko throws an error and fails in the ansible config file the host key checking false is set steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used name delete remote config nxos command provider cli host ansible host commands delete bootflash inventory hostname conf expected results ignore ssh key change and establish a connection actual results an exception occurred during task execution the full traceback is traceback most recent call last file tmp ansible sespbz ansible module nxos command py line in main file tmp ansible sespbz ansible module nxos command py line in main supports check mode true file tmp ansible sespbz ansible modlib zip ansible module utils network py line in init file tmp ansible sespbz ansible modlib zip ansible module utils network py line in connect file tmp ansible sespbz ansible modlib zip ansible module utils nxos py line in connect file tmp ansible sespbz ansible modlib zip ansible module utils shell py line in connect file tmp ansible sespbz ansible modlib zip ansible module utils shell py line in open file usr lib dist packages paramiko client py line in connect raise badhostkeyexception hostname server key our server key paramiko ssh exception badhostkeyexception fatal failed changed false failed true invocation module name nxos command module stderr traceback most recent call last n file tmp ansible sespbz ansible module nxos command py line in n main n file tmp ansible sespbz ansible module nxos command py line in main n supports check mode true n file tmp ansible sespbz ansible modlib zip ansible module utils network py line in init n file tmp ansible sespbz ansible modlib zip ansible module utils network py line in connect n file tmp ansible sespbz ansible modlib zip ansible module utils nxos py line in connect n file tmp ansible sespbz ansible modlib zip ansible module utils shell py line in connect n file tmp ansible sespbz ansible modlib zip ansible module utils shell py line in open n file usr lib dist packages paramiko client py line in connect n raise badhostkeyexception hostname server key our server key nparamiko ssh exception badhostkeyexception n module stdout msg module failure ssh response to the key emarq solutions network automation mas ansible cisco nexus ssh admin vvvvv openssh ubuntu openssl mar reading configuration data home emarq ssh config reading configuration data etc ssh ssh config etc ssh ssh config line applying options for resolving port ssh connect direct needpriv connecting to port connection established identity file home emarq ssh masd rsa type key load public no such file or directory identity file home emarq ssh masd rsa cert type enabling compatibility mode for protocol local version string ssh openssh ubuntu ssh exchange identification dcos sshd run in non fips mode remote protocol version remote software version openssh fips match openssh fips pat openssh compat fd setting o nonblock authenticating to as admin hostkeys foreach reading file home emarq ssh known hosts record hostkey found key type rsa in file home emarq ssh known hosts load hostkeys loaded keys from order hostkeyalgs prefer hostkeyalgs ssh rsa cert openssh com rsa rsa ssh rsa send packet type msg kexinit sent receive packet type msg kexinit received local client kexinit proposal kex algorithms libssh org ecdh ecdh ecdh diffie hellman group exchange diffie hellman group exchange diffie hellman ext info c host key algorithms ssh rsa cert openssh com rsa rsa ssh rsa ecdsa cert openssh com ecdsa cert openssh com ecdsa cert openssh com ssh cert openssh com ecdsa ecdsa ecdsa ssh ciphers ctos openssh com ctr ctr ctr gcm openssh com gcm openssh com cbc cbc cbc cbc ciphers stoc openssh com ctr ctr ctr gcm openssh com gcm openssh com cbc cbc cbc cbc macs ctos umac etm openssh com umac etm openssh com hmac etm openssh com hmac etm openssh com hmac etm openssh com umac openssh com umac openssh com hmac hmac hmac macs stoc umac etm openssh com umac etm openssh com hmac etm openssh com hmac etm openssh com hmac etm openssh com umac openssh com umac openssh com hmac hmac hmac compression ctos none zlib openssh com zlib compression stoc none zlib openssh com zlib languages ctos languages stoc first kex follows reserved peer server kexinit proposal kex algorithms diffie hellman group exchange diffie hellman group exchange diffie hellman diffie hellman host key algorithms ssh rsa ciphers ctos cbc cbc cbc cbc rijndael cbc lysator liu se ctr ctr ctr ciphers stoc cbc cbc cbc cbc rijndael cbc lysator liu se ctr ctr ctr macs ctos hmac macs stoc hmac compression ctos none zlib openssh com compression stoc none zlib openssh com languages ctos languages stoc first kex follows reserved kex algorithm diffie hellman group exchange kex host key algorithm ssh rsa kex server client cipher ctr mac hmac compression none kex client server cipher ctr mac hmac compression none send packet type msg kex dh gex request sent receive packet type got msg kex dh gex group bits set send packet type msg kex dh gex init sent receive packet type got msg kex dh gex reply server host key ssh rsa hostkeys foreach reading file home emarq ssh known hosts record hostkey found key type rsa in file home emarq ssh known hosts load hostkeys loaded keys from warning remote host identification has changed it is possible that someone is doing something nasty someone could be eavesdropping on you right now man in the middle attack it is also possible that a host key has just been changed the fingerprint for the rsa key sent by the remote host is please contact your system administrator add correct host key in home emarq ssh known hosts to get rid of this message offending rsa key in home emarq ssh known hosts remove with ssh keygen f home emarq ssh known hosts r rsa host key for has changed and you have requested strict checking host key verification failed | 1 |
5,395 | 27,108,566,017 | IssuesEvent | 2023-02-15 13:52:58 | centerofci/mathesar | https://api.github.com/repos/centerofci/mathesar | closed | Usability testing for basic Mathesar features | restricted: maintainers type: meta work: product status: started | - [x] Come up with scenarios
- [x] Run tests
- [x] Process and analyze tests - https://hackmd.io/@mathesar/B1aXELfpj
- [x] Put usability testing videos on our Google Drive
- [x] Create GitHub issues for launch blockers or nice-to-have
- [x] Decide if we need to run additional tests – *we're not doing further tests* | True | Usability testing for basic Mathesar features - - [x] Come up with scenarios
- [x] Run tests
- [x] Process and analyze tests - https://hackmd.io/@mathesar/B1aXELfpj
- [x] Put usability testing videos on our Google Drive
- [x] Create GitHub issues for launch blockers or nice-to-have
- [x] Decide if we need to run additional tests – *we're not doing further tests* | main | usability testing for basic mathesar features come up with scenarios run tests process and analyze tests put usability testing videos on our google drive create github issues for launch blockers or nice to have decide if we need to run additional tests – we re not doing further tests | 1 |
1,782 | 6,575,831,237 | IssuesEvent | 2017-09-11 17:29:48 | ansible/ansible-modules-core | https://api.github.com/repos/ansible/ansible-modules-core | closed | rpm_key key_id verification erroneous | affects_2.1 bug_report waiting_on_maintainer | ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ansible-modules-core/packaging/os/rpm_key.py
##### ANSIBLE VERSION
```
ansible 2.1.0.0
```
##### CONFIGURATION
not relevant
##### OS / ENVIRONMENT
N/A
Redhat/Centos rpm-based
##### SUMMARY
Function is_key_imported does not work reliably because
Function getkeyid only extracts the last part of the first signature packet,
therefore the key will be imported on every ansible run
##### STEPS TO REPRODUCE
Install the Mono gpg key (from the Ubuntu keyserver, as per official docu):
```
http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
```
Short Summary:
`getkeyid()` essentially runs
`gpg --no-tty --batch --with-colons --fixed-list-mode --list-packets /tmp/key.1 |grep signature`
And returns the last 8 characters of the first key id it finds.
Then `is_key_imported()` runs
`rpm -qa gpg-pubkey` and matches the keyid against the first key part of the filename:
gpg-pubkey-**d3d831ef**-53dfa827
This does'nt work with the Mono key because
`gpg --no-tty --batch --with-colons --fixed-list-mode --list-packets /tmp/key.1 |grep signature`
returns:
```
:signature packet: algo 1, keyid C90F9CB90E1FAD0C
:signature packet: algo 1, keyid A6A19B38D3D831EF
:signature packet: algo 1, keyid A6A19B38D3D831EF
```
and so the last 8 characters of the second keyid match the first 8 character set of the rpm key information
Perhaps verifying the Fingerprint of the keys, or verify the full key ids(patch following):
``````
--- rpm_key.py 2016-09-30 13:38:31.000000000 +0200
+++ new_rpm_key.py 2016-09-30 14:49:18.000000000 +0200
@@ -149,33 +149,27 @@
stdout, stderr = self.execute_command([gpg, '--no-tty', '--batch', '--with-colons', '--fixed-list-mode', '--list-packets', keyfile])
for line in stdout.splitlines():
line = line.strip()
- if line.startswith(':signature packet:'):
- # We want just the last 8 characters of the keyid
- keyid = line.split()[-1].strip()[8:]
+ if "keyid:" in line:
+ keyid = line.split()[-1]
return keyid
self.json_fail(msg="Unexpected gpg output")
def is_keyid(self, keystr):
"""Verifies if a key, as provided by the user is a keyid"""
- return re.match('(0x)?[0-9a-f]{8}', keystr, flags=re.IGNORECASE)
+ return re.match('(0x)?[0-9a-f]{16}', keystr, flags=re.IGNORECASE)
def execute_command(self, cmd):
- rc, stdout, stderr = self.module.run_command(cmd)
+ rc, stdout, stderr = self.module.run_command(cmd,use_unsafe_shell=True)
if rc != 0:
self.module.fail_json(msg=stderr)
return stdout, stderr
def is_key_imported(self, keyid):
- stdout, stderr = self.execute_command([self.rpm, '-qa', 'gpg-pubkey'])
+ cmd=self.rpm+' -q gpg-pubkey --qf "%{description}" | gpg --no-tty --batch --with-colons --fixed-list-mode --list-packets -'
+ stdout, stderr = self.execute_command(cmd)
for line in stdout.splitlines():
- line = line.strip()
- if not line:
- continue
- match = re.match('gpg-pubkey-([0-9a-f]+)-([0-9a-f]+)', line)
- if not match:
- self.module.fail_json(msg="rpm returned unexpected output [%s]" % line)
- else:
- if keyid == match.group(1):
+ if "keyid: " in line:
+ if keyid.upper() == line.split()[-1].upper():
return True
return False```
``````
| True | rpm_key key_id verification erroneous - ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
ansible-modules-core/packaging/os/rpm_key.py
##### ANSIBLE VERSION
```
ansible 2.1.0.0
```
##### CONFIGURATION
not relevant
##### OS / ENVIRONMENT
N/A
Redhat/Centos rpm-based
##### SUMMARY
Function is_key_imported does not work reliably because
Function getkeyid only extracts the last part of the first signature packet,
therefore the key will be imported on every ansible run
##### STEPS TO REPRODUCE
Install the Mono gpg key (from the Ubuntu keyserver, as per official docu):
```
http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
```
Short Summary:
`getkeyid()` essentially runs
`gpg --no-tty --batch --with-colons --fixed-list-mode --list-packets /tmp/key.1 |grep signature`
And returns the last 8 characters of the first key id it finds.
Then `is_key_imported()` runs
`rpm -qa gpg-pubkey` and matches the keyid against the first key part of the filename:
gpg-pubkey-**d3d831ef**-53dfa827
This does'nt work with the Mono key because
`gpg --no-tty --batch --with-colons --fixed-list-mode --list-packets /tmp/key.1 |grep signature`
returns:
```
:signature packet: algo 1, keyid C90F9CB90E1FAD0C
:signature packet: algo 1, keyid A6A19B38D3D831EF
:signature packet: algo 1, keyid A6A19B38D3D831EF
```
and so the last 8 characters of the second keyid match the first 8 character set of the rpm key information
Perhaps verifying the Fingerprint of the keys, or verify the full key ids(patch following):
``````
--- rpm_key.py 2016-09-30 13:38:31.000000000 +0200
+++ new_rpm_key.py 2016-09-30 14:49:18.000000000 +0200
@@ -149,33 +149,27 @@
stdout, stderr = self.execute_command([gpg, '--no-tty', '--batch', '--with-colons', '--fixed-list-mode', '--list-packets', keyfile])
for line in stdout.splitlines():
line = line.strip()
- if line.startswith(':signature packet:'):
- # We want just the last 8 characters of the keyid
- keyid = line.split()[-1].strip()[8:]
+ if "keyid:" in line:
+ keyid = line.split()[-1]
return keyid
self.json_fail(msg="Unexpected gpg output")
def is_keyid(self, keystr):
"""Verifies if a key, as provided by the user is a keyid"""
- return re.match('(0x)?[0-9a-f]{8}', keystr, flags=re.IGNORECASE)
+ return re.match('(0x)?[0-9a-f]{16}', keystr, flags=re.IGNORECASE)
def execute_command(self, cmd):
- rc, stdout, stderr = self.module.run_command(cmd)
+ rc, stdout, stderr = self.module.run_command(cmd,use_unsafe_shell=True)
if rc != 0:
self.module.fail_json(msg=stderr)
return stdout, stderr
def is_key_imported(self, keyid):
- stdout, stderr = self.execute_command([self.rpm, '-qa', 'gpg-pubkey'])
+ cmd=self.rpm+' -q gpg-pubkey --qf "%{description}" | gpg --no-tty --batch --with-colons --fixed-list-mode --list-packets -'
+ stdout, stderr = self.execute_command(cmd)
for line in stdout.splitlines():
- line = line.strip()
- if not line:
- continue
- match = re.match('gpg-pubkey-([0-9a-f]+)-([0-9a-f]+)', line)
- if not match:
- self.module.fail_json(msg="rpm returned unexpected output [%s]" % line)
- else:
- if keyid == match.group(1):
+ if "keyid: " in line:
+ if keyid.upper() == line.split()[-1].upper():
return True
return False```
``````
| main | rpm key key id verification erroneous issue type bug report component name ansible modules core packaging os rpm key py ansible version ansible configuration not relevant os environment n a redhat centos rpm based summary function is key imported does not work reliably because function getkeyid only extracts the last part of the first signature packet therefore the key will be imported on every ansible run steps to reproduce install the mono gpg key from the ubuntu keyserver as per official docu short summary getkeyid essentially runs gpg no tty batch with colons fixed list mode list packets tmp key grep signature and returns the last characters of the first key id it finds then is key imported runs rpm qa gpg pubkey and matches the keyid against the first key part of the filename gpg pubkey this does nt work with the mono key because gpg no tty batch with colons fixed list mode list packets tmp key grep signature returns signature packet algo keyid signature packet algo keyid signature packet algo keyid and so the last characters of the second keyid match the first character set of the rpm key information perhaps verifying the fingerprint of the keys or verify the full key ids patch following rpm key py new rpm key py stdout stderr self execute command for line in stdout splitlines line line strip if line startswith signature packet we want just the last characters of the keyid keyid line split strip if keyid in line keyid line split return keyid self json fail msg unexpected gpg output def is keyid self keystr verifies if a key as provided by the user is a keyid return re match keystr flags re ignorecase return re match keystr flags re ignorecase def execute command self cmd rc stdout stderr self module run command cmd rc stdout stderr self module run command cmd use unsafe shell true if rc self module fail json msg stderr return stdout stderr def is key imported self keyid stdout stderr self execute command cmd self rpm q gpg pubkey qf description gpg no tty batch with colons fixed list mode list packets stdout stderr self execute command cmd for line in stdout splitlines line line strip if not line continue match re match gpg pubkey line if not match self module fail json msg rpm returned unexpected output line else if keyid match group if keyid in line if keyid upper line split upper return true return false | 1 |
153,690 | 19,708,559,827 | IssuesEvent | 2022-01-13 01:40:57 | artsking/linux-4.19.72_CVE-2020-14386 | https://api.github.com/repos/artsking/linux-4.19.72_CVE-2020-14386 | opened | CVE-2020-16119 (High) detected in linux-yoctov5.4.51 | security vulnerability | ## CVE-2020-16119 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/dccp/minisocks.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/dccp/minisocks.c</b>
</p>
</details>
<p></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>
Use-after-free vulnerability in the Linux kernel exploitable by a local attacker due to reuse of a DCCP socket with an attached dccps_hc_tx_ccid object as a listener after being released. Fixed in Ubuntu Linux kernel 5.4.0-51.56, 5.3.0-68.63, 4.15.0-121.123, 4.4.0-193.224, 3.13.0.182.191 and 3.2.0-149.196.
<p>Publish Date: 2021-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-16119>CVE-2020-16119</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>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-16119 (High) detected in linux-yoctov5.4.51 - ## CVE-2020-16119 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/dccp/minisocks.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/dccp/minisocks.c</b>
</p>
</details>
<p></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>
Use-after-free vulnerability in the Linux kernel exploitable by a local attacker due to reuse of a DCCP socket with an attached dccps_hc_tx_ccid object as a listener after being released. Fixed in Ubuntu Linux kernel 5.4.0-51.56, 5.3.0-68.63, 4.15.0-121.123, 4.4.0-193.224, 3.13.0.182.191 and 3.2.0-149.196.
<p>Publish Date: 2021-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-16119>CVE-2020-16119</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>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_main | cve high detected in linux cve high severity vulnerability vulnerable library linux yocto linux embedded kernel library home page a href found in base branch master vulnerable source files net dccp minisocks c net dccp minisocks c vulnerability details use after free vulnerability in the linux kernel exploitable by a local attacker due to reuse of a dccp socket with an attached dccps hc tx ccid object as a listener after being released fixed in ubuntu linux kernel and publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href step up your open source security game with whitesource | 0 |
5,694 | 30,002,436,074 | IssuesEvent | 2023-06-26 10:10:03 | precice/precice | https://api.github.com/repos/precice/precice | opened | Don't allow duplicate read/write-data names on different meshes | maintainability breaking change | The following configuration is currently allowed:
```
<participant name="SolverTwo">
<receive-mesh name="MeshOne" from="SolverOne" />
<provide-mesh name="MeshTwo" />
...
<write-data name="DataTwo" mesh="MeshTwo" />
<read-data name="DataOne" mesh="MeshTwo" />
<read-data name="DataOne" mesh="MeshOne" />
</participant>
```
I would suggest to only allow unique names for `read-data`, since this would simplify the implementation. (I was just trying to navigate from an `exchange` tag to the corresponding `read-data` to perform some checks. This usually works, but there is no guarantee, if multiple `read-data` with identical names exist)
Is there an actual use-case for using the same data name for `read-data` on different meshes?
Remark: I guess this might also help us to further simplify the read/write API. | True | Don't allow duplicate read/write-data names on different meshes - The following configuration is currently allowed:
```
<participant name="SolverTwo">
<receive-mesh name="MeshOne" from="SolverOne" />
<provide-mesh name="MeshTwo" />
...
<write-data name="DataTwo" mesh="MeshTwo" />
<read-data name="DataOne" mesh="MeshTwo" />
<read-data name="DataOne" mesh="MeshOne" />
</participant>
```
I would suggest to only allow unique names for `read-data`, since this would simplify the implementation. (I was just trying to navigate from an `exchange` tag to the corresponding `read-data` to perform some checks. This usually works, but there is no guarantee, if multiple `read-data` with identical names exist)
Is there an actual use-case for using the same data name for `read-data` on different meshes?
Remark: I guess this might also help us to further simplify the read/write API. | main | don t allow duplicate read write data names on different meshes the following configuration is currently allowed i would suggest to only allow unique names for read data since this would simplify the implementation i was just trying to navigate from an exchange tag to the corresponding read data to perform some checks this usually works but there is no guarantee if multiple read data with identical names exist is there an actual use case for using the same data name for read data on different meshes remark i guess this might also help us to further simplify the read write api | 1 |
1,933 | 6,609,877,225 | IssuesEvent | 2017-09-19 15:50:01 | Kristinita/Erics-Green-Room | https://api.github.com/repos/Kristinita/Erics-Green-Room | closed | [Feature request] Показ всех засчитываемых ответов | need-maintainer | ### 1. Запрос
Неплохо было бы, если игрок видел бы все ответы, которые засчитываются.
### 2. Аргументация
1. **Развивающие цели**. Узнать синонимы к понятию/понятиям ответа, другие его/их названия.
1. **Помощь редактору**. В процессе игры тренирующемуся могут прийти в голову ответы, фактически являющиеся правильными, но не являющиеся авторскими. Если тренирующийся будет видеть все возможные засчитываемые варианты ответов, ему легче будет ориентироваться, какие варианты ответов можно ещё добавить в пакет, а какие уже есть.
### 3. Примеры
Данная функция была реализована на турнирах Альфа-хаба 2015 года. Примеры:
```markdown
[20:40:02] <Турнир> Правильный ответ: "Краткая история времени"
[20:40:02] <Турнир> Ещё варианты ответов: 'A Brief History of Time'
[20:02:25] <Турнир> Правильный ответ: "filimania.ru"
[20:02:25] <Турнир> Ещё варианты ответов: 'филимания', 'филимания.ру'
```
Спасибо. | True | [Feature request] Показ всех засчитываемых ответов - ### 1. Запрос
Неплохо было бы, если игрок видел бы все ответы, которые засчитываются.
### 2. Аргументация
1. **Развивающие цели**. Узнать синонимы к понятию/понятиям ответа, другие его/их названия.
1. **Помощь редактору**. В процессе игры тренирующемуся могут прийти в голову ответы, фактически являющиеся правильными, но не являющиеся авторскими. Если тренирующийся будет видеть все возможные засчитываемые варианты ответов, ему легче будет ориентироваться, какие варианты ответов можно ещё добавить в пакет, а какие уже есть.
### 3. Примеры
Данная функция была реализована на турнирах Альфа-хаба 2015 года. Примеры:
```markdown
[20:40:02] <Турнир> Правильный ответ: "Краткая история времени"
[20:40:02] <Турнир> Ещё варианты ответов: 'A Brief History of Time'
[20:02:25] <Турнир> Правильный ответ: "filimania.ru"
[20:02:25] <Турнир> Ещё варианты ответов: 'филимания', 'филимания.ру'
```
Спасибо. | main | показ всех засчитываемых ответов запрос неплохо было бы если игрок видел бы все ответы которые засчитываются аргументация развивающие цели узнать синонимы к понятию понятиям ответа другие его их названия помощь редактору в процессе игры тренирующемуся могут прийти в голову ответы фактически являющиеся правильными но не являющиеся авторскими если тренирующийся будет видеть все возможные засчитываемые варианты ответов ему легче будет ориентироваться какие варианты ответов можно ещё добавить в пакет а какие уже есть примеры данная функция была реализована на турнирах альфа хаба года примеры markdown правильный ответ краткая история времени ещё варианты ответов a brief history of time правильный ответ filimania ru ещё варианты ответов филимания филимания ру спасибо | 1 |
252,522 | 21,582,735,300 | IssuesEvent | 2022-05-02 20:36:58 | damccorm/test-migration-target | https://api.github.com/repos/damccorm/test-migration-target | opened | Java Examples are failing for different runners | test P2 testing examples-java | With the recent addition of suites to continuously test Java examples in different runners, some existing integration tests fail for different runners
* `_`org.apache.beam.examples.WindowedWordCountIT.testWindowedWordCountInBatchDynamicSharding`_`, fails in FlinkRunner with AssertionError, for DirectRunner and SparkRunner the test never finishes.
* _org.apache.beam.examples.WindowedWordCountIT.testWindowedWordCountInStreamingStaticSharding_ fails in SparkRunner with error _Failed to read from sharded output_
* _org.apache.beam.examples.cookbook.BigQueryTornadoesIT.testE2eBigQueryTornadoesWithStorageApiUsingQuery_ fails in FlinkRunner with _Error deleting table, Not found: Dataset_
Imported from Jira [BEAM-14019](https://issues.apache.org/jira/browse/BEAM-14019). Original Jira may contain additional context.
Reported by: benglez. | 2.0 | Java Examples are failing for different runners - With the recent addition of suites to continuously test Java examples in different runners, some existing integration tests fail for different runners
* `_`org.apache.beam.examples.WindowedWordCountIT.testWindowedWordCountInBatchDynamicSharding`_`, fails in FlinkRunner with AssertionError, for DirectRunner and SparkRunner the test never finishes.
* _org.apache.beam.examples.WindowedWordCountIT.testWindowedWordCountInStreamingStaticSharding_ fails in SparkRunner with error _Failed to read from sharded output_
* _org.apache.beam.examples.cookbook.BigQueryTornadoesIT.testE2eBigQueryTornadoesWithStorageApiUsingQuery_ fails in FlinkRunner with _Error deleting table, Not found: Dataset_
Imported from Jira [BEAM-14019](https://issues.apache.org/jira/browse/BEAM-14019). Original Jira may contain additional context.
Reported by: benglez. | non_main | java examples are failing for different runners with the recent addition of suites to continuously test java examples in different runners some existing integration tests fail for different runners org apache beam examples windowedwordcountit testwindowedwordcountinbatchdynamicsharding fails in flinkrunner with assertionerror for directrunner and sparkrunner the test never finishes org apache beam examples windowedwordcountit testwindowedwordcountinstreamingstaticsharding fails in sparkrunner with error failed to read from sharded output org apache beam examples cookbook bigquerytornadoesit fails in flinkrunner with error deleting table not found dataset imported from jira original jira may contain additional context reported by benglez | 0 |
4,698 | 24,239,819,878 | IssuesEvent | 2022-09-27 05:15:23 | aws/aws-sam-cli | https://api.github.com/repos/aws/aws-sam-cli | closed | How to debug Node Lambda using TypeScript | type/question maintainer/need-followup | Does anyone has successfully debug the Lambda function using TypeScript? If so, can you share configurations? | True | How to debug Node Lambda using TypeScript - Does anyone has successfully debug the Lambda function using TypeScript? If so, can you share configurations? | main | how to debug node lambda using typescript does anyone has successfully debug the lambda function using typescript if so can you share configurations | 1 |
141,815 | 5,444,892,165 | IssuesEvent | 2017-03-07 05:01:37 | patxu/cs98-senior-project | https://api.github.com/repos/patxu/cs98-senior-project | closed | Classification performance seems to be worse with auto detection | High Priority | Is this just me or have other people been finding this? My guess is we might not be waiting long enough after switching the screen to black before we grab a frame and classify off of it. I imagine there is some lag between when we change the color and when the actual projector changes color. Is it possible this is slower than the code running? - @db2882 | 1.0 | Classification performance seems to be worse with auto detection - Is this just me or have other people been finding this? My guess is we might not be waiting long enough after switching the screen to black before we grab a frame and classify off of it. I imagine there is some lag between when we change the color and when the actual projector changes color. Is it possible this is slower than the code running? - @db2882 | non_main | classification performance seems to be worse with auto detection is this just me or have other people been finding this my guess is we might not be waiting long enough after switching the screen to black before we grab a frame and classify off of it i imagine there is some lag between when we change the color and when the actual projector changes color is it possible this is slower than the code running | 0 |
84,536 | 15,724,681,552 | IssuesEvent | 2021-03-29 09:05:45 | crouchr/learnage | https://api.github.com/repos/crouchr/learnage | opened | CVE-2017-12376 (High) detected in multiple libraries | security vulnerability | ## CVE-2017-12376 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>clamav-develclamav-0.97</b>, <b>salix-sboclamav-0.97.5</b>, <b>clamav-develclamav-0.98.4</b></p></summary>
<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>
ClamAV AntiVirus software versions 0.99.2 and prior contain a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition or potentially execute arbitrary code on an affected device. The vulnerability is due to improper input validation checking mechanisms when handling Portable Document Format (.pdf) files sent to an affected device. An unauthenticated, remote attacker could exploit this vulnerability by sending a crafted .pdf file to an affected device. This action could cause a handle_pdfname (in pdf.c) buffer overflow when ClamAV scans the malicious file, allowing the attacker to cause a DoS condition or potentially execute arbitrary code.
<p>Publish Date: 2018-01-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-12376>CVE-2017-12376</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>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-12376">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-12376</a></p>
<p>Release Date: 2018-01-26</p>
<p>Fix Resolution: clamav-0.99.3-beta2</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-2017-12376 (High) detected in multiple libraries - ## CVE-2017-12376 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>clamav-develclamav-0.97</b>, <b>salix-sboclamav-0.97.5</b>, <b>clamav-develclamav-0.98.4</b></p></summary>
<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>
ClamAV AntiVirus software versions 0.99.2 and prior contain a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition or potentially execute arbitrary code on an affected device. The vulnerability is due to improper input validation checking mechanisms when handling Portable Document Format (.pdf) files sent to an affected device. An unauthenticated, remote attacker could exploit this vulnerability by sending a crafted .pdf file to an affected device. This action could cause a handle_pdfname (in pdf.c) buffer overflow when ClamAV scans the malicious file, allowing the attacker to cause a DoS condition or potentially execute arbitrary code.
<p>Publish Date: 2018-01-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-12376>CVE-2017-12376</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>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-12376">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-12376</a></p>
<p>Release Date: 2018-01-26</p>
<p>Fix Resolution: clamav-0.99.3-beta2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_main | cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries clamav develclamav salix sboclamav clamav develclamav vulnerability details clamav antivirus software versions and prior contain a vulnerability that could allow an unauthenticated remote attacker to cause a denial of service dos condition or potentially execute arbitrary code on an affected device the vulnerability is due to improper input validation checking mechanisms when handling portable document format pdf files sent to an affected device an unauthenticated remote attacker could exploit this vulnerability by sending a crafted pdf file to an affected device this action could cause a handle pdfname in pdf c buffer overflow when clamav scans the malicious file allowing the attacker to cause a dos condition or potentially execute arbitrary code publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution clamav step up your open source security game with whitesource | 0 |
2,327 | 8,320,258,780 | IssuesEvent | 2018-09-25 19:39:31 | TabbycatDebate/tabbycat | https://api.github.com/repos/TabbycatDebate/tabbycat | closed | Check/implement a conflict test for double-past institution conflicts | admin ui awaiting maintainer wudc2019 | IIRC we don't currently check/test for situations where a speaker has a past institution in a debate with an adjudicator who also shares a past institution with them. That said checking for this kind of test would probably involve changing the `Institution` data structure in a significant way which may not be worth the effort.
A workaround could be adding a new form of conflict, say `TeamInstitutionConflict` that nominates that past institution which could then be checked against `AdjudicatorInstitutionConflict`. | True | Check/implement a conflict test for double-past institution conflicts - IIRC we don't currently check/test for situations where a speaker has a past institution in a debate with an adjudicator who also shares a past institution with them. That said checking for this kind of test would probably involve changing the `Institution` data structure in a significant way which may not be worth the effort.
A workaround could be adding a new form of conflict, say `TeamInstitutionConflict` that nominates that past institution which could then be checked against `AdjudicatorInstitutionConflict`. | main | check implement a conflict test for double past institution conflicts iirc we don t currently check test for situations where a speaker has a past institution in a debate with an adjudicator who also shares a past institution with them that said checking for this kind of test would probably involve changing the institution data structure in a significant way which may not be worth the effort a workaround could be adding a new form of conflict say teaminstitutionconflict that nominates that past institution which could then be checked against adjudicatorinstitutionconflict | 1 |
208,778 | 23,650,871,034 | IssuesEvent | 2022-08-26 06:27:28 | Satheesh575555/packages_apps_Settings_AOSP10_r33_CVE-2020-0416 | https://api.github.com/repos/Satheesh575555/packages_apps_Settings_AOSP10_r33_CVE-2020-0416 | closed | CVE-2022-20112 (Medium) detected in Settingsandroid-10.0.0_r44 - autoclosed | security vulnerability | ## CVE-2022-20112 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Settingsandroid-10.0.0_r44</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/packages/apps/Settings>https://android.googlesource.com/platform/packages/apps/Settings</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/src/com/android/settings/network/PrivateDnsPreferenceController.java</b>
</p>
</details>
<p></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>
In getAvailabilityStatus of PrivateDnsPreferenceController.java, there is a possible way for a guest user to change private DNS settings due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-206987762
<p>Publish Date: 2022-05-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-20112>CVE-2022-20112</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</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://source.android.com/security/bulletin/2022-05-01">https://source.android.com/security/bulletin/2022-05-01</a></p>
<p>Release Date: 2022-05-10</p>
<p>Fix Resolution: android-12.1.0_r5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-20112 (Medium) detected in Settingsandroid-10.0.0_r44 - autoclosed - ## CVE-2022-20112 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Settingsandroid-10.0.0_r44</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/packages/apps/Settings>https://android.googlesource.com/platform/packages/apps/Settings</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/src/com/android/settings/network/PrivateDnsPreferenceController.java</b>
</p>
</details>
<p></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>
In getAvailabilityStatus of PrivateDnsPreferenceController.java, there is a possible way for a guest user to change private DNS settings due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-206987762
<p>Publish Date: 2022-05-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-20112>CVE-2022-20112</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.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</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://source.android.com/security/bulletin/2022-05-01">https://source.android.com/security/bulletin/2022-05-01</a></p>
<p>Release Date: 2022-05-10</p>
<p>Fix Resolution: android-12.1.0_r5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_main | cve medium detected in settingsandroid autoclosed cve medium severity vulnerability vulnerable library settingsandroid library home page a href found in base branch master vulnerable source files src com android settings network privatednspreferencecontroller java vulnerability details in getavailabilitystatus of privatednspreferencecontroller java there is a possible way for a guest user to change private dns settings due to a permissions bypass this could lead to local escalation of privilege with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android android android android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution android step up your open source security game with mend | 0 |
8,989 | 3,814,478,904 | IssuesEvent | 2016-03-28 13:35:19 | zeqing-guo/algorithms-study | https://api.github.com/repos/zeqing-guo/algorithms-study | opened | Leetcode-173: Binary Search Tree Iterator | Design Leetcode Stack Tree |
## Description
Implement an iterator over a binary search tree (BST). Your iterator will be initialized with the root node of a BST.
Calling `next()` will return the next smallest number in the BST.
Note: `next()` and `hasNext()` should run in average  time and uses  memory, where h is the height of the tree.
## My Solution
代码的run time是5ms (95.39%)。
```java
/**
* Definition for binary tree
* public class TreeNode {
* int val;
* TreeNode left;
* TreeNode right;
* TreeNode(int x) { val = x; }
* }
*/
public class BSTIterator {
private TreeNode root = null;
private TreeNode parent = null;
private TreeNode node = null;
public BSTIterator(TreeNode root) {
this.root = root;
}
/** @return whether we have a next smallest number */
public boolean hasNext() {
return root != null;
}
/** @return the next smallest number */
public int next() {
node = root;
parent = root;
while (node.left != null) {
parent = node;
node = node.left;
}
if (node != root) {
parent.left = node.right;
} else {
root = node.right;
}
node.right = null;
return node.val;
}
}
/**
* Your BSTIterator will be called like this:
* BSTIterator i = new BSTIterator(root);
* while (i.hasNext()) v[f()] = i.next();
*/
```
## Analysis
上面代码中`next()`操作的时间复杂度实际上不是题干要求的，不过这样写比在构造函数初始化时将tree转换成queue效率要高。
使用queue的代码：
```java
/**
* Definition for binary tree
* public class TreeNode {
* int val;
* TreeNode left;
* TreeNode right;
* TreeNode(int x) { val = x; }
* }
*/
public class BSTIterator {
LinkedList<Integer> it = new LinkedList<>();
public BSTIterator(TreeNode root) {
TreeNode node = root;
TreeNode parent = root;
while (node != null) {
while (node.left != null) {
parent = node;
node = node.left;
}
if (node != root) {
parent.left = node.right;
} else {
root = node.right;
}
node.right = null;
it.add(node.val);
node = root;
parent = root;
}
}
/** @return whether we have a next smallest number */
public boolean hasNext() {
return !it.isEmpty();
}
/** @return the next smallest number */
public int next() {
return it.remove();
}
}
/**
* Your BSTIterator will be called like this:
* BSTIterator i = new BSTIterator(root);
* while (i.hasNext()) v[f()] = i.next();
*/
```
上面代码的 runtime 是7 ms。
| 1.0 | Leetcode-173: Binary Search Tree Iterator -
## Description
Implement an iterator over a binary search tree (BST). Your iterator will be initialized with the root node of a BST.
Calling `next()` will return the next smallest number in the BST.
Note: `next()` and `hasNext()` should run in average  time and uses  memory, where h is the height of the tree.
## My Solution
代码的run time是5ms (95.39%)。
```java
/**
* Definition for binary tree
* public class TreeNode {
* int val;
* TreeNode left;
* TreeNode right;
* TreeNode(int x) { val = x; }
* }
*/
public class BSTIterator {
private TreeNode root = null;
private TreeNode parent = null;
private TreeNode node = null;
public BSTIterator(TreeNode root) {
this.root = root;
}
/** @return whether we have a next smallest number */
public boolean hasNext() {
return root != null;
}
/** @return the next smallest number */
public int next() {
node = root;
parent = root;
while (node.left != null) {
parent = node;
node = node.left;
}
if (node != root) {
parent.left = node.right;
} else {
root = node.right;
}
node.right = null;
return node.val;
}
}
/**
* Your BSTIterator will be called like this:
* BSTIterator i = new BSTIterator(root);
* while (i.hasNext()) v[f()] = i.next();
*/
```
## Analysis
上面代码中`next()`操作的时间复杂度实际上不是题干要求的，不过这样写比在构造函数初始化时将tree转换成queue效率要高。
使用queue的代码：
```java
/**
* Definition for binary tree
* public class TreeNode {
* int val;
* TreeNode left;
* TreeNode right;
* TreeNode(int x) { val = x; }
* }
*/
public class BSTIterator {
LinkedList<Integer> it = new LinkedList<>();
public BSTIterator(TreeNode root) {
TreeNode node = root;
TreeNode parent = root;
while (node != null) {
while (node.left != null) {
parent = node;
node = node.left;
}
if (node != root) {
parent.left = node.right;
} else {
root = node.right;
}
node.right = null;
it.add(node.val);
node = root;
parent = root;
}
}
/** @return whether we have a next smallest number */
public boolean hasNext() {
return !it.isEmpty();
}
/** @return the next smallest number */
public int next() {
return it.remove();
}
}
/**
* Your BSTIterator will be called like this:
* BSTIterator i = new BSTIterator(root);
* while (i.hasNext()) v[f()] = i.next();
*/
```
上面代码的 runtime 是7 ms。
| non_main | leetcode binary search tree iterator description implement an iterator over a binary search tree bst your iterator will be initialized with the root node of a bst calling next will return the next smallest number in the bst note next and hasnext should run in average time and uses memory where h is the height of the tree my solution 代码的run 。 java definition for binary tree public class treenode int val treenode left treenode right treenode int x val x public class bstiterator private treenode root null private treenode parent null private treenode node null public bstiterator treenode root this root root return whether we have a next smallest number public boolean hasnext return root null return the next smallest number public int next node root parent root while node left null parent node node node left if node root parent left node right else root node right node right null return node val your bstiterator will be called like this bstiterator i new bstiterator root while i hasnext v i next analysis 上面代码中 next 操作的时间复杂度实际上不是题干要求的 使用queue的代码： java definition for binary tree public class treenode int val treenode left treenode right treenode int x val x public class bstiterator linkedlist it new linkedlist public bstiterator treenode root treenode node root treenode parent root while node null while node left null parent node node node left if node root parent left node right else root node right node right null it add node val node root parent root return whether we have a next smallest number public boolean hasnext return it isempty return the next smallest number public int next return it remove your bstiterator will be called like this bstiterator i new bstiterator root while i hasnext v i next 上面代码的 runtime ms。 | 0 |
13,289 | 8,409,345,260 | IssuesEvent | 2018-10-12 06:57:40 | virtual-labs/problem-solving-iiith | https://api.github.com/repos/virtual-labs/problem-solving-iiith | closed | QA_Problem-Solving_Procedure_Sequences_Spelling-Mistake | Category :Usability Developed by:IIIT Hyd Open-edx-Issue Severity :S3 Status :Closed | Defect Description :
While testing this lab, found spelling mistakes in the Procedure page of Sequences experiment.
Actual Result :
While testing this lab, found spelling mistakes in the Procedure page of Sequences experiment. Please refer to the screen shot provided in attachments.
Environment :
OS: Windows 7, Ubuntu-16.04, Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM,
Processor:i5
Attachments:.
| True | QA_Problem-Solving_Procedure_Sequences_Spelling-Mistake - Defect Description :
While testing this lab, found spelling mistakes in the Procedure page of Sequences experiment.
Actual Result :
While testing this lab, found spelling mistakes in the Procedure page of Sequences experiment. Please refer to the screen shot provided in attachments.
Environment :
OS: Windows 7, Ubuntu-16.04, Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM,
Processor:i5
Attachments:.
| non_main | qa problem solving procedure sequences spelling mistake defect description while testing this lab found spelling mistakes in the procedure page of sequences experiment actual result while testing this lab found spelling mistakes in the procedure page of sequences experiment please refer to the screen shot provided in attachments environment os windows ubuntu centos browsers firefox chrome chromium bandwidth hardware configuration processor attachments | 0 |
2,042 | 6,892,498,623 | IssuesEvent | 2017-11-22 21:20:22 | acl2/acl2 | https://api.github.com/repos/acl2/acl2 | closed | books/centaur/quicklisp/clean.sh dependence on git foils release | Maintainability | There are git commands in books/centaur/quicklisp/clean.sh,
but the ACL2 release process involves a snapshot that avoids
the .git directory. Jared suggested that I create this Issue, for
him to address at his leisure (if at all) -- I can easily work around
this at release time, simply by temporarily commenting out the
git-related parts of that file (which Jared suggests is probably
good enough).
| True | books/centaur/quicklisp/clean.sh dependence on git foils release - There are git commands in books/centaur/quicklisp/clean.sh,
but the ACL2 release process involves a snapshot that avoids
the .git directory. Jared suggested that I create this Issue, for
him to address at his leisure (if at all) -- I can easily work around
this at release time, simply by temporarily commenting out the
git-related parts of that file (which Jared suggests is probably
good enough).
| main | books centaur quicklisp clean sh dependence on git foils release there are git commands in books centaur quicklisp clean sh but the release process involves a snapshot that avoids the git directory jared suggested that i create this issue for him to address at his leisure if at all i can easily work around this at release time simply by temporarily commenting out the git related parts of that file which jared suggests is probably good enough | 1 |
214,438 | 16,589,210,469 | IssuesEvent | 2021-06-01 04:59:50 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | System.CodeDom.Tests nullref on arm64 | area-VM-coreclr blocking-clean-ci bug disabled-test in pr | Started this morning. See https://runfo.azurewebsites.net/search/tests/?q=started%3A%7E7+definition%3Aruntime+name%3ASystem.CodeDom.Tests.CodeAttributeArgumentCollectionTests
<!-- runfo report start -->
Runfo Tracking Issue: [system.codedom.tests.codeattributeargumentcollectiontests](https://runfo.azurewebsites.net/tracking/issue/127)
|Build|Definition|Kind|Run Name|Console|Core Dump|Test Results|Run Client|
|---|---|---|---|---|---|---|---|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
Displaying 100 of 248 results
Build Result Summary
|Day Hit Count|Week Hit Count|Month Hit Count|
|---|---|---|
|7|59|62|
<!-- runfo report end -->
| 1.0 | System.CodeDom.Tests nullref on arm64 - Started this morning. See https://runfo.azurewebsites.net/search/tests/?q=started%3A%7E7+definition%3Aruntime+name%3ASystem.CodeDom.Tests.CodeAttributeArgumentCollectionTests
<!-- runfo report start -->
Runfo Tracking Issue: [system.codedom.tests.codeattributeargumentcollectiontests](https://runfo.azurewebsites.net/tracking/issue/127)
|Build|Definition|Kind|Run Name|Console|Core Dump|Test Results|Run Client|
|---|---|---|---|---|---|---|---|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159218](https://dev.azure.com/dnceng/public/_build/results?buildId=1159218)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/console.cccdcbb3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-373664ed49424878be/System.CodeDom.Tests/5aa311c0-9329-47aa-a61d-ea096009486d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T09%25253A41%25253A45Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dpqs6Ui7xnoBRUqF0agwzp9uQEH5z4S6UcOhZA5Sy9MQ%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1159065](https://dev.azure.com/dnceng/public/_build/results?buildId=1159065)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/console.7508b1a2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0f9b6874549547c081/System.CodeDom.Tests/f7aa33b6-7826-4f21-b4c0-700a683b5e32.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T06%25253A57%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DhTBKdaAhwd%25252B7ubZg1a9mVzAgrRlR0tHLZSco51FxsVc%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158923](https://dev.azure.com/dnceng/public/_build/results?buildId=1158923)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/console.1a5d542a.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c839ababc63e43a39e/System.CodeDom.Tests/407d7d08-d0e1-4640-848c-446448308c86.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T04%25253A51%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DbgLCmlreIOvADsvJQ52zHxHonOWyk4%25252FovTvqa0R2pIo%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158808](https://dev.azure.com/dnceng/public/_build/results?buildId=1158808)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/console.4d0f0871.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b7ed77ea914b50a8/System.CodeDom.Tests/7eca74e5-ebb1-4172-b6b0-6a01cc318063.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T02%25253A34%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dckn40Vu9LE1BoanguqbQ6hS%25252BSmHGRuhhwcetVErnHZs%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158600](https://dev.azure.com/dnceng/public/_build/results?buildId=1158600)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/console.aa88b3a8.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0b7d925ac77445d18d/System.CodeDom.Tests/673e1e48-4aeb-4889-8a9a-bed2bf8c2687.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-16T00%25253A21%25253A12Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DQpvCcikU%25252BanGZO2RhRqPE0SfFQ4H%25252BwJvVIqBqgyVXXg%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158368](https://dev.azure.com/dnceng/public/_build/results?buildId=1158368)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/console.af2b4ffd.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0843c8e231894c329b/System.CodeDom.Tests/440d46aa-6af0-4a4a-924b-55f3e9dc1c44.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T21%25253A59%25253A31Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D133tj2RC%25252ByT1JMurEMmL%25252Bp52CPVEUbe60U%25252B1%25252FuFpN4E%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1158131](https://dev.azure.com/dnceng/public/_build/results?buildId=1158131)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/console.cfcd67b3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-0fdb82ed05ff4a2aae/System.CodeDom.Tests/5a810a8b-d503-44b0-bb9a-25ef2a9b029d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T19%25253A34%25253A49Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dg7jCkfI06nJIcsWG4xoQTsyXzhUmQFk4D4dapY4fkAU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157757](https://dev.azure.com/dnceng/public/_build/results?buildId=1157757)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/console.f91c07ed.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3e55d98049774066a2/System.CodeDom.Tests/4b9f6496-1841-420b-a3de-a5501b6893c6.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T17%25253A17%25253A19Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DY01xDCB0W0uNxHEAaWeg5g6enoasdOsyJW4nj2h3YqU%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157471](https://dev.azure.com/dnceng/public/_build/results?buildId=1157471)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/console.70bd2dcc.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-65a037ec562545ccb3/System.CodeDom.Tests/03446360-4a7a-429b-802c-fd08254c687b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T14%25253A38%25253A50Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DWNqVu2Imi6xJo8xhmarRYELsJSCrg2i64yTdXaLWUfs%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157140](https://dev.azure.com/dnceng/public/_build/results?buildId=1157140)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/console.07c6dc69.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d3a782ff23444e9685/System.CodeDom.Tests/0b760cfc-a5ad-4f41-844d-526387670741.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T11%25253A40%25253A51Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DkW1cUC5FT5NEyrPxj%25252B0wFtOpmYSP35WNx2NZKG0y%25252Bts%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1157013](https://dev.azure.com/dnceng/public/_build/results?buildId=1157013)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/console.79da2366.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-88b8a71eb02445fd97/System.CodeDom.Tests/37f516f8-fedd-4eaf-8334-efa81ca17a53.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T09%25253A35%25253A57Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DElpapufhvSMgvISxmXvA%25252F2x46OFQ3QkJQPzzANIu1O4%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156910](https://dev.azure.com/dnceng/public/_build/results?buildId=1156910)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/console.acb22ad3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-96861e12a7304856b9/System.CodeDom.Tests/e2df5bc5-d895-4fed-ac7f-221880bc6fd5.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T07%25253A43%25253A36Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D%25252FPlW5J4Y0mzkgcMsJuCclTBBBZ0jB5ALJRNYzFCdLDQ%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156852](https://dev.azure.com/dnceng/public/_build/results?buildId=1156852)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/console.9f378f2d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ecea5836169340988d/System.CodeDom.Tests/0adfe719-c347-41b0-8105-513192a76a70.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T05%25253A44%25253A42Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DHDjjblfklkHthGNE653HTTCCnBFmZB3Qit2PNRK48cE%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156761](https://dev.azure.com/dnceng/public/_build/results?buildId=1156761)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/console.b3192142.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-81faca8431814d4faf/System.CodeDom.Tests/a847f29e-b1b9-4eab-bc3a-81cbed455809.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T03%25253A49%25253A47Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D4mI%25252B%25252BBcgx844mr5GZPIF68vP1wys7%25252BQnTBd3Plre13o%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156559](https://dev.azure.com/dnceng/public/_build/results?buildId=1156559)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/console.5ddc191b.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-14fc15e9e86047e0b0/System.CodeDom.Tests/3dd473af-05d0-41c4-b799-15f78ba8881e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-15T01%25253A35%25253A22Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVXs66FRsnqvo%25252B5YvRmI%25252F1L7Q5ZLpapVVjNaBLsdviIA%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1156287](https://dev.azure.com/dnceng/public/_build/results?buildId=1156287)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/console.b1c52119.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-01b24c4aa4ad4c1f89/System.CodeDom.Tests/4b405ead-43be-4cd2-917e-5af21a2a2fc0.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T23%25253A06%25253A17Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DC2jOUWFbKNHP90ZCL2YLJRV%25252FWxwWxP7ZSO%25252FqmHenXLM%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155922](https://dev.azure.com/dnceng/public/_build/results?buildId=1155922)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/console.6cbd6406.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-ddd89d7edad24cb1ae/System.CodeDom.Tests/215cd861-1925-42b0-927b-7d8455681c4f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T20%25253A42%25253A55Z%2526sr%253Dc%2526sp%253Drl%2526sig%253Dj4f0Iq%25252B%25252FxhN8Y%25252BFXrOJF9wl%25252F9bvjQ4gTTbNy8w%25252BF31c%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155610](https://dev.azure.com/dnceng/public/_build/results?buildId=1155610)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/console.84071999.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-387b4b8e22b34fef8c/System.CodeDom.Tests/165b934a-02a3-41f1-a427-4988a470cb43.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T18%25253A22%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253D9rdMN36QAtIx4jnjYbMGfeNCAb5uaGFM0PPQjJXeUBI%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155291](https://dev.azure.com/dnceng/public/_build/results?buildId=1155291)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/console.54fadc10.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-4afce42010d54239b4/System.CodeDom.Tests/0bb7c0d5-b4c1-4cf7-8bac-f2a18c13c033.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T16%25253A13%25253A14Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DyviKeDpzCrUlwghNpWD1pI%25252B60CJfaFTvuYBqUTUK4jE%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1155076](https://dev.azure.com/dnceng/public/_build/results?buildId=1155076)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/console.9e9d7b9e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-46c1e49b710b44e186/System.CodeDom.Tests/05cce5c5-de87-43dc-9dd4-ed88f14d7726.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T14%25253A03%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DypslP1g%25252BIauX8HWKAq2vdSb6pZypQZJq%25252B43G5XB8g58%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154833](https://dev.azure.com/dnceng/public/_build/results?buildId=1154833)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/console.c26c5cda.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-02f1b585e4b1494dbc/System.CodeDom.Tests/009176c1-6c9a-46ec-8c5e-4a62c5bb4d20.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T11%25253A35%25253A53Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DVSJK8Dr3LODoB7OFHdMmbsPx1QAcSB1et8MWkp%25252BFNBY%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154745](https://dev.azure.com/dnceng/public/_build/results?buildId=1154745)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/console.42f1bd4e.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-d8147d79707a49ad99/System.CodeDom.Tests/d0d4aef6-59ce-45b2-a047-9022fa3c276c.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T09%25253A27%25253A30Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DpIl3w8t2RBDqqjHrz%25252FwE1NnJ8X9ekuB7RTYO2vo%25252BA9I%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154637](https://dev.azure.com/dnceng/public/_build/results?buildId=1154637)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/console.94e1e6a3.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-c35ad00a40394a92a4/System.CodeDom.Tests/c310efc7-d68b-4123-9a7c-baf45e5b1502.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T06%25253A31%25253A05Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DLq6R4EqWiOaiBN5rpr%25252FzaJ7YucxpXLNlwLHfANV2ksU%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154469](https://dev.azure.com/dnceng/public/_build/results?buildId=1154469)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/console.b7bb5f80.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-fcba14bf1d4847b491/System.CodeDom.Tests/0a3c804b-00c1-4e5d-8904-8e3571a8452f.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T03%25253A16%25253A25Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DfKE4s7ES7AvyITHx1LyH2syaSsWM%25252F76erdDK0tgiKZc%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
|[1154298](https://dev.azure.com/dnceng/public/_build/results?buildId=1154298)|[runtime](https://dnceng.visualstudio.com/public/_build?definitionId=686)|Rolling|net6.0-windows-Release-arm64-CoreCLR_release-Windows.10.Arm64.Open|[console.log](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/console.3ff5f6f2.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|||[runclient.py](https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-a1f67101c3e34fc9ac/System.CodeDom.Tests/f550f191-5ea6-4434-b7e9-4a16de5fc32d.log?%3F%253Fsv%253D2019-07-07%2526se%253D2021-06-14T01%25253A02%25253A09Z%2526sr%253Dc%2526sp%253Drl%2526sig%253DaUR5Xx1G7uVFSh4%25252FR9oxJro%25252FMiBSQE%25252Bg1WUyIWm1PXY%25253D)|
Displaying 100 of 248 results
Build Result Summary
|Day Hit Count|Week Hit Count|Month Hit Count|
|---|---|---|
|7|59|62|
<!-- runfo report end -->
| non_main | system codedom tests nullref on started this morning see runfo tracking issue build definition kind run name console core dump test results run client displaying of results build result summary day hit count week hit count month hit count | 0 |
213,782 | 7,260,253,956 | IssuesEvent | 2018-02-18 07:08:54 | pombase/website | https://api.github.com/repos/pombase/website | closed | annotation counts sometimes missing | bug display high priority needs checking next |
I screen-shotted this and stupidly forgot to record which gene.
However, I found another one
https://www.pombase.org/gene/SPBC215.02
(here the nucleus total is missing)
| 1.0 | annotation counts sometimes missing -
I screen-shotted this and stupidly forgot to record which gene.
However, I found another one
https://www.pombase.org/gene/SPBC215.02
(here the nucleus total is missing)
| non_main | annotation counts sometimes missing i screen shotted this and stupidly forgot to record which gene however i found another one here the nucleus total is missing | 0 |
425,193 | 12,337,015,988 | IssuesEvent | 2020-05-14 14:24:37 | jwcorle/425_FinalProject | https://api.github.com/repos/jwcorle/425_FinalProject | closed | Interactable weapon pickups | enhancement high priority | Objectives:
- Interacting with the environment (Raycast while pressing 'E' ?)
- Make prefabs for each weapon so it can be interacted with (purchased)
- This also will mean weapons will need a "value" to go with them
Uses:
- These prefabs will be on walls and/or in our version of "The Box"
- User can hold (2?) guns, so they need to be able to purchase and swap out weapons | 1.0 | Interactable weapon pickups - Objectives:
- Interacting with the environment (Raycast while pressing 'E' ?)
- Make prefabs for each weapon so it can be interacted with (purchased)
- This also will mean weapons will need a "value" to go with them
Uses:
- These prefabs will be on walls and/or in our version of "The Box"
- User can hold (2?) guns, so they need to be able to purchase and swap out weapons | non_main | interactable weapon pickups objectives interacting with the environment raycast while pressing e make prefabs for each weapon so it can be interacted with purchased this also will mean weapons will need a value to go with them uses these prefabs will be on walls and or in our version of the box user can hold guns so they need to be able to purchase and swap out weapons | 0 |
251,570 | 18,955,003,675 | IssuesEvent | 2021-11-18 19:09:50 | yalelibrary/YUL-DC | https://api.github.com/repos/yalelibrary/YUL-DC | closed | Document process for adding new parameter for Docker/ECS | documentation dev-ops | **Description**
This task is from knowledge transfer discussion.
We would like to document the process for adding a new parameter to the parameter store and making it available to the containers.
**Acceptance**
- [x] Create a wiki page in the Camerata repo
- [x] Write a general explanation of the process
- [x] Make a checklist of steps required | 1.0 | Document process for adding new parameter for Docker/ECS - **Description**
This task is from knowledge transfer discussion.
We would like to document the process for adding a new parameter to the parameter store and making it available to the containers.
**Acceptance**
- [x] Create a wiki page in the Camerata repo
- [x] Write a general explanation of the process
- [x] Make a checklist of steps required | non_main | document process for adding new parameter for docker ecs description this task is from knowledge transfer discussion we would like to document the process for adding a new parameter to the parameter store and making it available to the containers acceptance create a wiki page in the camerata repo write a general explanation of the process make a checklist of steps required | 0 |
2,320 | 8,305,357,425 | IssuesEvent | 2018-09-22 05:16:00 | tgstation/tgstation-server | https://api.github.com/repos/tgstation/tgstation-server | closed | Test and Debug Instance Automatic Update Feature | Maintainability Issue Review | TODO
- [ ] Make sure it works
- [ ] Patch any issues | True | Test and Debug Instance Automatic Update Feature - TODO
- [ ] Make sure it works
- [ ] Patch any issues | main | test and debug instance automatic update feature todo make sure it works patch any issues | 1 |
43,992 | 23,452,588,606 | IssuesEvent | 2022-08-16 05:26:29 | modin-project/modin | https://api.github.com/repos/modin-project/modin | closed | Improve performance of "mean" groupby aggregation | Performance 🚀 | **Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. What kind of performance improvements would you like to see with this new API?
Currently "mean" aggregation uses `_apply_agg_function` which later calls `broadcast_apply_full_axis`. Its performance on NYC Taxi benchmark is worse than of a single threaded Pandas "mean" implementation. Instead a man-reduce approach could be used to better parallelize the calculations. | True | Improve performance of "mean" groupby aggregation - **Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. What kind of performance improvements would you like to see with this new API?
Currently "mean" aggregation uses `_apply_agg_function` which later calls `broadcast_apply_full_axis`. Its performance on NYC Taxi benchmark is worse than of a single threaded Pandas "mean" implementation. Instead a man-reduce approach could be used to better parallelize the calculations. | non_main | improve performance of mean groupby aggregation is your feature request related to a problem please describe a clear and concise description of what the problem is what kind of performance improvements would you like to see with this new api currently mean aggregation uses apply agg function which later calls broadcast apply full axis its performance on nyc taxi benchmark is worse than of a single threaded pandas mean implementation instead a man reduce approach could be used to better parallelize the calculations | 0 |
90,345 | 18,109,988,344 | IssuesEvent | 2021-09-23 01:36:48 | phetsims/fourier-making-waves | https://api.github.com/repos/phetsims/fourier-making-waves | closed | Code review | dev:code-review priority:2-high | # PhET Code-Review Checklist (a.k.a "CRC")
* The responsible dev is responsible for removing the irrelevant parts
* A checked-off item doesn't mean "no problem here", it means "it was reviewed"
* Problems can be noted in side issues that reference this issue, or through `// REVIEW` comments in the code
## GitHub Issues
The following standard GitHub issues should exist. _If these issues are missing, or have not been completed, pause code review until the issues have been created and addressed by the responsible dev._
- [x] results of memory testing for `brands=phet`, see #130
- [x] performance testing and sign-off, see #131
- [x] review of pointer areas, see #124
- [x] credits (will not be completed until after RC testing), see #2
## **Build and Run Checks**
If any of these items fail, pause code review.
- [x] Does the sim build without warnings or errors?
- [x] Does the html file size seem reasonable, compared to other similar sims?
- [x] Does the sim start up? (unbuilt and built versions)
- [x] Does the sim experience any assertion failures? (run with query parameter `ea`)
- [x] Does the sim pass a scenery fuzz test? (run with query parameters `fuzz&ea`)
- [x] Does the sim behave correctly when listener order is shuffled? (run with query parameters `ea&shuffleListeners` and `ea&shuffleListeners&fuzz`)
- [x] Does the sim output any deprecation warnings? Run with `?deprecationWarnings`. Do not use deprecated methods in new code. _See https://github.com/phetsims/vegas/issues/95, vegas.RewardNode uses deprecated Node.toImage.`_
## **Memory Leaks**
- [x] Does a heap comparison using Chrome Developer Tools indicate a memory leak? (Describing this process is beyond the scope of this document.) Test on a version built using `grunt --minify.mangle=false`. Compare to testing results done by the responsible developer. Results can be found in #130.
- [x] For each common-code component (sun, scenery-phet, vegas, …) that opaquely registers observers or listeners, is there a call to that component’s `dispose` function, or is it obvious why it isn't necessary, or is there documentation about why `dispose` isn't called? An example of why no call to `dispose` is needed is if the component is used in a `ScreenView` that would never be removed from the scene graph.
- [x] Are there leaks due to registering observers or listeners? The following guidelines should be followed unless documentation (in-line or in implementation-notes.md) describes why following them is not necessary.
* AXON: `Property.link` or `lazyLink` is accompanied by `unlink`.
* AXON: `Property.multilink` is accompanied by `unmultilink`.
* AXON: Creation of `Multilink` is accompanied by `dispose`.
* AXON: Creation of `DerivedProperty` is accompanied by `dispose`.
* AXON: `Emitter.addListener` is accompanied by `removeListener`.
* AXON: `ObservableArrayDef.element*Emitter.addListener` is accompanied by `ObservableArrayDef.element*Emitter.removeListener`
* SCENERY: `Node.addInputListener` is accompanied by `removeInputListener`
* TANDEM: Creation of an instrumented `PhetioObject` is accompanied by `dispose`.
- [x] Do all types that require a `dispose` function have one? This should expose a public `dispose` function that calls `this.disposeMyType()`, where `disposeMyType` is a private function declared in the constructor. `MyType` should exactly match the filename.
## **Performance**
- [x] Play with sim, identify any obvious performance issues. Examples: animation that slows down with large numbers of objects; animation that pauses or "hitches" during garbage collection.
- [x] N/A If the sim uses WebGL, does it have a fallback? Does the fallback perform reasonably well? (run with query parameter `webgl=false`)
## **Usability**
- [x] Are UI components sufficiently responsive? (especially continuous UI components, such as sliders)
- [x] Are pointer areas optimized, especially for touch? (run with query parameter `showPointerAreas`)
- [x] Do pointer areas overlap? (run with query parameter `showPointerAreas`) Overlap may be OK in some cases, depending on the z-ordering (if the front-most object is supposed to occlude pointer areas) and whether objects can be moved.
## **Internationalization**
- [x] Are there any strings that are not internationalized, and does the sim layout gracefully handle internationalized strings that are shorter than the English strings? (run with query parameter `stringTest=X`. You should see nothing but 'X' strings.)
- [x] Does the sim layout gracefully handle internationalized strings that are longer than the English strings? (run with query parameters `stringTest=double` and `stringTest=long`)
- [x] Does the sim stay on the sim page (doesn't redirect to an external page) when running with the query parameter `stringTest=xss`? This test passes if sim does not redirect, OK if sim crashes or fails to fully start. Only test on one desktop platform. For PhET-iO sims, additionally test `?stringTest=xss` in Studio to make sure i18n strings didn't leak to phetioDocumentation, see https://github.com/phetsims/phet-io/issues/1377
- [x] Avoid using concatenation to create strings that will be visible in the user interface. Use `StringUtils.fillIn` and a string pattern to ensure that strings are properly localized.
- [x] Use named placeholders (e.g. `"{{value}} {{units}}"`) instead of numbered placeholders (e.g. `"{0} {1}"`).
- [x] Make sure the string keys are all perfect, because they are difficult to change after 1.0.0 is published. Guidelines for string keys are:
(1) Strings keys should generally match their values. E.g.:
```js
"helloWorld": {
value: "Hello World!"
},
"quadraticTerms": {
value: "Quadratic Terms"
}
```
(2) If a string key would be exceptionally long, use a key name that is an abbreviated form of the string value, or that captures the purpose/essence of the value. E.g.:
```js
// key is abbreviated
"iWentToTheStore": {
value: "I went to the store to get milk, eggs, butter, and sugar."
},
// key is based on purpose
"describeTheScreen": {
value: "The Play Area is a small room. The Control Panel has buttons, a checkbox, and radio buttons to change conditions in the room."
}
```
(3) If string key names would collide, use your judgment to disambiguate. E.g.:
```js
"simplifyTitle": {
value: "Simplify!"
},
"simplifyCheckbox": {
value: "simplify"
}
```
(4) String keys for screen names should have the general form `"screen.{{screenName}}"`. E.g.:
```js
"screen.explore": {
"value": "Explore"
},
```
(5) String patterns that contain placeholders (e.g. `"My name is {{first}} {{last}}"`) should use keys that are unlikely to conflict with strings that might be needed in the future. For example, for `"{{price}}"` consider using key `"pricePattern"` instead of `"price"`, if you think there might be a future need for a `"price"` string.
(6) It is acceptable to prefix families of strings with a prefix, like so:
```json
"material.water": {
"value": "Water"
},
"material.wood": {
"value": "Wood"
},
"shape.block": {
"value": "Block"
},
"shape.cone": {
"value": "Cone"
},
```
Nested substructure is not yet fully supported.
- [x] N/A If the sim was already released, make sure none of the original string keys have changed. If they have changed, make sure any changes have a good reason and have been discussed with @jbphet (it is likely that an issue like https://github.com/phetsims/gravity-force-lab/issues/166 should be created).
## **Repository Structure**
- [x] The repository name should correspond to the sim title. For example, if the sim title is "Wave Interference", then the repository name should be "wave-interference".
- [x] Are all required files and directories present?
For a sim repository named “my-repo”, the general structure should look like this (where assets/, images/, mipmaps/ or sounds/ may be omitted if the sim doesn’t have those types of resource files).
```
my-repo/
assets/
doc/
images/
*see annotation
model.md
implementation-notes.md
images/
license.json
js/
(see section below)
mipmaps/
license.json
sound/
license.json
dependencies.json
.gitignore
my-repo_en.html
my-repo-strings_en.json
Gruntfile.js
LICENSE
package.json
README.md
```
*Any images used in model.md or implementation-notes.md should be added here. Images specific to aiding with documentation do not need their own license.
- [x] Verify that the same image file is not present in both images/ and mipmaps/. If you need a mipmap, use it for all occurrences of the image.
- [x] Is the js/ directory properly structured?
All JavaScript source should be in the js/ directory. There should be a subdirectory for each screen (this also applies for single-screen sims, where the subdirectory matches the repo name). For a multi-screen sim, code shared by 2 or more screens should be in a js/common/ subdirectory. Model and view code should be in model/ and view/ subdirectories for each screen and common/. For example, for a sim with screens “Introduction” and “Lab”, the general directory structure should look like this:
```
my-repo/
js/
common/
model/
view/
introduction/
model/
view/
lab/
model/
view/
my-repo-main.js
myRepo.js
myRepoStrings.js
```
- [x] Do filenames use an appropriate prefix? Some filenames may be prefixed with the repository name, e.g. `MolarityConstants.js` in molarity. If the repository name is long, the developer may choose to abbreviate the repository name, e.g. `EEConstants.js` in expression-exchange. If the abbreviation is already used by another respository, then the full name must be used. For example, if the "EE" abbreviation is already used by expression-exchange, then it should not be used in equality-explorer. Whichever convention is used, it should be used consistently within a repository - don't mix abbreviations and full names.
- [x] Is there a file in assets/ for every resource file in sound/ and images/? Note that there is *not necessarily* a 1:1 correspondence between asset and resource files; for example, several related images may be in the same .ai file. Check license.json for possible documentation of why some reesources might not have a corresponding asset file.
- [x] Was the README.md generated by `grunt published-README` or `grunt unpublished-README`?
- [x] Does package.json refer to any dependencies that are not used by the sim?
- [x] Is the LICENSE file correct? (Generally GPL v3 for sims and MIT for common code, see [this thread](https://github.com/phetsims/tasks/issues/875#issuecomment-312168646) for additional information).
- [x] Does .gitignore match the one in simula-rasa?
- [x] In GitHub, verify that all non-release branches have an associated issue that describes their purpose.
- [x] Are there any GitHub branches that are no longer needed and should be deleted?
- [x] Does `model.md` adequately describe the model, in terms appropriate for teachers? https://github.com/phetsims/fourier-making-waves/issues/126
- [x] Does `implementation-notes.md` adequately describe the implementation, with an overview that will be useful to future maintainers? **CODE REVIEWER: Please review implementation-notes and wrap up https://github.com/phetsims/fourier-making-waves/issues/127.**
- [x] Sim-specific query parameters (if any) should be identified and documented in one .js file in js/common/ or js/ (if there is no common/). The .js file should be named `{{PREFIX}}QueryParameters.js`, for example ArithmeticQueryParameters.js for the aritmetic repository, or FBQueryParameters.js for Function Builder (where the `FB` prefix is used).
- [x] Query parameters that are public-facing should be identified using `public: true` in the schema.
- [x] All sims should use a color file named `MyRepoColors.js` or, if using abbreviations, `MRColors.js`, and use `ProfileColorProperty` where appropriate, even if they have a single (default) profile (to support color editing and PhET-iO Studio). The `ColorProfile` pattern was converted to `*Colors.js` files in https://github.com/phetsims/scenery-phet/issues/515. Please see [GasPropertiesColors.js](https://github.com/phetsims/gas -properties/blob/master/js/common/GasPropertiesColors.js) for a good example.
## **Coding Conventions**
This section deals with PhET coding conventions. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
- [x] Is the code formatted according to PhET conventions? See [phet-idea-code-style.xml](https://github.com/phetsims/phet-info/blob/master/ide/idea/phet-idea-codestyle.xml) for IntelliJ IDEA code style.
- [x] Names (types, variables, properties, Properties, functions,...) should be sufficiently descriptive and specific, and should avoid non-standard abbreviations. For example:
```js
const numPart = 100; // incorrect
const numberOfParticles = 100; // correct
const width = 150; // incorrect
const beakerWidth = 150; // correct
```
- [x] Verify that [Best Practices for Modules](https://github.com/phetsims/phet-info/blob/master/doc/best-practices-for-modules.md) are followed.
- [x] For constructors, use parameters for things that don’t have a default. Use options for things that have a default value. This improves readability at the call site, especially when the number of parameters is large. It also eliminates order dependency that is required by using parameters.
For example, this constructor uses parameters for everything. At the call site, the semantics of the arguments are difficult to determine without consulting the constructor.
```js
class BallNode extends Node {
/**
* @param {Ball} ball - model element
* @param {Property.<boolean>} visibleProperty - is the ball visible?
* @param {Color|string} fill - fill color
* @param {Color|string} stroke - stroke color
* @param {number} lineWidth - width of the stroke
*/
constructor( ball, visibleProperty, fill, stroke, lineWidth ){
// ...
}
}
// Call site
const ballNode = new BallNode( ball, visibleProperty, 'blue', 'black', 2 );
```
Here’s the same constructor with an appropriate use of options. The call site is easier to read, and the order of options is flexible.
```js
class BallNode extends Node {
/**
* @param {Ball} ball - model element
* @param {Property.<boolean>} visibleProperty - is the ball visible?
* @param {Object} [options]
*/
constructor( ball, visibleProperty, options ) {
options = merge( {
fill: 'white', // {Color|string} fill color
stroke: 'black', // {Color|string} stroke color
lineWidth: 1 // {number} width of the stroke
}, options );
// ...
}
}
// Call site
const ballNode = new BallNode( ball, visibleProperty, {
fill: 'blue',
stroke: 'black',
lineWidth: 2
} );
```
- [x] When options are passed through one constructor to another, a "nested options" pattern should be used. This helps to avoid duplicating option names and/or accidentally overwriting options for different components that use the same option names. Make sure to use PHET_CORE/merge instead of `_.extend` or `_.merge`. `merge` will automatically recurse to keys named `*Options` and extend those as well.
Example:
```js
class ParticleBoxNode extends Node {
/**
* @param {ParticleBox} particleBox - model element
* @param {Property.<boolean>} visibleProperty - are the box and its contents visible?
* @param {Object} [options]
*/
constructor( particleBox, visibleProperty, options ) {
options = merge( {
fill: 'white', // {Color|string} fill color
stroke: 'black', // {Color|string} stroke color
lineWidth: 1, // {number} width of the stroke
particleNodeOptions: {
fill: 'red',
stroke: 'gray',
lineWidth: 0.5
},
}, options );
// add particle
this.addChild( new ParticleNode( particleBox.particle, options.particleNodeOptions ) );
...
}
}
```
A possible exception to this guideline is when the constructor API is improved by hiding the implementation details, i.e. not revealing that a sub-component exists. In that case, it may make sense to use new top-level options. This is left to developer and reviewer discretion.
For more information on the history and thought process around the "nested options" pattern, please see https://github.com/phetsims/tasks/issues/730.
- [x] N/A If references are needed to the enclosing object, such as for a closure, `self` should be defined, but it should only be used in closures. The `self` variable should not be defined unless it is needed in a closure. Example:
```js
const self = this;
someProperty.link( function(){
self.doSomething();
} );
this.doSomethingElse();
```
- [x] Generally, lines should not exceed 120 columns. Break up long statements, expressions, or comments into multiple lines to optimize readability. It is OK for require statements or other structured patterns to exceed 120 columns. Use your judgment!
- [x] Functions should be invoked using the dot operator rather than the bracket operator. For more details, please see https://github.com/phetsims/gravity-and-orbits/issues/9. For example:
```js
// avoid
this[ isFaceSmile ? 'smile' : 'frown' ]();
// OK
isFaceSmile ? this.smile() : this.frown();
// OK
if ( isFaceSmile ) {
this.smile();
}
else {
this.frown();
}
```
- [x] It is not uncommon to use conditional shorthand and short circuiting for invocation. Use parentheses to maximize readability.
```js
( expression ) && statement;
( expression ) ? statement1 : statement2;
( foo && bar ) ? fooBar() : fooCat();
( foo && bar ) && fooBar();
( foo && !(bar && fooBar)) && nowIAmConfused();
this.fill = ( foo && bar ) ? 'red' : 'blue';
```
If the expression is only one item, the parentheses can be omitted. This is the most common use case.
```js
assert && assert( happy, 'Why aren\'t you happy?' );
happy && smile();
const thoughts = happy ? 'I am happy' : 'I am not happy :(';
```
- [x] Naming for Property values: All `AXON/Property` instances should be declared with the suffix `Property`. For example, if a visible property is added, it should have the name `visibleProperty` instead of simply `visible`. This will help to avoid confusion with non-Property definitions. Identify violations by searching for regular expression "= new .*Property".
- [x] Properties should use type-specific subclasses where appropriate (e.g. BooleanProperty, NumberProperty, StringProperty) or provide documentation as to why they are not.
- [x] Are `Validator` validation options (`valueType`, `validValues`, etc...) utilized? These are supported in a number of core types like `Emitter` and `Property`. Is their presence or lack thereof properly documented?
- [x] Files should be named like `CapitalizedCamelCasing.js` when returning a constructor, or `lowerCaseCamelCasing.js` when returning a non-constructor function or singleton. When returning a constructor or singleton, the constructor name should match the filename. Where singletons are treated like classes with static attributes (like SimulaRasaConstants or SimulaRasaColors), uppercase should be used.
- [x] Assertions should be used appropriately and consistently. Type checking should not just be done in code comments. Use `Array.isArray` to type check an array.
- [x] If you need to namespace an inner class, use `{{namespace}}.register`, and include a comment about why the inner class needs to be namespaced. Use the form `'{{outerClassname}}.{{innerClassname}}'` for the key. For example:
```js
import myNamespace from '...';
class SlotMachineNode extends Node {
constructor( ... ) {
this.leverNode = new LeverNode(...);
...
}
...
}
myNamespace.register( 'SlotMachineNode', SlotMachineNode );
class LeverNode extends Node {
...
}
// It was useful to be able to instantiate this in the console for testing, and we may need to do so in the future.
myNamespace.register( 'SlotMachineNode.LeverNode', LeverNode );
return SlotMachineNode;
```
- [x] Putting unused parameters in callbacks is up to developer discretion, as long they are correct wrt to the actual callback signature.
For example, both of these are acceptable:
```js
Property.multilink(
[ styleProperty, activeProperty, colorProperty ],
( style, active, color ) => {
// some algorithm that uses style and active
} );
Property.multilink(
[ styleProperty, activeProperty, colorProperty ],
( style, active ) => {
// some algorithm that uses style and active
} );
```
This is not acceptable, because the 3rd parameter is incorrect.
```js
Property.multilink(
[ styleProperty, activeProperty, colorProperty ],
( style, active, lineWidth ) => {
// some algorithm that uses style and active
} );
```
- [x] ES5 getters/setters defined in sims should be used judiciously when a Property exists, only when the benefit of conciseness outweighs the potential loss of readability. If ES5 getters/setters exist, try to not mix usage of them with Property access.
- [x] The model and view code should be written such that it makes no assumptions about the animation frame rate this it will encounter. The default max dt (delta time) value is defined in `Screen.js`, and smaller values should be used if the default is too large. There is no minimum value for dt, which implies that there is no maximum supported frame
rate. The sim should be able to handle this. For an example of a problem that resulted from assuming that a max rate of 60 FPS would be the norm, please see [this GitHub issue](https://github.com/phetsims/states-of-matter/issues/354).
### Documentation
This section deals with PhET documentation conventions. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
- [x] All classes, methods and properties are documented.
- [x] Documentation at the top of .js files should provide an overview of purpose, responsibilies, and (where useful) examples of API use. If the file contains a subclass definition, it should indicate what functionality it adds to the superclass.
- [x] The HTML5/CSS3/JavaScript source code must be reasonably well documented. This is difficult to specify precisely, but the idea is that someone who is moderately experienced with HTML5/CSS3/JavaScript can quickly understand the general function of the source code as well as the overall flow of the code by reading through the comments. For an example of the type of documentation that is required, please see the example-sim repository.
- [x] Differentiate between `Property` and "property" in comments. They are different things. `Property` is a type in AXON; property is any value associated with a JavaScript object. Often "field" can be used in exchange for "property" which can help with clarity. Search for "property" to identify violations.
- [x] N/A Classes that mix in traits or mixin should use the `@mixes MyType` annotation.
- [x] Line comments should generally be preceded by a blank line. For example:
```js
// Randomly choose an existing crystal to possibly bond to
const crystal = this.crystals.get( _.random( this.crystals.length - 1 ) );
// Find a good configuration to have the particles move toward
const targetConfiguration = this.getTargetConfiguration( crystal );
```
- [x] When documenting conditionals (if/else statements), follow these guidlines:
1. Comments above the first `if` in a conditional should be about the entire conditional, not just the if block.
2. Comments should not break up sections of the conditional.
3. If a comment is needed to describe a single block of the conditional, then add that comment just inside the block (no space between the `if`/`else if`/`else` and the comment), with a space below it as to not be confused with a comment about logic below.
```js
// Comment about the reason to split on peppers were pickled.
if( peterPiperPickedAJarOfPickledPeppers ){
// if we want to explain what this `if` statement is about
peterAlsoHasBrine();
}
else {
// documentation about why we have no peppers. This is about the next line of code, and not the "else as a whole block."
peterHasNoPeppers();
}
```
- [x] Line comments should have whitespace between the `//` and the first letter of the line comment. See the preceding example.
- [x] Do the `@author` annotations seem correct?
- [x] Constructor and function documentation. Parameter types and names should be clearly specified for each constructor and function using `@param` annotations. The description for each parameter should follow a hyphen. Primitive types should use lower case. For example:
```js
/**
* The PhetDeveloper is responsible for creating code for simulations and documenting their code thoroughly.
*/
class PhetDeveloper {
/**
* @param {string} name - full name
* @param {number} age - age, in years
* @param {boolean} isEmployee - whether this developer is an employee of CU
* @param {function} callback - called immediate after coffee is consumed
* @param {Property.<number>} hoursProperty - cumulative hours worked
* @param {string[]} friendNames - names of friends
* @param {Object} [options]
*/
constructor( name, age, isEmployee, callback, hoursProperty, friendNames, options ) {
...
}
...
}
```
- [x] For most functions, the same form as above should be used, with a `@returns` annotation which identifies the return type and the meaning of the returned value. Functions should also document any side effects. For extremely simple functions that are just a few lines of simple code, an abbreviated line-comment can be used, for example: `// Computes {Number} distance based on {Foo} foo.`
- [x] Abstract methods should be annotated with `@abstract` and should typically throw an Error. For example:
```js
/**
* Updates this node.
* @abstract
* @protected
*/
update() {
throw new Error( 'update must be implemented by subclass' );
}
```
#### Type Expressions
This section deals with PhET conventions for type expressions. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
- [x] Type expressions should conform approximately to [Google Closure Compiler](https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler) syntax. PhET stretches the syntax in many cases (beyond the scope of this document to describe).
- [x] Prefer the most basic/restrictive type expression when defining APIs. For example, if a client only needs to know that a parameter is `{Node}`, don’t describe the parameter as `{Rectangle}`.
- [x] All method parameters should have type expressions. For example `@param {number} width`.
- [x] In sim-specific code, options and fields should have type expressions when their type is not obvious from the context. “Obvious” typically means that the value type is clearly shown in the righthand-side of the definition. E.g. `const width = 42` clear shows that `width` is `{number}`. E.g. `const checkbox = new Checkbox(…)` clearly shows that `checkbox` is `{Checkbox}`. If the type is obvious from the context, the developer may still provide a type expression at his/her discretion. Examples:
```js
// @public {GameState} the current state of the game
this.gameState = this.computeGameState();
// @public (read-only) the width of the container
this.containerWidth = 150;
// @private the checkbox used to show particles
this.particlesVisibleCheckbox = new Checkbox(...);
```
- [x] In common code repositories all options and fields should have type expressions, regardless of their visibility, and regardless whether their type is obvious from the context. If the same examples from above appeared in common code:
```js
// @public {GameState} the current state of the game
this.gameState = this.computeGameState();
// @public (read-only) {number} the width of the container
this.containerWidth = 150;
// @private {Checkbox} the checkbox used to show particles
this.particlesVisibleCheckbox = new Checkbox(...);
```
- [x] Type expressions for Enumeration values should be annotated as instances of that Enumeration, see examples in https://github.com/phetsims/phet-core/blob/master/js/Enumeration.js for more.
```js
/**
* @param {LeftOrRight} - whichHand
*/
function getHand( whichHand ){
if( whichHand === LeftOrRight.LEFT ){
return new LeftHand();
}
else if( whichHand === LeftOrRight.RIGHT ){
return new RightHand();
}
}
```
- [x] Type expressions for functions have a variety of possibilities, increasing in complexity depending on the case. In general note that `{function}` is not enough information. Here are some better options:
1. The most basic option it to use Google Closure Type syntax, for more info see https://github.com/google/closure-compiler/wiki/Types-in-the-Closure-Type-System. This specifies the param/return types, but nothing more. Here are some examples:
* `@param {function()} noParamsAndNoReturnValue`
* `@param {function(number)} giveMeNumberAndReturnNothing`
* `@param {function(number, number):Vector2} getVector2`
* `@param {function(new:Node)} createNode - a function that takes the Node constructor`
2. When needing to be a bit more specific, add a name to parameters of the function. Sometimes this is all that is needed for clarity on what the param does:
* `@param {function(model:MyModel, length:number, name:string): Node} getLengthNode`
* `@param {function(aSelfExplanatoryNameForAString:string): Node} getStringNode`
3. If (2) isn't enough, use English to explain the parameters and return values. This is easy because they are named, and can be easily mentioned:
* `@param {function(model:MyModel, length:number, name:string): Node} getLengthNode - returns the length Node that you have always wanted, name is the name of the source of your aspirations, length is a special number according to the following 24 criteria. . .`
4. If needing more complexity, or using jsdoc rendering tools (like PhET-iO documentation does), you must use a JSDoc compatible format, not (2) or (3), and you may need to use the more complicated solution. See JSDoc docs for more info. Here is an example of a named callback:
```js
/**
* @name mySpecialCallback
* Converts a string to a number
* @param {string}
* @returns {number}
*/
/**
* @param {mySpecialCallback} callback
*/
x = function( callback) { callback( 'still chocolate' ) };
```
- [x] Type expressions for anonymous Objects have a variety of possibilities, increasing in complexity depending on the case.
1. When the documentation is close by, then {Object} is still acceptable. This mainly applies to options and similar patterns:
* `@param {Object} [options] // this is great because of the extend call 5 lines down`
2. When using an `Object` with specific properties, name them and their types like so:
* `@param {name:string, address:{street:string}, returnNode:function(number):Node, [shoeSize:number]} personalData // note that shoeSize is optional here`
3. When you need a bit more explanation, keep the same type expression as (2), but feel free to outline specifics in English after the param name.
```
@ param {name:string, address:{street:string}, returnNode:function(number):Node, [shoeSize:number]} personalData - use english after to explain pieces of this
(if needed, outline properties on their own lines)
name is something
address is something else
returnNode does this thing
```
4. Not all objects have named keys like (2) and (3). Here is how to document dictionary-like `Object`s, where each key is some type, and the value is another type. For key value pairs use this:
* `{Object.<string, number>}` Where keys are strings, and values are numbers.
* `{Object.<phetioID:string, count:number>}` - naming each of these can help identify them too. Feel free to explain in English after the type expression if needed.
5. If things are too complicated for the above cases, use a `*Def.js` file (especially is used in more than one file), or a `@typedef` declaration right above the jsdoc that uses the typedef.
- [x] Look for cases where the use of type expressions involving Property subclasses are incorrect. Because of the structure of the `Property` class hierarchy, specifying type-specific Properties (`{BooleanProperty}`, `{NumberProperty}`,...) may be incorrect, because it precludes values of type `{DerivedProperty}` and `{DynamicProperty}`. Similarly, use of `{DerivedProperty}` and `{DynamicProperty}` precludes values of (e.g.) `{BooleanProperty}`. Especially in common code, using `{Property.<TYPE>}` is typically correct, unless some specific feature of the `Property` subclass is required. For example, `{Property.<boolean>}` instead of `{BooleanProperty}`.
#### Visibility Annotations
This section deals with PhET conventions for visibility annotations. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
Because JavaScript lacks visibility modifiers (public, protected, private), PhET uses JSdoc visibility annotations to document the intent of the programmer, and define the public API. Visibility annotations are required for anything that JavaScript makes public. Information about these annotations can be found here. (Note that other documentation systems like the Google Closure Compiler use slightly different syntax in some cases. Where there are differences, JSDoc is authoritative. For example, use `Array.<Object>` or `Object[]` instead of `Array<Object>`). PhET guidelines for visibility annotations are as follows:
- [x] Use `@public` for anything that is intended to be part of the public API.
- [x] Use `@protected` for anything that is intended for use by subtypes.
- [x] Use `@private` for anything that is NOT intended to be part of the public or protected API.
- [x] Put qualifiers in parenthesis after the annotation, for example:
* To qualify that something is read-only, use `@public (read-only)`. This indicates that the given Property (AND its value) should not be changed by outside code (e.g. a Property should not have its value changed)
* To qualify that something is public to a specific repository, use (for example) `@public (scenery-internal)`
* For something made public solely for a11y, use `@public (a11y)`
* For something made public solely for phet-io, use `@public (phet-io)`
* Separate multiple qualifiers with commas. For example: `@public (scenery-internal, read-only)`
- [x] For JSDoc-style comments, the annotation should appear in context like this:
```js
/**
* Creates the icon for the "Energy" screen, a cartoonish bar graph.
* @returns {Node}
* @public
*/
```
- [x] For Line comments, the annotation can appear like this:
```js
// @public {function(listener:function)} - Adds a listener
addListener: function( listener ) { /*...*/ }
```
- [x] Verify that every JavaScript property and function has a visibility annotation. Here are some helpful regular expressions to search for these declarations as PhET uses them.
* Regex for property assignment like `x.y = something`: `[\w]+\.[\w]+\s=`
* Regex for function declarations: `[\w]+: function\(`
## **Math Libraries**
- [x] `DOT/Utils.toFixed` or `DOT/Utils.toFixedNumber` should be used instead of `toFixed`. JavaScript's `toFixed` is notoriously buggy. Behavior differs depending on browser, because the spec doesn't specify whether to round or floor.
## IE11
- [x] IE is no longer supported. With that in mind remove IE-specific workarounds
- [x] Use `string.includes` and `string.startsWith` where possible.
## **Organization, Readability, and Maintainability**
- [x] Does the organization and structure of the code make sense? Do the model and view contain types that you would expect (or guess!) by looking at the sim? Do the names of things correspond to the names that you see in the user interface?
- [x] Are appropriate design patterns used? See [phet-software-design-patterns.md](https://github.com/phetsims/phet-info/blob/master/doc/phet-software-design-patterns.md). If new or inappropriate patterns are identified, create an issue.
- [x] Is inheritance used where appropriate? Does the type hierarchy make sense?
- [x] Is composition favored over inheritance where appropriate? See https://en.wikipedia.org/wiki/Composition_over_inheritance.
- [x] Is there any unnecessary coupling? (e.g., by passing large objects to constructors, or exposing unnecessary properties/functions)
- [x] Is there too much unnecessary decoupling? (e.g. by passing all of the properties of an object independently instead of passing the object itself)?
- [x] Are the source files reasonable in size? Scrutinize large files with too many responsibilities - can responsibilities be broken into smaller delegates?
- [x] Are any significant chunks of code duplicated? This will be checked manually as well as with https://github.com/danielstjules/jsinspect.
- [x] Is there anything that should be generalized and migrated to common code?
- [x] Are there any `TODO` or `FIXME` or `REVIEW` comments in the code? They should be addressed or promoted to GitHub issues.
- [x] Are there any [magic numbers](https://en.wikipedia.org/wiki/Magic_number_(programming)) that should be factored out as constants and documented?
- [x] Are there any constants that are duplicated in multiple files that should be factored out into a `{{REPO}}Constants.js` file?
- [x] Does the implementation rely on any specific constant values that are likely to change in the future? Identify constants that might be changed in the future. (Use your judgement about which constants are likely candidates.) Does changing the values of these constants break the sim? For example, see https://github.com/phetsims/plinko-probability/issues/84.
- [x] Is [PhetColorScheme](https://github.com/phetsims/scenery-phet/blob/master/js/PhetColorScheme.js) used where appropriate? Verify that the sim is not inventing/creating its own colors for things that have been standardized in `PhetColorScheme`. Identify any colors that might be worth adding to `PhetColorScheme`.
- [x] Are all dependent Properties modeled as `DerivedProperty` instead of `Property`?
- [x] All dynamics should be called from Sim.step(dt), do not use window.setTimeout or window.setInterval. This will help support Legends of Learning and PhET-iO.
## **Accessibility**
This section may be omitted if the sim has not been instrumented with accessibility features. Accessibility includes various features, not all are always include. Ignore sections that do not apply.
### General
- [x] Are accessibility features integrated well into the code. They should be added in a maintainable way, even if that requires upfront refactoring. _See the [A11y section of implementation-notes.md](https://github.com/phetsims/fourier-making-waves/blob/master/doc/implementation-notes.md#a11y)._
### Alternative Input
- [x] Does the sim pass an accessibility fuzz test? (run with query parameters `fuzzBoard&ea`)
- [x] Does this sim use specific keyboard shortcuts that overlap with global shortcuts? _See https://github.com/phetsims/fourier-making-waves/issues/93_
### Interactive Description
N/A
## **PhET-iO**
This section may be omitted if the sim has not been instrumented for PhET-iO, but is likely good to glance at no matter.
- [x] Does instrumentation follow the conventions described in [PhET-iO Instrumentation Guide](https://github.com/phetsims/phet-io/blob/master/doc/phet-io-instrumentation-technical-guide.md)? This could be an extensive bullet. At the very least, be sure to know what amount of instrumentation this sim supports. Describing this further goes beyond the scope of this document.
- [x] N/A PhET-iO instantiates different objects and wires up listeners that are not present in the PhET-branded simulation. It needs to be tested separately for memory leaks. To help isolate the nature of the memory leak, this test should be run separately from the PhET brand memory leak test. Test with a colorized Data Stream, and Studio (easily accessed from phetmarks). Compare to testing results done by the responsible developer and previous releases.
- [x] N/A Make sure unused `PhetioObject` instances are disposed, which unregisters their tandems.
- [x] Make sure JOIST `dt` values are used instead of `Date.now()` or other Date functions. Perhaps try `phet.joist.elapsedTime`. Though this has already been mentioned, it is necessary for reproducible playback via input events and deserves a comment in this PhET-iO section.
- [x] Are random numbers using `DOT/dotRandom` as an imported module (not a global), and all doing so after modules are declared (non-statically)? For example, the following methods (and perhaps others) should not be used: `Math.random`, `_.shuffle`, `_.sample`, `_.random`.
This also deserves re-iteration due to its effect on record/playback for PhET-iO.
- [x] Like JSON, keys for `undefined` values are omitted when serializing objects across frames. Consider this when determining whether `toStateObject` should use `null` or `undefined` values.
- [x] PhET prefers to use the term "position" to refer to the physical (x,y) position of objects. This applies to both brands, but is more important for the PhET-iO API. See https://github.com/phetsims/phet-info/issues/126
- [x] Are your IOType state methods violating the API of the core type by accessing private fields?
- [x] When defining a boolean Property to indicate whether something is enabled, use `AXON/EnabledProperty`. This should be done in both the model and the view.
| 1.0 | Code review - # PhET Code-Review Checklist (a.k.a "CRC")
* The responsible dev is responsible for removing the irrelevant parts
* A checked-off item doesn't mean "no problem here", it means "it was reviewed"
* Problems can be noted in side issues that reference this issue, or through `// REVIEW` comments in the code
## GitHub Issues
The following standard GitHub issues should exist. _If these issues are missing, or have not been completed, pause code review until the issues have been created and addressed by the responsible dev._
- [x] results of memory testing for `brands=phet`, see #130
- [x] performance testing and sign-off, see #131
- [x] review of pointer areas, see #124
- [x] credits (will not be completed until after RC testing), see #2
## **Build and Run Checks**
If any of these items fail, pause code review.
- [x] Does the sim build without warnings or errors?
- [x] Does the html file size seem reasonable, compared to other similar sims?
- [x] Does the sim start up? (unbuilt and built versions)
- [x] Does the sim experience any assertion failures? (run with query parameter `ea`)
- [x] Does the sim pass a scenery fuzz test? (run with query parameters `fuzz&ea`)
- [x] Does the sim behave correctly when listener order is shuffled? (run with query parameters `ea&shuffleListeners` and `ea&shuffleListeners&fuzz`)
- [x] Does the sim output any deprecation warnings? Run with `?deprecationWarnings`. Do not use deprecated methods in new code. _See https://github.com/phetsims/vegas/issues/95, vegas.RewardNode uses deprecated Node.toImage.`_
## **Memory Leaks**
- [x] Does a heap comparison using Chrome Developer Tools indicate a memory leak? (Describing this process is beyond the scope of this document.) Test on a version built using `grunt --minify.mangle=false`. Compare to testing results done by the responsible developer. Results can be found in #130.
- [x] For each common-code component (sun, scenery-phet, vegas, …) that opaquely registers observers or listeners, is there a call to that component’s `dispose` function, or is it obvious why it isn't necessary, or is there documentation about why `dispose` isn't called? An example of why no call to `dispose` is needed is if the component is used in a `ScreenView` that would never be removed from the scene graph.
- [x] Are there leaks due to registering observers or listeners? The following guidelines should be followed unless documentation (in-line or in implementation-notes.md) describes why following them is not necessary.
* AXON: `Property.link` or `lazyLink` is accompanied by `unlink`.
* AXON: `Property.multilink` is accompanied by `unmultilink`.
* AXON: Creation of `Multilink` is accompanied by `dispose`.
* AXON: Creation of `DerivedProperty` is accompanied by `dispose`.
* AXON: `Emitter.addListener` is accompanied by `removeListener`.
* AXON: `ObservableArrayDef.element*Emitter.addListener` is accompanied by `ObservableArrayDef.element*Emitter.removeListener`
* SCENERY: `Node.addInputListener` is accompanied by `removeInputListener`
* TANDEM: Creation of an instrumented `PhetioObject` is accompanied by `dispose`.
- [x] Do all types that require a `dispose` function have one? This should expose a public `dispose` function that calls `this.disposeMyType()`, where `disposeMyType` is a private function declared in the constructor. `MyType` should exactly match the filename.
## **Performance**
- [x] Play with sim, identify any obvious performance issues. Examples: animation that slows down with large numbers of objects; animation that pauses or "hitches" during garbage collection.
- [x] N/A If the sim uses WebGL, does it have a fallback? Does the fallback perform reasonably well? (run with query parameter `webgl=false`)
## **Usability**
- [x] Are UI components sufficiently responsive? (especially continuous UI components, such as sliders)
- [x] Are pointer areas optimized, especially for touch? (run with query parameter `showPointerAreas`)
- [x] Do pointer areas overlap? (run with query parameter `showPointerAreas`) Overlap may be OK in some cases, depending on the z-ordering (if the front-most object is supposed to occlude pointer areas) and whether objects can be moved.
## **Internationalization**
- [x] Are there any strings that are not internationalized, and does the sim layout gracefully handle internationalized strings that are shorter than the English strings? (run with query parameter `stringTest=X`. You should see nothing but 'X' strings.)
- [x] Does the sim layout gracefully handle internationalized strings that are longer than the English strings? (run with query parameters `stringTest=double` and `stringTest=long`)
- [x] Does the sim stay on the sim page (doesn't redirect to an external page) when running with the query parameter `stringTest=xss`? This test passes if sim does not redirect, OK if sim crashes or fails to fully start. Only test on one desktop platform. For PhET-iO sims, additionally test `?stringTest=xss` in Studio to make sure i18n strings didn't leak to phetioDocumentation, see https://github.com/phetsims/phet-io/issues/1377
- [x] Avoid using concatenation to create strings that will be visible in the user interface. Use `StringUtils.fillIn` and a string pattern to ensure that strings are properly localized.
- [x] Use named placeholders (e.g. `"{{value}} {{units}}"`) instead of numbered placeholders (e.g. `"{0} {1}"`).
- [x] Make sure the string keys are all perfect, because they are difficult to change after 1.0.0 is published. Guidelines for string keys are:
(1) Strings keys should generally match their values. E.g.:
```js
"helloWorld": {
value: "Hello World!"
},
"quadraticTerms": {
value: "Quadratic Terms"
}
```
(2) If a string key would be exceptionally long, use a key name that is an abbreviated form of the string value, or that captures the purpose/essence of the value. E.g.:
```js
// key is abbreviated
"iWentToTheStore": {
value: "I went to the store to get milk, eggs, butter, and sugar."
},
// key is based on purpose
"describeTheScreen": {
value: "The Play Area is a small room. The Control Panel has buttons, a checkbox, and radio buttons to change conditions in the room."
}
```
(3) If string key names would collide, use your judgment to disambiguate. E.g.:
```js
"simplifyTitle": {
value: "Simplify!"
},
"simplifyCheckbox": {
value: "simplify"
}
```
(4) String keys for screen names should have the general form `"screen.{{screenName}}"`. E.g.:
```js
"screen.explore": {
"value": "Explore"
},
```
(5) String patterns that contain placeholders (e.g. `"My name is {{first}} {{last}}"`) should use keys that are unlikely to conflict with strings that might be needed in the future. For example, for `"{{price}}"` consider using key `"pricePattern"` instead of `"price"`, if you think there might be a future need for a `"price"` string.
(6) It is acceptable to prefix families of strings with a prefix, like so:
```json
"material.water": {
"value": "Water"
},
"material.wood": {
"value": "Wood"
},
"shape.block": {
"value": "Block"
},
"shape.cone": {
"value": "Cone"
},
```
Nested substructure is not yet fully supported.
- [x] N/A If the sim was already released, make sure none of the original string keys have changed. If they have changed, make sure any changes have a good reason and have been discussed with @jbphet (it is likely that an issue like https://github.com/phetsims/gravity-force-lab/issues/166 should be created).
## **Repository Structure**
- [x] The repository name should correspond to the sim title. For example, if the sim title is "Wave Interference", then the repository name should be "wave-interference".
- [x] Are all required files and directories present?
For a sim repository named “my-repo”, the general structure should look like this (where assets/, images/, mipmaps/ or sounds/ may be omitted if the sim doesn’t have those types of resource files).
```
my-repo/
assets/
doc/
images/
*see annotation
model.md
implementation-notes.md
images/
license.json
js/
(see section below)
mipmaps/
license.json
sound/
license.json
dependencies.json
.gitignore
my-repo_en.html
my-repo-strings_en.json
Gruntfile.js
LICENSE
package.json
README.md
```
*Any images used in model.md or implementation-notes.md should be added here. Images specific to aiding with documentation do not need their own license.
- [x] Verify that the same image file is not present in both images/ and mipmaps/. If you need a mipmap, use it for all occurrences of the image.
- [x] Is the js/ directory properly structured?
All JavaScript source should be in the js/ directory. There should be a subdirectory for each screen (this also applies for single-screen sims, where the subdirectory matches the repo name). For a multi-screen sim, code shared by 2 or more screens should be in a js/common/ subdirectory. Model and view code should be in model/ and view/ subdirectories for each screen and common/. For example, for a sim with screens “Introduction” and “Lab”, the general directory structure should look like this:
```
my-repo/
js/
common/
model/
view/
introduction/
model/
view/
lab/
model/
view/
my-repo-main.js
myRepo.js
myRepoStrings.js
```
- [x] Do filenames use an appropriate prefix? Some filenames may be prefixed with the repository name, e.g. `MolarityConstants.js` in molarity. If the repository name is long, the developer may choose to abbreviate the repository name, e.g. `EEConstants.js` in expression-exchange. If the abbreviation is already used by another respository, then the full name must be used. For example, if the "EE" abbreviation is already used by expression-exchange, then it should not be used in equality-explorer. Whichever convention is used, it should be used consistently within a repository - don't mix abbreviations and full names.
- [x] Is there a file in assets/ for every resource file in sound/ and images/? Note that there is *not necessarily* a 1:1 correspondence between asset and resource files; for example, several related images may be in the same .ai file. Check license.json for possible documentation of why some reesources might not have a corresponding asset file.
- [x] Was the README.md generated by `grunt published-README` or `grunt unpublished-README`?
- [x] Does package.json refer to any dependencies that are not used by the sim?
- [x] Is the LICENSE file correct? (Generally GPL v3 for sims and MIT for common code, see [this thread](https://github.com/phetsims/tasks/issues/875#issuecomment-312168646) for additional information).
- [x] Does .gitignore match the one in simula-rasa?
- [x] In GitHub, verify that all non-release branches have an associated issue that describes their purpose.
- [x] Are there any GitHub branches that are no longer needed and should be deleted?
- [x] Does `model.md` adequately describe the model, in terms appropriate for teachers? https://github.com/phetsims/fourier-making-waves/issues/126
- [x] Does `implementation-notes.md` adequately describe the implementation, with an overview that will be useful to future maintainers? **CODE REVIEWER: Please review implementation-notes and wrap up https://github.com/phetsims/fourier-making-waves/issues/127.**
- [x] Sim-specific query parameters (if any) should be identified and documented in one .js file in js/common/ or js/ (if there is no common/). The .js file should be named `{{PREFIX}}QueryParameters.js`, for example ArithmeticQueryParameters.js for the aritmetic repository, or FBQueryParameters.js for Function Builder (where the `FB` prefix is used).
- [x] Query parameters that are public-facing should be identified using `public: true` in the schema.
- [x] All sims should use a color file named `MyRepoColors.js` or, if using abbreviations, `MRColors.js`, and use `ProfileColorProperty` where appropriate, even if they have a single (default) profile (to support color editing and PhET-iO Studio). The `ColorProfile` pattern was converted to `*Colors.js` files in https://github.com/phetsims/scenery-phet/issues/515. Please see [GasPropertiesColors.js](https://github.com/phetsims/gas -properties/blob/master/js/common/GasPropertiesColors.js) for a good example.
## **Coding Conventions**
This section deals with PhET coding conventions. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
- [x] Is the code formatted according to PhET conventions? See [phet-idea-code-style.xml](https://github.com/phetsims/phet-info/blob/master/ide/idea/phet-idea-codestyle.xml) for IntelliJ IDEA code style.
- [x] Names (types, variables, properties, Properties, functions,...) should be sufficiently descriptive and specific, and should avoid non-standard abbreviations. For example:
```js
const numPart = 100; // incorrect
const numberOfParticles = 100; // correct
const width = 150; // incorrect
const beakerWidth = 150; // correct
```
- [x] Verify that [Best Practices for Modules](https://github.com/phetsims/phet-info/blob/master/doc/best-practices-for-modules.md) are followed.
- [x] For constructors, use parameters for things that don’t have a default. Use options for things that have a default value. This improves readability at the call site, especially when the number of parameters is large. It also eliminates order dependency that is required by using parameters.
For example, this constructor uses parameters for everything. At the call site, the semantics of the arguments are difficult to determine without consulting the constructor.
```js
class BallNode extends Node {
/**
* @param {Ball} ball - model element
* @param {Property.<boolean>} visibleProperty - is the ball visible?
* @param {Color|string} fill - fill color
* @param {Color|string} stroke - stroke color
* @param {number} lineWidth - width of the stroke
*/
constructor( ball, visibleProperty, fill, stroke, lineWidth ){
// ...
}
}
// Call site
const ballNode = new BallNode( ball, visibleProperty, 'blue', 'black', 2 );
```
Here’s the same constructor with an appropriate use of options. The call site is easier to read, and the order of options is flexible.
```js
class BallNode extends Node {
/**
* @param {Ball} ball - model element
* @param {Property.<boolean>} visibleProperty - is the ball visible?
* @param {Object} [options]
*/
constructor( ball, visibleProperty, options ) {
options = merge( {
fill: 'white', // {Color|string} fill color
stroke: 'black', // {Color|string} stroke color
lineWidth: 1 // {number} width of the stroke
}, options );
// ...
}
}
// Call site
const ballNode = new BallNode( ball, visibleProperty, {
fill: 'blue',
stroke: 'black',
lineWidth: 2
} );
```
- [x] When options are passed through one constructor to another, a "nested options" pattern should be used. This helps to avoid duplicating option names and/or accidentally overwriting options for different components that use the same option names. Make sure to use PHET_CORE/merge instead of `_.extend` or `_.merge`. `merge` will automatically recurse to keys named `*Options` and extend those as well.
Example:
```js
class ParticleBoxNode extends Node {
/**
* @param {ParticleBox} particleBox - model element
* @param {Property.<boolean>} visibleProperty - are the box and its contents visible?
* @param {Object} [options]
*/
constructor( particleBox, visibleProperty, options ) {
options = merge( {
fill: 'white', // {Color|string} fill color
stroke: 'black', // {Color|string} stroke color
lineWidth: 1, // {number} width of the stroke
particleNodeOptions: {
fill: 'red',
stroke: 'gray',
lineWidth: 0.5
},
}, options );
// add particle
this.addChild( new ParticleNode( particleBox.particle, options.particleNodeOptions ) );
...
}
}
```
A possible exception to this guideline is when the constructor API is improved by hiding the implementation details, i.e. not revealing that a sub-component exists. In that case, it may make sense to use new top-level options. This is left to developer and reviewer discretion.
For more information on the history and thought process around the "nested options" pattern, please see https://github.com/phetsims/tasks/issues/730.
- [x] N/A If references are needed to the enclosing object, such as for a closure, `self` should be defined, but it should only be used in closures. The `self` variable should not be defined unless it is needed in a closure. Example:
```js
const self = this;
someProperty.link( function(){
self.doSomething();
} );
this.doSomethingElse();
```
- [x] Generally, lines should not exceed 120 columns. Break up long statements, expressions, or comments into multiple lines to optimize readability. It is OK for require statements or other structured patterns to exceed 120 columns. Use your judgment!
- [x] Functions should be invoked using the dot operator rather than the bracket operator. For more details, please see https://github.com/phetsims/gravity-and-orbits/issues/9. For example:
```js
// avoid
this[ isFaceSmile ? 'smile' : 'frown' ]();
// OK
isFaceSmile ? this.smile() : this.frown();
// OK
if ( isFaceSmile ) {
this.smile();
}
else {
this.frown();
}
```
- [x] It is not uncommon to use conditional shorthand and short circuiting for invocation. Use parentheses to maximize readability.
```js
( expression ) && statement;
( expression ) ? statement1 : statement2;
( foo && bar ) ? fooBar() : fooCat();
( foo && bar ) && fooBar();
( foo && !(bar && fooBar)) && nowIAmConfused();
this.fill = ( foo && bar ) ? 'red' : 'blue';
```
If the expression is only one item, the parentheses can be omitted. This is the most common use case.
```js
assert && assert( happy, 'Why aren\'t you happy?' );
happy && smile();
const thoughts = happy ? 'I am happy' : 'I am not happy :(';
```
- [x] Naming for Property values: All `AXON/Property` instances should be declared with the suffix `Property`. For example, if a visible property is added, it should have the name `visibleProperty` instead of simply `visible`. This will help to avoid confusion with non-Property definitions. Identify violations by searching for regular expression "= new .*Property".
- [x] Properties should use type-specific subclasses where appropriate (e.g. BooleanProperty, NumberProperty, StringProperty) or provide documentation as to why they are not.
- [x] Are `Validator` validation options (`valueType`, `validValues`, etc...) utilized? These are supported in a number of core types like `Emitter` and `Property`. Is their presence or lack thereof properly documented?
- [x] Files should be named like `CapitalizedCamelCasing.js` when returning a constructor, or `lowerCaseCamelCasing.js` when returning a non-constructor function or singleton. When returning a constructor or singleton, the constructor name should match the filename. Where singletons are treated like classes with static attributes (like SimulaRasaConstants or SimulaRasaColors), uppercase should be used.
- [x] Assertions should be used appropriately and consistently. Type checking should not just be done in code comments. Use `Array.isArray` to type check an array.
- [x] If you need to namespace an inner class, use `{{namespace}}.register`, and include a comment about why the inner class needs to be namespaced. Use the form `'{{outerClassname}}.{{innerClassname}}'` for the key. For example:
```js
import myNamespace from '...';
class SlotMachineNode extends Node {
constructor( ... ) {
this.leverNode = new LeverNode(...);
...
}
...
}
myNamespace.register( 'SlotMachineNode', SlotMachineNode );
class LeverNode extends Node {
...
}
// It was useful to be able to instantiate this in the console for testing, and we may need to do so in the future.
myNamespace.register( 'SlotMachineNode.LeverNode', LeverNode );
return SlotMachineNode;
```
- [x] Putting unused parameters in callbacks is up to developer discretion, as long they are correct wrt to the actual callback signature.
For example, both of these are acceptable:
```js
Property.multilink(
[ styleProperty, activeProperty, colorProperty ],
( style, active, color ) => {
// some algorithm that uses style and active
} );
Property.multilink(
[ styleProperty, activeProperty, colorProperty ],
( style, active ) => {
// some algorithm that uses style and active
} );
```
This is not acceptable, because the 3rd parameter is incorrect.
```js
Property.multilink(
[ styleProperty, activeProperty, colorProperty ],
( style, active, lineWidth ) => {
// some algorithm that uses style and active
} );
```
- [x] ES5 getters/setters defined in sims should be used judiciously when a Property exists, only when the benefit of conciseness outweighs the potential loss of readability. If ES5 getters/setters exist, try to not mix usage of them with Property access.
- [x] The model and view code should be written such that it makes no assumptions about the animation frame rate this it will encounter. The default max dt (delta time) value is defined in `Screen.js`, and smaller values should be used if the default is too large. There is no minimum value for dt, which implies that there is no maximum supported frame
rate. The sim should be able to handle this. For an example of a problem that resulted from assuming that a max rate of 60 FPS would be the norm, please see [this GitHub issue](https://github.com/phetsims/states-of-matter/issues/354).
### Documentation
This section deals with PhET documentation conventions. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
- [x] All classes, methods and properties are documented.
- [x] Documentation at the top of .js files should provide an overview of purpose, responsibilies, and (where useful) examples of API use. If the file contains a subclass definition, it should indicate what functionality it adds to the superclass.
- [x] The HTML5/CSS3/JavaScript source code must be reasonably well documented. This is difficult to specify precisely, but the idea is that someone who is moderately experienced with HTML5/CSS3/JavaScript can quickly understand the general function of the source code as well as the overall flow of the code by reading through the comments. For an example of the type of documentation that is required, please see the example-sim repository.
- [x] Differentiate between `Property` and "property" in comments. They are different things. `Property` is a type in AXON; property is any value associated with a JavaScript object. Often "field" can be used in exchange for "property" which can help with clarity. Search for "property" to identify violations.
- [x] N/A Classes that mix in traits or mixin should use the `@mixes MyType` annotation.
- [x] Line comments should generally be preceded by a blank line. For example:
```js
// Randomly choose an existing crystal to possibly bond to
const crystal = this.crystals.get( _.random( this.crystals.length - 1 ) );
// Find a good configuration to have the particles move toward
const targetConfiguration = this.getTargetConfiguration( crystal );
```
- [x] When documenting conditionals (if/else statements), follow these guidlines:
1. Comments above the first `if` in a conditional should be about the entire conditional, not just the if block.
2. Comments should not break up sections of the conditional.
3. If a comment is needed to describe a single block of the conditional, then add that comment just inside the block (no space between the `if`/`else if`/`else` and the comment), with a space below it as to not be confused with a comment about logic below.
```js
// Comment about the reason to split on peppers were pickled.
if( peterPiperPickedAJarOfPickledPeppers ){
// if we want to explain what this `if` statement is about
peterAlsoHasBrine();
}
else {
// documentation about why we have no peppers. This is about the next line of code, and not the "else as a whole block."
peterHasNoPeppers();
}
```
- [x] Line comments should have whitespace between the `//` and the first letter of the line comment. See the preceding example.
- [x] Do the `@author` annotations seem correct?
- [x] Constructor and function documentation. Parameter types and names should be clearly specified for each constructor and function using `@param` annotations. The description for each parameter should follow a hyphen. Primitive types should use lower case. For example:
```js
/**
* The PhetDeveloper is responsible for creating code for simulations and documenting their code thoroughly.
*/
class PhetDeveloper {
/**
* @param {string} name - full name
* @param {number} age - age, in years
* @param {boolean} isEmployee - whether this developer is an employee of CU
* @param {function} callback - called immediate after coffee is consumed
* @param {Property.<number>} hoursProperty - cumulative hours worked
* @param {string[]} friendNames - names of friends
* @param {Object} [options]
*/
constructor( name, age, isEmployee, callback, hoursProperty, friendNames, options ) {
...
}
...
}
```
- [x] For most functions, the same form as above should be used, with a `@returns` annotation which identifies the return type and the meaning of the returned value. Functions should also document any side effects. For extremely simple functions that are just a few lines of simple code, an abbreviated line-comment can be used, for example: `// Computes {Number} distance based on {Foo} foo.`
- [x] Abstract methods should be annotated with `@abstract` and should typically throw an Error. For example:
```js
/**
* Updates this node.
* @abstract
* @protected
*/
update() {
throw new Error( 'update must be implemented by subclass' );
}
```
#### Type Expressions
This section deals with PhET conventions for type expressions. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
- [x] Type expressions should conform approximately to [Google Closure Compiler](https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler) syntax. PhET stretches the syntax in many cases (beyond the scope of this document to describe).
- [x] Prefer the most basic/restrictive type expression when defining APIs. For example, if a client only needs to know that a parameter is `{Node}`, don’t describe the parameter as `{Rectangle}`.
- [x] All method parameters should have type expressions. For example `@param {number} width`.
- [x] In sim-specific code, options and fields should have type expressions when their type is not obvious from the context. “Obvious” typically means that the value type is clearly shown in the righthand-side of the definition. E.g. `const width = 42` clear shows that `width` is `{number}`. E.g. `const checkbox = new Checkbox(…)` clearly shows that `checkbox` is `{Checkbox}`. If the type is obvious from the context, the developer may still provide a type expression at his/her discretion. Examples:
```js
// @public {GameState} the current state of the game
this.gameState = this.computeGameState();
// @public (read-only) the width of the container
this.containerWidth = 150;
// @private the checkbox used to show particles
this.particlesVisibleCheckbox = new Checkbox(...);
```
- [x] In common code repositories all options and fields should have type expressions, regardless of their visibility, and regardless whether their type is obvious from the context. If the same examples from above appeared in common code:
```js
// @public {GameState} the current state of the game
this.gameState = this.computeGameState();
// @public (read-only) {number} the width of the container
this.containerWidth = 150;
// @private {Checkbox} the checkbox used to show particles
this.particlesVisibleCheckbox = new Checkbox(...);
```
- [x] Type expressions for Enumeration values should be annotated as instances of that Enumeration, see examples in https://github.com/phetsims/phet-core/blob/master/js/Enumeration.js for more.
```js
/**
* @param {LeftOrRight} - whichHand
*/
function getHand( whichHand ){
if( whichHand === LeftOrRight.LEFT ){
return new LeftHand();
}
else if( whichHand === LeftOrRight.RIGHT ){
return new RightHand();
}
}
```
- [x] Type expressions for functions have a variety of possibilities, increasing in complexity depending on the case. In general note that `{function}` is not enough information. Here are some better options:
1. The most basic option it to use Google Closure Type syntax, for more info see https://github.com/google/closure-compiler/wiki/Types-in-the-Closure-Type-System. This specifies the param/return types, but nothing more. Here are some examples:
* `@param {function()} noParamsAndNoReturnValue`
* `@param {function(number)} giveMeNumberAndReturnNothing`
* `@param {function(number, number):Vector2} getVector2`
* `@param {function(new:Node)} createNode - a function that takes the Node constructor`
2. When needing to be a bit more specific, add a name to parameters of the function. Sometimes this is all that is needed for clarity on what the param does:
* `@param {function(model:MyModel, length:number, name:string): Node} getLengthNode`
* `@param {function(aSelfExplanatoryNameForAString:string): Node} getStringNode`
3. If (2) isn't enough, use English to explain the parameters and return values. This is easy because they are named, and can be easily mentioned:
* `@param {function(model:MyModel, length:number, name:string): Node} getLengthNode - returns the length Node that you have always wanted, name is the name of the source of your aspirations, length is a special number according to the following 24 criteria. . .`
4. If needing more complexity, or using jsdoc rendering tools (like PhET-iO documentation does), you must use a JSDoc compatible format, not (2) or (3), and you may need to use the more complicated solution. See JSDoc docs for more info. Here is an example of a named callback:
```js
/**
* @name mySpecialCallback
* Converts a string to a number
* @param {string}
* @returns {number}
*/
/**
* @param {mySpecialCallback} callback
*/
x = function( callback) { callback( 'still chocolate' ) };
```
- [x] Type expressions for anonymous Objects have a variety of possibilities, increasing in complexity depending on the case.
1. When the documentation is close by, then {Object} is still acceptable. This mainly applies to options and similar patterns:
* `@param {Object} [options] // this is great because of the extend call 5 lines down`
2. When using an `Object` with specific properties, name them and their types like so:
* `@param {name:string, address:{street:string}, returnNode:function(number):Node, [shoeSize:number]} personalData // note that shoeSize is optional here`
3. When you need a bit more explanation, keep the same type expression as (2), but feel free to outline specifics in English after the param name.
```
@ param {name:string, address:{street:string}, returnNode:function(number):Node, [shoeSize:number]} personalData - use english after to explain pieces of this
(if needed, outline properties on their own lines)
name is something
address is something else
returnNode does this thing
```
4. Not all objects have named keys like (2) and (3). Here is how to document dictionary-like `Object`s, where each key is some type, and the value is another type. For key value pairs use this:
* `{Object.<string, number>}` Where keys are strings, and values are numbers.
* `{Object.<phetioID:string, count:number>}` - naming each of these can help identify them too. Feel free to explain in English after the type expression if needed.
5. If things are too complicated for the above cases, use a `*Def.js` file (especially is used in more than one file), or a `@typedef` declaration right above the jsdoc that uses the typedef.
- [x] Look for cases where the use of type expressions involving Property subclasses are incorrect. Because of the structure of the `Property` class hierarchy, specifying type-specific Properties (`{BooleanProperty}`, `{NumberProperty}`,...) may be incorrect, because it precludes values of type `{DerivedProperty}` and `{DynamicProperty}`. Similarly, use of `{DerivedProperty}` and `{DynamicProperty}` precludes values of (e.g.) `{BooleanProperty}`. Especially in common code, using `{Property.<TYPE>}` is typically correct, unless some specific feature of the `Property` subclass is required. For example, `{Property.<boolean>}` instead of `{BooleanProperty}`.
#### Visibility Annotations
This section deals with PhET conventions for visibility annotations. You do not need to exhaustively check every item in this section, nor do you necessarily need to check these items one at a time. The goal is to determine whether the code generally meets PhET standards.
Because JavaScript lacks visibility modifiers (public, protected, private), PhET uses JSdoc visibility annotations to document the intent of the programmer, and define the public API. Visibility annotations are required for anything that JavaScript makes public. Information about these annotations can be found here. (Note that other documentation systems like the Google Closure Compiler use slightly different syntax in some cases. Where there are differences, JSDoc is authoritative. For example, use `Array.<Object>` or `Object[]` instead of `Array<Object>`). PhET guidelines for visibility annotations are as follows:
- [x] Use `@public` for anything that is intended to be part of the public API.
- [x] Use `@protected` for anything that is intended for use by subtypes.
- [x] Use `@private` for anything that is NOT intended to be part of the public or protected API.
- [x] Put qualifiers in parenthesis after the annotation, for example:
* To qualify that something is read-only, use `@public (read-only)`. This indicates that the given Property (AND its value) should not be changed by outside code (e.g. a Property should not have its value changed)
* To qualify that something is public to a specific repository, use (for example) `@public (scenery-internal)`
* For something made public solely for a11y, use `@public (a11y)`
* For something made public solely for phet-io, use `@public (phet-io)`
* Separate multiple qualifiers with commas. For example: `@public (scenery-internal, read-only)`
- [x] For JSDoc-style comments, the annotation should appear in context like this:
```js
/**
* Creates the icon for the "Energy" screen, a cartoonish bar graph.
* @returns {Node}
* @public
*/
```
- [x] For Line comments, the annotation can appear like this:
```js
// @public {function(listener:function)} - Adds a listener
addListener: function( listener ) { /*...*/ }
```
- [x] Verify that every JavaScript property and function has a visibility annotation. Here are some helpful regular expressions to search for these declarations as PhET uses them.
* Regex for property assignment like `x.y = something`: `[\w]+\.[\w]+\s=`
* Regex for function declarations: `[\w]+: function\(`
## **Math Libraries**
- [x] `DOT/Utils.toFixed` or `DOT/Utils.toFixedNumber` should be used instead of `toFixed`. JavaScript's `toFixed` is notoriously buggy. Behavior differs depending on browser, because the spec doesn't specify whether to round or floor.
## IE11
- [x] IE is no longer supported. With that in mind remove IE-specific workarounds
- [x] Use `string.includes` and `string.startsWith` where possible.
## **Organization, Readability, and Maintainability**
- [x] Does the organization and structure of the code make sense? Do the model and view contain types that you would expect (or guess!) by looking at the sim? Do the names of things correspond to the names that you see in the user interface?
- [x] Are appropriate design patterns used? See [phet-software-design-patterns.md](https://github.com/phetsims/phet-info/blob/master/doc/phet-software-design-patterns.md). If new or inappropriate patterns are identified, create an issue.
- [x] Is inheritance used where appropriate? Does the type hierarchy make sense?
- [x] Is composition favored over inheritance where appropriate? See https://en.wikipedia.org/wiki/Composition_over_inheritance.
- [x] Is there any unnecessary coupling? (e.g., by passing large objects to constructors, or exposing unnecessary properties/functions)
- [x] Is there too much unnecessary decoupling? (e.g. by passing all of the properties of an object independently instead of passing the object itself)?
- [x] Are the source files reasonable in size? Scrutinize large files with too many responsibilities - can responsibilities be broken into smaller delegates?
- [x] Are any significant chunks of code duplicated? This will be checked manually as well as with https://github.com/danielstjules/jsinspect.
- [x] Is there anything that should be generalized and migrated to common code?
- [x] Are there any `TODO` or `FIXME` or `REVIEW` comments in the code? They should be addressed or promoted to GitHub issues.
- [x] Are there any [magic numbers](https://en.wikipedia.org/wiki/Magic_number_(programming)) that should be factored out as constants and documented?
- [x] Are there any constants that are duplicated in multiple files that should be factored out into a `{{REPO}}Constants.js` file?
- [x] Does the implementation rely on any specific constant values that are likely to change in the future? Identify constants that might be changed in the future. (Use your judgement about which constants are likely candidates.) Does changing the values of these constants break the sim? For example, see https://github.com/phetsims/plinko-probability/issues/84.
- [x] Is [PhetColorScheme](https://github.com/phetsims/scenery-phet/blob/master/js/PhetColorScheme.js) used where appropriate? Verify that the sim is not inventing/creating its own colors for things that have been standardized in `PhetColorScheme`. Identify any colors that might be worth adding to `PhetColorScheme`.
- [x] Are all dependent Properties modeled as `DerivedProperty` instead of `Property`?
- [x] All dynamics should be called from Sim.step(dt), do not use window.setTimeout or window.setInterval. This will help support Legends of Learning and PhET-iO.
## **Accessibility**
This section may be omitted if the sim has not been instrumented with accessibility features. Accessibility includes various features, not all are always include. Ignore sections that do not apply.
### General
- [x] Are accessibility features integrated well into the code. They should be added in a maintainable way, even if that requires upfront refactoring. _See the [A11y section of implementation-notes.md](https://github.com/phetsims/fourier-making-waves/blob/master/doc/implementation-notes.md#a11y)._
### Alternative Input
- [x] Does the sim pass an accessibility fuzz test? (run with query parameters `fuzzBoard&ea`)
- [x] Does this sim use specific keyboard shortcuts that overlap with global shortcuts? _See https://github.com/phetsims/fourier-making-waves/issues/93_
### Interactive Description
N/A
## **PhET-iO**
This section may be omitted if the sim has not been instrumented for PhET-iO, but is likely good to glance at no matter.
- [x] Does instrumentation follow the conventions described in [PhET-iO Instrumentation Guide](https://github.com/phetsims/phet-io/blob/master/doc/phet-io-instrumentation-technical-guide.md)? This could be an extensive bullet. At the very least, be sure to know what amount of instrumentation this sim supports. Describing this further goes beyond the scope of this document.
- [x] N/A PhET-iO instantiates different objects and wires up listeners that are not present in the PhET-branded simulation. It needs to be tested separately for memory leaks. To help isolate the nature of the memory leak, this test should be run separately from the PhET brand memory leak test. Test with a colorized Data Stream, and Studio (easily accessed from phetmarks). Compare to testing results done by the responsible developer and previous releases.
- [x] N/A Make sure unused `PhetioObject` instances are disposed, which unregisters their tandems.
- [x] Make sure JOIST `dt` values are used instead of `Date.now()` or other Date functions. Perhaps try `phet.joist.elapsedTime`. Though this has already been mentioned, it is necessary for reproducible playback via input events and deserves a comment in this PhET-iO section.
- [x] Are random numbers using `DOT/dotRandom` as an imported module (not a global), and all doing so after modules are declared (non-statically)? For example, the following methods (and perhaps others) should not be used: `Math.random`, `_.shuffle`, `_.sample`, `_.random`.
This also deserves re-iteration due to its effect on record/playback for PhET-iO.
- [x] Like JSON, keys for `undefined` values are omitted when serializing objects across frames. Consider this when determining whether `toStateObject` should use `null` or `undefined` values.
- [x] PhET prefers to use the term "position" to refer to the physical (x,y) position of objects. This applies to both brands, but is more important for the PhET-iO API. See https://github.com/phetsims/phet-info/issues/126
- [x] Are your IOType state methods violating the API of the core type by accessing private fields?
- [x] When defining a boolean Property to indicate whether something is enabled, use `AXON/EnabledProperty`. This should be done in both the model and the view.
| non_main | code review phet code review checklist a k a crc the responsible dev is responsible for removing the irrelevant parts a checked off item doesn t mean no problem here it means it was reviewed problems can be noted in side issues that reference this issue or through review comments in the code github issues the following standard github issues should exist if these issues are missing or have not been completed pause code review until the issues have been created and addressed by the responsible dev results of memory testing for brands phet see performance testing and sign off see review of pointer areas see credits will not be completed until after rc testing see build and run checks if any of these items fail pause code review does the sim build without warnings or errors does the html file size seem reasonable compared to other similar sims does the sim start up unbuilt and built versions does the sim experience any assertion failures run with query parameter ea does the sim pass a scenery fuzz test run with query parameters fuzz ea does the sim behave correctly when listener order is shuffled run with query parameters ea shufflelisteners and ea shufflelisteners fuzz does the sim output any deprecation warnings run with deprecationwarnings do not use deprecated methods in new code see vegas rewardnode uses deprecated node toimage memory leaks does a heap comparison using chrome developer tools indicate a memory leak describing this process is beyond the scope of this document test on a version built using grunt minify mangle false compare to testing results done by the responsible developer results can be found in for each common code component sun scenery phet vegas … that opaquely registers observers or listeners is there a call to that component’s dispose function or is it obvious why it isn t necessary or is there documentation about why dispose isn t called an example of why no call to dispose is needed is if the component is used in a screenview that would never be removed from the scene graph are there leaks due to registering observers or listeners the following guidelines should be followed unless documentation in line or in implementation notes md describes why following them is not necessary axon property link or lazylink is accompanied by unlink axon property multilink is accompanied by unmultilink axon creation of multilink is accompanied by dispose axon creation of derivedproperty is accompanied by dispose axon emitter addlistener is accompanied by removelistener axon observablearraydef element emitter addlistener is accompanied by observablearraydef element emitter removelistener scenery node addinputlistener is accompanied by removeinputlistener tandem creation of an instrumented phetioobject is accompanied by dispose do all types that require a dispose function have one this should expose a public dispose function that calls this disposemytype where disposemytype is a private function declared in the constructor mytype should exactly match the filename performance play with sim identify any obvious performance issues examples animation that slows down with large numbers of objects animation that pauses or hitches during garbage collection n a if the sim uses webgl does it have a fallback does the fallback perform reasonably well run with query parameter webgl false usability are ui components sufficiently responsive especially continuous ui components such as sliders are pointer areas optimized especially for touch run with query parameter showpointerareas do pointer areas overlap run with query parameter showpointerareas overlap may be ok in some cases depending on the z ordering if the front most object is supposed to occlude pointer areas and whether objects can be moved internationalization are there any strings that are not internationalized and does the sim layout gracefully handle internationalized strings that are shorter than the english strings run with query parameter stringtest x you should see nothing but x strings does the sim layout gracefully handle internationalized strings that are longer than the english strings run with query parameters stringtest double and stringtest long does the sim stay on the sim page doesn t redirect to an external page when running with the query parameter stringtest xss this test passes if sim does not redirect ok if sim crashes or fails to fully start only test on one desktop platform for phet io sims additionally test stringtest xss in studio to make sure strings didn t leak to phetiodocumentation see avoid using concatenation to create strings that will be visible in the user interface use stringutils fillin and a string pattern to ensure that strings are properly localized use named placeholders e g value units instead of numbered placeholders e g make sure the string keys are all perfect because they are difficult to change after is published guidelines for string keys are strings keys should generally match their values e g js helloworld value hello world quadraticterms value quadratic terms if a string key would be exceptionally long use a key name that is an abbreviated form of the string value or that captures the purpose essence of the value e g js key is abbreviated iwenttothestore value i went to the store to get milk eggs butter and sugar key is based on purpose describethescreen value the play area is a small room the control panel has buttons a checkbox and radio buttons to change conditions in the room if string key names would collide use your judgment to disambiguate e g js simplifytitle value simplify simplifycheckbox value simplify string keys for screen names should have the general form screen screenname e g js screen explore value explore string patterns that contain placeholders e g my name is first last should use keys that are unlikely to conflict with strings that might be needed in the future for example for price consider using key pricepattern instead of price if you think there might be a future need for a price string it is acceptable to prefix families of strings with a prefix like so json material water value water material wood value wood shape block value block shape cone value cone nested substructure is not yet fully supported n a if the sim was already released make sure none of the original string keys have changed if they have changed make sure any changes have a good reason and have been discussed with jbphet it is likely that an issue like should be created repository structure the repository name should correspond to the sim title for example if the sim title is wave interference then the repository name should be wave interference are all required files and directories present for a sim repository named “my repo” the general structure should look like this where assets images mipmaps or sounds may be omitted if the sim doesn’t have those types of resource files my repo assets doc images see annotation model md implementation notes md images license json js see section below mipmaps license json sound license json dependencies json gitignore my repo en html my repo strings en json gruntfile js license package json readme md any images used in model md or implementation notes md should be added here images specific to aiding with documentation do not need their own license verify that the same image file is not present in both images and mipmaps if you need a mipmap use it for all occurrences of the image is the js directory properly structured all javascript source should be in the js directory there should be a subdirectory for each screen this also applies for single screen sims where the subdirectory matches the repo name for a multi screen sim code shared by or more screens should be in a js common subdirectory model and view code should be in model and view subdirectories for each screen and common for example for a sim with screens “introduction” and “lab” the general directory structure should look like this my repo js common model view introduction model view lab model view my repo main js myrepo js myrepostrings js do filenames use an appropriate prefix some filenames may be prefixed with the repository name e g molarityconstants js in molarity if the repository name is long the developer may choose to abbreviate the repository name e g eeconstants js in expression exchange if the abbreviation is already used by another respository then the full name must be used for example if the ee abbreviation is already used by expression exchange then it should not be used in equality explorer whichever convention is used it should be used consistently within a repository don t mix abbreviations and full names is there a file in assets for every resource file in sound and images note that there is not necessarily a correspondence between asset and resource files for example several related images may be in the same ai file check license json for possible documentation of why some reesources might not have a corresponding asset file was the readme md generated by grunt published readme or grunt unpublished readme does package json refer to any dependencies that are not used by the sim is the license file correct generally gpl for sims and mit for common code see for additional information does gitignore match the one in simula rasa in github verify that all non release branches have an associated issue that describes their purpose are there any github branches that are no longer needed and should be deleted does model md adequately describe the model in terms appropriate for teachers does implementation notes md adequately describe the implementation with an overview that will be useful to future maintainers code reviewer please review implementation notes and wrap up sim specific query parameters if any should be identified and documented in one js file in js common or js if there is no common the js file should be named prefix queryparameters js for example arithmeticqueryparameters js for the aritmetic repository or fbqueryparameters js for function builder where the fb prefix is used query parameters that are public facing should be identified using public true in the schema all sims should use a color file named myrepocolors js or if using abbreviations mrcolors js and use profilecolorproperty where appropriate even if they have a single default profile to support color editing and phet io studio the colorprofile pattern was converted to colors js files in please see properties blob master js common gaspropertiescolors js for a good example coding conventions this section deals with phet coding conventions you do not need to exhaustively check every item in this section nor do you necessarily need to check these items one at a time the goal is to determine whether the code generally meets phet standards is the code formatted according to phet conventions see for intellij idea code style names types variables properties properties functions should be sufficiently descriptive and specific and should avoid non standard abbreviations for example js const numpart incorrect const numberofparticles correct const width incorrect const beakerwidth correct verify that are followed for constructors use parameters for things that don’t have a default use options for things that have a default value this improves readability at the call site especially when the number of parameters is large it also eliminates order dependency that is required by using parameters for example this constructor uses parameters for everything at the call site the semantics of the arguments are difficult to determine without consulting the constructor js class ballnode extends node param ball ball model element param property visibleproperty is the ball visible param color string fill fill color param color string stroke stroke color param number linewidth width of the stroke constructor ball visibleproperty fill stroke linewidth call site const ballnode new ballnode ball visibleproperty blue black here’s the same constructor with an appropriate use of options the call site is easier to read and the order of options is flexible js class ballnode extends node param ball ball model element param property visibleproperty is the ball visible param object constructor ball visibleproperty options options merge fill white color string fill color stroke black color string stroke color linewidth number width of the stroke options call site const ballnode new ballnode ball visibleproperty fill blue stroke black linewidth when options are passed through one constructor to another a nested options pattern should be used this helps to avoid duplicating option names and or accidentally overwriting options for different components that use the same option names make sure to use phet core merge instead of extend or merge merge will automatically recurse to keys named options and extend those as well example js class particleboxnode extends node param particlebox particlebox model element param property visibleproperty are the box and its contents visible param object constructor particlebox visibleproperty options options merge fill white color string fill color stroke black color string stroke color linewidth number width of the stroke particlenodeoptions fill red stroke gray linewidth options add particle this addchild new particlenode particlebox particle options particlenodeoptions a possible exception to this guideline is when the constructor api is improved by hiding the implementation details i e not revealing that a sub component exists in that case it may make sense to use new top level options this is left to developer and reviewer discretion for more information on the history and thought process around the nested options pattern please see n a if references are needed to the enclosing object such as for a closure self should be defined but it should only be used in closures the self variable should not be defined unless it is needed in a closure example js const self this someproperty link function self dosomething this dosomethingelse generally lines should not exceed columns break up long statements expressions or comments into multiple lines to optimize readability it is ok for require statements or other structured patterns to exceed columns use your judgment functions should be invoked using the dot operator rather than the bracket operator for more details please see for example js avoid this ok isfacesmile this smile this frown ok if isfacesmile this smile else this frown it is not uncommon to use conditional shorthand and short circuiting for invocation use parentheses to maximize readability js expression statement expression foo bar foobar foocat foo bar foobar foo bar foobar nowiamconfused this fill foo bar red blue if the expression is only one item the parentheses can be omitted this is the most common use case js assert assert happy why aren t you happy happy smile const thoughts happy i am happy i am not happy naming for property values all axon property instances should be declared with the suffix property for example if a visible property is added it should have the name visibleproperty instead of simply visible this will help to avoid confusion with non property definitions identify violations by searching for regular expression new property properties should use type specific subclasses where appropriate e g booleanproperty numberproperty stringproperty or provide documentation as to why they are not are validator validation options valuetype validvalues etc utilized these are supported in a number of core types like emitter and property is their presence or lack thereof properly documented files should be named like capitalizedcamelcasing js when returning a constructor or lowercasecamelcasing js when returning a non constructor function or singleton when returning a constructor or singleton the constructor name should match the filename where singletons are treated like classes with static attributes like simularasaconstants or simularasacolors uppercase should be used assertions should be used appropriately and consistently type checking should not just be done in code comments use array isarray to type check an array if you need to namespace an inner class use namespace register and include a comment about why the inner class needs to be namespaced use the form outerclassname innerclassname for the key for example js import mynamespace from class slotmachinenode extends node constructor this levernode new levernode mynamespace register slotmachinenode slotmachinenode class levernode extends node it was useful to be able to instantiate this in the console for testing and we may need to do so in the future mynamespace register slotmachinenode levernode levernode return slotmachinenode putting unused parameters in callbacks is up to developer discretion as long they are correct wrt to the actual callback signature for example both of these are acceptable js property multilink style active color some algorithm that uses style and active property multilink style active some algorithm that uses style and active this is not acceptable because the parameter is incorrect js property multilink style active linewidth some algorithm that uses style and active getters setters defined in sims should be used judiciously when a property exists only when the benefit of conciseness outweighs the potential loss of readability if getters setters exist try to not mix usage of them with property access the model and view code should be written such that it makes no assumptions about the animation frame rate this it will encounter the default max dt delta time value is defined in screen js and smaller values should be used if the default is too large there is no minimum value for dt which implies that there is no maximum supported frame rate the sim should be able to handle this for an example of a problem that resulted from assuming that a max rate of fps would be the norm please see documentation this section deals with phet documentation conventions you do not need to exhaustively check every item in this section nor do you necessarily need to check these items one at a time the goal is to determine whether the code generally meets phet standards all classes methods and properties are documented documentation at the top of js files should provide an overview of purpose responsibilies and where useful examples of api use if the file contains a subclass definition it should indicate what functionality it adds to the superclass the javascript source code must be reasonably well documented this is difficult to specify precisely but the idea is that someone who is moderately experienced with javascript can quickly understand the general function of the source code as well as the overall flow of the code by reading through the comments for an example of the type of documentation that is required please see the example sim repository differentiate between property and property in comments they are different things property is a type in axon property is any value associated with a javascript object often field can be used in exchange for property which can help with clarity search for property to identify violations n a classes that mix in traits or mixin should use the mixes mytype annotation line comments should generally be preceded by a blank line for example js randomly choose an existing crystal to possibly bond to const crystal this crystals get random this crystals length find a good configuration to have the particles move toward const targetconfiguration this gettargetconfiguration crystal when documenting conditionals if else statements follow these guidlines comments above the first if in a conditional should be about the entire conditional not just the if block comments should not break up sections of the conditional if a comment is needed to describe a single block of the conditional then add that comment just inside the block no space between the if else if else and the comment with a space below it as to not be confused with a comment about logic below js comment about the reason to split on peppers were pickled if peterpiperpickedajarofpickledpeppers if we want to explain what this if statement is about peteralsohasbrine else documentation about why we have no peppers this is about the next line of code and not the else as a whole block peterhasnopeppers line comments should have whitespace between the and the first letter of the line comment see the preceding example do the author annotations seem correct constructor and function documentation parameter types and names should be clearly specified for each constructor and function using param annotations the description for each parameter should follow a hyphen primitive types should use lower case for example js the phetdeveloper is responsible for creating code for simulations and documenting their code thoroughly class phetdeveloper param string name full name param number age age in years param boolean isemployee whether this developer is an employee of cu param function callback called immediate after coffee is consumed param property hoursproperty cumulative hours worked param string friendnames names of friends param object constructor name age isemployee callback hoursproperty friendnames options for most functions the same form as above should be used with a returns annotation which identifies the return type and the meaning of the returned value functions should also document any side effects for extremely simple functions that are just a few lines of simple code an abbreviated line comment can be used for example computes number distance based on foo foo abstract methods should be annotated with abstract and should typically throw an error for example js updates this node abstract protected update throw new error update must be implemented by subclass type expressions this section deals with phet conventions for type expressions you do not need to exhaustively check every item in this section nor do you necessarily need to check these items one at a time the goal is to determine whether the code generally meets phet standards type expressions should conform approximately to syntax phet stretches the syntax in many cases beyond the scope of this document to describe prefer the most basic restrictive type expression when defining apis for example if a client only needs to know that a parameter is node don’t describe the parameter as rectangle all method parameters should have type expressions for example param number width in sim specific code options and fields should have type expressions when their type is not obvious from the context “obvious” typically means that the value type is clearly shown in the righthand side of the definition e g const width clear shows that width is number e g const checkbox new checkbox … clearly shows that checkbox is checkbox if the type is obvious from the context the developer may still provide a type expression at his her discretion examples js public gamestate the current state of the game this gamestate this computegamestate public read only the width of the container this containerwidth private the checkbox used to show particles this particlesvisiblecheckbox new checkbox in common code repositories all options and fields should have type expressions regardless of their visibility and regardless whether their type is obvious from the context if the same examples from above appeared in common code js public gamestate the current state of the game this gamestate this computegamestate public read only number the width of the container this containerwidth private checkbox the checkbox used to show particles this particlesvisiblecheckbox new checkbox type expressions for enumeration values should be annotated as instances of that enumeration see examples in for more js param leftorright whichhand function gethand whichhand if whichhand leftorright left return new lefthand else if whichhand leftorright right return new righthand type expressions for functions have a variety of possibilities increasing in complexity depending on the case in general note that function is not enough information here are some better options the most basic option it to use google closure type syntax for more info see this specifies the param return types but nothing more here are some examples param function noparamsandnoreturnvalue param function number givemenumberandreturnnothing param function number number param function new node createnode a function that takes the node constructor when needing to be a bit more specific add a name to parameters of the function sometimes this is all that is needed for clarity on what the param does param function model mymodel length number name string node getlengthnode param function aselfexplanatorynameforastring string node getstringnode if isn t enough use english to explain the parameters and return values this is easy because they are named and can be easily mentioned param function model mymodel length number name string node getlengthnode returns the length node that you have always wanted name is the name of the source of your aspirations length is a special number according to the following criteria if needing more complexity or using jsdoc rendering tools like phet io documentation does you must use a jsdoc compatible format not or and you may need to use the more complicated solution see jsdoc docs for more info here is an example of a named callback js name myspecialcallback converts a string to a number param string returns number param myspecialcallback callback x function callback callback still chocolate type expressions for anonymous objects have a variety of possibilities increasing in complexity depending on the case when the documentation is close by then object is still acceptable this mainly applies to options and similar patterns param object this is great because of the extend call lines down when using an object with specific properties name them and their types like so param name string address street string returnnode function number node personaldata note that shoesize is optional here when you need a bit more explanation keep the same type expression as but feel free to outline specifics in english after the param name param name string address street string returnnode function number node personaldata use english after to explain pieces of this if needed outline properties on their own lines name is something address is something else returnnode does this thing not all objects have named keys like and here is how to document dictionary like object s where each key is some type and the value is another type for key value pairs use this object where keys are strings and values are numbers object naming each of these can help identify them too feel free to explain in english after the type expression if needed if things are too complicated for the above cases use a def js file especially is used in more than one file or a typedef declaration right above the jsdoc that uses the typedef look for cases where the use of type expressions involving property subclasses are incorrect because of the structure of the property class hierarchy specifying type specific properties booleanproperty numberproperty may be incorrect because it precludes values of type derivedproperty and dynamicproperty similarly use of derivedproperty and dynamicproperty precludes values of e g booleanproperty especially in common code using property is typically correct unless some specific feature of the property subclass is required for example property instead of booleanproperty visibility annotations this section deals with phet conventions for visibility annotations you do not need to exhaustively check every item in this section nor do you necessarily need to check these items one at a time the goal is to determine whether the code generally meets phet standards because javascript lacks visibility modifiers public protected private phet uses jsdoc visibility annotations to document the intent of the programmer and define the public api visibility annotations are required for anything that javascript makes public information about these annotations can be found here note that other documentation systems like the google closure compiler use slightly different syntax in some cases where there are differences jsdoc is authoritative for example use array or object instead of array phet guidelines for visibility annotations are as follows use public for anything that is intended to be part of the public api use protected for anything that is intended for use by subtypes use private for anything that is not intended to be part of the public or protected api put qualifiers in parenthesis after the annotation for example to qualify that something is read only use public read only this indicates that the given property and its value should not be changed by outside code e g a property should not have its value changed to qualify that something is public to a specific repository use for example public scenery internal for something made public solely for use public for something made public solely for phet io use public phet io separate multiple qualifiers with commas for example public scenery internal read only for jsdoc style comments the annotation should appear in context like this js creates the icon for the energy screen a cartoonish bar graph returns node public for line comments the annotation can appear like this js public function listener function adds a listener addlistener function listener verify that every javascript property and function has a visibility annotation here are some helpful regular expressions to search for these declarations as phet uses them regex for property assignment like x y something s regex for function declarations function math libraries dot utils tofixed or dot utils tofixednumber should be used instead of tofixed javascript s tofixed is notoriously buggy behavior differs depending on browser because the spec doesn t specify whether to round or floor ie is no longer supported with that in mind remove ie specific workarounds use string includes and string startswith where possible organization readability and maintainability does the organization and structure of the code make sense do the model and view contain types that you would expect or guess by looking at the sim do the names of things correspond to the names that you see in the user interface are appropriate design patterns used see if new or inappropriate patterns are identified create an issue is inheritance used where appropriate does the type hierarchy make sense is composition favored over inheritance where appropriate see is there any unnecessary coupling e g by passing large objects to constructors or exposing unnecessary properties functions is there too much unnecessary decoupling e g by passing all of the properties of an object independently instead of passing the object itself are the source files reasonable in size scrutinize large files with too many responsibilities can responsibilities be broken into smaller delegates are any significant chunks of code duplicated this will be checked manually as well as with is there anything that should be generalized and migrated to common code are there any todo or fixme or review comments in the code they should be addressed or promoted to github issues are there any that should be factored out as constants and documented are there any constants that are duplicated in multiple files that should be factored out into a repo constants js file does the implementation rely on any specific constant values that are likely to change in the future identify constants that might be changed in the future use your judgement about which constants are likely candidates does changing the values of these constants break the sim for example see is used where appropriate verify that the sim is not inventing creating its own colors for things that have been standardized in phetcolorscheme identify any colors that might be worth adding to phetcolorscheme are all dependent properties modeled as derivedproperty instead of property all dynamics should be called from sim step dt do not use window settimeout or window setinterval this will help support legends of learning and phet io accessibility this section may be omitted if the sim has not been instrumented with accessibility features accessibility includes various features not all are always include ignore sections that do not apply general are accessibility features integrated well into the code they should be added in a maintainable way even if that requires upfront refactoring see the alternative input does the sim pass an accessibility fuzz test run with query parameters fuzzboard ea does this sim use specific keyboard shortcuts that overlap with global shortcuts see interactive description n a phet io this section may be omitted if the sim has not been instrumented for phet io but is likely good to glance at no matter does instrumentation follow the conventions described in this could be an extensive bullet at the very least be sure to know what amount of instrumentation this sim supports describing this further goes beyond the scope of this document n a phet io instantiates different objects and wires up listeners that are not present in the phet branded simulation it needs to be tested separately for memory leaks to help isolate the nature of the memory leak this test should be run separately from the phet brand memory leak test test with a colorized data stream and studio easily accessed from phetmarks compare to testing results done by the responsible developer and previous releases n a make sure unused phetioobject instances are disposed which unregisters their tandems make sure joist dt values are used instead of date now or other date functions perhaps try phet joist elapsedtime though this has already been mentioned it is necessary for reproducible playback via input events and deserves a comment in this phet io section are random numbers using dot dotrandom as an imported module not a global and all doing so after modules are declared non statically for example the following methods and perhaps others should not be used math random shuffle sample random this also deserves re iteration due to its effect on record playback for phet io like json keys for undefined values are omitted when serializing objects across frames consider this when determining whether tostateobject should use null or undefined values phet prefers to use the term position to refer to the physical x y position of objects this applies to both brands but is more important for the phet io api see are your iotype state methods violating the api of the core type by accessing private fields when defining a boolean property to indicate whether something is enabled use axon enabledproperty this should be done in both the model and the view | 0 |
319,421 | 9,743,903,914 | IssuesEvent | 2019-06-03 04:28:05 | ga4gh/data-repository-service-schemas | https://api.github.com/repos/ga4gh/data-repository-service-schemas | closed | Update master to get latest docs from develop | Due: Feb Priority: Critical | In the interest of time, #192 is being merged with changes that have not been propagated entirely through the codebase. In particular, we need to update the documentation to reflect new paths (i.e. `/ga4gh/dos/v1/` to `/ga4gh/drs/v1/`) and the newly-named Bundles and Objects, to ensure that Snyk testing is properly configured for this repository, and to properly document the name change. | 1.0 | Update master to get latest docs from develop - In the interest of time, #192 is being merged with changes that have not been propagated entirely through the codebase. In particular, we need to update the documentation to reflect new paths (i.e. `/ga4gh/dos/v1/` to `/ga4gh/drs/v1/`) and the newly-named Bundles and Objects, to ensure that Snyk testing is properly configured for this repository, and to properly document the name change. | non_main | update master to get latest docs from develop in the interest of time is being merged with changes that have not been propagated entirely through the codebase in particular we need to update the documentation to reflect new paths i e dos to drs and the newly named bundles and objects to ensure that snyk testing is properly configured for this repository and to properly document the name change | 0 |
2,180 | 7,652,905,529 | IssuesEvent | 2018-05-10 00:36:58 | react-navigation/react-navigation | https://api.github.com/repos/react-navigation/react-navigation | closed | IOS native swipe gesture animation freezes InteractionManager.runAfterInteractions | needs action from maintainer | ## The issue tracker is reserved for bug reports only.
### Current Behavior
If you navigatie from screen A to screen B and quickly swipe back to screen A, InteractionManager wont execute tasks which causes the flatlist to stop rendering new items. You can still see the previously rendered items but it wont render any new one so you just see a grey background.
Screen A contains a flatlist
Screen B detail page
The issue is caused by the PanResponder inside CardStack.js because on every render a new PanResponder is created. This is an issue since you can end up working with a old reference. In some cases like in which i describe it will call onResponderGrant on the previous PanResponder and will call onResponderEnd on the newly created PanResponder. And since PanResponder.onResponderEnd calls clearInteractionHandle which will only clear the interaction handle if there is one present it will never clear the interaction handle. So InteractionManager wont be able to run any of its scheduled tasks.
FlatList which is basically just a wrapped VirtualizedList uses react native its Batchinator to update the cells to render.
```javascript
this._updateCellsToRenderBatcher = new Batchinator(
this._updateCellsToRender,
this.props.updateCellsBatchingPeriod,
);
```
```javascript
class Batchinator {
_callback: () => void;
_delay: number;
_taskHandle: ?{cancel: () => void};
constructor(callback: () => void, delayMS: number) {
this._delay = delayMS;
this._callback = callback;
}
/*
* Cleanup any pending tasks.
*
* By default, if there is a pending task the callback is run immediately. Set the option abort to
* true to not call the callback if it was pending.
*/
dispose(options: {abort: boolean} = {abort: false}) {
if (this._taskHandle) {
this._taskHandle.cancel();
if (!options.abort) {
this._callback();
}
this._taskHandle = null;
}
}
schedule() {
if (this._taskHandle) {
return;
}
const timeoutHandle = setTimeout(() => {
this._taskHandle = InteractionManager.runAfterInteractions(() => {
// Note that we clear the handle before invoking the callback so that if the callback calls
// schedule again, it will actually schedule another task.
this._taskHandle = null;
this._callback();
});
}, this._delay);
this._taskHandle = {cancel: () => clearTimeout(timeoutHandle)};
}
}
```
PanResponder.js
```javascript
function clearInteractionHandle(
interactionState: {handle: ?number},
callback: Function,
event: Object,
gestureState: Object
) {
if (interactionState.handle) {
InteractionManager.clearInteractionHandle(interactionState.handle);
interactionState.handle = null;
}
if (callback) {
callback(event, gestureState);
}
}
```
**Example project https://github.com/wesleymooiman/react-navigation-bug-example**
### Expected Behavior
Its should clear the correct handle so InteractionManager knows its handle has been cleared and can process scheduled tasks.
### How to reproduce
Create an app with a StackRouter which contains two screens, a list screen which use a flatlist and a detail page. Navigate from screen A with the flatlist to screen B and quickly swipe back before screen B has completely loaded. Now scroll inside the FlatList and notice it wont render any new items.
### Your Environment
| software | version
| ---------------- | -------
| react-navigation | 1.5.11
| react-native | 0.53.0
| node | 9.11.1
| npm or yarn | 1.6.0
| True | IOS native swipe gesture animation freezes InteractionManager.runAfterInteractions - ## The issue tracker is reserved for bug reports only.
### Current Behavior
If you navigatie from screen A to screen B and quickly swipe back to screen A, InteractionManager wont execute tasks which causes the flatlist to stop rendering new items. You can still see the previously rendered items but it wont render any new one so you just see a grey background.
Screen A contains a flatlist
Screen B detail page
The issue is caused by the PanResponder inside CardStack.js because on every render a new PanResponder is created. This is an issue since you can end up working with a old reference. In some cases like in which i describe it will call onResponderGrant on the previous PanResponder and will call onResponderEnd on the newly created PanResponder. And since PanResponder.onResponderEnd calls clearInteractionHandle which will only clear the interaction handle if there is one present it will never clear the interaction handle. So InteractionManager wont be able to run any of its scheduled tasks.
FlatList which is basically just a wrapped VirtualizedList uses react native its Batchinator to update the cells to render.
```javascript
this._updateCellsToRenderBatcher = new Batchinator(
this._updateCellsToRender,
this.props.updateCellsBatchingPeriod,
);
```
```javascript
class Batchinator {
_callback: () => void;
_delay: number;
_taskHandle: ?{cancel: () => void};
constructor(callback: () => void, delayMS: number) {
this._delay = delayMS;
this._callback = callback;
}
/*
* Cleanup any pending tasks.
*
* By default, if there is a pending task the callback is run immediately. Set the option abort to
* true to not call the callback if it was pending.
*/
dispose(options: {abort: boolean} = {abort: false}) {
if (this._taskHandle) {
this._taskHandle.cancel();
if (!options.abort) {
this._callback();
}
this._taskHandle = null;
}
}
schedule() {
if (this._taskHandle) {
return;
}
const timeoutHandle = setTimeout(() => {
this._taskHandle = InteractionManager.runAfterInteractions(() => {
// Note that we clear the handle before invoking the callback so that if the callback calls
// schedule again, it will actually schedule another task.
this._taskHandle = null;
this._callback();
});
}, this._delay);
this._taskHandle = {cancel: () => clearTimeout(timeoutHandle)};
}
}
```
PanResponder.js
```javascript
function clearInteractionHandle(
interactionState: {handle: ?number},
callback: Function,
event: Object,
gestureState: Object
) {
if (interactionState.handle) {
InteractionManager.clearInteractionHandle(interactionState.handle);
interactionState.handle = null;
}
if (callback) {
callback(event, gestureState);
}
}
```
**Example project https://github.com/wesleymooiman/react-navigation-bug-example**
### Expected Behavior
Its should clear the correct handle so InteractionManager knows its handle has been cleared and can process scheduled tasks.
### How to reproduce
Create an app with a StackRouter which contains two screens, a list screen which use a flatlist and a detail page. Navigate from screen A with the flatlist to screen B and quickly swipe back before screen B has completely loaded. Now scroll inside the FlatList and notice it wont render any new items.
### Your Environment
| software | version
| ---------------- | -------
| react-navigation | 1.5.11
| react-native | 0.53.0
| node | 9.11.1
| npm or yarn | 1.6.0
| main | ios native swipe gesture animation freezes interactionmanager runafterinteractions the issue tracker is reserved for bug reports only current behavior if you navigatie from screen a to screen b and quickly swipe back to screen a interactionmanager wont execute tasks which causes the flatlist to stop rendering new items you can still see the previously rendered items but it wont render any new one so you just see a grey background screen a contains a flatlist screen b detail page the issue is caused by the panresponder inside cardstack js because on every render a new panresponder is created this is an issue since you can end up working with a old reference in some cases like in which i describe it will call onrespondergrant on the previous panresponder and will call onresponderend on the newly created panresponder and since panresponder onresponderend calls clearinteractionhandle which will only clear the interaction handle if there is one present it will never clear the interaction handle so interactionmanager wont be able to run any of its scheduled tasks flatlist which is basically just a wrapped virtualizedlist uses react native its batchinator to update the cells to render javascript this updatecellstorenderbatcher new batchinator this updatecellstorender this props updatecellsbatchingperiod javascript class batchinator callback void delay number taskhandle cancel void constructor callback void delayms number this delay delayms this callback callback cleanup any pending tasks by default if there is a pending task the callback is run immediately set the option abort to true to not call the callback if it was pending dispose options abort boolean abort false if this taskhandle this taskhandle cancel if options abort this callback this taskhandle null schedule if this taskhandle return const timeouthandle settimeout this taskhandle interactionmanager runafterinteractions note that we clear the handle before invoking the callback so that if the callback calls schedule again it will actually schedule another task this taskhandle null this callback this delay this taskhandle cancel cleartimeout timeouthandle panresponder js javascript function clearinteractionhandle interactionstate handle number callback function event object gesturestate object if interactionstate handle interactionmanager clearinteractionhandle interactionstate handle interactionstate handle null if callback callback event gesturestate example project expected behavior its should clear the correct handle so interactionmanager knows its handle has been cleared and can process scheduled tasks how to reproduce create an app with a stackrouter which contains two screens a list screen which use a flatlist and a detail page navigate from screen a with the flatlist to screen b and quickly swipe back before screen b has completely loaded now scroll inside the flatlist and notice it wont render any new items your environment software version react navigation react native node npm or yarn | 1 |
242 | 2,971,403,873 | IssuesEvent | 2015-07-14 06:31:35 | spyder-ide/spyder | https://api.github.com/repos/spyder-ide/spyder | closed | Release 2.4 | Maintainability | Because it is hard to backport stable changes (that people need to use in their workflow right away) from 2.3 to master, I propose to cut 2.4. It will solve the broken merge problem with linefeeds and new signal/slot mechanism. | True | Release 2.4 - Because it is hard to backport stable changes (that people need to use in their workflow right away) from 2.3 to master, I propose to cut 2.4. It will solve the broken merge problem with linefeeds and new signal/slot mechanism. | main | release because it is hard to backport stable changes that people need to use in their workflow right away from to master i propose to cut it will solve the broken merge problem with linefeeds and new signal slot mechanism | 1 |
3,682 | 15,037,306,024 | IssuesEvent | 2021-02-02 16:11:45 | IITIDIDX597/sp_2021_team1 | https://api.github.com/repos/IITIDIDX597/sp_2021_team1 | opened | System updates notifications | Epic: 5 Maintaining the system Story Week 3 | **Project Goal:** S Lab is a tailored integrative learning and collaboration platform for clinicians that combines the latest research and tacit knowledge gained from experience in a practical way, while at the same time foster deeper learning experiences in order to deliver better AbilityLab Patient care.
**Hill Statement:** Individual Clinicians can reference relevant, continuously evolving information for their patient's therapy needs to self-manage their approach & patient care plan development in a single platform.
**Sub-Hill Statements:**
1. The learning platform will be routinely updated with S Lab's own research advancements, as well as outside discoveries and best practices developed for rehabilitation treatments.
### **Story Details:**
As a: clinician
I want: to get a notification of any system updates or site downtimes a day before it is scheduled
So that: I can plan my learning accordingly | True | System updates notifications - **Project Goal:** S Lab is a tailored integrative learning and collaboration platform for clinicians that combines the latest research and tacit knowledge gained from experience in a practical way, while at the same time foster deeper learning experiences in order to deliver better AbilityLab Patient care.
**Hill Statement:** Individual Clinicians can reference relevant, continuously evolving information for their patient's therapy needs to self-manage their approach & patient care plan development in a single platform.
**Sub-Hill Statements:**
1. The learning platform will be routinely updated with S Lab's own research advancements, as well as outside discoveries and best practices developed for rehabilitation treatments.
### **Story Details:**
As a: clinician
I want: to get a notification of any system updates or site downtimes a day before it is scheduled
So that: I can plan my learning accordingly | main | system updates notifications project goal s lab is a tailored integrative learning and collaboration platform for clinicians that combines the latest research and tacit knowledge gained from experience in a practical way while at the same time foster deeper learning experiences in order to deliver better abilitylab patient care hill statement individual clinicians can reference relevant continuously evolving information for their patient s therapy needs to self manage their approach patient care plan development in a single platform sub hill statements the learning platform will be routinely updated with s lab s own research advancements as well as outside discoveries and best practices developed for rehabilitation treatments story details as a clinician i want to get a notification of any system updates or site downtimes a day before it is scheduled so that i can plan my learning accordingly | 1 |
4,505 | 23,445,967,993 | IssuesEvent | 2022-08-15 19:40:22 | carbon-design-system/carbon | https://api.github.com/repos/carbon-design-system/carbon | closed | [Bug]: Pointer events on assistive text for icon-only buttons get in the way | status: needs more info type: bug 🐛 component: button status: waiting for maintainer response 💬 package: @carbon/react | ### Package
carbon-components, carbon-components-svelte
### Browser
Chrome, Firefox, Edge
### Package version
v10.56.0 (via carbon-components-svelte)
### React version
_No response_
### Description
When using icon buttons in tables, the tooltip popup can get in the way. Consider action icons at the end of a row:
When hovering one of the buttons, the button in the adjacent row is almost completely obscured by the tooltip and the pointer events stop the cursor from interacting with the other button:
When creating a CodeSandbox example, I noticed that for the React library the description appears above, but the issue is the same:
There appears to be a specific rule for icon only buttons that enables pointer events:
### CodeSandbox example
https://codesandbox.io/s/carbon-assistive-text-issue-9xc962?file=/src/index.js
### Steps to reproduce
- Add a table
- Add icon-only buttons with icon descriptions to every row
- Hover over one of the buttons and try to access the button underneath the tooltip in another row
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md)
- [X] I checked the [current issues](https://github.com/carbon-design-system/carbon/issues) for duplicate problems | True | [Bug]: Pointer events on assistive text for icon-only buttons get in the way - ### Package
carbon-components, carbon-components-svelte
### Browser
Chrome, Firefox, Edge
### Package version
v10.56.0 (via carbon-components-svelte)
### React version
_No response_
### Description
When using icon buttons in tables, the tooltip popup can get in the way. Consider action icons at the end of a row:
When hovering one of the buttons, the button in the adjacent row is almost completely obscured by the tooltip and the pointer events stop the cursor from interacting with the other button:
When creating a CodeSandbox example, I noticed that for the React library the description appears above, but the issue is the same:
There appears to be a specific rule for icon only buttons that enables pointer events:
### CodeSandbox example
https://codesandbox.io/s/carbon-assistive-text-issue-9xc962?file=/src/index.js
### Steps to reproduce
- Add a table
- Add icon-only buttons with icon descriptions to every row
- Hover over one of the buttons and try to access the button underneath the tooltip in another row
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/carbon-design-system/carbon/blob/f555616971a03fd454c0f4daea184adf41fff05b/.github/CODE_OF_CONDUCT.md)
- [X] I checked the [current issues](https://github.com/carbon-design-system/carbon/issues) for duplicate problems | main | pointer events on assistive text for icon only buttons get in the way package carbon components carbon components svelte browser chrome firefox edge package version via carbon components svelte react version no response description when using icon buttons in tables the tooltip popup can get in the way consider action icons at the end of a row when hovering one of the buttons the button in the adjacent row is almost completely obscured by the tooltip and the pointer events stop the cursor from interacting with the other button when creating a codesandbox example i noticed that for the react library the description appears above but the issue is the same there appears to be a specific rule for icon only buttons that enables pointer events codesandbox example steps to reproduce add a table add icon only buttons with icon descriptions to every row hover over one of the buttons and try to access the button underneath the tooltip in another row code of conduct i agree to follow this project s i checked the for duplicate problems | 1 |
5,247 | 26,566,382,564 | IssuesEvent | 2023-01-20 20:40:59 | tethysplatform/tethys | https://api.github.com/repos/tethysplatform/tethys | opened | [FEATURE] Make Most Dependencies Optional | maintain dependencies feature request | **Is your feature request related to a problem? Please describe.**
Tethys has a lot of dependencies and most are not used in every installation. Provide a way to handle optional dependencies so we can create a "MiniTethys"
**Describe the solution you'd like**
Develop a function that can be used to import optional dependencies and handle failure gracefully when not installed. Provide a standardized error message.
| True | [FEATURE] Make Most Dependencies Optional - **Is your feature request related to a problem? Please describe.**
Tethys has a lot of dependencies and most are not used in every installation. Provide a way to handle optional dependencies so we can create a "MiniTethys"
**Describe the solution you'd like**
Develop a function that can be used to import optional dependencies and handle failure gracefully when not installed. Provide a standardized error message.
| main | make most dependencies optional is your feature request related to a problem please describe tethys has a lot of dependencies and most are not used in every installation provide a way to handle optional dependencies so we can create a minitethys describe the solution you d like develop a function that can be used to import optional dependencies and handle failure gracefully when not installed provide a standardized error message | 1 |
85,406 | 15,736,700,487 | IssuesEvent | 2021-03-30 01:14:19 | forse01/CVE-2020-17527-Tomcat | https://api.github.com/repos/forse01/CVE-2020-17527-Tomcat | opened | CVE-2021-25122 (High) detected in tomcat-coyote-9.0.0.M1.jar | security vulnerability | ## CVE-2021-25122 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-coyote-9.0.0.M1.jar</b></p></summary>
<p>Tomcat Connectors and HTTP parser</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to vulnerable library: CVE-2020-17527-Tomcat/lib/tomcat-coyote.jar</p>
<p>
Dependency Hierarchy:
- :x: **tomcat-coyote-9.0.0.M1.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</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>
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25122>CVE-2021-25122</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>7.5</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: High
- 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://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:8.5.62,9.0.42,10.0.2;org.apache.tomcat:tomcat-coyote:8.5.62,9.0.42,10.0.2</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-25122 (High) detected in tomcat-coyote-9.0.0.M1.jar - ## CVE-2021-25122 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-coyote-9.0.0.M1.jar</b></p></summary>
<p>Tomcat Connectors and HTTP parser</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to vulnerable library: CVE-2020-17527-Tomcat/lib/tomcat-coyote.jar</p>
<p>
Dependency Hierarchy:
- :x: **tomcat-coyote-9.0.0.M1.jar** (Vulnerable Library)
<p>Found in base branch: <b>main</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>
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-25122>CVE-2021-25122</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>7.5</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: High
- 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://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:8.5.62,9.0.42,10.0.2;org.apache.tomcat:tomcat-coyote:8.5.62,9.0.42,10.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_main | cve high detected in tomcat coyote jar cve high severity vulnerability vulnerable library tomcat coyote jar tomcat connectors and http parser library home page a href path to vulnerable library cve tomcat lib tomcat coyote jar dependency hierarchy x tomcat coyote jar vulnerable library found in base branch main vulnerability details when responding to new connection requests apache tomcat versions to to and to could duplicate request headers and a limited amount of request body from one request to another meaning user a and user b could both see the results of user a s request 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 high 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 org apache tomcat embed tomcat embed core org apache tomcat tomcat coyote step up your open source security game with whitesource | 0 |
113,228 | 9,633,118,515 | IssuesEvent | 2019-05-15 17:50:34 | hashmapinc/Drillflow | https://api.github.com/repos/hashmapinc/Drillflow | closed | QA: Certification Tests:Soap UI Cert Tests Trajectory | API Blocked Testing | Shehzad needs a chance to review the tests to understand what they are doing similar to what happened with Sukhendu & Theresa with Logs on 4/26. This is anticipated to happen with Mike today (4/26). | 1.0 | QA: Certification Tests:Soap UI Cert Tests Trajectory - Shehzad needs a chance to review the tests to understand what they are doing similar to what happened with Sukhendu & Theresa with Logs on 4/26. This is anticipated to happen with Mike today (4/26). | non_main | qa certification tests soap ui cert tests trajectory shehzad needs a chance to review the tests to understand what they are doing similar to what happened with sukhendu theresa with logs on this is anticipated to happen with mike today | 0 |
807,370 | 29,998,478,514 | IssuesEvent | 2023-06-26 07:40:56 | GSM-MSG/SMS-FrontEnd | https://api.github.com/repos/GSM-MSG/SMS-FrontEnd | closed | Not Found Page 추가 | 1️⃣ Priority: High ✨ Feature | ### Describe
404 페이지를 추가합니다
<img width="745" alt="image" src="https://github.com/GSM-MSG/SMS-FrontEnd/assets/57276315/67f866f1-487c-4dd3-9f15-98d4bcb9ba28">
### Additional
_No response_ | 1.0 | Not Found Page 추가 - ### Describe
404 페이지를 추가합니다
<img width="745" alt="image" src="https://github.com/GSM-MSG/SMS-FrontEnd/assets/57276315/67f866f1-487c-4dd3-9f15-98d4bcb9ba28">
### Additional
_No response_ | non_main | not found page 추가 describe 페이지를 추가합니다 img width alt image src additional no response | 0 |
4,635 | 23,992,516,272 | IssuesEvent | 2022-09-14 03:24:35 | centerofci/mathesar | https://api.github.com/repos/centerofci/mathesar | closed | Add record selector to "table" BreadcrumbItem | type: enhancement work: frontend status: ready restricted: new maintainers | ## Current behavior
- On the Record Page the app header has a link to the Table Page, but nothing comes after it
## Desired behavior
- The [Navigation specs](https://github.com/centerofci/mathesar-wiki/blob/master/design/specs/navigation.md#navigation-via-site-header) require an icon button after the Table Page link which opens the record selector
- When the user clicks this link, a modal Record Selector should open. Upon selecting a record, the browser should navigate to the Record Page for that Record.
_Note: If you're curious, see #1521 for additional improvements we plan to do later to make navigation even better._
| True | Add record selector to "table" BreadcrumbItem - ## Current behavior
- On the Record Page the app header has a link to the Table Page, but nothing comes after it
## Desired behavior
- The [Navigation specs](https://github.com/centerofci/mathesar-wiki/blob/master/design/specs/navigation.md#navigation-via-site-header) require an icon button after the Table Page link which opens the record selector
- When the user clicks this link, a modal Record Selector should open. Upon selecting a record, the browser should navigate to the Record Page for that Record.
_Note: If you're curious, see #1521 for additional improvements we plan to do later to make navigation even better._
| main | add record selector to table breadcrumbitem current behavior on the record page the app header has a link to the table page but nothing comes after it desired behavior the require an icon button after the table page link which opens the record selector when the user clicks this link a modal record selector should open upon selecting a record the browser should navigate to the record page for that record note if you re curious see for additional improvements we plan to do later to make navigation even better | 1 |
3,372 | 13,057,142,587 | IssuesEvent | 2020-07-30 06:41:11 | tgstation/tgstation-server | https://api.github.com/repos/tgstation/tgstation-server | closed | IInstanceManager.GetInstance should allow for null returns instead of throwing | Area: Instance Component Issue Maintainability Issue Work In Progress | Gives controllers a better change to react to an offline instance. New error code perhaps? | True | IInstanceManager.GetInstance should allow for null returns instead of throwing - Gives controllers a better change to react to an offline instance. New error code perhaps? | main | iinstancemanager getinstance should allow for null returns instead of throwing gives controllers a better change to react to an offline instance new error code perhaps | 1 |
3,490 | 13,622,177,042 | IssuesEvent | 2020-09-24 02:51:46 | amyjko/faculty | https://api.github.com/repos/amyjko/faculty | closed | Data: Model to organize functionality and metadata | maintainability | It would have an interface for returning data sorted in various ways, and identifying links between data. At the moment, components just grab raw data structures and do their own filtering. | True | Data: Model to organize functionality and metadata - It would have an interface for returning data sorted in various ways, and identifying links between data. At the moment, components just grab raw data structures and do their own filtering. | main | data model to organize functionality and metadata it would have an interface for returning data sorted in various ways and identifying links between data at the moment components just grab raw data structures and do their own filtering | 1 |
5,656 | 29,169,883,457 | IssuesEvent | 2023-05-19 00:03:38 | project-chip/connectedhomeip | https://api.github.com/repos/project-chip/connectedhomeip | closed | KVS is being initialized multiple times with different paths | stale v1.1 maintainability | The KVS Init() call is being made atleast two times in Linux/Darwin applications (perhaps others as well). The first time with a custom path passed in by the application command line arguments (or default KVS path.). The second time inside PosixConfig::Init() with the default KVS path.
This might cause discrepancies, especially if the configuration paths are different. Currently, the code silently ignores the second init().
_Originally posted by @andy31415 in https://github.com/project-chip/connectedhomeip/pull/15963#discussion_r821853254_ | True | KVS is being initialized multiple times with different paths - The KVS Init() call is being made atleast two times in Linux/Darwin applications (perhaps others as well). The first time with a custom path passed in by the application command line arguments (or default KVS path.). The second time inside PosixConfig::Init() with the default KVS path.
This might cause discrepancies, especially if the configuration paths are different. Currently, the code silently ignores the second init().
_Originally posted by @andy31415 in https://github.com/project-chip/connectedhomeip/pull/15963#discussion_r821853254_ | main | kvs is being initialized multiple times with different paths the kvs init call is being made atleast two times in linux darwin applications perhaps others as well the first time with a custom path passed in by the application command line arguments or default kvs path the second time inside posixconfig init with the default kvs path this might cause discrepancies especially if the configuration paths are different currently the code silently ignores the second init originally posted by in | 1 |
2,651 | 9,083,425,139 | IssuesEvent | 2019-02-17 20:22:48 | lrozenblyum/chess | https://api.github.com/repos/lrozenblyum/chess | opened | Automate version verification | maintainability | dependencies and plugins upgrades possibilities might be automated.
See for example: http://www.mojohaus.org/versions-maven-plugin/display-plugin-updates-mojo.html
Discovered during #277
Probably blocked by #303 | True | Automate version verification - dependencies and plugins upgrades possibilities might be automated.
See for example: http://www.mojohaus.org/versions-maven-plugin/display-plugin-updates-mojo.html
Discovered during #277
Probably blocked by #303 | main | automate version verification dependencies and plugins upgrades possibilities might be automated see for example discovered during probably blocked by | 1 |
1,593 | 6,572,373,301 | IssuesEvent | 2017-09-11 01:48:43 | ansible/ansible-modules-extras | https://api.github.com/repos/ansible/ansible-modules-extras | closed | nmcli module throws IndexError in Subprocess | affects_2.1 bug_report networking waiting_on_maintainer | ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
nmcli
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.1.1.0
config file = /Users/.../ansible/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
```
[defaults]
remote_user=root
#host_key_checking=False
# Uncomment to get profiling information for executed tasks
#callback_whitelist = profile_tasks
#retry_files_enabled = False
retry_files_save_path = .
[ssh_connection]
pipelining = True
```
##### OS / ENVIRONMENT
macOS 10.11.6
Remote target:
```
# cat /etc/centos-release
CentOS Linux release 7.2.1511 (Core)
```
##### SUMMARY
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
# Enable Ansible's nmcli module
- name: Provide python networkmanager API
yum:
name: NetworkManager-glib
- name: setup VIP
nmcli:
state: present
conn_name: lo
ip4: "{{ VIP }}/32"
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
The ip addr should be added to the existing interface lo.
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with high verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
TASK [broker : Provide python networkmanager API] ******************************
ok: [local-broker-1]
TASK [broker : setup VIP] ********************************
fatal: [local-broker-1]: FAILED! => {"changed": false, "cmd": "", "failed": true, "msg": "Traceback (most recent call last):\n File \"/tmp/ansible_SfwO6E/ansible_modlib.zip/ansible/module_utils/basic.py\", line 2093, in run_command\n cmd = subprocess.Popen(args, **kwargs)\n File \"/usr/lib64/python2.7/subprocess.py\", line 711, in __init__\n errread, errwrite)\n File \"/usr/lib64/python2.7/subprocess.py\", line 1207, in _execute_child\n executable = args[0]\nIndexError: list index out of range\n", "rc": 257}
```
| True | nmcli module throws IndexError in Subprocess - ##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
nmcli
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.1.1.0
config file = /Users/.../ansible/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
```
[defaults]
remote_user=root
#host_key_checking=False
# Uncomment to get profiling information for executed tasks
#callback_whitelist = profile_tasks
#retry_files_enabled = False
retry_files_save_path = .
[ssh_connection]
pipelining = True
```
##### OS / ENVIRONMENT
macOS 10.11.6
Remote target:
```
# cat /etc/centos-release
CentOS Linux release 7.2.1511 (Core)
```
##### SUMMARY
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
# Enable Ansible's nmcli module
- name: Provide python networkmanager API
yum:
name: NetworkManager-glib
- name: setup VIP
nmcli:
state: present
conn_name: lo
ip4: "{{ VIP }}/32"
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
The ip addr should be added to the existing interface lo.
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with high verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
TASK [broker : Provide python networkmanager API] ******************************
ok: [local-broker-1]
TASK [broker : setup VIP] ********************************
fatal: [local-broker-1]: FAILED! => {"changed": false, "cmd": "", "failed": true, "msg": "Traceback (most recent call last):\n File \"/tmp/ansible_SfwO6E/ansible_modlib.zip/ansible/module_utils/basic.py\", line 2093, in run_command\n cmd = subprocess.Popen(args, **kwargs)\n File \"/usr/lib64/python2.7/subprocess.py\", line 711, in __init__\n errread, errwrite)\n File \"/usr/lib64/python2.7/subprocess.py\", line 1207, in _execute_child\n executable = args[0]\nIndexError: list index out of range\n", "rc": 257}
```
| main | nmcli module throws indexerror in subprocess issue type bug report component name nmcli ansible version ansible config file users ansible ansible cfg configured module search path default w o overrides configuration remote user root host key checking false uncomment to get profiling information for executed tasks callback whitelist profile tasks retry files enabled false retry files save path pipelining true os environment macos remote target cat etc centos release centos linux release core summary steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used enable ansible s nmcli module name provide python networkmanager api yum name networkmanager glib name setup vip nmcli state present conn name lo vip expected results the ip addr should be added to the existing interface lo actual results task ok task fatal failed changed false cmd failed true msg traceback most recent call last n file tmp ansible ansible modlib zip ansible module utils basic py line in run command n cmd subprocess popen args kwargs n file usr subprocess py line in init n errread errwrite n file usr subprocess py line in execute child n executable args nindexerror list index out of range n rc | 1 |
703,404 | 24,157,817,407 | IssuesEvent | 2022-09-22 09:08:31 | ansible-collections/azure | https://api.github.com/repos/ansible-collections/azure | closed | Keyvault lookup plugin doesn't take into account environment varibales | has_pr medium_priority | <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
##### ISSUE TYPE
- Feature idea
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
lookup plugins azure_keyvault_secret.py
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible [core 2.13.3]
config file = /home/xxx/Devs/services-factory_git/feat_groups/ansible.cfg
configured module search path = ['/home/xxx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/xxx/venv/ansible/lib/python3.10/site-packages/ansible
ansible collection location = /home/xxx/.ansible/collections:/usr/share/ansible/collections
executable location = /home/xxx/venv/ansible/bin/ansible
python version = 3.10.4 (main, Jun 29 2022, 12:14:53) [GCC 11.2.0]
jinja version = 3.1.2
libyaml = True
```
##### COLLECTION VERSION
<!--- Paste verbatim output from "ansible-galaxy collection list <namespace>.<collection>" between the quotes
for example: ansible-galaxy collection list community.general
-->
```paste below
Collection Version
------------------ -------
azure.azcollection 1.13.0
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Linux ubuntu
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
Export env vars
```bash
export AZURE_CLIENT_ID=<Service principal Client ID>
export AZURE_SECRET=<Service principal Secret>
export AZURE_TENANT=<Azure Tenancy ID>
```
Run this playbook
```yaml
gather_facts: false
connection: local
collections:
- azure.azcollection
tasks:
- name: Look up secret when ansible host is general VM
vars:
url: 'https://xxxxx.vault.azure.net'
secretname: 'test/b6e7b922f5814f17a9401f86a99adb81'
ansible.builtin.debug:
msg: "the value of this secret is {{
lookup(
'azure.azcollection.azure_keyvault_secret',secretname,vault_url=url
)
}}"
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
```
TASK [Look up secret when ansible host is general VM]
ok: [localhost] => {
"msg": "the value of this secret is ***************"
}
```
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
TASK [Look up secret when ansible host is general VM] ********************************************************************************
task path: /home/xxx/Devs/services-factory_git/feat_groups/playbooks/test_azure_keyvault/lookup2.yml:21
Unable to fetch MSI token. Will use service principal if provided.
exception during Jinja2 execution: Traceback (most recent call last):
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/ansible/template/__init__.py", line 984, in _lookup
ran = instance.run(loop_terms, variables=self._available_variables, **kwargs)
File "/home/xxx/.ansible/collections/ansible_collections/azure/azcollection/plugins/lookup/azure_keyvault_secret.py", line 203, in run
return lookup_secret_non_msi(terms, vault_url, kwargs)
File "/home/xxx/.ansible/collections/ansible_collections/azure/azcollection/plugins/lookup/azure_keyvault_secret.py", line 162, in lookup_secret_non_msi
credentials = ServicePrincipalCredentials(
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 355, in __init__
self.set_token()
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 362, in set_token
super(ServicePrincipalCredentials, self).set_token()
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 188, in set_token
self._create_adal_context()
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 109, in _create_adal_context
authority_url = authority_url + '/' + self._tenant
TypeError: can only concatenate str (not "NoneType") to str
fatal: [localhost]: FAILED! => {
"msg": "An unhandled exception occurred while running the lookup plugin 'azure.azcollection.azure_keyvault_secret'. Error was a <class 'TypeError'>, original message: can only concatenate str (not \"NoneType\") to str. can only concatenate str (not \"NoneType\") to str"
}
```
To avoid this problem, we can write the variables as parameters in the playbook but this is inconvenient. This behavior seems also inconsistent with other components of the collection.
| 1.0 | Keyvault lookup plugin doesn't take into account environment varibales - <!--- Verify first that your issue is not already reported on GitHub -->
<!--- Also test if the latest release and devel branch are affected too -->
<!--- Complete *all* sections as described, this form is processed automatically -->
##### SUMMARY
<!--- Explain the problem briefly below -->
##### ISSUE TYPE
- Feature idea
##### COMPONENT NAME
<!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure -->
lookup plugins azure_keyvault_secret.py
##### ANSIBLE VERSION
<!--- Paste verbatim output from "ansible --version" between quotes -->
```paste below
ansible [core 2.13.3]
config file = /home/xxx/Devs/services-factory_git/feat_groups/ansible.cfg
configured module search path = ['/home/xxx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/xxx/venv/ansible/lib/python3.10/site-packages/ansible
ansible collection location = /home/xxx/.ansible/collections:/usr/share/ansible/collections
executable location = /home/xxx/venv/ansible/bin/ansible
python version = 3.10.4 (main, Jun 29 2022, 12:14:53) [GCC 11.2.0]
jinja version = 3.1.2
libyaml = True
```
##### COLLECTION VERSION
<!--- Paste verbatim output from "ansible-galaxy collection list <namespace>.<collection>" between the quotes
for example: ansible-galaxy collection list community.general
-->
```paste below
Collection Version
------------------ -------
azure.azcollection 1.13.0
```
##### OS / ENVIRONMENT
<!--- Provide all relevant information below, e.g. target OS versions, network device firmware, etc. -->
Linux ubuntu
##### STEPS TO REPRODUCE
<!--- Describe exactly how to reproduce the problem, using a minimal test-case -->
<!--- Paste example playbooks or commands between quotes below -->
Export env vars
```bash
export AZURE_CLIENT_ID=<Service principal Client ID>
export AZURE_SECRET=<Service principal Secret>
export AZURE_TENANT=<Azure Tenancy ID>
```
Run this playbook
```yaml
gather_facts: false
connection: local
collections:
- azure.azcollection
tasks:
- name: Look up secret when ansible host is general VM
vars:
url: 'https://xxxxx.vault.azure.net'
secretname: 'test/b6e7b922f5814f17a9401f86a99adb81'
ansible.builtin.debug:
msg: "the value of this secret is {{
lookup(
'azure.azcollection.azure_keyvault_secret',secretname,vault_url=url
)
}}"
```
<!--- HINT: You can paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- Describe what you expected to happen when running the steps above -->
```
TASK [Look up secret when ansible host is general VM]
ok: [localhost] => {
"msg": "the value of this secret is ***************"
}
```
##### ACTUAL RESULTS
<!--- Describe what actually happened. If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes -->
```paste below
TASK [Look up secret when ansible host is general VM] ********************************************************************************
task path: /home/xxx/Devs/services-factory_git/feat_groups/playbooks/test_azure_keyvault/lookup2.yml:21
Unable to fetch MSI token. Will use service principal if provided.
exception during Jinja2 execution: Traceback (most recent call last):
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/ansible/template/__init__.py", line 984, in _lookup
ran = instance.run(loop_terms, variables=self._available_variables, **kwargs)
File "/home/xxx/.ansible/collections/ansible_collections/azure/azcollection/plugins/lookup/azure_keyvault_secret.py", line 203, in run
return lookup_secret_non_msi(terms, vault_url, kwargs)
File "/home/xxx/.ansible/collections/ansible_collections/azure/azcollection/plugins/lookup/azure_keyvault_secret.py", line 162, in lookup_secret_non_msi
credentials = ServicePrincipalCredentials(
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 355, in __init__
self.set_token()
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 362, in set_token
super(ServicePrincipalCredentials, self).set_token()
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 188, in set_token
self._create_adal_context()
File "/home/xxx/venv/ansible/lib/python3.10/site-packages/msrestazure/azure_active_directory.py", line 109, in _create_adal_context
authority_url = authority_url + '/' + self._tenant
TypeError: can only concatenate str (not "NoneType") to str
fatal: [localhost]: FAILED! => {
"msg": "An unhandled exception occurred while running the lookup plugin 'azure.azcollection.azure_keyvault_secret'. Error was a <class 'TypeError'>, original message: can only concatenate str (not \"NoneType\") to str. can only concatenate str (not \"NoneType\") to str"
}
```
To avoid this problem, we can write the variables as parameters in the playbook but this is inconvenient. This behavior seems also inconsistent with other components of the collection.
| non_main | keyvault lookup plugin doesn t take into account environment varibales summary issue type feature idea component name lookup plugins azure keyvault secret py ansible version paste below ansible config file home xxx devs services factory git feat groups ansible cfg configured module search path ansible python module location home xxx venv ansible lib site packages ansible ansible collection location home xxx ansible collections usr share ansible collections executable location home xxx venv ansible bin ansible python version main jun jinja version libyaml true collection version between the quotes for example ansible galaxy collection list community general paste below collection version azure azcollection os environment linux ubuntu steps to reproduce export env vars bash export azure client id export azure secret export azure tenant run this playbook yaml gather facts false connection local collections azure azcollection tasks name look up secret when ansible host is general vm vars url secretname test ansible builtin debug msg the value of this secret is lookup azure azcollection azure keyvault secret secretname vault url url expected results task ok msg the value of this secret is actual results paste below task task path home xxx devs services factory git feat groups playbooks test azure keyvault yml unable to fetch msi token will use service principal if provided exception during execution traceback most recent call last file home xxx venv ansible lib site packages ansible template init py line in lookup ran instance run loop terms variables self available variables kwargs file home xxx ansible collections ansible collections azure azcollection plugins lookup azure keyvault secret py line in run return lookup secret non msi terms vault url kwargs file home xxx ansible collections ansible collections azure azcollection plugins lookup azure keyvault secret py line in lookup secret non msi credentials serviceprincipalcredentials file home xxx venv ansible lib site packages msrestazure azure active directory py line in init self set token file home xxx venv ansible lib site packages msrestazure azure active directory py line in set token super serviceprincipalcredentials self set token file home xxx venv ansible lib site packages msrestazure azure active directory py line in set token self create adal context file home xxx venv ansible lib site packages msrestazure azure active directory py line in create adal context authority url authority url self tenant typeerror can only concatenate str not nonetype to str fatal failed msg an unhandled exception occurred while running the lookup plugin azure azcollection azure keyvault secret error was a original message can only concatenate str not nonetype to str can only concatenate str not nonetype to str to avoid this problem we can write the variables as parameters in the playbook but this is inconvenient this behavior seems also inconsistent with other components of the collection | 0 |
582,625 | 17,366,189,259 | IssuesEvent | 2021-07-30 07:38:43 | ChadGoymer/githapi | https://api.github.com/repos/ChadGoymer/githapi | closed | Use {fs} for paths, directories and files | effort:3 feature priority:2 | ## Description
{fs} is much more reliable across OS's and file storage technologies. Replace all base functions for paths, directories and files with {fs} functions.
## Proposed Solution
Replace the following functions:
- [x] `file.path()` with `fs::path()` (unless it is being used for a URL)
- [x] `normalizePath()` with `fs::path_expand()`
- [x] `dirname()` with `fs::path_dir()` (unless it is being used for a URL)
- [x] `basename()` with `fs::path_file()`
- [x] `dir.exists()` with `fs::dir_exists()`
- [x] `file.exists()` with `fs::file_exists()`
- [x] `list.files()` with `fs::dir_ls(type = "file")`
- [x] `list.dirs()` with `fs::dir_ls(type = "directory")`
- [x] `dir.create()` with `fs::dir_create()`
- [x] `file.create()` with `fs::file_create()`
- [x] `dir.copy()` with `fs::dir_copy()`
- [x] `file.copy()` with `fs::file_copy()`
- [x] `dir.delete()` with `fs::dir_delete()`
- [x] `unlink()` with `fs::dir_delete()` or `fs::file_delete()`
- [x] `file.delete()` with `fs::file_delete()`
- [x] `tempfile()` with `fs::file_temp()`
- [x] `tempdir()` with `fs::file_temp()`
| 1.0 | Use {fs} for paths, directories and files - ## Description
{fs} is much more reliable across OS's and file storage technologies. Replace all base functions for paths, directories and files with {fs} functions.
## Proposed Solution
Replace the following functions:
- [x] `file.path()` with `fs::path()` (unless it is being used for a URL)
- [x] `normalizePath()` with `fs::path_expand()`
- [x] `dirname()` with `fs::path_dir()` (unless it is being used for a URL)
- [x] `basename()` with `fs::path_file()`
- [x] `dir.exists()` with `fs::dir_exists()`
- [x] `file.exists()` with `fs::file_exists()`
- [x] `list.files()` with `fs::dir_ls(type = "file")`
- [x] `list.dirs()` with `fs::dir_ls(type = "directory")`
- [x] `dir.create()` with `fs::dir_create()`
- [x] `file.create()` with `fs::file_create()`
- [x] `dir.copy()` with `fs::dir_copy()`
- [x] `file.copy()` with `fs::file_copy()`
- [x] `dir.delete()` with `fs::dir_delete()`
- [x] `unlink()` with `fs::dir_delete()` or `fs::file_delete()`
- [x] `file.delete()` with `fs::file_delete()`
- [x] `tempfile()` with `fs::file_temp()`
- [x] `tempdir()` with `fs::file_temp()`
| non_main | use fs for paths directories and files description fs is much more reliable across os s and file storage technologies replace all base functions for paths directories and files with fs functions proposed solution replace the following functions file path with fs path unless it is being used for a url normalizepath with fs path expand dirname with fs path dir unless it is being used for a url basename with fs path file dir exists with fs dir exists file exists with fs file exists list files with fs dir ls type file list dirs with fs dir ls type directory dir create with fs dir create file create with fs file create dir copy with fs dir copy file copy with fs file copy dir delete with fs dir delete unlink with fs dir delete or fs file delete file delete with fs file delete tempfile with fs file temp tempdir with fs file temp | 0 |
1,670 | 6,574,082,601 | IssuesEvent | 2017-09-11 11:24:25 | ansible/ansible-modules-core | https://api.github.com/repos/ansible/ansible-modules-core | closed | service/systemd module cannot enable new ("missing") services | affects_2.2 bug_report waiting_on_maintainer | ##### ISSUE TYPE
- Bug Report (regression)
##### COMPONENT NAME
module `service`/`systemd`
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0.0
config file = /home/lukas/.ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
nothing relevant there
##### OS / ENVIRONMENT
both Debian stretch/sid
##### SUMMARY
I used to use the `service` module to enable (i.e. add) new services (i.e. unit files) with Ansible 2.1. With 2.2, the corresponding Playbook fails with "Could not find the requested service \\"'/tmp/dummy.service'\\"".
##### STEPS TO REPRODUCE
run the Playbook:
```
- name: add a new unit file
hosts: localhost
become: yes
vars:
f: /tmp/dummy.service
tasks:
- blockinfile:
dest: "{{ f }}"
create: yes
block: |
[Service]
ExecStart=echo
Type=oneshot
- service: name="{{ f }}" enabled=yes
```
##### EXPECTED RESULTS
Service gets symlinked and enabled accordingly (like in 2.1).
##### ACTUAL RESULTS
```
$ ansible-playbook /tmp/playbook.yml -Kvvvv
Using /home/lukas/.ansible.cfg as config file
SUDO password:
Loading callback plugin default of type stdout, v2.0 from /usr/lib/python2.7/dist-packages/ansible/plugins/callback/__init__.pyc
PLAYBOOK: playbook.yml *********************************************************
1 plays in /tmp/playbook.yml
PLAY [add a new unit file] *****************************************************
TASK [setup] *******************************************************************
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/core/system/setup.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: lukas
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=olalnnvscferlfdemtugfdgjqrneqipt] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-olalnnvscferlfdemtugfdgjqrneqipt; /usr/bin/python'"'"' && sleep 0'
ok: [localhost]
TASK [blockinfile] *************************************************************
task path: /tmp/playbook.yml:10
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/extras/files/blockinfile.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: lukas
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=jhuyttrpjgbqflakdvmfhpjossmgctnj] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-jhuyttrpjgbqflakdvmfhpjossmgctnj; /usr/bin/python'"'"' && sleep 0'
ok: [localhost] => {
"changed": false,
"invocation": {
"module_args": {
"backup": false,
"block": "[Service]\nExecStart=echo\nType=oneshot\n",
"content": null,
"create": true,
"delimiter": null,
"dest": "/tmp/dummy.service",
"directory_mode": null,
"follow": false,
"force": null,
"group": null,
"insertafter": null,
"insertbefore": null,
"marker": "# {mark} ANSIBLE MANAGED BLOCK",
"mode": null,
"owner": null,
"regexp": null,
"remote_src": null,
"selevel": null,
"serole": null,
"setype": null,
"seuser": null,
"src": null,
"state": "present",
"unsafe_writes": null,
"validate": null
},
"module_name": "blockinfile"
},
"msg": ""
}
TASK [service] *****************************************************************
task path: /tmp/playbook.yml:18
Running systemd
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/core/system/systemd.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: lukas
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=jihnhcdcrlgqulqxcpjdplduksltuceb] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-jihnhcdcrlgqulqxcpjdplduksltuceb; /usr/bin/python'"'"' && sleep 0'
fatal: [localhost]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_args": {
"daemon_reload": false,
"enabled": true,
"masked": null,
"name": "/tmp/dummy.service",
"state": null,
"user": false
}
},
"msg": "Could not find the requested service \"'/tmp/dummy.service'\": "
}
PLAY RECAP *********************************************************************
localhost : ok=2 changed=0 unreachable=0 failed=1
```
##### WORKAROUND
```
- register: systemctl_result
command: systemctl enable /tmp/dummy.service
changed_when: systemctl_result.stdout != ""
``` | True | service/systemd module cannot enable new ("missing") services - ##### ISSUE TYPE
- Bug Report (regression)
##### COMPONENT NAME
module `service`/`systemd`
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.2.0.0
config file = /home/lukas/.ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
nothing relevant there
##### OS / ENVIRONMENT
both Debian stretch/sid
##### SUMMARY
I used to use the `service` module to enable (i.e. add) new services (i.e. unit files) with Ansible 2.1. With 2.2, the corresponding Playbook fails with "Could not find the requested service \\"'/tmp/dummy.service'\\"".
##### STEPS TO REPRODUCE
run the Playbook:
```
- name: add a new unit file
hosts: localhost
become: yes
vars:
f: /tmp/dummy.service
tasks:
- blockinfile:
dest: "{{ f }}"
create: yes
block: |
[Service]
ExecStart=echo
Type=oneshot
- service: name="{{ f }}" enabled=yes
```
##### EXPECTED RESULTS
Service gets symlinked and enabled accordingly (like in 2.1).
##### ACTUAL RESULTS
```
$ ansible-playbook /tmp/playbook.yml -Kvvvv
Using /home/lukas/.ansible.cfg as config file
SUDO password:
Loading callback plugin default of type stdout, v2.0 from /usr/lib/python2.7/dist-packages/ansible/plugins/callback/__init__.pyc
PLAYBOOK: playbook.yml *********************************************************
1 plays in /tmp/playbook.yml
PLAY [add a new unit file] *****************************************************
TASK [setup] *******************************************************************
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/core/system/setup.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: lukas
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=olalnnvscferlfdemtugfdgjqrneqipt] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-olalnnvscferlfdemtugfdgjqrneqipt; /usr/bin/python'"'"' && sleep 0'
ok: [localhost]
TASK [blockinfile] *************************************************************
task path: /tmp/playbook.yml:10
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/extras/files/blockinfile.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: lukas
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=jhuyttrpjgbqflakdvmfhpjossmgctnj] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-jhuyttrpjgbqflakdvmfhpjossmgctnj; /usr/bin/python'"'"' && sleep 0'
ok: [localhost] => {
"changed": false,
"invocation": {
"module_args": {
"backup": false,
"block": "[Service]\nExecStart=echo\nType=oneshot\n",
"content": null,
"create": true,
"delimiter": null,
"dest": "/tmp/dummy.service",
"directory_mode": null,
"follow": false,
"force": null,
"group": null,
"insertafter": null,
"insertbefore": null,
"marker": "# {mark} ANSIBLE MANAGED BLOCK",
"mode": null,
"owner": null,
"regexp": null,
"remote_src": null,
"selevel": null,
"serole": null,
"setype": null,
"seuser": null,
"src": null,
"state": "present",
"unsafe_writes": null,
"validate": null
},
"module_name": "blockinfile"
},
"msg": ""
}
TASK [service] *****************************************************************
task path: /tmp/playbook.yml:18
Running systemd
Using module file /usr/lib/python2.7/dist-packages/ansible/modules/core/system/systemd.py
<127.0.0.1> ESTABLISH LOCAL CONNECTION FOR USER: lukas
<127.0.0.1> EXEC /bin/sh -c 'sudo -H -S -p "[sudo via ansible, key=jihnhcdcrlgqulqxcpjdplduksltuceb] password: " -u root /bin/sh -c '"'"'echo BECOME-SUCCESS-jihnhcdcrlgqulqxcpjdplduksltuceb; /usr/bin/python'"'"' && sleep 0'
fatal: [localhost]: FAILED! => {
"changed": false,
"failed": true,
"invocation": {
"module_args": {
"daemon_reload": false,
"enabled": true,
"masked": null,
"name": "/tmp/dummy.service",
"state": null,
"user": false
}
},
"msg": "Could not find the requested service \"'/tmp/dummy.service'\": "
}
PLAY RECAP *********************************************************************
localhost : ok=2 changed=0 unreachable=0 failed=1
```
##### WORKAROUND
```
- register: systemctl_result
command: systemctl enable /tmp/dummy.service
changed_when: systemctl_result.stdout != ""
``` | main | service systemd module cannot enable new missing services issue type bug report regression component name module service systemd ansible version ansible config file home lukas ansible cfg configured module search path default w o overrides configuration nothing relevant there os environment both debian stretch sid summary i used to use the service module to enable i e add new services i e unit files with ansible with the corresponding playbook fails with could not find the requested service tmp dummy service steps to reproduce run the playbook name add a new unit file hosts localhost become yes vars f tmp dummy service tasks blockinfile dest f create yes block execstart echo type oneshot service name f enabled yes expected results service gets symlinked and enabled accordingly like in actual results ansible playbook tmp playbook yml kvvvv using home lukas ansible cfg as config file sudo password loading callback plugin default of type stdout from usr lib dist packages ansible plugins callback init pyc playbook playbook yml plays in tmp playbook yml play task using module file usr lib dist packages ansible modules core system setup py establish local connection for user lukas exec bin sh c sudo h s p password u root bin sh c echo become success olalnnvscferlfdemtugfdgjqrneqipt usr bin python sleep ok task task path tmp playbook yml using module file usr lib dist packages ansible modules extras files blockinfile py establish local connection for user lukas exec bin sh c sudo h s p password u root bin sh c echo become success jhuyttrpjgbqflakdvmfhpjossmgctnj usr bin python sleep ok changed false invocation module args backup false block nexecstart echo ntype oneshot n content null create true delimiter null dest tmp dummy service directory mode null follow false force null group null insertafter null insertbefore null marker mark ansible managed block mode null owner null regexp null remote src null selevel null serole null setype null seuser null src null state present unsafe writes null validate null module name blockinfile msg task task path tmp playbook yml running systemd using module file usr lib dist packages ansible modules core system systemd py establish local connection for user lukas exec bin sh c sudo h s p password u root bin sh c echo become success jihnhcdcrlgqulqxcpjdplduksltuceb usr bin python sleep fatal failed changed false failed true invocation module args daemon reload false enabled true masked null name tmp dummy service state null user false msg could not find the requested service tmp dummy service play recap localhost ok changed unreachable failed workaround register systemctl result command systemctl enable tmp dummy service changed when systemctl result stdout | 1 |
79,744 | 23,033,246,288 | IssuesEvent | 2022-07-22 15:49:49 | google-coral/edgetpu | https://api.github.com/repos/google-coral/edgetpu | closed | ValueError: Failed to load delegate from libedgetpu.so.1.0 on coral usb tpu | type:build/install subtype:ubuntu/linux Hardware:USB Accelerator | ### Description
im in ubuntu 22.04 LTS (GNU/Linux 5.15.0-39-generic x86_64), docker Docker version 20.10.14, build a224086349 and python3 3.10.4-0ubuntu2
run lsusb with the result Bus 001 Device 002: ID 1a6e:089a Global Unichip Corp.
there is no way to initialize usb acelerator
i run in docker frigate and get
Process detector:coral:
[2022-07-13 11:54:51] frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
delegate = Delegate(library, options)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in init
raise ValueError(capture.message)
ValueError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector
object_detector = LocalObjectDetector(
File "/opt/frigate/frigate/edgetpu.py", line 44, in init
edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
raise ValueError('Failed to load delegate from {}\n{}'.format(
ValueError: Failed to load delegate from libedgetpu.so.1.0
im in ubuntu 22.04 LTS (GNU/Linux 5.15.0-39-generic x86_64), docker Docker version 20.10.14, build a224086349 and python3 3.10.4-0ubuntu2
can you please help me?
<details><summary>Click to expand!</summary>
### Issue Type
Build/Install
### Operating System
Linux
### Coral Device
USB Accelerator
### Other Devices
_No response_
### Programming Language
_No response_
### Relevant Log Output
```shell
Process detector:coral:
[2022-07-13 18:16:22] frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
delegate = Delegate(library, options)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in init
raise ValueError(capture.message)
ValueError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector
object_detector = LocalObjectDetector(
File "/opt/frigate/frigate/edgetpu.py", line 44, in init
edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
raise ValueError('Failed to load delegate from {}\n{}'.format(
ValueError: Failed to load delegate from libedgetpu.so.1.0
```
</details> | 1.0 | ValueError: Failed to load delegate from libedgetpu.so.1.0 on coral usb tpu - ### Description
im in ubuntu 22.04 LTS (GNU/Linux 5.15.0-39-generic x86_64), docker Docker version 20.10.14, build a224086349 and python3 3.10.4-0ubuntu2
run lsusb with the result Bus 001 Device 002: ID 1a6e:089a Global Unichip Corp.
there is no way to initialize usb acelerator
i run in docker frigate and get
Process detector:coral:
[2022-07-13 11:54:51] frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
delegate = Delegate(library, options)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in init
raise ValueError(capture.message)
ValueError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector
object_detector = LocalObjectDetector(
File "/opt/frigate/frigate/edgetpu.py", line 44, in init
edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
raise ValueError('Failed to load delegate from {}\n{}'.format(
ValueError: Failed to load delegate from libedgetpu.so.1.0
im in ubuntu 22.04 LTS (GNU/Linux 5.15.0-39-generic x86_64), docker Docker version 20.10.14, build a224086349 and python3 3.10.4-0ubuntu2
can you please help me?
<details><summary>Click to expand!</summary>
### Issue Type
Build/Install
### Operating System
Linux
### Coral Device
USB Accelerator
### Other Devices
_No response_
### Programming Language
_No response_
### Relevant Log Output
```shell
Process detector:coral:
[2022-07-13 18:16:22] frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
delegate = Delegate(library, options)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in init
raise ValueError(capture.message)
ValueError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/opt/frigate/frigate/edgetpu.py", line 136, in run_detector
object_detector = LocalObjectDetector(
File "/opt/frigate/frigate/edgetpu.py", line 44, in init
edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
raise ValueError('Failed to load delegate from {}\n{}'.format(
ValueError: Failed to load delegate from libedgetpu.so.1.0
```
</details> | non_main | valueerror failed to load delegate from libedgetpu so on coral usb tpu description im in ubuntu lts gnu linux generic docker docker version build and run lsusb with the result bus device id global unichip corp there is no way to initialize usb acelerator i run in docker frigate and get process detector coral frigate edgetpu error no edgetpu was detected if you do not have a coral device yet you must configure cpu detectors traceback most recent call last file usr lib dist packages tflite runtime interpreter py line in load delegate delegate delegate library options file usr lib dist packages tflite runtime interpreter py line in init raise valueerror capture message valueerror during handling of the above exception another exception occurred traceback most recent call last file usr lib multiprocessing process py line in bootstrap self run file usr lib multiprocessing process py line in run self target self args self kwargs file opt frigate frigate edgetpu py line in run detector object detector localobjectdetector file opt frigate frigate edgetpu py line in init edge tpu delegate load delegate libedgetpu so device config file usr lib dist packages tflite runtime interpreter py line in load delegate raise valueerror failed to load delegate from n format valueerror failed to load delegate from libedgetpu so im in ubuntu lts gnu linux generic docker docker version build and can you please help me click to expand issue type build install operating system linux coral device usb accelerator other devices no response programming language no response relevant log output shell process detector coral frigate edgetpu error no edgetpu was detected if you do not have a coral device yet you must configure cpu detectors traceback most recent call last file usr lib dist packages tflite runtime interpreter py line in load delegate delegate delegate library options file usr lib dist packages tflite runtime interpreter py line in init raise valueerror capture message valueerror during handling of the above exception another exception occurred traceback most recent call last file usr lib multiprocessing process py line in bootstrap self run file usr lib multiprocessing process py line in run self target self args self kwargs file opt frigate frigate edgetpu py line in run detector object detector localobjectdetector file opt frigate frigate edgetpu py line in init edge tpu delegate load delegate libedgetpu so device config file usr lib dist packages tflite runtime interpreter py line in load delegate raise valueerror failed to load delegate from n format valueerror failed to load delegate from libedgetpu so | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.