Skip to content

Latest version doesn't work with freezegun #15073

Closed as not planned
Closed as not planned

Description

@jacobg

The latest versions 2.11.0 and 1.34.0 don't support using freezegun in unit tests, e.g., in conjunction with google-cloud-datastore. It seems the following merge broke it:
fix: Major refactoring of Polling, Retry and Timeout logic
googleapis/python-api-core#462

Version 2.10.2, which is the last version before that merge, works fine.

Do you need more info?

Activity

  1. jacobg commented on Mar 8, 2023

    @jacobg
    Author
  2. atulep commented on Apr 13, 2023

    @atulep
    Contributor

    Hey @jacobg ,

    From your stack trace, the code failed because of deadline exceeded. Can you try setting deadline to a larger value like 60*60 (hour), for example? In client lib function call, pass deadline arg.

  3. added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Apr 13, 2023
  4. vchudnov-g commented on Apr 24, 2023

    @vchudnov-g
    Contributor

    Were you able to get this to work, @jacobg ?

  5. jacobg commented on Apr 25, 2023

    @jacobg
    Author

    @atulep - A one hour deadline is necessary for unit testing with the datastore emulator? Why doesn't this issue occur without freezegun?

    @vchudnov-g - No, I pinned the version of python-api-core before the breaking commit referenced above. Obviously, it's not a permanent solution, but I was waiting and hoping maybe it would be fixed before in the near future.

  6. vchudnov-g commented on May 16, 2023

    @vchudnov-g
    Contributor

    @jacobg To clarify, are you saying unpinning the version and passing the deadline argument did not work?

  7. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on May 16, 2023
  8. parthea commented on Jan 12, 2026

    @parthea
    Contributor

    Transferring to google-cloud-python as the code for python-api-core will be migrated there in 1-3 weeks.

  9. daniel-sanche commented on May 28, 2026

    @daniel-sanche
    Contributor

    This issue is being bulk closed due to inactivity. Please re-open if you think this still requires attention, and we'll take another look. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions