DefangLabs / DefangLabs/defang

OutOfMemory not showing up in logs

Open
#591 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
166
Forks
24
Avg merge
10h 8m
Merged PRs (30d)
33

Description

Screenshot 2024-07-30 at 11 46 07 AM Screenshot 2024-07-30 at 11 46 49 AM

As can be seen, the OutOfMemory did not appear on our logs for portal / playground.

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 the portal/playground logging path and reproduce the OutOfMemory condition shown in the issue screenshots. Identify where that failure is lost, then verify that an OutOfMemory event appears in the portal and playground logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.