I couldn't install this package with Laravel 7.3.0 !!!

$ composer require gloudemans/shoppingcart
Using version ^2.6 for gloudemans/shoppingcart
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1

Installation request for gloudemans/shoppingcart ^2.6 -> satisfiable by gloudemans/shoppingcart[2.6.0].
Conclusion: remove laravel/framework v7.3.0
Conclusion: don't install laravel/framework v7.3.0
gloudemans/shoppingcart 2.6.0 requires illuminate/events 5.1.* || 5.2.* || 5.3.* || 5.4.* || 5.5.|| 5.6. || 5.7.* -> satisfiable by illuminate/events[5.1.x-dev, 5.2.x-dev, 5.3.x-dev, 5.4.x-dev, 5.5.x-dev, 5.6.x-dev, 5.7.17, 5.7.18, 5.7.19, 5.7.x-dev, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8, v5.2.0, v5.2.19, v5.2.21, v5.2.24, v5.2.25, v5.2.26, v5.2.27, v5.2.28, v5.2.31, v5.2.32, v5.2.37, v5.2.43, v5.2.45, v5.2.6, v5.2.7, v5.3.0, v5.3.16, v5.3.23, v5.3.4, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9].
don't install illuminate/events 5.1.x-dev|don't install laravel/framework v7.3.0
don't install illuminate/events 5.2.x-dev|don't install laravel/framework v7.3.0
don't install illuminate/events 5.3.x-dev|don't install laravel/framework v7.3.0
don't install illuminate/events 5.4.x-dev|don't install laravel/framework v7.3.0
don't install illuminate/events 5.5.x-dev|don't install laravel/framework v7.3.0
don't install illuminate/events 5.6.x-dev|don't install laravel/framework v7.3.0
don't install illuminate/events 5.7.17|don't install laravel/framework v7.3.0
don't install illuminate/events 5.7.18|don't install laravel/framework v7.3.0
don't install illuminate/events 5.7.19|don't install laravel/framework v7.3.0
don't install illuminate/events 5.7.x-dev|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.1|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.13|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.16|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.2|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.20|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.22|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.25|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.28|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.30|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.31|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.41|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.6|don't install laravel/framework v7.3.0
don't install illuminate/events v5.1.8|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.0|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.19|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.21|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.24|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.25|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.26|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.27|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.28|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.31|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.32|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.37|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.43|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.45|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.6|don't install laravel/framework v7.3.0
don't install illuminate/events v5.2.7|don't install laravel/framework v7.3.0
don't install illuminate/events v5.3.0|don't install laravel/framework v7.3.0
don't install illuminate/events v5.3.16|don't install laravel/framework v7.3.0
don't install illuminate/events v5.3.23|don't install laravel/framework v7.3.0
don't install illuminate/events v5.3.4|don't install laravel/framework v7.3.0
don't install illuminate/events v5.4.0|don't install laravel/framework v7.3.0
don't install illuminate/events v5.4.13|don't install laravel/framework v7.3.0
don't install illuminate/events v5.4.17|don't install laravel/framework v7.3.0
don't install illuminate/events v5.4.19|don't install laravel/framework v7.3.0
don't install illuminate/events v5.4.27|don't install laravel/framework v7.3.0
don't install illuminate/events v5.4.36|don't install laravel/framework v7.3.0
don't install illuminate/events v5.4.9|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.0|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.16|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.17|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.2|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.28|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.33|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.34|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.35|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.36|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.37|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.39|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.40|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.41|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.43|don't install laravel/framework v7.3.0
don't install illuminate/events v5.5.44|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.0|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.1|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.10|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.11|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.12|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.13|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.14|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.15|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.16|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.17|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.19|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.2|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.20|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.21|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.22|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.23|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.24|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.25|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.26|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.27|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.28|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.29|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.3|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.30|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.31|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.32|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.33|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.34|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.35|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.36|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.37|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.38|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.39|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.4|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.5|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.6|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.7|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.8|don't install laravel/framework v7.3.0
don't install illuminate/events v5.6.9|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.0|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.1|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.10|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.11|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.15|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.2|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.20|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.21|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.22|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.23|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.26|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.27|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.28|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.3|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.4|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.5|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.6|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.7|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.8|don't install laravel/framework v7.3.0
don't install illuminate/events v5.7.9|don't install laravel/framework v7.3.0
Installation request for laravel/framework (locked at v7.3.0, required as ^7.3.0) -> satisfiable by laravel/framework[v7.3.0].

