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

overfull indicator is applied when there are shared sessions #3319

Closed
ietf-svn-bot opened this issue Jun 23, 2021 · 2 comments · Fixed by #5044
Closed

overfull indicator is applied when there are shared sessions #3319

ietf-svn-bot opened this issue Jun 23, 2021 · 2 comments · Fixed by #5044

Comments

@ietf-svn-bot
Copy link

type_defect | by [email protected]


See /meeting/110/agenda/[email protected]/prelim110/edit/ and note the thu 1500 rtgarea/rtgwg shared session.

This issue has been present for awhile, but was highlighted after a6e08f1. (Liz - you won't see this until a release with a6e08f1 in it is put into production).

This may be on purpose though - sometimes when we put multiple sessions in a single timeslot the intent is that they run in parallel, and sometimes they run sequentially, so Liz - do you want it to show a potential overflow even if in the parallel case the combined sessions will fit? We have no way to know if the intent is parallel or sequential, so right now the view acts as if such things are always sequential. Is that the right choice?


Issue migrated from trac:3319 at 2022-03-04 08:44:18 +0000

@ietf-svn-bot
Copy link
Author

@[email protected] commented


Email conversations say to remove the overfull indicator when the only reason is sessions sharing a timeslot, but to keep it if there is a session that is longer than the timeslot can hold.

@ietf-svn-bot
Copy link
Author

@[email protected] changed status from new to accepted

@jennifer-richards jennifer-richards self-assigned this Jan 27, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants