Skip to content

Stream output from judger #88

@Eason0729

Description

@Eason0729

Currently, we wait application(user submitted program) to end before sending any byte to client(for convenience).

This issue contains two parts to fix:

  • rework assert stage(module: judger/src/language/stage) to accept stream and possibly return WA early.
  • rework output monitor(judger/src/sandbox/monitor/output.rs)
    we should use pipe(2) instead of duplex, which we can ensure no intermediate copy and thus ensure output limit isn't enforced too early or late.

This won't affect application's usability. However, use of pipe(2) should be tested to prove its effectiveness.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions