Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions recipe/meta.yaml
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{% set name = "zstash" %}
{% set version = "1.5.0rc1" %}
{% set version = "1.5.0rc3" %}
{% set python_min = "3.11" %}

package:
Expand All @@ -8,7 +8,7 @@ package:

source:
url: https://github.com/E3SM-Project/zstash/archive/v{{ version }}.tar.gz
sha256: 0deda016d8ba4fb5f4051d3a01516a3d38cc28dc7beb09ac54515955313d96e7
sha256: 5f039b176f6c5a63b42b6ce330bcb7291ce3753713218bfa40edaf9a2320ef1d

build:
number: 0
Expand All @@ -25,7 +25,7 @@ requirements:
- python >={{ python_min }}
- sqlite
- six >=1.16.0
- globus-sdk >=3.15.0
- globus-sdk >=3.15.0,<4.0
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without this, we get AttributeError: 'TransferClient' object has no attribute 'endpoint_autoactivate'. It should be possible to fix the erroring code itself, but I'm not sure how long that will take to debug. I think at this point in the testing period, we should just pin the versions like this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@forsyth2, excellent instincts on this one. I agree with you on both counts. This should be fixed "properly" in zstash but not right now in the middle of Unified testing, so the upper bound is the right fix for now.

Furthermore, it tells us that we probably want to have an upper bound constraint on globus-sdk in general, so once we support 4.x, we would still have a <5.0 constraint because we know to expect breaking changes.


test:
imports:
Expand Down