Synthesis failed for CustomSearch

Hello! Autosynth couldn't regenerate CustomSearch. :broken_heart:
Here's the output from running synth.py:
2020-06-06 05:38:16,734 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-06 05:38:17,175 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-06 05:38:17,178 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-06 05:38:17,181 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-06 05:38:17,183 autosynth [DEBUG] > Running: git config push.default simple
2020-06-06 05:38:17,186 autosynth [DEBUG] > Running: git branch -f autosynth-customsearch
2020-06-06 05:38:17,189 autosynth [DEBUG] > Running: git checkout autosynth-customsearch
Switched to branch 'autosynth-customsearch'
2020-06-06 05:38:17,564 autosynth [INFO] > Running synthtool
2020-06-06 05:38:17,564 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/custom_search/synth.metadata', 'synth.py', '--']
2020-06-06 05:38:17,566 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/custom_search/synth.metadata synth.py -- CustomSearch
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-06 05:38:17,794 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-customsearch
nothing to commit, working tree clean
2020-06-06 05:38:19,663 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpt8l5otsp/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 CustomSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpt8l5otsp/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 CustomSearch
/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:38:53.486 [info]  FETCHING: https://www.googleapis.com/discovery/v1/apis/customsearch/v1/rest

12:38:53.623 [info]  FOUND: https://www.googleapis.com/discovery/v1/apis/customsearch/v1/rest
Revision check: old=20200511, new=20200604, generating=true
Creating leading directories
Writing Promotion to clients/custom_search/lib/google_api/custom_search/v1/model/promotion.ex.
Writing PromotionBodyLines to clients/custom_search/lib/google_api/custom_search/v1/model/promotion_body_lines.ex.
Writing PromotionImage to clients/custom_search/lib/google_api/custom_search/v1/model/promotion_image.ex.
Writing Result to clients/custom_search/lib/google_api/custom_search/v1/model/result.ex.
Writing ResultImage to clients/custom_search/lib/google_api/custom_search/v1/model/result_image.ex.
Writing ResultLabels to clients/custom_search/lib/google_api/custom_search/v1/model/result_labels.ex.
Writing Search to clients/custom_search/lib/google_api/custom_search/v1/model/search.ex.
Writing SearchQueries to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries.ex.
Writing SearchQueriesNextPage to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_next_page.ex.
Writing SearchQueriesPreviousPage to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_previous_page.ex.
Writing SearchQueriesRequest to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_request.ex.
Writing SearchSearchInformation to clients/custom_search/lib/google_api/custom_search/v1/model/search_search_information.ex.
Writing SearchSpelling to clients/custom_search/lib/google_api/custom_search/v1/model/search_spelling.ex.
Writing SearchUrl to clients/custom_search/lib/google_api/custom_search/v1/model/search_url.ex.
Writing Cse to clients/custom_search/lib/google_api/custom_search/v1/api/cse.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:38:54.016 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-06 05:38:57,104 synthtool [DEBUG] > Wrote metadata to clients/custom_search/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/custom_search/synth.metadata.
2020-06-06 05:38:57,136 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 CustomSearch. :sob:
Here's the output from running synth.py:
2020-06-07 05:34:06,875 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-07 05:34:07,357 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-07 05:34:07,360 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-07 05:34:07,369 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-07 05:34:07,372 autosynth [DEBUG] > Running: git config push.default simple
2020-06-07 05:34:07,375 autosynth [DEBUG] > Running: git branch -f autosynth-customsearch
2020-06-07 05:34:07,378 autosynth [DEBUG] > Running: git checkout autosynth-customsearch
Switched to branch 'autosynth-customsearch'
2020-06-07 05:34:07,766 autosynth [INFO] > Running synthtool
2020-06-07 05:34:07,766 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/custom_search/synth.metadata', 'synth.py', '--']
2020-06-07 05:34:07,768 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/custom_search/synth.metadata synth.py -- CustomSearch
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-07 05:34:07,985 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-customsearch
nothing to commit, working tree clean
2020-06-07 05:34:09,846 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpa5r0jf11/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 CustomSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpa5r0jf11/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 CustomSearch
/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:34:40.374 [info]  FETCHING: https://www.googleapis.com/discovery/v1/apis/customsearch/v1/rest

12:34:40.485 [info]  FOUND: https://www.googleapis.com/discovery/v1/apis/customsearch/v1/rest
Revision check: old=20200511, new=20200604, generating=true
Creating leading directories
Writing Promotion to clients/custom_search/lib/google_api/custom_search/v1/model/promotion.ex.
Writing PromotionBodyLines to clients/custom_search/lib/google_api/custom_search/v1/model/promotion_body_lines.ex.
Writing PromotionImage to clients/custom_search/lib/google_api/custom_search/v1/model/promotion_image.ex.
Writing Result to clients/custom_search/lib/google_api/custom_search/v1/model/result.ex.
Writing ResultImage to clients/custom_search/lib/google_api/custom_search/v1/model/result_image.ex.
Writing ResultLabels to clients/custom_search/lib/google_api/custom_search/v1/model/result_labels.ex.
Writing Search to clients/custom_search/lib/google_api/custom_search/v1/model/search.ex.
Writing SearchQueries to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries.ex.
Writing SearchQueriesNextPage to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_next_page.ex.
Writing SearchQueriesPreviousPage to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_previous_page.ex.
Writing SearchQueriesRequest to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_request.ex.
Writing SearchSearchInformation to clients/custom_search/lib/google_api/custom_search/v1/model/search_search_information.ex.
Writing SearchSpelling to clients/custom_search/lib/google_api/custom_search/v1/model/search_spelling.ex.
Writing SearchUrl to clients/custom_search/lib/google_api/custom_search/v1/model/search_url.ex.
Writing Cse to clients/custom_search/lib/google_api/custom_search/v1/api/cse.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:34:40.854 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-07 05:34:43,829 synthtool [DEBUG] > Wrote metadata to clients/custom_search/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/custom_search/synth.metadata.
2020-06-07 05:34:43,854 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 CustomSearch. :sob:
Here's the output from running synth.py:
2020-06-08 05:34:10,062 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-08 05:34:10,518 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-08 05:34:10,521 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-08 05:34:10,524 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-08 05:34:10,527 autosynth [DEBUG] > Running: git config push.default simple
2020-06-08 05:34:10,530 autosynth [DEBUG] > Running: git branch -f autosynth-customsearch
2020-06-08 05:34:10,533 autosynth [DEBUG] > Running: git checkout autosynth-customsearch
Switched to branch 'autosynth-customsearch'
2020-06-08 05:34:10,812 autosynth [INFO] > Running synthtool
2020-06-08 05:34:10,813 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/custom_search/synth.metadata', 'synth.py', '--']
2020-06-08 05:34:10,815 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/custom_search/synth.metadata synth.py -- CustomSearch
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-08 05:34:11,026 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-customsearch
nothing to commit, working tree clean
2020-06-08 05:34:12,565 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpjkc_t9v0/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 CustomSearch
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpjkc_t9v0/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 CustomSearch
/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:34:43.947 [info]  FETCHING: https://www.googleapis.com/discovery/v1/apis/customsearch/v1/rest

12:34:44.073 [info]  FOUND: https://www.googleapis.com/discovery/v1/apis/customsearch/v1/rest
Revision check: old=20200511, new=20200604, generating=true
Creating leading directories
Writing Promotion to clients/custom_search/lib/google_api/custom_search/v1/model/promotion.ex.
Writing PromotionBodyLines to clients/custom_search/lib/google_api/custom_search/v1/model/promotion_body_lines.ex.
Writing PromotionImage to clients/custom_search/lib/google_api/custom_search/v1/model/promotion_image.ex.
Writing Result to clients/custom_search/lib/google_api/custom_search/v1/model/result.ex.
Writing ResultImage to clients/custom_search/lib/google_api/custom_search/v1/model/result_image.ex.
Writing ResultLabels to clients/custom_search/lib/google_api/custom_search/v1/model/result_labels.ex.
Writing Search to clients/custom_search/lib/google_api/custom_search/v1/model/search.ex.
Writing SearchQueries to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries.ex.
Writing SearchQueriesNextPage to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_next_page.ex.
Writing SearchQueriesPreviousPage to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_previous_page.ex.
Writing SearchQueriesRequest to clients/custom_search/lib/google_api/custom_search/v1/model/search_queries_request.ex.
Writing SearchSearchInformation to clients/custom_search/lib/google_api/custom_search/v1/model/search_search_information.ex.
Writing SearchSpelling to clients/custom_search/lib/google_api/custom_search/v1/model/search_spelling.ex.
Writing SearchUrl to clients/custom_search/lib/google_api/custom_search/v1/model/search_url.ex.
Writing Cse to clients/custom_search/lib/google_api/custom_search/v1/api/cse.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:34:44.459 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-08 05:34:47,005 synthtool [DEBUG] > Wrote metadata to clients/custom_search/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/custom_search/synth.metadata.
2020-06-08 05:34:47,035 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:


SCM completion should have a setting to just insert the #NUMBER pattern

Currently, accepting an issue suggestion in the SCM input will insert the issue's title as well as the #NUMBER pattern. It would be great to just get the #NUMBER.

There's a setting for that :):
"githubIssues.issueCompletionFormatScm": "${issueNumberLabel}"


Python (3) code files with .py3 extensions are not detected or highlighted

Problem: the repo contains several code files in both Python2 and Python3. To distinguish between them we use .py extension for py2 and .py3 extension for py3. But GitHub doesn't highlight syntax in .py3 files and doesn't count them as code in python language (or any language in fact). This should be fixed.

Hey there,
There aren't too many files on GitHub that use the .py3 extension, so I'm afraid its usage isn't widespread enough for it to be added as a recognised Python extension.
However, you can tell GitHub those files are Python by using your repository's .gitattributes file:
*.py3 linguist-language=Python

Syntax highlighting can also be set using Vim or Emacs modelines. =)
# vim: ft=python
# -*- python -*-

@Alhadis unfortunately, it's not proper solution, at least for my case. These files shouldn't contain any extra comments (for the purpose they are used), and there probably will be quite a few of them in the future.
.gitattibutes solution would be OK, if it affected the highlighting, since it's the main thing that is lacking.
I've seen some PRs/discussions that involve some heuristics to determine the language in the file in this repo, but my problem doesn't require such hackery.
As demonstrated by the github search .py3 is used, although not that frequent, for the sole purpose of python code files. So there shouldn't be any conflict which may cause wrong detection. IIUC, all that's needed is too add it to known python language extensions list (which is already quite large and pervasive if I found the right place to look).

@Alhadis Do you have an estimate of the number of repositories using the .py3 extension?

Sorry, I meant to address this earlier today, but got distracted.
The 1895 py3 files on GitHub are distributed among 392 repositories by 366 users. On second thought, I'd say that's adequate enough distribution to warrant being included as an extension.

@danilaml You can open a pull request by following the guidelines. There seem to be enough usage on github.com to warrant support of the extension. That being said, we'll still need a :+1: on the pull request from one GitHub's maintainers to confirm.

