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
BOFS missing from the agenda's session selection widget #784
Comments
@olau@iola.dk changed owner from `` to |
@olau@iola.dk commented Yeah, the model has changed slightly regarding state versus type so the querysets doesn't return the right set of groups. My first try at fixing it didn't work, I'll have to dig deeper into this Monday. |
@olau@iola.dk changed status from |
@olau@iola.dk changed resolution from `` to |
@olau@iola.dk commented Fixed in 09281df. Improve IETFWG proxy to take "bof" groups into account when querying for active groups and map "bof" to IETFWG.ACTIVE. Fixes #784. |
@henrik@levkowetz.com changed status from |
@henrik@levkowetz.com changed resolution from |
@henrik@levkowetz.com commented Reopening this, as I think this solution will result in WG pages for the bofs, with no annotation
|
@olau@iola.dk commented Good point. Actually, the status_id part isn't necessary for the meeting views since they get the right groups through the queryset which is patched separately. So I've just committed your patch, and I think this should make both cases work. The reason I changed status_id is because the submit code adds a warning if you submit a draft for a group which is not status_id == IETFWG.ACTIVE, and I guess posting drafts for BOFs is not something that requires a warning? So we probably need to check for state_id in ("active", "bof") there now? |
@henrik@levkowetz.com commented Replying to ietf-svn-conversion/datatracker#784 (comment:4):
Not quite (I haven't looked into the details of why, I'm just observing this page at the URL in
Hm. Posting a draft which is owned by a BOF is never done -- it's all individual drafts at that point, |
@olau@iola.dk commented I think I need to clarify - you still need the queryset part of 09281df, my latest commit only overwrote the status_id part. I have a pristine checked out dev server, and in there I do see those three BOFs (this is with a database dump from yesterday). Regarding the posting part, I suppose we're fine there too, then, with what is currently committed as you would then get a warning. I think it says you're posting to an inactive group. I don't think you got the warning with the old schema, that's why I asked (but I could be wrong, I didn't actually test it, I was just grepping the code to look for other issues). |
@henrik@levkowetz.com changed status from |
@henrik@levkowetz.com changed resolution from `` to |
@henrik@levkowetz.com commented Replying to ietf-svn-conversion/datatracker#784 (comment:6):
Ah, Ok. Ok, patch added. Not sure how to resolve that with the repository now, but the functionality
Ok, good. Thanks :-) |
@henrik@levkowetz.com changed status from |
@henrik@levkowetz.com changed priority from |
owner:olau@iola.dk
resolution_fixed
type_defect
| by rjsparks@nostrum.comThe calendar graphic at
https://datatracker.ietf.org/meeting/83/agenda.html#GEN
shows the GEN bofs, but the columns above the calendar that let you select
which sessions you want to attend does not list those bofs.
This is true for BOFs in general, not just GEN. INSIPID does not show in the list for RAI, weirds does not show in the list for apps, etc.
Issue migrated from trac:784 at 2022-03-04 01:59:52 +0000
The text was updated successfully, but these errors were encountered: