7 ms·
Webpack Doesn't Work on Monday (On Windows)
- the_duke 7y agoEasy fix: just don't work on Mondays. ( you don't really want to anyway...) A: "Hey boss, I'm not coming in today." B: "Why not??" A: "Well, webpack does not work on Mondays. Do you expect me to write plain Javascript code without Babel???" B: "Makes sense. See you tomorrow."
- ZeroCool2u 7y agoThis solution seems to be optimal.
- sascha_sl 7y agoBut unironically.
- _AzMoo 7y ago"Sure. See you Saturday then."
- the_duke 7y agoSorry, due to French union demands, Typescript (tsc) does not work on weekends anymore (in the EU).
- avip 7y agoNow that's a proper OOTB thinking. Monday is a wasted day anyhow full of "status meetings" and "week planning". Hopefully it'll get more traction than the low-quality "upgrade to 3.3.5".
- jasonhansel 7y agoTry my new JS library! Key feature: it doesn't compile when the weather is nice outside.
- jasonhansel 7y agoCall it `time-pad`
- raverbashing 7y agoModern js seems to have a good amount of tail-wagging-the-dog cases
- stackola 7y agoReminds me of this old classic: Openoffice can’t print on Tuesdays https://news.ycombinator.com/item?id=8171956 https://news.ycombinator.com/item?id=8171956
- usrusr 7y agoReminds me of the build script I found in a single-dev project I inherited: failed due to truncated/missing leading zero when the wall clock was earlier than 10 am. My predecessor was notoriously late at the office, it would have worked for him every single time.
- lloeki 7y agoOk, let me up the game. I had one simple short-lived cron command that failed on even minutes before h:20 where 5AM < h < 8AM on Sat, Sun, Mon. Cause was another job that hammered IO because reasons, so mine was being killed by some unreported IO timeout after 1min, and retried the next minute (so every other minute). The other one was scheduled to run on off business time (weekends and Monday before people get to work) and had some burstiness that made the IO go down enough every other minute which allowed my short-execution one to proceed. top was silent because IO, took us a long time to even thing about iotop because the failure was non obviously tied to IO.
- jononor 7y ago... due to a bug in the code that is supposed to show banner asking for donations.
- kabwj 7y agoLike when you can’t use a game because the drm server is down.
- edwintorok 7y agoYeah looks like it didn't have the intended effect, some people consider moving away from webpack due to this: " Someone should really rethink if this is the most effective way to get donations (while I rethink if webpack should be kept in our toolchain)." Which is understandable, everytime something breaks is an opportunity to rethink whether you really need that dependency, and if so whether there would be a better alternative implementation .
- nailer 7y agoRollup has a lot of momentum behind it.
- preommr 7y agoparcel is also a great alternative. Its a little bit rough (lack of documentation and some plugins don't have things like debug info) but its great for how small it is. Very easy to get started and easy to migrate to something else like webpack or rollup as a backup plan if the project requires it.
- tekkk 7y agoI think that's an exaggerated reaction. Bugs happen all the time, is this one any different because it involved such unusual circumstance? It wasn't a security bug, and how many users did actually freshly install Webpack on Windows-based computer on monday? Not a large subset. So it's more amusing than harmful. Whenever things like these happen, of course you should think if the effort ripping off Webpack is better than suffering possible losses of productivity in the long run. But for majority existing projects I'd bet the projected cost of lost hours vs the cost of changing your bundler would result in net-loss. And as an observation, I feel programmers often have a habit of lamenting loudly about other people's mistakes while not saying a word if they make an error of their own. Maybe they have a psychological need of maintaining a feeling of superiority about your own abilities, I don't know. Just something I've noticed during my years.
- deleted 7y ago[deleted]
- griko 7y agoOther day related bugs: OpenOffice can’t print on Tuesdays https://news.ycombinator.com/item?id=8171956 https://news.ycombinator.com/item?id=8171956
- Waterluvian 7y agoFor a lark someone should curate a collection of these kinds of errors, even if fixed, and make a calendar of what days we can't do certain things.
- red_admiral 7y agoThere's the classic 'Wednesday bug': http://web.media.mit.edu/~lieber/Lieberary/Softviz/CACM-Debugging/Hairiest.html http://web.media.mit.edu/~lieber/Lieberary/Softviz/CACM-Debu... [Story 'B'] (I'm sure I've read a longer version of this one somewhere else on the internet.)
- jrockway 7y agoThe lesson here is that codepaths gated by conditionals like "if day == MONDAY" get 1/7th the testing of codepaths that aren't. If you want to have features like this, which is fine, check those code coverage reports and make sure that your tests can pretend it's Monday.
- perfunctory 7y agoAnd the incentive to do that is?
- holtalanm 7y agoless bugs?
- hluska 7y agoBasically, it’s a good chance to: 1.) Question whether that codepath should be gated to a particular day of the week. 2.) Assess the cost of that codepath failing (or failing to load). Does it have the potential to brick the project? 3.) How big could the bug be? If software tells me it’s “just another manic Monday” on Tuesday, or that I should “Walk like an Egyptian” on February 31, who cares? There is no incentive to unit test because honestly, who cares? On the other hand, if it has the potential to brick the project, go back to #1. Do you really need to test the day of the week? Are you bloody sure?? :) 4.) If you reach #4, it’s time to invest in unit tests. You wrote a condition where a day of the week test could result in software failure.
- jrockway 7y agoI assume the motivation for typing in code is for it to run to completion successfully every time. In this case, because of the bug, Webpack didn't print a message reminding you to donate money to them. You would think you'd want to keep that working, because those donations are what make continued improvement of the software possible. So you write a test for it, and then you can hack on the other parts of the code knowing, with confidence, that your donation reminder works. Even on Windows. Even on Monday.
- evenstensberg 7y agoI'm sorry, link to a fix found here: https://twitter.com/evenstensberg/status/1145755812129845249 https://twitter.com/evenstensberg/status/1145755812129845249 Happy to help you to fix the issue through email or DMs... Even (One causing this issue..)
- cevn 7y agoEveryone breaks something in prod at some point, don't beat yourself up.
- preommr 7y agoFor additional hilarity: This bug was introduced because it displays a banner asking for donations. People complained that the dontation message was being shown too often. So they made it ask on mondays only.
- jschuur 7y agoWhy Monday? Was there A/B testing done to find the best day to ask?
- franciscop 7y agoA problem with OSS funding, not surprised. If only 1% of all the productivity lost with this bug was donated to Webpack, they would probably not need to ask for money at all. But the market doesn't work that way, so it's just a sad reminder of our own problems.
- pure-awesome 7y agoReminds me of this: "We had a unit test once which only failed on Sundays" https://qntm.org/unit https://qntm.org/unit
- neotek 7y agoUgh, thanks, now I have to read the Fine Structure series all over again.
- leksak 7y agoLink?
- michaelmior 7y ago> Link? https://qntm.org/structure https://qntm.org/structure
- pure-awesome 7y agoRough. Good luck! ;-) I just re-read Ra, which is amazing. Found it much easier to follow than the (equally amazing) Fine Structure. https://qntm.org/ra https://qntm.org/ra
- regularfry 7y agoI've seen tests which fail between 2 and 3pm, but only for 6 months of the year.
- DocTomoe 7y agoSounds like a DST issue, tbh.
- regularfry 7y agoCombination of comparing a localtime Time.now to a UTC value, daylight savings, and devs in more than one timezone.
- baybal2 7y agoI really want to find an alternative to Webpack for our projects. Webpack + babel is an extremely fragile piece of tooling that eats work hours of senior devs like a candy. Few years ago it might've been like 50/50 split in between fighting tooling and development in shorter term projects The problem in replacing webpack+babel combo is that what we call "the JavaScript ecosystem" over the years turned into a "webpack ecosystem" with even most trivial packages not working with some kind of all-involving "build process"
- lpellis 7y agoI've been trying out parcel ( https://parceljs.org/ https://parceljs.org/ ), so far it has been awesome, the normal flow just works without setup for most projects.
- have_faith 7y agoReminds me of the classic "I cant send email more than 500 miles" story: http://web.mit.edu/jemorris/humor/500-miles http://web.mit.edu/jemorris/humor/500-miles
- ratsimihah 7y agoA bit off-topic but imagine if there was an internet-free day, like Sunday...
- Japhy_Ryder 7y agoApparently it "crushes". It doesn't "crash". It "crushes".