Details

      Description

      There are several problems from international olympiads that use output-only format, i.e. contestant can submit only output files for given inputs (in zip format or txt). Right now SIO does not support such tasks.

        Activity

        Hide
        Szymon Acedański added a comment -
        This issue has been automatically closed as Obsolete due to no activity for 365 days.

        Feel free to reopen it or create a new one if it's still relevant.
        Show
        Szymon Acedański added a comment - This issue has been automatically closed as Obsolete due to no activity for 365 days. Feel free to reopen it or create a new one if it's still relevant.
        Szymon Acedański made changes -
        Field Original Value New Value
        Status New [ 10000 ] Resolved [ 5 ]
        Assignee Szymon Acedański [ accek ]
        Resolution Obsolete [ 7 ]
        Hide
        Michalina Sidor added a comment -
        @kostka reports that this is still a desired feature
        Show
        Michalina Sidor added a comment - @kostka reports that this is still a desired feature
        Michalina Sidor made changes -
        Resolution Obsolete [ 7 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Assignee Szymon Acedański [ accek ]
        Jakub Wasilewski made changes -
        Assignee Jakub Wasilewski [ wasyl ]
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 1
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that threats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This mean that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. ATM checkers and ingens are being runned by blindly
        executing given executable (one of the reasons why python and java code
        doesn't work for those), which could theoretically create possibility
        of sending a package with arbitrary executable called "???ingen.txt".
        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be runned through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 1 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that threats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This mean that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. ATM checkers and ingens are being runned by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be runned through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 2
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that threats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This mean that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. ATM checkers and ingens are being runned by blindly
        executing given executable (one of the reasons why python and java code
        doesn't work for those), which could theoretically create possibility
        of sending a package with arbitrary executable called "???ingen.txt".
        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be runned through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 2 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that threats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This mean that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. ATM checkers and ingens are being runned by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be runned through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 3
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that threats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This mean that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. ATM checkers and ingens are being runned by blindly
        executing given executable (one of the reasons why python and java code
        doesn't work for those), which could theoretically create possibility
        of sending a package with arbitrary executable called "???ingen.txt".
        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be runned through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 3 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that threats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This mean that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. ATM checkers and ingens are being runned by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be runned through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 4
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that threats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This mean that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. ATM checkers and ingens are being runned by blindly
        executing given executable (one of the reasons why python and java code
        doesn't work for those), which could theoretically create possibility
        of sending a package with arbitrary executable called "???ingen.txt".
        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be runned through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 4 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that threats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This mean that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. ATM checkers and ingens are being runned by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be runned through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 5
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that threats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This mean that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. In curent version of oioioi checkers and ingens
        are being runned by blindly executing given executable
        (one of the reasons why python and java code doesn't work for those),
        which could theoretically create possibility of sending a package with
        arbitrary executable called "???ingen.txt".

        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be runned through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 5 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that threats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This mean that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. In curent version of oioioi checkers and ingens are being runned by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be runned through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 6
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that threats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This mean that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. In curent version of oioioi checkers and ingens
        are being runned by blindly executing given executable
        (one of the reasons why python and java code doesn't work for those),
        which could theoretically create possibility of sending a package with
        arbitrary executable called "???ingen.txt".

        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be runned through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 6 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that threats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This mean that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. In curent version of oioioi checkers and ingens are being runned by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be runned through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 7
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that treats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This means that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. In current version of oioioi checkers and ingens
        are being run by blindly executing given executable
        (one of the reasons why python and java code doesn't work for those),
        which could theoretically create possibility of sending a package with
        arbitrary executable called "???ingen.txt".

        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be run through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 7 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that treats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This means that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. In current version of oioioi checkers and ingens are being run by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be run through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 8
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output-only". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that treats executables marked as "output" in a
        special way as those are from "output" compiler and should be treated as
        program invocation outputs instead of real executables. This means that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. In current version of oioioi checkers and ingens
        are being run by blindly executing given executable
        (one of the reasons why python and java code doesn't work for those),
        which could theoretically create possibility of sending a package with
        arbitrary executable called "???ingen.txt".

        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output" sources.

        Checkers and ingens should probably be run through FileRunners. This
        would both make "output" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 8 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output-only". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that treats executables marked as "output" in a special way as those are from "output" compiler and should be treated as program invocation outputs instead of real executables. This means that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. In current version of oioioi checkers and ingens are being run by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output" sources. Checkers and ingens should probably be run through FileRunners. This would both make "output" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 9
        https://gerrit.sio2project.mimuw.edu.pl/3650

        SIO-2055 Add support for output-only tasks

        Adds new compiler to sioworkers called "output-only". This compiler moves its
        source code argument further as compiled binary, then there is new code in
        executors/common.py that treats executables marked as "output-only" in a
        special way as those are from "output-only" compiler and should be treated as
        program invocation outputs instead of real executables. This means that
        instead of running the executable it is being moved as output file.

        In every of those steps environ has to be filled with proper key value
        pairs used by other parts of code to investigate compilation/execution
        result, even though compilation/execution haven't happened.

        New code in executors/common.py mentioned before affects only task
        solution evaluation. In current version of oioioi checkers and ingens
        are being run by blindly executing given executable
        (one of the reasons why python and java code doesn't work for those),
        which could theoretically create possibility of sending a package with
        arbitrary executable called "???ingen.txt".

        This doesn't happen either way for current version of "oioioi" as
        checkers and ingens sources are being send to compilers prefixed with
        "default-", and no such compiler has been introduced for "output-only" sources.

        Checkers and ingens should probably be run through FileRunners. This
        would both make "output-only" executables fail as there is no FileRunner for
        them and would allow interpreted languages ingens and checkers. However
        such change is not a topic of this ticket, so it is not introduced with
        this commit.

        To test the change reinstallation of sioworkers is advisable as changes
        to "setup.py" don't propagate upon file modification.

        To test with oioioi, every variable in settings that refers to
        compilers/programming languages has to be filled with information about
        "output-only" language and compiler.

        Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Show
        Gerrit Gerrit added a comment - Change sioworkers~master~Id28318b2ae7504fde2156bc1768aa98facdfdb67, patchset 9 https://gerrit.sio2project.mimuw.edu.pl/3650 SIO-2055 Add support for output-only tasks Adds new compiler to sioworkers called "output-only". This compiler moves its source code argument further as compiled binary, then there is new code in executors/common.py that treats executables marked as "output-only" in a special way as those are from "output-only" compiler and should be treated as program invocation outputs instead of real executables. This means that instead of running the executable it is being moved as output file. In every of those steps environ has to be filled with proper key value pairs used by other parts of code to investigate compilation/execution result, even though compilation/execution haven't happened. New code in executors/common.py mentioned before affects only task solution evaluation. In current version of oioioi checkers and ingens are being run by blindly executing given executable (one of the reasons why python and java code doesn't work for those), which could theoretically create possibility of sending a package with arbitrary executable called "???ingen.txt". This doesn't happen either way for current version of "oioioi" as checkers and ingens sources are being send to compilers prefixed with "default-", and no such compiler has been introduced for "output-only" sources. Checkers and ingens should probably be run through FileRunners. This would both make "output-only" executables fail as there is no FileRunner for them and would allow interpreted languages ingens and checkers. However such change is not a topic of this ticket, so it is not introduced with this commit. To test the change reinstallation of sioworkers is advisable as changes to "setup.py" don't propagate upon file modification. To test with oioioi, every variable in settings that refers to compilers/programming languages has to be filled with information about "output-only" language and compiler. Change-Id: Id28318b2ae7504fde2156bc1768aa98facdfdb67
        Hide
        Gerrit Gerrit added a comment -
        Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 1
        https://gerrit.sio2project.mimuw.edu.pl/3704

        SIO-2055 Add support for Output-only

        Adds Output-only to keys in settings. Introduces new meta data key for
        every language: "type". This key can be set to "main" or "extra", the
        later means that the language can only be enabled by listing it on
        language whitelist for certain problem. An only language of this type is
        "Output-only", as it would probably be used quite rarely and enabling it
        on every problem by default might confuse some users (especially
        considering fact, that problem has to be prepared in special way in
        order to be solvable by output-only).

        Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Show
        Gerrit Gerrit added a comment - Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 1 https://gerrit.sio2project.mimuw.edu.pl/3704 SIO-2055 Add support for Output-only Adds Output-only to keys in settings. Introduces new meta data key for every language: "type". This key can be set to "main" or "extra", the later means that the language can only be enabled by listing it on language whitelist for certain problem. An only language of this type is "Output-only", as it would probably be used quite rarely and enabling it on every problem by default might confuse some users (especially considering fact, that problem has to be prepared in special way in order to be solvable by output-only). Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Jakub Wasilewski made changes -
        Affects Version/s TAG 2020/21 Summer Sprint 2 [ 13200 ]
        Jakub Wasilewski made changes -
        Fix Version/s TAG 2020/21 Summer Sprint 2 [ 13200 ]
        Affects Version/s TAG 2020/21 Summer Sprint 2 [ 13200 ]
        Hide
        Gerrit Gerrit added a comment -
        Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 2
        https://gerrit.sio2project.mimuw.edu.pl/3704

        SIO-2055 Add support for Output-only

        Adds Output-only to keys in settings. Introduces new meta data key for
        every language: "type". This key can be set to "main" or "extra", the
        later means that the language can only be enabled by listing it on
        language whitelist for certain problem. An only language of this type is
        "Output-only", as it would probably be used quite rarely and enabling it
        on every problem by default might confuse some users (especially
        considering fact, that problem has to be prepared in special way in
        order to be solvable by output-only).

        Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Show
        Gerrit Gerrit added a comment - Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 2 https://gerrit.sio2project.mimuw.edu.pl/3704 SIO-2055 Add support for Output-only Adds Output-only to keys in settings. Introduces new meta data key for every language: "type". This key can be set to "main" or "extra", the later means that the language can only be enabled by listing it on language whitelist for certain problem. An only language of this type is "Output-only", as it would probably be used quite rarely and enabling it on every problem by default might confuse some users (especially considering fact, that problem has to be prepared in special way in order to be solvable by output-only). Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Hide
        Gerrit Gerrit added a comment -
        Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 3
        https://gerrit.sio2project.mimuw.edu.pl/3704

        SIO-2055 Add support for Output-only

        Adds Output-only to keys in settings. Introduces new meta data key for
        every language: "type". This key can be set to "main" or "extra", the
        later means that the language can only be enabled by listing it on
        language whitelist for certain problem. An only language of this type is
        "Output-only", as it would probably be used quite rarely and enabling it
        on every problem by default might confuse some users (especially
        considering fact, that problem has to be prepared in special way in
        order to be solvable by output-only).

        Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Show
        Gerrit Gerrit added a comment - Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 3 https://gerrit.sio2project.mimuw.edu.pl/3704 SIO-2055 Add support for Output-only Adds Output-only to keys in settings. Introduces new meta data key for every language: "type". This key can be set to "main" or "extra", the later means that the language can only be enabled by listing it on language whitelist for certain problem. An only language of this type is "Output-only", as it would probably be used quite rarely and enabling it on every problem by default might confuse some users (especially considering fact, that problem has to be prepared in special way in order to be solvable by output-only). Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Hide
        Gerrit Gerrit added a comment -
        Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 4
        https://gerrit.sio2project.mimuw.edu.pl/3704

        SIO-2055 Add support for Output-only

        Adds Output-only to keys in settings. Introduces new meta data key for
        every language: "type". This key can be set to "main" or "extra", the
        later means that the language can only be enabled by listing it on
        language whitelist for certain problem. An only language of this type is
        "Output-only", as it would probably be used quite rarely and enabling it
        on every problem by default might confuse some users (especially
        considering fact, that problem has to be prepared in special way in
        order to be solvable by output-only).

        Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Show
        Gerrit Gerrit added a comment - Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 4 https://gerrit.sio2project.mimuw.edu.pl/3704 SIO-2055 Add support for Output-only Adds Output-only to keys in settings. Introduces new meta data key for every language: "type". This key can be set to "main" or "extra", the later means that the language can only be enabled by listing it on language whitelist for certain problem. An only language of this type is "Output-only", as it would probably be used quite rarely and enabling it on every problem by default might confuse some users (especially considering fact, that problem has to be prepared in special way in order to be solvable by output-only). Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Hide
        Gerrit Gerrit added a comment -
        Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 5
        https://gerrit.sio2project.mimuw.edu.pl/3704

        SIO-2055 Add support for Output-only

        Adds Output-only to keys in settings. Introduces new meta data key for
        every language: "type". This key can be set to "main" or "extra", the
        later means that the language can only be enabled by listing it on
        language whitelist for certain problem. An only language of this type is
        "Output-only", as it would probably be used quite rarely and enabling it
        on every problem by default might confuse some users (especially
        considering fact, that problem has to be prepared in special way in
        order to be solvable by output-only).

        Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Show
        Gerrit Gerrit added a comment - Change oioioi~master~I284b16c9bbbd7af021827abea5f08fedbf4f57f5, patchset 5 https://gerrit.sio2project.mimuw.edu.pl/3704 SIO-2055 Add support for Output-only Adds Output-only to keys in settings. Introduces new meta data key for every language: "type". This key can be set to "main" or "extra", the later means that the language can only be enabled by listing it on language whitelist for certain problem. An only language of this type is "Output-only", as it would probably be used quite rarely and enabling it on every problem by default might confuse some users (especially considering fact, that problem has to be prepared in special way in order to be solvable by output-only). Change-Id: I284b16c9bbbd7af021827abea5f08fedbf4f57f5
        Jakub Wasilewski made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Assignee Jakub Wasilewski [ wasyl ] Wojciech Dubiel [ wolf480 ]
        Resolution Fixed [ 1 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        New New Resolved Resolved
        830d 21h 51m 1 Szymon Acedański 2020-04-27 16:28
        Resolved Resolved Reopened Reopened
        1h 28m 1 Michalina Sidor 2020-04-27 17:56
        Reopened Reopened Resolved Resolved
        385d 21h 11m 1 Jakub Wasilewski 2021-05-18 15:08

          People

          • Assignee:
            Wojciech Dubiel
            Reporter:
            Bartosz Kostka
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: