I found a few things surprising about this bug too, but this might be due to my own ignorance about how these processes work:
- I was expecting the package to either be revoked, or to have a new `6.1.64-2` version being published with the previously good known state.
Maybe it wasn't done because it was not possible (mirrors being write-only, and maybe other complications in publishing a 6.1.64-2).
- I was expecting some guidelines to be published for affected machines. I've seen questions being asked [1], but no answers to them yet (so users are not sure if it would be safe to rollback to the previous kernel version (6.1.55-1) or not).
Maybe it's because the problem is not well understood yet, or maybe there are not enough people available to answer such questions on a weekend?
If someone can provide some context about "how these things work", it would be interesting to learn more about this.
The `6.1.66-1` release with a fix was uploaded to Debian's infrastructure about 2 hours after the bug was filed, but it takes a bit for it to be compiled for all Debian's architectures (the mipsel builder e.g. needed 9 hours) and for it to propgate through the mirror network.
I also manually upgraded yesterday (bad luck, just a few hours after the update) and just now reverted to the previous kernel. Not sure this was the right thing to do but didn't want to take any chances
My desktop and laptop are both root on ZFS so I dodged this bug. (Actually I saw the press on this before upgrading anyway so I'm holding off until I see a fix released.)
I saw the message yesterday late in the evening, I still had 8 hours before my automated updates ran and I thought the package would be revoked by then. Mistake :/
Very nice! Happy to see this evolution coming from Obsidian, it seems like a more natural way to organize concepts and ideas.
One question: It seems it could be troublesome to have to move / resize everything when adding a new card once a canvas is already quite busy. Is there something like auto-layout in the work, to handle these situations? (like to automatically re-layout cards and groups once adding a new item in between)
There are several layout options you can use to easily align and rearrange cards on the canvas. We have considered a "clean up" shortcut to reorganize the whole canvas at once but haven't gotten there yet.
Done the same for over 10 years with a local "@Worklog.md" file on a light text editor (to get syntax highlighting). Can be synced with Dropbox or Obsidian too.
Recently switched to do the same on Notion, moving items in a "Worklogs" database at the end of each month (with one entry per month) to keep the Worklog size manageable. If a task gets too long I can just create a sub-page for it (or a toggle), put all the context information there, and just add a link to the TODO item.
> Don't be "pro-active" be "re-active" - is my way of putting it.
As much as I recognize this can be good advice, this comment makes me sad.
It's like "start underperforming" is the answer given to bad management problems.
Which I agree actually makes sense in a lot of companies (if pro-active efforts are not already being recognized, then it's hard to change the culture).
I also think that a lot of comments here are directed toward financial success, but many people are actually looking for meaningful ways to contribute. People for which the "re-active" approach might not be a solution.
What would be the solution for those people? How unlikely is it to actually switch to a company which recognizes employees willing to be more involved?
i think it depends on your goals. If you're ambitious and driven and willing to take on extra responsibilities - perhaps with little immediate reward then go for it. For some, it's more about finding a balance to avoid getting too jaded or burnt out.
Some of the best devs I've worked with are those who just like to work. They are also up for any problem and rarely complain even if (imo) they have too much on their plate. It really just comes down to your personality and needs at that stage of your life.
For myself, I sort of came to the conclusion that I won't encounter meaningful financial success in my day job. I would have to work another 20-30 years to accomplish (financially) what I used to expect I would have done already in my late 20s. So, it's more about trying to maintain some kind enjoyment in my work and also to protect my mental/physical health.
I loved StumbleUpon, and I find myself missing a discovery tool like that one. Reddit and other websites give me the impression of running in loop. If anyone has good discovery tools to recommend!
I second this! Algorithmic discovery tools solve for sameness whereas StumbleUpon solved for variety. It was a wonderful tool for breaking out of thought bubbles.
As a college student outside of the US who had never heard of YCombinator, StumbleUpon was how I discovered HN. Now I work at startups and can't imagine going back to a bigger company. Strange to think that in a world where StumbleUpon didn't exist, I may still be working at BigCorp.
- I was expecting the package to either be revoked, or to have a new `6.1.64-2` version being published with the previously good known state.
Maybe it wasn't done because it was not possible (mirrors being write-only, and maybe other complications in publishing a 6.1.64-2).
- I was expecting some guidelines to be published for affected machines. I've seen questions being asked [1], but no answers to them yet (so users are not sure if it would be safe to rollback to the previous kernel version (6.1.55-1) or not).
Maybe it's because the problem is not well understood yet, or maybe there are not enough people available to answer such questions on a weekend?
If someone can provide some context about "how these things work", it would be interesting to learn more about this.
[^1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843#33