Hacker News new | ask | show | jobs
by click170 3301 days ago
This whole thing seems to stem from the authors inability to reproduce and understand the problem.

Has anyone submitted a test case demonstrating the problem? I don't see one linked in the comments. It may also help to explain how you deploy and why you do it that way, not everyone does this as their day job so some perspective can be enlightening.

Closing an issue like this that is ostensibly a problem for a lot of people and projects isn't good etiquette. At the same time, Foss authors dont owe us or anyone else anything. The least we can do is help them reproduce the issue when they have trouble doing it themselves. Seems like failures on both sides here to me.

Edit: I also don't want to criticize the author for not pushing a patch they don't understand. I wouldnt merge a patch if I didn't understand the problem it was solving, but I would ask for details and a test case to understand it better instead of closing the ticket.
2 comments
justinsaccount 3300 days ago
What are you talking about? It was explained multiple times that the released tarball had broken timestamps.

> I also don't want to criticize the author for not pushing a patch they don't understand.

This issue had absolutely nothing to do with patches. The maintainer published a broken tarball. The users were asking the maintainer to re-publish a non-broken tarball.

link
edmccard 3300 days ago
>The users were asking the maintainer to re-publish a non-broken tarball.

Yes, with such helpful suggestions as changing to a fresh directory because the original directory was "corrupt". Except that wouldn't have fixed it; the problem was eventually discovered to be a bug in npm on Windows[1], so every single "republished" package would have also been broken.

[1]https://github.com/npm/npm/issues/16734

link
justinsaccount 3299 days ago
And the maintainers have not re-published a fixed tarball yet and the issue remains closed. Even after the underlying issue has been fixed in npm.

I think it's pretty clear which side here is acting inappropriately.

link
brepl 3301 days ago
> This whole thing seems to stem from the authors inability to reproduce and understand the problem.

It's up to issue reporters to clearly demonstrate an issue, not for authors to try to recreate every rumoured bug.

link