I was just wondering - how long does it usually take for changes to apply (i.e. when it'll start indexing .py3 files as python)?

It'll be visible in the next release of Linguist. =) New releases are cut every few weeks, so it might be a week or two before you see changes. I'm not sure exactly when the next release is due, however.

Thanks, good to know.

https://stackoverflow.com/a/77460424/9731176


Better error message in Orbit.from_sbdb

Address #916

Not blocking this because of the numba failures. Merging!


icudt61.dll required

starting the TSEMO Example, I get the following error
"....TS-EMO-master\Mex_files\invchol\invChol.mexw64': Missing dependent shared
libraries:
'icudt61.dll' required by"
'....\Mex_files\invchol\invChol.mexw64'
Can you help me with this or is this rather a problem of my Matlab version (19a) ?

The Matlab version is fine. If I had to make an educated guess, you might be running 32 bit Matlab? Either way try one of the following that should fix it:

Compile the mex file yourself, then the dependable files will suit your system. In the same folder you can find "invChol_mex.c". Just follow the steps on the Matlab website to compile this file (https://www.mathworks.com/help/matlab/ref/mex.html), I think it is just "mex invChol_mex.c". Once compiled, simply rename the new file to "invChol" and delete the previous file (invChol.mexw64).

Just delete the file "invChol.mexw64", then Matlab will use the .m file instead (invChol.m). This is an easier solution, but it will be slightly slower than using the .mex file.

I tried your 2. solution and it worked! Thanks a lot!


The method for providing platform translations has changed in Home Assistant Core

The method for providing platform translations has changed in Home Assistant Core, and this integration needs to be updated.
Details can be found in https://developers.home-assistant.io/blog/2024/03/05/platform_entity_translations_deprecation

Thanks! This is already supported for en language.


Run through competition and make sure B4A can handle it

Go through the WW challenges for 2018 and using VoiceOver/disabled screen, make sure B4A can handle all the challenges

katie did a few run throughs, all issues are now in github, closing


NewsAPI integration

Obsei have google news search but google impose rate limit on it also it does not search any article older than 7 days. Hence having NewsAPI  integration will provide user this capability.

Closing it as current Google News integration sufficient.
We may revisit in the future if need ariase


no rule to make target mpbuild

Hi Jiawei,
I am trying to run a geosfp_2x2.5_standard run on AWS. I've followed the instructions given here (https://cloud-gc.readthedocs.io/en/latest/chapter02_beginner-tutorial/research-workflow.html#get-source-code-and-checkout-model-version) including making a GC directory, downloading the source code and Unit Tester, and changing the copyrundirs.input file with the appropriate information (GCGRID_root, data_root, etc.).
I went into the run directory and tried to compile (make realclean worked, make -j4 mpbuild NC_Diag gave an error).
Do you have any thoughts why this may have happened?
Best,
Raj

Which model version do you use? Did you checkout the proper version by git checkout 12.1.0, for both source code and unit tester?

If you are using the 12.6.0 AMI, you can use “make -j4 build”.  That was changed in I think 12.4.0 and higher.  Sorry about that, I did not get around to updating the doc yet (we are all a bit slammed here this week).
Get Outlook for iOShttps://aka.ms/o0ukef

From: Jiawei Zhuang<EMAIL_ADDRESS>Sent: Wednesday, October 30, 2019 8:15:06 PM
To: geoschem/geos-chem-cloud<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [geoschem/geos-chem-cloud] no rule to make target mpbuild (#31)
Which model version do you use? Did you checkout the proper version by git checkout 12.1.0, for both source code and unit tester?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoschem_geos-2Dchem-2Dcloud_issues_31-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DABM3T2FFXGJHI6BYCFKYAIDQRIPQVA5CNFSM4JHB5KU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWFJ6Q-23issuecomment-2D548164858&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=XTJBopAzwSsAgEljIk6g1TdJEZxb_bVLEjVNpBxfBIw&m=fW-skIF3gIZMITLEDgNdGqxcIrrVVWLAplqyo-Yq-ew&s=huC1Wpd-nuFeVM7YECgftMN32xw35_V89vnqKaw1RuQ&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABM3T2FAYZTLGRBEEA54X6TQRIPQVANCNFSM4JHB5KUQ&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=XTJBopAzwSsAgEljIk6g1TdJEZxb_bVLEjVNpBxfBIw&m=fW-skIF3gIZMITLEDgNdGqxcIrrVVWLAplqyo-Yq-ew&s=SHdnbLsFa3S9Tt_QUw0TW9BMpoCNKnziCbF_DlCn2qw&e=.

Thank you Jiawei and Bob!
The "make -j4 build" command works for me and the code is compiling.
~Raj

Glad to see this!

Also, you can always type “make help” for a list of compilation options.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Jiawei Zhuang<EMAIL_ADDRESS>Sent: Thursday, October 31, 2019 9:33:43 AM
To: geoschem/geos-chem-cloud<EMAIL_ADDRESS>Cc: Yantosca, Robert M<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [geoschem/geos-chem-cloud] no rule to make target mpbuild (#31)
Glad to see this!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoschem_geos-2Dchem-2Dcloud_issues_31-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DABM3T2DC5PQW57FJVIVDZDTQRLNDPA5CNFSM4JHB5KU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXZDTY-23issuecomment-2D548377039&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=XTJBopAzwSsAgEljIk6g1TdJEZxb_bVLEjVNpBxfBIw&m=vKRCejPeEPAqS1mQMeegxcusnqqlbEOqmdHYkYmgIfs&s=mwVZw2P6-GQ4Kj_fY0NH90BGBr6Wybe1achsgZ5-_sU&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABM3T2FDUOIW37F6CICRSFLQRLNDPANCNFSM4JHB5KUQ&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=XTJBopAzwSsAgEljIk6g1TdJEZxb_bVLEjVNpBxfBIw&m=vKRCejPeEPAqS1mQMeegxcusnqqlbEOqmdHYkYmgIfs&s=KUPgVxhQQVSnjUE8BoEqXvXL_5_UOhmpdGW25ecqIHw&e=.

Hi Raj,
What version of GEOS-Chem are you using? In newer versions of GEOS-Chem the build commands have changed. Type ‘make help’ to see the options. You may need to use build rather than mpbuild.
Best,
Lizzie
--
Lizzie Lundgren
Senior Scientific Programmer
GEOS-Chem Support Team
geos-chem-support<EMAIL_ADDRESS>Please direct all GEOS-Chem support emails to the entire GEOS-Chem Support Teamhttp://wiki.geos-chem.org/GEOS-Chem_Support_Team. If you are reporting a bug, please create an issue on GitHubhttps://github.com/geoschem/.
From: RajMLal<EMAIL_ADDRESS>Reply-To: geoschem/geos-chem-cloud<EMAIL_ADDRESS>Date: Wednesday, October 30, 2019 at 7:55 PM
To: geoschem/geos-chem-cloud<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [geoschem/geos-chem-cloud] no rule to make target mpbuild (#31)
Hi Jiawei,
I am trying to run a geosfp_2x2.5_standard run on AWS. I've followed the instructions given here (https://cloud-gc.readthedocs.io/en/latest/chapter02_beginner-tutorial/research-workflow.html#get-source-code-and-checkout-model-versionhttps://urldefense.proofpoint.com/v2/url?u=https-3A__cloud-2Dgc.readthedocs.io_en_latest_chapter02-5Fbeginner-2Dtutorial_research-2Dworkflow.html-23get-2Dsource-2Dcode-2Dand-2Dcheckout-2Dmodel-2Dversion&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=mIqQPIUGGaUoZjGqxkCAPMGs7WqKwQ7FdbYMfyHRfFA&s=96yx9VdcvusjhC-Pq5tMasRyy1tfk-r9oOjjHcwqwX4&e=) including making a GC directory, downloading the source code and Unit Tester, and changing the copyrundirs.input file with the appropriate information (GCGRID_root, data_root, etc.).
I went into the run directory and tried to compile (make realclean worked, make -j4 mpbuild NC_Diag gave an error).
Do you have any thoughts why this may have happened?
Best,
Raj
[Image removed by sender. mpbuild error]https://urldefense.proofpoint.com/v2/url?u=https-3A__user-2Dimages.githubusercontent.com_57201024_67907687-2D28fa6f00-2Dfb4f-2D11e9-2D8543-2D0368594c336a.png&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=mIqQPIUGGaUoZjGqxkCAPMGs7WqKwQ7FdbYMfyHRfFA&s=w0ummcRQlM0TfgOgLqvW73ELmrfXWW5ra9DA0nHj0s4&e=
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_geoschem_geos-2Dchem-2Dcloud_issues_31-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAAE7FK5UUJFY6FTEEGQYFG3QRINFZA5CNFSM4JHB5KU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HVTD64A&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=mIqQPIUGGaUoZjGqxkCAPMGs7WqKwQ7FdbYMfyHRfFA&s=fv3smekBLXqcVRzB3-HyLgh_WD8UXNAHPgcPIa_T6m8&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAE7FKZQ3COT55FE5P2I3VLQRINFZANCNFSM4JHB5KUQ&d=DwMCaQ&c=WO-RGvefibhHBZq3fL85hQ&r=xyVOGV-4mAPz62S8RZON4khwZesGKcGg2_BHL4y5NjQ&m=mIqQPIUGGaUoZjGqxkCAPMGs7WqKwQ7FdbYMfyHRfFA&s=ZEo5yUvNBpWGLf3QCPHpzPEkZd_ESkEUeVxhw_Vih4E&e=.


Emit signer event for all transactions

Describe your changes and provide context
Emit event that indicate the signer(s) of a transaction in both Sei address and EVM address
Testing performed to validate your change
local sei

Codecov Report
Attention: Patch coverage is 60.00000% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 61.62%. Comparing base (b36bfe4) to head (76248a1).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1651      +/-   ##
==========================================
+ Coverage   61.61%   61.62%   +0.01%
==========================================
  Files         367      367
  Lines       26620    26629       +9
==========================================
+ Hits        16401    16410       +9
+ Misses       9128     9127       -1
- Partials     1091     1092       +1

Files
Coverage Δ

x/evm/ante/preprocess.go
76.44% <60.00%> (-0.33%)
:arrow_down:

... and 2 files with indirect coverage changes


Rebuild

Should help with the py38 migration.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Expose deploymentId of created or updated application to be used in deployment monitoring

There are certain situations when after requesting a deployment of an application to the Marathon cluster we need to wait certain amount of time till the deployment finished before we can query another API call in the context of this application e.g. some metadata (hostname, port) about the deployment. We were trying to use this scenario - see: https://github.com/holidaycheck/marathon-maven-plugin/pull/1#issuecomment-121939044 - but since we do not have currently support to obtain deploymentId when creating or updating an application, we ended up with heuristics like this one: https://github.com/holidaycheck/marathon-maven-plugin/blob/fac26f9d6f837604f911ac1513ac4d12479bce5c/src/main/java/com/holidaycheck/marathon/maven/AppTasksMojo.java#L78 (contributed by @bsneade)
In order to make it more reliable and not to use timeout-based approach some changes would need to be applied (still their validity is to be discussed probably) to this project to support the approach based on deploymentId monitoring.
Application creation API:
https://mesosphere.github.io/marathon/docs/rest-api.html#post-/v2/apps
returns:
"deployments": [
    {
        "id": "f44fd4fc-4330-4600-a68b-99c7bd33014a"
    }
]

element
Application update API:
https://mesosphere.github.io/marathon/docs/rest-api.html#put-/v2/apps/{appid}
returns:
"deploymentId": "83b215a6-4e26-4e44-9333-5c385eda6438"

element.
This can be used by checking the result of this call:
https://mesosphere.github.io/marathon/docs/rest-api.html#get-/v2/deployments
and looking for deploymentId in:
"affectedApps": [
    "/test"
],
"id": "867ed450-f6a8-4d33-9b0e-e11c5513990b",

element.
Currently in marathon-client we have https://github.com/willroden/marathon-client/blob/5c33bfc8296678aef95ef9a19c79498a64c2a306/src/main/java/mesosphere/marathon/client/Marathon.java#L36
for application creation and https://github.com/willroden/marathon-client/blob/5c33bfc8296678aef95ef9a19c79498a64c2a306/src/main/java/mesosphere/marathon/client/Marathon.java#L39 for updating the application.
We are missing deploymentIds in returned types, e.g. creation returns https://github.com/willroden/marathon-client/blob/5c33bfc8296678aef95ef9a19c79498a64c2a306/src/main/java/mesosphere/marathon/client/model/v2/App.java
(doesn't contain deploymentIds) and update return type is void currently.
We already have deployments request https://github.com/willroden/marathon-client/blob/5c33bfc8296678aef95ef9a19c79498a64c2a306/src/main/java/mesosphere/marathon/client/Marathon.java#L70
and the model returned https://github.com/willroden/marathon-client/blob/5c33bfc8296678aef95ef9a19c79498a64c2a306/src/main/java/mesosphere/marathon/client/model/v2/Deployment.java#L10 contains ID of deployment to match on.

I've been away and just saw this.  I'll look at it in detail shortly.

Thanks to @bsnead's pull request.  This is implemented in 0.4.8 which should be in maven central very shortly.


Moved serialization of Cookie to Cookie.

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
yes/no

Tests pass?
yes

Fixed issues
#13135

Note that this also adds support for non-string values in cookies (when validation is enabled).
Should this be expanded so that cookies can contain any kind of data in all cases?
(Basically always serialize / unserialize regardless of validation?)

I think an exception for scalar values is made for cookies which are meant to be used via JavaScript.

I think an exception for scalar values is made for cookies which are meant to be used via JavaScript.

What do you mean?

If the value is not an array, it's not encoded in any special way. That is for using it without decoding.

Are you sure?
https://github.com/yiisoft/yii2/blob/master/framework/web/Response.php#L397
I don't see that happening anywhere; as far as I can tell if cookie validation is enabled cookies get encoded.

You're right.

@samdark This one could be ready for merge, maybe. 8-)

I wonder how would that work with existing cookies set with data which was passed through old serialize()/unserialize()?

That's the main reason I was suggesting it for 2.1.x

Well those cookies would be come "invalid", meaning users lose whatever data is stored in there.
I don't feel it's a big issue, since users sessions tend to get remove whenever you do an upgrade anyway (that's what I do at least). And logging in again is not a big hassle.
Other than that, cookies that are used for preferences (like grid view settings) tend not to be validated anyway since they are changed via client side code.
Up to you which one you prefer, I'm in no rush to get this merged, just want it to be finished so it no longer needs a spot on my todo list.

Cookies may hold more than sessions.

Changing Cookie serialization from PHP serialize() to JSON can not be done at 2.0.x as it causes a BC break: all existing Cookies in particular Yii-based will stop function after such update.

I do not like the idea: processing of the Cookie value is still depends on Request and Response since they  use Security to process the hash.
It would be more consistent to keep all fucntionality related to hash composition at single place rather then extend it to the extra class.

Well validation of user data is part of the request object, so that makes sense in my opinion.
Just like formatting the response is part of the response object.

Note that all this 'cookie data string' support exists only because of necessity of cookie value protection, which is introduced and configured(!) at Request/Response level. Changes proposed here looks like encapsulation break to me.

I can see absolutely no benefit in proposes changes - just a redundant overcomplication of code.

The serialization is not only for cookie protection, it also enables use of complex cookie values.

The serialization is not only for cookie protection, it also enables use of complex cookie values.

I can not see any complex valu handling in your PR. Besides what prevent us to simply use Json methods instead of PHP serialize()/unserialize() and Request and Response? Why there is a necessity of instroduction of extra methods at Cookie class?

Because it should be the cookies'  responsibility to handle its serialization / deserialization.
Discuss this with the team make a decision, I've got no more arguments to add.

Because it should be the cookies' responsibility to handle its serialization / deserialization.

It would be so in case I can use single Cookie class to get/set complex cookie value, like following:
$cookie = Cookie::parse($_COOKIES['someComplexValue']);
var_dump($cookie->value);

but this code can not function since cookie value may contain security hash, which handled and configured at Request class.
In case there is no way to provide clear interface for cookie serialization/unserializion and single Cookie class value - why should we create a half-solution methods at Cookie class? Those will just confuse the developer, which expects it handles it all - while it does not take security hash into account.
Creating those methods just because 'it seems they should be there' does not seem right.
Either entire Cookie value processing including security hash should be moved inside the Cookie class - or it should remain intact.

Look at the tests..
It will work just fine like this:
$cookie = new Cookie();
$cookie->value = ['abc', 'def'];
$cookie->name = test;

This cookie can be serialized and unserialized by the request / response object, or other code.

The raw value, which includes security hash, can not be parsed.

It only includes the security hash if it was signed by the Response. If you add it manually as you propose then it'll work without.
Your argument does not make sense. I could use it for any encryption / signing library, arguing that when encrypting data it does not work unless decrypted....
Of course if you sign the data and thus change it you have to undo that change, which is what the Request and Response objects do.
If you bypass them, the cookie serialization part will work just fine without it.

Your argument does not make sense. I could use it for any encryption / signing library, arguing that when encrypting data it does not work unless decrypted....

Cookies, which submitted per request are built and processed by Request class, which handles thier unserialization and decryption.
Standalone unserialization without decryption of the Cookie value make a little sence.
The only use case, in which I may want to unserialize some Cookie value on my own is getting this value from raw request, but in this case this value will contain the security hash in it.
Can you describe the use case, in which you get some random Cookie string value and want to unserialize it, but can be sure its value is secure and decrypted?

Can you describe the use case, in which you get some random Cookie string value and want to unserialize it, but can be sure its value is secure and already decrypted?

When I use any other implementation than the default Request / Response class.
Note that "being sure" is not really relevant here. Can you be sure no developer will subclass Response but not Request and guarantee that they still use the same scheme for validation? (No you can not)

When I use any other implementation than the default Request / Response class.

This is exactly the case - if you wish the Cookie ecryption/serialization change - you need to override Request/Response classes pair - this is the only consistent solution I see for such task. During such implementation another way for cookie serialization can be used as well.

Can you be sure no developer will subclass Response but not Request and guarantee that they still use the same scheme for validation?

When it comes to override existing core functionality developer is responsible for its results. I can not see how new methods in Cookie class ensures anything in this field - who can garantee developer will use those methods, while creating its own Cookie protection solution?
Yii is not a Symfony and it does not follow SOLID methodology - we do not introduce a new abstraction layer just because we have found a potential place for it.

I think it’s useful to extract a Cookie serialization completely, so it can be swapped without the need to touch Request/Response (like using JWT for signing/validation).

I think in this case serialization should be extracted as @sergeymakinen suggested.

Signing and validation will require configuration though.
Currently that is set in the Request component (cookieValidationKey).
I think serialization (transformation from complex to string) is a separate step from signing (transformation from string to protected string).
I agree that signing should be removed from Request / Response, but it should not be in Cookie; since cookies are not the only thing you can / could sign, you could sign any piece of data that you want to send to the client and get back in a later request. (For example, hidden form field).
That said, this is a first step to separate the serialization part, feel free to make the next step and make a PR for it...
This PR does what I want it to do, if you don't want that in the framework that's fine, close this issue. If you do want it but see improvements for the future I suggest we create a separate issue for that and mark this as "ready to merge into 2.1".

As @klimov-paul noted, that's significant enough to go to 2.1. I like these changes overall so would not vote for not accepting the pull request.

Won't be merged into 2.0.


EV notebook

The data for each Notebook will consist of one-second interval data for a subset of homes with complete data over a one-year period. The Notebook will be pre-populated with analysis and visualization code to help researchers understand the value of Dataport data and how to work with it. The analysis and visualization codes will answer the following questions for each relevant Notebook:
EV Notebook:
Included data:
• One-minute interval EV charging and whole home energy use data for 25 homes
• 4CP timing for 2016-2019 in Texas
• 6 months of solar production data from the same homes from March – August 2018
Queries and visualizations will allow users to evaluate:

How does at-home EV charging align with the State of Texas’s critical peak power events? EV charging alignment with 4CP in Texas.

How much are people actually charging their vehicles during those events?

How does at-home EV charging align with rooftop solar generation and what percent of the EV charging energy load is powered by the home’s rooftop solar over one year? (what percent of the EV charging load is powered by solar? that's probably pretty low) (look at ave charging curve and solar curve and put them together. )

What percent of a home’s overall energy demand is attributable to at-home EV charging? On a yearly basis how much energy is being used, what percentage is going into the EVs.


Best-Practice for default component styling

I have recently started using svelte and as a long-time bootstrap user, I love using sveltestrap. However, I was wondering if there is a best practice for styling default sveltestrap components. Let's take a bit a sample code (from the documentation) as an example:
Supposed I have a card like this:
<Card>   <CardBody>Hello World</CardBody> </Card>
Is it possible to access this <Card></Card> component in order to style it? I have tried to access it like so:
<style> .card {   background: red; } </style>
Predictably, this fails as the compiler is too smart as to include "unused" styles. Is there a standard way of accessing default component styles? Must I assign a class to each component? To me, this solution seems odd as it sort of defeats the purpose of component-level-styles?

Hi @Conceptiks , it depends on what you would like to accomplish.
If you need to do a quick override for a component or two, you can do this:
<style>
  :global(.card) {
    background: red;
  }
</style>

The :global(...) is required by svelte otherwise it's scoped with some generated class name. You can read more here:
https://svelte.dev/docs#style
But if you want to change your entire app's theme to match company branding, etc this is not the way to go.  You should instead look into making/using a custom Bootstrap theme so that lots of styles/overrides aren't built into your JavaScript code.
Hope this helps.

Closing, please comment if not resolved for you.


Make SpatialAccessor._get_weights() and TemporalAccessor._get_weights() public

Description

Summary of Changes

Closes #251
Add default None value for lat_bounds and lon_bounds keyword args to SpatialAccessor.get_weights()
Delete redundant tests for private methods in test_spatial.py (related to #242)

It is usually a code smell to test the implementation details for public interfaces

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

If applicable:

[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass with my changes (locally and CI/CD build)
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

I have no objection to making get_weights() public, though I didn't fully understand the the changes to the unit tests. Should I view the changes in tests/ as a reorganization or something that I should review more carefully?

I addressed this comment in one of the PR review comments.

I think the error for test_weights_for_region_in_lon_domain_with_both_spanning_p_meridian is correct and we should represent the problematic line as ds.lon_bnds.data[:] = np.array([[-1, 1], [1, 90], [90, 180], [180, 359]]).

I ended up removing tests where the domain bounds has a larger left hand value than right hand value because they are supposed to throw an error, rather than pass.  There's already a test to check that an error is thrown for this case.
I kept test_weights_for_region_in_lon_domain_with_region_spanning_p_meridian since regions can have a larger lower bound vs. upper bound.

Codecov Report

Merging #252 (d4a49f1) into main (1fdc8a9) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #252   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         8    -1
  Lines          742       727   -15
=========================================
- Hits           742       727   -15

Impacted Files
Coverage Δ

xcdat/axis.py
100.00% <ø> (ø)

xcdat/utils.py
100.00% <ø> (ø)

xcdat/__init__.py
100.00% <100.00%> (ø)

xcdat/bounds.py
100.00% <100.00%> (ø)

xcdat/dataset.py
100.00% <100.00%> (ø)

xcdat/spatial.py
100.00% <100.00%> (ø)

xcdat/temporal.py
100.00% <100.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 223e73b...d4a49f1. Read the comment docs.

Hi @pochedls, @lee1043, and @chengzhuzhang, instead of making _get_weights() public for temporal averaging so the user can get weights, I implemented a keep_weights keyword argument to the temporal averaging APIs. This gives users the choice with whether or not they want to couple time_weights with its related output.

Option
Make _get_weights() public
Option to keep time_weights in the output xr.Dataset

Pros
* User can calculate weights independently of temporal averaging, which makes it faster to get weights instead of running temporal averaging first (do scientists normally calculate weights independently? does CDAT allow have a method for this?)
* Makes sense to couple the weights to its related averaging output * Implementation is straightforward, just add the time_weights DataArray to the final output Dataset                         * User has the option to not include the weights in the output

Cons
* User needs to provide the same arguments as temporal averaging APIs (data_var, mode, freq, season_config) which makes the method less intuitive to implement and use * Weights are decoupled from the output, which removes context on how they should be used for averaging* We don't accept weights in our temporal averaging APIs right now (does it make sense to?)
* For group_average and climatology we must append "_original" to the name of time_weights time dimension/coordinates since datasets share dimensions and coordinates. Otherwise, it will use the reduced  timedimension/coordinates (not correct, will result in  np.nan weights)

Example for ds.temporal.climatology():
https://github.com/xCDAT/xcdat/blob/44620c0953350fffa4df69c1ae2050088d31f058/xcdat/temporal.py#L332-L339
https://github.com/xCDAT/xcdat/blob/44620c0953350fffa4df69c1ae2050088d31f058/xcdat/temporal.py#L742-L745
Example for ds.temporal.departures()
https://github.com/xCDAT/xcdat/blob/44620c0953350fffa4df69c1ae2050088d31f058/xcdat/temporal.py#L624-L627
https://github.com/xCDAT/xcdat/blob/44620c0953350fffa4df69c1ae2050088d31f058/xcdat/temporal.py#L465-L472
_keep_weights() method:
https://github.com/xCDAT/xcdat/blob/44620c0953350fffa4df69c1ae2050088d31f058/xcdat/temporal.py#L1369-L1402
If this looks good, we can implement keep_weights with the spatial averaging API as well.

Hi @tomvothecoder Thank you for the discussion. I don't recall that I have a use case that requires to get/keep the weights to pass down to another operation. With the exception that, they are useful to be examed during xcdat development/validation. So I don't have strong opinion on the implementation, maybe keeping it private is fine. I will defer to Steve and Jiwoo.

I like keep_weights. I didn't totally understand the downside for keep_weights: why can't we just overwrite the original time_weights? Are both the full time series and the climatology time series saved in the dataset when calculating a climatology?
I think it would be good to keep .get_weights in spatial averaging, though I don't object to adding a keep_weights in that routine. One thing that might confuse people is that the weights we generate for spatial averaging are 2D (we never explicitly generate a time resolved weighting matrix).

I like keep_weights. I didn't totally understand the downside for keep_weights: why can't we just overwrite the original time_weights?

There is only one time_wts generated using the time_bounds, which is saved in the Dataset when keep_weights=True. I'm not sure what you mean by overwriting the original time_wts.
Keeping weights with Climatology

time_wts uses the original time coordinates, so it CANNOT share the reduced time dimension and coordinates from the climatology data variable.

"time_original" is the original time dimension (1919 coord pts)
"time" is the reduced time dimension (4 coord pts)

ds.temporal.climatology("tas", freq="season", weighted=True, keep_weights=True)

<xarray.Dataset>
Dimensions:        (lon: 320, nv: 2, lat: 160, bnds: 2, time: 4,
                    time_original: 1919)
Coordinates:
  * lon            (lon) float64 0.0 1.125 2.25 3.375 ... 356.6 357.8 358.9
  * lat            (lat) float64 -89.14 -88.03 -86.91 ... 86.91 88.03 89.14
  * time           (time) object 0001-01-01 00:00:00 ... 0001-10-01 00:00:00
  * time_original  (time_original) datetime64[ns] 1850-01-16T12:00:00 ... 200...
Dimensions without coordinates: nv, bnds
Data variables:
    lon_bounds     (lon, nv) float64 dask.array<chunksize=(320, 2), meta=np.ndarray>
    lat_bounds     (lat, nv) float64 dask.array<chunksize=(160, 2), meta=np.ndarray>
    lon_bnds       (lon, bnds) float64 -0.5625 0.5625 0.5625 ... 358.3 359.4
    lat_bnds       (lat, bnds) float64 -89.7 -88.59 -88.59 ... 88.59 88.59 89.7
    tas            (time, lat, lon) float64 dask.array<chunksize=(1, 160, 320), meta=np.ndarray>
    time_wts       (time_original) float64 0.002038 0.002038 ... 0.002083

Keeping weights with Departures

time_wts uses the original "time" dimension and coordinates, which are maintained from the departures data variable so they can be shared.
Notice there is no "time_original" dim or coords

ds.temporal.departures("tas", freq="season", weighted=True, keep_weights=True)

<xarray.Dataset>
Dimensions:     (lon: 320, nv: 2, lat: 160, time: 1919, bnds: 2)
Coordinates:
  * lon         (lon) float64 0.0 1.125 2.25 3.375 ... 355.5 356.6 357.8 358.9
  * lat         (lat) float64 -89.14 -88.03 -86.91 -85.79 ... 86.91 88.03 89.14
  * time        (time) datetime64[ns] 1850-01-16T12:00:00 ... 2009-11-16
Dimensions without coordinates: nv, bnds
Data variables:
    lon_bounds  (lon, nv) float64 dask.array<chunksize=(320, 2), meta=np.ndarray>
    lat_bounds  (lat, nv) float64 dask.array<chunksize=(160, 2), meta=np.ndarray>
    time_bnds   (time, bnds) datetime64[ns] 1850-01-01T18:00:00 ... 2009-12-0...
    tas         (time, lat, lon) float64 dask.array<chunksize=(2, 160, 320), meta=np.ndarray>
    lon_bnds    (lon, bnds) float64 -0.5625 0.5625 0.5625 ... 358.3 358.3 359.4
    lat_bnds    (lat, bnds) float64 -89.7 -88.59 -88.59 ... 88.59 88.59 89.7
    time_wts    (time) float64 0.002038 0.002038 0.002059 ... 0.002083 0.002083

Are both the full time series and the climatology time series saved in the dataset when calculating a climatology?
Only the climatology time series is stored in the climatology output.

I think it would be good to keep .get_weights in spatial averaging, though I don't object to adding a keep_weights in that routine.

Sounds good, I added keep_weights as a keyword argument to ds.spatial.average().

One thing that might confuse people is that the weights we generate for spatial averaging are 2D (we never explicitly generate a time resolved weighting matrix).

Hmmm, we can address this if users open up an issue about it, unless you think it is worth addressing now.

Got it – thanks Tom.


New package: Samsung.Gear360ActionDirector version 1.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/111988&drop=dogfoodAlpha

Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest. actual 'manifests\s\Samsung\Gear360ActionDirector\1.0', expected 'manifests\s\Samsung\Gear360ActionDirector\<IP_ADDRESS>31'

Is this 1.0 or <IP_ADDRESS>31?

Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest. actual 'manifests\s\Samsung\Gear360ActionDirector\1.0', expected 'manifests\s\Samsung\Gear360ActionDirector\<IP_ADDRESS>31'

Is this 1.0 or <IP_ADDRESS>31?

<IP_ADDRESS>31 is what is written to Control Panel

Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest. actual 'manifests\s\Saung\Gear360ActionDirector\1.0', expected 'manifests\s\Saung\Gear360ActionDirector\<IP_ADDRESS>31'

/AzurePipelines run

/AzurePipelines run

Automatic Validation ended with:

Automatic Validation ended with:

Appears to be Interactive Only.

[Policy] Interactive-Only-Installer


Incorrect ratio::abs() behavior for INTMAX_MIN

https://github.com/DymOK93/KTL/blob/master/include/ratio.hpp#L9

Seems it is a common implementation across main STL implementations.
Moreover it is an implementation detail, that is not available for direct usage. Maybe it is not quite necessary to fix such behaviour. Well, actually there's no good way to fix it without assigning a value to another type (e.g. uintmax_t)
Using unsigned type seems to be a good solution, because an absolute value is always non-negative, but what about semantics and expectations? As I can see, the result of details::abs is compared or assigned to a variable of a signed type. This case could be broken in such a way. Actually it is broken even now, but now it is a compile-time error and it is ok.

Yes, that's right - STL implementations (MS STL for example) have the same bug and I don't consider it dangerousю

Closed by #132


[Windows] "'C:\Program' is not recognized as an internal or external command, operable program or batch file."

<EMAIL_ADDRESS>binary version: 96c499d9956096a0f06d01f0e6fdf6e90ce89c24
init wizard selection: Blank project > SQLite > Confirm (with both) > JavaScript > Demo script leads to:
C:\Users\Jan\Documents\throwaway>prisma2 init p2WinTest4

Preparing your demo script (JavaScript) ...

Preparing your demo script (JavaScript) ...

✔  Downloading the demo script from GitHub ...
✔  Extracting content to p2WinTest4 ...
✔  Installing dependencies with: `npm install` ...
⠋  Preparing your database ...
 ERROR  Error during command execution

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

This points to some exec/spawn using a non quoted / not shell escaped path of an executable (e.g. node and npm are installed in C:\Program Files\nodejs for me, but could also be binary or something like that).

This case the script is using the CLI itself, which in this case is:
C:\Users\Jan\Documents\throwaway>where prisma2
C:\Program Files\nodejs\prisma2
C:\Program Files\nodejs\prisma2.cmd

I also get this, however, if you select "just the prisma schema" instead of "demo script" in the last option, it seems to work
I assume there's an issue with the script installation process on windows, as all the other demo scripts also cause the same error

I'm facing this same issue, while I also stuck with "just the prisma schema" option.. It just says Processing the blank project.
I'm using Windows 10 and powershell

while I also stuck with "just the prisma schema" option.. It just says Processing the blank project.

Please open a new issue for that separate problem.
We are actively working on fixing this one here.

@timsuchanek i just uninstalled prisma2 on windows, and reinstalled. Then I ran prisma2 init and chose the GraphQL API starter kit. Again, I see this output:

✔  Downloading the starter kit from GitHub ...
✔  Extracting content to ./ ...
✔  Installing dependencies with: `npm install` ...
⠋  Preparing your database ...
5  Seeding your database with: `npm run seed` ...
 ERROR  Error during command execution

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

npm i -g<EMAIL_ADDRESS>I can repro on this version, re-opening till we figure out the alpha publishing/further fix.

@divyenduz i just realized - maybe the Windows patch was not included in the 2.0.0-alpha.204 version?

Yes @brunocrosier, that is our current thinking there. Still investigating.

@janpio I just tried npm i -g<EMAIL_ADDRESS>(which I assume has the proposed windows fix) and encountered the same issue.

Then this assumption is probably not true - or the fix didn't work. We don't know yet and are still investigating.

Confirmation that the problem still exists in alpha.205:
C:\Users\Jan\Documents
λ npm install -g prisma2@alpha
C:\Program Files\nodejs\prisma2 -> C:\Program Files\nodejs\node_modules\prisma2\build\index.js

><EMAIL_ADDRESS>install C:\Program Files\nodejs\node_modules\prisma2
> node download-build/index.js || echo ""

> Downloading windows binary [====================] 100%

+<EMAIL_ADDRESS>updated 1 package in 13.781s

C:\Users\Jan\Documents
λ cd throwaway\

C:\Users\Jan\Documents\throwaway
λ prisma2 init 531

Preparing your demo script (JavaScript) ...

✔  Downloading the demo script from GitHub ...
✔  Extracting content to 531 ...
✔  Installing dependencies with: `npm install` ...
⠋  Preparing your database ...
 ERROR  Error during command execution

'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

This should be fixed now in the just release preview-13.

Congrats! Can confirm this error is fixed. There is another issue relating to Windows though which I have just opened: #614


On using withCString

I was looking through C++ code and found that it assumes its text data is in UTF-8.
This may not be necessarily the case, since Foreign.withCString is locale-dependent and some users may have ASCII/C or some other national locales. This regularly trips up Windows users with symptoms like "invalid argument (invalid character)".
Besides, using withCString will waste CPU on the same [Char] -> CString conversion for every call on every frame. While the raw bindings are exempt from this churn, the library can provide smart constructors that will take in something like Text, encode to UTF8 ByteString once and then use its pointer for raw calls. Anyway, even with Text-to-BS encoding happening every frame at least it will be correct for any environment.

GHC.Foreign is encoding-aware :thinking:
https://hackage.haskell.org/package/base-<IP_ADDRESS>/docs/GHC-Foreign.html#v:withCString

Due to how text labels are used in the dearimgui code perhaps would be better to use a special Label data type.
There are 3 cases:

Label, no id
Label and id
No label, only id

IDK if a completely empty label is allowed.

They can be set up at runtime, or compile time.

Runtime labels will be copied for each invocation unless allocated somewhere as a CString.
Compile-time labels can be encoded and stored for zero-copy passing, just like native static strings.

I think current String arguments should use such a Label instead, with IsString (IsLabel for type-3 labels?) instance and TH/QQ wrappers.


Seg-Fault in certain cases

I’m getting a seg-fault with the following setup:

A directory containing files with the following names:

img_x(1-10)_c1_darkfield.ome.tif
img_x(1-10)_c1_flatfield.ome.tif
img_x(1-10)_c2_darkfield.ome.tif
img_x(1-10)_c2_flatfield.ome.tif
img_x(1-10)_c3_darkfield.ome.tif
img_x(1-10)_c3_flatfield.ome.tif
img_x(1-10)_c4_darkfield.ome.tif
img_x(1-10)_c4_flatfield.ome.tif

The pattern: "img_x(1-10)_c{c:d}_flatfield.ome.tif"

And the following python code:
ff_fp = FilePattern(str(ff_dir), ff_pattern)
ff_variables = ff_fp.get_variables()
logger.info(f"Flatfield variables: {ff_variables}")

for group, files in ff_fp(group_by=ff_variables):
    logger.info(f"Flatfield group: {group}")
    logger.info(f"Flatfield names: {[p.name for _, [p] in files]}")

The variables are correctly identified as ["c"] and the seg-fault happens in the for ... statement starting the loop.
The error message is uninformative, simply saying that a seg-fault occurred.

Fixed in v2.0.1


#462 Allow RulePushPtr to apply to ops with output varnodes having multiple descendants

Fixes #462 and possibly others. Previously, RulePushPtr only applied if the output varnode of the op being processed had a single descendant due to the usage of loneDescend(). This led to poor recognition of struct field accesses when a pointer is partially constructed and then reused multiple times for the actual accesses. For a simple example, consider the following test case (with decompilation debug output at pushptr.txt):
typedef struct {
	int x;
	int array[4];
} test_struct;

void bug(test_struct *test, int i) {
	test->array[i] += test->x;
}

which compiles (with arm-none-eabi-gcc -g -c -Os) to:
                             **************************************************************
                             *                          FUNCTION                          *
                             **************************************************************
                             void __stdcall bug(test_struct * test, int i)
             void              <VOID>         <RETURN>
             test_struct *     r0:4           test
             int               r1:4           i
                             bug                                             XREF[4]:     Entry Point(*),
                                                                                _elfSectionHeaders::00000034(*),
                                                                                _elfSectionHeaders::00000084(*),
                                                                                _elfSectionHeaders::000000ac(*)
        00010000 01 11 80 e0     add        r1,r0,r1, lsl #0x2
        00010004 04 30 91 e5     ldr        r3,[r1,#0x4]
        00010008 00 20 90 e5     ldr        r2,[r0,#0x0]
        0001000c 02 30 83 e0     add        r3,r3,r2
        00010010 04 30 81 e5     str        r3,[r1,#0x4]
        00010014 1e ff 2f e1     bx         lr

At 00010000, the output varnode for r1 is constructed to point to &test->array[i]. Because it is used at both 00010004 (for the load) and 00010010 (for the store), it ends up with multiple descendants and RulePushPtr would previously have failed to apply. This prevented the decompiler from recovering the field accesses to test_struct.array. Without the patch, the decompiler produces:
void bug(test_struct *test,int i)

{
  (&test->x + i)[1] = (&test->x + i)[1] + test->x;
  return;
}

whereas with the patch, we get the much nicer looking:
void bug(test_struct *test,int i)

{
  test->array[i] = test->array[i] + test->x;
  return;
}

As for the change itself, I think it's safe to apply RulePushPtr to all descendants of the output varnode, but it wouldn't hurt if someone with more knowledge of the decompiler internals could confirm this.

Fixed by 7cbaa4fd610a48b151e193868f2537cd80b60f66.  Thank you for this submission.  The approach was good but needed to be coordinated with other rules, particularly RulePtrArith.


Update command doesn't work

Describe the bug
Update command doesn't work on<EMAIL_ADDRESS>using CapacitorSQLite.execute() while INSERT works just fine. Table was created using importFromJson()
Result ==> {
"changes": {
"changes": -1
}
}
To Reproduce
Steps to reproduce the behavior:
const statement = UPDATE importedBulkScan SET jsonData_='testtest' WHERE itemId = 4;;
const r = await CapacitorSQLite.execute({
statements: statement,
database: this.dbName,
});
Expected behavior
Should update the item but the following command won't show any change
const statement = SELECT * FROM importedBulkScan;;
const r = await CapacitorSQLite.query({
statement,
values: [],
database: this.dbName,
});
Smartphone (please complete the following information):

Device: [e.g. iPhone6] Galaxy S10
OS: [e.g. iOS8.1] Android 10

@fr3shn3ss thank for using the plugin but the release 2.9.7 is not maintained anymore. So upgrade to the latest release and tell me if you still have the issue

Thanks. I found the issue.
This version requires "last_modified" as one of the columns.
Sample Schema
[
{ column: "id", value: "INTEGER PRIMARY KEY AUTOINCREMENT" },
{ column: "jsonData", value: "TEXT NOT NULL" },
{
column: "last_modified",
value: "INTEGER DEFAULT (strftime('%s', 'now'))",
},
];

@fr3shn3ss i am glad that you find the reason. I still encourage you to move to the latest version which is strongest and maintain


Rethink how linking/unlinking locations of map panes works

We've had a few questions and enhancement requests for the linking/unlinking locations functionality:

#121
#122

Let's use this issue as an opportunity to collect other feedback about this functionality and consider how it could be clearer and more useful.

@ebrelsford I'm going to close here since this ticket hasn't seen any action - please re-open if you'd like to make any additions here!


support go mod

PR
https://github.com/skip2/go-qrcode/pull/29

Any plan for merging this?

I have merged this, thank you for your patience :)


Allow to manually destroy a spy

Copy-paste of an issue that I have with Jasmine/Jest.
Since expect mimics Jasmine API and will be used by Jest, I think it does no harm to discuss it here too.

Following the discussion on Google Groups: https://groups.google.com/forum/#!topic/jasmine-js/0RXvFo707EQ, I think my usecase is valid.
Jasmine expect does not allow to manually delete/destroy a spy and this is limitating, use case:
function signIn(done) {
  ...
  // Fails the 2x time with "<spyOn> : bar has already been spied upon"
  const mySpy = spyOn(foo, 'bar').and.callThrough();
  ...
  expect(foo.bar).toHaveBeenCalledTimes(1);

  // Missing feature:
  //mySpy.destroy();
}

function signOut(done) {
  ...
}

it('should be able to sign in/sign out multiple times', done => {
  signIn(() => {
    signOut(() => {
      signIn(() => { // Fails with "<spyOn> : bar has already been spied upon"
        done();
      });
    });
  });
});

signIn, signOut... are bricks (i.e simple functions - not Jasmine tests) that are reused to write complex Jasmine test scenarios like:

signIn, doSomething1, signOut
signIn, doSomething1, doSomething2, doSomething3, signOut
signIn, signOut, signIn, signOut, signIn, signOut

Remarks:

Currently the second signIn call fails with <spyOn> : bar has already been spied upon
I cannot make spyOn global otherwise error Spies must be created in a before function or a spec
Adding beforeEach(()=> { spyOn(foo, 'bar').and.callThrough(); }) is not the solution because expect(foo.bar).toHaveBeenCalledTimes(1) will fail with the 2x signIn call (because .toHaveBeenCalledTimes(2))

does spy.restore() not work? That's how sinon does it.

@ljharb Oh you are right! spy.restore() works perfectly! thx a lot
To sum up: Jasmine is missing restore()
Working example:
import { spyOn } from 'expect';
import * as expect from 'expect';

class Foo {
  bar(msg: string | number) {
    console.log('foo bar', msg);
  }
}

const foo = new Foo();

function loadApis(done: () => void) {
  console.log('loadApis');
  done();
}

let msgCount = 0;

function signIn(done: () => void) {
  console.log('signIn');

  const spy = spyOn(foo, 'bar').andCallThrough();
  foo.bar(msgCount++);
  expect(spy).toHaveBeenCalled();
  expect(spy.calls.length).toEqual(1);
  spy.restore();

  done();
}

function signOut(done: () => void) {
  console.log('signOut');
  done();
}

test('multiple sign in / sign out', done => {
  loadApis(() => {
    signIn(() => {
      signOut(() => {
        signIn(() => {
          signOut(() => {
            done();
          });
        });
      });
    });
  });
});

if line spy.restore() is commented:
  const spy = spyOn(foo, 'bar').andCallThrough();
  foo.bar(msgCount++);
  expect(spy).toHaveBeenCalled();
  expect(spy.calls.length).toEqual(1);
  //spy.restore();

it fails as expected at line expect(spy.calls.length).toEqual(1): Expected 2 to equal 1


[Feature][Connector-V2] Support multi-table sink feature for hdfs file

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
Support multi-table sink feature for hdfs file. Link #5652
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, @dengd1937 , Is there any progress on this task?


Add documentation about the configuration parameters of a Garden

Explain the different configuration settings of the Aragon Apps.

Done in our documentation: https://1hive.gitbook.io/gardens/users/apps
@willjgriff, when you have a chance, would you mind review the new documentation as well.


When creating a new project new journal file doesn't get noticed by watcher.

[x] Check if watcher is watching root folder
[ ] alt-p only opens project journal file if user is in a file that's part of the project when it's pressed

opened via imdone.io from a code comment on e570db4f by Jesse

https://github.com/imdone/imdone-atom/blob/3ca69cfcc218142dafd5fbabd7bc964b647880cf/todo.md#L29-L32

Issue closed with imdone.io by removing a comment.

https://github.com/imdone/imdone-atom/blob/d7f334583159f0c6e11fcd9456d69a19eed7c2c0/todo.md#L29-L36


Deadline resets to vanilla value after quota reached.

Describe the bug
Whenever I reach the deadline quota and sell of the items the custom value of 0 days for the deadline resets to the vanilla value of 3 days after the first quota.
To Reproduce
Steps to reproduce the behavior:

Set the deadline to a custom value

Finish deadline

Start new deadline

Deadline resets into vanilla value of 3 days
                        Or

Set deadline 0

Kill yourself by fall damage

Let the game reset

Deadline resets into vanilla value of 3 days

Screenshots
AC setting.

Before "I set it 0 so it would be faster to showcase"

After "You're Fired"

Expected behavior
The deadline value to reset at 0 days after quota reached.
Additional context
At first I thought the cause was of other mods that use the deadline value but after deleting said mods the issue still persists.
Edit
It happens after the failing the quota too which resets the deadline to 3 days and also givers credits even though I have set it to 0 in AC menu.
Add a list of all of your mods
018d5118-612e-2014-ede8-5996ce9017eb
BepInEx-BepInExPack-5.4.2100
RugbugRedfern-Skinwalkers-4.0.1
Ozone-Runtime_Netcode_Patcher-0.2.5
Sligili-More_Emotes-1.3.3
x753-More_Suits-1.4.1
RickArg-Helmet_Cameras-2.1.5
x753-Mimics-2.3.2
Suskitech-AlwaysHearActiveWalkies-1.4.4
sunnobunno-YippeeMod-1.2.3
Evaisa-HookGenPatcher-0.0.5
Evaisa-LethalLib-0.13.2
FlipMods-LetMeLookDown-1.0.1
EliteMasterEric-Coroner-1.5.3
FlipMods-TooManyEmotes-1.8.2
Verity-TooManySuits-1.0.5
AlexCodesGames-AdditionalContentFramework-1.0.3
Drakorle-MoreItems-1.0.2
Rune580-LethalCompany_InputUtils-0.6.1
notnotnotswipez-MoreCompany-1.7.6
itsmeowdev-DoorFix-1.0.0
TwinDimensionalProductions-CoilHeadStare-1.0.3
EladNLG-EladsHUD-1.2.1
MegaPiggy-BuyableShotgunShells-1.0.5
Hexnet111-SuitSaver-1.1.4
MegaPiggy-BuyableShotgun-1.0.4
FutureSavior-Hold_Scan_Button-1.1.1
Ozone-BepInUtils-1.2.1
Ozone-Glow_Steps-1.1.2
NiceHairs-NuclearLib-1.0.4
NiceHairs-Symbiosis-1.0.5
amnsoft-EmployeeAssignments-1.1.0
Monkeytype-HideChat-1.0.0
togglemybits-Strange_Objects-1.2.3
ohotdog-LootableMusicTapes-1.0.1
2018-LC_API-3.4.5
BLKNeko-HookGun-1.3.4
IntegrityChaos-Diversity-1.1.10
BunyaPineTree-ModelReplacementAPI-2.3.6
FoxGod-ThiccCompanyModelReplacement-2.0.1
BatTeam-LethalFashion-1.0.6
Owen3H-IntroTweaks-1.4.2
ASmolBoy-Intro_Company_Speech_Extended_Remix-1.0.0
Pinta-PintoBoy-1.0.4
Mellowdy-HandheldMap-1.0.0
Dwarggo-Fashion_Company-1.3.0
CyanBlob-Motion_Tracker-1.0.0
Silvercore-Permanent_Ladder-1.0.3
eXish-Batteries-1.0.4
BlueAmulet-LCBetterClock-1.0.3
KoderTeh-Boombox_Controller-1.1.9
CTNOriginals-CrossHair-1.0.5
ENZ-Lock_Doors_Mod-1.1.0
MegaPiggy-InsanityMeter-1.0.0
darmuh-ghostCodes-1.5.1
JunLethalCompany-GamblingMachineAtTheCompany-1.3.5
bigmcnugget-VanillaContentExpansion-0.1.8
jockie-LethalExpansionCore-1.3.15
Justice69-ImmersiveScraps-1.1.5
HolographicWings-LethalExpansion-1.3.25
sfDesat-Orion-1.2.3
sfDesat-ExpansionAssets-1.0.0
sfDesat-Aquatis-1.1.0
Magic_Wesley-Infernis-1.5.2
LethalMoonTeam-Ether-1.6.2
FireNoobsta-Ducks_Moons-1.1.3
Magic_Wesley-Acidir-2.0.0
Magic_Wesley-Etern-1.3.4
Generic_GMD-Generic_Moons-3.1.1
AudioKnight-StarlancerMoons-0.3.1
AudioKnight-StarlancerMusic-1.1.0
AudioKnight-Starlancer-0.4.1
sfDesat-Celest-0.2.1
jockie-LethalExpansionCoreModules-1.3.5
Xaymar-Assal-1.2.1
Olemyth-Crypt-1.3.3
BudgetAirpods-InsanityRemastered-1.1.2
PotatoePet-AdvancedCompany-1.0.139
Jamil-Corporate_Restructure-1.0.6
EliteMasterEric-WackyCosmetics-2.0.0
NiaNation-AbsasCosmetics-1.2.3
HGG-JigglePhysicsPlugin-1.1.2
Mhz-MoreHead-1.2.5
bandaidroo-BandaidsMegaCosmetics-1.1.0
broiiler-inacraft_cosmetics_megapack-1.0.1
ZTK-ZTKCosmetics-2.0.0
Hexa-Hexas_Cosmetics-0.0.2
companyemployee-EquipmentCompany-1.3.0
Sluka-CosmeticMegapack-1.2.0
fonnymunkey-SimpleHats-1.0.0
Insomniax-InsomniaxCosmetics-1.2.0
Pooble-LCBetterSaves-1.7.3
HomelessGinger-MaskedEnemyOverhaul-3.1.1
kuba6000-LC_Masked_Fix-0.0.2
KoderTeh-Television_Controller-1.0.3
MonAmiral-PlayerDogModel-1.0.3
mrov-LethalRichPresence-0.5.7
IAmBatby-LethalLevelLoader-1.0.7
NomnomAB-RollingGiant-2.4.4
TheFluff-FairAI-1.3.2
malco-Lategame_Upgrades-3.1.0
Evaisa-LethalThings-0.9.4
no00ob-LCSoundTool-1.5.0
Clementinise-CustomSounds-2.3.2
LethalResonance-LETHALRESONANCE-2.2.8
aqua_dot-CompanyWardrobe-1.0.1
Smxrez-SmoreCosmetics-1.5.0
Major_And_Skiz-MoreInteriors-1.3.0
Alice-ScarletDevilMansion-1.1.7
HolographicWings-ChristmasVillage_Legacy-1.3.16
scoopy-Scoopys_Variety_Mod-0.6.5
RedCrowbar-BuffedPresents-0.0.5
malco-SellBodies-1.1.0
DrinkableWater-Brutal_Company_Minus-0.7.3
NotAtomicBomb-TerminalApi-1.5.1
loaforc-FacilityMeltdown-2.1.1
Spyci-CozyImprovements-1.2.2
Badham_Mods-SCPFoundationDungeon-2.2.0
Search for a setting

Should be fixed with 141


Offscreen Rendering

To enhance the capabilities of potential browsers or applications built on Servo and Tauri, we must provide robust offscreen rendering support. This will enable the implementation of advanced features such as multiview, headless mode, command line interfaces, and offscreen rendering itself.
The initial step in this development process is to ensure that our rendering framework can operate offscreen by default. OpenGL possesses the capability to maintain the buffer in the background and transfer it to a window when required. Therefore, a strategic refactoring of our codebase in this direction is imperative.
Below will list all commits and PRs related to this milestone:

https://github.com/european-browser/verso/issues/6
https://github.com/european-browser/verso/pull/7
https://github.com/european-browser/verso/pull/8
https://github.com/european-browser/verso/pull/10

Reopen to track more following issues.


Expand description and results of the test pipeline.

Description

Expand description and results of the test pipeline.
How Has This Been Tested?

Looked at https://github.com/adelton/opendatahub-ai-edge/tree/test-pipeline/pipelines.
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

Conceptually this needs https://github.com/opendatahub-io/ai-edge/pull/117.

If the purpose of the test-mlflow-image pipeline is to test the behaviour of the container image and push the image to its "final" location, it is not clear why the applications and services stay around even after skopeo-copy finished.
Some clarification of the purpose of the metrics Service might also be useful.

@piotrpdev Thanks for the approval.
Should I file a separate issue for the question about the applications and services above, to have the reasoning properly discussed?

@piotrpdev Thanks for the approval.
Should I file a separate issue for the question about the applications and services above, to have the reasoning properly discussed?

Sure if you want, here's the current reasoning:

If the purpose of the test-mlflow-image pipeline is to test the behaviour of the container image and push the image to its "final" location, it is not clear why the applications and services stay around even after skopeo-copy finished.

This is what Stefan's pipeline code did (which the current pipeline code is based on) and we just haven't updated it to clean up after itself yet (and it's been used a lot for dev testing), feel free to make an issue for this.

Some clarification of the purpose of the metrics Service might also be useful.

It was added back in #48 to expose metrics for the deployed image but we have a template for that now. Pretty sure it's obsolete and can be removed unless we decide to test the metrics port using test-mlflow-image-pipeline. I doubt it though since we're planning to completely change how testing is done.

Thanks.
I've filed https://github.com/opendatahub-io/ai-edge/pull/127 for the cleanup and https://github.com/opendatahub-io/ai-edge/pull/128 to avoid creating the metrics service.


add a simple overdrive effect

I want to implement a simple overdrive effect for a sink like this example? How do you think I should start?
I have copied the Amplify implementation but cannot make progress implementing the process_samples function from the example link. Something like this:
#[derive(Clone, Debug)]
pub struct Overdrive<I> {
    pub input: I,
    pub bypassing: bool,
    pub factor: f32,
}

impl<I> Iterator for Overdrive<I>
where
    I: Source,
    I::Item: Sample,
{
    type Item = I::Item;

    #[inline]
    fn next(&mut self) -> Option<I::Item> {
        self.input.next().map(|value|  {
            // I think I should modify the samples here but don't know how to get the array of samples.
            process_samples(value)
        })
    }

    #[inline]
    fn size_hint(&self) -> (usize, Option<usize>) {
        self.input.size_hint()
    }
}

Any pointers?

please let me know if this can be closed


fix(modal): update title font, close icon, cancel button, modal fade in/out

fixes https://github.com/atlasmap/atlasmap/issues/489

Can one of the admins verify this patch?


Prettify data

Are there any reason that you prettify data in only some format? I'm happy if I can get prettified data in Markdown.

StyleStats v4.3 supports markdown output.
https://github.com/t32k/stylestats/releases/tag/v4.3.0
However, it might be different what you want, and someone wanted another markdown format like table in markdown, not list.
We can't support formats everyone wants, so we adopted your template feature to solve the problem at v5.0.0. The feature enables them to get formats they want.

@t32k I mean the prettified data by prettify.js. For example, not ratioOfDataUriSize but Ratio of Data URI Size is good for me. As you mentioned, nicer markdown style will be gotten at v5.0.0. It' really helpful for me!
What do you think of such as a  --prettify option or a --raw option for raw data? Is this a little bit complex?

I misunderstood. Actually, it sounds good. I'll think about it.:)

:bow:


Does this boilerplate supports async await ?

Hi, I want to use async-await. Does this boilerplate supports it out of the box or will I have to do something on my own ? Normally i am greeted with the below error whenever I am trying to. If this boilerplate supports es7 features out of the box, then I think the issue is somewhere in my setup.
I read this here

You’ve got to be careful here. If the Node.js version on the machine that’s transpiling the code is newer than the target version, then Babel won’t do the correct operations.

My nvm current shows  a 6.9.0 while I am seeing 6.10 in webpack config. Might be the case

sls SlStats shows this

Sorry, my bad. It does


AutomaticKeepAliveClientMixin can not keep second page state

i have a application use BottomNavigationBar and TabBarView which contains three pages,
app like this

but when i tap second bar item show second page,and tap first bar item ,tap third bar item, and tap second bar item, i saw second page state lose.

only second page hanppend.
code
i found four page also hava this bug,only second page has.
Flutter Doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v0.2.12-pre.4, on Mac OS X 10.13.4 17E199, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK 27.0.1)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[✓] iOS toolchain - develop for iOS devices (Xcode 9.3)
[✓] Android Studio (version 3.0)
[!] IntelliJ IDEA Ultimate Edition (version 2016.3.2)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
✗ This install is older than the minimum recommended version of 2017.1.0.
[✓] Connected devices (4 available)
! Doctor found issues in 2 categories.

This problem has been fixed recently. Try updating flutter to version 0.3.0 or newer.

@keluokeda Sorry for the late response. Is this still an issue?

Same here. Page state not saved with AutomaticKeepAliveClientMixin

@g-balas This is a long closed issue that is supposed to be fixed.
Please create a new issue with fully filled issue template and a runnable minimal reproduction.

the same problem

same problem

same problem


Questionable implementation of getProcessId

Testing https://github.com/Microsoft/vscode/issues/12595
See https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/api/node/extHostTerminalService.ts#L44
public get processId(): Thenable<number> {
	this._checkDisposed();
	if (this._processId) {
		return Promise.resolve<number>(this._processId);
	}
	setTimeout(() => {
		return this.processId;
	}, 200);
}

First of all, if you reach the setTimeout, there is no return value after all (just undefined). And then, how do you know that the process id is there after 200ms?

Inside the promise it recurses as it returns the getter not the backing value, I was planning on removing the setTimeout in October https://github.com/Microsoft/vscode/issues/12434
Fixing the bug now though.

And the 200ms is just a guess?

Yes, it likely only needs much less than that thought. I'll improve it in October.


OctopusDeploy Automation

What would you like to see changed/added?
Hi, I work for Octopus Deploy and was looking into how our application gets up to WinGet, as we are interested in doing it ourselves. The search lead me here, so thank you for publishing it for us.
Co-incidentally it looks like the automation was removed yesterday. Did it move somewhere else?

Hi, you can publish of OctopusDeploy by integrating Microsoft's WinGet-Create in CI/CD pipelines.
For Octopus Server:
wingetcreate update OctopusDeploy.Server -v 2023.1.9791 -u https://download.octopusdeploy.com/octopus/Octopus.2023.1.9791-x64.msi -t <GITHUB_PAT> --submit

For Octopus Tentacle:
wingetcreate update OctopusDeploy.Tentacle -v 6.3.417 -u https://download.octopusdeploy.com/octopus/Octopus.Tentacle.6.3.417-x64.msi https://download.octopusdeploy.com/octopus/Octopus.Tentacle.6.3.417.msi -t <GITHUB_PAT> --submit

Documentation for update command: https://github.com/microsoft/winget-create/blob/main/doc/update.md
Documentation for integrating into CI/CD pipelines: https://github.com/microsoft/winget-create#using-windows-package-manager-manifest-creator-in-a-cicd-pipeline
Example of a GitHub workflow which uses WinGet Releaser: https://github.com/microsoft/PowerToys/blob/main/.github/workflows/package-submissions.yml

I'm updating it to use updated tools and the new automation will be shortly available at https://github.com/vedantmgoyal2009/winget-manifests-manager.
Actually, I previously kept all my projects in one repository to ease my triage, but soon later I realized it created confusion for contributors to understand the repository structure since it was becoming more complex day by day. Also, different projects should live in different repositories, so that was also the reason to move the codebase.

@droyad hello?

@droyad hello?

@vedantmgoyal2009 Thanks for the info. At the moment we're not going to do any official support for WinGet, so thank you for your efforts.


Implement IRawValue on ${whenEmpty}

@snakefoot could you please help me getting this ready?
I doesn't work unfortunately, probably because MutableUnsafe = true. See this screenie when debugging (SimpleLayout.cs)

Any idea how to fix that?
Also think this isn't the most efficient way, but dunno how to write a more efficient test.
   public bool TryGetRawValue(LogEventInfo logEvent, out object value)
        {
            var item = Inner.Render(logEvent);
            if (item.Length > 0)
                 ...

       }

Don't do this:
var item = Inner.Render(logEvent);
Instead check if the raw-value-returned is null or empty-string.

Created #3398

Syoer


Hoppers are not an example of SidedInventory

…because they are not sided inventories

Hmm, should we just remove "such as" clauses if they are available in subclasses? In IDE, you can navigate easily; in html javadoc, it offers all known (vanilla) implementations of an interface and direct subclasses. Those should be more reliable.

I think that class comment is fine as it, with "hopper" changed to "furnace". Everyone knows how furnace works with hoppers, so that's a good example.
What's not fine are comments on methods inside it, they are just rephrasing method name and parameter types:
    /**
     * Gets the available slot positions that are reachable from a given side.
     */
    public int[] getAvailableSlots(Direction var1);

    /**
     * Determines whether the given stack can be inserted into this inventory at the specified slot position from the given direction.
     */
    public boolean canInsert(int var1, ItemStack var2, @Nullable Direction var3);

    /**
     * Determines whether the given stack can be removed from this inventory at the specified slot position from the given direction.
     */
    public boolean canExtract(int var1, ItemStack var2, Direction var3);

I would just remove these, they are purely tautological. But that's outside of the scope of this PR ;3
On getAvailableSlots comment could mention that it's not just available slots, but also an order in which hopers and most other users would try to insert/extract items.


chore: address clippy suggestions from new clippy version

New rust version => new clippy suggestions

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.01%. Comparing base (da65efa) to head (231a416).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2849      +/-   ##
==========================================
- Coverage   78.02%   78.01%   -0.01%
==========================================
  Files         229      229
  Lines       70351    70350       -1
  Branches    70351    70350       -1
==========================================
- Hits        54890    54884       -6
+ Misses      12360    12358       -2
- Partials     3101     3108       +7

Flag
Coverage Δ

unittests
78.01% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Date filtering

I've created optional parameters "since" and "until", but feel free to rename them. Default behavior still is to bring all future events.

Thanks for your PR! I just published the new 0.1.4 version to npm...


Restrain elements retrieval to viewport only

The current retriever gathers interactive elements from the entire page, including those outside the viewport. This can result in retrieving elements that are less relevant (e.g. footer ones). We want to test if performance improves by filtering out elements that are not visible in the viewport, allowing the retriever to concentrate on visible elements.
The option to retrieve all elements should remain available for the agent when it performs a full-page scan.
To do so, the get_possible_interactions Driver method should accept a parameter to filter out elements outside viewport.

Restrain has been done in #466


Access the rails console in all environments

Context
Before this PR, the make command was accessing the clock app which has less memory than the others so the following error was raised:
$ make qa console
wait: remote command exited without exit status or exit signal
FAILED

This PR adds the possibility to access the other server which has more memory therefore we can access the rails console without errors.

Closing the PR. Refer to comments 🙌