Dave Hirschfeld

Let me know if you want any more info - I'm happy to help debug the problem, just not too sure where to start...

Poking around the db, things look ok? ``` quetz.sqlite> select * from packages ***************************[ 1. row ]*************************** name | seau-tns-dashboards-demo channel_name | seau-dev description | n/a summary | n/a channeldata...

``` quetz.sqlite> select * from users +------------------------------------+-------------------+--------+ | id | username | role | +------------------------------------+-------------------+--------+ | 0x32aca2c961fc4f149d12ae18590140a2 | dhirschfeld | owner | | 0x09f15cb108b1495c94dd417348dc9f2a | | | +------------------------------------+-------------------+--------+ 2 rows...

As a data point, uploading via the swagger UI works and I can browse the package info:  ...so, it seems to be an issue with `quetz-client`. There doesn't appear...

Thanks for the example @gnestor - it very useful for a JS noob like me!

Indeed, that's straightforward for an analyst/developer but a button with a popup save-file dialog is quite convenient and probably more noob-friendly. I can imagine that if the table display is...

3. :+1:

Just cross-referencing in case there's anything to be learnt from previous discussions: https://docs.scipy.org/doc/numpy-dev/neps/missing-data.html (though it's also linked to from @ResidentMario's blog)

IMO, in practice there's no difference between EffVer and SemVer - it's just different marketing for users who might otherwise take SemVer too literally. * https://jacobtomlinson.dev/effver/

As a consumer of packages, I really struggle with CalVer - should I update from `2024-02-07` to `2024-03-02`? I've got zero basis to make an informed decision from the output...