Internal server error 500

Rhino Developer Yak
1

Hi,

I published a plugin (SmartPieMenu) on Rhino package manager with yak.

I successfully published v2.0.1, v2.02 and v2.0.3, but since this morning every time I try to publish new version (v2.0.4 and v2.0.5) I get a simple message saying “500: Internal Server Error”

The problem is that if I re-try to publish a version that had the “500 error” with yak, the result of the yak command is saying “409: A distribution of ‘rh8_23-mac’ for a package by the name of ‘SmartPieMenu’ with version number ‘2.0.5’ already exists.”

So v2.0.4 and v2.0.5 seems “known” by Rhino but not visible in package manager due to the error 500.

I stopped to increment version number and trying to publish since it seems that publishing with yak command is always failing.

Any help would be appreciated :slight_smile:

3

I can now reproduce the issue with packages that were previously published successfully, e.g. 2.0.2.

So this does not look specific to the current package contents anymore.

Current behavior:

  • production server: HTTP 500 on push, then HTTP 409 if retrying same version
  • test server: also returns HTTP 500, even for older .yak files that were already published successfully before

Additional weird behavior:

yak search smartpiemenu
returns:
SmartPieMenu (2.0.5)

but

yak search -a --prerelease smartpiemenu
returns only:
SmartPieMenu (2.0.3, 2.0.2)

This looks inconsistent, because --all --prerelease should be more complete, not less.
So 2.0.5 seems to exist in some server index state, but not in the normal full version listing and not in Rhino Package Manager either.

This now looks like an issue with Yak upload infrastructure rather than with this specific package.

Can someone at McNeel can help me with this ?

Environment

- Rhino 8.29.26063.11002

- yak version: Yak 0.15.0 (0.15.9559.19955)

- OS: macOS 26.4 (not yet tested on Windows)

4

Having the same issues HTTP 500: Internal Server Error and then HTTP 409 saying the version number already exists, it is how ever not showing up when you do a yak search

5

I feel not alone :slight_smile: Did you have this problem since today ? Before today, I had no problem with yak push.

6

have the same issue

7

actually both on mac/windows

8

Same.

Mcneel vibecoded something and it broke. Came here to report myself.

Same with my macbook and iphone, they work so shitty, AI vibecoded some of the new os features and ofc they broke unrelated features like keyboards shortcuts, swipes and more.. on a fucking apple product…

Welcome to the future

9

I’m having the same issue today with a new version of a previously published plugin.

10

Thanks all for reporting the problems. Should have this fixed shortly!

11

Fixed.

There was an issue (unfortunately a human one) with cache invalidation. Packages were being published correctly, but an error occurred when clearing the caching layer.

I’ve manually cleared the cache so all package versions that were published in the last ~12 hours should now be visible.

2 Likes
12

Great ! Thank you :+1: