Hari Bhaskaran

Results 9 comments of Hari Bhaskaran

![image](https://user-images.githubusercontent.com/952886/47866122-2689fb80-ddbb-11e8-8e6f-825dac27811a.png) I have to periodically kill the language server and live with missing features with vscode. Is there anything I can help with? what logs/traces can I extract the next...

@ramya-rao-a , it does seem to work after I updated the language server. I did not remember that language-server was installed via a separate `go get` command. Sorry about this....

(Not an expert nor repo-contributor yet, but working on similar problems. this is my 2 cents) 1. No, you can't run untrusted code without some serious mitigations. 2. As far...

Here is some more info from my (probably misguided) attempt to run it with gdb [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff6a9f700 (LWP 294882)]...

Well, that was quick.... I discovered the segfault was caused by my using a path that had two components - "fdbtest02/testing/" - just putting "fdbtest03" seems to have created at...

Error seem to be coming from the message - [invalid URL prefix](https://github.com/apple/foundationdb/search?q=%22invalid+URL+prefix%22&type=code) and it appears as per code that can only happen if BUILD_AZURE_BACKUP is not defined. Quite possible some...

It seems not all code is enabled - there should ideally be a `#define` [here](https://github.com/apple/foundationdb/blob/e35633149cf19df99ba644143379557a8aec0c30/fdbclient/BackupContainer.actor.cpp#L349). I will make that change and see if it makes progress.

It seems the Segfault is caused at [BackupContainerAzureBlobStore.actor.cpp:336](https://github.com/apple/foundationdb/blob/main/fdbclient/azure_backup/BackupContainerAzureBlobStore.actor.cpp#L336) when the container already exists. However, the trace is well inside azure::storage_lite::CurlEasyRequest::perform . I also seeing other folks reporting similar bugs https://github.com/Azure/azure-storage-cpplite/issues/87...

@sfc-gh-clin - I still see a repeat of the issue in a different environment. I am still debugging.