-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: avoid certificate experation #144
Conversation
Avoid certificate expiration by using the `verify` flag set to False.
|
Updated the pandas fill method, replacing the deprecated `fillna` with `ffill`.
Updated the pandas indexing and fill method, replacing the deprecated `fillna` with `ffill`.
Added logger output for file creation at the info level.
Updated the pandas series indexing method.
Updated the NCEI name. Did not add a link, as their website is not stable.
Added links to ignore in the unit tests, as they are file but require certificates to access.
Updated changelog.
Updated intersphinx mapping.
Removed Python 3.9 from listed support.
Updated the main CI test by: - cycling the python versions tested, - updated NEP29, and - attempting to use the coveralls action.
Fixed the syntax for the tuple in the intersphinx mapping.
Cycle the pysat_rc tests to use the highest supported version.
Fixed yaml syntax.
Added the github token secret specification to the coveralls action.
Removed 's' in call to GitHub Actions.
The correct change for resampling to maintain the old behaviour was to change `fillna` with `asfreq`.
If the frequency is less than a day, use the mean for the entire day. Otherwise, include a fill value.
`addopts` was interfering with local testing, move back to test yaml.
Probably need coveralls installed to get something to report.
Update the format of the pandas frequency to address FutureWarnings.
Implement pandas iloc to address FutureWarnings.
Ensure coveralls output is xml.
Fixed a typo in the new `iloc` call.
Try and force coveralls to finish even if some jobs fail.
Try carryforward instead of 'fail-on-error'.
@jklenzing any idea how I can get the coverage analysis to run? |
Changes were unnecessary, lost track of maintenance updates.
Here's what is working for pysatSeasons: pysat/pysatSeasons#43 |
Added the "always" yaml call to coveralls.
…ather into kp_verify_bug
Test removing the carryforward command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sure the updates to coveralls are included in the pysat_rc.yml
Update coveralls in pysat_rc tests.
Padding failures in all workflows |
@jklenzing that was an unlucky timing issue with one of the realtime files. Reran tests and now have only expected failures. |
Avoid certificate expiration by using the
verify
flag set to False.Addresses an issue identified at APL, where their certificate had expired.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Unit tests
Test Configuration
Checklist:
develop
(notmain
) branchCHANGELOG.md
, summarizing the changesIf this is a release PR, replace the first item of the above checklist with the
release checklist on the pysat wiki:
https://github.com/pysat/pysat/wiki/Checklist-for-Release