3 ms·

Since when dumping out stacktrace and surrounding source code and env is OK for the world to see?

• grenoire 7y ago
  "You're seeing this error because you use Rack::ShowExceptions." Seems like somebody forgot to configure that...
  • deleted 7y ago
    [deleted]
• philwelch 7y ago
  [deleted]
  • ewalk153 7y ago
    You can see in the stack trace that it’s using the cuba [1] framework. [1] https://github.com/soveran/cuba https://github.com/soveran/cuba
    • deleted 7y ago
      [deleted]
• buboard 7y ago
  tbf , they do dump the rest of the source code too https://github.com/antirez/redis-io https://github.com/antirez/redis-io
• ldng 7y ago
  Since it might not really need to hide anything ?
  • ldng 7y ago
    Thanks for the argument-less down vote but it still is a legitimate question. I did not see the stackstrace. But then again, the site seeming relatively static/read-only from an outsider perspective, the environment variable might not contain any secret or password. Did someone see actual secrets ?
    • jve 7y ago
      Nop, (luckily) no secrets. The stack was fairly deep actually. But I had no interest to preserve it.
      • antirez 7y ago
        That's just the Redis client call stack, once the connection failed.
• lkbm 7y ago
  Seems like it doesn't matter since the website source is open source: https://github.com/antirez/redis-io https://github.com/antirez/redis-io EDIT: I guess env could matter.
• antirez 7y ago
  We don't have anything to hide and having the error apparent leads to faster resolution. There are at least two other people other than me having access to the VM, so that if I sleep and they see a problem, they react. This way is simpler.