Installation failed, reverting ./composer.json to its original content.

https://github.com/Crinsane/LaravelShoppingcart/issues/593#issuecomment-551254784

https://github.com/Crinsane/LaravelShoppingcart/wiki/Maintained-Forks


DES-5564-support for newer java versions

Looks good to me, let's see how it works with apps using Java 17/21.


How to restore checkpoints if not all arrays are sharded?

Hi,
I am trying to restore a checkpoint where some of its array are not partitioned. I believe this is a common use case, as one may not want (or can't) to partition all parameters in a model. The following is a minimal example:
import numpy as np
import jax
import flax

mesh_shape = (2, 2)
devices = np.asarray(jax.devices()).reshape(*mesh_shape)
mesh = jax.sharding.Mesh(devices, ('x', 'y'))

sharded = jax.device_put(np.arange(4).reshape(2, 2), jax.sharding.NamedSharding(mesh, jax.sharding.PartitionSpec('x', 'y')))
unsharded = jax.device_put(np.arange(1), jax.sharding.NamedSharding(mesh, PartitionSpec()))
ckpt = dict(sharded=sharded, unsharded=unsharded)

jax.distributed.initialize("localhost:8889", num_processes=1, process_id=0)

async_ckptr = orbax.checkpoint.AsyncCheckpointer(orbax.checkpoint.PyTreeCheckpointHandler(), timeout_secs=50)
async_ckpt_mgr = orbax.checkpoint.CheckpointManager('/tmp/example', async_ckptr)
async_ckpt_mgr.wait_until_finished()
async_ckpt_mgr.save(0, ckpt)
async_ckpt_mgr.wait_until_finished()

restore_args = flax.training.orbax_utils.restore_args_from_target(ckpt)
restored_ckpt = async_ckpt_mgr.restore(0, items=ckpt, restore_kwargs={'restore_args': restore_args})

I get the following error message:
"ValueError: Sharding of jax.Array cannot be None. Provide mesh and mesh_axes OR sharding."
I then found out that I can transform unsharded into a numpy.array, restore it, then assign again an empty partition. As follows:
ref_ckpt = dict(sharded=sharded, unsharded=np.array(unsharded))
restore_args = flax.training.orbax_utils.restore_args_from_target(ref_ckpt)
restored_ckpt = async_ckpt_mgr.restore(0, items=ref_ckpt, restore_kwargs={'restore_args': restore_args})
restored_ckpt["unsharded"] = jax.device_put(restored_ckpt["unsharded"], NamedSharding(mesh, PartitionSpec()))

This seems to work as desired. Would you say this is the right way to do it? Is there an easier way?
Thanks!

I think this may be consequence of using the Flax restore_args_from_target function which makes certain assumptions about how on-device, fully replicated arrays should be restored. Try using construct_restore_args instead.

Thanks, it appears to work.
Here is a follow-up question: in the documentation, the target object passed to both construct_restore_args and CheckpointManager.restore have the same shapes as the train_state that we are trying to restore. This seems not ideal, considering that it may take up quite some memory.
In the Flax documentation here, it seems to be possible to pass a smaller target reference. However, I've trying creating one with the same axis dimension as my shardings, but I get an error like
ValueError: Cannot intersect index domain { [0, 40*) } with index domain {  }: Ranks do not match [source locations='tensorstore/index_space/index_transform.cc:484']
What is the exact logic? How can I create a reference smaller than the actual train state?

For starters, the item argument for CheckpointManager.restore is optional, and is quite unnecessary in your case since it's just a dict, and not a custom PyTree.
Secondly, it is possible to skip the initialization of target if you are constrained by memory. Simply use restore_args=dict(sharded=orbax.checkpoint.ArrayRestoreArgs(sharding=...), unsharded=orbax.checkpoint.ArrayRestoreArgs(sharding=...))
I'm not actually sure what the Flax documentation is talking about when they say the reference may be smaller than the actual train state.... the construct_restore_args function is really only intended for use when you already have the entire PyTree initialized with arrays of the correct shape and sharding. If you have jax.ShapeDtypeStruct, for example, you would just use similar logic to initialize the restore_args.

Fantastic, seems to have worked like a charm. Thanks a lot!

Reopening the issue since I have got a follow-up problem. In my code, the restoring function comes within a jitted function. Unfortunately, I get the following concretization error:
jax.errors.ConcretizationTypeError: Abstract tracer value encountered where concrete value is expected: Traced<ShapedArray(uint32[])>with<DynamicJaxprTrace(level=2/0)>

This value became a tracer due to JAX operations on these lines:
  operation a:u32[1] = host_local_array_to_global_array[
  global_mesh=Mesh(device_ids=array([[0]]), axis_names=('processes', 'local_devices'))
  pspec=PartitionSpec('processes',)
] b

Any idea how I can work around this issue?

As of now, I got around this issue by a pure callback, but if possible I'd rather avoid it.

This is an easy answer: you can't restore from within a jitted function. This is an issue we encountered before with a few other Flax users, and we reached the conclusion that they would just need to move their restore outside the jitted function. Sorry!

Alright, then perhaps there is a way to obtain a tree of shapes corresponding to the checkpoint, without actually restoring the checkpoint? I tried using jax.eval_shape in combination with a CheckpointManager.restore, but it turns out that jax.eval_shape jits the function, therefore this approach did not work.

There is, but it's currently not well integrated into the API. Orbax does support getting the pytree structure of the checkpoint via the structure API or using lazy restore. However, if you want the shapes of the arrays, we currently don't have an API for that, though we're working on it. What you can do is parse through the .zarray files, which store the shape (and other metadata) for each parameter.

Thanks. Related to structure, I've noticed that when there is only one checkpoint in the directory, structure creates a pytree with the same structure as the checkpoint, with numpy arrays as values. However, when multiple checkpoints are available, it returns a pytree with lists of placeholder strings as values. I find this difference a little odd. For example, it would seem I could get shapes in the first case, but not in the second?
Anyway, in order to get shapes, currently I'm restoring the whole checkpoint as lazy (using ArrayRestoreArgs(lazy=True)), then I get the shape of their values in a tree_map as follows:
shapes = tree_map(lambda v: v.get().shape, restored_checkpoint)

Would you say this method allocates the full checkpoint in memory?

If you only have a checkpoint file in the directory, that means all your values were saved with aggregate=True, so they are all stored in one file. Otherwise, they will be stored separately using Tensorstore, in which case they will be represented with PLACEHOLDER in the structure file. You're right that this difference is a bit annoying, and it's not easy to get metadata for all arrays, to look at things like the shape and stuff without doing a full restoration.
This does materialize the entire checkpoint. If you want to look up the shapes without doing so, you have to parse through the .zarray files, or use Tensorstore to do so. Again, we're working on a more user-friendly way of doing this. In the future, LazyArray will also have properties like shape and dtype even before materialization.

Looks like this has landed in main a while back: https://github.com/google/orbax/pull/639


add @chippieTV to VOTING_MEMBERS.md

thanks for the invitation

!! yes, sorry I went off radar, been a bit busy and we had a baby (well my wife did). It was nice to get a message, I'll try to make myself useful when things calm down again :)


Synthesis failed for kms

Hello! Autosynth couldn't regenerate kms. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the kms API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
ch 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 6244244 chore: ignore release-please.yml if it already exists (#1059)
2021-04-27 03:06:59,445 autosynth [DEBUG] > Running: git checkout e7d77d65f0e05ce584c1a824c7ecab53b411498b
Note: checking out 'e7d77d65f0e05ce584c1a824c7ecab53b411498b'.

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 e7d77d65 fix: specify valid go_package option
2021-04-27 03:06:59,461 autosynth [DEBUG] > Running: git branch -f autosynth-kms-322
2021-04-27 03:06:59,465 autosynth [DEBUG] > Running: git checkout autosynth-kms-322
Switched to branch 'autosynth-kms-322'
2021-04-27 03:06:59,494 autosynth [INFO] > Running synthtool
2021-04-27 03:06:59,495 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-04-27 03:06:59,495 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Kms/322/sponge_log.log
2021-04-27 03:06:59,497 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-04-27 03:06:59,728 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-php/Kms/synth.py.
On branch autosynth-kms-322
nothing to commit, working tree clean
2021-04-27 03:06:59,898 synthtool [DEBUG] > Ensuring dependencies.
DEBUG:synthtool:Ensuring dependencies.
2021-04-27 03:06:59,910 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
2021-04-27 03:06:59,914 synthtool [DEBUG] > Cloning googleapis.
DEBUG:synthtool:Cloning googleapis.
2021-04-27 03:06:59,915 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2021-04-27 03:06:59,918 synthtool [DEBUG] > Which version of bazel will I run?
DEBUG:synthtool:Which version of bazel will I run?
bazel 3.0.0
2021-04-27 03:06:59,922 synthtool [DEBUG] > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-php.
DEBUG:synthtool:Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-php.
2021-04-27 03:07:00,167 synthtool [ERROR] > Failed executing bazel --max_idle_secs=240 build //google/cloud/kms/v1:google-cloud-kms-v1-php:

Loading:
Loading: 0 packages loaded
DEBUG: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/rules_python/python/pip.bzl:61:5: DEPRECATED: the pip_repositories rule has been replaced with pip_install, please see rules_python 0.1 release notes
Analyzing: target //google/cloud/kms/v1:google-cloud-kms-v1-php (1 packages loaded, 0 targets configured)
ERROR: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/upb/bazel/upb_proto_library.bzl:257:29: aspect() got unexpected keyword argument 'incompatible_use_toolchain_transition'
ERROR: /home/kbuilder/.cache/synthtool/googleapis/google/cloud/kms/v1/BUILD.bazel:206:1: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors and referenced by '//google/cloud/kms/v1:kms_php_grpc'
ERROR: Analysis of target '//google/cloud/kms/v1:google-cloud-kms-v1-php' failed; build aborted: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors
INFO: Elapsed time: 0.230s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (3 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (3 packages loaded, 0 targets configured)

ERROR:synthtool:Failed executing bazel --max_idle_secs=240 build //google/cloud/kms/v1:google-cloud-kms-v1-php:

Loading:
Loading: 0 packages loaded
DEBUG: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/rules_python/python/pip.bzl:61:5: DEPRECATED: the pip_repositories rule has been replaced with pip_install, please see rules_python 0.1 release notes
Analyzing: target //google/cloud/kms/v1:google-cloud-kms-v1-php (1 packages loaded, 0 targets configured)
ERROR: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/upb/bazel/upb_proto_library.bzl:257:29: aspect() got unexpected keyword argument 'incompatible_use_toolchain_transition'
ERROR: /home/kbuilder/.cache/synthtool/googleapis/google/cloud/kms/v1/BUILD.bazel:206:1: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors and referenced by '//google/cloud/kms/v1:kms_php_grpc'
ERROR: Analysis of target '//google/cloud/kms/v1:google-cloud-kms-v1-php' failed; build aborted: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors
INFO: Elapsed time: 0.230s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (3 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (3 packages loaded, 0 targets configured)

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/google-cloud-php/Kms/synth.py", line 31, in <module>
    bazel_target='//google/cloud/kms/v1:google-cloud-kms-v1-php',
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 66, in php_library
    return self._generate_code(service, version, "php", clean_build, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 204, 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', '--max_idle_secs=240', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-php']' returned non-zero exit status 1.
2021-04-27 03:07:00,219 autosynth [ERROR] > Synthesis failed
2021-04-27 03:07:00,219 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 7b571cd4 feat: Allow RequestWrapperTrait to use its auth cache when fetching ADC (#3959)
2021-04-27 03:07:00,266 autosynth [DEBUG] > Running: git checkout autosynth-kms
Switched to branch 'autosynth-kms'
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 356, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 336, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 68, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, 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 kms. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the kms API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
gain. Example:

  git checkout -b <new-branch-name>

HEAD is now at e6f3d54 build(node): switch $default-branch with template variable (#1060)
2021-04-28 03:07:10,068 autosynth [DEBUG] > Running: git checkout ef119e7aa2eee147ecf854e5154c93351ed7de25
Note: checking out 'ef119e7aa2eee147ecf854e5154c93351ed7de25'.

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 ef119e7a feat: Expose supported languages of the agent; feat: add export / import flow API docs: Update docs on Pages, Session, Version, etc.
2021-04-28 03:07:10,085 autosynth [DEBUG] > Running: git branch -f autosynth-kms-334
2021-04-28 03:07:10,090 autosynth [DEBUG] > Running: git checkout autosynth-kms-334
Switched to branch 'autosynth-kms-334'
2021-04-28 03:07:10,123 autosynth [INFO] > Running synthtool
2021-04-28 03:07:10,123 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-04-28 03:07:10,123 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Kms/334/sponge_log.log
2021-04-28 03:07:10,125 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-04-28 03:07:10,374 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-php/Kms/synth.py.
On branch autosynth-kms-334
nothing to commit, working tree clean
2021-04-28 03:07:10,554 synthtool [DEBUG] > Ensuring dependencies.
DEBUG:synthtool:Ensuring dependencies.
2021-04-28 03:07:10,567 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
2021-04-28 03:07:10,573 synthtool [DEBUG] > Cloning googleapis.
DEBUG:synthtool:Cloning googleapis.
2021-04-28 03:07:10,573 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2021-04-28 03:07:10,578 synthtool [DEBUG] > Which version of bazel will I run?
DEBUG:synthtool:Which version of bazel will I run?
bazel 3.0.0
2021-04-28 03:07:10,583 synthtool [DEBUG] > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-php.
DEBUG:synthtool:Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-php.
2021-04-28 03:07:10,865 synthtool [ERROR] > Failed executing bazel --max_idle_secs=240 build //google/cloud/kms/v1:google-cloud-kms-v1-php:

Loading:
Loading: 0 packages loaded
DEBUG: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/rules_python/python/pip.bzl:61:5: DEPRECATED: the pip_repositories rule has been replaced with pip_install, please see rules_python 0.1 release notes
Analyzing: target //google/cloud/kms/v1:google-cloud-kms-v1-php (1 packages loaded, 0 targets configured)
ERROR: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/upb/bazel/upb_proto_library.bzl:257:29: aspect() got unexpected keyword argument 'incompatible_use_toolchain_transition'
ERROR: /home/kbuilder/.cache/synthtool/googleapis/google/cloud/kms/v1/BUILD.bazel:206:1: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors and referenced by '//google/cloud/kms/v1:kms_php_grpc'
ERROR: Analysis of target '//google/cloud/kms/v1:google-cloud-kms-v1-php' failed; build aborted: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors
INFO: Elapsed time: 0.267s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)

ERROR:synthtool:Failed executing bazel --max_idle_secs=240 build //google/cloud/kms/v1:google-cloud-kms-v1-php:

Loading:
Loading: 0 packages loaded
DEBUG: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/rules_python/python/pip.bzl:61:5: DEPRECATED: the pip_repositories rule has been replaced with pip_install, please see rules_python 0.1 release notes
Analyzing: target //google/cloud/kms/v1:google-cloud-kms-v1-php (1 packages loaded, 0 targets configured)
ERROR: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/upb/bazel/upb_proto_library.bzl:257:29: aspect() got unexpected keyword argument 'incompatible_use_toolchain_transition'
ERROR: /home/kbuilder/.cache/synthtool/googleapis/google/cloud/kms/v1/BUILD.bazel:206:1: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors and referenced by '//google/cloud/kms/v1:kms_php_grpc'
ERROR: Analysis of target '//google/cloud/kms/v1:google-cloud-kms-v1-php' failed; build aborted: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors
INFO: Elapsed time: 0.267s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)

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/google-cloud-php/Kms/synth.py", line 31, in <module>
    bazel_target='//google/cloud/kms/v1:google-cloud-kms-v1-php',
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 66, in php_library
    return self._generate_code(service, version, "php", clean_build, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 204, 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', '--max_idle_secs=240', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-php']' returned non-zero exit status 1.
2021-04-28 03:07:10,922 autosynth [ERROR] > Synthesis failed
2021-04-28 03:07:10,922 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 7b571cd4 feat: Allow RequestWrapperTrait to use its auth cache when fetching ADC (#3959)
2021-04-28 03:07:10,969 autosynth [DEBUG] > Running: git checkout autosynth-kms
Switched to branch 'autosynth-kms'
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 356, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 336, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 68, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, 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 kms. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the kms API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
ain 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 06a8cd0 chore(deps): update dependency google-api-core to v1.26.3 (#996)
2021-04-29 03:07:08,982 autosynth [DEBUG] > Running: git checkout 5deb21826a6645d278010dc384a8d5dd942dfebd
Note: checking out '5deb21826a6645d278010dc384a8d5dd942dfebd'.

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 5deb2182 feat: publish protos for Google Ads API v7
2021-04-29 03:07:08,999 autosynth [DEBUG] > Running: git branch -f autosynth-kms-352
2021-04-29 03:07:09,002 autosynth [DEBUG] > Running: git checkout autosynth-kms-352
Switched to branch 'autosynth-kms-352'
2021-04-29 03:07:09,031 autosynth [INFO] > Running synthtool
2021-04-29 03:07:09,032 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-04-29 03:07:09,032 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/Kms/352/sponge_log.log
2021-04-29 03:07:09,034 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-04-29 03:07:09,259 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-php/Kms/synth.py.
On branch autosynth-kms-352
nothing to commit, working tree clean
2021-04-29 03:07:09,423 synthtool [DEBUG] > Ensuring dependencies.
DEBUG:synthtool:Ensuring dependencies.
2021-04-29 03:07:09,433 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
2021-04-29 03:07:09,437 synthtool [DEBUG] > Cloning googleapis.
DEBUG:synthtool:Cloning googleapis.
2021-04-29 03:07:09,437 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2021-04-29 03:07:09,441 synthtool [DEBUG] > Which version of bazel will I run?
DEBUG:synthtool:Which version of bazel will I run?
bazel 3.0.0
2021-04-29 03:07:09,444 synthtool [DEBUG] > Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-php.
DEBUG:synthtool:Generating code for: //google/cloud/kms/v1:google-cloud-kms-v1-php.
2021-04-29 03:07:09,699 synthtool [ERROR] > Failed executing bazel --max_idle_secs=240 build //google/cloud/kms/v1:google-cloud-kms-v1-php:

Loading:
Loading: 0 packages loaded
DEBUG: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/rules_python/python/pip.bzl:61:5: DEPRECATED: the pip_repositories rule has been replaced with pip_install, please see rules_python 0.1 release notes
Analyzing: target //google/cloud/kms/v1:google-cloud-kms-v1-php (1 packages loaded, 0 targets configured)
ERROR: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/upb/bazel/upb_proto_library.bzl:257:29: aspect() got unexpected keyword argument 'incompatible_use_toolchain_transition'
ERROR: /home/kbuilder/.cache/synthtool/googleapis/google/cloud/kms/v1/BUILD.bazel:206:1: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors and referenced by '//google/cloud/kms/v1:kms_php_grpc'
ERROR: Analysis of target '//google/cloud/kms/v1:google-cloud-kms-v1-php' failed; build aborted: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors
INFO: Elapsed time: 0.242s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)

ERROR:synthtool:Failed executing bazel --max_idle_secs=240 build //google/cloud/kms/v1:google-cloud-kms-v1-php:

Loading:
Loading: 0 packages loaded
DEBUG: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/rules_python/python/pip.bzl:61:5: DEPRECATED: the pip_repositories rule has been replaced with pip_install, please see rules_python 0.1 release notes
Analyzing: target //google/cloud/kms/v1:google-cloud-kms-v1-php (1 packages loaded, 0 targets configured)
ERROR: /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/upb/bazel/upb_proto_library.bzl:257:29: aspect() got unexpected keyword argument 'incompatible_use_toolchain_transition'
ERROR: /home/kbuilder/.cache/synthtool/googleapis/google/cloud/kms/v1/BUILD.bazel:206:1: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors and referenced by '//google/cloud/kms/v1:kms_php_grpc'
ERROR: Analysis of target '//google/cloud/kms/v1:google-cloud-kms-v1-php' failed; build aborted: error loading package '@com_github_grpc_grpc//src/compiler': in /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl: Extension file 'bazel/upb_proto_library.bzl' has errors
INFO: Elapsed time: 0.242s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (2 packages loaded, 0 targets configured)

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/google-cloud-php/Kms/synth.py", line 31, in <module>
    bazel_target='//google/cloud/kms/v1:google-cloud-kms-v1-php',
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 66, in php_library
    return self._generate_code(service, version, "php", clean_build, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 204, 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', '--max_idle_secs=240', 'build', '//google/cloud/kms/v1:google-cloud-kms-v1-php']' returned non-zero exit status 1.
2021-04-29 03:07:09,744 autosynth [ERROR] > Synthesis failed
2021-04-29 03:07:09,745 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 7b571cd4 feat: Allow RequestWrapperTrait to use its auth cache when fetching ADC (#3959)
2021-04-29 03:07:09,787 autosynth [DEBUG] > Running: git checkout autosynth-kms
Switched to branch 'autosynth-kms'
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 356, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 336, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 68, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, 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:


Load LFRic based data

Linking AVD's slam tool development as needed for loading LFRic based data. Slam does not yet allow lazy data and is potentially memory hungry which could be an issue for loading our data.
https://github.com/bjlittle/geovista-slam/issues/77

Duplicate of #382


[Bug]: TypeError: 'type' object is not subscriptable

What happened?
when following instructions getting error
Exception has occurred: TypeError
'type' object is not subscriptable
File "/home/vicente/vss/gen/vehicle-model-generator/sdv/model_generator/cpp/cpp_generator.py", line 83, in VehicleModelCppGenerator
def __get_namespace_for_node(self, node: VSSNode) -> list[str]:
File "/home/vicente/vss/gen/vehicle-model-generator/sdv/model_generator/cpp/cpp_generator.py", line 29, in
class VehicleModelCppGenerator:
File "/home/vicente/vss/gen/vehicle-model-generator/sdv/model_generator/main.py", line 25, in
from sdv.model_generator.cpp.cpp_generator import VehicleModelCppGenerator
File "/home/vicente/vss/gen/vehicle-model-generator/gen_vehicle_model.py", line 17, in
from sdv.model_generator.main import main
TypeError: 'type' object is not subscriptable
Operating System
Linux
What release version or branch did you use?
latest
Relevant log output
see above

Code of Conduct

[X] I agree to follow this project's rules for contributions

@rony-ferzli  Can you please provide the exact input you have provided to the model generated to cause this issue? Thanks!

@rony-ferzli Bug potentially fixed with release v0.3.0. Please check. Thx!

great thank you!

Hi,
Yes please do, I did have the chance to verify but will check
Thank you!
Regards
Rony
From: BjoernAtBosch @.>
Sent: Monday, March 27, 2023 7:32 AM
To: eclipse-velocitas/vehicle-model-generator @.>
Cc: Ferzli, Rony @.>; Mention @.>
Subject: Re: [eclipse-velocitas/vehicle-model-generator] [Bug]: TypeError: 'type' object is not subscriptable (Issue #33)
We are closing this issue as

we were not able to reproduce it,
the referenced code part has been reworked inbetween, and
we did not receive further input/feedback for four weeks.

Please re-open if you have new insights. Thx!
—
Reply to this email directly, view it on GitHubhttps://github.com/eclipse-velocitas/vehicle-model-generator/issues/33#issuecomment-1485222722, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASRGJUDQEBTDCK7WHUZTZADW6GQEJANCNFSM6AAAAAAUWD2R44.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>