Synthesis failed for IAMCredentials

Hello! Autosynth couldn't regenerate IAMCredentials. :broken_heart:
Here's the output from running synth.py:
2020-06-06 06:05:07,146 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-06 06:05:07,969 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-06 06:05:07,971 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-06 06:05:07,974 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-06 06:05:07,977 autosynth [DEBUG] > Running: git config push.default simple
2020-06-06 06:05:07,979 autosynth [DEBUG] > Running: git branch -f autosynth-iamcredentials
2020-06-06 06:05:07,982 autosynth [DEBUG] > Running: git checkout autosynth-iamcredentials
Switched to branch 'autosynth-iamcredentials'
2020-06-06 06:05:08,215 autosynth [INFO] > Running synthtool
2020-06-06 06:05:08,215 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/iam_credentials/synth.metadata', 'synth.py', '--']
2020-06-06 06:05:08,217 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/iam_credentials/synth.metadata synth.py -- IAMCredentials
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-06 06:05:08,441 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-iamcredentials
nothing to commit, working tree clean
2020-06-06 06:05:10,303 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpjj3n508f/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh IAMCredentials
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpjj3n508f/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh IAMCredentials
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

13:05:42.134 [info]  FETCHING: https://iamcredentials.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:05:42.249 [info]  FOUND: https://iamcredentials.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200501, new=20200529, generating=true
Creating leading directories
Writing GenerateAccessTokenRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_access_token_request.ex.
Writing GenerateAccessTokenResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_access_token_response.ex.
Writing GenerateIdTokenRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_id_token_request.ex.
Writing GenerateIdTokenResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_id_token_response.ex.
Writing SignBlobRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_blob_request.ex.
Writing SignBlobResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_blob_response.ex.
Writing SignJwtRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_jwt_request.ex.
Writing SignJwtResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_jwt_response.ex.
Writing Projects to clients/iam_credentials/lib/google_api/iam_credentials/v1/api/projects.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:05:42.611 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-06 06:05:45,640 synthtool [DEBUG] > Wrote metadata to clients/iam_credentials/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/iam_credentials/synth.metadata.
2020-06-06 06:05:45,666 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating IAMCredentials. :sob:
Here's the output from running synth.py:
2020-06-07 05:58:31,353 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-07 05:58:32,536 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-07 05:58:32,539 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-07 05:58:32,542 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-07 05:58:32,544 autosynth [DEBUG] > Running: git config push.default simple
2020-06-07 05:58:32,547 autosynth [DEBUG] > Running: git branch -f autosynth-iamcredentials
2020-06-07 05:58:32,550 autosynth [DEBUG] > Running: git checkout autosynth-iamcredentials
Switched to branch 'autosynth-iamcredentials'
2020-06-07 05:58:32,782 autosynth [INFO] > Running synthtool
2020-06-07 05:58:32,782 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/iam_credentials/synth.metadata', 'synth.py', '--']
2020-06-07 05:58:32,785 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/iam_credentials/synth.metadata synth.py -- IAMCredentials
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-07 05:58:33,007 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-iamcredentials
nothing to commit, working tree clean
2020-06-07 05:58:34,939 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp5mrgjsde/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh IAMCredentials
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp5mrgjsde/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh IAMCredentials
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:59:04.771 [info]  FETCHING: https://iamcredentials.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:59:04.892 [info]  FOUND: https://iamcredentials.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200501, new=20200529, generating=true
Creating leading directories
Writing GenerateAccessTokenRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_access_token_request.ex.
Writing GenerateAccessTokenResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_access_token_response.ex.
Writing GenerateIdTokenRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_id_token_request.ex.
Writing GenerateIdTokenResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_id_token_response.ex.
Writing SignBlobRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_blob_request.ex.
Writing SignBlobResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_blob_response.ex.
Writing SignJwtRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_jwt_request.ex.
Writing SignJwtResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_jwt_response.ex.
Writing Projects to clients/iam_credentials/lib/google_api/iam_credentials/v1/api/projects.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:59:05.254 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-07 05:59:08,402 synthtool [DEBUG] > Wrote metadata to clients/iam_credentials/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/iam_credentials/synth.metadata.
2020-06-07 05:59:08,426 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating IAMCredentials. :sob:
Here's the output from running synth.py:
2020-06-08 05:59:03,084 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-08 05:59:04,286 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-08 05:59:04,289 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-08 05:59:04,292 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-08 05:59:04,295 autosynth [DEBUG] > Running: git config push.default simple
2020-06-08 05:59:04,298 autosynth [DEBUG] > Running: git branch -f autosynth-iamcredentials
2020-06-08 05:59:04,302 autosynth [DEBUG] > Running: git checkout autosynth-iamcredentials
Switched to branch 'autosynth-iamcredentials'
2020-06-08 05:59:04,546 autosynth [INFO] > Running synthtool
2020-06-08 05:59:04,546 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/iam_credentials/synth.metadata', 'synth.py', '--']
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api2020-06-08 05:59:04,549 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/iam_credentials/synth.metadata synth.py -- IAMCredentials
: Is a directory
2020-06-08 05:59:04,758 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-iamcredentials
nothing to commit, working tree clean
2020-06-08 05:59:06,287 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp5na7zwxz/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh IAMCredentials
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp5na7zwxz/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh IAMCredentials
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:59:38.115 [info]  FETCHING: https://iamcredentials.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:59:38.233 [info]  FOUND: https://iamcredentials.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200501, new=20200529, generating=true
Creating leading directories
Writing GenerateAccessTokenRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_access_token_request.ex.
Writing GenerateAccessTokenResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_access_token_response.ex.
Writing GenerateIdTokenRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_id_token_request.ex.
Writing GenerateIdTokenResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/generate_id_token_response.ex.
Writing SignBlobRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_blob_request.ex.
Writing SignBlobResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_blob_response.ex.
Writing SignJwtRequest to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_jwt_request.ex.
Writing SignJwtResponse to clients/iam_credentials/lib/google_api/iam_credentials/v1/model/sign_jwt_response.ex.
Writing Projects to clients/iam_credentials/lib/google_api/iam_credentials/v1/api/projects.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:59:38.596 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-08 05:59:41,151 synthtool [DEBUG] > Wrote metadata to clients/iam_credentials/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/iam_credentials/synth.metadata.
2020-06-08 05:59:41,178 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Format XML with prettier

After looking at a few different XML parsers, I think this integration from prettier seems to be the best.

I looked into the Red Hat one, which is a popular VSCode extension, but there does not seem to be a way to get the formatting from it as a command line tool or in a GitHub action.
I also looked into xmllint but its formatting wasn't that much of an improvement from what we have.
Prettier seems to do the best job at formatting, and it's nice and easy to run from the command line. It will be integrated into the CI/CD easily. If this formatting is okay, I will update this PR to update the actions.

Will look into CI failing. Regardless, this PR is fine to review as it's just about if you guys are fine with this formatting style!

Since some of the MSBuild stuff is whitespace sensitive the latest commit does the formatting in two passes
prettier --write '**/*.{props,csproj,targets}' --plugin=@prettier/plugin-xml --ignore-path .prettierignore
prettier --write 'tools/**/*.{props,targets}' --plugin=@prettier/plugin-xml --config tools/.prettierrc --ignore-path /dev/null

Where the pass over the tools directory uses a config file that removes the whitespace formatting. Not ideal but should fix the builds.

It would be good to open the projects with Visual Studio (_not VS code) to make sure VS does not immediately reformat all the project files.

@bernardnormier Just opened the IceRpc.sln on my mac with visual studio and nothing changed! I have 0 familiarity with Visual Studio so im not sure if this is sufficient to show that the formatting is preserved. @pepone could you verify if Visual Studio leaves the files with the new formatting?

could you verify if Visual Studio leaves the files with the new formatting?

Yes, formatting remains the same after opening the solution in Visual Studio 2022 on Windows.


Move to the center button

not sure the purpose of this…  I initially thought it moved your blocks together in a central part of the editor, but if my program has a bunch of different blocks spread out all over my editor, it just moves my screen to the middle.  I think what would be more helpful to line up your blocks program to the top left (like what happens when you move from JavaScript back to blocks).
[enhancement]

This is a good idea. I was just looking into that today.
I think that would be possible, our current experience is a little jarred with where we place the blocks. Here are three scenarios where you end up with your blocks positioned in different parts of the screen:

Add a block, move it a little to the right (The blocks position is at X, 0)
Reload the page, the block first appears a little to the left of its position then snaps to the right position. (I believe this is fixed with #692)
Go to JS and back to Blocks. The block shows in the top left corner (even though its position is x,0)
Move the workspace around, so that the block is in the middle. In this case the workspace has moved, going to JS or reloading the page, that translation is lost.  (I think this is Okay)

It is a blockly feature, we should measure if it is being used before rebuilding it.

No longer relevant as we removed the Blockly zoom buttons.


CMake + Ninja not working?

Hi. I found that blueprint engine does not work when building with Ninja Generator on CMake though it can be successfully compiled. (Both of my project and GainPlugin Example.) Update: sorry, I confirmed GainPlugin works properly.
When I inspected with a debugger,  registerNativeRenderingHooks function was not called on an event loop, which was normally called when built with Unix Makefiles. It finally causes an error because of the missing window.__BlueprintNative__ variable.
ReferenceError: identifier '__BlueprintNative__' undefined
  at [anon] (../Dependencies/blueprint/blueprint/duktape/src-noline/duktape.c:81729) internal
  at eval (eval:1) preventsyield

I could not find a specific reason but just for a bug report...
Environments:

macOS Catalina 10.15.5
Xcode 11.4.1
cmake version 3.18.3(installed via homebrew)
ninja 1.10.1(installed via homebrew)
blueprint 5604b941e39a3e6a13633023e5b823fdd8b1269d

I found a problem that __FILE__ returns absolute path when using Unix Makefiles but Ninja returns a relative path to project-root like ../examples/GainPlugin/PluginProcessor.cpp.
juce::File's constructor expects an absolute path, so maybe when used with cmake+Ninja, it seems to nice to add a preprocessor definition
target_compile_definition(your_project PRIVATE JS_MAINFILE_PATH="path/to/main.js")

And in cpp files,
-   File sourceDir = File(__FILE__).getParentDirectory();
-   File bundle = sourceDir.getChildFile("jsui/build/js/main.js");
+  #ifndef JS_MAINFILE_PATH
+    #define JS_MAINFILE_PATH  File(__FILE__).getParentDirectory().getChildFile("jsui/build/js/main.js");
+  #endif
+   File bundle(JS_MAINFILE_PATH);

Wow, interesting, thanks @tomoyanonymous! I wonder if we should be using something more standardized than __FILE__? I'd prefer to avoid preprocessor defs if we can, but might be a necessary move

I found a more clear explanation.
https://github.com/approvals/ApprovalTests.cpp/issues/74#issuecomment-572207017

On all platforms, the Ninja program:

Gives the compiler relative paths, if the build tree is inside the source tree
Gives the compiler absolute paths if build tree is outside the source tree

I think no standardized way to get source file path at least language level. In C++20,  std::source_location::current().file_name() returns a name of source file but still not a full path.
I know it is better to avoid preprocessor definitions if we can, but __FILE__ is also a preprocessor definition which compiler and build system define.
How about like this, it can tell that FILE is not an absolute path and also no preprocessor definition for source directory given to users at compile-time.

File source;
#ifndef PROJECT_ROOT_PATH
  static constexpr char *bar = (char *)__FILE__;
  static_assert(bar[0] == '/', "__FILE__ is not absolute path. Please specify project root path to preprocessor definition PROJECT_ROOT_PATH .");
  sourcedir  File(__FILE__).getParentDirectory();
  #else
  sourcedir = PROJECT_ROOT_PATH;
#endif
  File bundle = sourceDir.getChildFile("jsui/build/js/main.js");

Hi, just wanted to confirm that I got the same issue on Windows 10 when building with Ninja. I used @tomoyanonymous workaround to fix it and it worked.

Hey @stfufane @tomoyanonymous check out #197.
Rather than trying to do a preprocessor dance around the inconsitentices in FILE, I added a small workaround for GainPlugin and updated the docs so that new users avoid FILE in the first place. Let me know what you think

Closed with #197. Thanks all!


Little update

Update readme creating corresponding signatures between text and solutions
Little text and class updates

Nice :+1:


addition of FAQ section details

FAQ section needs details to be filled capturing the need for the site

thanks
On Wed, 16 Oct 2024 at 21:25, Najam Ali Abbas @.***>
wrote:

it is assigned ;)
—
Reply to this email directly, view it on GitHub
https://github.com/Ctoic/Lisbook/issues/106#issuecomment-2417247959, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3RAQLAF4AZ7N5Y6DRE5ZRLZ32D65AVCNFSM6AAAAABQBYDMTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJXGI2DOOJVHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Name of the controller: CLIC or FLIC?

Here I'm capturing the discussion in the TG meeting 2020/9/8:
It was suggested that CLIC and CLINT are too close in name and sound.
The CLINT name has propagated and is being used widely for the original scheme, despite not having a clear definition anywhere.
It is proposed we should therefore change the name of CLIC to something that is further lexically from CLINT.  One proposal is FLIC for "Fast Local Interrupt Controller".

CLIC name has been around for a while, and I don't think it really needs changing, and that CLINT and CLIC are reasonably distinguishable.

The main problem is that these 2 names are NOT self-explanatory. Also, by having identical words and meaning, they are too confusing for millions of new readers in the future:
Core Local INTerruptor (for CLINT)
Core Local Interrupt Controller (for CLIC)
Therefore, before ratification, we better replace them with clear self-explanatory names to avoid confusion and misuse in the future.

I'm not eager to change, but a potential name for CLIC is CNIC, Core Nested Interrupt Controller.   That contains its biggest differentiation.

We're agreeing to sticking to CLIC as that's what we have been using.


No images.txt  on Search and tagged feature ?

There is not images.txt generated with search or tagged feature.

Because it's not implemented and thus also not available in the UI.
see #175.


[FLINK-29219][table]fix CREATE TABLE AS statement blocks SQL client's execution

What is the purpose of the change

fix CTAS statement blocks SQL client's execution

Brief change log
ContextResolvedTable objects are constructed manually and not obtained using CatalogManager.
Verifying this change

The change was verified manually by using sql-client.sh to execute the CTAS statement with table.dml-sync=false then the sql client was not blocked.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not documented)

Let's continue this work in https://github.com/apache/flink/pull/20869.

@Tartarus0zm close this pr?

@lsyldliu  ok, thanks for your work


feat: parallel limited time load of user META info

Now Public IP, ASN, Region, ... are loaded using separated helper daemon process
Data are shared using shared memory between two processes
we have a minimum wait time to let helper process complete, if not ,main
process will terminate assuming meta data cannot be found (No Internet or etc)

Now everything in get_meta is done in separated process to overcome lack of timeout in gethostbyname in some cases
call is made serially before trace
Also a privilege drop is done in separated process nobody and nogroup (this needs test in windows)

there is a rice condition that should be fixed. but it's a UX bug, so we are good for now and will take care of it later.
Thank you @RYNEQ and @bassosimone :heart: :hibiscus: :tada:


I am very sorry for what I did, but I don't want to let go of the current problems (I'm sorry🥲)

I want to adjust our understanding that what I did was against the rules, but my plan is that I see the growth of the Vtube industry in my country. But!! New Vtubers have limited financial resources, so I did this to reduce the over-reliance on the Apple ecosystem, so that new Vtubers have more spending options so that they don't have financial problems in the future. (This is something that I have never told anyone🥲)

You realize that you just notified every single person following this repo?
I have no clue what this is about, but this does not belong in the issues. If there is something Apple-related that bugs you, feel free to open a proper issue about it.

Please delete all the parts I posted so that the problem does not get worse in the future 🥲

I am not a moderator in the VTube Studio Discord, nor do I have any influence on moderation decisions. And, even if I did, this is not an appropriate way to contest those decisions, for the reasons Yuta said.


How to check the dataset's Image and GT are matched or not. (ex. # of images, name, ...)

should I just check the name of image and GT are matched or not ?

Yes. You can easily(?) compare the names by print(os.listdir()). File format(jpg, png) does not matter, but number of datas and name of datas should be matched.

If you think it is hard to match files, I'll make utils/match_data.py for correct DUTS Dataset. as soon as possible.

I think this part need take some time. May be you should make utils/match_data.py for convenience.
The DUT-TR-Image has 10553 jpg images, but DUT-TR-Mask has 10553 png images and 3 jpg images. This 3 jpg have same name with 3 png images in 10553 png images. So, I just delete these 3 jpg images in DUT-TR-Mask.
The DUT-TE-Image has 5019 jpg images, but DUT-TE-Mask has 5021 png images, which has 3 png mask image do not have the matched jpg images in DUT-TE-Image. So, I also delete these 3 png images in DUT-TE-Mask.
So DUT-TR  has 10553 image and matched mask, DUT-TE has 5019 images and matched mask, right?
(all the image name without suffix seems matched, right?)

Yes you are right. There are some over-datas

@Sucran I added arrange method to DUTSdataset class.


Future Deprecated Warnings when trying to evaluate Object Detector Model

Repro:
Follow the Introductory example here.
model.evaluate(test, "mean_average_precision_50") leads to:
venv/lib/python2.7/site-packages/numpy/core/fromnumeric.py:57: FutureWarning: 'argmax' is deprecated. Use 'idxmax' instead. The behavior of 'argmax' will be corrected to return the positional maximum in the future. Use 'series.values.argmax' to get the position of the maximum now.
  return getattr(obj, method)(*args, **kwds)

venv/lib/python2.7/site-packages/turicreate/toolkits/object_detector/_evaluation.py:56: DeprecationWarning:
.ix is deprecated. Please use
.loc for label based indexing or
.iloc for positional indexing

