benoitg

It depends. The inspiration sometimes comes after a Saturday evening with friends and lots of drinks. Having a foolproof recipe comes in handy, and having the perfect stress-free pancake batter already made the next morning turns you into a household hero.

Not necessarily, I often make changes on unrelated commits. You can always use jj split to extract the change and put it somewhere else.

One of the uses cases on their website is the agent deleted my .env file.

jj wouldn’t help with that as it would be gitignored.

Recent versions of MySQL and MariaDB default to repeatable-read for InnoDB tables, not read-commited :

https://dev.mysql.com/doc/refman/8.4/en/set-transaction.html...

https://mariadb.com/docs/server/reference/sql-statements/adm...

I don't know about MyISAM though (who uses it anyway ;-) ).

I’m the same as the parent, auto-track = none() works perfectly for me

I’d love to know more, do you have any links to your articles?

Châtelet is there, you have to click on the 3D icon to experience the full majesty of its unending corridors in 3D

I fixed this by changing the default immutable heads to include all remote bookmarks. This way, you cannot edit them and the new commit is automatically created when you push to the remote branch.

  [revset-aliases]
  "immutable_heads()" = "trunk() | tags() | remote_bookmarks()"

I had the same copy paste problem, now I use jjui (https://github.com/idursun/jjui). The daily operations become even smoother, it looks like I’m flying over the log.

The Jetbrains suite of IDEs have this handy feature : if you copy a curl command into an HTTP scratch file, it is automatically converted to the HTTP equivalent, which is IMHO much more readable.

Your project looks very cool though, and expands on the share aspect of the Jetbrains feature, very interesting!

Yes, the instructions are in the OP.

I don't know how VACUUM works, I couldn't tell you about the differences.

The OPTIMIZE works almost exclusively with online DDL statements. There's only a brief table lock held during table metadata operations, but I haven't found that to be a problem in practice. (https://dev.mysql.com/doc/refman/8.4/en/optimize-table.html#...)

Not really, the innodb_file_per_table variable has been set to 1 for a long time. Running OPTIMIZE TABLE frees up the disk space in this case.

They just posted an update : https://twitter.com/olesovhcom/status/1448196879020433409

Following a human error during the reconfiguration of the network on our DC to VH (US-EST), we have a problem on the entire backbone. We will isolate the DC VH and then fix the conf.

The ISO country codes are different though (FR and GP), the heuristics may be based on that ?