Jamovi failed to show a plot - r

Some laptop with a Hebrew user name failed to show plots in Descriptive in Jamovi 2.3.18
I opened Jamovi in debug mode and saw the following messages:
jamovi.server.server - listening across origin(s): 127.0.0.1:64652 127.0.0.1:64653 127.0.0.1:64654
jamovi.server.server - jamovi accessible from: 127.0.0.1:64652/?access_key=7b76b6f8ad9441a1889886c42ebce92c
ports: 64652, 64653, 64654, access_key: 7b76b6f8ad9441a1889886c42ebce92c
jamovi.server.session - creating instance: f25af653-5baf-47a5-9cc0-1018aa45d1c4
instance_started f25af653-5baf-47a5-9cc0-1018aa45d1c4
jamovi.server.session - creating instance: 4d3d54e2-6d7f-4dca-a18c-14ac6b98bf8c
instance_started 4d3d54e2-6d7f-4dca-a18c-14ac6b98bf8c
jamovi.server.session - destroying instance: f25af653-5baf-47a5-9cc0-1018aa45d1c4
instance_ended f25af653-5baf-47a5-9cc0-1018aa45d1c4
Uncaught exception GET /4d3d54e2-6d7f-4dca-a18c-14ac6b98bf8c/2/res/02%20descriptives/resources/14e8622d253285f2.png (127.0.0.1)
HTTPServerRequest(protocol='http', host='127.0.0.1:64654', method='GET', uri='/4d3d54e2-6d7f-4dca-a18c-14ac6b98bf8c/2/res/02%20descriptives/resources/14e8622d253285f2.png', version='HTTP/1.1', remote_ip='127.0.0.1')
Traceback (most recent call last):
File "C:\Program Files\jamovi 2.3.18.0\bin\Lib/site-packages\tornado\web.py", line 1590, in _execute
result = method(*self.path_args, **self.path_kwargs)
File "jamovi\Resources\jamovi\server\jamovi\server\server.py", line 120, in get
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\╫נ╫ץ╫¿╫ש╫ש╫ƒ\\AppData\\Local\\Temp\\tmp0hr7g53g\\916e0323-151c-4d63-a10d-299c3a256f42\\4d3d54e2-6d7f-4dca-a18c-14ac6b98bf8c/02 descriptives/resources/14e8622d253285f2.png'
500 GET /4d3d54e2-6d7f-4dca-a18c-14ac6b98bf8c/2/res/02%20descriptives/resources/14e8622d253285f2.png (127.0.0.1) 0.00ms
I suspect the failure to see the plot is caused by the Hebrew user name. Would appreciate your advice on how to handle this.

The gist of your problem seems to be directly related to this error message:
No such file or directory: 'C:\\Users\\╫נ╫ץ╫¿╫ש╫ש╫ƒ\\AppData\\Local\\Temp\\tmp0hr7g53g\\916e0323-151c-4d63-a10d-299c3a256f42\\4d3d54e2-6d7f-4dca-a18c-14ac6b98bf8c/02 descriptives/resources/14e8622d253285f2.png'
There are likely two reasons for this problem:
Jamovi cannot find this folder, because it has been modified in some way since the file was originally created.
It could be that because the file is named in Hebrew, it may not parse
the string correctly when loading through Jamovi. If this is the
case, you could consider simply renaming the directory and seeing if
that alleviates the issue. Johnathon Love in fact mentions this
as a potential issue in Jamovi/R at times.

Related

How can I solve the error for crawling send mail data in r?

