[bot-automerge] google-cloud-cpp v2.23.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
google-cloud-cpp-ai	2.23.0
google-cloud-cpp-bigquery	2.23.0
google-cloud-cpp-compute	2.23.0
google-cloud-cpp-core	2.23.0
google-cloud-cpp	2.23.0

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: disabled to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

• pandas
• numpy
• plotnine

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/8700216351 - please use this URL for debugging.}

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: failed

Thus the PR was not passing and not merged.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

It appears that not all commits to this PR were made by the bot. Thus this PR is not being automatically merged. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[coryan]

Seems like the osx jobs are stuck in:

WARNING: Partially parsed some '.tbd' files in sysroot /Applications/Xcode_13.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk, pretending .tbds are their install-names
Adding support to 'conda-build' for parsing these in 'liefldd.py' would be easy and useful:
['System/Library/PrivateFrameworks/ProVideo.framework/ProVideo.tbd', 'usr/lib/libcupsimage.tbd'] ...

It has been at least 10 minutes for https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=917885&view=logs&j=ced5d8de-8227-5f3f-33a1-45cf1592c45a&t=f7bcb349-6dca-53ba-d88d-1d9963e119ba

[coryan]

@h-vetinari sorry to bother you, but the builds seem to be stuck on some Conda specific post-processing. Do you have any ideas of what might be going on?

[h-vetinari]

Do you have any ideas of what might be going on?

The processing there is the link-check that inspects the shared libraries and figures out which symbols from what libraries are being actually used (and comparing that with the libraries as present in the environment specified by the run-requirements). This is done principally through lief, and can take a while (depending on size and quantity of libs, I've seen up to ~30min).

So the jobs are almost certainly not stuck; however we recently had a new lief release and I had the impression that there were some regressions on osx in terms of processing speed. The changes in 278a150 bring us back to the CI from before lief 0.14 was merged. That might not solve our problems though, because it could just as well be that 2.23 grew in terms of targets/objects that we now run out of the 6h.

In any case, CC @mbargull for the lief side.

[coryan]

Thanks! If your changes work I will test without my changes in 22b1a5e. Naturally, I will shard more if that is what it takes.

FWIW, we are exploring ideas to reduce the overall build time (maybe 5-10%, nothing too dramatic). And I refreshed my list of "what to shard next", so we have a decent list of candidates if just "organic" growth of the libraries caused the timeouts.