sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Public bug reported:

***************** problem

There MUST be some unicode characters be involved in the environment and
startup sequence in such a case.

The problem comes up at the edge between UTF-8 (Jython level) and UTF-16 (Java level) and according to the comments in the net is a common problem with implementations, that have to handle both worlds.
According to the spec, the unicode points U+D800 to U+DFFF are invalid as single character (you always need 2 of them).
So it surely is some Jython bug, that cannot arise with Jython 2.5, since this does not handle unicode internally at all.

So in case: use Jython 2.5 ;-)
--------------------------------

It turns out that I still get this error semi-frequently on startup.
Exactly the same command produces it perhaps 20% of the time I run it,
and it appears to be entirely random. The print out is as follows:

+++ running this Java
+++ trying to run SikuliX
+++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar C:\Users\e601429\sikulix1.1.0\sikulix.jar -r C:/Users/E601429/tmp.sikuli
[error] RunTimeIDE: *** terminating: JythonScriptRunner: cannot be initialized:
Traceback (most recent call last):
  File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\site.py", line 62, in <module>
  File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\os.py", line 59, in <module>
ValueError: unpaired surrogate 0xdc7e at code unit 691

What could be the cause of this? As discussed in the previous question,
I installed SikuliX using 64-bit Java but have since been running it
under 32-bit Java. All my SikuliX DLLs appear to be 32-bit now, but I
still have this problem. Will wiping my installation and reinstalling
with 32-bit Java help, do you think?

** Affects: sikuli
     Importance: Medium
     Assignee: RaiMan (raimund-hocke)
         Status: In Progress

** Changed in: sikuli
       Status: New => In Progress

** Changed in: sikuli
   Importance: Undecided => Medium

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

** Changed in: sikuli
    Milestone: None => 1.1.0

** Description changed:

- This is really a follow on to my previous question at
- https://answers.launchpad.net/sikuli/+question/264829
+ ***************** problem
+ 
+ There MUST be some unicode characters be involved in the environment and
+ startup sequence in such a case.
+ 
+ The problem comes up at the edge between UTF-8 (Jython level) and UTF-16 (Java level) and according to the comments in the net is a common problem with implementations, that have to handle both worlds.
+ According to the spec, the unicode points U+D800 to U+DFFF are invalid as single character (you always need 2 of them).
+ So it surely is some Jython bug, that cannot arise with Jython 2.5, since this does not handle unicode internally at all.
+ 
+ So in case: use Jython 2.5 ;-)
+ --------------------------------
  
  It turns out that I still get this error semi-frequently on startup.
  Exactly the same command produces it perhaps 20% of the time I run it,
  and it appears to be entirely random. The print out is as follows:
  
  +++ running this Java
  +++ trying to run SikuliX
  +++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar C:\Users\e601429\sikulix1.1.0\sikulix.jar -r C:/Users/E601429/tmp.sikuli
  [error] RunTimeIDE: *** terminating: JythonScriptRunner: cannot be initialized:
  Traceback (most recent call last):
-   File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\site.py", line 62, in <module>
-   File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\os.py", line 59, in <module>
+   File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\site.py", line 62, in <module>
+   File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\os.py", line 59, in <module>
  ValueError: unpaired surrogate 0xdc7e at code unit 691
  
  What could be the cause of this? As discussed in the previous question,
  I installed SikuliX using 64-bit Java but have since been running it
  under 32-bit Java. All my SikuliX DLLs appear to be 32-bit now, but I
  still have this problem. Will wiping my installation and reinstalling
  with 32-bit Java help, do you think?

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1450362

Title:
  [1.1.0] Jython 2.7: unicode problem: unpaired surrogate at start up in
  site.py (Windows only ????)

Status in Sikuli:
  In Progress

Bug description:
  ***************** problem

  There MUST be some unicode characters be involved in the environment
  and startup sequence in such a case.

  The problem comes up at the edge between UTF-8 (Jython level) and UTF-16 (Java level) and according to the comments in the net is a common problem with implementations, that have to handle both worlds.
  According to the spec, the unicode points U+D800 to U+DFFF are invalid as single character (you always need 2 of them).
  So it surely is some Jython bug, that cannot arise with Jython 2.5, since this does not handle unicode internally at all.

  So in case: use Jython 2.5 ;-)
  --------------------------------

  It turns out that I still get this error semi-frequently on startup.
  Exactly the same command produces it perhaps 20% of the time I run it,
  and it appears to be entirely random. The print out is as follows:

  +++ running this Java
  +++ trying to run SikuliX
  +++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar C:\Users\e601429\sikulix1.1.0\sikulix.jar -r C:/Users/E601429/tmp.sikuli
  [error] RunTimeIDE: *** terminating: JythonScriptRunner: cannot be initialized:
  Traceback (most recent call last):
    File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\site.py", line 62, in <module>
    File "C:\Users\e601429\sikulix1.1.0\sikulix.jar\Lib\os.py", line 59, in <module>
  ValueError: unpaired surrogate 0xdc7e at code unit 691

  What could be the cause of this? As discussed in the previous
  question, I installed SikuliX using 64-bit Java but have since been
  running it under 32-bit Java. All my SikuliX DLLs appear to be 32-bit
  now, but I still have this problem. Will wiping my installation and
  reinstalling with 32-bit Java help, do you think?

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1450362/+subscriptions