- edit over tramp - dired over tramp - magit over tramp - build over tramp
Just Beautiful.
179 karma · joined August 11, 2009
- edit over tramp - dired over tramp - magit over tramp - build over tramp
Just Beautiful.
This way, if enough people filter-out, the person will be silenced. Others, who are more forgiving, would continue to receive that person's contributions.
My rule is, I make decisions for myself and only myself.
As per vgo blog posts, this scenario is not an Upgrade, but replacing one package with another package. A package is uniquely identified by it's import path, so if major version is changed, import path changes, so it is not same package.
Imagine the packaging and development ecosystem in internet scale.
My understanding is, it does Two-Phase-Commit (across WAN) over fault-tolerant objects (located in a Paxos Group). Paxos Group could span across Data-Centers, but there it just uses normal Multi-Paxos -- perhaps with some extra leader election tricks.
I have ~/go for all 3rd party code that I did not develop. My personal projects live in a different directory with a different structure (including, configure.ac, Makefile.am, etc.). My projects tend to use multiple languages, so I need Makefile support.
I fix GOPATH in project specific Makefiles with ~/go as the first directory followed by project specific directory for Go code. For example, I add the following in Makefile.am of every project.
GOPATH := $(HOME)/go:$(CURDIR)/go
One cool result of this is: When I do go-get of any 3rd party package (either through command-line or as part of a rule from Makefiles), Go downloads them into ~/go directory (it picks the first directory in GOPATH or defaults to ~/go). This leaves my project specific directories free of 3rd party code -- which is what I want.
End result is, ~/go ends up with 3rd party code from across all projects and it doesn't include my project code, so can be deleted any time and re-created automatically by Makefile rules.
On the left I see the old MR and my comments on that upload and on the right I see the new diff around the commented lines.
They upgrade every week. Who the hell does that to paying customers? And half of their website functionality doesn't work when they upgrade -- but their upgrade-banner always says "no down time is expected". It is a running joke in my company.
We constantly get error 500 during upgrades. Merge requests don't commit. Rebase feature didn't work till a few weeks back. Gitlab runners get stuck every now and then. I use it everyday because of company policy, but folks, Gitlab is a really poor product. Feels like they test their product on paying customers.
Also, do they even know how good their competition is at? You can't see the what is changed in response to your comment between two MR uploads. You can't add comments on unchanged parts of the code in the diff-view. You can't add comments when you view the diff between two uploads of an MR. My list of complaints is endless.
I always hear this from CockroachDB folks and fans, but no details. What are the downsides?
As per my understanding, if a server/replica could not catch up wrt time (i.e. goes out of sync), it can be identified and usually be marked as a temporary-replica-failure -- which is the maximum extent that Hybrid Logical Clocks can help us with. Rest of the system has to deal with consequences: A new replica must take it's place to keep-up the fault-tolerance-level and start making-a-new-copy -- which is in the order-of the amount of data stored in the out-of-sync replica. I assume this puts lot different design requirements on the storage-engine; also, making-a-copy and cancel-copying operations would eat network traffic, thus throughput.
IIRC Google Spanner uses atomic clocks only on few severs per data-center because cross data-center latencies are much higher and erratic (over internet). So CockroadDB has much higher rate of temporary-failures due to out of time-sync and associated downsides. It would be helpful if CockroachDB guys could shed some light on this.
My understanding from 2012 paper was that it doesn't support nested transactions, even at the storage layer.
Can anybody provide insider-knowledge if it was even a requested feature from Google devs internally?
It still has few rough edges, so may not be for everybody.
I would recommend everybody I know to stay away from Scott and may be, even A16Z.
Of course, this comparison is not really fair because Lamport BFT achieves deterministic consensus, where as, bitcoin only gives probabilistic consensus.
I hope there is room for Deterministic BFT with <50% malicious actors.
> or in some new highly-academic algorithms O(N polylog(N))
Could you point me to this algorithm? I am not aware of any BFT solution other Lamport BFT.
Is a "VC firm filing for bankruptcy" the only indicator?
Can someone more knowledgeable share some thoughts on this?
NSO and ISO are usually termed Stock Options.
Which category are they? "stock" or "options"?
Also, doesn't outstanding stock an useless/misleading metric without disclosing liquidation preferences of the investors?
I can't find PoE to micro-usb cable anywhere else but this comes close.