P403n1x87/austin-vscode

Issues

• Profiling breaks with error "spawn austin ENOENTaustin process exited with code -4058"

  #63 opened 3 months ago by ckaldemeyer
  3

• Running 'Profile with Austin' command fails without error message, causes script to abort at start

  #62 opened 3 months ago by beerman58
  2

• Code 33

  #64 opened 3 months ago by ayush22jain
  1

• Process exited with code -2

  #61 opened 5 months ago by yeswecan
  2

• Vscode flamegraph different compared to flamegraph.pl

  #58 opened 9 months ago by andresgit
  2

• Line heat color can make lines unreadable on dark themes

  #56 opened 9 months ago by iburakov
  2

• Missing instructions for using austin with sudo through vs code?

  #55 opened 10 months ago by zestysoft
  3

• Unable to launch profiler

  #23 opened 3 years ago by partnerinflight
  15

• Not possible to select conda environment to run with

  #54 opened a year ago by simaosr
  2

• Set environment variables when running Austin task

  #37 opened a year ago by Oblynx
  5

• Issues with launching tasks on Mac

  #50 opened a year ago by juanfcocontreras
  2

• Use memory profiling option

  #39 opened a year ago by cwerner
  1

• austin process exited with code -4058

  #47 opened a year ago by dbookstaber
  2

• Unable to launch profile, austin process exited with code -4058

  #46 opened a year ago by CamilleHamon
  10

• austin: unrecognized option '--pipe'

  #45 opened a year ago by schodge
  2

• Space in path problem

  #42 opened a year ago by francescobodria
  3

• Color Highlighting

  #43 opened a year ago by francescobodria
  2

• Add MacOS instructions for modifying `sudoers`

  #41 opened a year ago by bgyarfas
  1

• Bug: Austin fails on pshell when executable path is a string

  #40 opened 2 years ago by LiquidPulsar
  1

• exited with code 127 Error, possible shell config issue?

  #34 opened 2 years ago by k-a-mendoza
  2

• Respect active environment

  #38 opened 2 years ago by cwerner
  2

• Improve sample loading time

  #36 opened 2 years ago by Al12rs
  4

• tasks.json not accepting variable replacement

  #35 opened 2 years ago by tjdcs
  7

• Live updates?

  #30 opened 2 years ago by leokleingmx
  1

• Can jupyter notebook cells be profiled?

  #25 opened 3 years ago by matifali
  1

• Trying to run pytest using Austin in VS code.

  #24 opened 2 years ago by hrshdhgd
  11

• bundle extension

  #17 opened 2 years ago by iynehz
  1

• Flamegraph not displaying properly, certain parts not clickable, displaying NaNs in sidebar

  #32 opened 2 years ago by sgbaird
  3

• command not recognized when using conda environment in Windows

  #20 opened 2 years ago by sgbaird
  3

• Flame graph view not loading in 0.10.6

  #29 opened 2 years ago by P403n1x87
  1

• Flame Graph Panel not showing once extension is loaded

  #28 opened 2 years ago by tonybaloney
  0

• Load stats crashes when flame graph view not showing

  #26 opened 2 years ago by tonybaloney
  0

• Austin not running file correctly if there is whitespace in the filepath or path to Python executable

  #22 opened 3 years ago by LiquidPulsar
  0

• austin process exited with code 127

  #21 opened 3 years ago by cyraid
  5

• Task doesn't start in correct working directory

  #19 opened 3 years ago by othi
  3

• flame graph does not show

  #15 opened 3 years ago by iynehz
  9

• doesn't work on my setup

  #14 opened 3 years ago by xinstein
  2

• Please add a license

  #13 opened 3 years ago by iynehz
  2

• Fails to launch and closes window

  #2 opened 3 years ago by tonybaloney
  3

• Poor test coverage

  #12 opened 3 years ago by P403n1x87
  0

• No FlameGraph Visualisation

  #11 opened 3 years ago by isvoboda
  3

• Austin path is defaulting to ""

  #7 opened 3 years ago by tonybaloney
  0

• Run Austin from a Task

  #4 opened 3 years ago by tonybaloney
  1