Releases: PelicanPlatform/xrdcl-pelican
v1.5.6
What's Changed
- Fix a bug that could cause the client to stop processing new requests if a significant number (approximately 16k) of operations have expired since process startup.
Full Changelog: v1.5.5...v1.5.6
v1.5.5
What's Changed
- Fix a bug that could trigger a deadlock when a busy plugin is unable to continue an ongoing prefetch request.
Full Changelog: v1.5.4...v1.5.5
v1.5.4
- Fix a bug that could trigger a deadlock when an ongoing operation has expired.
v1.5.3
- Fix a bug that triggers a segfault after an OPTIONS request has failed
v1.6.0
- Add ability for the client to query only for caches when using
pelican://URLs - Allow connection callback to occur without a DNS lookup
- Fix potential use-after-free in the prefetch code that is enabled by default. To trigger, the read operation must complete almost immediately (possible in unit tests, unlikely in "real world" situations where the client and server are not on the same host).
- Fix ability to have multiple write calls ongoing in parallel
- Basic implementation of a local writeback cache for
pelican://URLs. This is considered experimental and not currently user-facing.
v1.5.2
- Add infrastructure for automating GitHub releases from a pushed tag
- Automatically build as part of a release.
v1.5.1
What's Changed
Update the version number in the RPM spec file and in the HTTP User Agent to match the actual released version; this was omitted in the V1.5.0 release.
Full Changelog: v1.5.0...v1.5.1
v1.4.2
What's Changed
- Bumped the version numbers in the user-agent and the RPM spec file; these were missing from the v1.4.1 release.
Full Changelog: v1.4.1...v1.4.2
v.1.5.0
This release features extensive statistics about the performance of the XrdClCurl client.
If the XRD_CURLSTATISTICSLOCATION environment variable is set, statistics are written into the referenced location. Otherwise, they are recorded in the logfile or sent via the g-stream monitoring mechanism (currently only available in the XRootD 6 branch).
The new statistics provide for better detection of stuck threads (which likely indicate fatal issues) and the load from the origin requests for when XrdClCurl is used within a PFC.