Closed fjetter closed 2 years ago
Sorry Florian. We were treating package sync as pretty "beta" for awhile.
@shughes-uk At this point I think we need to be more careful about requiring upgrades, right?
No problem for me. Just wanted to raise awareness since others may run into it as well
FYI This happened again
File ~/mambaforge/envs/dask-distributed-310-main/lib/python3.10/site-packages/coiled/_beta/core.py:535, in CloudBeta._create_senv_package(self, package_file, md5, account)
528 response = await self._do_request(
529 "POST",
530 self.server
531 + f"/api/v2/software-environment/account/{account}/package-upload",
532 json={"name": Path(package_file.name).name, "md5": md5},
533 )
534 data = await response.json()
--> 535 if data["should_upload"]:
536 try:
537 await self._put_package(
538 url=data["upload_url"], package_data=package_data
539 )
I was running 0.2.42
From a UX perspective this is really bad. At the very least there should be a warning letting me know that there is a newer version available
Also, any particular reason you switched to a public issue? (https://github.com/coiled/feedback/issues/221)
There's some circumstances where engagement in the public feedback repo seems valuable, [sorry if this sounds grouchy] but an old bug that you hit again b/c you were still using an old version doesn't strike me as one.
Ohh, I'm sorry. I guess this is a new instance of the issue?
You upgraded from 0.2.38
to 0.2.42
to make things work a couple weeks ago, and then hit it again in 0.2.42
because of recent changes.
Also, any particular reason you switched to a public issue? (https://github.com/coiled/feedback/issues/221)
This is also public. Didn't switch but I can open these things in the private tracker from now on
You upgraded from 0.2.38 to 0.2.42 to make things work a couple weeks ago, and then hit it again in 0.2.42 because of recent changes.
I know this is not identical. I wanted to reduce spam for you. Will open a dedicated issue next time. Feel the pain!
This is also public.
Ah indeed it is! :-) Sorry, confused about what repo I'm in. That's okay, not saying anything that shouldn't be public.
Will open a dedicated issue next time. Feel the pain!
Either way is fine. Mostly I'm just sorry, and glad we're hearing from you.
I suspect the error in https://github.com/coiled/feedback/issues/216#issuecomment-1333623555 isn't about backwards compatibility. I'd want to make sure client-side code is checking for non-200 response (maybe it is already, not sure).
It appears we rolled out something on server side that made the client incompatible.
I was running version
0.2.38
and got the error below when creating a clusterUpgrading to latest resolved the issue.
Are we sticking to semantic versioning?