gh-103225: Fixed zero lineno issue for pdb#103265
Conversation
|
Sure! Thank you for extracting the workaround and the test for Regarding adding co-authors, this article might be helpful. But that is fine anyway 🙂 |
Sorry, something went wrong.
Co-authored-by: Artem Mukhin <ortem00@gmail.com>
73afc79 to
0b3c3b8
Compare
April 5, 2023 16:00
Thanks! That's helpful! |
Sorry, something went wrong.
|
@iritkatriel could you take a look at this fix which originally was done in |
Sorry, something went wrong.
|
I've added the "co-authored by" line to the first comment. |
Sorry, something went wrong.
I redid the commit with co-authored-by so @ortem is showing as the co-author in the commit now. |
Sorry, something went wrong.
…D3JVU.rst Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
|
I’m not sure that would work, because we squash the commits when merging and typically remove the individual commit messages. It does get picked up from the description of the PR though. |
Sorry, something went wrong.
|
Hmm, interesting to know that. Next time I'll do it in the PR. |
Sorry, something went wrong.
Actually I think more accurately - GitHub probably picks up the coauthor from the commit message, but the person who merges typically deletes all the individual commit messages, and is more likely to notice the "co-authored by" in the main message and not erase it. |
Sorry, something went wrong.
Co-authored-by: Artem Mukhin <ortem00@gmail.com>
We could, if this bug is there as well. Could you check to make sure, and then make a PR for 3.11? |
Sorry, something went wrong.
Co-authored-by: Artem Mukhin <ortem00@gmail.com>
Confirmed that 3.11 has this issue as well, PR was made. |
Sorry, something went wrong.
According to #103225,
inspect.getsourcelines()returns wrong line number. Fixing it itinspectwill take extra discussion so we fixed it inpdbfor now. If in the future this got fixed ininspectwe can take the fix away.Co-authored-by: Artem Mukhin ortem00@gmail.com