Skip to content

Default values the way the docs suggest we do#1

Merged
ghalse merged 1 commit intomasterfrom
options-match-docs
Nov 29, 2021
Merged

Default values the way the docs suggest we do#1
ghalse merged 1 commit intomasterfrom
options-match-docs

Conversation

@ghalse
Copy link
Collaborator

@ghalse ghalse commented Nov 29, 2021

The documentation says we default process name and facility, but this doesn't happen if logdest=remote and a logconfig is set to point somewhere other than localhost (as is the case when sending to eduGAIN!). This change makes the behaviour match the documentation.

@codecov
Copy link

codecov bot commented Nov 29, 2021

Codecov Report

Merging #1 (39bf6a2) into master (4a4d19d) will increase coverage by 0.38%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master       #1      +/-   ##
============================================
+ Coverage     68.94%   69.32%   +0.38%     
- Complexity       58       60       +2     
============================================
  Files             1        1              
  Lines           161      163       +2     
============================================
+ Hits            111      113       +2     
  Misses           50       50              

@ghalse ghalse requested a review from tvdijen November 29, 2021 14:28
@ghalse
Copy link
Collaborator Author

ghalse commented Nov 29, 2021

@tvdijen since you've made a number of changes, I want to make sure this bug fix isn't going backwards on anything you've done?

Also at what point do we create a new release?

@ghalse ghalse added the bug Something isn't working label Nov 29, 2021
@tvdijen
Copy link
Member

tvdijen commented Nov 29, 2021

Any changes I've made were related upgrading dependencies or taking advantage of typehinting... I see I've also split some code to reduce complexity.. No real changes.
I think now is the time to merge this, branch off a release-1.0 branch and tag v1.1.3.
We can also tag v1.2.0 in master once we bump the required SSP-version to ^2.0-beta.1 and start testing that.

@ghalse ghalse merged commit 9f085e6 into master Nov 29, 2021
@ghalse ghalse deleted the options-match-docs branch November 29, 2021 18:19
@tvdijen
Copy link
Member

tvdijen commented Nov 29, 2021

I've changed the dependency on SSP from dev-master to ^2.0.0-beta.1.. It should now be ready for a 1.1.3 tag

@ghalse
Copy link
Collaborator Author

ghalse commented Dec 1, 2021

Yeah, I realised when I did some testing that we couldn't tag as-is (hence the draft). I was trying to work out which of your changes were compatible with the current 1.x branch and merge those into a release-1.0 branch. Started on that, but hadn't finished :)

@tvdijen
Copy link
Member

tvdijen commented Dec 1, 2021

You want your change to be in a 1.19 compatible version? In this case I would check out v1.1.2, push it to a release-1.0 branch and cherry-pick this PR on top.. Then tag it as v1.1.3.
For master/SSP2.0 we can tag 2.0.0

@ghalse
Copy link
Collaborator Author

ghalse commented Dec 1, 2021

Yup, that's what I'm doing :)

@ghalse
Copy link
Collaborator Author

ghalse commented Dec 1, 2021

The release-1.0 branch now includes this patch, and tests fine against SSP 1.19.1. The draft is tagged against that now.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants