TritonDataCenter node-debug-school issues

TritonDataCenter / node-debug-school

nodeschool curriculum for debugging Node.js

MIT License

48 stars 9 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

fixes #17 Incorrect platform compatibility check

#18 rjloura closed 6 years ago
4
Incorrect platform compatibility check

#17 rjloura closed 6 years ago
0
Support for container-native Linux on Triton

#16 misterbisson opened 9 years ago
0
Fix incorrect solution check and add clarity to incorrect solution output.

#15 richardkiene closed 9 years ago
3
Display hint when GENERATE CORE WHEN AN APP CRASHES doesn't abort

#14 misterdjules opened 10 years ago
0
monkey-patch coreadm to prevent invalid patterns

#13 misterdjules closed 10 years ago
1
Send changes made to workshopper upstream

#12 misterdjules opened 10 years ago
0
dumpCore does not clean changes made to coreadm

#11 misterdjules opened 10 years ago
0
Mention other resources on production debugging

#10 misterdjules opened 10 years ago
1
coreadm not usable anymore when a given solution script is checked

#9 misterdjules closed 10 years ago
5
Implement basic analytics

#8 misterdjules opened 10 years ago
0
Do not detect if platform is supported every time node-debug-school is started

#7 misterdjules opened 10 years ago
1
Display more helpful message if platform is not supported

#6 misterdjules closed 10 years ago
0
More precise hints when verifying solution for GENERATE CORE WHEN AN APP CRASHES

#5 misterdjules opened 10 years ago
0
node-debug-school help is not correct for `verify` and `run` subcommands

#4 misterdjules opened 10 years ago
0
ulimit -c 0 in generate_core_when_an_app_crashes doesn't prevent submissions to generate core files

#3 misterdjules closed 10 years ago
1
core files generation is too slow

#2 misterdjules closed 10 years ago
0
Initial implementation

#1 tjfontaine closed 10 years ago
1