Visual Studio Code - Blank Window no border - visual-studio-code

It first started with just a blank window with some purple marking at the bottom.
I have used it for a few years and updated regularly and all of a sudden this happened when i start visual studio code. Never had any problems before.
Empty Window Purple
I have tried
--disable-gpu
--disable-extensions
I have tried other projects that i have and i have tried to open just single files outside of projects..
I also installed Insider and same thing with that..
No difference
I have uninstalled twice and the second time i deleted all the left over folders too before installing again and when i started it, and after that it was just a complete blank window instead.
Empty Window
I tested to run verbose but i dont understand the info it gives..
[main 2021-07-13T14:16:34.370Z] Starting VS Code
[main 2021-07-13T14:16:34.371Z] from: r:\appdata\local\Programs\Microsoft VS Code\resources\app
[main 2021-07-13T14:16:34.371Z] args: {
_: [],
diff: false,
add: false,
goto: false,
'new-window': false,
'reuse-window': false,
wait: false,
help: false,
'list-extensions': false,
'show-versions': false,
version: false,
verbose: true,
status: false,
'prof-startup': false,
'no-cached-data': false,
'prof-v8-extensions': false,
'disable-extensions': false,
'disable-gpu': false,
telemetry: false,
debugRenderer: false,
logExtensionHostCommunication: false,
'skip-release-notes': false,
'skip-welcome': false,
'disable-telemetry': false,
'disable-updates': false,
'disable-keytar': false,
'disable-workspace-trust': false,
'disable-crash-reporter': false,
'crash-reporter-id': '2cc1e8c2-4377-4843-9280-055c7d494850',
'skip-add-to-recently-opened': false,
'unity-launch': false,
'open-url': false,
'file-write': false,
'file-chmod': false,
'driver-verbose': false,
force: false,
'do-not-sync': false,
trace: false,
'force-user-env': false,
'force-disable-user-env': false,
'open-devtools': false,
__sandbox: false,
'no-proxy-server': false,
nolazy: false,
'force-renderer-accessibility': false,
'ignore-certificate-errors': false,
'allow-insecure-localhost': false,
logsPath: 'C:\\Users\\Dennis\\AppData\\Roaming\\Code\\logs\\20210713T161634'
}
[main 2021-07-13T14:16:34.373Z] Resolving machine identifier...
[main 2021-07-13T14:16:34.373Z] Resolved machine identifier: 79c92c3e31c61cc29cd600c13169fb4e4b470ce2feba0574f1d54b0eca86b50d
[main 2021-07-13T14:16:34.374Z] Main->SharedProcess#connect
[main 2021-07-13T14:16:34.394Z] StorageMainService: creating global storage
[main 2021-07-13T14:16:34.394Z] lifecycle (main): phase changed (value: 2)
[main 2021-07-13T14:16:34.395Z] windowsManager#open
[main 2021-07-13T14:16:34.395Z] windowsManager#open pathsToOpen [
{
backupPath: 'C:\\Users\\Dennis\\AppData\\Roaming\\Code\\Backups\\1626094841957',
remoteAuthority: undefined
}
]
[main 2021-07-13T14:16:34.396Z] IPC Object URL: Registered new channel vscode:877f5a97-b13c-4466-a984-900fbecea355.
[main 2021-07-13T14:16:34.396Z] window#validateWindowState: validating window state on 3 display(s) { mode: 1, x: 448, y: 156, width: 1024, height: 768 }
[main 2021-07-13T14:16:34.396Z] window#validateWindowState: multi-monitor working area { x: 0, y: 0, width: 1920, height: 1040 }
[main 2021-07-13T14:16:34.397Z] window#ctor: using window state { mode: 1, x: 448, y: 156, width: 1024, height: 768 }
[main 2021-07-13T14:16:34.397Z] window: using vscode-file:// protocol and V8 cache options: bypassHeatCheck
[main 2021-07-13T14:16:34.426Z] Setting proxy to '', bypassing '192.168.99.100,<local>'
[main 2021-07-13T14:16:34.441Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 0, emptyToRestore: 1, emptyToOpen: 0)
[main 2021-07-13T14:16:34.441Z] lifecycle (main): phase changed (value: 3)
[main 2021-07-13T14:16:34.447Z] update#setState idle
[main 2021-07-13T14:16:34.447Z] resolveShellEnv(): skipped (Windows)
[main 2021-07-13T14:16:34.561Z] [File Watcher (node.js)] [CHANGED] c:\Users\Dennis\AppData\Roaming\Code\User\globalStorage
[main 2021-07-13T14:16:34.565Z] [File Watcher (node.js)] [CHANGED] c:\Users\Dennis\AppData\Roaming\Code\User\globalStorage
[main 2021-07-13T14:16:34.635Z] resolveShellEnv(): skipped (Windows)
[main 2021-07-13T14:16:34.683Z] [File Watcher (node.js)] [CHANGED] c:\Users\Dennis\AppData\Roaming\Code\User\globalStorage
[main 2021-07-13T14:16:34.684Z] [File Watcher (node.js)] [CHANGED] c:\Users\Dennis\AppData\Roaming\Code\User\globalStorage
[main 2021-07-13T14:16:34.899Z] [File Watcher (node.js)] >> normalized [CHANGED] c:\Users\Dennis\AppData\Roaming\Code\User\globalStorage
[main 2021-07-13T14:17:04.458Z] update#checkForUpdates, state = idle
[main 2021-07-13T14:17:04.458Z] update#setState checking for updates
[main 2021-07-13T14:17:04.459Z] RequestService#request https://update.code.visualstudio.com/api/update/win32-x64-user/stable/2d23c42a936db1c7b3b06f918cde29561cc47cd6
[main 2021-07-13T14:17:04.459Z] resolveShellEnv(): skipped (Windows)
[main 2021-07-13T14:17:04.792Z] update#setState idle

Don't worry. I've already faced this problem. This generally appears if your system RAM is mostly occupied i.e many applications are running in the background or some cache. Firstly, restart your system. Open Task Manager and go to the Performance tab and select Memory. If you have very high memory usage, check which application is causing problem i.e using high memory. Google it. If it is a system task, it might be your Antivirus or Windows Defender or some update. In my case, it appears for few minutes and then the main screen and loads. Wait patiently for 5 minutes. My laptop is of 2GB ram only and I'm still able to run VS Code smoothly. If this doesn't work, might be some error in the application itself or some modification made by you. Uninstall VS Code. Since VS code doesn't remove all of its content. You have to do some manual work. Follow this link on How to fully remove VS Code-
https://debug.to/1074/how-to-uninstall-vs-code-completely#:~:text=1%20Go%20to%20Visual%20Studio%20Code%20path.%20%25LocalAppData%25%5CPrograms%5CMicrosoft,the%20.vscode%20folder%20at%20the%20below%20path%20%25UserProfile%25
If you have any problem regarding my answer. let me know in the comments.

Related

Tests when run multiple times then driver is not working after getOrientaion(used for making the script wait) method is run

I've created an appium script and my testcases contain wait functionality i.e. I'm making any app like youtube or any game wait for long duration of times.
The Wait code is like this:
for(int j=1; j<((min*2)+1);j++)
{
Thread.sleep(30000);
driver.getOrientation();}
Here min is the number of minutes that i'm trying to wait the application.
I'm also using invocationCount attribute of #Test testng to run tests multiple times.
After first Iteration when this wait section comes then the script crashes i.e. the next driver command like driver.findelement... is not working.
It is giving error like this:
org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: 'POST /element' cannot be proxied to UiAutomator2 server because the instrumentation process is not running (probably crashed). Check the server log and/or the logcat output for more details
Build info: version: '4.1.3', revision: '7b1ebf28ef'
System info: host: 'DESKTOP-M7R3JD6', ip: '192.168.52.1', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '16.0.2'
Driver info: io.appium.java_client.android.AndroidDriver
Command: [9d59677d-0ce4-4720-b837-8964d3946cf7, findElement {using=accessibility id, value=Camera}]
Capabilities {appium:adbExecTimeout: 20000, appium:appActivity: com.android.dialer.main.imp..., appium:appPackage: com.sh.smart.caller, appium:databaseEnabled: false, appium:desired: {adbExecTimeout: 20000, appActivity: com.android.dialer.main.imp..., appPackage: com.sh.smart.caller, deviceName: Infinix HOT 12 PRO, newCommandTimeout: 36000, platformName: android, platformVersion: 12, udid: 085733723N000129}, appium:deviceApiLevel: 31, appium:deviceManufacturer: INFINIX, appium:deviceModel: Infinix X668, appium:deviceName: 085733723N000129, appium:deviceScreenDensity: 320, appium:deviceScreenSize: 720x1612, appium:deviceUDID: 085733723N000129, appium:javascriptEnabled: true, appium:locationContextEnabled: false, appium:networkConnectionEnabled: true, appium:newCommandTimeout: 36000, appium:pixelRatio: 2, appium:platformVersion: 12, appium:statBarHeight: 72, appium:takesScreenshot: true, appium:udid: 085733723N000129, appium:viewportRect: {height: 1372, left: 0, top: 72, width: 720}, appium:warnings: {}, appium:webStorageEnabled: false, platformName: android}
Session ID: 9d59677d-0ce4-4720-b837-8964d3946cf7
What do i do to make it work?

