aayjaychan

5 ms·

1.
by aayjaychan 2y ago
There is no "one-time" over the network. Invalidating the refresh token immediately when the server recieves it is asking for trouble.
2.
by aayjaychan 2y ago
it's always wild to me hearing what pressure people use. on my road bike with 28c and inner tubes, 60 psi is what i use on _good_ road surface. maybe the roads are just shit here, but even 55 psi feel rough. i usually run on around 5
3.
by aayjaychan 2y ago
navigation properties are not loaded automatically, because they can be expensive. you need to use `.Include(foo => foo.Bars)` to tell EF to retrieve them. EF tries to be smart and will fix up the property in memory if the referenced en
4.
by aayjaychan 3y ago
Published history in Mercurial is sacred [1]. Modern Mercurial fully embraces history editing, and provides (IMO) better tools than git to facilitate (safe, collaborative) history editing. [1] You can still change published history if y
5.
by aayjaychan 3y ago
I drew a different conclusion from similar experience. I avoid navigation properties and other advanced mapping features, so an entity maps flatly to one table. The LINQ queries will be more verbose as you'll need to write the join an
6.
by aayjaychan 4y ago
You can use `hg commit --interactive` to use the the commit itself as the staging area. And I'd argue that's a better model because: - It limits the amount of time changes are stored in an intermediate state, making it much less
7.
by aayjaychan 4y ago
No reflog, but there is the obslog, which stores obsolescence history of individual revisions. Better yet, the obslog is distributed during pull / push. Because Mercurial knows precisely which commit is replaced by which commit, it c
8.
by aayjaychan 4y ago
I agree having production updated frequently is ideal, but sometimes we don't get to choose when things are deployed when working with external clients. I'm glad Terraform doesn't dictate the workflow, so that we can fix one
9.
by aayjaychan 4y ago
I'll consider this a variation on moving state elsewhere. Now you have to keep the deleted resource forever. Or keep track of which environments the version with the removal directive is deployed to, or risk having orphaned resources
10.
by aayjaychan 4y ago
If Terraform is stateless, how does it know what it needs to / can delete? You'll either have to: - Move the state management elsewhere, and invoke different commands depends on what and how resources are changed. This will make
11.
by aayjaychan 4y ago
csproj is fine these days. sln on the other hand...
12.
by aayjaychan 4y ago
that would be `hg prune` in modern Mercurial.
13.
by aayjaychan 4y ago
By default, Mercurial doesn't allow editing of public history pushed to or pulled from a remote repository. There are no such restrictions for local revisions, which are considered draft. And if you configure the remote as a draft r
14.
by aayjaychan 4y ago
We have have been on self-hosted Heptapod [1] for about a year without much complaint. Heptapod is a fork of GitLab with Mercurial support. For open source projects, there is a free hosted version [2]. [1]: https://heptapod.net
15.
by aayjaychan 5y ago
if you do this often and want some automation, `git absorb` [1] may be worth a look. it will try to find lines that can be unambiguously attributed to a diff based on when the line and its surrounding lines are last modified, and then gene
16.
by aayjaychan 5y ago
in some accents they rhyme because of the cot-caught merger. https://en.wikipedia.org/wiki/Cot%E2%80%93caught_merger
17.
by aayjaychan 5y ago
Does GitLab count as a GitHub-like experience? There is a fork of GitLab called Heptapod that supports Mercurial. https://heptapod.net/
18.
by aayjaychan 6y ago
Changeset Evolution [1], which allows me to amend and rebase shared commits without co-workers hating me, even when they are building on top of the mutated commits. [1]: https://www.mercurial-scm.org/wiki/ChangesetEvolu
19.
by aayjaychan 6y ago
There is one (though incomplete)! And it's called Mercurial. Since 5.4 released earlier this year, Mercurial is slowly gaining [1] the ability to operate on local Git repositories with its bundled git extension [2]. [1]: https:/&
20.
by aayjaychan 6y ago
Yes, unreachable commits in Git are GC'd eventually, but you can disable it. In Mercurial, hidden changesets are kept locally indefinitely, but they are not exchanged; only their obsolescence makers are. So you always know the meta-his
21.
by aayjaychan 6y ago
Git does hide the old commits as well. What git doesn't do is track which commits are replaced by which. So sharing mutable history and seeing how a commit evolved over time requires more heuristic than necessary.
22.
by aayjaychan 6y ago
It works pretty well for the most part, since vim verbs and nouns are kind of like acronyms. 'w' goes to next Word. 'b' goes Back a word, 'i' enables Insert mode, 'd' Deletes something. So as long as
23.
by aayjaychan 6y ago
To me as a daily Mercurial user, the biggest thing it brings is, in Git parlance, a distributed reflog. It makes sharing of mutable history much easier and safer. Mercurial has the concept of changeset evolution [1] that tracks the meta-