I've been trying to install Deeplab2 for a week but it's getting a bit hard.
Today, I've been able to achieve the test configuration step
However, once there, I find the next errors:
NotFoundError: C:[...]\DeepLab\models-master\research\deeplab2\tensorflow_ops\python\ops....\kernels\merge_semantic_and_instance_maps_op.so not found**
And that's true, you can find a screenshot of that folder attached.
kernels folder
All in all, in the instructions I did not find any step that helps my creating that .so.
I've tried to look at ways of compiling cc to so, but it's not working. Additionally, I looked for the file on the internet but it's not available to be downloaded.
Ps. I'm working in Windows.
Related
I'm trying to run some TestCafe tests from our build server, but getting the following error...
"Could not find test files at the following location: "C:\Testing\TestCafe".
Check patterns for errors:
tests/my-test.ts
or launch TestCafe from a different directory."
I did have them running or able to be found on this machine previously, but others have taken over the test coding and changed the structure a bit when moving it to a Git repository. Now when I grab the tests from Git and try to run, the problem presents itself. I'm not sure if there is something in a config file that needs adjustment but don't know where to start looking.
The intention is to have it part of our CI process, but the problem is also seen when I attempt to run the tests from the command line. The build process does install TestCafe, but there is something strange around this as well.
When the build failes with the can't find tests error, if I try to run the following command in the proper location...
tescafe chrome tests/my-test.ts
... I get, 'testcafe' is not recognized as an internal or external command,
operable program or batch file.
Just can't understand why I can't get these tests running. TestCafe setup was pretty much easy previously.
ADDENDUM: I've added a screenshot of the working directory where I cd to and run the testcafe command as well as the tests subdirectory containing the test I'm trying to run.
Any help is appreciated!!
testcafe chrome tests/my-test.ts is just a template; it isn't a real path to your tests. This error means that the path that you set in CLI is wrong, and there aren't any tests. You need to:
Find out where you start CLI. Please attach a screenshot to your question.
Define an absolute path to tests or a path relative to the place where CLI was started. Please share a screenshot of your project tree where the directory with tests is open.
Also, you missed t in the tescafe chrome tests/my-test.ts command. It should be tesTcafe chrome tests/my-test.ts. That is why you get the "'tescafe' is not recognized as an internal or external command" error.
I was able to get things working by starting from scratch. I uninstalled TestCafe and cleaned the working folder. During next build it was fine. I'm sure I've tried this several times, but it just started working.
One positive that came out of it was that I discovered a typo in a test file name, which was also causing issues finding the test I was using to check testing setup.
Thanks for helping!!
I'm adding security to a 'forgot password' process and using the securimage code. I know it is not recommended, but it is only 1 step in a multi-step validation ... just using the tools I have available until something better comes along
I simply installed the securimage files in a root directory under public_html, ran the compatibility check (all good except the LAME M_3 support)
When I run securimage_show by itself, I get a good image. When I run example_form or captcha.html, I get a background image with 'Failed to load TIF font file'. I looked for any errors, did some debugging, and do not see any difference in the debug log with respect to the TFF file location or name.
Any pointers would be appreciated!
Version: apache-log4cxx-0.12.0.tar.gz
Configuration:
mkdir build; cd build && cmake -DBUILD_SHARED_LIBS=off -DAPR_STATIC=yes -DAPU_STATIC=yes ..
Symptoms (log snippet):
32882 error: downloading 'https://www-us.apache.org/dist/logging/log4j/1.2.17/log4j-1.2.17.tar.gz' failed
32883 status_code: 6
32884 status_string: "Couldn't resolve host name"
32885 log:
32886 --- LOG BEGIN ---
This was building just last month. I can't 100% attest to the fact that the build procedure has not changed (since it was done manually) but I don't believe it was significantly different.
At first, I thought my DNS resolver was just out of date, but after some dig-ing and fiddling with /etc/resolv.conf, it has become apparent that the www-us.apache.org url log4cxx was using to get the tarball from has disappeared from the face of the earth.
Two methods you can use to fix this (which I wish someone had posted before me).
First
Hack your /etc/hosts file to spoof www-us.apache.org to actually go to www.apache.org (where you will find a redirect for the link). To give neophytes an idea of what I'm talking about, here is kinda how I did it on Debian.
sudo echo '151.101.2.132 www-us.apache.org' >> /etc/hosts
Second
Fix the cmake script src/test/java/CMakeLists.txt line 3 to point to the right link. The broken one is
https://www-us.apache.org/dist/logging/log4j/1.2.17/log4j-1.2.17.tar.gz
The right one is
https://downloads.apache.org/logging/log4j/1.2.17/log4j-1.2.17.tar.gz
Digging around the GitHub account we found this code merged and (I assume) ready to go out with the next release, whenever that is.
https://github.com/apache/logging-log4cxx/commit/341a23aa0d13278c8ae85b6017d49de9790f00fe
Here's hoping this helps someone not remain stuck, expecting the build to work like it did a month ago.
I'm new to Tensorflow and I just started using Google Colab a week ago, and I want to run it locally so that it can use my own CPU to avoid Colab Resource Restrictions, so I followed the Official guide on running Colab locally, and after I'm all set and try to run any cell in the Colab, it pops up this error:
And then immediately changed to this -
And here is the full runtime logs it gave me:
Could not fetch resource at : 404 Not Found
FetchError: Could not fetch resource at : 404 Not Found
at ny.fr [as constructor] (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20210513-060327-RC00_373550014:684:397)
at new ny (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20210513-060327-RC00_373550014:1299:1093)
at za.program_ (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20210513-060327-RC00_373550014:5067:158)
at Ba (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20210513-060327-RC00_373550014:19:336)
at za.next_ (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20210513-060327-RC00_373550014:17:503)
at Ca.next (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20210513-060327-RC00_373550014:20:206)
at f (https://colab.research.google.com/v2/external/external_polymer_binary.js?vrz=colab-20210513-060327-RC00_373550014:61:101)
Since I've been struggling with this error all day, and I also reinstall and upgrade the Python, TensorFlow as well as the jupyter-notebook a few times, so PLEASE HELP ME!!! Or if anyone knows how to change the runtime back to browser will also be helpful, I'm kind of stuck here...
Since you mentioned you are new to colab, just double checking the basics - did you try Connect Button (in top right area of colab) and choosing "Connect to Local Run time"?
Also note that sometimes large datasets cause out of memory error, so that might be one cause too.
I'm experiencing a problem that I could not find a solution for yet.
I use Test Complete to automate some GUI related scenarios for an app. I developed some scripts that were working at some point in the past. After a few months I got back and tried to run one of the scripts. The script failed with the following error while it was executing a ClickCell operation on a grid object.
An error occurred.
Possible reasons:
1. The application stopped responding.
2. The application was compiled incorrectly (see the Open Applications topic in the help system).
3. An error occurred in TestComplete.
Technical information:
379 0x80070057 (The parameter is incorrect.) .
Tested object:
...
I executed the same script on another machine with another Test Complete installation and it worked. So I guess it's not the target app that is the problem.
I checked solutions on the web for this issue, but nothing worked. I cleaned up the temp files in all the locations I could find in this answer. The behavior was the same.
So I guess it might be something related with the Test Complete installation. I tried reinstalling it a few times, but it didn't do the trick.
I then used Dependency Walker (as suggested somewhere on the web) on testcomplete.exe and found that there are some dlls that are missing from the Bin directory of Test Complete. Could they generate this error? If yes, how can I get them? As I said, I already re-installed the app a few times.
Did anyone bump into this while working with Test Complete? Is there any .net temp location that I should clean?