See the documentation here:
http://pandas.pydata.org/pandas-docs/stable/indexing.html#ix-indexer-is-deprecated
  if best_iou > iou_threshold and not gts.ix[best_gt_index, 'correct_%d' % th_index]:

venv/lib/python2.7/site-packages/turicreate/toolkits/object_detector/_evaluation.py:70: RuntimeWarning: invalid value encountered in true_divide
  recall = pad1(cum_tp / len(c_groundtruth), 0, 1)

venv/lib/python2.7/site-packages/turicreate/toolkits/object_detector/_evaluation.py:78: RuntimeWarning: invalid value encountered in greater
  ii = _np.where(rec_diff_th > 0)[0]

Fixed as of Turi Create 5.0b1 @gustavla

Yup, got fixed in these changes: 5b6e6cee9f761fce1f2a407f86571ab508797522


[Improvement-4480][API] change method checkAdmin to isNotAdmin

Tips

Thanks very much for contributing to Apache DolphinScheduler.
Please review https://dolphinscheduler.apache.org/en-us/community/index.html before opening a pull request.

What is the purpose of the pull request
issue #4480
for the better understand of method 'checkAdmin' in class BaseService.
Brief change log

Modify the method's name 'checkAdmin' to 'isNotAdmin' in class BaseService
Where we use this method

Verify this pull request
This pull request is code cleanup without any test coverage.

Manually verified the change by testing locally.

Codecov Report

Merging #4483 (40b0dfb) into dev (91dfe09) will decrease coverage by 0.00%.
The diff coverage is 51.72%.

@@             Coverage Diff              @@
##                dev    #4483      +/-   ##
============================================
- Coverage     43.58%   43.57%   -0.01%
+ Complexity     3201     3200       -1
============================================
  Files           471      471
  Lines         21765    21765
  Branches       2640     2640
============================================
- Hits           9486     9484       -2
- Misses        11376    11378       +2
  Partials        903      903

Impacted Files
Coverage Δ
Complexity Δ

...ache/dolphinscheduler/api/service/BaseService.java
87.87% <ø> (ø)
18.00 <0.00> (ø)

...che/dolphinscheduler/api/service/QueueService.java
75.51% <0.00%> (ø)
21.00 <0.00> (ø)

...lphinscheduler/api/service/WorkerGroupService.java
79.03% <0.00%> (ø)
8.00 <0.00> (ø)

...nscheduler/api/service/impl/TenantServiceImpl.java
67.82% <0.00%> (ø)
18.00 <0.00> (ø)

...scheduler/api/service/impl/ProjectServiceImpl.java
87.86% <66.66%> (ø)
42.00 <0.00> (ø)

...dolphinscheduler/api/service/ResourcesService.java
48.56% <72.72%> (ø)
66.00 <0.00> (ø)

...olphinscheduler/api/service/AlertGroupService.java
88.37% <83.33%> (ø)
16.00 <0.00> (ø)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-4.88%)
7.00% <0.00%> (-1.00%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 91dfe09...40b0dfb. Read the comment docs.

Codecov Report

Merging #4483 (40b0dfb) into dev (91dfe09) will decrease coverage by 0.00%.
The diff coverage is 51.72%.

@@             Coverage Diff              @@
##                dev    #4483      +/-   ##
============================================
- Coverage     43.58%   43.57%   -0.01%
+ Complexity     3201     3200       -1
============================================
  Files           471      471
  Lines         21765    21765
  Branches       2640     2640
============================================
- Hits           9486     9484       -2
- Misses        11376    11378       +2
  Partials        903      903

Impacted Files
Coverage Δ
Complexity Δ

...ache/dolphinscheduler/api/service/BaseService.java
87.87% <ø> (ø)
18.00 <0.00> (ø)

...che/dolphinscheduler/api/service/QueueService.java
75.51% <0.00%> (ø)
21.00 <0.00> (ø)

...lphinscheduler/api/service/WorkerGroupService.java
79.03% <0.00%> (ø)
8.00 <0.00> (ø)

...nscheduler/api/service/impl/TenantServiceImpl.java
67.82% <0.00%> (ø)
18.00 <0.00> (ø)

...scheduler/api/service/impl/ProjectServiceImpl.java
87.86% <66.66%> (ø)
42.00 <0.00> (ø)

...dolphinscheduler/api/service/ResourcesService.java
48.56% <72.72%> (ø)
66.00 <0.00> (ø)

...olphinscheduler/api/service/AlertGroupService.java
88.37% <83.33%> (ø)
16.00 <0.00> (ø)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-4.88%)
7.00% <0.00%> (-1.00%)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 91dfe09...40b0dfb. Read the comment docs.


Add transpiler support for array index overloading

It would be great if we could reduce long winded property access statements like myObj.getArrayObj().getItem(2).getMyPropValue() down to their native equivalent like myObj.arrayObj[2].myPropValue; to do this requires that the Qooxdoo property mechanism is updated to use Object.defineProperty so that getters and setters can be implicitly defined on class prototypes, but there is no mechanism in ES5 which will allow array indexes to be overridden.
It may be possible to override array accessors with the help of transpilation, eg if myObj[0] is transpiled to myObj.getItem(0) and there is a polyfill of Array.prototype.getItem=function(index){return this[index]; }.  Replacing every array access with a method call would cause a slow down in performance, but by using the prototype chain the javascript interpretter would (hopefully) be able to efficiently determine the function to call and inline the array access where appropriate.
Note that implementing ES6 Proxy in ES5 is possible via a similar mechanism but has been shown to be very slow because Proxy allows you to intercept every property access, so the plugin has to change every get or set with a function call (eg myObj.x=1 becomes globalSetter(myObj, “x”, 1)) - see babel-plugin-proxy
This solution would mean that referencing anything with [...] would have to be intercepted, eg:
var myObj = { a: 1 };
myObj["a"] = 2;

would transpile as:
var myObj = { a: 1 };
myObj.getItem("a") = 2;

so our polyfill would have to be on Object:
Object.prototype.getItem = function(index){
  return this[index];
};

This is just an idea at present, it may not actually be possible, or possible but just too slow.

This should be embedded in the general modernization of the property system and databinding, using Proxies. Here is an example how to implement negative array indexes with proxies. Fun stuff, but a complex project!

@derrell said in gitter:
I started playing with creating ES6 class-compatible qx classes. I have a general framework. The biggest problem is that you can't use qx style constructor or member functions, and still use super, because at definition time, they are function objects, not class members.
let GLOBAL = global || window;
let qx = { Class : { define : define } };
qx.Class.define(
"A",
{
construct : function(junk)
{
console.log(A constructor: junk=${junk});
},
members :
{
  foo : function()
  {
    console.log("foo in A");
  },

  bar : function()
  {
    console.log("bar in A");
  }
}

});
console.log(A= + A.toString());
qx.Class.define(
"B",
{
extends : A,
construct : function()
{
  //super("Hi there");
  console.log("B constructor");
},

members :
{
  foo : function()
  {
    //super();
    console.log("foo in B");
  }
}

});
console.log(B= + B.toString());
let a = new A("hello");
a.foo();
a.bar();
let b = new B();
b.foo();
b.bar();
//------------------------------------------------------------------------------
function define(name, config)
{
let             s;
let             clazz;
let             separator;
s =
[
return class ${name},
"{",
config.construct.toString().replace("function", "constructor"),
].join("\n");
s += "\n";
separator = "";
for (let member in config.members)
{
s +=
[
${member},
config.members[member].toString().replace("function",""),
${separator}
].join("");
s += "\n";
}
s += "}";
clazz = GLOBAL[name] = Function(s)();
Object.defineProperty(clazz, "name", { value : name });
if (config.extends)
{
let             base = config.extends;
Object.setPrototypeOf(clazz, base);
Object.setPrototypeOf(clazz.prototype, base.prototype);

}
}

