PlatformIO Community

Platformio not detect my library update on github within 24 hour

Is there something wrong? Here’s my repo

Press Ctrl+R to refresh browser cache:

What it take so much time? Maybe platformio should add update button like composer to manually fetch data from repo. Just my opinion.

Thank you so much

Patience and “within 24 hours” don’t really go well together in this age of instant gratification.

I’m wondering how the current setup scales - does the pio server have to poll all the libraries in its registry, all the time? What percentage is hardly ever being updated? Would a switch to request-driven updates reduce the load, or would it just tempt people & scripts to constantly submit update requests - hard to predict.

PS. This is also my sneaky way to ping Ivan to update #3082 … <wink>

1 Like

I see a lot of errors by our crawler for your manifest:

$ git clone --single-branch -v https://git.jeelabs.org/jcw/jeeh.git
fatal: unable to access 'https://git.jeelabs.org/jcw/jeeh.git/': gnutls_handshake() failed: Handshake failed

Do you have any ideas?

The host is specially configured to only use the Curve25519 elliptic curve and with TLS v1.2 or the newest experimental TLS v1.3.

Older clients which do not know this curve or these specific ciphersuite get rejected (from ssllabs)

So you’d need a fairly recent gnutls library. Either follow this and replace libcurl4-gnutls-dev with libcurl4-openssl-dev (hoping that openssl can handle this server) or get a recent version of libcurl4-gnutls-dev for the distro

My windows git installation can handle it.

Thanks for checking - I’m pretty much out of my depth here, I’m afraid.

My setup is a Caddy server as reverse proxy in front of a Gitea server, with settings to get a good SSL rating (this was done a year or so ago). As I understand it, Caddy does not use the libraries you mention - it’s written in Go, which has its own (well-maintained, I think) SSL implementation. Or maybe I’m misreading Max’s comments, and those instructions are meant for Ivan?

See https://www.ssllabs.com/ssltest/analyze.html?d=git.jeelabs.org for details.

Max’s comments are for Ivan… as he pointed out, there are issues with old clients, and only allows the exprimental v1.3 TLS and v1.2 TLS… meaning Ivan will probably need to update stuff on the server doing the crawling in order to get it to handshake properly.