I tried to crawl my email data by using 'edeR' package.
I succeeded in getting 'inbox' folder, but failed to get 'sent mail'.
Here are the codes.
Sys.setenv(JAVA_HOME="C:/Program Files/Java/jre1.8.0_121")
library(rJava)
library(edeR)
mail_sen<-extractBetween(username="xxxx#gmail.com",
password="xxxxx", folder="[Gmail]/Sent Mail",
startDate="06-Jan-2017", endDate="06-Mar-2017", nmail=5)
When I change (folder="[Gmail]/Sent Mail") into (folder="inbox"), it works.
However, when I use the code above, error comes.
Error in .jcall("RJavaTools", "Ljava/lang/Object;", "invokeMethod", cl, :
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "C:\Program Files\Java\jre1.8.0_121\lib\ext\jython.jar\Lib\imaplib.py", line 749, in uid
imaplib.error: command SEARCH illegal in state AUTH
I'm stuck in this error...
Anyone who can solve this problem?
the error is not very informative but this post suggests it means that it can't find your folder: edeR seems to be a wrapper around the imaplib Python library that is referenced in that question. According to the answers, the name of the "Sent Mail" folder is language-dependent.
So i think you might have to try different translations of "Sent Mail" in folder="[Gmail]/Sent Mail"
eta: i do not recommend changing your gmail language settings to see what happens to the "Sent Mail" folder name to a language you do not speak. I just spent five minutes finding out which option under the little cogwheel in gmail meant "settings" in Bahasa Indonesia.

TypeError: Expected bytes While printing Any Report Using Client Database in OpenERP 7.0

I am using Client Database and it will be restored successfully in my local system and working fine but when I am printing any report the within that database at that time.
I got the below traceback from the terminal.
Traceback (most recent call last):
File "/home/best/workspace/dynaweld/web/addons/web/http.py", line 285, in dispatch
r = method(self, **self.params)
File "/home/best/workspace/dynaweld/web/addons/web/controllers/main.py", line 1769, in index
cookies={'fileToken': int(token)})
File "/home/best/workspace/dynaweld/web/addons/web/http.py", line 332, in make_response
response.set_cookie(k, v)
File "/usr/local/lib/python2.7/dist-packages/Werkzeug-0.10.4-py2.7.egg/werkzeug/wrappers.py", line 1008, in set_cookie
self.charset))
File "/usr/local/lib/python2.7/dist-packages/Werkzeug-0.10.4-py2.7.egg/werkzeug/http.py", line 920, in dump_cookie
value = to_bytes(value, charset)
File "/usr/local/lib/python2.7/dist-packages/Werkzeug-0.10.4-py2.7.egg/werkzeug/_compat.py", line 106, in to_bytes
raise TypeError('Expected bytes')
TypeError: Expected bytes
I have tried the following way to resolve above traceback issue but I have not yet succeed.
1. Try remove the unwanted data from my local client database remove the all the data of mail.message object.
2. Remove all the unnecessary database from my system and using only 2-3 database for my OpenERP Server Run.
3. Clean my pc for unwanted files and other detail which was not relevant for my database.
4. I have also check with my enough memory space but I have that enough space for restoring that database file.
Can any one help me how can i fix this issue.
This is because cookies are not intended to support unicode characters, you must use a decoded variable in the cookie you are trying to set. something like :
set_cookie(k, bytes(v))
or at least send your variable as bytes.
I have fixed this by installing an older version of werkzeug, 0.6.2

Swift Juno complains 'Account not found'

I'm new to stack so this might be a very silly mistake.
I'm trying to setup a one node swift configuration for a simple proof of concept. I did follow the instructions. However, something is missing. I keep getting this error:
root#lab-srv2544:/etc/swift# swift stat
Traceback (most recent call last):
File "/usr/bin/swift", line 10, in <module>
sys.exit(main())
File "/usr/lib/python2.7/dist-packages/swiftclient/shell.py", line 1287, in main
globals()['st_%s' % args[0]](parser, argv[1:], output)
File "/usr/lib/python2.7/dist-packages/swiftclient/shell.py", line 492, in st_stat
stat_result = swift.stat()
File "/usr/lib/python2.7/dist-packages/swiftclient/service.py", line 427, in stat
raise SwiftError('Account not found', exc=err)
swiftclient.service.SwiftError: 'Account not found'
Also, the syslog always complains about proxy-server:
Dec 12 12:16:37 lab-srv2544 proxy-server: Account HEAD returning 503 for [] (txn: tx9536949d19d14f1ab5d8d-00548b4d25) (client_ip: 127.0.0.1)
Dec 12 12:16:37 lab-srv2544 proxy-server: 127.0.0.1 127.0.0.1 12/Dec/2014/20/16/37 HEAD /v1/AUTH_71e79a29599149099aa98d5d276eaa0b HTTP/1.0 503 - python-swiftclient-2.3.0 8d2b0748804f4b34... - - - tx9536949d19d14f1ab5d8d-00548b4d25 - 0.0013 - - 1418415397.334497929 1418415397.335824013
Anyone seen this problem before?
When using 'swift' command to access swift storage, pass user id and password as argument, if it is not set in environment variable.
The most probable reason for this behavior is a funny order in your "pipeline" directive in /etc/swift/proxy-server.conf
To verify this hypothesis:
comment out your current pipeline, and write this one instead:
pipeline = authtoken cache healthcheck keystoneauth proxy-logging proxy-server
restart your proxy server with the command
swift-init proxy-server restart
Make sure the environment variables OS_USERNAME, OS_PASSWORD, OS_TENANT_NAME and OS_AUTH_URL are defined
try to list your containers with
swift list
If you get a list of containers then the diagnoses is correct.
Get back to your proxy-server.conf and try to add one element per time to your pipeline, restarting the server each time, and testing each time, until you find the right order.
For your reference see http://docs.openstack.org/developer/swift/deployment_guide.html#proxy-server-configuration

Getting Error in config.txt file of NetSim Simulator

When I open NetSim's Config.txt file after Simulation I get the following error:
Error in config file ---
1) Unknown xml tag "UPDATE_TIMER" in line number 166.
Tag path: TETCOS_NETSIM/NETWORK_CONFIGURATION/DEVICE_CONFIGURATION/DEVICE
[3] /LAYER [2]/ROUTING_PROTOCOL/PROTOCOL_PROPERTY
However, Simulation runs Successfully. What does this mean?
You need to specify the missing parameters in the Configuration file which are mentioned in the "ConfigLog.txt". Since, NetSim will crash if all the required parameters are not configured, NetSim addresses this issue by enabling default values where ever required. Error produced in the "ConfigLog.txt" because the value for the "UPDATE_TIMER" for "ROUTING_PROTOCOL" is not specified in the Configuration file. In order to obtain accurate metrics for the desired scenario you need to update your Configuration.xml file.

Can you make R print more detailed error messages?

I've often been frustrated by R's cryptic error messages. I'm not talking about during an interactive session, I mean when you're running a script. Error messages don't print out line numbers, and it's often hard to trace the offending line, and the reason for the error (even if you can find the location).
Most recently my R script failed with the the incredibly insightful message: "Execution halted." The way I usually trace such errors is by putting a lot of print statements throughout the script -- but this is a pain. I sometimes have to go through the script line by line in an interactive session to find the error.
Does anyone have a better solution for how to make R error output more informative?
EDIT: Many R-debugging things work for interactive sessions. I'm looking for help on command-line scripts run through Rscript. I'm not in the middle of an R session when the error happens, I'm at the bash shell. I can't run "traceback()"
Try some of the suggestions in this post:
General suggestions for debugging in R
Specifically, findLineNum() and traceback()/setBreakpoint().
#Nathan Well add this line sink(stdout(), type="message") at the beginning of the script and you should get in console message both script content and output along with error message so you can see it as in interactive mode in the console. (you can then also redirect to a log file if you prefer keeping the console "clean")
Have a look at my package tryCatchLog (https://github.com/aryoda/tryCatchLog).
While it is impossible to improve the R error messages directly you can save a lot of time by identifying the exact code line of the error and have actual variables at the moment of the error stored in a dump for "post mortem" analysis!
The main advantages of the tryCatchLog function over tryCatch are
easy logging of errors, warnings and messages into a file or console
warnings do not stop the program execution (tryCatch stops the execution if you pass a warning handler function)
identifies the source of errors and warnings by logging a stack trace with a reference to the source file name and line number (since traceback does not contain the full stack trace)
allows post-mortem analysis after errors by creating a dump file with all variables of the global environment (workspace) and each function called (via dump.frames) - very helpful for batch jobs that you cannot debug on the server directly to reproduce the error!
This will show a more detailed traceback, but not the line number:
options(error = function() {traceback(2, max.lines=100); if(!interactive()) quit(save="no", status=1, runLast=T)})
One way inside a script to get more info on where the error occurred is to redirect R message to the same stream as errors :
sink(stdout(), type="message")
This way you get both messages and errors in the same output so you see which line raised the error...

Resources