Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Supported by

Extension update_checker misbehaved on event startup (see debug window for stack trace)

edited February 2017 in OpenSesame

Edit by @Sebastiaan: If you see this error, update to OpenSesame 3.1.5.

Hi everyone!

I've just installed OpenSesame. When starting the program, I receive the folowing error message: "Extension update_checker misbehaved on event startup (see debug window for stack trace)."

Does anyone know how I can solve the problem?

Best regards,
Bruno

Comments

  • Hi Bruno,

    Would you mind providing a bit more information?

    • What version of OpenSesame are you running? You can see this in the bottom-right of the Welcome tab.
    • What operating system are you using exactly?
    • Could you post the stacktrace here. You will find that in the debug window.

    And don't worry: You can safely click away the error, which only affects this one extension, and continue using OpenSesame.

    Cheers,
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • edited November 2016

    Hi Sebastiaan,

    I am running OpenSesame 3.1.3 Jazzy James. I am using Windows 7. This is the stacktrace:

    Python 2.7.12

    • Type "help()", "copyright()", "credits()" or "license()" for more information.
    • Use the "print([msg])" function in inline_script items to print to this debug window.
    • Inspect inline_script variables when an experiment is finished.

    Extension error

    item-stack: 
    exception message: 'ascii' codec can't decode byte 0xc3 in position 13: ordinal not in range(128)
    time: Mon Nov 21 23:31:57 2016
    exception type: UnicodeDecodeError
    
    Traceback:
      File "C:\Program Files\OpenSesame\lib\site-packages\libqtopensesame\extensions\_extension_manager.py", line 133, in fire
        ext.fire(event, **kwdict)
      File "C:\Program Files\OpenSesame\lib\site-packages\libqtopensesame\extensions\_base_extension.py", line 386, in fire
        getattr(self, u'event_%s' % event)(**kwdict)
      File "C:\Program Files\OpenSesame\lib\site-packages\share\opensesame_extensions\update_checker\update_checker.py", line 36, in event_startup
        self.check_for_updates(always=False)
      File "C:\Program Files\OpenSesame\lib\site-packages\share\opensesame_extensions\update_checker\update_checker.py", line 85, in check_for_updates
        title=u'Update available!')
      File "C:\Program Files\OpenSesame\lib\site-packages\libqtopensesame\widgets\tab_widget.py", line 456, in open_markdown
        if md.endswith(u'.md'):
    UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 13: ordinal not in range(128)
    

    Thank you so much for your help!

  • This is how the program looks like when I open it. As you can see there is missing something in the top left. After clicking away the error the issue remains.

  • Hi Bruno,

    Thanks for reporting this, I filed an issue (#484) for it. It's a problem because of the non-ascii characters in the German translation.

    If you update to 3.1.4 the problem will go away (at least until the next time that an update is available!). Or you can disable the update_checker extension under Menu → Tools → Plugin and extension manager.

    Cheers!
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • Hi Sebastiaan,

    I can't disable the update checker because the empty window in the top left overlaps the tool button. Could you send me the link for Opensesame 3.1.4, please? On your website I can only find the version 3.1.3.

    Thank you so much for your support!

    Bruno

  • On your website I can only find the version 3.1.3.

    Refresh the page!

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • edited February 2017

    Hello!

    First of all, very nice software !

    However, I have a small problem. I have the Version 3.1.4 running on my PC. I had the same error message, and the same problem as BrunoRichter with a weird window that prevents me from doing anything on the Menu.
    I uninstalled OpenSesam and re-installed it, but the same problem persists :-/

    Can you help me please?

    Thank you very much!
    Céline

  • Hi Céline,

    This bug is triggered now, because I just released 3.1.5, and OpenSesame chokes when trying to inform you of the update.

    If you just download 3.1.5, the problem will go away. And because this is one of the bugs fixed in 3.1.5, it won't come back either.

    Cheers,
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • Thank you !!

    But... I can't install the new version! :'(

    thx!
    Céline

  • PS I uninstalled Version 1.3.4 before trying again to install version 1.3.5 .

  • But... I can't install the new version! :'(

    Why not? Please explain what exactly tried and why it doesn't work!

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • I had the problem I mentioned earlier. I wanted to install version 1.3.5, and... just nothing happens !

    I am using Windows 7 - 32bits.

  • edited February 2017

    With 'exactly', I mean a description along these lines:

    • I downloaded this-and-this package (i.e. the .exe installer or the .zip, the Python 2 or Python 3 version)
    • Then I double-clicked on it
    • And then: I received an error message such-as-and-such or the computer asked for an administrator password which I don't know or nothing happens (as in really nothing whatsoever happened)

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • edited February 2017

    OK OK

    • I downloaded the 1.3.5 installer

    • I uninstalled version 1.3.4
    • I doubled-clicked on the 1.3.5 installer
    • and the system is "searching for" what it has to do but nothing happens except the "aero busy mouse pointer"

    Hope this is clear enough? :p
    I can't do better...

  • Ah, ok, so your browser doesn't start the download. There can be any number of reasons for this, but it's probably some security measure that blocks the download. Another browser?

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • OK I try without security. Thank you !

  • That works !! Great, thank you very much!

    Céline

  • Cheers Sebastiaan,

    i have got an experiment running on several laptops of the volunteers at the moment.
    Actually i was already waiting for this update problem for a long time already ;)
    Now that it's there, it is even a little worse.

    1. I have got no problem with windows, as we start it with opensesamerun :smile:

    2. Other with the Apple Users. As far as i see you withdraw the update for the Macs. Hence, we cannot even install the new version. Which is a real problem. :(

    Any suggestions?

  • Other with the Apple Users. As far as i see you withdraw the update for the Macs. Hence, we cannot even install the new version. Which is a real problem. :(

    There seemed to be a problem with the packaging of expyriment in the 3.1.5 Mac package. So until we've figured out what's wrong here, I've rolled back the link on the download page. You can still grab it from GitHub though:

    It would be very helpful for us if you'd download the 3.1.5 Mac OS package from GitHub, and let us know whether you experience the same issue as described here:

    Cheers!
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • edited March 26

    Hello,

    For information, same issue with OpenSesame 3.2 run on Ubuntu 14.04.5 LTS.

    I wasn't able to find a proper solution, so I worked my way around by installing the Windows 3.2 version and run it on Linux. The issue is not present in this case.

    EDIT: (using Wine) I clicked on QuickRun for a very simple experiment (loop, sequence, one empty display lasting 1000ms, one display with a circle, and a python code randomizing the location of the circle on the display). I had gone that far when I tried running it, but it showed a bug 'Oops, I did it again'. However, the whole window froze and I am not able to scroll down to read the Traceback.

    Sincerely,
    Gabriel

  • Hi Gabriel,

    There are two separate issues here.

    The first error that you get on Linux is indeed the same error as reported above, which has been fixed in recent versions of OpenSesame. So updating should resolve the issue. (I'm not sure which version you're running but I can tell from the screenshot that it's not 3.2.)

    The second error that you get within Wine could be anything. Wine is an interesting concept, but also fragile and finicky, and I would not recommend trying to run OpenSesame experiments within a Wine environment!

    Cheers!
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • Hello,

    Same issue for me on opensesame 3.2.4 on windows.

    I have a special character I display (÷). When it is displayed I get the error:

    "Extension variable_inspector misbehaved on event end_experiment (see debug window for stack trace)"

    and on the terminal

    UnicodeEncodeError: 'ascii' codec can't encode character u'\xf7' in position 436: ordinal not in range(128)

  • Hi Sylvain,

    Is that all you see in the debug window? There should be a full stacktrace.

    Cheers!
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • edited April 20

    Hey Sebastiaan,

    Here is the full backtrace

    Traceback:
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libqtopensesame\misc\process.py", line 154, in run
        exp.run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\experiment.py", line 449, in run
        self.items.execute(self.var.start)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 103, in execute
        self.run(name)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 122, in run
        self[name].run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\sequence.py", line 51, in run
        self.experiment.items.run(_item)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 122, in run
        self[name].run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\sequence.py", line 51, in run
        self.experiment.items.run(_item)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 122, in run
        self[name].run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\loop.py", line 341, in run
        self.experiment.items.execute(self._item)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 103, in execute
        self.run(name)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 122, in run
        self[name].run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\sequence.py", line 51, in run
        self.experiment.items.run(_item)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 122, in run
        self[name].run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\loop.py", line 341, in run
        self.experiment.items.execute(self._item)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 103, in execute
        self.run(name)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 122, in run
        self[name].run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\sequence.py", line 51, in run
        self.experiment.items.run(_item)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\item_store.py", line 122, in run
        self[name].run()
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\logger.py", line 56, in run
        self.experiment.log.write_vars(self._logvars)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\openexp\_log\csv.py", line 79, in write_vars
        val = safe_decode(val)
      File "C:\Program Files (x86)\OpenSesame\lib\site-packages\libopensesame\py3compat.py", line 56, in safe_decode
        return str(s)
    UnicodeEncodeError: 'ascii' codec can't encode character u'\xf7' in position 350: ordinal not in range(128)
    

    Just this little inline at the very beginning of the script solved the issue however:

    import sys
    reload(sys)
    sys.setdefaultencoding('utf-8')
    
  • edited April 20

    Hi Sylvain,

    That's an interesting error. I suspect you've set an unusual type of object as an experimental variable, maybe an Exception object or something like that. Can you give an example script that triggers this error?

    Cheers!
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

  • Hey Sebastian!

    Yes it is an error happening when I try to use this division charater : ÷
    For some reasons I have trouble replicating the issue with a shortened version of what I did but what I can say is:

    • I loaded operations such as (2÷2) and so on in a numpy array. The type of every cell is then numpy unicode;
    • then I place these operations (op1_str) in a datamatrix (dmStim) with for instance dmStim.Operation1[i] = op1_str
    • the odd thing is that if I combine various operation, with for instance op1_str = (2÷2), op2_str =3, and I want to create another operation such as (2÷2) + 3 = , by using op_concat = op1_str + '+' + op2_str then it does not generate any error!

    I do not know it is so odd because I tried to replicate the error in a simple script and I have not been able to get it.

    Sylvain

  • Hi Sylvain,

    The error itself comes from the logger item, when it's trying to write something to file. If you add a logger to your test scripts, are you then able to reproduce the error?

    Cheers!
    Sebastiaan

    There's much bigger issues in the world, I know. But I first have to take care of the world I know.
    cogsci.nl/smathot

Sign In or Register to comment.