@johnspackman said:
@derrell one of my wish list items was to transpile so that super() works on Qooxdoo classes; and this.base is implemented by calculating the actual function to call (ie this.base() becomes myPackage.myClass.prototype.myFunction.call(...)
and so we could consider a scheme where the compiler intercepts super()/this.base to work with your framework

@cboulanger said in gitter:
@derrell Can you explain why you would want to convert qooxdoo "classes" into ES6 classes? I thought the idea was to use ES6 classes to behave like qooxdoo "classes"?

@derrell said in gitter:
@cboulanger ES6 classes are almost syntactic sugar on top of prototype-based classes. The one real exception is super() which can't be fully emulated in ES5. (See, beginning at the paragraph above "Superclass property access" in https://medium.com/@robertgrosse/how-es6-classes-really-work-and-how-to-build-your-own-fd6085eb326a) Basing qooxdoo classes on real ES6 classes means that we would have the full ability of the language, including, likely, things that get added in the future. I see it as the forward-thinking way of implementing, rather than trying to emulate the future using features of the past (which may or may not be possible).

the down side of that could be that ES6 additions may not sit easily along side Qooxdoo features, or may be incompatible with Qooxdoo classes; it would also mean that we could be restricted in future in the language features that we want to add.
IMHO it would be cool if the Qooxdoo implementation is the reference implementation, and also make it interoperate with ES6 classes.  So you would be able to derive an ES6 class from a Qooxdoo class, and derive a Qooxdoo class from an ES6 class.
The super() implementation would be done by the compiler, in the same way that this.base is implemented now, and properties are added by using Object.defineProperty so that code like myObject.setMyProp(123) and myObject.myProp = 123 are synonymous.
Whether this means that we have to make the implementation of qx.Class.define be backed by actual ES6 classes or not (ie can we get away with just using Object.defineProperty) I don't know.


Prepare 10.0.2.final

Core - Full Integration Build 9152 outcome was FAILURE using a merge of 189b6dc9a7ff58496d129c745dace054dff386fe
Summary: Exit code 1 (Step: Build & test full (Maven)) (new) Build time: 00:02:07

Core - Full Integration Build 9154 outcome was FAILURE using a merge of 33b9fd1df10e28600acd031083c7822ee6dabd76
Summary: Exit code 1 (Step: Build & test full (Maven)) Build time: 00:01:43

Core - Full Integration Build 9155 outcome was FAILURE using a merge of 33b9fd1df10e28600acd031083c7822ee6dabd76
Summary: Exit code 1 (Step: Build & test full (Maven)) Build time: 00:03:12

Core - Full Integration Build 9156 outcome was FAILURE using a merge of 33b9fd1df10e28600acd031083c7822ee6dabd76
Summary: Exit code 1 (Step: Build & test full (Maven)) Build time: 00:01:43

Core - Full Integration Build 9158 outcome was FAILURE using a merge of 33b9fd1df10e28600acd031083c7822ee6dabd76
Summary: Tests passed: 1145, ignored: 29; exit code 1 (Step: Build & test full (Maven)) Build time: 00:21:54

Core - Full Integration Build 9159 outcome was FAILURE using a merge of 33b9fd1df10e28600acd031083c7822ee6dabd76
Summary: Tests passed: 1145, ignored: 29; exit code 1 (Step: Build & test full (Maven)) Build time: 00:17:40


Adding omnibase to documentation index for distro

I would like omnibase to be indexed and documented on ros.org.

Thanks for iterating.


[New Port Request]  Dynamic Animation and Robotics Toolkit (DART)

Library name: Dynamic Animation and Robotics Toolkit (DART)
Library description: DART (Dynamic Animation and Robotics Toolkit) is a collaborative, cross-platform, open source library that provides data structures and algorithms for kinematic and dynamic applications in robotics and computer animation.
Source repository URL: https://github.com/dartsim/dart
Project homepage (if different from the source repository): http://dartsim.github.io/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

Repology: https://repology.org/project/dart/versions and https://repology.org/project/dartsim/versions
Debian package: https://packages.debian.org/source/sid/dart
Homebrew Formula: https://formulae.brew.sh/formula/dartsim
Testing port repository: https://github.com/jslee02/vcpkg-dart

Was about to create a request for this. Definitely a good candidate to be added into vcpkg!

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Feat: Re-add Obs Networks.

What?

Re-add obs networks. We have separate observation networks for the actor and the critic, which get optimized by different optimizers. In future, we should explore different variations of this.
Adapt assert that breaks on nested observations.

Why?

Certain envs uses obs networks e.g. pong.

How?

Extra

Looks good, just very minor changes.
If you could also open an issue for investigating a shared obs net, that would be great

I created an investigation issue for this. :+1:


Some Questions About CorrBlock.

I noticed that the calculation of CostVolume is different in RAFT-Stereo and SEA-RAFT. RAFT-Stereo seems to be more efficient, why is SEA-RAFT not used? Also, in most stereo flows, the CostVolume is calculated using the global shift and then dot multiply and average method, instead of matrix multiplication in the non-stereo flow method. Is this because the flow produced in stereo flow is mainly the global motion? Thank you very much.

After rectification, the stereo-flow is 1D, which allows more efficient implementations. We did not investigate the efficient implementations of CostVolume in SEA-RAFT.


wip frq-tx-payment boiler

Goal
The goal of this PR is
Closes
Discussion

Checklist

[ ] Chain spec updated
[ ] Custom RPC OR Runtime API added/changed? Updated js/api-augment.
[ ] Design doc(s) updated
[ ] Tests added
[ ] Benchmarks added
[ ] Weights updated

Since building it is taking forever, I am now opening it up for review.
Pending todo:

better commit message
squash commits
remove api-augment code I added.

Please ask questions.


Switch to ADM2 on Windows Desktop

Switch audio implementation on Windows Desktop to the new Core Audio
based audio device module (ADM2), which avoids a crash in ADM1 when one
device is not supported by that module (even if unused), like Azure
Kinect DK.
Add a new function |mrsLibraryUseAudioDeviceModule2()| to enable users
to switch back to ADM1 in case there would be issues with ADM2, as
support and maturity of ADM2 are unclear, and the module is not always
well tested, though is the recommended way from Google going forward.
Bug: #124

Is this working for UWP x64 for Windows 10 apps?

No, this is Windows Desktop, not UWP.


Update the metadata on test image to match current implementation

Good day.
I noticed the changes introduced by #536 did not update the test cases for parsing image metadata. Since #536 increased the number of decimal digits, the exposure attribute parsed from the images may have different values compared to the existing test data. Therefore, I made this PR to update the metadata on the test data.

thanks you!


Create helper function to convert data source to executable schema

In order to allow data sources to be used in frameworks that require individual data sources to be executable schemas (e.g. qewl), we should add a helper that converts a GrAMPS data source to an executable schema + context + namespace.
See this comment for a potential solution.
Question: should this be a named export from @gramps/gramps?

This is now a duplicate of #26


Feature/#49 add support for user roles

Adds a Roles []string property onto the User model.

Pull Request Test Coverage Report for Build 330

39 of 41 (95.12%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.8%) to 29.152%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mongo/client_manager.go
0
2
0.0%

Totals

Change from base Build 324:
0.8%

Covered Lines:
839

Relevant Lines:
2878

💛  - Coveralls


Created Tweet Monster Pattern

What this Pull Request (PR) does
Created Tweet Monster Pattern
Any help would be great to make it better.

Hey Bro, AFAIK LLMs temporarily unable to interact with the webpage for registration operations just within a System Message, not to speak of analyzing the performance of your tweets. How did you do it in this Pattern?

This used to work for me but it no longer does. It just creates a tweet about tweeting now. Is it just me?


[quirrel.dev service] Occasional 400 from api.quirrel.dev

Bug Report
Current Behavior
Occasionally, a queue fails to post a handler success response back to api.quirrel.dev. The lack of a response causes the Quirrel service to think the call failed.
Expected behavior/code
The communication with api.quirrel.dev has built in retries, or at least on failure throws a useful error since the 400 shows up in quirrel.dev as an empty string ""
Environment

package
version

Quirrel
1.7.4

next.js
12.0.7

node
lts (16)

yarn
3.0.2

Quirrel version: [e.g. v1.0.3]
Node/npm version: [e.g. Node 14/npm 6]

Possible Solution
As a workaround, I can pass my own fetch implementation into the route, wrapping with fetch-retry or an equivalent library. However, it feels like some amount of basic retrying should be baked into the client library itself instead of throwing on a 400.
I prototyped a few API alternatives to get fetch exposed at the point of Queue creation. I think the most reasonable place to put this if we don't want to change the way the Quirrel client works is to expose fetch in EnqueueJobOptions ref which defaults to (options) => fetch(options), allowing for a custom fetching implementation.
Or we can add retries to makeRequest, enqueue, enqueueMany, etc. In that case, I would strongly recommend using something like fetch-retry with sensible defaults.
Additional context/Screenshots
2022-01-03T21:04:04.230Z	e3ee4716-20fd-452c-91b2-3d153315278f
ERROR	Unhandled Promise Rejection
{
  "errorType": "Runtime.UnhandledPromiseRejection",
  "errorMessage": "FetchError: request to https://api.quirrel.dev/queues/<queue> failed, reason: read ECONNRESET",
  "reason": {
    "errorType": "FetchError",
    "errorMessage": "request to https://api.quirrel.dev/queues/<queue> failed, reason: read ECONNRESET",
    "code": "ECONNRESET",
    "message": "request to https://api.quirrel.dev/queues/<queue> failed, reason: read ECONNRESET",
    "type": "system",
    "errno": "ECONNRESET",
    "stack": [
      "FetchError: request to https://api.quirrel.dev/queues/<queue> failed, reason: read ECONNRESET",
      "    at ClientRequest.<anonymous> (/var/task/node_modules/node-fetch/lib/index.js:1461:11)",
      "    at ClientRequest.emit (events.js:400:28)",
      "    at TLSSocket.socketErrorListener (_http_client.js:475:9)",
      "    at TLSSocket.emit (events.js:400:28)",
      "    at emitErrorNT (internal/streams/destroy.js:106:8)",
      "    at emitErrorCloseNT (internal/streams/destroy.js:74:3)",
      "    at processTicksAndRejections (internal/process/task_queues.js:82:21)"
    ]
  },
  "promise": {},
  "stack": [
    "Runtime.UnhandledPromiseRejection: FetchError: request to https://api.quirrel.dev/queues/<queue> failed, reason: read ECONNRESET",
    "    at process.<anonymous> (/var/runtime/index.js:35:15)",
    "    at process.emit (events.js:412:35)",
    "    at processPromiseRejections (internal/process/promises.js:245:33)",
    "    at processTicksAndRejections (internal/process/task_queues.js:96:32)"
  ]
}

[ERROR] [1641243844254] LAMBDA_RUNTIME Failed to post handler success response. Http response code: 400.
RequestId: 0eac4614-0a52-4a16-b13e-f33138398502 Error: Runtime exited with error: exit status 128
Runtime.ExitError

Hey @jakobo! This is a sensible request. In fact, it's so sensible I already have a PR for that open: https://github.com/quirrel-dev/quirrel/pull/882 😁 Will try to get that merged soon.

released in https://github.com/quirrel-dev/quirrel/releases/tag/v1.8.1!


Still Maintained?

I notice that some potentially serious issues have gone unanswered for a while. In addition, there hasn't been any recent new code. Finally, there are some pretty low hanging pull requests. All of this makes it appear as if the project is no longer maintained. If this is not true, can you give a description of your intentions for the future of this project?

It could be that the maintainer is on vacation or otherwise away from computer. His GitHub profile shows no/low activity in the past month, https://github.com/phpnode.
Which issues/PRs in particular are you referring to? I have merge rights, though I wouldn't be able to publish new NPM version.
If there are particular issues that babel-plugin-typecheck does not address, consider https://github.com/gcanti/babel-plugin-tcomb as an alternative. Mind you, I have not tested the latter, just came across it recently and noted its existence.

Here are a few examples. #165 has been open for 22 days without a comment. #155 was the issue that particularly scared me. Looking at milestone 1 there are 5 issues marked as bugs going back as far as Jan 25. These are acknowledged bugs in the current implementation, plan to be fixed, but have yet been fixed. It is worth mentioning that 1 bug marked for the milestone was fixed. Also 1 low hanging MR was closed since I last looked by gajus.
I'll admit, I kinda sound like a jerk right now. Everyone that participates in open source deserves credit for the work they do. Thank you!

It looks like @phpnode (the maintainer) is alive and well, and working on a new project:

https://github.com/codemix/flow-runtime

But yeah, it would be nice to get confirmation as to whether this project is still maintained or being orphaned; I'm in the middle of evaluating static type libraries, and I tend to shy away from anything without active development.

Hey, yeah sorry for the lack of updates on this, I've badly neglected this project for too long and I'm really sorry about that - other things in life took over. The last few weeks I've been working on flow-runtime which will deprecate this project, it does everything that babel-plugin-typecheck does but uses a runtime library and aims for full flow compatibility which was not possible with the previous approach. I'm still working on the docs site but hope to do a release very soon.

@phpnode glad to see you are Okay.
On the subject of flow-runtime, is there a reason for duplicating the effort with https://github.com/gcanti/babel-plugin-tcomb. As far as I can tell, both strive for full compatibility with Flow type.

@gajus I raised this very issue with @gcanti about this here - https://github.com/gcanti/flow-io/issues/19 - tl;dr - babel-plugin-tcomb ran into the same issues as babel-plugin-typecheck - it's very hard to coexist with flow if you don't support absolutely everything flow does, and total flow compat is not a goal of tcomb (or now flow-io). I really do hope we can bring the projects together eventually because they are so similar.

Ok I just published the first (hopefully) usable version of flow-runtime and put together a docs site with some examples here - https://codemix.github.io/flow-runtime/ I'll go through the issues in this repo and transfer any applicable ones over to https://github.com/codemix/flow-runtime and deprecate this project.

@phpnode Thanks! I was just about to start playing with flow-runtime and had to npm-link a checkout (since package.json dependencies don't support Git subfolder URLs, so no monorepos), but a published version will make it easier.

Thanks for giving everyone an update! I am excited to checkout flow-runtime! I think this issue has been settled.


fix(react-dom): allow unstable ref props

closes #1760 @threehams
not sure why i didn't think of this originally 😄 can remove the docs about it too

hmm seems like there could be a problem with allowing null to unset the ref value as the second commit reintroduces the loop

Seems like this realistically can't be fixed for the whileElementsMounted prop due to React calling it with null again 😒


xss in path

Sometimes need check xss in path.

Hi @ghsec ,
Thank you for a good idea. I am of the same opinion.
I'm thinking of an option to specify a inject point to test, but if you have anything to add, please let me know.
- params
- cookie
- path
- user-agent

Cookie and UA are thinking about integrating into the header. But Heather may have the potential to induce malfunctions..

And need add xss oauloads in js functio

I will try edit and test this localy.

However, I will develop the path(and js function) testing first. it as need some structural changes to support all the inject points. I'll leave a comment when I'm done.
I always welcome pull requests :)

Ok thank

Hi @ghsec ,
As I was thinking about plan, I have a question. Is it true that what you said was the addition of an XSS case that works inside the JS? Let me know if I got it wrong!
e.g
// [test param on request ]: '+alert(45);//
// [ response ]

var a = 'test'+alert(45);//';

If the above content is correct, I think it would be better to add payload, and Selenium detection would be less misleading than Reflected detection. (It was just memo for me)

@hahwul sorry I don't know python but it is right way, keyword'-alert(45)-'
keyword for search reflection and you can build regexs for detecting xss payloads.

@hahwul we can change ideas on twitter
[@GochaOqradze] (https://twitter.com/GochaOqradze)

@ghsec
I understood it. I also knew the need to add these skill(in-js) because they are used a lot. Thank you for your opinion! Maybe next January at the latest, v1.3 with that feature will be released! Thank you very much.

Hi @ghsec ,
Version 1.3 with path scan and in-js scan is released. Maybe i need to add more patterns. If you need a bug or a pattern, please leave a comment. Thank you very much for your good opinion. Happy New Year
$ gem update XSpear


Add support for async/await

Kilo's callback model already mirrors the "async throws" style described in this proposal:
https://gist.github.com/lattner/429b9070918248274f25b714dcfc7619
It should not be difficult to update the API to use async/await instead, if this feature ends up being added to the Swift language.

https://developer.apple.com/videos/play/wwdc2021/10132

Async/await support has been added to the development branch.

Resolved in 4.0.0.


Where or what is Sparky Watch?

These docs state that:

watch
Same as src above, the only difference is that it is a daemon so it will always run whenever a file in the captured globing changes.

I found a code example of Sparky src, but I can't find watch anywhere in the code base.

oof, I don't think it's been implemented. We really need to brush it up. I will try to get some time this week.

Thank you  so much!
I'm working on a docs project with a lot of .md files that I was hoping sparky could keep up to date.
I think this might be my 20th or so fuse-box project.


fix(transloco): 🐛 prioritize finding culture languages

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/ngneat/transloco/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #472
What is the new behavior?
When looking for the language in navigator.languages, the first culture language (i.e. en-US or en_US instead of en) is selected.
This solves the case where the list is ['en', 'en-US', 'fr', 'fr-FR'] while still taking the order into account.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

This will result in different languages across different browsers.
From the issue you referenced #472:

Using getBrowserCultureLang() returns:
Chrome: de-DE (correct)
Firefox: de (wrong)
Safari: de-de (wrong)

This means that de will be skipped in Firefox and return a second language if one is defined, if not, it will still return de

Well the main goal here is to skip languages that are not culture language, so skipping de would be fine?

getBrowserCultureLang is working as expected. please read my comment.

getBrowserCultureLang is working as expected. please read my comment.

Right, that makes sense, so essentially the "plain" language code is still a "culture language" and if for some reason an app would rather than the more accurate code with sublang first, it's the app's job.
I guess I can just close the PR?

@rraziel yes.
Thanks for opening it in the first place.
Would you like to open a PR to fix the isLocaleFormat function?

Sure I'll look into it


React 0.13 compatibility etc.

This looks great except I'd rather not have the compiled version checked in to Github. If you could remove that and add dist back to .gitignore I'll merge this and make a new release.

Went ahead and merged the changes and removed the compiled files and made a new 0.6.0 release. Thanks!


Do not delete ExternalIPs

What this PR does / why we need it: ExternalIPs are not managed by Kubernetes and should not be touched.
This is copy of PR from k8s repo https://github.com/kubernetes/kubernetes/pull/51894
NONE

/kind bug
cc @quinton-hoole

/lgtm
(the issue is already discussed and concluded in https://github.com/kubernetes/kubernetes/pull/51894)


aggr function

Is there a function that could ajust the sequencing depth of many samples to the same level, like the aggr fucntion of 10x?
Thank you very much.

CeleScope does not have such function. You can simply normalize the data in downstream analysis.
https://github.com/satijalab/seurat/issues/672


Fail to compile target mips64-unknown-linux-gnuabi64

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
Cross-compiling mips64el-unknown-linux-gnuabi64 failed with the following error
Digest: sha256:59e496d0e1ebe88c6c1ba878c0c7ac256b74922e113b0082fd4d9a95e2f2f95d
Status: Downloaded newer image for ghcr.io/cross-rs/mips64-unknown-linux-gnuabi64:main
   Compiling proc-macro2 v1.0.66
   Compiling crossbeam-utils v0.8.20
   Compiling unicode-ident v1.0.11
   Compiling libc v0.2.155
   Compiling cfg_aliases v0.1.1
   Compiling rayon-core v1.12.1
   Compiling nix v0.28.0
error[E0463]: can't find crate for `core`
  |
  = note: the `mips64-unknown-linux-gnuabi64` target may not be installed
  = help: consider downloading the target with `rustup target add mips64-unknown-linux-gnuabi64`

   Compiling cfg-if v1.0.0
For more information about this error, try `rustc --explain E0463`.
error: could not compile `libc` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `cfg-if` (lib) due to 1 previous error
error: could not compile `crossbeam-utils` (lib) due to 1 previous error
[cross] warning: rust-std is not available for mips64-unknown-linux-gnuabi64
[cross] note: you may need to build components for the target via `-Z build-std=<components>` or in your cross configuration specify `target.mips64-unknown-linux-gnuabi64.build-std`
              the available components are core, std, alloc, and proc_macro
Error: Process completed with exit code 101.

What target(s) are you cross-compiling for?
mips64-unknown-linux-gnuabi64
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[ ] Windows
[X] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[X] docker
[ ] podman
[ ] other container engine (specify in description)

cross version
0.2.5
Example
cargo install cross --git https://github.com/cross-rs/cross
cross build --release --locked --target=mips64-unknown-linux-gnuabi64

Additional information / notes
All run in Github Action Ubuntu-latest Runner
Bold mips64-unknown-linux-gnuabi64 and mips64el-unknown-linux-gnuabi64 got and issue
No response

resolve by adding cargo flags
- cross build --release --locked --target=mips64-unknown-linux-gnuabi64
+ cross build --release --locked --target=mips64-unknown-linux-gnuabi64 -Z build-std=core,std,alloc,proc_macro,panic_abort

I thought cross would help me build these exact libraries.


Brian/allow fee update

Pull Request Test Coverage Report for Build 7553

11 of 54 (20.37%)  changed or added relevant lines in 5 files are covered.
1283 unchanged lines in 61 files lost coverage.
Overall coverage decreased (-79.6%) to 20.42%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/core/fee-calculators/PerformanceFeeCalculator.sol
0
43
0.0%

Files with Coverage Reduction
New Missed Lines
%

contracts/core/fee-calculators/FixedFeeCalculator.sol
1
86.67%

contracts/core/tokens/SetToken.sol
1
80.43%

contracts/core/lib/SetMath.sol
2
0%

contracts/core/tokens/rebalancing-v2/RebalancingFailure.sol
2
80.77%

contracts/core/extensions/CoreOperationState.sol
3
33.33%

contracts/core/lib/SetTokenLibrary.sol
3
46.67%

contracts/core/modules/lib/ModuleCoreStateV2.sol
3
0%

contracts/core/tokens/rebalancing-v2/Issuance.sol
3
66.67%

contracts/lib/CompoundUtils.sol
3
0%

contracts/core/lib/Rebalance.sol
4
33.33%

Totals

Change from base Build 7545:
-79.6%

Covered Lines:
381

Relevant Lines:
1707

💛  - Coveralls


Update modules to Terraform 1.0.x

Update modules to Terraform 1.0.x

Thanks for review! Merging now.


Support for SwiftyJSON?

Hi guys,
Are you compatible with SwiftyJSON? For example, can I do:
pusher.bind("new-comment", callback: { (data: AnyObject?) -> Void in
    if let data = data as? JSON {
       // more stuff
    }
})

Hi @josephyzhou!
You can set the value of attemptToReturnJSONObject to false in your Pusher initializer, like so:
let pusher = Pusher(
  key: "APP_KEY",
  options: [ "attemptToReturnJSONObject": false ]
)

More info about configuration in the docs: https://github.com/pusher-community/pusher-websocket-swift#configuration
Then when you receive the data in the callback it will be a String that you can then parse using any JSON parser you'd like, including SwiftyJSON. Specifically, with SwiftyJSON it looks like you'll need to do something like this (a bit pseudo-codey so you might need to tweak it):
pusher.bind("new-comment", callback: { (jsonString: AnyObject?) -> Void in
  if let dataFromString = jsonString.dataUsingEncoding(NSUTF8StringEncoding, allowLossyConversion: false) {
    let json = JSON(data: dataFromString)
    // do stuff with your json object
  }
})

Hi there,
i notice that the flag you're talking about was not working, so I fixed the issue and made a #63
Then you can make a JSON object from a String the way you want.


White text on preview button in hc mode

Fixes https://github.com/Microsoft/pxt/issues/3415

Needs to go in v0 (#3415 is on micro:bit)


FF: Pending state in Import Flag modal while validating json

On successful drag end or on successful user-select (i.e. a json file was able to be parse), a call will go out to /featureflags/validation. While that call is pending:

the large draggable "Import" widget will be hidden
a spinner will show in the middle of the modal (retain the same height as when showing the widget though so it's not janky and popping up and down in height)
when the response has been received, the spinner will disappear and the next state will be dispatched.

The load-spinner sounds good to me.

QA: this looks good.


WIP Finish tests

#136
Also stumped why my coverage would be 0. Reason: TBD

@logrdog I can pair on this with you if you need help or finish it up and give you the solution if you are totally stuck, just let me know

@JoshuaVSherman yeah sorry, I am stumped on why coverage fails even after the fact every test passes. I do need help on why that would be happening, whatever option would be easier :+1:

@logrdog I did some upgrades and added a new test, this branch works now for me and is at 100 percent coverage, so please review the changes and let me know when you are ready, then I will merge it. Talk to you later


Bug: Application error: Uncaught (in promise): CloseEvent: {"isTrusted":true}

Error message: Uncaught (in promise): CloseEvent: {"isTrusted":true}
Error stack:
Error: Uncaught (in promise): CloseEvent: {"isTrusted":true}
    at ve (altair://-/polyfills.js:1:35936)
    at altair://-/polyfills.js:1:34973
    at t (altair://-/main.js:1:2601566)
    at _ (altair://-/main.js:1:2601769)
    at x.invoke (altair://-/polyfills.js:1:25842)
    at Object.onInvoke (altair://-/main.js:1:107574)
    at x.invoke (altair://-/polyfills.js:1:25781)
    at x.run (altair://-/polyfills.js:1:20882)
    at altair://-/polyfills.js:1:36771
    at x.invokeTask (altair://-/polyfills.js:1:26527)

When did this error occur? And does it re occur, or it happened only once?
This happens on an example subscription from Apollo.
resolver:
Subscription: {
chatMessageCreated: {
// More on pubsub below
subscribe: () => pubsub.asyncIterator(['CHAT_MESSAGE_CREATED']),
},
},
types:
type ChatMessage {
text: String # Property
}
type Subscription {
chatMessageCreated: ChatMessage
}
Please provide some helpful screenshots of the bug
Version 4.4.1

Is it reproducible for you? If I can reproduce it, then I know what to do to fix it easily.

Sorry - my explanation wasn't appended. This is a typical error with the Apollo framework - what happens in the tool is that a dialog comes up for a few seconds and then goes away. is there anyway to make this part of a status screen? In a subscription these errors happen frequently.

@jdevng I'm not sure I still understand. What error is typical?

It's how the error is displayed, not the error. The error appears as a notification, it disappears too fast, and the window isn't large enough to show the information above. Is it possible to de-activate this notification of the error? In subscriptions, the errors will repeat in this case, and the notifications will just stack up.

Oh. The purpose of the error is to track down and fix it, which is why clicking the error creates a new issue on GitHub. If the error repeats, I want to know the steps needed to reproduce it so I can look into it and fix it. That way you also don't get the error alert.

ah, i didn't realize that was an application error - i thought it was a normal part of your design. i can send you an example server with the error - but i don't want it posted on the internet.

<EMAIL_ADDRESS>


feat: Save column data into json_metadata for all Query executions

SUMMARY

Anytime a user executes a query in Sqllab we want to store columns data inside the new json_metadata field to allow us leverage this information whenever a user may want to run this same query inside Explore.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Is there a reason not to reuse the ExtraJSONMixin？

Is there a reason not to reuse the ExtraJSONMixin？

I'm using the extra mixin here
https://github.com/apache/superset/pull/20059/files#diff-68d044828e32dbc106f7cece56d7aeeccbe2eb455cf33307df4fc9d07dfb1fd5R67

My apologies. The fact that the the command is called save_metadata made me think the ExtraJSONMixin was not used. Not sure if we need to change it , but it's worth checking what other modules are doing for similar operations.


⚠ ClamAV has degraded performance

In 0cc346b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 92 ms

Resolved: ClamAV performance has improved in 98d6a1d.


Product feed pagination total number of pages bug

Environment:
PHP - 7.0
Magento - upgraded to 2.2.2
Channable extension - 1.0.12 (installed via composer)
This is what the first page of the product feed (channable/feed/json/ request) returns:
"products_total":1,
"products_limit":"50",
"products_output":50,
"products_pages":1,
"current_page":1,
"next_page":"false",

"products_total", "products_pages" and "next_page" are incorrect.
Looking at the extension code, I see that the source of this bug is in the magmodules/magento2-channable/Model/Collection/Products class, getCollectionCountWithFilters() method:
public function getCollectionCountWithFilters($productCollection)
    {
        $selectCountSql = $productCollection->getSelectCountSql();
        $connection = $this->resource->getConnection(ResourceConnection::DEFAULT_CONNECTION);
        $count = $connection->fetchAll($selectCountSql);
        return count($count);
    }

var_dump($count):
array(1) {
    [0]=>
        array(1) {
            ["COUNT(DISTINCT e.entity_id)"]=> string(3) "841"
	}
}

and then count($count) always returns:
int(1)

If I use this instead:
return array_shift($count[0]);

I get the correct response:
"products_total":"841",
"products_limit":"50",
"products_output":"50",
"products_pages":"17",
"current_page":"1",
"next_page":"true"

I checked the latest stable release of the extension, but the same problem persists, so the upgrade wouldn't suffice.
Could you please take a look at this issue and give me feedback when you expect it to be corrected?

I am so sorry, this turned out to be the bug caused by another extension, which created afterGetSelectCountSql, overriding Magento core functionality, which you used in your method.
It just so happened that this bug became visible through your extension.
This issue can be closed, I apologize again, it was my mistake not testing this on clean Magento installation


Use associated type in memory managers

It makes it clearer that an XMemoryManager only manages a single target type.

I'd ideally like to get rid of the memory manager stuff btw. It doesn't really bring any advantage and just adds more things for the compiler to optimize away.


Incorrect result from X'y in Julia

Please see this issue posted at JuliaLang.

Interestingly this appears to use the same GEMV_T codepath as assumed to cause a problematic loss of precision in #4324 - though here the exact same kernel works when compiled for AVX2-only but not when AVX512 instructions are available.

Actually not related as it only happens with the ancient SSE kernel for Core2 that was the default for an unrecognized (too recent) cpu in past versions.


Fix bootstrap size differences

To minimize spurious size differences, I made the following changes:

Disable compression for the table
Compact the sstables (probably not needed, but safer)
Account for the size of the node before loading data

I also added conversions to floats to avoid doing math between floats and Decimals (which results in an error).

+1. The type error was just introduced last week, thanks for fixing it.


Long time no see!

Hello, just want to say this is a cool approach for railway programming. I also encountered something similar while searching for an alternative way to implement service object. Turns out your idea was not that crazy at all!
^^

Just came to say hi, wonder if you are still somewhere around HCM this September. I would like to invite you to join my farewell party. If you are free let me know.


src_dir is deprecated

Coveralls throws errors when src_dir is set.

Build failing due to CS issues. Can be merged together with #42


Integration Test - Release - 2021/09/14 19:19:01

Auto create for integration test. IssueCommandFlow

@PRMerger-test-1 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Docs Build status updates of commit 94bf09c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

csidevdocs-public/IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md
:warning:Warning

Details

csidevdocs-public/IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md

Line 4, Column 8: [Warning-duplicate-titles] Title 'VS Code Authoring Extension' is duplicated in: 'Demo/demo.md(4,8), Demo/v-caxian/auto-merge.md(4,8), Demo/v-caxian/auto-merger.md(4,8), IntegrationTest/BuildIntegrationTestFiles/ChangeSentToAuthor.md(4,8)'. Titles must be unique within a docset.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Aadi/track local queues

add instance + frame data structures for easier data manipulation.
implement track local queues for tracking so that we track across individual instance gaps instead of ending trajectory every time it leaves the queue.
Add Miscellaneous formatting/doc string fixes

Summary by CodeRabbit

New Features

Search functionality added to the app interface.
New search bar integrated into the Hero component for improved user experience.

Documentation

Updated method docstrings for enhanced clarity and consistency across the codebase.

Refactor

Improved data handling with the introduction of Frame and Instance classes.
Enhanced tracking logic with the new TrackQueue class.

Style

Adjusted styles for the search bar to align with the app's design language.

Tests

Expanded test coverage for new data structures and tracking functionality.

Bug Fixes

Fixed issues with bounding box calculations and data processing logic.

Chores

Codebase cleanup including removal of unused imports and minor docstring corrections.

@coderabbitai review


Functional Question: Pasting text from clipboard into prompt window

Behavior:
When pressing Ctrl+shift+v the text is not inserted into the prompt window
Use case:

I oftentimes write very long prompts.
It is not possible to view longer prompts within the prompt window. Also it is difficult to edit them.

Consequently, it would be nice to be able to write longer prompts in a normal neovim buffer and then paste it to the prompt window
Additional Considerations:
If telescope / nui.nvim does not allow this, it would be nice to have a command similar to "ChatGPTEditWithInstructions".
This command would allow the user to directly send a visual selection into text-davinci.

New Observation:
My described issue is present when yanking text from a neovim buffer.
I have just found out that when I copy text from another source (e.g. browser), I can press ctrl+shift+v and it inserts the text.

it would be nice to have a command similar to "ChatGPTEditWithInstructions".

Exactly, I've found this try to do exactly this, but doesn't work over markdown files 🤷


Ampersands in Terraform Outputs are being Encoded

Hi there,
In PR #91 there was a change to the way that this mixin grabs output from Terraform. Specifically, the mixin now requests output values as json rather than raw format. Here is the change in question:
https://github.com/getporter/terraform-mixin/pull/91/files#diff-282757e263fe02ec96e35fd1120b9263db1ca315d75cea25d3ccf68239bd7472L56
Unfortunately, due to some strange formatting rules within Terraform, this breaks any URI that includes an ampersand (i.e. URIs or URLs that have querystring parameters) and this is a common case for connection strings or service endpoints.
My investigation into an issue has been written up here, and includes a small repro sample that demonstrates the issue:
https://github.com/microsoft/AzureTRE/issues/2549#issuecomment-1239341427
There is a closed Terraform issue describes this behaviour  and it was closed by simply adding additional documentation to explain the behaviour (and a comment that they will never change this behaviour):
https://github.com/hashicorp/terraform/issues/26110
The fix was to better document it:
https://github.com/hashicorp/terraform/pull/26122
Can the terraform-mixin either switch back to using the -raw flag when accessing TF outputs? I'm not sure what the alternative is (I'm not sure how safe it would be to patch up/replace these encoded characters)

A conversation about this issue has taken place on the Terraform repo.
The following are the most useful comments:
https://github.com/hashicorp/terraform/issues/31756#issuecomment-1241378444
https://github.com/hashicorp/terraform/issues/31756#issuecomment-1242155295
The point made in these comments is that it's not a valid use of the -json format switch to take JSON output from Terraform and then parse it as a string, rather than as JSON.
A suggested (untested) code fix has been given that might allow the outputs to be inspected, for true JSON output to then be returned as JSON, but for other output (regular strings) to be returned as their raw value.

The use of the -raw switch within this mixin means that JSON encoded strings are being passed as outputs from the bundle, but they are being treated as regular strings. In the case where that string has an ampersand it results in an encoded ampersand being passed back.

@martinpeck Thanks for the the background on the problem and apologies for the regression. It's a bit to digest but I'm sure we can get this fixed in the mixin with all the great info from the other issue's comments.
If you are up for trying a PR, great! Otherwise I'll keep it at the top of our backlog and will try to get it fixed in the 1.0 release of the mixin.

Thanks @carolynvs. I'll take a look next week and see if I can PR a fix for this.
I'll also take a look at the reasoning behind the switch from -raw to -json, but if you have some context as to why that change was made that might he helpful when it comes to testing.

@sgettys can provide more detail, here is the original issue and PR that prompted the switch

The reason for the switch from -raw to -json is because -raw doesn't support complex object types for the output, only string, bool, and number. I've moved over to doing proper JSON unmarshaling for the output string to essentially rip off the json encoding put on there by Terraform. I'll be adding in some more tests to make sure we're not missing another regression for this, thanks for finding and detailing this bug!

That's awesome @sgettys !
Thanks!

Thanks @sgettys , @VinozzZ , @carolynvs ! Really appreciate the quick turn around.
Can you let me know roughly when this might appear in a release? I'd like to pick this change up for a project I'm working on right now, if possible.

I am fixing a bug in the mixins today and then cutting new release candidates of everything. You can always build the mixin locally with mage build and then install it into your PORTER_HOME directory with mage install until an updated release candidate is available.

I recommend installing porter v1.0.0-rc.2 and then install the terraform mixin with porter mixins install terraform --version v1.0.0-rc.1.
The new versions of the mixins probably work with v0 still but really I have never tried. They are intended to work with porter v1.

Out of interest...for a fresh install of everything, how does porter determine which mixin versions to install?

Just in case anyone else is wondering, here's how it works.
 Now Porter v1's install script only installs porter and the exec mixin (the same version as porter, since they are in the same repo). All other mixins must be explicitly installed.
Also the porter mixins install command installs only the latest stable version which excludes these pre-release versions of the mixins. So you have to explicitly pick the version when installing a pre-release mixin with the --version flag.


trivial corrections Linux OS version support list

CentOS download list (subsequent section) lists CentOS-7.4 (not 7.2) - presuming thusly that TRex supports CentOS-7.4 at this time
the "/ Redhat" was probably meant to be "RHEL" (Redhat Enterprise Linux)
Neither CentOS nor RHEL have release trains denoted by "LTS" (long term support) - removed

https://linuxlifecycle.com/

(mistake in PR to myself ;/)  closed it - properly replaced by https://github.com/cisco-system-traffic-generator/trex-core/pull/94


[Bug]: Dropdown changes in design system affected performance of modal

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Recent changes in design system dropdown component affected the re-rendering time of modal widget. This is due to the use of createGlobalStyle functionality of styled component
Steps To Reproduce

Goto performance dashboard
Check the PR details tab with 16718
Notice the re-rendering time diff in MODAL_OPEN

Public Sample App
No response
Version
@appsmithorg/design-system-1.0.25

This issue has been verified in release.


Document of PHP need update? cannot set to 7.1

Hi team,
I have a question for setting the php version of Azure App Service.
According to the this documentation.
https://docs.microsoft.com/en-us/azure/app-service/web-sites-php-configure
It should be able to set the php versiont to 7.1, but the fact is the configuration page only have the 7.0 and 7.2.

and i notice that the documentation seems like outdated, it was edited on 04/11/2018 last time.
And my questions is below:

Is this command is still working? cause it shows error when i run.
az webapp list-runtimes | grep php

Is it still available for php version 7.1? Can I config my php version to 7.1 for now?
According to this post, 7.1 should be EOL by 1 Jan 2020. So when i try to new a php app service, it didn't come out with the 7.1 version for sure. but i want to change to 7.1 following the documentation

 az webapp config set --php-version 7.1 --name {app-name} --resource-group {resource-group-name}, and it shows up a part of JSON, and seems like nothing happen.
But when i try this code
az webapp config set --name <app-name> --resource-group <resource-group-name> --linux-fx-version "PHP|7.1"
it can successfully change it to "PHP|7.1".
Can you please also explain the difference between this two to me?
Thank you so much.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5e564777-8d59-9065-6f0d-d8ea3fc6ee62
Version Independent ID: ec93756c-4d7f-efc8-a8ca-9b87d1be8ac3
Content: Configure PHP runtime - Azure App Service
Content Source: articles/app-service/web-sites-php-configure.md
Service: app-service
GitHub Login: @msangapu-msft
Microsoft Alias: msangapu

@Pancat007 Thank you for the feedback. We will review and update accordingly.

@Pancat007 We typically only show the latest version or two in the Azure portal. If a version is nearly EOL, it will likely be replaced in the portal for a newer version to ensure customers are following best security practices.
We do want to ensure we remain compatibility for customers as well. So we do make older frameworks available but you'll need to manually configure them, as you pointed out.
I was able to get the cmdlet to show runtime to output. You might want to narrow the scope of your cmdlet by specifying a specific web app as each app could have a different version of web apps software on it due to our staggered roll out of updates.

In regards to the cmdlet to set the version, I initially thought this might be a compatibility issue with using a cmdlet meant for windows on a Linux web app but I encountered the same behavior as you. I have started a conversation with the doc author to see if the failing cmdlet is outdated and if so, should the latest cmdlet be used. They will make the necessary changes going forward.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Hello @BryanTrach-MSFT
I have the same issue I also want my web app in 7.1.
But same if I executing command which is below,
az webapp config set --name <app-name> --resource-group <resource-group-name> --linux-fx-version "PHP|7.1"
It's not working it's changed but still, my app is not working,

As per the image here no 7.1. And also not that command is working and right now I am not at this stage that I can change web app to higher PHP leave I need to go live soon so can you help me out of this to do 7.1.
Here below screen also no option in selection.

Please help me asap.
Thanks.


Support apiextensions.k8s.io/v1 App CRD

When using kubectl 1.19.1 to install kapp-controller in a Kubernetes v1.19.1 cluster, we got this warning:   apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition. Using kubectl 1.18.x doesn’t get the warning.
Shall we provide the apiextensions.k8s.io/v1 App CRD? Thanks.
Reference: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#create-a-customresourcedefinition

Also: https://vmware.slack.com/archives/CUK1X0Z8Q/p1606317265094900

👍  Also: https://vmware.slack.com/archives/CUK1X0Z8Q/p1606317265094900 :
Dmitriy Kalinin:  5 hours ago
we have plans to switch to v1 CRD api and add schema for the CR fields which would catch this problem i believe.

Making a note for this issue that we should update docs for users who install kapp-controller via kubectl instead of kapp. If upgrading to a version of kapp-controller with the updated crd versions, it may not delete old versions of the crds. We should document how to remove these old versions as part of the installation docs.

Making a note for this issue that we should update docs for users who install kapp-controller via kubectl instead of kapp. If upgrading to a version of kapp-controller with the updated crd versions, it may not delete old versions of the crds. We should document how to remove these old versions as part of the installation docs.

After further investigating, this does not appear to be an issue for kubectl users as the newer crds versions will simply replace the older versions.


Add all the STM32 series targets

Thanks for adding the part numbers.
Only the STM32F412ZG had a part number before, and now it has a different number.
Where did you take it from?

The part number comes directly from the Reference Manual from ST.
RM0402 section 30.6.1 page 1127
https://www.st.com/content/ccc/resource/technical/document/reference_manual/group0/4f/7b/2b/bd/04/b3/49/25/DM00180369/files/DM00180369.pdf/jcr:content/translations/en.DM00180369.pdf

Oh, I now tried with a stm32f401 and I noticed that the part ID that I listed (0x433) doesn't match the part ID that is actually read (0x411). What I listed is the DEV_ID which is part of the IDCODE. The ID that is actually read is the Part In the PeripheraID from the romtable which is an entirely different thing.
The ID that is read seems highly unspecific (is it 0x411 for all STM32F4 ?)
I will have a deeper look at this when I find some time.
BTW: I initially messed up because I only tested on a STM32F103 for which both IDs are identical (0x410).

Thanks for your efforts! Very good find! We are not well versed here yet either and trying to find the best approach, so any insight is very welcome!
I myself would prefer a general approach instead of an STM32 specific one. But IDCODE is an ARM thing, so we could rely on that I think.
How do we want to handle this PR in the meantime? Go for the old PART approach and fix everything later, once we investigated this?

How do we want to handle this PR in the meantime? Go for the old PART approach and fix everything later, once we investigated this?

Maybe we could just skip entirely the PART for now and let user specify the chip they use instead of trying to auto-detect (until we find a proper auto-detection method).

Skipping the PART ID is ok for me, then we can look at automatic identification at a later point. I've created an issue so that we don't loose track of it.

Hey @aurelj we did a lot of changes on the algorithm format and in turn of that also regenerated the configs. So this PR has outlived it's purpose. I hope it's ok for you if I close this.
Thanks a ton for your work nevertheless :)

I'm trying to add support for the F3 series, I see there was a YAML for it in this PR but there doesn't appear to be one in master? What are the steps I'd need to take to add support?

@chocol4te Have a look at this: https://github.com/probe-rs/target-gen :) You need a Pack for your core (a good source is https://developer.arm.com/tools-and-software/embedded/cmsis/cmsis-search). target-gen --help should tell how it works. HINT: The input file/dir can either be the .pack file or a dir containing the unzipped .pack contents. The output dir must be an existing directory where it will put all the YAML files :)

@chocol4te Have a look at this: https://github.com/probe-rs/target-gen :) You need a Pack for your core (a good source is https://developer.arm.com/tools-and-software/embedded/cmsis/cmsis-search). target-gen --help should tell how it works. HINT: The input file/dir can either be the .pack file or a dir containing the unzipped .pack contents. The output dir must be an existing directory where it will put all the YAML files :)

Cheers, thank you!


migrate off UUIDs

OpenAI Assistants uses prefix-alphanumeric ID's and some libraries (like agency-swarm) depend on this https://github.com/VRSEN/agency-swarm/blob/94f79ca4d6bec95a866ffbb4b04e15210ec05e6e/agency_swarm/agents/agent.py#L345

https://github.com/datastax/astra-assistants-api/pull/42