ounds like you've got that solved.
>
> -- Marcin
>
> On Thu, May 30, 2019 at 7:55 AM James Hartig > wrote:
>
>> What's the best way to automatically always pull the latest
>> release/commit for certain repos? We use gerrit internally so all of our
>> imp
What's the best way to automatically always pull the latest release/commit
for certain repos? We use gerrit internally so all of our import paths for
internal packages start with something like gerrit.corp. We have over 50
different repos and it would be painstaking to have to update (pull lates
We are having a weird case where an atomic number was increasing and not
decreasing, despite calls to decrease it. Hopefully, someone on the list
can point out something I'm doing wrong with the atomic package.
The function with the issue is:
func UnhealthyOverConcurrent(prefix string, limit in
d when the handshake was never started.
Should I file a bug to remove the log in that case?
On Wednesday, May 3, 2017 at 9:45:00 AM UTC-4, James Hartig wrote:
>
> We're also seeing 100k of these errors per day per server. The majority of
> the time its just a result of:
> cli
We're also seeing 100k of these errors per day per server. The majority of
the time its just a result of:
client SYN
server SYN-ACK
client FIN
server FIN-ACK
or
client SYN
server SYN-ACK
Retransmission
Retransmission
RST
...
The error if the version is unsupported is:
http: TLS handshake error
There's x509.ParsePKCS8PrivateKey but no x509.MarshalPKCS8PrivateKey, which
is unlike the other x509.ParseTPrivateKey and x509.MarshalTPrivateKey
combinations. It seems trivial, so I'm curious why it was omitted?
Assuming no objections, I'd be willing to make a patch in gerrit adding
this.
--
