Instance initializer causes 'dummy' application to stop working - ember-cli

I am learning ember-cli and started with the tutorial/guide. Everything went fine till I added my own instance initializer and the application stopped working. After playing around a bit with various options, I find that just doing a touch instance-initializer/foo.js also causes the same issue. What started me on this path was trying to pull AWS amplify as a service and configuring it, but removed all the code and found that just creating a zero length file in the instance initializer directory causes the same issue.
Obviously I don't have a clear understanding of how ember-cli uses instance initializers. Any help here is appreciated.
ember-cli: 3.15.1
node: 13.6.0
os: linux x64

Related

Why am I getting an error when loading webviews in VS Code?

I'm using a portable install of VS Code 1.56.1 on Windows 10. Whenever open an extension from the marketplace, I get the following error:
Error loading webview: Error: Could not register service workers: TypeError: Failed to register a ServiceWorker for scope ('vscode-webview://extensioneditor/') with script ('vscode-webview://extensioneditor/service-worker.js?platform=electron&id=extensionEditor&vscode-resource-origin=https%3A%2F%2FextensionEditor.vscode-webview-test.com'): ServiceWorker cannot be started.
Same thing happens for other things using webviews, with a slightly different path (like VS Code release notes). I'm able to install plugins and view the Feature Contributions tab, but I cannot view the Details and Changelog tabs.
Any thoughts on what could be causing this? This is on a managed machine where security settings might be changing. I'm using a portable install because my installed version stopped working out of the blue last week and this was supposed to be the workaround until that was figured out.
I was getting the same error, it looks like an issue introduced on version 1.56.0.
For me the fix was running VS Code without elevated permissions.
I always run as administrator and running without it fixed the issue for me.
I had this problem, in terminal use code . --no-sandbox
Updating python3 to the most recent version may also help.

service fabric local cluster exception from 0x80071BFF

I created a solution with a few applications, and it worked perfectly. But a day later when I was about to debug the solution again, it suddenly cannot start.
I did have firewall and AV disabled, both when it worked and later when it didn't work.
It works fine when deployed to azure, but not locally.
The error thrown is:
Exception from HRESULT: 0x80071BFF
at System.Fabric.Interop.NativeRuntime.FabricGetNodeContext()
at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.GetNodeContextHelper()
at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag, String functionArgs)
A related post register-servicefabricapplicationtype-on-a-secure-cluster-always-times-out
describes a similar thing.
However, I get this while debugging locally and with smallest possible application: I even just created 1 application, 1 actor, did no changes, hit F5 and I get this error.
So, I looked at service-fabric-troubleshoot-local-cluster-setup and while I also get the TypeInitializationException, the solution of:
Your path variable was not correctly set during installation. Please sign out of Windows and sign back in. This will fully refresh your path.
did not work at all.
Nothing else on that page seemed to be related.
Now I begin to feel that I've hit the end of what key words I can google, and still I have no idea what to do.
Any help would be greatly appreciated.
EDIT:
I've tried starting via cluster manager and apps can still not start.
I've removed apps, removed cluster, tried with new solutions, over and over. The only thing I haven't tried is reinstalling SDK and VS. I'm a bit reluctant to reinstall VS, so I'd hope to find some clues before resorting to that.
UPDATE1:
Now I reinstalled Service Fabric v. 5.3.311.9590, SDK and Tools.
Created a solution, added a stateless service. Hit F5. The exact same error is thrown.
I will now try to install on another machine with mostly the same configuration.
UPDATE2:
Installed the SDK on an identical VM, Win10, also with VS2015 Update 3. Created solution, added 1 actor, hit F5 and also on this macchine the exact error is thrown.
I tried Debug without debugging (as mentioned here) to attach later. But the application never starts. It is failed. This is the same on both the machines.
It all worked and from one day to the other it doesn't, and it's a problem that I cannot find anywhere on the net. What can this be? I found that the security updates from windows was made about the same date this happened...
I will uninstall and try again.
UPDATE3:
Uninstalling security update was not possible, but I could hide a couple of other updates. To no luck though.
From here I found this https://github.com/Azure/service-fabric-issues/issues/15 and realised I actually was very low on diskspace, and so I increased it (hyper-v manager) to 20 gigs free. But no, still the same problem.

Getting error "Timeouts can be caused by AngularJS services $http and $timeout which fail to complete quick enough."

I have wrote a function which technically and logically is correct and while running it runs perfectly locally. But on server I am getting the above error which I could not figure out. I am on protractor version 1.6.0 as same as server but still not able to figure out what causes this.
Scenario is like, I have created many it functions inside my spec.js. But when I ran my spec starting two it functions execute precisely, but on third it scripts fails with above error on server. But when I ran the same spec on my local system with similar settings and configuration, it runs smoothly. Please give me any suggestion if you have encounter the same issue earlier. You can also share the link of a blog if you have any. I am a newbie. Thanks in advance.
Actually , I did a mistake, when we use non angular locators we have to use findElementDriver instead of findElement. Locally, its runs whithout any issues but on server it gives the above error.

VSDBCMD Won't Start - Sql100DatabaseSchemaProvider can not be instantiated

I've followed the instructions over at http://msdn.microsoft.com/en-us/library/dd193258(v=vs.100).aspx
I've copied the deploy folder and the other dll's over to the remote machine and installed SQL Server 2008 Management Objects. However, when I attempt to run my command (real credentials stripped)
vsdbcmd /a:Import /cs:"Data Source=mydb;Integrated Security=false;Pooling=False;Initial Catalog=dbname;User ID=sa;Password=password;" /model:today.dbschema
I always get the error
The extension type Microsoft.Data.Schema.Sql.Sql100DatabaseSchemaProvider could not be instantiated.
I've searched around, but don't see anything that points to this. Any help please?
I found the issue - the server had .NET 4.0 Client Profile installed. Once I installed the full runtime, this issue went away.

problem with linked libraries or classes?

i recently finished one project..now when i create a new navigation project in xcode and try to run it in simulator the application crashes and error in debugger window shows that i am missing some classes which i had used in my previous project(not in this one) and in some cases it gives
Couldn't register com.yourcompany.GuessGame with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.
is this some problem related to linked libraries??
I assume you're tried restarting the simulator / restarting XCode / cleaning your build (build->Clean All Targets) ?
What's the name of your first project beacuse if it's com.yourcomany.GuessGame as well, you might run into problems?