Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / maelstrom-software/maelstrom issues and pull requests

#46 - Worker can theoretically deadlock reporting large execution error

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#46 - Worker can theoretically deadlock reporting large execution error

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#46 - Worker can theoretically deadlock reporting large execution error

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#45 - Get the worker dummy process to be cloned with CLONE_VM

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker, optimization

#45 - Get the worker dummy process to be cloned with CLONE_VM

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker, optimization

#45 - Get the worker dummy process to be cloned with CLONE_VM

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker, optimization

#45 - Get the worker dummy process to be cloned with CLONE_VM

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker, optimization

#44 - Wrap up our uses of syscalls in the worker into one crate

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#44 - Wrap up our uses of syscalls in the worker into one crate

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#44 - Wrap up our uses of syscalls in the worker into one crate

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#44 - Wrap up our uses of syscalls in the worker into one crate

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#43 - Come up with a story about jobs that dump core

Issue - State: open - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom, job, maelstrom-run

#43 - Come up with a story about jobs that dump core

Issue - State: open - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom, job, maelstrom-run

#43 - Come up with a story about jobs that dump core

Issue - State: open - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom, job, maelstrom-run

#43 - Come up with a story about jobs that dump core

Issue - State: open - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom, job, maelstrom-run

#42 - cargo-metest should support color cargo output if stderr is a TTY

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#42 - cargo-metest should support color cargo output if stderr is a TTY

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#42 - cargo-metest should support color cargo output if stderr is a TTY

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#42 - cargo-metest should support color cargo output if stderr is a TTY

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#42 - cargo-metest should support color cargo output if stderr is a TTY

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#41 - cargo-metest should forward environment variables to workers

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#41 - cargo-metest should forward environment variables to workers

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#41 - cargo-metest should forward environment variables to workers

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#41 - cargo-metest should forward environment variables to workers

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#41 - cargo-metest should forward environment variables to workers

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#40 - cargo-metest should handle stdout being piped

Issue - State: closed - Opened by bobbobbio about 1 year ago - 1 comment
Labels: cargo-maelstrom

#39 - Have cargo-metest use artifacts correctly

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#39 - Have cargo-metest use artifacts correctly

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#39 - Have cargo-metest use artifacts correctly

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#39 - Have cargo-metest use artifacts correctly

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#39 - Have cargo-metest use artifacts correctly

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#38 - Provide a scheduler that is user-aware

Issue - State: open - Opened by nfachan about 1 year ago

#38 - Provide a scheduler that is user-aware

Issue - State: open - Opened by nfachan about 1 year ago

#38 - Provide a scheduler that is user-aware

Issue - State: open - Opened by nfachan about 1 year ago

#38 - Provide a scheduler that is user-aware

Issue - State: open - Opened by nfachan about 1 year ago

#38 - Provide a scheduler that is user-aware

Issue - State: open - Opened by nfachan about 1 year ago

#37 - Provide a way for jobs to have temporary, special, and output directories

Issue - State: closed - Opened by nfachan about 1 year ago - 2 comments
Labels: job

#37 - Provide a way for jobs to have temporary, special, and output directories

Issue - State: closed - Opened by nfachan about 1 year ago - 2 comments
Labels: job

#37 - Provide a way for jobs to have temporary, special, and output directories

Issue - State: closed - Opened by nfachan about 1 year ago - 2 comments
Labels: job

#37 - Provide a way for jobs to have temporary, special, and output directories

Issue - State: closed - Opened by nfachan about 1 year ago - 2 comments
Labels: job

#37 - Provide a way for jobs to have temporary, special, and output directories

Issue - State: closed - Opened by nfachan about 1 year ago - 2 comments
Labels: job

#36 - Worker needs to be containerized

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#36 - Worker needs to be containerized

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#36 - Worker needs to be containerized

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#36 - Worker needs to be containerized

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: worker

#35 - Provide a status bar for outstanding jobs

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#35 - Provide a status bar for outstanding jobs

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#35 - Provide a status bar for outstanding jobs

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#35 - Provide a status bar for outstanding jobs

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#34 - Provide a status bar for artifact upload when running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom

#34 - Provide a status bar for artifact upload when running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom

#34 - Provide a status bar for artifact upload when running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom

#34 - Provide a status bar for artifact upload when running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom

#34 - Provide a status bar for artifact upload when running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom

#33 - Get unit tests the "right" way

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#33 - Get unit tests the "right" way

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#33 - Get unit tests the "right" way

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#33 - Get unit tests the "right" way

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#32 - Provide status when building artifacts for tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#32 - Provide status when building artifacts for tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#32 - Provide status when building artifacts for tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#32 - Provide status when building artifacts for tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#31 - Queue tests as soon as associated artifacts are built

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#31 - Queue tests as soon as associated artifacts are built

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#31 - Queue tests as soon as associated artifacts are built

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#31 - Queue tests as soon as associated artifacts are built

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#30 - Look at Rust test runners and decide what features we should add

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom, research

#30 - Look at Rust test runners and decide what features we should add

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom, research

#30 - Look at Rust test runners and decide what features we should add

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom, research

#30 - Look at Rust test runners and decide what features we should add

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom, research

#29 - Print summary for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#29 - Print summary for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#29 - Print summary for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#29 - Print summary for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#29 - Print summary for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: cargo-maelstrom

#28 - Have a quiet mode for running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#28 - Have a quiet mode for running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#28 - Have a quiet mode for running unit tests

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#27 - Print package or binary name for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#27 - Print package or binary name for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#27 - Print package or binary name for unit tests

Issue - State: closed - Opened by nfachan about 1 year ago - 1 comment
Labels: cargo-maelstrom

#26 - Provide a way for the client to limit the size of stdout and stderr

Issue - State: open - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom, job, maelstrom-run

#26 - Provide a way for the client to limit the size of stdout and stderr

Issue - State: open - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom, job, maelstrom-run

#26 - Provide a way for the client to limit the size of stdout and stderr

Issue - State: open - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom, job, maelstrom-run

#25 - Support arbitrarily large stdout/stderr output from jobs

Issue - State: open - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom, job, maelstrom-run

#25 - Support arbitrarily large stdout/stderr output from jobs

Issue - State: open - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom, job, maelstrom-run

#25 - Support arbitrarily large stdout/stderr output from jobs

Issue - State: open - Opened by nfachan about 1 year ago
Labels: enhancement, cargo-maelstrom, job, maelstrom-run

#23 - Should the worker reconnect if it loses contact with the broker?

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: worker

#23 - Should the worker reconnect if it loses contact with the broker?

Issue - State: open - Opened by nfachan about 1 year ago
Labels: worker

#22 - Provide option for running broker and worker as daemons

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: enhancement, worker

#22 - Provide option for running broker and worker as daemons

Issue - State: closed - Opened by nfachan about 1 year ago
Labels: enhancement, worker

#21 - Decide on a trust strategy between various processes

Issue - State: open - Opened by nfachan about 1 year ago

#21 - Decide on a trust strategy between various processes

Issue - State: open - Opened by nfachan about 1 year ago