-
Notifications
You must be signed in to change notification settings - Fork 0
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
transform is ~100x slower on data.table than on data.frame #5492 #2
Comments
the "not found" comes from the branch being in OfekShilon's fork, so you would have to make a new branch/pr with a copy of those commits in the main Rdatatable/data.table repo. but actually there is a problem with Before: "Before"="93ce3ce1373bf733ebd2036e2883d2ffe377ab58",#fIRST COMMIT IN THE PR(https://github.com/Rdatatable/data.table/pull/5493/commits) Before should not be any commit in the PR which fixes the issue, because any of those commits could have actually provided the fix. Instead, please take Before from the parent of the first commit in the PR which causes the issue (any of the commits in that PR could have started the regression). Does that make sense? |
"Regression"="0bacebc9b813d84b9b267e0928b5fd7c7ea126fb", #PARENT OF THE LAST OF THE PR THAT BFIXES THE ISSUE (https://github.com/Rdatatable/data.table/commit/1e03fe7b890e63da9651d997ea52548c90b3ae32) is not properly documented, can you please fix? |
also please ask any questions required to clarify your understanding. We discussed this on Tuesday and I thought you understood already? |
Apologies, I think i mixed the commits of the Before. Yes, suppose we have Commit A (Before), Commit B (Regression) and commit C (fix), Commit A represents the initial state where the issue was reported. Commit B is the regression commit that introduced the problem, and Commit C is the fix commit that resolves the issue. Commit B would typically have Commit A as its parent, indicating that it is based on the state of the code at Commit A. Commit C, on the other hand, would typically have Commit B as its parent, indicating that it is based on the state of the code at Commit B. |
got it, thanks |
you wrote "Regression can be the parent of any of the commits in the fixed PR," which is incorrect. Regression can only be the parent of the first commit in the Fixed PR, because any of the commits in that PR could have provided the fix. "Additionally, the Before commits can be the PR that reported the issue." -> this does not make sense. issues are reported in issues, not PRs. "However, I would like you to clarify if the Before commits can also be the parent of the Regression commits?" Before commit can be the parent of the first comit in the PR which caused the regression (because any of the commits in that PR may be responsible for the regression). |
|
Before needs improvement/fix. Before can be parent of first commit in PR which causes the issue (you wrote fixes instead of causes). also please do not write "this is a link to the commit 19b" in the comment, as that is redundant with the Before="19b..." in the code. (potentially confusing) Regression doc needs improvement. You wrote "This commit (93ce3ce) is parent of the first commit of the PR that fixes" but actually 93ce3ce is the first commit (not parent) of the PR #5493, can you please fix by moving parentheses? #parent of first commit (93ce3ce) etc |
also please use triple quotes when writing R code in issue comments:
|
@tdhock
similar to the other issue I sent,
I am running this performance test and I am encountering this error which is I am not able to install of the commit ids
This is the link to the PR that fixes the issue (Rdatatable/data.table#5493) and the link to the issue (Rdatatable/data.table#5492)
Error message
This is the code I am running
The text was updated successfully, but these errors were encountered: