-
Notifications
You must be signed in to change notification settings - Fork 31
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
ACNA-882 - Rewriting files during app run is error prone, and leads to unexpected issues #309
Conversation
…pected issues 1. during --verbose, java version is not shown since that output is to stderr (and we use stdout). fixed. 2. 100% test coverage
Codecov Report
@@ Coverage Diff @@
## master #309 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 27 29 +2
Lines 1259 1255 -4
Branches 219 206 -13
=========================================
- Hits 1259 1255 -4
Continue to review full report at Codecov.
|
I find this potentially more confusing. Now I don't have a .vscode/launch.json and then I do, and then I don't ... Also, with .env file now in dist/ ... we have one which is a copy of ../.env when run without --local, and one with ... can we just keep a local.env and prod.env in the dist/ folder instead? |
I didn't change the existing functionality, so this behaviour is consistent with the previous behaviour. Not sure the rationale for this functionality.
Not sure I follow exactly. When you run with |
Windows 10 manual tests have been done (via a local patch, see Description), and local debugging etc works. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One inline question about the stop log arg.
Didn't tested, just looked at the code for now, but this looks mostly fine to me.
I agree with @purplecabbage about the vscode file, that it should be generated via generator-aio-app (on init), but I think this could be addressed in another PR
About the dist/.env discussion, I guess one potential enhancement would be, if possible, to pass wskdebug vars via environment instead of dist/.env
, so that we can rename dist/.env
to dist/.env.local
(makes the intent clearer for advanced devs looking at dist/
) and only have it generated on --local
. But again not sure if it's possible or should be done as part of this PR
Also thanks for the extra refactoring and cleanup work !
I left this precisely for another PR, since I saw that comment somewhere about moving to the generator eventually.
We could pass it in as env vars instead of dist/.env, but I'm not sure what the advantage is since dist/.env is functionally equivalent and cleaner. We can rename dist/.env to anything so that is not a problem in renaming it. |
I meant to limit the cases where we generate the extra file, but ok might be more confusing to have multiple means of setting env variables indeed. Maybe we can add some comments in the generated .env instead ? |
Ok I think I get what you mean Moritz.
I will keep the existing |
ok agree to do this in incremental steps 🙂 |
…se dist/.env.local (file rename, with comments)
Travis-CI builds have stopped on this org. Migrating to Github Actions in another PR, and when that is integrated, we can merge it into this PR. |
Fixes #275
How Has This Been Tested?
aio app run --local --verbose
(openwhisk) #304 via re-fix: add new Windows docker.exe location apache/openwhisk#5021)Types of changes
Checklist: