Shibboleth Developer's Meeting, 2020-06-05
Call Administrivia
09:00 Central US / 10:00 Eastern US / 15:00 UK / 17:00 FI
Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2020-06-19. Any reason to deviate from this?
60 to 90 minute call window.
This week's call will use the Zoom system at GU, see ZoomGU for access info.
AGENDA
- PKIX root behavior
Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1583 - Opening up master branches
- Ian Young's thread safety thing, see below
Attendees:
Brent
Daniel
Henri
Ian
- (Maybe an agenda item) Thread safety is hard:
- Arises through
; full discussion there.Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key MDA-242 - A lot of things we say are
@ThreadSafereally aren't, although they are mostly@ThreadSafeAfterInitand other things probably conspire to mean we're probably OK in practice. This makes me uncomfortable. - It's not possible even in principle to make most things truly
@ThreadSafebecause of
.Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key JSPT-97 - We could fix that (and I think we should, see this commit) but that wouldn't address all the issues, just make it possible to do so for cases we care most about.
- Beyond that, I don't think really nailing this down is going to be felt to be worthwhile, but we might want to document some assumptions and change some annotations anyway.
- Arises through
- Building from Docker containers:
iay/shibboleth-build-dockerseems to work
...