Closed burnerlee closed 3 years ago
@Ram81 ping for review
@Ram81 all requested changes made except https://github.com/Cloud-CV/evalai-cli/pull/315#discussion_r565924669. Would wait for your reply on that
@Ram81 added the required check as well along with the *
@Ram81 changes made
@burnerlee minor comments. Rest of it LGTM, nice work
Thank you ❤️
@Ram81 @RishabhJain2018, this PR and the one on cyclic-imports are almost ready to be merged. Could you please assign me some issues on these projects or any other? Maybe I can implement some feature on any of those
@burnerlee can you share a screenshot with sample submission with meta attributes input?
@RishabhJain2018 PR LGTM, can you take a look.
Can we please fix the travis build?
@burnerlee can you share a screenshot with sample submission with meta attributes input?
https://github.com/Cloud-CV/evalai-cli/pull/315#issuecomment-767709514 already attached this screenshot, if you're asking about this @Ram81
@burnerlee can you fix the failing tests in travis build.
You might've to incorporate changes in tests for submission meta attributes input in evalai submit
command
Oh, sure. I'll just check it out
@Ram81 @RishabhJain2018, I ran setup.py in my local after installing all the dependencies, but could not understand the error behind the failure of these 5 tests. Could you please give me an insight on this
For the tests with evalai submit
command we passN/y
for submission meta attributes input but after your change this input is accepted twice. So these tests might need an additional N/y
as input and if input is y
you might also have to pass values for metadata attributes. Let me know if you have any more questions
So for the tests with N
as input you'll have to replace it with N\nN
and for tests with Y
as input you'll have to pass Y\nvalue1\nvalue2\nvalue3\nvalue4
then again Y/N
for new added meta attributes.
@burnerlee Any update on this? cc: @Ram81
Yeah, I'll update this today. Have my last exam today. Was preparing for it
okay, thanks for letting us know.
@Ram81 the requests for the tests are made to the eval server hosted. Could you please tell me the submission_meta_attributes for the test? challenge id is 1, phase id is 2, ["1", "phase", "2", "submit", "--file", "test_file.txt"]
. I would need to add the values to enter for the attributes accordingly
@burnerlee those are not actual requests I think. The responses for those requests are being mocked, see the tests in this PR for reference
@Ram81, after consoling some logs I actually understood the problem. The changes for adding \nN
have to be made. Along with that, I was facing another error. i.e. In the challenge submission, I make a request to the server for fetching the attributes for the challenge phase. This is causing errors while I am testing and needs to be handled in the same way as tests are written, maybe hardcoded. I'll now see how to handle this in testing as this wouldn't be an actual request ig
@Ram81, when the get_meta_attributes function would be called in testing, I think it would be
@Ram81, after consoling some logs I actually understood the problem. The changes for adding
\nN
have to be made. Along with that, I was facing another error. i.e. In the challenge submission, I make a request to the server for fetching the attributes for the challenge phase. This is causing errors while I am testing and needs to be handled in the same way as tests are written, maybe hardcoded. I'll now see how to handle this in testing as this wouldn't be an actual request ig
Yeah, understood how everything was working. Works fine now
@RishabhJain2018 @Ram81 build fixed. Please review
@RishabhJain2018 made all the requested changes and tasks
Fixes #305 by adding a feature to allow users to provide metadata along with making submissions from the cli. When a user makes a submission, a request is made to the server to check if any submission_meta_attributes are available for the corresponding challenge_phase. If any attributes are found, a prompt would appear asking the user if he/she wants to submit the values. The user can agree to submit these values and then fill in their corresponding choice for each field prompted. Enough instructions and choices are provided to the user through the prompts too