Closed promehul closed 5 years ago
Tests on this PR failed with error messages "no environment variables set". I am not able to get what I did wrong !!
Then merge it if you find it correct!!
I don't think this is a good idea of providing the service name as a default. It should be localhost.
Your service name should be overriden by environment variables passed into your docker service.
Closing this.
@achillesrasquinha please check now if its what you asked for.
@promehul are you still facing that refresh problem - pipeline not saving in db on refreshing?
Its getting saved in db but it is not getting displayed ON REFRESH !! @rupav
just created a pipeline named 'pilot', logged out, logged in back pipeline is still present. Refreshed, then logged in, and again found the pipeline correctly.
Please check again, and let us know. Install a screen recorder (like 'peek'), to record the flow of the app, and thus the error you are facing, post the gif here when you are done.
@rupav are you running it on docker or using get_candis script? I followed the same steps that you followed .
One error found in the flow so far, forgot password
functionality. That's a seperate issue, because of Gmail auth of our mail server. Except this, try finding other issues in docker setup @promehul .
I am running it on docker @promehul using your changes.
If it is running all fine, then please merge my PR.
@rupav I did this
You have to open the existing file, not creating new. How can it create new with the same name, rather try opening the existing file. All works fine then.
This is the correct behavior of the app, if pipe with same name exists, you cant create one, and thus the warning.
try clicking on 'open' instead of 'new' after refreshing the browser, once you have created 'qwerty' pipe.
Thanks @rupav
This has been open for 9 days. Any follow up? @rupav
Did you @promehul try running the pipeline on docker? Are you able to populate the 'file' (by creating new file) with CEL files? If so, please explain how so. Refer Readme GIF, for checking how to run the pipeline.
Explanation About What Code Achieves:
Screenshots/GIFs:
Steps To Test:
-Run it.
TODOs: