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

Port DevCom bugs to GitHub #939

Closed
53 of 58 tasks
Tracked by #4699
StephanTLavavej opened this issue Jun 30, 2020 · 59 comments
Closed
53 of 58 tasks
Tracked by #4699

Port DevCom bugs to GitHub #939

StephanTLavavej opened this issue Jun 30, 2020 · 59 comments
Labels
documentation Related to documentation or comments resolved Successfully resolved without a commit

Comments

@StephanTLavavej
Copy link
Member

StephanTLavavej commented Jun 30, 2020

As part of our work to migrate all STL development to GitHub, we're porting our Microsoft-internal bug database ("VSO"; originally Visual Studio Online, renamed Azure DevOps and Azure Boards) to GitHub issues. Some bugs were directly filed in VSO (by STL maintainers and other people within MS, sometimes on behalf of customers), while some were replicated from Developer Community ("DevCom").

As part of this porting process, we aren't resolving any bugs. The intended goal is for GitHub to be the source of truth for all bug reports (in addition to performance/enhancement/etc. suggestions); it's also our preferred place for new issues to be filed. (Issues filed on GitHub aren't replicated anywhere else, so it's the most convenient for us.) However, users who filed DevCom bugs in the past (or continue to file them in the future) will have their bugs remain active, and will receive feedback from STL maintainers there (in addition to their bugs being ported to GitHub issues where they can be linked to pull requests etc.). Additionally, VSO bugs (whether filed directly or replicated from DevCom) will remain active because our bosses and boss-like entities prefer that.

"Porting" a bug to GitHub involves capturing the true essence of the bug report, without distorting or over-simplifying it. (Much like compiler bugs, STL bugs can be very sensitive to the exact code, compiler options, etc. used.) However, we also want our GitHub issues to be readable and comprehensible, so that both maintainers and contributors can understand what's wrong and easily investigate a fix. So, when possible, it's nice to clean up the title and test case, so that they're as clear and minimal as possible. (It is often a good idea to have an "original repro" and "reduced repro", to avoid the dangers of over-simplifying away something important - and I speak as someone who has over-simplified a dozen compiler bug reports in the past.) It's better to err on the side of less cleanup than more - fixing only grammatical issues is fine.

Example bugs ported from DevCom: GH-371 (from DevCom-758960) and GH-503 (from DevCom-371962)

While only the STL maintainers will be able to port the MS-internal bugs that were directly filed in VSO, the DevCom database is publicly viewable, so we could use some help with those bugs. 😸

Here's a list of the DevCom bugs, along with their VSO IDs and Titles. (Sometimes, multiple DevCom bugs were linked to a single VSO bug, when we had a strong belief that they're all duplicates.) I generated this by hand, so if anything looks wrong (e.g. mismatched VSO/DevCom bugs), please let me know. Note that everyone in this repo has the ability to use our Custom Autolinks in GitHub issues/comments; you can just say DevCom-NNN instead of copying a whole URL.

In general, we have already tried to resolve clearly-invalid bugs, and obvious duplicates, but there are several categories of possible duplicates that we haven't resolved because there may be multiple underlying issues.

Finally, in addition to the title and repro, ported bugs should mention the DevCom and VSO IDs, so we can easily navigate to the linked bugs:

Also tracked by DevCom-publicnumber and VSO-internalnumber / AB#internalnumber.

AB followed by # (not - like other autolinks) will activate automation: your issue will be automatically edited by @msalehmsft to add a hyperlink (it won't appear in a Preview), and the internal bug will gain a special link. This must be mentioned in the original issue to create the internal link; using this syntax in issue comments below will be hyperlinked from GitHub, but not to GitHub.

Please don't use AB#nnn syntax here, in this thread as it will link "Port DevCom bugs to GitHub" to whatever's mentioned. DevCom-nnn and VSO-nnn are safe to mention anywhere.

🪲 Remaining: VSO ID | DevCom ID(s) | Original VSO Title

  • All done!

⏳ In Progress

  • None.

⚠️ Blocked

  • Let us know if anything simply can't be ported due to test cases in non-public attachments, descriptions that don't make sense, etc. We'll handle these bugs separately.
  • Non-public attachments:
    • VSO-238123 | DevCom-189336 | <iomanip>: std::get_time cause Debug Assertion Failed when the second parameter have extra delimiter
    • VSO-275595 | DevCom-246257 | <regex>: Instantiating std::regex("meow") changes output of strftime in a different thread
    • VSO-406125 | DevCom-246250 | <iomanip>: std::get_time does not report fail on an invalid date
  • Non-public screenshots:
  • Needs extra attention, see linked comments below:

❌ Resolved As Invalid

🛠️ Compiler Bug, Reduced To Library-Free Test Case And Sent To Compiler Team

😸 Fixed

✔️ Done

@StephanTLavavej StephanTLavavej added documentation Related to documentation or comments help wanted Extra attention is needed labels Jun 30, 2020
@StephanTLavavej

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@Amaroker

This comment has been minimized.

@Amaroker

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@statementreply

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@StephanTLavavej StephanTLavavej pinned this issue Jul 1, 2020
@AlexGuteniev

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev
Copy link
Contributor

AlexGuteniev commented Jul 5, 2020

Ported the following:

Did not port:

  • VSO-275595 | DevCom-246257 | <regex>: Instantiating std::regex("meow") changes output of strftime in a different thread - Non-public attachment.
  • VSO-399948 | DevCom-249123 DevCom-86665 DevCom-267556 | std::regex_search causes infinite recursion on a sample that works with Visual Studio 2013 and gcc - Suspicious
    • DevCom-249123 does not have enough public info.
    • DevCom-86665 looks like infinite recursion, but I'm not completely sure
    • DevCom-267556 is clearly a different issue and apparently invalid issue. To me looks like regex_constants::error_brace is legitimately thrown

@statementreply

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@Amaroker

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@Amaroker

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@fsb4000

This comment has been minimized.

@fsb4000

This comment has been minimized.

@StephanTLavavej

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@AlexGuteniev

This comment has been minimized.

@StephanTLavavej
Copy link
Member Author

Thanks @AlexGuteniev! I agree about GH-412 and have linked them up.

Yay - all bugs with public info have been ported! Thanks everyone! 🎉

@StephanTLavavej StephanTLavavej added resolved Successfully resolved without a commit and removed help wanted Extra attention is needed labels Aug 19, 2020
@StephanTLavavej StephanTLavavej unpinned this issue Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Related to documentation or comments resolved Successfully resolved without a commit
Projects
None yet
Development

No branches or pull requests

6 participants