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
The issue_introduction.patch seems to be invalid for 32 instances, causing the setup_expensify setup script called from run.sh to fail at the line patch -p1 < "/app/tests/issues/$ISSUE_ID/issue_introduction.patch"
Reproduction Steps:
Take issue 203 as an example.
Build the swelancer docker container based on the README.md
Run the container with an overrided entrypoint for debugging docker run -d --name my_container --entrypoint "" swelancer:latest tail -f /dev/null
Attach to the container.
git reset --hard origin/master
git checkout <commit_id>, in this case git checkout da2e6688c3f16e8db76d2bcf4b098be5990e8968
patch -p1 < "/app/tests/issues/{issue_id}/issue_introduction.patch", in this case patch -p1 < "/app/tests/issues/203/issue_introduction.patch"
Output:
patching file src/components/MoneyRequestConfirmationList.tsx
patching file src/components/SelectionList/BaseSelectionList.tsx
patching file src/languages/en.ts
patching file src/languages/es.ts
patching file src/pages/tasks/NewTaskPage.tsx
patch: **** malformed patch at line 180: @@ -145,14 +179,14 @@ function NewTaskPage({route}: NewTaskPageProps) {
There are 178 / 381 instances with an issue_introduction.patch. The majority of them are working properly, but I have encountered these patch failures with the issue_introduction.patch on the following 32 issue_ids=[203, 208, 210, 211, 213, 216, 217, 220, 221, 226, 229, 231, 246, 255, 266, 271, 275, 277, 297, 299, 300, 301, 303, 313, 320, 324, 338, 340, 342, 345, 355, 370]
Additional question:
There is this figure in the paper showing a success rate of 7.7% on instances with a task price >= $2k. This implies there are 13 samples, or some multiple of 13, with value >=$2k. However, if you query the swelancer_tasks.csv, you will only find 2 samples that meet this criterion. What is the reason for this mismatch?
The text was updated successfully, but these errors were encountered:
Issue
The issue_introduction.patch seems to be invalid for 32 instances, causing the
setup_expensify
setup script called fromrun.sh
to fail at the linepatch -p1 < "/app/tests/issues/$ISSUE_ID/issue_introduction.patch"
Reproduction Steps:
Take
issue 203
as an example.docker run -d --name my_container --entrypoint "" swelancer:latest tail -f /dev/null
git reset --hard origin/master
git checkout <commit_id>
, in this casegit checkout da2e6688c3f16e8db76d2bcf4b098be5990e8968
patch -p1 < "/app/tests/issues/{issue_id}/issue_introduction.patch"
, in this casepatch -p1 < "/app/tests/issues/203/issue_introduction.patch"
Output:
There are 178 / 381 instances with an
issue_introduction.patch
. The majority of them are working properly, but I have encountered these patch failures with theissue_introduction.patch
on the following 32issue_ids=[203, 208, 210, 211, 213, 216, 217, 220, 221, 226, 229, 231, 246, 255, 266, 271, 275, 277, 297, 299, 300, 301, 303, 313, 320, 324, 338, 340, 342, 345, 355, 370]
Additional question:
There is this figure in the paper showing a success rate of
7.7%
on instances with atask price >= $2k
. This implies there are 13 samples, or some multiple of 13, with value >=$2k. However, if you query theswelancer_tasks.csv
, you will only find 2 samples that meet this criterion. What is the reason for this mismatch?The text was updated successfully, but these errors were encountered: