React to pydata-sphinx-theme theme change

Problem
Somewhat related to https://github.com/pydata/pydata-sphinx-theme/issues/745
pydata-sphinx-theme has a theme switch allowing to go from a light to a dark theme. We could have the embedded jupyterlite respect the current theme flavor.
In order to do this, we need to tell JupyterLab app which theme to use:
Proposed Solution
For replite
For replite it's quite straightforward, we can simply change the URL to pass the right query parameter ?theme=Jupyterlab Dark.
For JupyterLite and RetroLite
We can probably force JupyterLab to expose its app object with:
iframe.addEventListener('load', () => {
    iframe.contentWindow.document.body.dataset.exposeAppInBrowser = "true";
});

And then use the iframe.contentWindow.jupyterapp object to access the themeManager and make it switch to the theme flavor that is currently used in the docs?
Pinging @jtpio in case you have some ideas

We can probably force JupyterLab to expose its app object with:

This can also be enabled with the exposeAppInBrowser setting in jupyter-lite.json: https://jupyterlite.readthedocs.io/en/latest/reference/schema-v0.html#jupyter-config-data

Maybe https://github.com/jupyterlite/jupyterlite/pull/525 could also be relevant and apply to more apps than just repl.

Another idea would be to have a JupyterLab extension honoring the prefers-color-scheme CSS media feature: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme
Which is what most light / dark themes use nowadays to choose a default theme on page load.
Although this could be done separately and would not sync the theme when a user switches from light to dark by clicking on the button.

I wanted to work on it from our theme side and I have few comments to add here

Another idea would be to have a JupyterLab extension honoring the prefers-color-scheme CSS media feature

That won't be sufficient as theming is not natively supported by Sphinx so the few theme implementing it (pydata-sphinx-theme, sphinx-book, lutra and furo to my knowledge) are doing it in different ways and can enforce theming that is not matching with this parameter.
Also as they are all doing it a different way, I think the best way to proceed is to expose a JS handle that themes can switch when changing the theme. by doing so you will be compatible with any theme as long as their maintainers are happy to support your extention. We are willing to work on it from pydata-sphinx-theme (https://github.com/pydata/pydata-sphinx-theme/issues/745) but we are missing this interface.

looking down the web it seems that I'm not facing any cross-domain issues when manipulating the content of the iframe via javascript. I tried the following code and it worked like a charm:
var frm = document.querySelectorAll(".jupyterlite_sphinx_iframe")

var cssLink = document.createElement("link");
cssLink.href = "style.css";
cssLink.rel = "stylesheet";
cssLink.type = "text/css";

frm.forEach( frame => {
    frame.contentWindow.document.head.appendChild(cssLink);
})

I think the next step for me is to change the css when a theme changed is triggered in the page.
3 questions:

Are all the css already loaded in the iframe (meaning both the dark and light theme of jupyterlab) ?
What is the parameter that drive the used theme in jupyterlite ?
Is it the same for all 3 supported interfaces (jupyterlite,  retrolite and replite) ?

Uploading MobileGame …

Hi!
I ended up here on this issue while reviewing pydata/pydata-sphinx-theme#1900. I then started working on my own implementation (in pydata-sphinx-theme) to sync color mode (light/dark) between pydata-sphinx-theme and jupyterlite-sphinx. I was able to come up with a reliable, working way to switch a loaded JupyterLite iframe from one theme to another. But while working on this I realized that I also really want a way to tell a JupyterLite application to use a particular theme before it loads. That way we avoid the iframe flashing from light to dark as it loads on the page.
I want to be able to provide the theme configuration at run time with JavaScript, rather than at build time. The reason why is that a PST page doesn't know until run time whether it is in dark or light mode. This is because PST's JavaScript stores the user's preference in local storage, and then it queries local storage before the page renders to determine whether the page should be in dark or light mode.
After digging through docs and source code, I'm not sure how to load a JupyterLite application with a given theme at runtime. As mentioned in this issue's description, for REPLite I can get consistent behavior by passing theme as a query string parameter like so: ?theme=${encodeURIComponent("Theme Name")}. But this does not work for a JupyterLite iframe.
If every JupyterLite application took theme as a query string parameter and ensured that the application applies that theme before it renders, that would solve my problem.
Is there some other way to load JupyterLite at run time with a given theme?
PS. As a side note, I think I discovered a bug while working on this. If you use jupyterlite-sphinx's directives to put a REPLite and JupyterLite together on the same page, the JupyterLite instance will follow the theme set in the REPLite instance. So for example, if I click to load the JupyterLite instance before clicking a dark-mode REPLite loader, then the JupyterLite instance will load in light mode. If I click to load the dark-mode REPLite instance first, then JupyterLite will load in dark mode.

Is there some other way to load JupyterLite at run time with a given theme?

Although probably less convenient that a URL parameter, there could be a bridge between the host page and the IFrame forwarding JupyterLab commands, similar to https://jupyterlite.readthedocs.io/en/stable/howto/configure/advanced/iframe.html.
Otherwise there was some experimentation at some point about being able to extension the REPL URL parameters, which could maybe be applied to other JupyterLite apps too (lab, notebook, voici?): https://github.com/jupyterlite/jupyterlite/pull/525. It's still a draft, but it could be interesting to revive the PR.

I think I discovered a bug while working on this. If you use jupyterlite-sphinx's directives to put a REPLite and JupyterLite together on the same page, the JupyterLite instance will follow the theme set in the REPLite instance. So for example, if I click to load the JupyterLite instance before clicking a dark-mode REPLite loader, then the JupyterLite instance will load in light mode. If I click to load the dark-mode REPLite instance first, then JupyterLite will load in dark mode.

This is because JupyterLite stores settings (for example the theme), in the browser storage by default. Which would then be shared when the different apps are served from the same host / port. But this can normally be disabled using a volatile storage driver like memoryStorageDriver: https://jupyterlite.readthedocs.io/en/stable/howto/configure/storage.html#settings-storage

Thanks @jtpio for the explanation!
I was aware of the iframe bridge method to change the theme of a running Jupyter app instance. I assume that you're suggesting to use the iframe bridge not just to change the theme of a running instance but to wait for a signal from the host page to load the Jupyter app with a particular theme. I don't think I have enough know-how to revive jupyterlite/jupyterlite#525, but for jupyterlite-sphinx, I could create an extension that essentially copies functionality from the repl-extension: by parsing theme out of the iframe's URL query string and calling themeManager.setTheme(themeName).
As for storing settings, would it make sense to change jupyterlite-sphinx so that it uses memoryStorageDriver by default? That makes sense to me on the one hand because it seems that there is a valid use case to have several JupyterLite instances on the same page, or across a set of pages (but still with same host and port), with different configurations. On the other hand, it seems that there are other valid use cases for which this default would be problematic.

I could create an extension that essentially copies functionality from the repl-extension: by parsing theme out of the iframe's URL query string and calling themeManager.setTheme(themeName).

A custom extension sounds good for now. Then maybe we could try to revive https://github.com/jupyterlite/jupyterlite/pull/525 to see if it can be made more generic.

As for storing settings, would it make sense to change jupyterlite-sphinx so that it uses memoryStorageDriver by default?

It might indeed make sense. If this is the case by default, we could then document how to disable it for those who really need persistence. Folks browsing documentation likely don't use the JupyterLite REPL and apps to persist content and settings.


Brother, PLEASE HOW TO SOLUCIONE ACC NO Started? D:  Please HELP

Please HELPPPP

Agar-lvlgen is abandoned for now. You are free to look at the code.


In the identities view, it'd be great to have a drop-down filter to limit view to a single domain

I realise that there is already a filter, and this should not replace that, but having to type the domains all the time is a pain.

This issue was moved to modoboa/modoboa-admin#4


deps: bump k8s to 1.6.2 in order to fix wrong dep issue

kubernetes/apiextensions-apiserver@cf97893

run skydive-compile-tests

run skydive-compile-tests

run skydive-compile-tests

run skydive-compile-tests

run skydive-scale-tests


Azure OpenAI logic

implements frontend for: https://github.com/grafana/grafana-llm-app/issues/55
This allows users to use azure openai like openai.
e.g.
import { llms } from '@grafana/experimental';

const enabled = await llms.azure.enabled();

const stream = llms.openai.streamChatCompletions(...);

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


cmd/go: in go 1.21 module, go mod tidy and 'go list -m -u all' disagree over which go.sum lines are needed

What version of Go are you using (go version)?

$ go version
go version go1.21rc3 darwin/arm64

Does this issue reproduce with the latest release?
No(-ish).
I first ran into this in a module whose 'go' line is 1.21, so the latest release today (1.20.6) isn't applicable.
If I change the 'go' line to 1.20, then 'go mod tidy' no longer deletes as many go.sum lines, and the issue doesn't reproduce.

I ran go mod tidy in a medium sized local module whose go.mod has 'go 1.21' (primarily to help test this language version and its semantics, not because I need it; this go.mod file isn't public).
Then I ran go list -m -u all.
Edit: It turned out trivial to trigger the issue with a very minified top-level go.mod file.
The usual list of modules and available updates, and exit code 0.
What did you see instead?
$ go list -m -u all
go: updates to go.sum needed, disabled by -mod=readonly
$ echo $?
1

Running the go list command with -mod=mod re-adds the go.sum lines and makes the command work.
Or setting go to 1.20 instead of 1.21 and re-running go mod tidy also works around the issue.

Here's a test case version. I have not managed to whittle it down but I think I see a way to make it stop breaking (not the right way, but a way).
[!net:golang.org] skip

env GOPROXY=https://proxy.golang.org/
env GOSUMDB=

! go list
stderr 'missing go.sum entry'
go mod tidy
go list all
cat go.sum

go list -m -u
cat go.sum

go list -m -u all
cat go.sum

go list -mod=mod -m -u
cat go.sum

go list -mod=mod -m -u all
cat go.sum
stdout xxx

-- go.mod --
module m
require golang.org/x/build v0.0.0-20230726111318-84c18c56e0b0

-- x.go --
package p; import _ "golang.org/x/build/maintner/reclog"

After CL 513778 is submitted to the Go 1.21 release branch, we can move this to the Go 1.22 milestone.

Submitted the band-aid to the Go 1.21 release branch. Now a Go 1.22 bug.

I think a proper fix is in the general direction of #40775. The set of checksums to retain should be associated with the modload.Requirements struct in some way rather than tracked as a global variable.

@matloob, @samthanawalla: this is a code cleanup needed in cmd/go. I expect that a proper solution to it will be fairly involved; there is an unfortunate amount of communication through global variables in the code that updates the go.sum file.


fix: cast node.size to IntegerLiteral for qubit register size

Issue: #240
Description of changes:
Fixes bug [#240] by casting node.size into IntegerLiteral.
Building a circuit from a quasi string raises an AttributeError exception in case the qubit register is specified as a string literal.
Testing done:
A unit-test is added that checks that the AttributeError is not raised anymore.
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x ] I have read the CONTRIBUTING doc
[ x] I used the commit message format described in CONTRIBUTING
[x ] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@EuGig Thank you for your contribution! Could you please add details to the PR description on what you have tested, as well as a unit test showing that the issue is resolved by your change?

Hi @rmshaffer! Tests added 👍
Please, let me now if the PR is ok!

@EuGig to ensure that code formatting is correct, please run tox -e linters locally, commit any changes it makes, and/or fix any problems it finds! thank you.

This is great, thanks @EuGig!
I'm just looking what the spec says about casting here: https://openqasm.com/language/types.html#casting-specifics. I feel like the spec itself could do with some clearing up with regard to what constants are allowed for the 'size' when declaring a register - https://openqasm.com/language/types.html#classical-bits-and-registers does not mention it. Though https://openqasm.com/language/types.html#qubits mentions that indexing by constant values must be supported.
I personally feel as though qubit["1" != "0"] r1; where a bool is cast to int feels a little off, and maybe shouldn't be allowed; but then again int array['a']; is a valid array definition (with length 97) in C, so maybe it's not unacceptably weird.

Thank you @rmshaffer! I'll continue working on the PR.

Thank you @EuGig for your work on this so far! Because the unitaryHACK period is ending, I'm going to merge the PR in its current state into the branch feature/integer-literal-cast, and I'll assign the issue to you and close it so that you get credit for your contribution.
I'll then open a new draft PR to merge that feature/integer-literal-cast branch to main, which we can use to continue working on this until it's ready to go.
If you are able to continue to make some of the suggested changes, please open another PR from your fork which targets the feature/integer-literal-cast branch.


Show if vendor has active interfaces on vendor page

On Vendor search page could we indicate of that vendor has active interfaces and allow to sort by this field? This will make it easier for user's of the app as we start to configure more interfaces for loading.
May need input from @aaron-collier. I believe in design doc here
The Vendor model includes a  has_active_vendor_interfaces

Done.


Add teaspoon javascript runner

Tried to add a custom test runner for teaspoon and I'm getting the error: Not a test file
Can you show me what I'm doing wrong?
function! test#javascript#teaspoon#test_file(file) abort
 return a:file =~# '_spec\.(js|coffee|js.coffee)$'
endfunction

function! test#javascript#teaspoon#build_position(type, position) abort
  if a:type == 'nearest'
    return [a:position['file'].':'.a:position['line']]
  elseif a:type == 'file'
    return [a:position['file']]
  else
    return []
  endif
endfunction

function! test#javascript#teaspoon#build_args(args) abort
  return a:args
endfunction

function! test#javascript#teaspoon#executable() abort
  if filereadable('./bin/teaspoon')
    return './bin/teaspoon'
  elseif filereadable('Gemfile')
    return 'bundle exec teaspoon'
  else
    return 'teaspoon'
  endif
endfunction

This error means that your test filename wasn't recognized by the regex. Vim regexes are a bit weird, if you want them to behave normally, you need to put "\v" at the beginning, so '\v_spec.(js|coffee|js.coffee)$' should work.

That worked! Thanks for the fast response and this great plugin.


[Task] Integrate with CRUD Apis for library persistence

@arunvjn can this be marked as done?

Yes @bharath31
Task complete in https://github.com/appsmithorg/appsmith/pull/17895


showArraySize should default to false if undefined.

I'm submitting this PR because I think the extension behavior changed for me and I see showArraySize default changed from true to false about a week ago.
I don't fully understand this code base. I don't see why the true/false is hardcoded in the modified line. I would expect that to refer to structure in extension/src/json-viewer/options/defaults.js.

Thanks, we have merged a lot of PR's and we missed this.


Synthesis failed for java-datalabeling

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

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 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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:30:51 [INFO] Running synthtool
2020-05-05 21:30:51 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:30:51,244 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:30:51,376 synthtool > Ensuring dependencies.
2020-05-05 21:30:51,387 synthtool > Cloning googleapis.
2020-05-05 21:30:51,387 synthtool > Using precloned repo /tmpfs/tmp/tmpfnnoxo_l/googleapis
2020-05-05 21:30:51,392 synthtool > Generating code for: //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java.
2020-05-05 21:30:51,502 synthtool > Failed executing bazel build //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/d0be3d6e618947eff2f49cdbc7b2804b/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/tmpfnnoxo_l/googleapis/hs_err_pid20381.log

2020-05-05 21:30:51,503 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 29, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  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/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java']' returned non-zero exit status 37.
2020-05-05 21:30:51 [ERROR] Synthesis failed
HEAD is now at 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth-self'
Note: checking out '7ee8db8c0ea7b9108a5f647fc3509c7c1e0a253b'.

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 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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:30:51 [INFO] Running synthtool
2020-05-05 21:30:51 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:30:51,824 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-103
nothing to commit, working tree clean
2020-05-05 21:30:51,957 synthtool > Ensuring dependencies.
2020-05-05 21:30:51,968 synthtool > Cloning googleapis.
2020-05-05 21:30:51,969 synthtool > Using precloned repo /tmpfs/tmp/tmpfnnoxo_l/googleapis
2020-05-05 21:30:51,974 synthtool > Generating code for: //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java.
2020-05-05 21:30:52,084 synthtool > Failed executing bazel build //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/d0be3d6e618947eff2f49cdbc7b2804b/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/tmpfnnoxo_l/googleapis/hs_err_pid20419.log

2020-05-05 21:30:52,085 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 29, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  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/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java']' returned non-zero exit status 37.
2020-05-05 21:30:52 [ERROR] Synthesis failed
HEAD is now at 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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-datalabeling. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpl4zwwz7d/googleapis'...
Cloning into '/tmpfs/tmp/tmpl4zwwz7d/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '7ee8db8c0ea7b9108a5f647fc3509c7c1e0a253b'.

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 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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 06:59:51 [INFO] Running synthtool
2020-05-07 06:59:51 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 06:59:51,635 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-07 06:59:51,768 synthtool > Ensuring dependencies.
2020-05-07 06:59:51,779 synthtool > Cloning googleapis.
2020-05-07 06:59:51,780 synthtool > Using precloned repo /tmpfs/tmp/tmpl4zwwz7d/googleapis
2020-05-07 06:59:51,785 synthtool > Generating code for: //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java.
2020-05-07 06:59:51,895 synthtool > Failed executing bazel build //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/df7e9d686ce2e99275d59ee46e8d265c/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/tmpl4zwwz7d/googleapis/hs_err_pid13486.log

2020-05-07 06:59:51,896 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 29, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  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/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java']' returned non-zero exit status 37.
2020-05-07 06:59:51 [ERROR] Synthesis failed
HEAD is now at 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth-self'
Note: checking out '7ee8db8c0ea7b9108a5f647fc3509c7c1e0a253b'.

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 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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 06:59:52 [INFO] Running synthtool
2020-05-07 06:59:52 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 06:59:52,231 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-111
nothing to commit, working tree clean
2020-05-07 06:59:52,364 synthtool > Ensuring dependencies.
2020-05-07 06:59:52,375 synthtool > Cloning googleapis.
2020-05-07 06:59:52,376 synthtool > Using precloned repo /tmpfs/tmp/tmpl4zwwz7d/googleapis
2020-05-07 06:59:52,381 synthtool > Generating code for: //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java.
2020-05-07 06:59:52,492 synthtool > Failed executing bazel build //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/df7e9d686ce2e99275d59ee46e8d265c/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/tmpl4zwwz7d/googleapis/hs_err_pid13521.log

2020-05-07 06:59:52,493 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 29, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  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/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java']' returned non-zero exit status 37.
2020-05-07 06:59:52 [ERROR] Synthesis failed
HEAD is now at 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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-datalabeling. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpky89_2os/googleapis'...
Cloning into '/tmpfs/tmp/tmpky89_2os/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '7ee8db8c0ea7b9108a5f647fc3509c7c1e0a253b'.

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 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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:25:53 [INFO] Running synthtool
2020-05-08 03:25:53 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:25:53,236 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:25:53,377 synthtool > Ensuring dependencies.
2020-05-08 03:25:53,387 synthtool > Cloning googleapis.
2020-05-08 03:25:53,388 synthtool > Using precloned repo /tmpfs/tmp/tmpky89_2os/googleapis
2020-05-08 03:25:53,392 synthtool > Generating code for: //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java.
2020-05-08 03:25:53,503 synthtool > Failed executing bazel build //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/3e7bc841d86915b10161d8d1a9f168c4/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/tmpky89_2os/googleapis/hs_err_pid22728.log

2020-05-08 03:25:53,504 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 29, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  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/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java']' returned non-zero exit status 37.
2020-05-08 03:25:53 [ERROR] Synthesis failed
HEAD is now at 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
Switched to branch 'autosynth-self'
Note: checking out '7ee8db8c0ea7b9108a5f647fc3509c7c1e0a253b'.

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 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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:25:53 [INFO] Running synthtool
2020-05-08 03:25:53 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:25:53,850 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-116
nothing to commit, working tree clean
2020-05-08 03:25:53,987 synthtool > Ensuring dependencies.
2020-05-08 03:25:53,997 synthtool > Cloning googleapis.
2020-05-08 03:25:53,998 synthtool > Using precloned repo /tmpfs/tmp/tmpky89_2os/googleapis
2020-05-08 03:25:54,002 synthtool > Generating code for: //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java.
2020-05-08 03:25:54,112 synthtool > Failed executing bazel build //google/cloud/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/3e7bc841d86915b10161d8d1a9f168c4/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/tmpky89_2os/googleapis/hs_err_pid22763.log

2020-05-08 03:25:54,113 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 29, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  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/datalabeling/v1beta1:google-cloud-datalabeling-v1beta1-java']' returned non-zero exit status 37.
2020-05-08 03:25:54 [ERROR] Synthesis failed
HEAD is now at 7ee8db8 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#164)
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.


[Shortcut Guide] Set lower boundaries for opacity and response time

Summary of the new feature/enhancement
Currently, lower boundaries for Shortcut Guide opacity and response time when Win key is pressed are both 0.
For opacity, this means that labels are mostly unreadable when background window is dark:

And for response time that as soon as Win key is pressed Shortcut Guide will appear, which is not the best user experience.

Proposed technical implementation details (optional)
Set minimal possible value for opacity to 15
Set minimal possible value for response time to 100ms

We never received any complain for this. Closing as won't fix.


Data too long for column 'agent' when firing PostViewed event

Hello.
When i trying to fire:
event(new PostViewed($post));
Sometimes (usually at mobile devices) I got error like this.
SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'agent' at row 1 (SQL: insert into canvas_views (post_id, ip, agent, referer, updated_at, created_at) values (bd50dcc6-c38d-4155-8da2-95d8f3644887, <IP_ADDRESS>, Mozilla/5.0 (iPhone; CPU iPhone OS 13_6 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 [FBAN/FBIOS;FBDV/iPhone11,2;FBMD/iPhone;FBSN/iOS;FBSV/13.6;FBSS/3;FBID/phone;FBLC/pl_PL;FBOP/5], http://m.facebook.com, 2020-08-25 12:33:46, 2020-08-25 12:33:46))
'Agent', 'referer' fields are to short.

Thanks for bringing this up @hoRacy.
If you're up for making a PR, you could just add some logic in the:

CaptureVisit
CaptureView

.. event listeners that only saves trimmed data, such as the host from the referrer. If not, I'll take a look at this later today.

Hi @austintoddj,
I can confirm this is an issue. I have my database charset set as utf8mb4, so I run with Schema::defaultStringLength(191); in my AppServiceProvider's boot method. This prevents filling string fields with more than 191 characters. I see now that this is only if you have an "older" MySQL version:

Laravel uses the utf8mb4 character set by default, which includes support for storing "emojis" in the database. If you are running a version of MySQL older than the 5.7.7 release or MariaDB older than the 10.2.2 release, you may need to manually configure the default string length generated by migrations in order for MySQL to create indexes for them.

From Laravel Migration docs, Index Lengths & MySQL / MariaDB
I personally solved this issue by making the agent columns in canvas_views and canvas_visits text instead of varchar. I'm on MySQL 8 now so I can probably remove the defaultStringLength setting, but my app was created before MySQL 5.7.7 was released.
@hoRacy Can you confirm if you also use the Schema::defaultStringLength in your app? What MySQL version are you using? (Or MariaDB if that is what you use...) Does removing the defaultStringLength fix the issue for you?

Facing the same issue when opening the post links from instagram,  probably due to the web view from mobiles, when you select open in chrome the issue is not seen.

@NavaneethVijay @hoRacy Getting a fix in now. Should be up in a few minutes.

Fixed in 5.4.1


made enable to compile chainerx with MSVC

write a hack for MSVC
upgrade gtest (1.80 has a bug on MSVC)

upgrade gtest (1.80 has a bug on MSVC)

Could you provide a pointer to the bug?

upgrade gtest (1.80 has a bug on MSVC)

Could you provide a pointer to the bug?

https://github.com/google/googletest/issues/1138

Jenkins, test this please

Jenkins CI test (for commit 6d20867f4d3b0789c65b4087de2ba94e1dbd0097, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 6d20867f4d3b0789c65b4087de2ba94e1dbd0097, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 6d20867f4d3b0789c65b4087de2ba94e1dbd0097, target branch master) succeeded!

Thanks!

Jenkins CI test (for commit 6d20867f4d3b0789c65b4087de2ba94e1dbd0097, target branch master) failed with status FAILURE.


Only Debian-like minions/clients require wget in our testsuite

What does this PR change?
We had issues on Liberty 9, as we couldn't find wget installed or available in the pristine image.
In fact, we don't need it, we only need that package in Debian-like systems for our testsuite minions/clients.
See also that:
https://github.com/uyuni-project/uyuni/blob/master/testsuite/features/step_definitions/navigation_steps.rb#L1107-L1112
  # debian based systems don't come with curl installed
  if (os_family.include? 'debian') || (os_family.include? 'ubuntu')
    node.run_until_ok("wget --no-check-certificate -qO- #{protocol}://#{system_name}:#{port}#{path} | grep -i '#{text}'")
  else
    node.run_until_ok("curl -s -k #{protocol}://#{system_name}:#{port}#{path} | grep -i '#{text}'")
  end

That's true, this state is only for testsuite minion / client and will not impact mirror, etc. I missed this part ! Thanks Oscar !


Support japan passport number

issue: #268

@snuyanzin or @bodiam Could you please take a look if you have a chance?

@yuokada Thanks for the PR, looks fine to me! It will be available in the 1.6.0-SNAPSHOT in a few minutes.

@bodiam Thanks for reviewing and merging my PR. 😄

@yuokada My pleasure, you contribution is welcome!


Bug with noSubmission transmission in API call (coords were transmitted even though it was a noSubmission

closed https://github.com/sopra-fs24-group-12/PeekSeek-server/commit/df62e6122c79f19fd345b49ac9fb9fa2fbacdb9d


Fix a few typos in docs/messages

Fix two typos in documentation and one in a sample's console message
found while learning Zephyr and exploring the source code.
Feel free to close if it's too much hassle to have this merged :)

Thanks for the fix. The changes look good, but you need to fix the commit message. See the compliance check details

@MaureenHelm, sure! CI messages were very clear on what to do and pointed me in the right direction (nicely done!), I just didn't have time earlier :grin: Added doc:  to the subject, as couldn't think of anything better. Please correct me, if I'm wrong.


Supporting Apple silicon M1

Request to be able to use this natively on the M1 as Apple has dedicated their hardware to to using this from here on out.

I believe whylogs is available on m1 natively now. What error are you getting?

Seems like it. :) The developer side on Java is not, but the python is working on use and contributor levels.


Problem with triple curly braces

I followed the migration guide that Virk posted on the blog for a new project I was working on and encountered the following issue:
Code:
  <script>
    window.addEventListener("load", function() {
      var datetimeField = document.getElementById("myDatetimeField");
      datetimeField.value = {{{ `"${timezone}"` }}};
    });
  </script>

Error:
[error] resources/file.edge: Error: {"message":"Unexpected token: punc «{», expected: punc «[»","filename":"file1.js","line":4,"col":29,"pos":150}
[error]     at wm (file:///home/filipebraida/Work/workspace/project/node_modules/prettier-edgejs/dist/main.js:8419:11)

I simplified the code a bit to make it easier to understand.
Thanks for the project!

Hey,
Thanks for the bug.
I'll have to look into this when I have some ample spare time. The issue is coming because between the script tag we are using minifyjs to format the javascript code. So the minifyjs library is throwing an error when trying to parse the edgejs related content.
Might be that I have to remove minifyjs in general to get this working, but will need further investigation.
Will let you know as soon as possible

@filipebraida could you please try the following for me - should fix your issue.

@filipebraida could you please try the following for me - should fix your issue.
<script>
  window.addEventListener("load", function() {
    var datetimeField = document.getElementById("myDatetimeField");
    datetimeField.value = `{{timezone}}`
  });
</script>

You could use the triple curly brackets if you want html safe too
<script>
  window.addEventListener("load", function() {
    var datetimeField = document.getElementById("myDatetimeField");
    datetimeField.value = `{{{timezone}}}`
  });
</script>

The formatter won't break in this manner; and the EdgeJS will still parse the template correctly and pass in the variable as you need.
I'll continue my investigations until as well.

@thetutlage do you have any advice on how we should be passing variables from the controller to the EdgeJS template to be used in a script tag as such?
From my understanding we'd have to do one of the following;

Set a data attribute on an element and use JS to grab the value inside the script tag

JSON.stringify the data and then inside the script tag do something such as

JSON.parse(`{{{test1}}}`)

Is this correct?

Thank you for the response! I simplified the code to make the issue clearer.
I thought of a few ways to work around it, but I had to leave and haven’t had the chance to make any changes yet.
The problem is indeed more complicated, especially since it's important to format the JS code within Edge.

I fixed the code by moving the logic outside because any Edge constructor doesn’t work within the script tag.
This is my actual example with the fixed code:
  @if(textAnnotation)
    <script>
      window.addEventListener("load", function() {
        var datetimeField = document.getElementById("myDatetimeField");
        datetimeField.value = "{{ textAnnotation.entry.getStandardizedDate(timezone) }}";
      });
    </script>
  @else
    <script>
      window.addEventListener("load", function() {
        var datetimeField = document.getElementById("myDatetimeField");
        datetimeField.value = localDatetime();
      });
    </script>
  @end

Original code:
datetimeField.value = {{{ textAnnotation ? `"${textAnnotation.entry.getStandardizedDate(timezone)}"` : 'localDatetime()' }}};

Awesome - il keep this open for a bit longer in case Virk replies with any info that could improve the way we handle things.
Otherwise id like to update Edge doco + ReadMe file here explaining how it should he handled because im sure someone else will run into an issue eventually too

@sajansharmanz I also noticed that there are some code variations that trigger the same exception, even without any Edge code. In those cases, it was indeed incorrect code, but the error still appears. For example:
    <script>
      window.addEventListener("load", function() {
        var datetimeField = document.getElementById("myDatetimeField");
        datetimeField.value =
      });
    </script>

My question is whether this error should really appear even with incorrect code. If so, one option might be to make minifyjs optional, allowing the developer to enable it in the settings.

@filipebraida I think the behavior of throwing error is same with other files to when using Prettier. Prettier will show an error if the source file is invalid.
@sajansharmanz I think there are two things here. First, do we want to allow using Edge expression within the inline script and style tags. Technically they are allowed and should be allowed, even though I will recommend not using them heavily.
So yes, it will be nice if the printer can also check for Edge code within the script and the style tags. Or the printer can be limited to only the HTML portion and simply ignore inline styles and scripts.

Sounds good - I will disable our style and script formatters inside for now and investigate a way forward from there
Thanks!

@filipebraida I have published<EMAIL_ADDRESS>which disables the formatters I was using for style and script tags. The this will indent the tags and there content to the level they should sit, but it won't format the content inside anymore.
I will investigate a way forward from here - which might mean writing my own print logic for CSS and JS. I will keep this issue open as part of it and further updates.

I have similar problem with prettier but in my case i don't get any errors from it. When im saving the file formatter simply removes one bracket from the end and seperate one from the beggining (im ataching photo). Problem only occurs when im trying to put 3 brackets inline of html object, outside of it its working normal.

@SUGEREK I checked it here, and Prettier is indeed removing a closing bracket at the end. In fact, it’s also adding a space between the first two brackets and the third one.

@SUGEREK I will need to adjust the parser and formatter to handle triple bracket. In the meantime you can use double bracket or even an @if() tag as a workaround.
I'll open another issue for this problem and move details there for it

Seems to be fixed https://github.com/sajansharmanz/prettier-plugin-edgejs/issues/8.

@filipebraida I have released<EMAIL_ADDRESS>which re-enables the use of the

@filipebraida I have released<EMAIL_ADDRESS>which re-enables the use of the


[C++] Remove std::optional from arrow::ArrayStatistics::is_{min,max}_exact

Describe the enhancement requested
They should be false (not exact) by default.
See also: https://github.com/apache/arrow/pull/43273#discussion_r1701348425
Component(s)
C++

Issue resolved by pull request 43595
https://github.com/apache/arrow/pull/43595


Working on PR for "Missing HEAD method when the code moved to chi"

Gitea version (or commit ref): 6064bfa3c3076254ad40f4d238d0c9c48d728e3d

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (provide example URL)
[ ] No

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/data/testgitea(master*) # curl --head https://try.gitea.io/anyuser/anyrepo/raw/branch/master/anyfile.png
HTTP/2 405
date: Sat, 30 Jan 2021 23:04:16 GMT
set-cookie: i_like_gitea=10985d2770de63e2; Path=/; HttpOnly
set-cookie: _csrf=kFz_ot6_LVT-Jsf6zgWksSWXVLU6MTYxMjA0Nzg1NjQ0NDU5MjM5MA; Path=/; Expires=Sun, 31 Jan 2021 23:04:16 GMT; HttpOnly
set-cookie: macaron_flash=; Path=/; Max-Age=0; HttpOnly
x-frame-options: SAMEORIGIN

Description
When I was trying to fix issue #8030 I had a look at the code base. Then two days later it moved from Macaron to Chi, the HEAD HTTP method no longer works automatically when GET is defined.
I already added and tested the code locally. Adding this line to WebRoutes function in 'routers/routes/web.go' fixes the issue.
r.Use(middleware.GetHead)

As for fixing issue #8030 :
This is a problem when trying to make a program download from Gitea. For example, Windows executables break when trying to download from Gitea /raw route as it does not give "Content-Length" in HEAD response.
The only function that needed to change is ServeData in 'routers/repo/download.go'. By changing the call to io.Copy to ioutil.ReadAll() + ctx.Resp.Write() . Then Writing the Content-Length explicitly by taking the length of the ioutil.ReadAll() byte array.
Questions :
1- Are the design decisions good ? should I make a PR ?
2- Should I make one or two PRs ?
3- I have no idea how to write tests these two functionalities ?
Related issues
https://github.com/go-gitea/gitea/issues/8030

Should we really need an automatical head response?
For those file routes, I think we can add HEAD methods specially.


Issue/1076

Fixed a issue   It's a little bug, this text "Create new collection is not a property #1074
Fixed a issue   It's a little bug, this text "Create new environment is not a property #1076

Hey @joelcamus,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: d0744b10-dee9-11ea-a7d8-3d177b5d5f1d


SPDX license expression parser using lalrpop library.

First off: apologies. It wasn't my intention to use an entirely new parser. It's only that I am new to Rust and this was the only path to success that I could implement. I was investigating spdx and Rust and discovered https://github.com/rust-lang/cargo/issues/2039 which led me to https://github.com/withoutboats/license-exprs/issues/3 and then this patch was created to both become more familiar with Rust and to solve the reported issue.
Maybe the most controversial change is renaming the crate from "license-exprs" to "license_exprs". When I was writing the tests I tried extern crate "license-exprs" as license_exprs but that generated a compiler error.

Rename create from "license-exprs" to "license_exprs"
I tried following the guidelines from
github.com/rust-lang/rfcs/blob/master/text/0940-hyphens-considered-harmful.md
I could not get the rename on import working so I bailed and
renamed the package.
LicenseExpr enum removed
ParseError::InvalidStructure construction changed from LicenseExpr to str
version number bumped to 2.0.0 due to previous changes
Fixes https://github.com/withoutboats/license-exprs/issues/3

Hey, thanks for this PR! I'll look into it more this week, but at the surface level it looks awesome; thanks for turning this into more of a real library.

Maybe the most controversial change is renaming the crate from "license-exprs" to "license_exprs". When I was writing the tests I tried extern crate "license-exprs" as license_exprs but that generated a compiler error.

I don't think this is necessary. That RFC was not written in a future proof way, so its very unclear if you weren't around before it was accepted. It used to work that you'd have to use extern crate "license-exprs" as license_exprs; now a crate called "license-exprs" will be imported as extern crate license_exprs without doing anything special. crates.io won't allow you to upload a crate "foo_bar" if "foo-bar" already exists, and vice versa. For the purpose of crate names, underscore and hyphen are the same character.
Also, to help me review the PR, what aspect of the changes that you made are breaking changes, and why are they needed? Specifically, I would consider these to be breaking changes:

Changing the type signatures in the existing API (adding new API surface isn't breaking).
Rejecting a license expression that was accepted before (I don't consider accepting previously rejected license expressions a breaking change, since that was a bug that no one ought to rely on).

Thanks! Yes the definition of the error enum is the only breaking change. I think. I've double-checked I hope I didn't miss another breaking change by accident.
The version of ParseError that is in master has the InvalidStructure variant that is constructed from a LicenseExpr. The LicenseExpr in the branch has been removed. I attempted two alternatives in the branch: in the first alternative I was constructing an AST that could be been exposed through a new public function. In that alternative the LicenseExpr would have been changed to store the AST. The second alternative is not to generate an AST. In this alternative the parser returns a void type and we are using the parser to report either success or failure. I found the second alternative a lot easier to implement the first alternative. In either of these cases LicenseExpr would have been changed leading to the change in ParseError.
In addition to changing the parameters for ParseError it was renamed to SpdxParseError only to reduce confusion with the ParseError enum in the LALRPOP library. I think the same goal could be achieved with "import foo as bar".

I'm so sorry that reviewing this slipped my mind!

Left some comments, most of them are very minor, a few are not. I'd like to know what you think we should do about the last, largest one. Thanks again for the PR, and apologies again for taking 2 weeks to look at it.

Doing some cleanup; it looks like this change is stale and not what's ultimately desired anyway, so I'm closing this PR. Thank you!


fix gl_stats (missing import)

There is a missing import that prevents compiling with gl_stats flag.
Should fix https://github.com/openfl/openfl/issues/2485

Thanks


Fix julia 0.4 type deprecations

Now with the addition of the Union deprecation, the logs are quite bad: https://travis-ci.org/timholy/Images.jl/jobs/80997593
Fixing that in a 0.3-compatible way would require an additional 55 @compats. I think it's time to branch for 0.4 and leave julia-0.3 in the dust.
Awaiting comments.

I'm all in =)

Sounds good to me.
I have a question, should we be excluding the next major release in our REQUIRES file?  Something like julia 0.4 0.5?  That does allow julia 0.5-, I think. It's tough to predict the future, but I imagine that our current code won't work with future versions of Julia, and it might be best to spell that out with each commit.
I ask because I've never seen that feature used in other packages.  It seems quite useful.

:+1:

Sounds like a quorum to me.
@rsrock, it's an interesting idea. I haven't really thought about it. Since the package manager will always default to the most recent version, and I'm presuming we'll eventually have a version that will run on 0.5, it seems like the old ones should never be chosen. Can you further clarify the advantage?

Fixing that in a 0.3-compatible way would require an additional 55 @compats. I think it's time to branch for 0.4 and leave julia-0.3 in the dust.

I've been going in the add 55 @compat route and it's not that bad, but I think branching isn't too bad either.


Can't update project when copying from local template

Describe the problem
I created a project from a local template. I created the project using copier copy path/to/template . in ~/Desktop. When I cd into my new project (~/Desktop/project) and run copier update . I get a ValueError("Local template must be a directory.") error.
I'm able to update the project if I change _src_path key in the .copier-answers.yml file to the absolute path to the template.
Is this expected or am I not using my local template as intended?
Found this https://github.com/copier-org/copier/issues/335 which seems related.
Template
local template
To Reproduce
No response
Logs
raise ValueError("Local template must be a directory.")
Expected behavior
The project should update from the template without error.
Screenshots/screencasts/logs
No response
Operating system
macOS
Operating system distribution and version
Venture 13.5
Copier version
9.2.0
Python version
CPython 3.10
Installation method
pipx+pypi
Additional context
No response

Duplicate of #335.


s390x: Support tail calls

This adds support for a newly defined tail-call ABI for s390x as well as supporting tail calls themselves.
We now use the tail-call ABI by default for Wasmtime, and enable tail calls by default.
This also allows getting rid of a number of special case and test exclusions for s390x.
Fixes: https://github.com/bytecodealliance/wasmtime/issues/6530

Thanks for the review, @fitzgen !   The latest version should address all review comments.


Gesture Test Failing

[ROSUNIT] Outputting test results to /root/.ros/test_results/harmoni_gesture/rostest-test_gesture.xml
[INFO] [1621439158.279799]: Initializing the gesture service
[INFO] [1621439158.284864]: Setting up the gesture
[INFO] [1621439158.787637]: Initializing the gesture_qt service
[INFO] [1621439159.718419]: Initializing the gesture service
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Could not initialize OpenGL for RasterGLSurface, reverting to RasterSurface.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Traceback (most recent call last):
  File "/root/harmoni_catkin_ws/src/HARMONI/harmoni_actuators/harmoni_gesture/src/harmoni_gesture/gesture_service.py", line 239, in <module>
    main()
  File "/root/harmoni_catkin_ws/src/HARMONI/harmoni_actuators/harmoni_gesture/src/harmoni_gesture/gesture_service.py", line 230, in main
    s = GestureService(service_name, params)
  File "/root/harmoni_catkin_ws/src/HARMONI/harmoni_actuators/harmoni_gesture/src/harmoni_gesture/gesture_service.py", line 48, in __init__
    self.setup_gesture()
  File "/root/harmoni_catkin_ws/src/HARMONI/harmoni_actuators/harmoni_gesture/src/harmoni_gesture/gesture_service.py", line 79, in setup_gesture
    rospy.sleep(0.1)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/timer.py", line 134, in sleep
    rospy.rostime.wallsleep(duration)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/rostime.py", line 277, in wallsleep
    time.sleep(duration)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/core.py", line 504, in _ros_signal
    prev_handler(sig, stackframe)
TypeError: 'Handlers' object is not callable
[Testcase: testtest_gesture] ... ok

[ROSTEST]-----------------------------------------------------------------------

[harmoni_gesture.rosunit-test_gesture/test_request_response][ERROR]-------------
init_node interrupted before it could complete
  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 601, in run
    self.setUp()
  File "/root/harmoni_catkin_ws/src/HARMONI/harmoni_actuators/harmoni_gesture/test/rostest_gesture.py", line 28, in setUp
    rospy.init_node("test_gesture", log_level=rospy.INFO)
  File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/client.py", line 323, in init_node
    raise rospy.exceptions.ROSInitException("init_node interrupted before it could complete")
--------------------------------------------------------------------------------

SUMMARY
 * RESULT: FAIL
 * TESTS: 1
 * ERRORS: 1
 * FAILURES: 0

rostest log file is in /root/.ros/log/rostest-harmoni_full-3306.log

This test works in the latest builds.


How to disable line numbers on specific code block?

Hi,
Is there a way to disable line numbers on specific code block? Generally, I want to have line numbers on my code blocks but there are occasions where I would like to disable line numbers on specific code block.
I'm using markdown with fenced code blocks.
# config.rb
set :markdown, :fenced_code_blocks => true, :smartypants => true

This is a markdown code block with ruby with line numbers, just for an example:
```ruby
# hello.rb
def hello
  puts "hello"
end
```

The end result is a code block with line numbers:
1  # hello.rb
2  def hello
3    puts "hello"
4  end

This is a markdown code block where I would like to disable line numbers:
This is just an imaginary example, there is no nolinenumbers syntax.
```nolinenumbers
middleman init MY_PROJECT
bundle exec middleman serve
```

The end result would be a code block without line numbers:
middleman init MY_PROJECT
bundle exec middleman serve

Is there an option or parameter that would handle this?

Not in markdown, no. If you use the code helper in another template language, you can pass parameters.

Here is an experiment that I tried:
https://github.com/tuomasj/middleman-syntax/blob/no_linenumbers_experiment/lib/middleman-syntax/highlighter.rb#L8
This is not the way this "problem" should be fixed for production, but since I'm the only one using, this will do for me :smile:
So, now I have a syntax called "plain":
```plain
puts "Look ma, no line numbers!"
```

Actually...
Try this:
```ruby?line_numbers=false
puts "Look ma, no line numbers!"
```

Hey - I tried ?line_numbers=false but line numbers were still present. Anything else you advise?
relevant config.rb:
set :markdown_engine, :redcarpet
set :markdown, :fenced_code_blocks => true, :smartypants => true
activate :syntax, :line_numbers => true

versions:
middleman: (3.3.12)
middleman-blog: (3.5.3)
middleman-syntax: (2.1.0)
redcarpet (3.3.4)

Yeah, looks like we'd need to make some changes for that to work.

puts "Look ma, no line numbers parameter is working now!"

Here is the commit for working version with Redcarpet: https://github.com/tuomasj/middleman-syntax/commit/3d19e5b544648eddf86ae27324fa7fc1a2edba4a
When using redcarpet this language parameter approach works, but Kramdown handles the language parameter differently. Any suggestions what would be the best approach?

Neat! Wanna send a PR? I'm not sure Kramdown will make this available.

Yeah, I'll send it as soon as I remove all Kramdown releated stuff

Created a pull request #63, closing this issue. If there are any addition discussions, the pull request is better place for it.


PRIORITY: Climate Actions Possible in Specific Regions

As a [description of user]?
member of the general public in BC,
I want to [functionality]
access information about climate actions that are possible where I live (certain actions face barriers in some areas such as heat pumps and EVs),
So that [benefit]
I can take actions where I live that I can feel confident will make a difference.
Additional context
Corresponding summary: take climate actions that are possible and feasible in my area of BC
Acceptance Criteria
Agreed-upon confirmation of the requirements when done can be deemed as complete

duplicated by #88, closing


Read-only Kafka

Document how to set up Kafka to allow read-only access for anonymous users.

Config files in branch "issue226" of narcissus.
General description:

Have 2 listeners - SASL_PLAINTEXT for internal/inter-broker operations; PLAINTEXT for external read-only access.

Create a super user "admin" - see kafka_server_jaas.conf
Set an ACL to allow read access for anon users to topics starting with "lsst_":
ResourcePattern(resourceType=TOPIC, name=lsst_, patternType=PREFIXED):
(principal=User:, host=, operation=READ, permissionType=ALLOW)

30/JUN/21
-RoyW and TerryS agreed this can be closed


implement experimental ffi-rs library

Stack:

#145
#143
#142
#141 ⬅
#140

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #145


Static pages

The goal is to abstract the logic to generate static pages (/about, /tos, /privacypolicy, etc.)
I've also added a new page for /about

@HipsterBrown I wanted to update the global-styles to match the new generic style for static pages defined by @cuiki here: https://github.com/opencollective/opencollective/issues/1194#issuecomment-409084052
But that messes up the homepage. I think that the proper way to do this would be to have specific styles for the homepage since it's such a special page. And we should put the generic styles for static pages in the global-styles file. In the meantime, I've simply added them as <style global jsx> here: https://github.com/opencollective/frontend/blob/af3065ebc38d1349799279b51e04111c62163e9f/src/pages/staticPage.js#L46-L86


Rewrite tests to use new KIP-470 API

Updated this. (Added some side cleanup to use hamcrest for testing in all test)

Rebasing this to new branch 5.4.x and also resolve merge conflicts.