Can't update problem status with [WARN] Failed to get memory percentile.
See original GitHub issue🐛 Bug Report
When I submitted the answer and get accepted, the last line of the response was [WARN] Failed to get memory percentile.
And with this warning, the problem status cannot be updated, even though my answer was accepted.
To Reproduce
Just submit the question.
Expected behavior
Problem status not updated
Your Environment
- os: Windows 10, 1809
- extension settings:
- nodejs version: v10.15.2
- vscode version: 1.32.1
- extension version: 0.12.0
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Go expvar does not work on metrics containing / #1060 - GitHub
I have a lot of metrics on the form app/foo/bar , which are not imported into the datadog charts. Examples of metrics: ubuntu@35:~$...
Read more >How to chart performance with VM insights - Azure Monitor
Choose Virtual Machines in the Solutions section. Select the Performance tab. VM insights Performance Top N List view. On the Top N Charts...
Read more >Use percentiles to analyze application performance - Dynatrace
Learn how percentiles are better than averages in understanding the real performance characteristics of your application.
Read more >Troubleshoot the Monitoring agent | Google Cloud
This message indicates that the status update of memory throttling fails once. It is normally harmless, but could be a sign that the...
Read more >Fix common cluster issues | Elasticsearch Guide [8.5] | Elastic
This error indicates a data node is critically low on disk space and has reached the flood-stage disk usage watermark. Circuit breaker errors:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tomleung1996 Yes, I failed to trigger the warning.
After some efforts of investigation, I finally get to know that it is not the problem with skygragon’s leetcode-cli, but @jdneo 's forked version.
There’s
And at the last line of function there is:
Originally, the former code logic was wrapped in a callback, so when
log.warn
makes the callback returns, the latter code can still be executed.Yet now the former code is exposed in the same level as the latter, so when the
return
is met, the latter code is skipped, resulting in the local cache not updated.If you delete the cache in
$HOME/.lc
, the behavior may return right.Cool!