Synthesis failed for java-os-login

Hello! Autosynth couldn't regenerate java-os-login. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmprpytj5l_/googleapis'...
Cloning into '/tmpfs/tmp/tmprpytj5l_/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out 'e811b807425a978f47c8412c6fc56b5f941a32f6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Note: checking out 'd741cd976975c745d0199987aff0e908b8352992'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at d741cd97 chore: enable gapicv2 for firestore/v1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-05-05 21:32:45 [INFO] Running synthtool
2020-05-05 21:32:45 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:32:45,906 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-05 21:32:46,039 synthtool > Ensuring dependencies.
2020-05-05 21:32:46,050 synthtool > Cloning googleapis.
2020-05-05 21:32:46,051 synthtool > Using precloned repo /tmpfs/tmp/tmprpytj5l_/googleapis
2020-05-05 21:32:46,056 synthtool > Generating code for: //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java.
2020-05-05 21:32:46,166 synthtool > Failed executing bazel build //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/94d16073cd1d34f21abe4c9d38f1cb8d/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmprpytj5l_/googleapis/hs_err_pid25149.log

2020-05-05 21:32:46,167 synthtool > Wrote metadata to synth.metadata.
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 30, in <module>
    destination_name='os-login',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/oslogin/v1:google-cloud-oslogin-v1-java']' returned non-zero exit status 37.
2020-05-05 21:32:46 [ERROR] Synthesis failed
HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Switched to branch 'autosynth-self'
Note: checking out 'e811b807425a978f47c8412c6fc56b5f941a32f6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Previous HEAD position was d741cd97 chore: enable gapicv2 for firestore/v1 API
HEAD is now at a3a0bf0f BREAKING_CHANGE: Removing TimeSeriesQueryLanguageCondition as an alert condition type. The condition type is unsupported and unused. It was originally added for the Monitoring Query Language Alpha feature. refactor!: Drop support for TimeSeriesQueryLanguageCondition as an alert condition type.
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at ab88356 fix: make .kokoro-autosynth executable (#522)
Switched to a new branch 'autosynth-103'
2020-05-05 21:32:46 [INFO] Running synthtool
2020-05-05 21:32:46 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:32:46,491 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-103
nothing to commit, working tree clean
2020-05-05 21:32:46,622 synthtool > Ensuring dependencies.
2020-05-05 21:32:46,634 synthtool > Cloning googleapis.
2020-05-05 21:32:46,635 synthtool > Using precloned repo /tmpfs/tmp/tmprpytj5l_/googleapis
2020-05-05 21:32:46,639 synthtool > Generating code for: //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java.
2020-05-05 21:32:46,749 synthtool > Failed executing bazel build //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/94d16073cd1d34f21abe4c9d38f1cb8d/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmprpytj5l_/googleapis/hs_err_pid25184.log

2020-05-05 21:32:46,751 synthtool > Wrote metadata to synth.metadata.
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 30, in <module>
    destination_name='os-login',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/oslogin/v1:google-cloud-oslogin-v1-java']' returned non-zero exit status 37.
2020-05-05 21:32:46 [ERROR] Synthesis failed
HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-os-login. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmp0xq88jwy/googleapis'...
Cloning into '/tmpfs/tmp/tmp0xq88jwy/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out 'e811b807425a978f47c8412c6fc56b5f941a32f6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Note: checking out 'd741cd976975c745d0199987aff0e908b8352992'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at d741cd97 chore: enable gapicv2 for firestore/v1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-05-07 07:01:59 [INFO] Running synthtool
2020-05-07 07:01:59 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:02:00,163 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-07 07:02:00,297 synthtool > Ensuring dependencies.
2020-05-07 07:02:00,309 synthtool > Cloning googleapis.
2020-05-07 07:02:00,310 synthtool > Using precloned repo /tmpfs/tmp/tmp0xq88jwy/googleapis
2020-05-07 07:02:00,314 synthtool > Generating code for: //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java.
2020-05-07 07:02:00,424 synthtool > Failed executing bazel build //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/4cd6416dc569cc6cd45bfe20c32a8321/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmp0xq88jwy/googleapis/hs_err_pid18294.log

2020-05-07 07:02:00,425 synthtool > Wrote metadata to synth.metadata.
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 30, in <module>
    destination_name='os-login',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/oslogin/v1:google-cloud-oslogin-v1-java']' returned non-zero exit status 37.
2020-05-07 07:02:00 [ERROR] Synthesis failed
HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Switched to branch 'autosynth-self'
Note: checking out 'e811b807425a978f47c8412c6fc56b5f941a32f6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Previous HEAD position was d741cd97 chore: enable gapicv2 for firestore/v1 API
HEAD is now at 2fc2caaa chore: enable gapic v2 and proto annotation for bigquery/storage/v1beta2 API.
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at be74d3e build: do not fail builds on codecov errors (#528)
Switched to a new branch 'autosynth-111'
2020-05-07 07:02:00 [INFO] Running synthtool
2020-05-07 07:02:00 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:02:00,746 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-111
nothing to commit, working tree clean
2020-05-07 07:02:00,873 synthtool > Ensuring dependencies.
2020-05-07 07:02:00,884 synthtool > Cloning googleapis.
2020-05-07 07:02:00,885 synthtool > Using precloned repo /tmpfs/tmp/tmp0xq88jwy/googleapis
2020-05-07 07:02:00,889 synthtool > Generating code for: //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java.
2020-05-07 07:02:00,999 synthtool > Failed executing bazel build //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/4cd6416dc569cc6cd45bfe20c32a8321/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmp0xq88jwy/googleapis/hs_err_pid18329.log

2020-05-07 07:02:01,000 synthtool > Wrote metadata to synth.metadata.
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 30, in <module>
    destination_name='os-login',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/oslogin/v1:google-cloud-oslogin-v1-java']' returned non-zero exit status 37.
2020-05-07 07:02:01 [ERROR] Synthesis failed
HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-os-login. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpuxaxp1wz/googleapis'...
Cloning into '/tmpfs/tmp/tmpuxaxp1wz/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out 'e811b807425a978f47c8412c6fc56b5f941a32f6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Note: checking out 'd741cd976975c745d0199987aff0e908b8352992'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at d741cd97 chore: enable gapicv2 for firestore/v1 API
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Switched to a new branch 'autosynth-self-2'
2020-05-08 03:27:54 [INFO] Running synthtool
2020-05-08 03:27:54 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:27:55,094 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-08 03:27:55,234 synthtool > Ensuring dependencies.
2020-05-08 03:27:55,245 synthtool > Cloning googleapis.
2020-05-08 03:27:55,245 synthtool > Using precloned repo /tmpfs/tmp/tmpuxaxp1wz/googleapis
2020-05-08 03:27:55,250 synthtool > Generating code for: //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java.
2020-05-08 03:27:55,360 synthtool > Failed executing bazel build //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/51550bff4932e17dab0a74fb274af113/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpuxaxp1wz/googleapis/hs_err_pid27906.log

2020-05-08 03:27:55,360 synthtool > Wrote metadata to synth.metadata.
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 30, in <module>
    destination_name='os-login',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/oslogin/v1:google-cloud-oslogin-v1-java']' returned non-zero exit status 37.
2020-05-08 03:27:55 [ERROR] Synthesis failed
HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Switched to branch 'autosynth-self'
Note: checking out 'e811b807425a978f47c8412c6fc56b5f941a32f6'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Previous HEAD position was d741cd97 chore: enable gapicv2 for firestore/v1 API
HEAD is now at 83816bb3 Add kokoro-specific .bazelrc file with arguments specific only for kokoro environments. This is to fix autosynth builds when it tries building older commits.
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 4674113 build: use Bazel 3.0.0 for autosynth builds (#529)
Switched to a new branch 'autosynth-116'
2020-05-08 03:27:55 [INFO] Running synthtool
2020-05-08 03:27:55 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:27:55,714 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-116
nothing to commit, working tree clean
2020-05-08 03:27:55,861 synthtool > Ensuring dependencies.
2020-05-08 03:27:55,872 synthtool > Cloning googleapis.
2020-05-08 03:27:55,873 synthtool > Using precloned repo /tmpfs/tmp/tmpuxaxp1wz/googleapis
2020-05-08 03:27:55,878 synthtool > Generating code for: //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java.
2020-05-08 03:27:55,988 synthtool > Failed executing bazel build //google/cloud/oslogin/v1:google-cloud-oslogin-v1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/51550bff4932e17dab0a74fb274af113/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpuxaxp1wz/googleapis/hs_err_pid27941.log

2020-05-08 03:27:55,989 synthtool > Wrote metadata to synth.metadata.
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 30, in <module>
    destination_name='os-login',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/oslogin/v1:google-cloud-oslogin-v1-java']' returned non-zero exit status 37.
2020-05-08 03:27:56 [ERROR] Synthesis failed
HEAD is now at e811b80 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#150)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.


1.3 imprecise

I was asked for documentation about signals being published serially by a Publisher and looked at 1.3. Seems rather imprecise. It says:

onSubscribe, onNext, onError and onComplete signaled to a Subscriber MUST be signaled in a thread-safe manner—and if performed by multiple threads—use external synchronization.

The vague bit to me is signalled in a thread-safe manner. I think we can be more precise, something like:

signals (onSubscribe, onNext, onError and onComplete) must be signaled to a Subscriber serially.

The comment box for 1.3 could then mention that

the signals may be sent from different threads but there must be happens-before relationships between the signals sent to a Subscriber.

Hi @davidmoten,
apologies for the late response.
Good point. Perhaps we should say "sequentially", and if performed by multiple threads, each signal must happen-before the other?
@reactive-streams/contributors Wdyt?

@davidmoten Perhaps we should add it to the explanation of 3:2? https://github.com/reactive-streams/reactive-streams-jvm#3.2

As @davidmoten suggested originally, "serially" (see Serializability, wiki) is a quite common term in multithreading/concurrency literature (also present in RxJava sources) that means "without overlapping in time",
might be a bit better choice than "sequentially" :)

@davidmoten
How about:

onSubscribe, onNext, onError and onComplete signaled to a Subscriber MUST be signaled serially—and if performed by multiple threads—use external synchronization.

@viktorklang when you use the happens-before term, does it also apply to the state managed by these methods ?

@vietj That is managed by 2:11

@viktorklang

onSubscribe, onNext, onError and onComplete signaled to a Subscriber MUST be signaled serially—and if performed by multiple threads—use external synchronization.

Yeah that helps. I think we can do better with the term external synchronization though. All contributors here understand this but a wider audience might be confused by it. When I google "external synchronization" all I see is clock synchronization for distributed systems.

@davidmoten Any suggestions there?

The best I can come up with is to use happens-before terminology. happens-before applies to actions not signals (messages) so mixing happens-before with the verb/noun signal is a tad confusing.
I notice that the glossary defines signal like so:

As a noun: one of the onSubscribe, onNext, onComplete, onError, request(n) or cancel methods. As a verb: calling/invoking a signal.

AFAICS the normal interpretation of a noun signal in a computer science context is as a message and we have now redefined it to be the action incurred by that message. A tad confusing but we can run with it.
With regards to:

onSubscribe, onNext, onError and onComplete signaled to a Subscriber MUST be signaled serially—and if performed by multiple threads—use external synchronization.

We don't need to add "and if performed by multiple threads ..." because it is redundant (the wording implies it is an extra criterion) but rather some clarification about the use of multiple threads is nice to have in the comment under the rule.
So I'm thinking:

onSubscribe, onNext, onError and onComplete signaled to a Subscriber MUST be signaled serially.

and a comment of:

Serially does not preclude the signalling of signals from multiple threads but it does demand that there be a happens-before relation between the signals.

@davidmoten "signal" is conceptually messages in this model, but since synchronous Publishers and Subscribers are permitted, it has to refer to the methods (as a noun).

Serially does not preclude the signalling of signals from multiple threads but it does demand that there be a happens-before relation between the signals.

Sounds like a great explanation. I would want to avoid using "demand" in this context as to avoid confusion with the other notion of "demand" in this spec. Perhaps something like this?
Serially does not preclude the signalling of signals from multiple threads but it does require establishing a happens-before relation between each of the signals.

@viktorklang sounds good. Might be able to improve on my double negative:
Serially allows the signalling of signals from multiple threads but it does require establishing a happens-before relation between each of the signals.
Could be simplified a bit more? Perhaps
Serially allows the signalling of signals from multiple threads but there must be a happens-before relation between each of the signals.

@davidmoten Perhaps even simpler:
Serially permits the signalling of signals from multiple threads if a happens-before relation between each of the signals is established.

I'm good with that. Could replace the is established with there is:
Serially permits the signalling of signals from multiple threads if there is a happens-before relation between each of the signals.

@davidmoten I felt that wording to be a bit vague on what was required by the implementor. Is there some wording which clearly states that the implementor much provide this?

I understand. If you want to emphasize that then let's leave it as you had it.

@davidmoten Cool. Do you want to do the honors of opening a PR?

Okey doke

I realize there is a tad more to talk about.
We propose for 1.3:
onSubscribe, onNext, onError and onComplete signaled to a Subscriber MUST be signaled serially.
and a comment of:
Serially permits the signalling of signals from multiple threads if a happens-before relation between each of the signals is established.
However, I see there is a convention in place where every comment starts with "The intent of this rule is". If we do follow the convention then perhaps something like:
The intent of this rule is to permit the signalling of signals from multiple threads if a happens-before relation between each of the signals is established.

@davidmoten Great catch with the Intent-section! I believe we also need to supersede the use of "External synchronization" in the spec (amend 2:7).
Come to think of it, I think we need an iff in the intent:
The intent of this rule is to permit the signalling of signals from multiple threads iff a happens-before relation between each of the signals is established.

Come to think of it, I think we need an iff in the intent

Yeah I agree, you want it expanded (if and only if)?
To retire the "External synchronization" term we'll need to

remove External Synchronization entry from glossary
reword Thread-Safety in Glossary
reword 2.7

I'll put up some suggestions and we can bounce them around.

@davidmoten I think we need to spell it out so people who are unfamiliar with it don't think it's a typo.
Your plan sounds good, I'm looking forward to having a look at your suggestions.

@davidmoten What's the status here, David?

@viktorklang I'll have another look this week

@viktorklang
Thanks for working with me on this one. Apologies for the big delay. I'm still stretched a bit far to invest time in the retirement of the term "External Synchronization". I'd be happy to make a PR to cover the 1.3 rewording and raise an issue as a TODO on further rewording. Does that suit for the moment?

@davidmoten No worries, I understand. As for 2.7, see the discussion here: https://github.com/reactive-streams/reactive-streams-jvm/issues/405#issuecomment-414566683

@davidmoten Ping.

@davidmoten Ping.


Installer script doesn't work for scoop

as you can see from here, the script is broken for mpv, as it does not place the files at all, but still shows as completed. also, the slashes should be backslashes, as per windows file explorer rules. I managed to get it working by myself, but this should still be addressed

I simply copied/renamed the respective files to C:\users[username]\scoop\persist\mpv


[bug] Shell command added to scope cannot be run in 1.7

Describe the bug
After upgrading my app from Tauri version 1.5 to 1.7 my shell commands cannot be executed with the error
The Shell module is not enabled. You must enable one of its APIs in the allowlist.
I've confirmed that the scopes are defined properly, and changing the tauri.conf.json.tauri.allowList.all property to true has allowed the command to be run, but I don't think that should be needed.
Reproduction
https://github.com/billyjacoby/browsernaut/tree/chore/dep-upgrades
This branch compared to the current main branch on the repo has the issue, while main works as expetced.
Expected behavior
No response
Full tauri info output
yarn tauri info

[✔] Environment
    - OS: Mac OS 15.0.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.72.0 (5680fa18f 2023-08-23)
    ✔ cargo: 1.72.0 (103a7ff2e 2023-08-15)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 20.12.2
    - yarn: 4.0.1
    - npm: 10.5.0

[-] Packages
    - tauri [RUST]: 1.7.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.0

[-] App

### Stack trace

_No response_

### Additional context

_No response_

The error is correct, this is how it was always meant to be. The scope config alone should not enable the apis themselves. For that you'll need shell.all or shell.execute

Ahhh got it, thanks a ton for the clairifcation!


how to destory tengo script

how to destory tengo engine after run the script

Just don't keep reference and let GC clean it up?


Pass headers to upload endpoint

The purpose of this PR is make uppy-server be able to pass request headers configured in uppy XHR to upload endpoint.
There are a lot of use cases that need of this feature (authorizations, refer, and so on..).
Nowadays, the headers already are sended to providers endpoints but is not passed to upload endpoint.
This discussion was started in uppy project, follow the link: https://github.com/transloadit/uppy/issues/779

We should make sure that this can't be used to bypass browser restrictions on headers. There is a list here of headers that can't be set using browser XMLHttpRequest: https://fetch.spec.whatwg.org/#forbidden-header-name
Any of that list + anything starting with Proxy- or Sec- should be removed from the headers object before we use it

tks @goto-bus-stop, I will implement this header blacklist and push soon.

@goto-bus-stop @ifedapoolarewaju new PR available. Let mw know that changes or improves.
tks

thank you for the PR


GEODE-5259: remove class id from data serializable

I still have strong reservations about the how the type information is reduced to a string. Please give me a day or two to think about this.


Remove unused function and fix #10 and other compilation fixes

Tested personally and anyway this function is never called in the current code.
This function may have been a try for debugging while enso alpha.
Thanks to TheFloW for the make clean improvement
Fixes #10 compilation with latest vita-headers
Fixes .vpk packaging

No longer needed.


Are the form parsed after download

Hi,
I want to know if the form are parsed after the doanload.
Best,
Adam

No. These are just downloaded. Parsing feature needs to be added.


change Delete to Update in docs in Redundant update protection section

I think you meant Update here in the Redundant update protection section?

Good catch, thanks!


License for image files

Hi there,
Thanks for working on this project.
I'm going to package this to Debian. However, according to rule of Debian, every file should be cleared in license.
So I'm writing to you to double confirm the following file:
fast.png kcptun.png layeredparams.png logo-small.png logo.png rs.png
Are you created the above 6 files by yourself? If so, we can safely treat it same as the code you wrote, so it's MIT/Expat license.
But if you borrow some files from other project, please let me know. So I can trace the license of each image file.
Thank you!
Cheers,
Roger

rs.png comes from https://www.backblaze.com/blog/reed-solomon/
others are created by myself.


Added gettext calls for chargeback

Issue: English string occurs in Services -> Workloads -> VMs and Instances -> All VMs and Instances -> Monitoring -> Chargeback Preview
Steps for Testing/QA

Click Services -> Workload-> All VMs and Instances
Select one instance
Click Monitoring
Click Chargeback preview

Original Issue
English string occurred

Result

@miq-bot add_label kasparov/yes?
@gtanzillo could you look into back-porting this PR as well?

This pull request shouldn't have been merged in its current state. There is still the thing mentioned above in https://github.com/ManageIQ/manageiq/pull/20781#discussion_r522024622 that should have been addressed (and still needs to be addressed).

Related: https://github.com/ManageIQ/manageiq-ui-classic/pull/7512

It seems like this should be rolled back per @mzazrivec. Also, looking above, it seems like unites like Mhz and Bytes shouldn't need to be translated. But, in this case, it looks like "Bytes" was translated but "Mhz" wasn't. That's inconsistent.
"Totals" seems fine, though.
@DavidResende0 Can you make a new PR to address the above?

@gtanzillo after looking at the issue and discussing with @mzazrivec I made a PR (https://github.com/ManageIQ/manageiq/pull/20867) to address the issues with MiqReport::GROUPINGS. However, I noticed that none of the units like Mhz or Bytes are currently being translated in the master branch so I didn't make any changes there.

Kasparov backport details:
$ git log -1
commit 5dadf754de38ddfc6049a09ad73f47e43f69d478
Author: Keenan Brock<EMAIL_ADDRESS>Date:   Wed Nov 11 10:48:28 2020 -0500

    Merge pull request #20781 from Maria-Cordero-ibm/Chargeback_translation

    Added gettext calls for chargeback

    (cherry picked from commit bfcd2492f1d2ceffe43aee1dfa78eb28ad570278)

@gtanzillo The related PRs (https://github.com/ManageIQ/manageiq/pull/20867 and https://github.com/ManageIQ/manageiq-ui-classic/pull/7530) are not marked as kasparov/yes. Not sure if that's intended...


Feature: Make Model::updateBatch() work with Builder methods

This PR allows the use of setData(), updateFields(), onConstraint(), etc with Model::updateBatch().
This also changes the $index parameter of Model::updateBatch() to $constraints bringing it inline with Builder.
Because the new Builder::updateBatch() uses a different SQL structure some changes were made in Model's version. Instead of filtering the allowed fields from the dataset they are now filtered from $QBOptions['updateFields']. These are ultimately the fields that will get updated. Currently if someone were to use Builder::updateFields()  with the current version of model they could buypass the filter. Also not filtering the dataset allows inclusion of other fields that can be used with updateFields()  to create a calculated field update.
Once we can iron out this I will update the other batch methods as well.
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[x] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

And BaseModel is for all databases, Model is only for SQL databases.

I really don't quite get the difference between BaseModel and Model. I just tried to follow what was already there.. otherwise I probably would have done it differently.
What is a database other than a SQL database? Are these suppose to have the same methods available as SQL Databases? These databases are not compatible with Builder?
For example: with updateBatch() the dataset need not even have the updated_at field when using Builder. It can be set using updateFields instead. For other databases not compatible with Builder who knows what format they need the data. Who knows if they can even perform such operations as updateBatch().
If Model is the class for SQL databases and Builder only supports SQL databases then why was updateBatch() only implemented in BaseModel?
It seems I should leave the method in BaseModel alone and just completely override it in Model. No need to execute the parent method. But then the question remains, what is the point of the BaseModel method? What are its requirements?

Don't you think that the model turns into some kind of monster? We add methods to the model for convenient use of QueryBuilder, thereby turning it into an adapter for BaseBuilder.

Don't you think that the model turns into some kind of monster?

Ya I was trying to avoid that.
I almost think it might work better to change Builder to be able to define the timestamp fields and to filter the fields. Then use model to set these options on builder.

@kenjis Ok, I completely changed this around to deal with all the issues you pointed out.
The thing now is that BaseModel::updateBatch() isn't being used anymore by the framework. Should we remove the method?

@sclubricants In fact, you have now written the behavior of Laravel.
There, the model (entity) is injected into the builder. And the behavior of the builder is based on the data of the model.

@iRedds
I'd really like model to return Entity or a new EntityCollection class and then have DML methods on those classes.
Then you could do:
$entity = $model->where('some condition')->getEntity();
$entity->name = 'change the name';
$entity->update();

// OR

$entityCollection = $model->where('some condition')->getEntityCollection();

foreach ($entityCollection as $entity) {
    $entity->name = 'change the name';
    $entity->update(); // could save individually
}

$entityCollection->update(); // performs batch method

Really entity should be model.

What is a database other than a SQL database?

NoSQL databases.

The goal with this change is to have BaseModel which does not contain any database related code so that it can easily be extended to support other kinds of databases like NoSQL document based
https://github.com/codeigniter4/CodeIgniter4/pull/3930

Are these suppose to have the same methods available as SQL Databases?

BaseModel should provide only methods for all databases.

These databases are not compatible with Builder?

Probably yes.

If Model is the class for SQL databases and Builder only supports SQL databases then why was updateBatch() only implemented in BaseModel?

I'm not sure, but something like batch updates may exist in other databases.
E.g., https://www.mongodb.com/docs/manual/reference/method/db.collection.updateMany/
And the execution of the query is delegated to doUpdateBatch().

$entity = $model->where('some condition')->getEntity();
$entity->name = 'change the name';
$entity->update();

This is completely different design from the current CI4 implementation.
An entity in CI4 represents a record, and should not know how to update itself.
So $entity->update() should not work.

@sclubricants This will no longer be an entity, but an ActiveRecord.

Well this PR isn't attempting to do anything with Entity.


Known 2.6 Issues - WIP Fixes for v2.6.2

[ ] https://github.com/pydantic/pydantic/issues/8729
[ ] https://github.com/pydantic/pydantic/issues/8736
[ ] https://github.com/pydantic/pydantic/issues/8709

I am not sure wether there is already an Issue on this repo for this one, but it was reported on mypy side and I am facing a similar issue: https://github.com/python/mypy/issues/16858

Actually, it seems it was fixed in 2.6.1 by https://github.com/pydantic/pydantic/pull/8666, I will check in detail

@HenriBlacksmith,
We're following up on #8666 with https://github.com/pydantic/pydantic/issues/8729, just fyi!

Closing this in favor of a small milestone :).


feat: make RouterService to implements RouterServiceInterface

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

v1.1.0
GitHub release

Your semantic-release bot :package::rocket:


Prevent leaking WPF textview

This fixes the fact that StickerAdornment leaks every IWpfTextView it attaches itself to.

This is a fix for this bug: https://github.com/doki-theme/doki-theme-visualstudio/issues/66


Memory Leak

Hi,
I am just letting you know that I have found a memory leak when using this application on a raspberry PI 3.
Background
My company has a product with architecture very similar to that of a raspberry PI and we are required to read GPIOs at regular intervals. We we reading every 10 seconds, and found that the memory was leaking, albeit very slowly. Now, we fixed our issue by actually just reading once and then caching the read value (we actually just needed one reading).
The Current Issue
As I mentioned, our device is very similar to that of a PI, and so I got a PI and tried to reproduce it there as I thought it would be easier for sharing my findings and for others to reproduce if they wanted. I also increased the rate at which I read the GPIOs to speed up the test. It is the "system" memory in the :erlang.memory() that increases, and never seems to be released (albeit in this test, the "processes" increases as well).
I created a test project for anyone who wants to observe this: https://github.com/alanj853/gpio_bug
Simply run:
mix deps.get && iex -S mix
iex> Reader.start_link()
This will start of reading the GPIOs every second, and writes the memory to a file (every 3 mins) for later analysis.
After leaving for about 30 mins, you can run the following to stop the reading of the GPIOs, and observe how the memory is never released:
iex> Reader.stop_read()
After leaving for 30 mins of so, you can see the memory is never released.
Here is an output I collected earlier on:
+----------------------+-----------+---------------+----------+--------+----------+--------+---------+--------+
|        Total         | Processes | ProcessesUsed |  System  |  Atom  | AtomUsed | Binary |  Code   |  ETS   |
+----------------------+-----------+---------------+----------+--------+----------+--------+---------+--------+
| 14692296             |   3413200 |       3411652 | 11279096 | 387413 |   378244 |  47760 | 6191273 | 346656 |
| 14713104             |   3412736 |       3411092 | 11300368 | 387413 |   378244 |  47712 | 6191273 | 346520 |
| 14793048             |   3446576 |       3444932 | 11346472 | 387413 |   378244 |  47664 | 6191273 | 346520 |
| 14851064             |   3458432 |       3456788 | 11392632 | 387413 |   378244 |  47664 | 6191273 | 346552 |
| 14873584             |   3434872 |       3433324 | 11438712 | 387413 |   378244 |  47664 | 6191273 | 346552 |
| 14937416             |   3452616 |       3450972 | 11484800 | 387413 |   378244 |  47664 | 6191273 | 346552 |
| 14997800             |   3466920 |       3465276 | 11530880 | 387413 |   378244 |  47664 | 6191273 | 346552 |
| 15034800             |   3457832 |       3456116 | 11576968 | 387413 |   378244 |  47664 | 6191273 | 346552 |
| 15087088             |   3464056 |       3462508 | 11623032 | 387413 |   378244 |  47664 | 6191273 | 346552 |
| GPIO Reading stopped |           |               |          |        |          |        |         |        |
| 15271072             |   3614692 |       3614692 | 11656380 | 387413 |   378244 |  47688 | 6191273 | 346504 |
| 15293016             |   3636236 |       3636236 | 11656780 | 387413 |   378244 |  48144 | 6191273 | 346504 |
| 15304472             |   3647580 |       3647580 | 11656892 | 387413 |   378244 |  48144 | 6191273 | 346504 |
| 15269912             |   3613236 |       3613236 | 11656676 | 387413 |   378244 |  47688 | 6191273 | 346688 |
| 15295432             |   3638436 |       3638436 | 11656996 | 387413 |   378244 |  48144 | 6191273 | 346552 |
| 15279800             |   3623220 |       3623220 | 11656580 | 387413 |   378244 |  47784 | 6191273 | 346552 |
| 15295376             |   3638436 |       3638436 | 11656940 | 387413 |   378244 |  48144 | 6191273 | 346552 |
| 15278368             |   3621372 |       3621372 | 11656996 | 387413 |   378244 |  48144 | 6191273 | 346552 |
| 15286472             |   3629932 |       3629932 | 11656540 | 387413 |   378244 |  47688 | 6191273 | 346552 |
| 15273304             |   3616820 |       3616820 | 11656484 | 387413 |   378244 |  47688 | 6191273 | 346552 |
| 15297552             |   3640636 |       3640540 | 11656916 | 387413 |   378244 |  48048 | 6191273 | 346552 |
| 15317536             |   3660628 |       3660628 | 11656908 | 387413 |   378244 |  48048 | 6191273 | 346552 |
| 15283488             |   3627148 |       3627148 | 11656340 | 387413 |   378244 |  47592 | 6191273 | 346552 |
+----------------------+-----------+---------------+----------+--------+----------+--------+---------+--------+
Perhaps this isn't an issue, and maybe the way I am reading and shutting down is not the best approach, but I thought I'd share it anyways just in case.
More Info
Elixir and OTP Version: IEx 1.10.3 (compiled with Erlang/OTP 21)
elixir_ale version: 1.2.1
raspberry PI version: 3
Kernel: Linux raspberrypi 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l GNU/Linux

Thanks for investigating this and for sending the report with an example. I can't tell you how much I appreciate this.
I have not seen this memory leak, but it's really curious since there's not much going on. In my usage, I have long lived GenServers that hold on to GPIOs pretty much forever, so I'm sure that I'm not exercising this case.
I've pretty much stopped maintaining ElixirALE and focused my efforts on Elixir Circuits. Would you be ok in switching to circuits_gpio and rerunning the experiment? If you're only reading the GPIO infrequently, I don't think the switch is too hard. Here's the guide: https://github.com/elixir-circuits/circuits_gpio/blob/main/PORTING.md#code-modifications.
Assuming that the memory leak is in Elixir Circuits as well, I'd much prefer to debug it there. Elixir Circuits is also lighter weight, so I'd expect a memory leak, if it exists, to be smaller.


What freq to use for weekday data?

I have daily data except for the weekends. How do I set the frequency for the same?

In the Python version, freq is passed to Pandas date_range which has a long list of possible frequencies: http://pandas.pydata.org/pandas-docs/stable/timeseries.html#offset-aliases . It looks like 'B' is what you want.
For the R version, freq is passed to seq.Date which supports only "day", "week", "month", "quarter" or "year". In this case (and more generally), you can always create the dataframe of future dates manually.
The output of make_future_dataframe in both Python and R is just a dataframe with a column ds containing the dates for which predictions will be made. You can manually construct a dataframe with only weekday dates and then use that as the input to predict (e.g. http://stackoverflow.com/questions/15139768/fill-a-vector-with-weekdays-only)


docs: Highlighting the fact, that certain methods do not work in place

Closes #189.
Summary of Changes
Highlighting the fact, that fitting methods of Classifier, Regressor, Tabletransformer and certain methods of the _table class do not work in place.

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ PYTHON
black
1
0
0
0.58s

✅ PYTHON
mypy
1

0
1.6s

✅ PYTHON
ruff
1
0
0
0.05s

✅ REPOSITORY
git_diff
yes

no
0.02s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by

:tada: This PR is included in version 0.12.0 :tada:
The release is available on:

v0.12.0
GitHub release

Your semantic-release bot :package::rocket:


Provider cannot be instantiated - permission denied

Terraform Version
v0.12.29
Affected Resource(s)
The provider itself
Terraform Configuration Files
provider "pact" {
  host         = "https://test.io"
  access_token = "testing"
  tls_insecure = true
}

Debug Output
https://gist.github.com/jlsan92/9c615cce4cc74db1b75bc20ccba39b61
Panic Output
NA
Expected Behavior
Normal TF plan procedure
Actual Behavior
Error: Failed to instantiate provider "pact" to obtain schema: fork/exec /root/.terraform.d/plugins/linux_amd64/terraform-provider-pact: permission denied
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

terraform plan or terraform validate

Thanks for the report.
The error looks to be related to starting the service itself as root - do you indeed have the permission to fork/exec?
Our build is able to successfully initialise and run the plugin - see the latest release build here: https://travis-ci.org/github/pactflow/terraform/builds/711706647
Can you please provide a build that reproduces the problem? We'll be able to fix it if it indeed is an issue.

Hi @jlsan92


Unable to generate shareable url

Describe the bug
Unable to generate share URL . Share button keeps showing infinite processing
To Reproduce
Steps to reproduce the behavior, including example Promptfoo configurations if applicable:

Run the promptfoo eval
Run the promptfoo view
Click the share button to create a shareable URL
Button keeps showing infinite processing

Expected behavior
Shareable URL for the eval results
Screenshots

System information (please complete the following information):
Request URL:
https://api.promptfoo.dev/api/eval
Request Method:
POST
Status Code:
413 Payload Too Large

Promptfoo version:
0.87.1

Out of curiosity, how large is the eval you are trying to share?  Are you able to share an example (e.g. produced by promptfoo eval -o output.json)

It has 12664 lines. Its size is 263MB. Its taking too long to upload on drive to share with you.

Unfortunately we can't support payloads of that size via public sharing
right now.  You could try self-hosting
https://www.promptfoo.dev/docs/usage/self-hosting/ or get in touch for
our paid cloud version @.***)
On Thu, Sep 26, 2024 at 7:51 AM Mehnoor Siddiqui @.***>
wrote:

It has 12664 lines. Its size is 263MB. Its taking too long to upload on
drive to share with you.
—
Reply to this email directly, view it on GitHub
https://github.com/promptfoo/promptfoo/issues/1772#issuecomment-2377199228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLYJU2FMVHT5UU724CGRDZYQNPLAVCNFSM6AAAAABO43RO42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGE4TSMRSHA
.
You are receiving this because you commented.Message ID:
@.***>

One more idea: you can set PROMPTFOO_LIGHTWEIGHT_RESULTS=1 to strip some information from the eval result and make it much smaller.  This may make it easier to share :)


fix: conditional require to not have side effects

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Proposal: Unambiguous Keywords

Proposal Summary / Motivation
I've briefly presented this idea on Slack and in the spirit of gathering more feedback I'm posting it here as well.
The Gherkin reference specifically stipulates that keywords should not be taken into account when looking for a step definition [1].
I've personally witnessed in several projects that this can lead to deterioration in test language unless every change is strictly reviewed.
Below is an example of a hastily written patch that breaks the flow of language, but doesn't yield an error (actually taken from my Git history, but modified slightly to anonymize the domain).
       When I press the foobar button
-      Then I should see 2 events in total
       And I should see these new fields with values
         | My Field      | foo |
         | Another Field | bar |

[1] https://cucumber.io/docs/gherkin/reference/#steps
Current Behavior
Currently, the following steps would yield ambiguity error.
• Given(“I press button”)
• When(“I press button”)
I don't propose changing this.
However, it doesn't matter which keyword you use in your feature files and the example below runs just fine.
# features/step_definitions/cucumber_steps.js
import {When} from 'cucumber'

When(/^a step$/, function() {});

# features/a.feature
Feature: a feature name
  Scenario: a scenario name
    Given a step

Proposed Behavior
Given the following step definitions.
When("step a", () => {});

... and the following feature file.
Feature: a feature name
  Scenario: a scenario name
    Given a step

I propose for Cucumber to fail with a wrong-keyword error. Furthermore, and just as importantly, for this to properly work, any use of And and But keyword must be interpreted as if they were of the same type as the previous step.
I've tried to outline this behavior with some test cases here.

I like this proposal because it encourages even less ambiguity. You can no longer mix and match Given/When/Then as you see fit.

The only thing I propose to this is we do a major update to all our APIs with this and only this, because I can see this either being reported 20 times or causing some grievances.
That being said, I do like it :)

I feel like this should be in the realm of a linters rather then in the realm of the interpreters.

@mpkorstanje that linter would require access to more than the gherkin document - it would also need the step definitions. I think that’s too heavy for a linter. Plus, people don’t use linters.
If we add this we could always add an option to disable it, so people with years of legacy scenarios can go on with their lives.
Interested in your perspective @mattwynne @sebrose

This would necessarily require a change in the messages, which contains the difficult-to-interpret synonym used in tests.

I very much like this proposal. It also mirrors the behaviour that has been implemented in Perl's implementation (pherkin/test-bdd-cucumber-perl) since before 2013.

I like this proposal too.
From my point of view, it's not just about language clashes, it's also about wanting to be able to do different technical stuff during context, action and outcome phases of a scenario. For example, if I'm using some kind of driver adapter to connect my steps to my app, I would ideally like to be able to use the domain-driver during Given steps, then switch to a UI driver during the When and Then steps.
It would be super-awesome if there were messages (that front-ends could them build hooks for) that told us when we were moving from context into action, from action into outcome phases of the scenario. But keep that out of scope for now!

I'm a fan of this. The example in the original summary is exactly the kind of thing I have seen happening in practise.

The only thing I propose to this is we do a major update to all our APIs with this and only this, because I can see this either being reported 20 times or causing some grievances.

It could work like a deprecation - ship the change whenever, have it raise a prominent warning at runtime initially but not fail (unless you opt in early), then move to hard failure in a major release after X months?
Another minor facet: cucumber-js currently exposes the generic defineStep function (that the keywords delegate to) in its API so removing that would be a prerequisite there I guess.

I love your thinking here @mattwynne - about separating the context/action/outcome scopes, and giving the user control over how they are created. It's something @joshski and I have been discussing regularly since we paired on the cucumber electron subscond tdd code a couple of years ago. We ended up implementing this pattern ourselves, but it would be much cleaner if it were part of Cucumber itself.

@davidjgoss - regarding removing defineStep we have an open ticket for that - which has caused some grievances. https://github.com/cucumber/cucumber-ruby/issues/1362 - I'd be interested in your thoughts in that ticket.

@aslakhellesoy I've looked through that thread but struggling to see the overlap - defineStep isn't a subroutines thing, it's just that it exposes a way to do a step definition without specifying which of "Given", "When" or "Then" it is - which would be at odds with this change.

I also think a warning would be suitable as a first step, with an option to turn warning into error.
Maybe a commandline option like -strict could be added, or we adopt something similar how gcc and other compilers work by adding +/-W switches.

Really like this idea. Want to recap to check my understand and see if we can determining next steps

With step definition: Given("x", ...)

Use in a feature file

Given x -> matches step definition
When x -> no match, wrong keyword
Then x -> no match, wrong keyword
And x / But x -> keyword need to be transformed to last usage of Given / When / Then

Multiple step definitions Given("x", ...) and Given("x", ...) lead to ambiguous result

Questions:

Are multiple step definitions Given("x", ...) and When("x", ...) allowed?

These stop leading to ambiguous results and could technically be allowed after initial rollout

Implementation Plan

Core changes

gherkin - pickle steps include a keyword type that is computed to be Given / When / Then (or context / action / outcome)
add example to compatibility kit

Language Libraries

Initial release

Warning generic step definitions will be removed (those without keyword type)
Warning on wrong keyword type
Opt-in flag to unambiguous keywords

Major release for unambiguous keywords only

Thoughts?

@charlierudolph sounds like a plan to me.

Are multiple step definitions Given("x", ...) and When("x", ...) allowed?

Still no IMO, because fundamentally Given (context), When (action) and Then (verification) should be different stuff.
There is also the * keyword which is potentially tricky with this.

Are multiple step definitions Given("x", ...) and When("x", ...) allowed?

Presumably, yes. If the fundamental complaint is that Given("x", ...) and When("x", ...) are being treated the same and the goal of this change is to treat them as different, then I would expect that both of those definitions would be allowed to co-exist because, you know, they are different.

Dependent on work involved, I would say maybe to start with do the smallest change (That would in theory permit both Given("x") and When("x"), and then maybe later set it up to prevent them. But I'm only spitballing at the moment.
Also shared this link with slack as we were discussing it recently.

I would prefer that this be a configurable option. I do occasionally reuse the same steps between Given and When, and I don't really want to have to write the same step definitions twice if I can help it. At the same time, I understand that some people see value in matching the keyword, and I don't want to deny them that either.

The Perl cucumber implementation Test::BDD::Cucumber combines the behavior proposed in this bug with behavior requested by @marnen:

And and But steps are explicitly mapped to the keyword on the preceding row (Given, When, Then) during the pickle generation phase
The executor only supports Given, When and Then steps (i.e. not *)
Step functions are usually bound to Given, When or Then using the syntax:Given qr/some setup step regex/, sub { ... };
When qr/some execution step regex/, sub { ... };
Then qr/some assertion step regex/, sub { ... };

A special Step step declaration keyword binds the step function to all three categories:Step qr/Some generally applicable regex/, sub { .... };

This allows the executor to throw a warning or error when the regex is not associated with the keyword specified, but is associated with another keyword. (E.g. there is a regex match for a Given step while the current step is specified to be a Then step.) Yet the Step step-definition keyword can be used to bind a generically applicable regex to a step function for @marnen's use-case.
Note that the above is achieved by implementing a home-grown parser, but the desire is to move to infrastructure developed in close cooperation with or best even as part of the Cucumber project -- meaning that the intent is to move away from the home-grown parser as soon as technically viable (as soon as possible).
Note that the current release of Test::BDD::Cucumber (0.77) does not throw this error, but I like the idea enough to work on this in a next release.

Got pointed here from Keywords : Strict keyword enforcement #1392
 ,  thanks @davidjgoss.
Registering interest and support of this feature

If this goes ahead we'll need to consider / test the impact on i18n
Will it add to my experience to have to remember to use Given() whenever I write Gegewe in my steps?

I'll be joining the stand-up coming Thursday. I'm keen to understand what will be required to bring this forward, because it's one of the last obstacles for Test::BDD::Cucumber to move to using the Gherkin library.

If this goes ahead we'll need to consider / test the impact on i18n
Will it add to my experience to have to remember to use Given() whenever I write Gegewe in my steps?

That depends: in the Perl Cucumber variant that I maintain, translations for Given/When/Then are registered for the step files to be available (documentation: https://metacpan.org/pod/Test::BDD::Cucumber::Manual::Tutorial#Non-English-features-and-step-files). No idea how other implementations would (be able to) deal with this though.

I really don't like this suggestion:

IMO it encourages ambiguous business domain language, with automation code modified by preceding keyword
Gherkin currently supports steps being preceded by '*'
when conjunctions are used (And, But) the reader will have to identify the preceding G/W/T keyword

However, a number of Gherkin implementations do work in this way (SpecFlow, Perl, Behat?). SpecFlow introduced the @StepDefinition annotation to emulate core Cucumber implementations.
I support the passing of the keyword to the pickle.

I also support passing of the keyword to the pickle.
But I do not support making the keyword part of the step definition. Major breaking change with no value.

Discussed on the weekly Cucumber team call; consensus was that since some implementations have had the step-definition-per-keyword behavior (mentioned during the meeting: SpecFlow and Test::BDD::Cucumber (Perl)), it's necessary to add the keywords to the pickles. Additionally, since Cucumber never exhibited this behavior, it's expected to be a major breaking change for all those who have Cucumber-based test suites. In other words: Let's do this in the pickle so more projects can move to the generic parser infrastructure, but lets not incorporate this any further than that.

It's my action to implement this in the Gherkin (and Messages) libraries up to the Pickle.

I can't think of anything left to do other than starting to integrate this in to Cucumbers.
They should all have an option to turn on the strict validation (matching against expression and keyword). I suggest we call this done for now and deal with any problems as we start integrating.

PHP will take a while (it requires Behat to actually use the cucumber parser, first)

Same for Perl. In order to start that work, the current state will need to be released though.

SpecFlow already behaves like that, so we are done.


[4.x] Handle certificate corruption

Avoid NPE and throw IOException
#fixes https://github.com/square/okhttp/issues/7978

https://github.com/square/okhttp/pull/7981 for master


Add Darwin availability annotations for concentration measurement clusters.

Fast-tracking platform-specific fix with platform owner review.


[reopen] Create an FAQs list from Top Tips content

@PatCapon39 Hurray the gitpod bot works now :point_up:

Hooray, thanks @neoformit! "Have a cup of tea while the workspace builds itself" gave me a good laugh 😁
@GarethPrice-Aus here's the page visible in draft form. I will email this too https://8000-patcapon39-galaxymedias-nqq8ht4t5oo.ws-us116.gitpod.io/faqs.html


Feature - Math Magicians Full Website

Project Description
In this project, I developed a full website for the Math magicians app, consisting of Home, Calculator and Quote pages and using React components.
Here is the line to the live page: Math Magicians
Feature Description

Add website header component
Add website footer component
Add calculator page to app
Add home page to app
Add quote page to app
Add random math quote using API
Deploy the app using GitHub pages

Output Screenshots

These Features were Tested on the Following Browsers

[X] Chrome
[X] Firefox
[X] Edge
[ ] Internet Explorer
[ ] Safari

Thanks @Bondok6 for the review and feedback!
Happy Coding! :champagne: :champagne: :champagne: :+1:


About dataset

Your work is excellent.！What is the directory structure for storing the datasets in this project?

Hi! thanks for your interest. The structures are different depends on the datasets.

Hi! thanks for your interest. The structures are different depends on the datasets.

Thank you for your reply!This is the dataset structure I set up, I only used the KITTI dataset.

But when I train, it remains in this state and does not respond. What is the problem?

You need to put all of them into a single folder. For example, you can take a look at this code .
Similar for images etc.

You need to put the content inside data_odometry_color, data_odometry_velodyne to the dataset folder that contains poses. For example, you can take a look at this code . Similar for images etc.
I have moved the data set according to the tips you gave, but when I train, I still have this problem and no response. What is the problem? Is there still a problem with my data?

I guess your dataloader is stuck. Can you try to set num_workers to 0?


Map to array

Hello,
Is there a way to map a object like this:
[{
	"title": "Product Title",
	"price": 199
}, {
	"title": "Product 2 Title",
	"price": 399
}]

to this:
[{
	"name": "Product Title",
	"price": [{
		"list": 199,
		"value": 199
	}]
}, {
	"name": "Product 2 Title",
	"price": [{
		"list": 399,
		"value": 399
	}]
}]

I thought of a map like this:
var map = {
	"products": {
		{
			"title": "name",
			"price": "price[].list",
			"price": "price[].value"
		}
	}
}

Thanks

That's a great idea and a unique use-case, i'd love to see a PR for the feature, and the tests at least shouldn't be hard to write.
You might be able to do this directly with wankdanker's object-mapper that this module is built on top of. I'd look into writing your own transform function for the price field.

I thought about doing a transform for it, but I'll use your package in a project that I need the map be configurable by the user, so it needs to be simple.
I'll check the code and try to work doing like I said.

Hi
I've just made the modifications in the wankdanker's object-mapper project, can you update to version 2.0.0?
Thanks

Yeah – I can get to it this this weekend. Thanks for putting the time in! I'll check it out and update when I get a minute.

@rafakato sorry for such a delay! Updated and published just now.


feat: Add OPUS mp4 support

Always use mp4 for opus

@Chokoabigail, can you please check this page and take care of Google's CLA requirement?  https://github.com/shaka-project/shaka-streamer/pull/143/checks?check_run_id=16608765464
Thanks for your contribution!

Hi, I solved Google's CLA requirement, can you marge this please?

Thanks for your contribution!


WIP: Fix build

This does not yet work but I’m opening this now to avoid us accidentally duplicating work. I hope to get this into a state where everything builds over the next one or two weeks so we can merge this.
After that we can add a test suite and then clean up the code base.

Indeed. There's a lot of ShortByteString <-> String conversions that need to be sorted. This looks like a great start. I'll rebase my next work on it.


Image uploading

Please provide with image uploading methods and usage examples.

Will be provided when we get to this point.

I think you shouldn't close issue if it is not solved


ctrl + ` launch terminal command also increases zoom level

My OS is Ubuntu 16.04 LS

I can't reproduce this, can you post the extensions you use and your keybindings.json file?

oh thanks, the default one was overwritten.


Wallet screen - Statuses for Max privacy tx's + tx details

Statuses for Max privacy tx's https://zpl.io/b6xJ58q

Wallet screen with new status (example) https://zpl.io/2ENXQ7M

Transaction details https://zpl.io/bzmYnqA

The offline transaction stucks in waiting for receiver status when the receiver is offline.

3. Transaction details https://zpl.io/bzmYnqA

Transaction details aren't added

The offline transaction stucks in waiting for receiver status when the receiver is offline.

This feature will be checked in #146

Checked


💡 [REQUEST] - VSCode Support For Foundry Test & Script File

Summary
In a Foundry project, test and script files like a.t.sol or a.s.sol lack support in VSCode for features like navigation or reference lookup.
Basic Example
Add navigation or reference lookup just as .sol files in foundry projects
Drawbacks
No drawbacks. Everyone using foundry will be grateful !
Unresolved questions
No response
Implementation PR
No response
Reference Issues
No response

Hello @CSWellesSun,
analysis for Foundry test and script files can be enabled by removing test and script directories from the compiler exclude_paths setting, either in VS Code settings or TOML config file (depending what you currently use).

cool really thx!


Rework Django admin integration

[x] Provide views / URLs under the /admin/ path

[x] login
[x] setup
[x] backup tokens
[x] profile
[x] QR code
[ ] Phone integration
[ ] YubiKey

[x] Custom Admin styling
[x] Rework patching of the admin for 2FA

Coverage decreased (-3.3%) to 92.675% when pulling 93afc9c6662d10049476e1187e8166452d0611bf on MarkusH:feature/admin-integration into f308883d7e1e327f06080da254c75a20e5fcc4fb on Bouke:master.

Coverage decreased (-3.3%) to 92.675% when pulling 714e6cbe024362ea3dc411624e5289eda006d5fc on MarkusH:feature/admin-integration into f308883d7e1e327f06080da254c75a20e5fcc4fb on Bouke:master.

It would be awesome if we could land this PR, as the current admin integration is rather lacking. Do you have plans to continue working on this? If not, I might have a look at this sometime in the next months.

@MarkusH, @Bouke do you think this could be largely superseded by https://github.com/jazzband/django-two-factor-auth/pull/491, or is there still value in porting this to the current master?


*.svc.ms listed as "default" required

Due to the way that share point zips multiple files and then send from a ".svc.ms" address i respectfully request that line 39 on the article be copied to line 31. specifically the "*.svc.ms" piece

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

ID: 077406d8-bff1-496e-3ea2-b38558fd9355
Version Independent ID: 57db3dec-2250-2dee-fd1a-ec6656911798
Content: Office 365 URLs and IP address ranges
Content Source: Enterprise/urls-and-ip-address-ranges.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@officedocsbot assign @mypil

@Strick1969 - Thank you for submitting feedback.
I will get this issue over to the Enterprise writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@Strick1969  Thank you for your Feedback. We have made the requested change via PR https://github.com/MicrosoftDocs/OfficeDocs-Enterprise/compare/live...msbemba:patch-6

@Strick1969 I will pass your suggestion on to the SharePoint Online product team that maintains these endpoints for their consideration in the next update. Thanks for letting us know.


fix(v): reflect new comment structure in parser

This change fixes the CI issue related to V

We really need some better integration CI between the different repos...

100%


DCS mid sem paper 2017 added

@divyanshu-rawat
Fixes #41

Hey Himanshu
Thanks for uploading
Add a seperate file for questions only.

So guys finally I fixed Travis now Travis build is passing congrats 👍

So guys finally I fixed Travis now Travis build is passing congrats 👍


decoding tokens are not equal for different methods

Hi, thank you so much for your awesome work!
I notice that when running equal.py to compare decoding tokens of speculative decoding methods (pld/eagle/hydra) with vanilla decoding tokens, the outputs are always Not Equal! I observe the decoding tokens between different methods are almost the same. What are the reasons that cause the slight differences between decoding results?

Thank you for your kind words and your question!
We have noticed similar discrepancies in our experiments with multiple Speculative Decoding methods compared to vanilla autoregressive (AR) decoding. Specifically, in our float32 precision and greedy decoding settings, only [SpS](https://huggingface.co/blog/assisted-generation) and [PLD](https://github.com/apoorvumang/prompt-lookup-decoding) produce results that are exactly the same as AR decoding. Other methods show minor differences, especially towards the end of long sequences.
We believe these slight variations may result from small computational errors that accumulate over each decoding step, becoming noticeable in longer sequences.
We plan to investigate this issue further in the coming days. If you have any insights or ideas, please feel free to share them!

BTW, we did not modify the coding of specific algorithms, which means that the original implementation also has this issue. You can also communicate with the authors of corresponding methods😊.


Normalization of WTH references to artifacts such as schemas, codes...

Ensure consistency of WTH URLs and resources outside of the Manual on WIS. Below are lists of what exists today in WTH.

Document location

https://community.wmo.int/wis2-topic-hierarchy

The normative provisions in this Standard are denoted by the URI:

http://wis.wmo.int/spec/wth/1

The WIS2 Topic Hierarchy Notification codelist bundle can be found at

https://schemas.wmo.int/wth/1.0/wth.zip

A browseable codelist can be found at

https://codes.wmo.int/wth

Requirements Class

http://www.wmo.int/spec/wth/1/req/core

A zip file of all the approved topics is available at

https://schemas.wmo.int/wth/a/1.0/wth.zip.

A browseable and searchable codelist of all topics can be found at

https://codes.wmo.int/wth.

Conformance with this standard shall be checked using the tests specified in the Conformance Class Abstract Test Suite (Normative). It is published at

https://schemas.wmo.int/wth/a/1.0/ats.

@tomkralidis

Community page:
https://community.wmo.int/en/activity-areas/wis/wis2-topic-hierarchy

As discussed with Tom, the plan is to publish to schemas.wmo.int like this:
Schemas site:

https://schemas.wmo.int/wth/a/1.0

standard

PDF (from GH tag release)

examples (maybe)
shemas
wth.zip (GH tag release, includes everything including examples)

http://www.wmo.int/spec/wcmp/2/conf/core --> this will change to wis.wmo.int/...
Update all xml snippets and update URLs from GH to codes.wmo.int

PR in #96
Release process updated in https://github.com/wmo-im/wis2-topic-hierarchy/wiki/ReleaseProcess


Add support for class-map and policy-map for QOS

Issue Type

[ ] Template enhancement
[x] Role enhancement
[ ] Documentation enhancement (avd.sh)

Is your feature request related to a problem? Please describe.
Implement class-map and policy-map in AVD to produce following configuration
! Example 1
class-map type qos match-any TEST
   match vlan 10-100
!
!  Example 3
class-map type qos match-any TEST
   match ip access-group TEST
!
policy-map type quality-of-service PM_TEST
   class TEST
      set dscp af11
   !
   class class-default
!

Describe the solution you'd like
Add support for the following datamodel in eos_cli_config_gen
class_maps:
  <class-map name>:
    vlan: <str>
    cos: <str>
    ip:
      access_group: <str>
policy_maps:
  qos:
    <PM name>:
      class:
      set:
        dscp: <str dscp field>
        traffic_class: <0-7>
        drop_precedence: < 1-2>

      # Not Implemented
      police:
        cir:
        rate:

hi
are you gonna implement police feature ?;)
thanks for your code.