You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
STORAGE: In _reload_properties, should we raise if _changes is not empty? #729
👎 Logging a warning might be appropriate, but if the user has triggered an API call (the only public way to reach _reload_properties), the server-side version of the metadata is always authoritative.
I'm uncertain why we would assign a priority to this, or slot it into a project, given that it is an open question (not a bug, not a requested enhancement).
Hello,
One of the challenges of maintaining a large open source project is that sometimes, you can bite off more than you can chew. As the lead maintainer of google-cloud-python, I can definitely say that I have let the issues here pile up.
As part of trying to get things under control (as well as to empower us to provide better customer service in the future), I am declaring a "bankruptcy" of sorts on many of the old issues, especially those likely to have been addressed or made obsolete by more recent updates.
My goal is to close stale issues whose relevance or solution is no longer immediately evident, and which appear to be of lower importance. I believe in good faith that this is one of those issues, but I am scanning quickly and may occasionally be wrong. If this is an issue of high importance, please comment here and we will reconsider. If this is an issue whose solution is trivial, please consider providing a pull request.
Activity
tseaver commentedon Nov 10, 2015
👎 Logging a warning might be appropriate, but if the user has triggered an API call (the only public way to reach
_reload_properties), the server-side version of the metadata is always authoritative.tseaver commentedon Jun 5, 2017
I'm uncertain why we would assign a priority to this, or slot it into a project, given that it is an open question (not a bug, not a requested enhancement).
lukesneeringer commentedon Aug 11, 2017
Hello,
One of the challenges of maintaining a large open source project is that sometimes, you can bite off more than you can chew. As the lead maintainer of
google-cloud-python, I can definitely say that I have let the issues here pile up.As part of trying to get things under control (as well as to empower us to provide better customer service in the future), I am declaring a "bankruptcy" of sorts on many of the old issues, especially those likely to have been addressed or made obsolete by more recent updates.
My goal is to close stale issues whose relevance or solution is no longer immediately evident, and which appear to be of lower importance. I believe in good faith that this is one of those issues, but I am scanning quickly and may occasionally be wrong. If this is an issue of high importance, please comment here and we will reconsider. If this is an issue whose solution is trivial, please consider providing a pull request.
Thank you!
Add snippets and tests for language tutorial. [(#729)](GoogleCloudPla…
feat: Update Compute Engine API to revision 20220831 (#729) (#345)
chore: fix prerelease_deps nox session [autoapprove] (#729)
chore(main): release 2.22.0 (#729)
fix: correct regression in `Model.get_or_insert` (#731)
fix: support custom alg in jwt header for signing (#729)
docs: update limitations about json query support and django version …
chore(deps): update dependency google-cloud-pubsub to v2.11.0 (#729)
chore: change repo maintainer (#729)