iamcco/coc-flutter

Too many dev logs leads to VNR(vim not response)

Open

#139 opened on Sep 16, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (36 forks)github user discovery
enhancementgood first issue

Repository metrics

Stars
 (479 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Describe the bug Too many dev logs leads to VNR(vim not response).

To Reproduce Steps to reproduce the behavior:

  1. flutter.run
  2. flutter app produces too many logs.
  3. not run flutter.dev.clearlog
  4. wait for a while until VNR.

Expected behavior Automatic clear overflowed logs (adding a max limit setting)

Desktop (please complete the following information):

  • OS: MacOS
  • Neovim:
  • (Neo)vim version: 0.5

Contributor guide

Research direction
Investigate the logging mechanism in the codebase, identify where logs are generated, and add a configurable max limit to prevent buffer overflow that causes Vim not responding.
Tech stack
typescript
Domain
devtools
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70