Re: [HTCondor-users] how do I test/debug condor_chirp ?

[Stefano Belforte <stefano.belforte@xxxxxxx>]

Thanks Tim,
While 5K is better than 1K, my string will still not fit.
it is now clear that in my use case I need a different means
to pass information from the job to the monitoring infrastructure
where that horribly-long thing will be digested.
I surely agree that chirp is not a substitute for files.
In our (CMS) setup the advantage of chirp was that we
already have an established path to send job classAds to HDFS
and ElasticSearch, a new file will need a new channel, but
we can do it.

Stefano

On 11/11/2023 21:40, Tim Theisen wrote:
> I took a quick look at the source and found that we increased the line 
> limit for chirp from 1024 characters to 5120 characters back in 2015. 
> Unfortunately, we missed updating the chirp line length in the Python 
> bindings. It is still 1024 there.