Ловить сигналы ошибок с принтера
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by identifying how the C# application submits print jobs and whether the printer integration exposes jam or other error status. Define the terminal-blocking and queue behavior, then verify it with printer-error scenarios.
Written by the indexing model from the issue text.
Description
Issue open by Mark Arzangulyan via telegram message.
Надо научиться ловить сигнал замятия (или других ошибок) с принтера и блочить терминал на это время, чтобы очередь не забивалась
- Dominant language
- C#
- Stars
- 14
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from profcomff/print-winapp
-
bug :lady_beetle:
Difficulty 4/5 3-5 days Newbie friendliness 25/100
profcomff/print-winapp#62 ·
-
new feature :new:
Difficulty 4/5 3-5 days Newbie friendliness 35/100
profcomff/print-winapp#55 · 2 comments ·
-
Error Недостаточно ресурсов памяти для обработки этой команды.May be free again @mrerro claimed this 1254 days ago, and no pull request is open. Openbug :lady_beetle:
profcomff/print-winapp#53 · 6 comments · 1 assignee ·
-
сделать алерт на конец бумаги принтераMay be free again @ArseniyMem claimed this 1185 days ago, and no pull request is open. Open
profcomff/print-winapp#51 · 1 comment · 1 assignee ·
-
good first issue :baby: new feature :new:
Difficulty 5/5 Over a week Newbie friendliness 25/100
profcomff/print-winapp#47 · 5 comments ·
All issues in profcomff/print-winapp
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/clickhouse-cs#639 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
ifpebj-ti/controle-acesso-veiculos#377 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Money ExploitsOpenS: Untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
project-wayfarer/wayfarer-14#1628 ·
Maintainers usually reply within 3 days
-
:watch: Not Triaged dotnet-target-version
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day