WebdriverIO can not create session to test Android emulator with Appium

I am using Visual Studio Code and WDIO with Appium to test Android on emulator by Android Studio, but I can not run Appium for some reason. However Android home and Java home has been set and Appium Doctor confirms necessary dependencies are completed, no fix needed.
I have tried with Appium stand-alone and from Command too.
Wit Appium standalone the ERROR log is the below:
ERROR webdriver: Request failed with status 500 due to session not created: Unable to create session from {
"desiredCapabilities": {
"platformName": "android",
"appium:deviceName": "Pixel",
"appium:platformVersion": "10.0",
"appium:app": "\u002fUsers\u002fzsolt\u002fappium_js\u002fApiDemos-debug.apk"
If I add ['appium'] to services in wdio.config.js the ERROR log is the below, though Appium stand-alone is shut:
ERROR #wdio/cli:utils: A service failed in the 'onPrepare' hook
Error: Appium exited before timeout (exit code: 2)
[HTTP] Could not start REST http interface listener. The requested port may already be in use. Please make sure there is no other instance of this server running already.
at ChildProcess.<anonymous> (C:\Users\zsolt\Documents\AppiumTestProject\node_modules\#wdio\appium-service\build\launcher.js:103:16)
at Object.onceWrapper (events.js:417:26)
at ChildProcess.emit (events.js:310:20)
at ChildProcess.EventEmitter.emit (domain.js:482:12)
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
This is my wdio.config.js file with using Appium stand-alone:
exports.config = {
runner: 'local',
port: 4723,
specs: [
'./test/specs/**/*.js'
],
exclude: [
// 'path/to/excluded/files'
],
maxInstances: 10,
capabilities: [{
platformName: 'android',
'appium:deviceName': 'Pixel',
'appium:platformVersion': '10.0',
'appium:app': '/Users/zsolt/appium_js/ApiDemos-debug.apk'
}],
logLevel: 'error',
bail: 0,
baseUrl: 'http://localhost',
waitforTimeout: 10000,
connectionRetryTimeout: 120000,
connectionRetryCount: 3,
services: ['selenium-standalone',
/*['appium', {
//command : 'appium'
}]*/],
reporters: ['spec'],
mochaOpts: {
ui: 'bdd',
timeout: 60000
},
These are my:
"devDependencies": {
"#wdio/local-runner": "^6.1.11",
"#wdio/mocha-framework": "^6.1.8",
"#wdio/selenium-standalone-service": "^6.0.16",
"#wdio/spec-reporter": "^6.1.9",
"#wdio/sync": "^6.1.8",
"appium": "^1.17.1"
Has anybody an idea what am I doing wrong?
Welcome to Stack-overflow!
Below is my configuration and I believe you are missing some important details.
{
platformName: 'Android',
maxInstances: 1,
'appium:deviceName': 'Device Name',
'appium:platformVersion': '8'
'appium:orientation': 'PORTRAIT',
'appium:app': 'Path to App',
'appium:automationName': 'UiAutomator2',
'appium:noReset': true,
'appium:newCommandTimeout': 240,
}
There are boilerplates from maintainers themselves here.
I have played with the boilerplates and was able to run the tests on android emulator through Appium finally.
I have then compared the differences in conf.js and figured out, the below is needed to execute the test.
services:[
[
'appium',
{
// For options see
// https://github.com/webdriverio/webdriverio/tree/master/packages/wdio-appium-service
args: {
// For arguments see
// https://github.com/webdriverio/webdriverio/tree/master/packages/wdio-appium-service
},
command: 'appium',
},
],
],
Interesting but actually the test runs with only the below capabilites too:
capabilities: [{
platformName: 'Android',
'appium:deviceName': 'Pixel 2',
'appium:app': join(process.cwd(), './ApiDemos/ApiDemos-debug.apk'),
}],
When I execute the test it logs almost the same error messages as before though at the end of the execution it runs the test on the emulator. I did not use the Appium Desktop app.
Not perfect but works...
I guess this issue has been sorted out.
Cheers
Also you need to install the Appium service:
$ npm i #wdio/appium-service --save-dev
Finally check in your wdio.conf.js:
port: 4723, // default appium port
services: [
[
'appium',
{
args: {
},
command: 'appium'
}
]
],
Check that the file you are running is inside the correct folder when you do the 'npx wdio'.
this file

Cannot Install Debugger for Chrome into Visual Studio Code

As the subject reads, I cannot install Debugger for Chrome extension in Visual Studio Code (Version: 1.23.0). As suggested in other posts, I closed VS Code, went out to User.vscode\extensions, removed any reference to it, and restarted VS Code. I tried using command line and receive this error
(command: code --install-extension msjsdiag.debugger-for-chrome):
$ code --install-extension msjsdiag.debugger-for-chrome
Found 'msjsdiag.debugger-for-chrome' in the marketplace.
Installing...
WARNING: Promise with no error callback:256
{ exception: null,
error:
{ Error: ENOENT: no such file or directory, open 'C:\Users\SOMEUSER\.vscode\extensions\.msjsdiag.debugger-for-chrome-4.4.0\node_modules\vscode-chrome-debug-core\out\src\(*&)))&^.js'
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\\Users\\SOMEUSER\\.vscode\\extensions\\.msjsdiag.debugger-for-chrome-4.4.0\\node_modules\\vscode-chrome-debug-core\\out\\src\\(*&)))&^.js' },
promise:
{ _oncancel: null,
_nextState: null,
_state:
{ name: 'error',
enter: [Function: enter],
cancel: [Function: s],
done: null,
then: null,
_completed: [Function: s],
_error: [Function: s],
_notify: [Function: v],
_progress: [Function: s],
_setCompleteValue: [Function: s],
_setErrorValue: [Function: s] },
_listeners: null,
_value:
{ Error: ENOENT: no such file or directory, open 'C:\Users\SOMEUSER\.vscode\extensions\.msjsdiag.debugger-for-chrome-4.4.0\node_modules\vscode-chrome-debug-core\out\src\(*&)))&^.js'
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\\Users\\SOMEUSER\\.vscode\\extensions\\.msjsdiag.debugger-for-chrome-4.4.0\\node_modules\\vscode-chrome-debug-core\\out\\src\\(*&)))&^.js' },
_isException: false,
_errorId: 256,
done: [Function: done],
then: [Function: then] },
handler: undefined,
id: 256,
parent: undefined }
C:\Program Files\Microsoft VS Code\resources\app\out\vs\code\node\cli.js:58
define(e[9],t([1,0,2]),function(e,t,n){"use strict";function r(e){i(e)||t.errorHandler.onUnexpectedError(e)}function i(e){return e instanceof Error&&e.name===u&&e.message===u}Object.defineProperty(t,"__esModule",{value:!0});var o={};n.TPromise.addEventListener("error",function(e){var t=e.detail,n=t.id;t.parent?t.handler&&o&&delete o[n]:(o[n]=t,1===Object.keys(o).length&&setTimeout(function(){var e=o;o={},Object.keys(e).forEach(function(t){var n=e[t];n.exception?r(n.exception):n.error&&r(n.error),console.log("WARNING: Promise with no error callback:"+n.id),console.log(n),n.exception&&console.log(n.exception.stack)})},0))});var s=function(){function e(){this.listeners=[],this.unexpectedErrorHandler=function(e){setTimeout(function(){if(e.stack)throw new Error(e.message+"\n\n"+e.stack);throw e},0)}}return e.prototype.addListener=function(e){var t=this;return this.listeners.push(e),function(){t._removeListener(e)}},e.prototype.emit=funct
Error: ENOENT: no such file or directory, open 'C:\Users\SOMEUSER\.vscode\extensions\.msjsdiag.debugger-for-chrome-4.4.0\node_modules\vscode-chrome-debug-core\out\src\(*&)))&^.js'
Error: ENOENT: no such file or directory, open 'C:\Users\SOMEUSER\.vscode\extensions\.msjsdiag.debugger-for-chrome-4.4.0\node_modules\vscode-chrome-debug-core\out\src\(*&)))&^.js'
at Timeout._onTimeout (C:\Program Files\Microsoft VS Code\resources\app\out\vs\code\node\cli.js:58:758)
at ontimeout (timers.js:386:14)
at tryOnTimeout (timers.js:250:5)
at Timer.listOnTimeout (timers.js:214:5)
Here is a temporary solution:
close VS Code
in file explorer go to %UserProfile%\.vscode\extensions
remove .msjsdiag.debugger-for-chrome-4.4.1 directory
start VS Code
disable auto updating extensions from EXTENSIONS menu in VS Code
download prior version from here: https://msjsdiag.gallery.vsassets.io/_apis/public/gallery/publisher/msjsdiag/extension/debugger-for-chrome/4.3.0/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage
rename the file to have a .vsix extension
choose "install from VSIX" from EXTENSIONS menu in VS Code and select the file you just renamed

data lost in mongodb replica set mode

My replica set has two nodes:
1: the master node
2: a slave node with priority:0, votes:0
The oplog size is 5000MB.
run this for loop in master shell:
for (i=0;i<1000000;i++)
{
db.getSiblingDB("ff").c.insert(
{ a:i,
d:i+".#234"+(++i)+".234546"+(++i)+".568679"+(++i)+"31234."+(++i)+".12342354"+(++i)+"5346457."+(++i)+"33543465456."+(++i)+".6346456"+(++i)+"123235434."+(++i)+".2345345345"+(++i)
}
)
}
Kill the slave node while the for loop is running: kill -9 $(pidof slave_node)
Stop the for loop after a second; then restart the slave node.
Then run db.getSiblingDB("ff").c.count() to check data in both slave and master nodes, with the results:
master:20w
slave:15w
The slave node can catch up with the primary, but there is a lot of data lost from the slave.
Why is this?
Here is the slave node's log as it restarts after being killed:
2017-11-27T05:53:53.873+0000 I NETWORK [thread1] waiting for connections on port 28006
2017-11-27T05:53:53.876+0000 I REPL [replExecDBWorker-0] New replica set config in use: { _id: "cpconfig2", version: 2, protocolVersion: 1, members: [ { _id: 0, host: "127.0.0.1:28007", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 3.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 1, host: "127.0.0.1:28006", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 0.0, tags: {}, slaveDelay: 0, votes: 0 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: 60000, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: ObjectId('5a1ba5bbb0a652502a5f002a') } }
2017-11-27T05:53:53.876+0000 I REPL [replExecDBWorker-0] This node is 127.0.0.1:28006 in the config
2017-11-27T05:53:53.876+0000 I REPL [replExecDBWorker-0] transition to STARTUP2
2017-11-27T05:53:53.876+0000 I REPL [replExecDBWorker-0] Starting replication storage threads
2017-11-27T05:53:53.877+0000 I REPL [replExecDBWorker-0] Starting replication fetcher thread
2017-11-27T05:53:53.877+0000 I REPL [replExecDBWorker-0] Starting replication applier thread
2017-11-27T05:53:53.877+0000 I REPL [replExecDBWorker-0] Starting replication reporter thread
2017-11-27T05:53:53.877+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Connecting to 127.0.0.1:28007
2017-11-27T05:53:53.877+0000 I REPL [rsSync] transition to RECOVERING
2017-11-27T05:53:53.878+0000 I REPL [rsSync] transition to SECONDARY
2017-11-27T05:53:53.879+0000 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 127.0.0.1:28007, took 2ms (1 connections now open to 127.0.0.1:28007)
2017-11-27T05:53:53.879+0000 I REPL [ReplicationExecutor] Member 127.0.0.1:28007 is now in state PRIMARY
2017-11-27T05:53:54.011+0000 I FTDC [ftdc] Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost. OK
2017-11-27T05:53:54.645+0000 I NETWORK [thread1] connection accepted from 127.0.0.1:52404 #1 (1 connection now open)
2017-11-27T05:53:54.645+0000 I NETWORK [conn1] received client metadata from 127.0.0.1:52404 conn1: { driver: { name: "NetworkInterfaceASIO-Replication", version: "3.4.9" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 8 (jessie)"", architecture: "x86_64", version: "Kernel 3.10.0" } }
2017-11-27T05:53:59.878+0000 I REPL [rsBackgroundSync] sync source candidate: 127.0.0.1:28007
See the page Accuracy after Unexpected Shutdown for details and information on how to recover from this situation.

'Globals' are not working as expected in protractor 4.0.0?

we have the following setting in our onPrepare function of config file-
exports.config = {
directConnect: true,
baseUrl: env.baseUrl,
capabilities: env.capabilities,
onPrepare: function () {
var chai = require('chai');
var chaiAsPromised = require('chai-as-promised');
chai.use(chaiAsPromised);
global.expect = chai.expect; // by removing this line error is not thrown
browser.manage().window().maximize();
},
setDefaultTimeout : 60 * 1000,
framework: 'custom',
frameworkPath: require.resolve('protractor-cucumber-framework'),
specs: [
'../Features/*.feature'
],
cucumberOpts: {
monochrome: true,
strict: true,
plugin: ["pretty"],
require: ['../StepDefinitions/*.js', '../Support/*.js'],
tags:'#AddActiveTip,#AddInActiveTip,~#AddActiveManufacturer,~#AddInActiveManufacturer'
//tags:'#TestSplitText'
}
};
since the upgrade to protractor 4.0, I am getting the following error and the browser hangs indefinitely and the error does not help to debug in anyway.
error:
> protractor Config/config.js --troubleshoot
[22:38:12] I/direct - Using FirefoxDriver directly...
[22:38:12] I/launcher - Running 1 instances of WebDriver
/Users/pasalar/protractor/psms-protractor/node_modules/protractor/built/exitCodes.js:87
if (e.message.indexOf(errMsg) !== -1) {
^
TypeError: Cannot read property 'indexOf' of undefined
at Function.ErrorHandler.isError (/Users/pasalar/protractor/psms-protractor/node_modules/protractor/built/exitCodes.js:87:30)
at Function.ErrorHandler.parseError (/Users/pasalar/protractor/psms-protractor/node_modules/protractor/built/exitCodes.js:98:26)
at process.<anonymous> (/Users/pasalar/protractor/psms-protractor/node_modules/protractor/built/launcher.js:169:54)
at emitOne (events.js:82:20)
at process.emit (events.js:169:7)
at process.emit (/Users/pasalar/protractor/psms-protractor/node_modules/protractor/node_modules/source-map-support/source-map-support.js:419:21)
at process._fatalException (node.js:224:26)
npm ERR! Test failed. See above for more details.
is anyone else facing this issue? are there any major changes that I am missing?
The error message shown has nothing to do with "globals", it is working as expected! my scripts were failing randomly due to network latency issues.But the error messages need to improved as the user has no idea what caused the error!
Marking it closed as I was able debug this issue!