srun: error: Ignoring conflicting option "x11" in plugin "x11" - tensorflow

When I am trying to get an interactive session on a gpu node, I got the following error. Does anyone know what the error means and how it will affect my interactive session? Thank you.
srun: error: Ignoring conflicting option "x11" in plugin "x11"

Related

ERROR #wdio/runner: Error: Unable to load spec files quite likely because they rely on `browser` object that is not fully initialised

After running npm install getting the following error: ERROR #wdio/runner: Error: Unable to load spec files quite likely because they rely on browser object that is not fully initialised
The code was running fine, only after npm install getting this error.
I after long trouble shooting it turned out to be one of my script had one line not correctly commented out, instead of // I had /. Now all is working.

IntelliJ IDEA can't Debug because "transport library not found: dt_socket"

I change my jdk a few days ago, today I changed it back. then I find my IDEA can run but can't debug. Here are Console info:
D:\Java\64位JDK\bin\java -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:59301,suspend=y
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError= AGENT_ERROR_TRANSPORT_LOAD(196)
ERROR: transport library not found: dt_socket
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_LOAD(509)
JDWP exit error AGENT_ERROR_TRANSPORT_LOAD(196): No transports initialized [debugInit.c:750]
I guess the first line is command that IDEA used, but I find dt_spcket.dll in D:\Java\64位JDK\jre\bin (64位JDK means 64-bit ) not \Java\64位JDK\bin . I don't know am I right and how to correct the path or solve the problem?
I have solved the problem with #CrazyCoder 's help , out-of-ascii path isn't the reason.When I delete the system environment variable , i find "java" command is legal in cmd, so i think there is an other java environment in my computer. Use java -verbose i find the location and delete it then problem have solved. So if you meet the same problem, check the environment first.if not work , try to reinstall the jdk :)
I found out that the problem was the diffents Java versions in the App configuration1 and the project structure2, I solved the problem by simply changing to be same.

Error while upgrading sensu puppet module: Invalid parameter prefetch on sensu_rabbitmq_config

I'm trying to upgrade the sensu-puppet module and im getting an error when i run puppet now: the error is:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Invalid parameter prefetch on Sensurabbitmqconfig[<(hostname
is here, removed for this post on ask puppet)>] at
/etc/puppet/environments/staging/modules/sensu/manifests/rabbitmq/config.pp:123
Warning: Not using cache on failed catalog Error: Could not retrieve
catalog; skipping run
I have no idea what's going wrong or how to fix it. I looked in the pathway at the rabbitmq config and found this:
prefetch => $sensu::rabbitmq_prefetch
But I'm not sure what the issue is. Anyone know what might be causing this?
Where did you get the puppet module and what way?
Did you use puppet module install or a git pull?
Make sure sure that the parameter you want to use is in
modules/sensu/lib/puppet/provider/sensu_rabbitmq_config/json.rb
and also
modules/sensu/lib/puppet/type/sensu_rabbitmq_config.rb

Icinga2 object ApiUser is unknown

I need help understanding an error why I'm seeing an error.
The feature api is already enabled with the correct ApiListener object, and Api logs are being updated in /var/lib/icinga2/api/log/current .
But I'm getting this error when I restart icinga2:
Error: Error while evaluating expression: The type 'ApiUser' is unknown: in /etc/icinga2/conf.d/api-users.conf: 1:0-1:20
I'm running version r2.3.10-1 of Icinga2 on Ubuntu.
Can someone explain what the problem is?
You are probably mixing the current snapshot packages with the released stable versions. The 'ApiUser' object is part of the upcoming Icinga 2 v2.4 release and only available in git master (and therefore snapshot packages as well as docs). The stable 2.3.x tree does not have that kind of configuration object type and therefore bails out with an error.
Remove that file or its content, you don't need it for 2.3.x.

EPIPE error uploading img to s3 using imagesquish

I've been testing imagesquish for a while and I can't seem to have it working.
It works with node.js, forever, express and knox and basically does image processing on the fly.
I'm trying to call an image on a server, it resizes, crops or whatever and then uploads to s3.
I've had permission issues but after creating a new s3 bucket, it seems I made some progress but then, the image doesn't get uploaded and I can't get any error.
I managed to go through it's code and go all the way to exports.uploadImage that would call img.toBuffer but apparently it doesn't get called.
At the end, I get the error:
events.js:72
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at errnoException (net.js:904:11)
at Object.afterWrite (net.js:720:19)
error: Forever detected script exited with code: 8
error: Script restart attempt #1
I need some help on this. Does anybody have any idea?
Luis. Not sure if you're still interested in an answer to this. I'm the author of ImageSquish. From the information you provide, this sounds like img.toBuffer is failing which is usually because graphicsmagick is not installed. The latest version of ImageSquish checks for the existence of this library on startup (see https://github.com/dmcquay/imagesquish/blob/master/check.js).
You might also find it easier to try it out using docker (https://registry.hub.docker.com/u/dmcquay/imagesquish/) so you don't have to worry about installing anything.
If this doesn't resolve your problem, you can find me via irc on freenode #imagesquish.