Leap second table in solid.for expired on 28 December 2025

[EJFielding]

For dates after 28 December 2025, the solid.for program generates warnings every time it is called. The expiration date is hard-coded into the program. Since there have been no leap seconds since 2017, this is an annual update hassle.

[EJFielding]

The solid.for code author explains that not implementing the exact leap second correction would be a very small error, so I propose to remove the warning from the version of the code here in PySolid. Since this program is called thousands of times in a typical NISAR interferogram processing with the insar.py workflow, it generates thousands of error messages sent to the terminal. When I run the interferogram workflow for a NISAR scene in a cloud JupyterHub terminal window, it brings the whole GUI to a standstill.

[yunjunz]

I agree with you Eric, let's remove the warning msg.

[yunjunz]

I will cut for a new release, after fixing the github docker issue (https://github.com/insarlab/PySolid/actions/runs/21201142808/job/60986931092).

[hfattahi]

Hi @yunjunz ,
Thanks for turning the warning off. That looks like what we could do at this point. I re-opened the issue to make sure that we make a release and push to conda. Any thoughts if you want to do that or maybe anyone else can help?
@scottstanie @piyushrpt @jhkennedy this fix is needed to reduce the size of log messages.

[yunjunz]

Thanks for the reminder @hfattahi. All urgent changes have been merged; I will make a new release today.

[yunjunz]

The new version 0.3.4 has been released and is available on PyPI (https://pypi.org/project/pysolid) and the conda forge channel (https://anaconda.org/channels/conda-forge/packages/pysolid/overview).