Skip to content
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

Merged
merged 31 commits into from
Aug 14, 2024
Merged

BUG: avoid certificate experation #144

merged 31 commits into from
Aug 14, 2024

Conversation

aburrell
Copy link
Member

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.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Unit tests

Test Configuration

  • Operating system: OS X Big Sur
  • Version number: Python 3.10
  • Any details about your local setup that are relevant: develop branch of pysat

Checklist:

  • Make sure you are merging into the develop (not main) branch
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • Add a note to CHANGELOG.md, summarizing the changes

If 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

Avoid certificate expiration by using the `verify` flag set to False.
@aburrell
Copy link
Member Author

aburrell commented Jul 30, 2024

  • fix broken links
  • update intersphinx mapping
  • fix whatever is up with the GA tests

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 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'.
@aburrell
Copy link
Member Author

@jklenzing any idea how I can get the coverage analysis to run?

Changes were unnecessary, lost track of maintenance updates.
@jklenzing
Copy link
Member

@jklenzing any idea how I can get the coverage analysis to run?

Here's what is working for pysatSeasons: pysat/pysatSeasons#43

Added the "always" yaml call to coveralls.
Test removing the carryforward command.
@aburrell aburrell requested a review from jklenzing August 13, 2024 19:24
Copy link
Member

@jklenzing jklenzing left a 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.
@aburrell aburrell requested a review from jklenzing August 13, 2024 23:55
@jklenzing
Copy link
Member

jklenzing commented Aug 14, 2024

FAILED pysatSpaceWeather/tests/test_instruments.py::TestInstruments::test_load_w_pad[pad0-inst_dict16] - AssertionError: Padding should have left data and didn't
FAILED pysatSpaceWeather/tests/test_instruments.py::TestInstruments::test_load_w_pad[pad0-inst_dict25] - AssertionError: Padding should have left data and didn't
FAILED pysatSpaceWeather/tests/test_instruments.py::TestInstruments::test_load_w_pad[pad1-inst_dict16] - AssertionError: Padding should have left data and didn't
FAILED pysatSpaceWeather/tests/test_instruments.py::TestInstruments::test_load_w_pad[pad1-inst_dict25] - AssertionError: Padding should have left data and didn't

Padding failures in all workflows

@aburrell
Copy link
Member Author

@jklenzing that was an unlucky timing issue with one of the realtime files. Reran tests and now have only expected failures.

@aburrell aburrell merged commit 6786a50 into develop Aug 14, 2024
26 of 30 checks passed
@aburrell aburrell deleted the kp_verify_bug branch August 14, 2024 14:50
@aburrell aburrell added this to the 0.2.0 milestone Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants