Closed eladb closed 1 week ago
Thanks for opening this pull request! :tada: Please consult the contributing guidelines for details on how to contribute to this project. If you need any assistence, don't hesitate to ping the relevant owner over Slack.
Topic | Owner |
---|---|
Wing SDK and utility APIs | @chriscbr |
Wing Console | @ainvoner , @skyrpex , @polamoros |
JSON, structs, primitives and collections | @hasanaburayyan |
Platforms and plugins | @hasanaburayyan |
Frontend resources (website, react, etc) | @tsuf239 |
Language design | @chriscbr |
VSCode extension and language server | @markmcculloh |
Compiler architecture, inflights, lifting | @yoav-steinberg |
Wing Testing Framework | @tsuf239 |
Wing CLI | @markmcculloh |
Build system, dev environment, releases | @markmcculloh |
Library Ecosystem | @chriscbr |
Documentation | @hasanaburayyan |
SDK test suite | @tsuf239 |
Examples | @hasanaburayyan |
Wing Playground | @eladcon |
Console preview environment is available at https://wing-console-pr-6408.fly.dev :rocket:
Self-mutation has run twice in a row. There may be a something non-deterministic in the build or test process. Check the last mutation commit (7f73b9798a13a042fa8bf7141edc686174d287c8) for suspicious changes. This is typically caused by:
@MarkMcCulloh ready for review
@eladb Hrm - it seems like errors that start from outside of the the unit tests aren't getting printed anymore, can we fix this?
Before:
After:
Thanks for contributing, @eladb! This PR will now be added to the merge queue, or immediately merged if eladb/container-logs
is up-to-date with main
and the queue is empty.
Congrats! :rocket: This was released in Wing 0.73.30.
Container improvements
Revisit how we are running containers in
sim.Container
to improve robustness and capture logs from docker build/pull commands and from running containers.To do that we've changed how container lifecycle is managed by running it without
--detach
and monitoring the child process for exit codes, errors and stdio capture.Simulator stability improvements
Additionally, this fixes a few long standing issues in the simulator which caused it to hang when one of the resources failed to start (e.g. due to unresolvable token). To fix this, we track failures and if there were any failing resources, we stop all the started resources and throw an error. Additionally, in the CLI we needed to catch this error, stop the spinner and bail out from the test execution routine. I believe this fixes #6052 and #5426.
Logging improvements
Add some initial support for log levels, because, come on, currently errors emitted from the simulator or resources are hidden by default because they are treated as "verbose". This includes the relevant Console fixes.
Tweak a little how logs are displayed when
DEBUG=1
so that log entries are separated by a newline and removed the indentation of the first line (basically like jest/vitest is doing).Other improvements
Hide the
cloud.Endpoint
nodes from the graph because it was a mistake (mine) to suggest to show them.Checklist
pr/e2e-full
label if this feature requires end-to-end testingBy submitting this pull request, I confirm that my contribution is made under the terms of the Wing Cloud Contribution License.