I'm trying to install the Veracity Learning LRS locally (on Windows). I followed this guide exactly, and MongoDB is installed and running with no apparent problems. However, I get a strange TypeError when I try to save the configuration:
Console: at processTicksAndRejections (internal/process/task_queues.js Some OSs will require you to run with administrator rights to bind to your selected port.
Console: at processTicksAndRejections (internal/process/task_queues.js Cannot convert undefined or null to object
TypeError: Cannot convert undefined or null to object
at Function.assign (<anonymous>)
at v (C:\snapshot\lrs2\build\lite\manager.js:2185:795751)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async C:\snapshot\lrs2\build\lite\manager.js:2185:796007
The given file locations don't exist on my machine, so I don't know where to look to debug this. I've also tried to run the command prompt as administrator, which removes the first message but not the second. Has anyone encountered this issue before? I'm also not committed to the Veracity LRS, so I'm also open to suggestions for a simpler installation; this was only supposed to be for testing.
I'm from Veracity, and this is an issue that cropped up on some configurations a while ago, but we've not seen it in a long time, so either the bug has reappeared or you just have an older version.
If you're not using 1.10.x, make sure to try the latest version.
Related
I am trying to follow the instructions in the mapbox installation guide but I am getting the error:
{"message":"Not Authorized - No Token"}
I am reasonably confident that I am using the correct password - and have even generated a new one to be sure. I have tried both the private password (as recommended) and my public one. I have also hard-coded the password into my build.gradle file, just in case I was failing to get it from the properties file. This is incredibly frustrating since, clearly, until I get the SDK, I can't write any code :-(
This is a really shame, since the V10 SDK looks much better than previous versions and has more sample code, which looks like being a huge help!
I am using Android Studio V4.2.2 running on MacOS Big Sur 11.5.
In conclusion, my original error was due to me not following the advice on the mapbox website, by configuring a token/password with DOWNLOADS:READ scope. My investigation was greatly helped by #tim_yates' input, which lead me to write a shell script that tested the remote connection, using a command of the form:
curl -u mapbox:<token> -G <url>
This returned much more meaningful errors than the ones returned by gradle inside Android Studio.
Sadly, this is not the end, since it has now left me with a new tranche of errors. However, at least it has moved me me forward a bit ;-/
I created a new application with react native windows, and it works well the first (few) times I run it, however, when closing the application I always end up with the following warning:
Attempt by security transparent method 'System.Reactive.Concurrency.CoreDispatcherScheduler..ctor(Windows.UI.Core.CoreDispatcher)' to access security-critical type 'Windows.UI.Core.CoreDispatcher' failed.
I've tried this on more than one computer and all of them get the same error but I can't find a way to fix this, meaning I cant proceed with my Native project in fear that it will malfunction every day.
How do I fix this, to stop this from happening again, or is it a bug?
I'm a novice in React Native myself, but here are a few suggestions:
1) There's an issue logged in GitHub on this exact problem: https://github.com/Microsoft/react-native-windows/issues/1954
2) I personally find that I get this with command-line execution (react-native run-windows) but I don't think(?) that I've seen it when running from inside Visual Studio. Try that approach to running instead.
3) As described at GitHub - I've found that deleting windows\Debug folder before running tends to resolve the issue.
I am trying to help someone get setup running nose tests. They are running into an error I have never seen before. A google search seems to be yielding results for Java, but not Python.
Below is a screenshot of the error:
Any ideas on how to correct this error?
I have tried uninstalling and re-installing Python. I have verified that the settings are correct as well as the parameters for the nose test. The PATH variables for Python are likewise correct.
Not sure what is going on here.
After trying and failing to run the test from the terminal, I was able to determine that the PATH variables were incorrect after all. I fixed them, and then logged off and back on again, and the issue is fixed.
I have a node.js project that runs fine on Pc and Linux however when running on a Mac (Mountain Lion) the jQuery module doesn't work. any assignment to a property of the window object is ignored.
That is
if(jQuery){
window.jQuery = jQuery;
if(!window.jQuery){
throw "assignment didn't have any effect";
}
}
will throw an exception. Any ideas to solve it will be appreciated
THe prototype of the object is undefined I would expect those two things to be related. The window object is created using jsdom.createWindow() (which in turn returns doc.parentWindow)
it would seem that it's caused by the line below
vm.runInContext('this', context);
which returns the actual object (with no prototype).
THe problem is a side effect of not being able to compile contextify while installing the jsdom module. This can be fixed by installing make. The conde in the question that fails is error handling that tries to handle the installation problem of contextify.
installing make on a make can be done be installing development tools (Commandline tools for XCode for OSX ). After installing make then reinstall contextify
im getting this error when im trying to update Meteor on windows.
Using git bash here, but getting the same error in command prompt.
Does the file simply not excist, or what is going on here, have had it for some days now, so im just curious if the file excist at all, since its not really officially supported on windows yet?
$ meteor update
New version available: 0.3.8
Failed to download: https://d3sqy0vbqsdhku.cloudfront.net/meteor-package-Windows
_NT-i686-0.3.8.tar.gz
It is not supported officially yet on Windows. You need to rely on weekly checking win.meteor.com for updates.
I believe you are correct in your assumption of it not really being officially supported on windows. I also get this same error and have tried everything to get around it. I tried scouring for this package manually and was unable to find it.