Closed navkuun closed 1 month ago
Hi @navkuun !
Thanks for the issue report. My guess is the error here is due to inspect view
trying to read C:/Users/N%k/Documents/...
whereas your logs seem to be located at C:/Users/Nk/Documents/...
. (notice the stray %
symbol).
Afaict the view command can see your logs, or you would be hitting this exit point here.
But it looks like when you actually make a get request and it comes into handle_log
, the path has become malformed somehow on the way to the logs being read. It's possible that some of the parsing steps here could have inadvertently caused this, but more details would be useful for us to narrow it down.
C:/Users/Nk/
, C:/Users/N%k/
, or C:/Users/N%K/
? (all three of which seem to be present in the logs, which is perplexing.). Sharing the true full path would be helpful so we can debug this on our end.log_dir
manually to inspect, do you observe the same behaviour?self.path
at the entrance to the function?
I was trying to run the first security guide example and the evaluation runs fine and the /logs file shows up and the contents of the file are as it should be.
Here's the code from the example that I used
However when I try to
inspect view
I get the following error
It says it's a file not found error but the file is clearly there![image](https://github.com/UKGovernmentBEIS/inspect_ai/assets/63613042/8a6ecad7-c771-40eb-b532-cc7d3b3a083f)
Using Python 3.12.2. The VScode extension also shows up when I run 'inspect view' in the CLI but it shows up as a blank new tab.
Would appreciate some help with this.