https://serverless-stack.com/ logo
Join Slack
Powered by
hi there, who knows how to hide grey logs during d...
# help
a
hi there, who knows how to hide grey logs during debugging?
r
What do you mean by grey logs?
a
when I’m running in debug mode, so it proxied through my machine, when I’m scaniing dynamo table I can see some logs that log all data i scanned
and it messed with my own logs so i can’t find them
they are in grey color in my console
r
Not sure I follow but setting
Copy code
"skipFiles": ["<node_internals>/**"],
in launch.json prevents debug of node.js internal processes, maybe can use something similar
a
hmm….. what is it launch.json? where it is?
r
Are you using Visual Studio Code?
a
aaaa no
intelij webstorm
r
ah, sorry, It's the debug config file for VSC. maybe something similar in webstorm
a
ok, I’ll search
r
👍🏻
a
but it doesn’t look like internal nodejs logs
because for the rest of libs i don’t have this
only for ss
only from sst
so I beleive it is sst config
r
yeah, was thinking you could apply the same principle for the files that were generating the logs
f
@Artem Kalantai are you running 
sst start
with 
-v
flag? Or have the 
DEBUG
environment variable set?
a
let me check
looks like both NO
Copy code
"start": "sst start",
echo $DEBUG is empty
f
hmm.. can u share a screenshot with these grey logs?
a
moment
so this is part of the response when I’m scan dynamo
maybe it is aws-sdk config?
f
Oh this is the Lambda response i think.. which version of SST r u using?
a
Copy code
"@serverless-stack/cli": "0.9.16",
too old?
f
Yeah try the latest release. We now truncate the Lambda response printed to the terminal.
a
thanks
f
Let me know if it looks better 👌
a
yea
i updated to
Copy code
0.9.18
it doesn’t help
still has those log
f
Can you try 
0.18.0
a
i'll try tomorrow
dissapeared, thanks
Open in Slack
PreviousNext
Powered by