msgbyte / msgbyte/tianji

Bug - monitor-get/monitor-delete Erroring with NOT_FOUND

Open
#130 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.1k
Forks
194
Avg merge
18m
Merged PRs (30d)
3

Description

Description

The following routes always return NOT_FOUND even with a valid monitorId that can be found at /workspace/:workspaceId/monitor/all:

  • GET /workspace/:workspaceId/monitor/:monitorId
  • DELETE /workspace/:workspaceId/monitor/:monitorId
{"message":"Not found","code":"NOT_FOUND"}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing GET /workspace/:workspaceId/monitor/:monitorId and DELETE /workspace/:workspaceId/monitor/:monitorId, then compare their monitor lookup with /workspace/:workspaceId/monitor/all. Confirm that valid monitorIds found by the all-monitors route can be retrieved and deleted without a NOT_FOUND response.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.