Skip to content
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

shim: organize code to different modules #185

Merged
merged 2 commits into from
Sep 20, 2024
Merged

shim: organize code to different modules #185

merged 2 commits into from
Sep 20, 2024

Conversation

Mossaka
Copy link
Member

@Mossaka Mossaka commented Sep 10, 2024

this commit organized code to different modules:

  • constants: to handling constants across entire crate
  • engine: the execution engine
  • source: manages application sources
  • stdio_hook: a trigger hook for stdio
  • trigger: manages spin triggers
  • utils: utility functions

it also removes ResolvedAppSource as it's not needed

Copy link
Collaborator

@kate-goldenring kate-goldenring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for this reorganization

@Mossaka
Copy link
Member Author

Mossaka commented Sep 13, 2024

Containerd logs for the failured spin wasm workloads:

time="2024-09-12T17:36:18.377934221Z" level=error msg="run_wasi ERROR >>>  failed: Unable to listen on 0.0.0.0:80

Caused by:
    Address in use (os error 98)"

@kate-goldenring
Copy link
Collaborator

@Mossaka I wonder if tests that used to run sequentially are now running in parallel or if this is a race case. In the integration tests, maybe we should randomize the host port for port forwarding rather than keeping it always at 8082

@Mossaka
Copy link
Member Author

Mossaka commented Sep 13, 2024

In the integration tests, maybe we should randomize the host port for port forwarding rather than keeping it always at 8082

That might be a good idea in general, but it won't help in this case, cuz I can reproduce it in my local running ctr run with one instance.

Mossaka and others added 2 commits September 19, 2024 23:27
this commit organized code to different modules:
- constants: to handling constants across entire crate
- engine: the execution engine
- source: manages application sources
- stdio_hook: a trigger hook for stdio
- trigger: manages spin triggers
- utils: utility functions

it also removes ResolvedAppSource as it's not needed

Signed-off-by: jiaxiao zhou <[email protected]>
@Mossaka
Copy link
Member Author

Mossaka commented Sep 19, 2024

#185 (comment)

is fixed by 79d54ba

@Mossaka Mossaka merged commit aed25ea into main Sep 20, 2024
8 checks passed
@Mossaka Mossaka deleted the refactoring branch September 20, 2024 00:38
@Mossaka Mossaka restored the refactoring branch September 20, 2024 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants