You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking back at older proceedings and looked at IETF 107. The areas listed here includes WIT, and do not list Transport (TSV). There appear the datatracker fails maintain/present correctly what area WGs belonged to at the particular point in time and meeting. This leads to strange presentation like for 107 where MASQUE WG was TSV, but WebTrans was ART at that time. And ART do exist as category due to other WGs. This appears to be common across all proceedings pages that are generated based on datatracker database.
This is most likely bug in the proceedings templates where it's not using group_parent_at_the_time (or getting to parrent correctly from group_at_the_time) where it should be.
Describe the issue
I was looking back at older proceedings and looked at IETF 107. The areas listed here includes WIT, and do not list Transport (TSV). There appear the datatracker fails maintain/present correctly what area WGs belonged to at the particular point in time and meeting. This leads to strange presentation like for 107 where MASQUE WG was TSV, but WebTrans was ART at that time. And ART do exist as category due to other WGs. This appears to be common across all proceedings pages that are generated based on datatracker database.
Example: https://datatracker.ietf.org/meeting/107/proceedings
Code of Conduct
The text was updated successfully, but these errors were encountered: