Synthesis failed for java-automl

Hello! Autosynth couldn't regenerate java-automl. :broken_heart:
Here's the output from running synth.py:
44 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at cbb1e0f chore(deps): update dependency com.google.cloud:libraries-bom to v8.1.0 (#253)
2020-07-16 14:56:54,353 autosynth [DEBUG] > Running: git checkout autosynth-googleapis
Switched to branch 'autosynth-googleapis'
2020-07-16 14:56:54,361 autosynth [ERROR] > Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.
2020-07-16 14:56:54,728 autosynth [DEBUG] > Running: git checkout cbb1e0f5ec1e080d0439a895bee17e4b85341486
Note: checking out 'cbb1e0f5ec1e080d0439a895bee17e4b85341486'.

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 cbb1e0f chore(deps): update dependency com.google.cloud:libraries-bom to v8.1.0 (#253)
2020-07-16 14:56:54,736 autosynth [DEBUG] > Running: git checkout 21f1470ecd01424dc91c70f1a7c798e4e87d1eec
Previous HEAD position was 4f2c9f7 ci(java): run dependency test on Java 8 and 11 (#639)
HEAD is now at 21f1470 chore: add config files for cloud-rad for node.js (#667)
2020-07-16 14:56:54,746 autosynth [DEBUG] > Running: git checkout b56aa06cc99050861c9a9b14d9569bd18eb09604
HEAD is now at b56aa06c feat: Adds AuditLog proto for reading IAM admin logs.
2020-07-16 14:56:54,790 autosynth [DEBUG] > Running: git branch -f autosynth-132
2020-07-16 14:56:54,794 autosynth [DEBUG] > Running: git checkout autosynth-132
Switched to branch 'autosynth-132'
2020-07-16 14:56:54,802 autosynth [INFO] > Running synthtool
2020-07-16 14:56:54,803 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-07-16 14:56:54,803 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/java-automl/132/sponge_log.log
2020-07-16 14:56:54,805 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2020-07-16 14:56:55,024 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/java-automl/synth.py.
On branch autosynth-132
nothing to commit, working tree clean
2020-07-16 14:56:55,177 synthtool [DEBUG] > Ensuring dependencies.
2020-07-16 14:56:55,182 synthtool [DEBUG] > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:b3b47805231a305d0f40c4bf069df20f6a2635574e6d4259fac651d3f9f6e098
Status: Image is up to date for googleapis/artman:latest
2020-07-16 14:56:56,177 synthtool [DEBUG] > Ensuring dependencies.
2020-07-16 14:56:56,189 synthtool [DEBUG] > Cloning googleapis.
2020-07-16 14:56:56,190 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2020-07-16 14:56:56,195 synthtool [DEBUG] > Generating code for: //google/cloud/automl/v1beta1:google-cloud-automl-v1beta1-java.
2020-07-16 14:56:58,225 synthtool [SUCCESS] > Generated code into /tmpfs/tmp/tmpypzze9ty.
2020-07-16 14:56:58,226 synthtool [WARNING] > No replacements made in [PosixPath('/tmpfs/tmp/tmpypzze9ty/google-cloud-automl-v1beta1-java/proto-google-cloud-automl-v1beta1-java/src/**/*.java')] for pattern // Generated by the protocol buffer compiler.  DO NOT EDIT!, maybe replacement is no longer needed?
2020-07-16 14:56:58,230 synthtool [WARNING] > No replacements made in [PosixPath('/tmpfs/tmp/tmpypzze9ty/google-cloud-automl-v1beta1-java/proto-google-cloud-automl-v1beta1-java/src/**/*Name.java'), PosixPath('/tmpfs/tmp/tmpypzze9ty/google-cloud-automl-v1beta1-java/proto-google-cloud-automl-v1beta1-java/src/**/*Names.java')] for pattern /\*
 \* Copyright \d{4} Google LLC
 \*
 \* Licensed under the Apache License, Version 2.0 \(the "License"\); you may not use this file except
 \* in compliance with the License. You may obtain a copy of the License at
 \*
 \* http://www.apache.org/licenses/LICENSE-2.0
 \*
 \* Unless required by applicable law or agreed to in writing, software distributed under the License
 \* is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
 \* or implied. See the License for the specific language governing permissions and limitations under
 \* the License.
 \*/
, maybe replacement is no longer needed?
2020-07-16 14:56:58,230 synthtool [WARNING] > No replacements made in [PosixPath('/tmpfs/tmp/tmpypzze9ty/google-cloud-automl-v1beta1-java/grpc-google-cloud-automl-v1beta1-java/src/**/*.java')] for pattern ^package (.*);, maybe replacement is no longer needed?
2020-07-16 14:56:58,231 synthtool [DEBUG] > 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 "/home/kbuilder/.cache/synthtool/java-automl/synth.py", line 32, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 318, in bazel_library
    destination_name=destination_name,
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 193, in _common_generation
    required=True,
  File "/tmpfs/src/github/synthtool/synthtool/transforms.py", line 208, in move
    f"No files in sources {sources} were copied. Does the source "
synthtool.transforms.MissingSourceError: No files in sources [PosixPath('/tmpfs/tmp/tmpypzze9ty/google-cloud-automl-v1beta1-java/gapic-google-cloud-automl-v1beta1-java/src')] were copied. Does the source contain files?
2020-07-16 14:56:58,281 autosynth [ERROR] > Synthesis failed
2020-07-16 14:56:58,282 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at cbb1e0f chore(deps): update dependency com.google.cloud:libraries-bom to v8.1.0 (#253)
2020-07-16 14:56:58,290 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-07-16 14:56:58,297 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 367, in synthesize_loop
    synthesize_inner_loop(fork, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 411, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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.

During handling of the above exception, another exception occurred:

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 657, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 506, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 637, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 375, in synthesize_loop
    synthesize_loop_single_pr(toolbox, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 401, in synthesize_loop_single_pr
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 411, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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-automl. :sob:
Here's the output from running synth.py:
 > Running: git reset --hard HEAD
HEAD is now at cbb1e0f chore(deps): update dependency com.google.cloud:libraries-bom to v8.1.0 (#253)
2020-07-17 01:45:07,263 autosynth [DEBUG] > Running: git checkout autosynth-googleapis
Switched to branch 'autosynth-googleapis'
2020-07-17 01:45:07,270 autosynth [ERROR] > Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.
2020-07-17 01:45:07,432 autosynth [DEBUG] > Running: git checkout cbb1e0f5ec1e080d0439a895bee17e4b85341486
Note: checking out 'cbb1e0f5ec1e080d0439a895bee17e4b85341486'.

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 cbb1e0f chore(deps): update dependency com.google.cloud:libraries-bom to v8.1.0 (#253)
2020-07-17 01:45:07,439 autosynth [DEBUG] > Running: git checkout 21f1470ecd01424dc91c70f1a7c798e4e87d1eec
Previous HEAD position was 4f2c9f7 ci(java): run dependency test on Java 8 and 11 (#639)
HEAD is now at 21f1470 chore: add config files for cloud-rad for node.js (#667)
2020-07-17 01:45:07,449 autosynth [DEBUG] > Running: git checkout bb46f87724ddd2fd1ce9f9dcb71f147427775592
HEAD is now at bb46f877 Adds bazel build file for public version of AuditData proto for bigquery.
2020-07-17 01:45:07,462 autosynth [DEBUG] > Running: git branch -f autosynth-133
2020-07-17 01:45:07,466 autosynth [DEBUG] > Running: git checkout autosynth-133
Switched to branch 'autosynth-133'
2020-07-17 01:45:07,472 autosynth [INFO] > Running synthtool
2020-07-17 01:45:07,472 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-07-17 01:45:07,472 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/java-automl/133/sponge_log.log
2020-07-17 01:45:07,474 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2020-07-17 01:45:07,676 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/java-automl/synth.py.
On branch autosynth-133
nothing to commit, working tree clean
2020-07-17 01:45:07,814 synthtool [DEBUG] > Ensuring dependencies.
2020-07-17 01:45:07,819 synthtool [DEBUG] > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:b3b47805231a305d0f40c4bf069df20f6a2635574e6d4259fac651d3f9f6e098
Status: Image is up to date for googleapis/artman:latest
2020-07-17 01:45:08,835 synthtool [DEBUG] > Ensuring dependencies.
2020-07-17 01:45:08,846 synthtool [DEBUG] > Cloning googleapis.
2020-07-17 01:45:08,847 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2020-07-17 01:45:08,851 synthtool [DEBUG] > Generating code for: //google/cloud/automl/v1beta1:google-cloud-automl-v1beta1-java.
2020-07-17 01:45:10,630 synthtool [SUCCESS] > Generated code into /tmpfs/tmp/tmpg5t7la1o.
2020-07-17 01:45:10,632 synthtool [WARNING] > No replacements made in [PosixPath('/tmpfs/tmp/tmpg5t7la1o/google-cloud-automl-v1beta1-java/proto-google-cloud-automl-v1beta1-java/src/**/*.java')] for pattern // Generated by the protocol buffer compiler.  DO NOT EDIT!, maybe replacement is no longer needed?
2020-07-17 01:45:10,635 synthtool [WARNING] > No replacements made in [PosixPath('/tmpfs/tmp/tmpg5t7la1o/google-cloud-automl-v1beta1-java/proto-google-cloud-automl-v1beta1-java/src/**/*Name.java'), PosixPath('/tmpfs/tmp/tmpg5t7la1o/google-cloud-automl-v1beta1-java/proto-google-cloud-automl-v1beta1-java/src/**/*Names.java')] for pattern /\*
 \* Copyright \d{4} Google LLC
 \*
 \* Licensed under the Apache License, Version 2.0 \(the "License"\); you may not use this file except
 \* in compliance with the License. You may obtain a copy of the License at
 \*
 \* http://www.apache.org/licenses/LICENSE-2.0
 \*
 \* Unless required by applicable law or agreed to in writing, software distributed under the License
 \* is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
 \* or implied. See the License for the specific language governing permissions and limitations under
 \* the License.
 \*/
, maybe replacement is no longer needed?
2020-07-17 01:45:10,636 synthtool [WARNING] > No replacements made in [PosixPath('/tmpfs/tmp/tmpg5t7la1o/google-cloud-automl-v1beta1-java/grpc-google-cloud-automl-v1beta1-java/src/**/*.java')] for pattern ^package (.*);, maybe replacement is no longer needed?
2020-07-17 01:45:10,637 synthtool [DEBUG] > 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 "/home/kbuilder/.cache/synthtool/java-automl/synth.py", line 32, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 318, in bazel_library
    destination_name=destination_name,
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 193, in _common_generation
    required=True,
  File "/tmpfs/src/github/synthtool/synthtool/transforms.py", line 208, in move
    f"No files in sources {sources} were copied. Does the source "
synthtool.transforms.MissingSourceError: No files in sources [PosixPath('/tmpfs/tmp/tmpg5t7la1o/google-cloud-automl-v1beta1-java/gapic-google-cloud-automl-v1beta1-java/src')] were copied. Does the source contain files?
2020-07-17 01:45:10,676 autosynth [ERROR] > Synthesis failed
2020-07-17 01:45:10,676 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at cbb1e0f chore(deps): update dependency com.google.cloud:libraries-bom to v8.1.0 (#253)
2020-07-17 01:45:10,684 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-07-17 01:45:10,690 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 367, in synthesize_loop
    synthesize_inner_loop(fork, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 411, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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.

During handling of the above exception, another exception occurred:

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 657, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 506, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 637, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 375, in synthesize_loop
    synthesize_loop_single_pr(toolbox, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 401, in synthesize_loop_single_pr
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 411, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, 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 passed, closing! :green_heart:


gitlab: 14.0.5 -> 14.1.0

Motivation for this change
https://about.gitlab.com/releases/2021/07/22/gitlab-14-1-released/
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

What's the reason for the backport label, @talyz ?

It triggers the automatic creation of a backport PR to stable when this is merged to master.

Sure - but I'm asking what qualifies this bump for the stable branch?

Sure - but I'm asking what qualifies this bump for the stable branch?

GitLab updates are usually backported, because security patches and bugfixes are not backported for more than 3 months. If we don't backport this now, we will need to do a huge version jump in three months in order to deliver security updates and bugfixes.

Oh, we just want GitLab as up-to-date as possible in stable to always have the latest security patches and bugfixes in place. The only exception I see to this is when it would cause major and unavoidable breakage, which doesn't seem to be the case here.

You could make the same argument about almost any package and then it makes a farce of the idea of trying to have a stable distribution at all.
I guess what I'm asking is - what is the advantage of porting this back to stable over just running off master?

I don't think that's fair. The point is to prioritize keeping important packages that are likely to pose security risks up-to-date in stable. GitLab is one of those packages. We're not a big team keeping GitLab updated in NixOS, so yes, diverging branches can significantly impact our ability to keep it up-to-date. In case updating the package would cause major breakage, we wouldn't backport the update to stable.
As for why I'm not just running off of master on my production system - severely breaking changes get added to master, which can affect the stability and availability of packages for extended periods of time. Compiler updates, changes to how frameworks are handled, breaking major version upgrades of core dependencies, etc. I want to run a secure and up-to-date version of GitLab, a leaf package, on a stable base.

The problem is, what you might consider to be a leaf package might not be a leaf package to a user. And users who have needs for stability (i.e. you won't have things randomly break on monday morning) and don't get it from the "stable" branch will simply stop updating at completely. And then they don't even get security updates.
I'm not even suggesting here that you maintain a security-backported branch for stable - I'm just suggesting that you don't bump stable unless you actually have a declared vulnerability. And who knows, if you manage to make it 6 months without a security issue, users get that stability as a bonus.

What you're describing is stale, not stable. You're just locking in the bugs and issues that exist at a certain point, refusing to fix them. Stable should be usable in practice, not ignored. That might imply leaving many packages untouched, but GitLab should be kept up-to-date: firstly, the scenario you describe where no security issues arise in six months doesn't happen in practice and secondly, a slow trickle of updates is much easier to handle than jumping multiple versions all at once when the next version of NixOS comes around (if it's even possible to upgrade cleanly at that point).
As stated earlier, major breaking changes should not be backported.
If GitLab is not a leaf package in your setup, I'm not sure what you're doing, but it probably falls outside any usage we can reasonably account for.

What you're describing is stale, not stable. You're just locking in the bugs and issues that exist at a certain point, refusing to fix them.

New releases not only fix bugs but also introduce them - especially when these releases introduce features.
And if 6-month old software is "stale", then frankly 90% of the internet is running on extremely stale software - and it's not accidental or due to laziness.

a slow trickle of updates is much easier to handle than jumping multiple versions all at once when the next version of NixOS comes around

That is the whole point of the stable branch. A user who is using the stable branch already accepts that a "big" (not that big, it's only 6 months) upgrade is going to happen every 6 months. This is something that can be planned for and pre-tested. A continual trickle of updates means every time you think you're just updating to make sure you're security patched, oops, it could break everything - hope you were planning on staying late tonight...
Incidentally if it's not safe to skip versions in upgrades for GitLab, then that itself is something I would worry about a lot, as it implies that a user's system that gets neglected for a few months (perhaps an auto-update trigger got broken?) would be in for trouble the next time they do update. So really, if that's the case, then any user's system is potentially going to fall victim to this - which would make me want to pre-plan updates even moreso rather than have them quietly trickled out to me on a "stable" branch.

If GitLab is not a leaf package in your setup, I'm not sure what you're doing, but it probably falls outside any usage we can reasonably account for.

GitLab is a package that exposes APIs left, right and centre. People build all sorts of integrations with GitLab that may be sensitive to all kinds of subtleties and corner cases.

And if 6-month old software is "stale", then frankly 90% of the internet is running on extremely stale software

For most software it probably isn't - many packages only receive one or two updates per year, but GitLab is updated constantly.

A continual trickle of updates means every time you think you're just updating to make sure you're security patched, oops, it could break everything - hope you were planning on staying late tonight...

This point really is secondary - the main point is that failing to backport will leave a vulnerable and obsolete version of GitLab that no one should be running in stable. The mindset of not backing up your production servers because you're running off of stable won't work in general, but especially not with GitLab.
GitLab issue bug fixes only for their latest stable release and security patches for the two previous monthly releases, leaving three months of unapplied security patches in the best case, if we don't backport. See the release and maintenance policy for more info.

Incidentally if it's not safe to skip versions in upgrades for GitLab, then that itself is something I would worry about a lot, as it implies that a user's system that gets neglected for a few months (perhaps an auto-update trigger got broken?) would be in for trouble the next time they do update.

The upgrade guidelines state that, when upgrading from one major version to the next, you have to go from the last minor of the previous major release to the first minor release of the next major release. Jumping between minor and patch releases within the same major release should be fine.

GitLab is a package that exposes APIs left, right and centre. People build all sorts of integrations with GitLab that may be sensitive to all kinds of subtleties and corner cases.

True, but even outside NixOS, there's no way to run an instance of the same minor version of GitLab with security patches for six months, because such a release doesn't exist. If you're that sensitive to potential API changes and don't want to update your code, your only alternative is to not upgrade at all. The way you would normally would run GitLab on any other distro is to add their third-party repository, install and update it from there, always getting the latest stable release, so this is nothing unique to NixOS. If you've been running GitLab somewhere else, you should be used to this, especially if you're at the level where you're heavily utilizing the API.
Also, major revisions and deprecations to the APIs are only made in major releases. Depending on the timing, we may have to backport major releases to be able to stay up-to-date (they should release on May 22 every year, which sadly collides with our release schedule). That's not really relevant to this PR, though, since this is a minor release update.


Fixed dependency issues and updated README

Fixed dependency issues caused by Bower deprecation, moved all dependencies to NPM instead;

Added dependency "natives" for the application to work with Node.js ^10.0.0;

Fixed some vulnerability issues in dependencies by running npm audit fix, there's still a good bunch of vulnerabilities that require manual intervention (TODO: fix them all);

Rewrote the README file to reflect changes in dependency management, clarify a likely to happen issue with MongoDB directory ownership and to state the project is currently being worked at.

Fechei a pull request porque comecei a fazer algumas mudanças de coding style e novas práticas que talvez você não vá querer incorporar no seu projeto.


bump polkadot 0.9.33

Thanks for the PR @blasrodri. I have such a bump in a branch I am working in but indeed not in master :)
Did you bump because you run into issues or for the sake of keeping things fresh ?
I would rather not use the polkadot release tag but a substrate-monthly release as before. Moreover, there is no reason to use the 'old' Polkaot v0.9.33 since we are at 0.9.36.
If you can edit and use the latest substrate monthly (monthly-2023-01), we could merge that to master.

Thanks for the quick reply. Seems to be working fine with the monthly-* tag!


[branch-2.0-pick] Picks "Fix Fix some bugs about sequence column #24915"

Proposed changes
picks https://github.com/apache/doris/pull/24915
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run feut


Include Omero-channels-metadata update in import-ome-zarr task

Checklist before merging

[x] I added an appropriate entry to CHANGELOG.md

Last missing point from #578:

[ ]  Assess whether we also need to add values for Window and/or colormap, if missing;

This is ready for a review, and it will be the last contribution to the upcoming v0.13.0.

(see here for a recap: https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/578#issuecomment-1770273392)

Thanks for the review, merging now


Invalid status_code received: 401. Possible solutions: Authorization header either missing or not provided.

At the part where I insert the API key without a user, getting the error

Invalid status_code received: 401. Possible solutions: Authorization header either missing or not provided.
Any ideas?

Please use the Pterodactyl Discord for configuration related support instead of GitHub issues.


win32 debug documentation link is broken

win32::debug is broken.
No issue to generate it on my machine.

Oh, I think that might be because of this. 😉
https://github.com/microsoft/windows-docs-rs/blob/c105bd478d8750cb785a8ac8654ed0dee527495c/.gitignore#L2

Oh, I think that might be because of this. 😉
https://github.com/microsoft/windows-docs-rs/blob/c105bd478d8750cb785a8ac8654ed0dee527495c/.gitignore#L2

I'll publish another update when I get a moment - thanks for letting me know!

I'll publish another update when I get a moment - thanks for letting me know!

Oh, I think that might be because of this. 😉
https://github.com/microsoft/windows-docs-rs/blob/c105bd478d8750cb785a8ac8654ed0dee527495c/.gitignore#L2

Good catch !

Oh, I think that might be because of this. 😉
https://github.com/microsoft/windows-docs-rs/blob/c105bd478d8750cb785a8ac8654ed0dee527495c/.gitignore#L2

Good catch !

This has now been fixed.


Support skip_lookup for Dataset and Table

Support the skip_lookup argument for Dataset and Table object creation.

Will this become the preferred approach for operations that do not involve dataset or table metadata/management? So that with Table#insert, for example, after this change, should the example be the following?
dataset = bigquery.dataset "my_dataset", skip_lookup: true
table = dataset.table "my_table", skip_lookup: true

rows = [
  { "first_name" => "Alice", "age" => 21 },
  { "first_name" => "Bob", "age" => 22 }
]
table.insert rows

My opinion is the main code example should show the default behavior which is to perform the lookup, but should also have additional named code examples that show skipping the lookup. Similar to how main code example for Pub/Sub's Project#topic shows the lookup, but an additional named code example shows the skip_lookup option.


UploadedFile should be converted to TemporaryUploadedFile

Description
UploadedFile::fake() should covert to TemporaryUploadedFile
Functional changes

[x] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[x] Documentation is up-to-date.

Please explain what the issue is here because you have provided very little context about what you are fixing

when I use SpatieMediaLibraryFileUpload in test, it should create a record to media table.
before v3.2.76, it work correctly, but after v3.2.76, it is broken
I found this
v3.2.76
https://github.com/filamentphp/filament/blob/04f2bcff66799d14a883818cdda8997fecc9ca3b/packages/forms/src/Testing/TestsForms.php#L35
it will call Livewire\Features\SupportTesting\Testable::uplolad
https://github.com/livewire/livewire/blob/b818a5b85f5ee041b6568fea16a2926a7b91c193/src/Features/SupportTesting/Testable.php#L129-L138
but v3.2.77
only set value to form
https://github.com/filamentphp/filament/blob/v3.2.77/packages/forms/src/Concerns/InteractsWithForms.php#L65
this change missing Livewire\Features\SupportTesting\Testable::uplolad

Thank you for providing more detail


Get balance in wei from provider instead of eth

needs https://github.com/trustlines-protocol/relay/pull/411 to work
closes https://github.com/trustlines-protocol/relay/issues/274

Codecov Report

Merging #307 into master will increase coverage by 0.04%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #307      +/-   ##
==========================================
+ Coverage   62.55%   62.59%   +0.04%
==========================================
  Files          19       19
  Lines        1199     1195       -4
  Branches      226      226
==========================================
- Hits          750      748       -2
+ Misses        387      385       -2
  Partials       62       62

Flag
Coverage Δ

#integration
33.13% <0%> (-0.06%)
:arrow_down:

#unit
62.59% <33.33%> (+0.04%)
:arrow_up:

Impacted Files
Coverage Δ

src/wallets/EthersWallet.ts
68.23% <0%> (+0.41%)
:arrow_up:

src/wallets/IdentityWallet.ts
62.87% <0%> (+0.19%)
:arrow_up:

src/providers/RelayProvider.ts
62.79% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Created README.md

Hi @roshanrajeev superb job done. Would be nice if you added a lil more description to your PR. Let me know if you need help with that.

Welcome @roshanrajeev! I really like your introduction, makes me wonder what quantum computing is like these days.
For your blog – is that https://roshanrajeev.com/? I was going to suggest blogging about the different CMS options you tried but I see you’ve already done this 😅 (https://roshanrajeev.com/blog/2021-04-06-the-best-cms-for-gatsby/)

I'm glad to hear that you're interested in quantum computing! The field is evolving rapidly, and there are many exciting developments taking place. If you have any questions or anything related to quantum computing comes up, let me know. 😅


Captions are still overlapping

@gaagul _a please take it up on priority _t. It has been reported by a client _t who uses a lot of images in his documentation.
//cc @AbhayVAshokan

@sandip-mane I had noticed this issue yesterday and added fix along with https://github.com/bigbinary/neeto-editor/pull/1080.
Upgrading the version of neeto-editor in neetoKb to the latest version will solve the issue. v1.31.5 is the latest version.

@gaagul could you please update the package in all the apps that use it?

@gaagul could you please update the package in all the apps that use it?

These changes will be rolled out on monday with compliance on all other apps, The changes are added to neetoKb: https://github.com/bigbinary/neeto-kb-web/pull/6145

I will close the issue after testing in all the products after next compliance.

Closing the issue since the latest editor version is released via compliance.


Missing cookbooks : Could not satisfy version constraints for : esri-iis

Hi @pbobov ,
I am getting the following error while executing the ArcGIS Enterprise recipe. Can you please help me in resolving the issue?
Missing Cookbooks:
Could not satisfy version constraints for: esri-iis
Expanded Run List:

arcgis-enterprise::system
esri-iis
arcgis-enterprise::server
arcgis-enterprise::server_wa

System Info:
chef_version=13.8.5
platform=windows
platform_version=6.3.9600
ruby=ruby 2.4.3p205 (2017-12-14 revision 61247) [x64-
program_name=C:/opscode/chefdk/embedded/bin/chef-solo
executable=C:/opscode/chefdk/embedded/bin/chef-solo

ArcGIS Chef cookbooks v3.2.0 and all the dependent cookbooks are packaged in https://github.com/Esri/arcgis-cookbook/releases/download/v3.2.0/arcgis-3.2.0-cookbooks.zip. You will need to extract the archive to C:\chef directory.

@pbobov Thanks for your help. I have extracted all the cookbooks, and now getting an error - FATAL: UncaughtThrowError: uncaught throw "Unsupport
ed ArcGIS version". Here is the error log -
UncaughtThrowError
uncaught throw "Unsupported ArcGIS version"
Cookbook Trace:
c:/chef/cache/cookbooks/arcgis-enterprise/attributes/default.rb:81:in throw'   c:/chef/cache/cookbooks/arcgis-enterprise/attributes/default.rb:81:in from_fi
le'
Relevant File Content:
c:/chef/cache/cookbooks/arcgis-enterprise/attributes/default.rb:
74:  end
75:
76:    case node['arcgis']['desktop']['version']
77:      when '10.5.1'
78:        default['arcgis']['desktop']['product_code'] = '{4740FC57-60FE-45BB-
B513-3309F6B73183}'
79:        default['arcgis']['licensemanager']['product_code'] = '{DF06C3DC-54B
5-49A1-9756-B68FD65A0AD0}'
80:      else
81>>       throw 'Unsupported ArcGIS version'
82:      end
83:
84:
85:
86:
System Info:
chef_version=13.8.5
platform=windows
platform_version=6.3.9600
ruby=ruby 2.4.3p205 (2017-12-14 revision 61247) [x64-mingw32]
program_name=C:/opscode/chefdk/embedded/bin/chef-solo
executable=C:/opscode/chefdk/embedded/bin/chef-solo
Running handlers:
[2018-04-11T12:31:16+00:00] ERROR: Running exception handlers
Running handlers complete
[2018-04-11T12:31:16+00:00] ERROR: Exception handlers complete
Chef Client failed. 0 resources updated in 08 seconds
[2018-04-11T12:31:16+00:00] FATAL: Stacktrace dumped to c:/chef/cache/chef-stack
trace.out
[2018-04-11T12:31:16+00:00] FATAL: Please provide the contents of the stacktrace
.out file if you file a bug report
[2018-04-11T12:31:16+00:00] FATAL: UncaughtThrowError: uncaught throw "Unsupport
ed ArcGIS version"

What ArcGIS version do  you use?
ArcGIS Chef Cookbook v3.2.0 support ArcGIS 10.4 to 10.6.
Did you set the ArcGIS version in the JSON file?
{
  "arcgis":{
    "run_as_password":"Run_As_Pa$$w0rd",
    "run_as_user":"arcgis",
    "version":"10.5.1",
...
}

The dialog most likely pops up because the ArcGIS Server installation directory is not accessible. By default arcgis-enterprise Chef cookbook installs ArcGIS Server in C:\\Program Files\\ArcGIS\\Server.  You can change the installation directory by setting arcgis/server/install_dir attribute in the JSON file.
{
  "arcgis" : {
     ...
     "server" : {
        "install_dir" : "C:\\ArcGIS",
        ...
   }
   ...
}

I'm not sure what windows-package with installation type custom  means...
This issue probably duplicates https://github.com/Esri/arcgis-cookbook/issues/129.


Escape only double-quote but no other ASCII char in multipart uploaded filenames

Please see related discussion and research in rack/rack#323.
RFC 1867 does not say to escape ASCII chars in filenames in multipart uploads using %XX (the URL-encoding scheme from RFC 1738). No browser I tried (see list in rack/rack#323) escapes ASCII filename characters in this way so Rack shouldn't either, with one exception: it could emulate either Firefox or Webkit by escaping only the double-quote character.

Firefox escapes double-quote as \".
Webkit escapes double-quote as %22.

All other ASCII characters--including single quote ('), percent (%), ampersand (&), question mark (?), backslash (\)--should be passed straight through without encoding.
Background: this bit me because rack-test escapes the entire filename using RFC 1738 encoding and rack unescapes the filename using the same method. I had a passing test in my app to verify that special characters were allowed in filenames and it was passing, but later I discovered that in a real browser with a % sign in the filename it raised an error in rack. The real browser did not escape the % sign but rack tried to unescape it. If rack-test were behaving more like a real browser and not escape percent signs, my test would have told me something was wrong.
The correct fix is for both rack-test and rack to be updated (which is why rack/rack#323 was filed along with this one).
Thanks!
cc @raggi

Leaving this open since the upstream Rack issue is still open after more than five years. Impressive! 😃
@junaruga This one is probably pretty good to get sorted out before releasing a 1.0 version eventually. The downside is that it requires a Rack fix upstream also.

@perlun ok, shall we use "Milestone" feature to recognize which task is for "1.0.0"?

Sure, works for me.


Tooltip can be outside of window

Hi !
For content on the side of the screen there is the possibility that the tooltip is partially outside of the window.
What about making sure the tooltip is always fully visible?
(Thanks for this series it's really great!)

yes, i agree it's a bummer of this implementation that the tip can go outside the window. i'm waiting for CSS anchor() to help with that, as it'll provide a way to get that style with ease. So I was a bit lazy and didnt want to write JS that would mitigate the off screen presentation.
glad you like the series, hopefully it's providing good insights into your own components and their ux! 🙂
closing for now, but expect the tooltip to be revisited in a future episode, where i'll round out issues in accessibility and presentation 👍🏻


Index and Middle finger columns stop working

Cheapino v1 btw.
Pretty consistently the two columns on the right board stop working for like 30 seconds or so. I've checked all of the solder points and I think they're all fine. I've also used both QMK and Vial, results are the same.

I've removed the keys that stop working. (Also, they all stop working and start again at the same time)

Hi. This sounds very annoying. Did you also check the soldering on the left part? Could you send a picture both sides of the left part also? These two columns both end up in one trace going through the rj45 socket ti the other side and into one pin of the mcu.

Thanks for the quick response!
I don't see anything wrong with the solder on the left, although it's not pretty I don't think it is causing issues. Attached are two pictures of the left side.

Looks pretty good. I agree. When this happens, is it related to the encoder? Does it help turning the encoder?

Ill dig out the schematics tomorrow and find the trace for this column. Typing from my bed and my wife is annoyed;)

Looks pretty good. I agree. When this happens, is it related to the encoder? Does it help turning the encoder?

As far as I know, no. It happens when I am just typing and not touching the encoder. I haven't tried to use the encoder to fix it, but I will try when it happens again.
No rush on resolving this, thanks again!

Hi again, I checked the layout for v1, and these two column are both mapped to column 1(with different diode directions per physical column).
Column 1 is routed through the square rj45 socket holes, so I would recommend you reflow these(especially the one on the right side seems a bit blobby, but hard to tell from pic: might be a cold joint).
The trace ends up at pin 4 on the mcu, counting from top left(marked 29). Try reflowing this as well, maybe add a little solder, seems a tad sparse maybe.
Also, cant tell if you socketed the mcu, but if you did, it might be worth a try to gently pry it out, and check if leg at 29 is shorter than the others(ie was not pushed entirely in when soldered)

Thanks so much! I've reflowed the square socket holes and the 29 pin. I don't think the 29 leg is shorter, so I left it for now. I will try this if the issue keeps occurring. So far so good though!


CRI API reference at Container Runtime page is stale

This is a Bug Report
/sig node
/kind bug
/priority important-soon
/help
Problem:
This page https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cri-versions suggests that v1alpha2  is still supported. However it was not a case for a few versions now.
Also this page https://kubernetes.io/docs/concepts/architecture/cri/ links the quite old CRI API proto page. Simply pointing on master branch should be better unless we want to keep bumping the link for each release.
Proposed Solution:
Page to Update:

https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cri-versions
https://kubernetes.io/docs/concepts/architecture/cri/

/triage accepted

/assign

I would like to work on this issue.

/assign

We need to correct both statements here, as they are misleading. They suggest that users can rely on v1alpha2, which is incorrect because v1alpha2 has been deprecated and should not be used as a fallback.
https://github.com/kubernetes/website/blob/92fad835876907c333dc185fcc78aa7545aa5de5/content/en/docs/setup/production-environment/container-runtimes.md?plain=1#L172-L179

This is important, but:
/remove-priority important-soon
/priority important-longterm
The issues at https://github.com/kubernetes/website/issues?q=is%3Aissue+is%3Aopen+label%3Apriority%2Fimportant-soon are the ones we really want to focus on.

sorry, didn't mean to hijack your prioritization. I was mostly thought from severity perspective as the info we give is incorrect for a few releases already.

The issue is fixed here: https://github.com/kubernetes/website/pull/48398


Control widget does not currently support directly inserting blazor html components

It seems the control widget is expecting SVG markup rather than directly inserting blazor components.
In my scenario I'd like to insert a menu component as the the contol's UI but it is not being displayed.

Hello, can you show me what you tried?

I eventually got it to work by wrapping it in a foreignobject. But still it wasn't immediately obvious that it was expecting svg.

It is not, unless your node is a SVG itself then your control needs to match the layer. I'm not sure why it didn't work for you. Maybe you can just tell me the steps to reproduce it for me?

I was attaching the control to links, which as it turns out exist in the svg layer and thus the control widget needed to be svg too. Instead I directly put a MudMenu (from MudBlazor) in the widget. Then when that didn't work I eventually copied the svg markup from one of the examples on the website then inserted a foreignobject to wrap around the MudMenu.
I'm away from my PC at the moment so I'll post the markup later.

Here's what ended up working:
@if (Model is SvgNodeModel or BaseLinkModel)
{
    <foreignObject width="50px" height="50px" style="overflow:visible">
        @Menu
    </foreignObject>
}
else
{
    @Menu
}

@code
{
    RenderFragment Menu =>
        @<MudMenu Dense="true"
                  MaxHeight="400"
                  ActivationEvent="MouseEvent.LeftClick"
                  AnchorOrigin="Origin.CenterRight"
                  TransformOrigin="Origin.CenterLeft">
            <ActivatorContent>
                <MudFab<EMAIL_ADDRESS>                        Color="Color.Info"
                        Size="Size.Medium"
                        Title="Transition Menu"/>
            </ActivatorContent>
            <ChildContent>
                <MudMenuItem<EMAIL_ADDRESS>OnClick="@(() => InsertNode(NodeType.Action))">Insert New Action</MudMenuItem>
                <MudDivider/>
                @if (Model is TransitionLinkModel transitionLink)
                {
                    <MudMenuItem<EMAIL_ADDRESS>OnClick="@(() => EditTransition(transitionLink.Transition.Id))">Edit Transition</MudMenuItem>
                }
                <MudMenuItem<EMAIL_ADDRESS>OnClick="@(DeleteTransition)">Delete Transition</MudMenuItem>
            </ChildContent>
        </MudMenu>;
}

Initially, I only had the part that's in the else branch above but that didn't work.