How to fix vagrant variable not defined? - vagrant

Please suggest what is the error in this.
I am getting error as ws2 variable not defined even though it is defined.
https://github.com/ukreddy-erwin/openstacklogs/tree/master/04-06-2020

I've used the files provided through your github and everything is working for me, there was no issues faced (i've terminated after the ws2 machine started since this means everything worked correctly), i've also attached an image showing that things actually worked.
Powershell output after vagrant up

Related

VS Code Go intellisense causing problems

fmt.Printf("hello") was working great with intellisense
but suddenly in every go file my fmt.P .. suggestion becomes this
and this
I am not getting "fmt.Printf()" suggestions anymore and getting stuck with those "const", "func", "import", "type", & "var".. what is happening? (Though it is not suggesting fmt.Printf() but it's still working). how can I get normal suggestions by intellisense like previous?
I tried disabling GO official extension, then it got fixed but also I lose all autocomplete/suggestion feature. a go file in root directory is working fine but other files inside packages are showing this kinda problems. Please help
After searching a lot I couldn't find exact problem and solution. And somehow I saw some were facing "case-insensitive import collision:" and it was due to upper-case and lower-case mixture usage in filename. I remembered it seeing in my package name (though this error vanishes sometimes and ignored it as code execution was working) and tried renaming my filename from "sequenceUtils.go" to "sequence_utils.go" and boom ..! intellisense started working ..! though my colleague was working with same filename and he wasn't facing problems..
I think the problem should be properly identified..!

Symfony Warning: DOMElement::setAttribute(): string is not in UTF-8

I am facing this error while running the Symfony 2.8 project on my windows machine. I have read all the related questions available in this forum and tried every one of them but no luck. Did anyone face this issue?
Note: This project works fine in ubuntu system without any issue.
Can anyone of you give me an input which will help me to resolve this issue?
The full error in the command line is,
[Symfony\Component\Debug\Exception\ContextErrorException]
Warning: DOMElement::setAttribute(): string is not in UTF-8
Seems this issue is related and according to this comment you need to either update your project to 3.x (or 4.x) or eliminate the reason of the issue from your code.

Linker Command Failed Error, Tried Everything

I've tried everything and it keeps giving me the same error. Not sure how to solve this.
Here is the error.
After setting it to 'fast whole', I'm getting this error.
I've tried deleting Derived Data, setting 'No Common Blocks' to NO, setting 'Enable Testability' to NO and setting 'Optimization' to fast whole (all from resources I found on StackOverFlow). Nothing works.
Thanks!
I actually didn't import my OBJC files properly. Once I did this, all seemed to be fine.

Tensorflow object detection: ImportError: No module named nets

I am currently attempting to install the tensorflow object detection app on Windows 7 (employer requirement) and I am failing at a few steps from the end.
Basically I get the following error when I run the installation test command:
ImportError: No module named nets.
I have read some solutions on the subject:
https://github.com/tensorflow/models/issues/729
https://github.com/tensorflow/models/issues/1842
which looks like this:
export PYTHONPATH="$PYTHONPATH:"somepath"/tensorflow/models/slim"
basically meaning that I must set the right path in the PYTHONPATH environmental variable.
Working with Windows, I tried calling this:
SET PYTHONPATH="$PYTHONPATH:C:tensorflow/models/slim
And when it didn't work, I created a PYTHONPATH variable in system-> environmental variables.
I'm still getting the error so I suppose that I am still missing something but due to my lack of knowledge I still can't figure out what.
Would someone familiar with Windows be able to point out what's missing?
Thanks
in linux:
add export export PYTHONPATH=$PYTHONPATH:pwd:pwd/slim to ~/.bashrc
attention:you should keep single quote mark
if you work with windows, i guess it should like this:PYTHONPATH=$PYTHONPATH:'C:/tensorflow/models':'C:/tensorflow/models'/slim
just my guess, you can take a try.
good luck!
If you run the setup.py it will install all the relevant modules for object detection. The other option is download the git directory. cd to the folder and try to run the module from there. You might face protubuf issue. Try to install it before running the code. It's bit complicated to install protobuf in windows. But if you are not using ".pb" file, then you don't need to.
I figured out a way to make it work. I am not writing this as a final answer as it is mostly a workaround and due to lack of understanding from my part I cannot guarantee it will work (and also it might not be best good practice).
Anyway here it is:
As Beta previously suggested, you have to run setup.py, however running it from models folder did not do it for me, I also had to run it from object detection folder.
However there was a problem there, it generated an error saying the BUILD already existed (which was correct) so I had to delete the BUILD file from inside of model.
After that it worked, turns out the path I had set was working fine.
Now if some experts would look into this and explain how and why this workaround worked it might make this a valid solution.

Python Cannot Run NoseTest due to CreateProcess Error 87

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.

Resources