Sublime Forum

Dev Build 3131

#21

Ok I checked again given that it worked for you.
You are totally right that it indeed works on a vanilla download.
I did find another puzzle piece to trigger the issue: when I install the “PlainTasks” plugin, then it fails 100%. Now what exactly in that plugin is causing it I don’t know yet since it does not seem to store a string in the package data for that window but I’ll keep investigating. I did go back on the latest released version though and found that the issue does exist there too. (would you be willing to double check if you can trigger the bug with PlainTasks, and if so given that it’s also in the released build I guess I should move that problem out of the Dev Build 3131 section?)

0 Likes

#22

I can confirm that your code above works in pure vanilla as well as vanilla with PackageControl but fails when PlainTasks is installed. Seems like it is indeed an issue a weird interaction with PlainTasks and not 3131 related.

0 Likes

#23

Apologies, didn’t see the scroll bar in the code segment; I copied over the on_thread_done method.
Interestingly, I get something completely different now :smiley:

>>> view.window().run_command('repo_test')
36: [TID: 140736271856576] -> : RepoTestCommand
Traceback (most recent call last):
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 160, in <lambda>
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 168, in detect_syntax_change
AttributeError: 'NoneType' object has no attribute 'run_command'
49: [TID: 140736271856576] -> : constructor pd: id: 4436892672, type: <class 'str'>
Traceback (most recent call last):
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 160, in <lambda>
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 168, in detect_syntax_change
AttributeError: 'NoneType' object has no attribute 'run_command'
syntax is none for <sublime.Settings object at 0x10bbb92d0>
syntax is none for <sublime.Settings object at 0x10bbbbed0>
25: [TID: 123145413300224] -> : RepoThread.run
28: [TID: 140736271856576] -> : RepoThread.on_done
57: [TID: 140736271856576] -> : pd: way before: id: 4506760328, type: <class 'dict'>
61: [TID: 140736271856576] -> : pd: after set settings: id: 4506760328, type: <class 'dict'>
64: [TID: 140736271856576] -> : pd: after update settings: id: 4506760328, type: <class 'dict'>
Traceback (most recent call last):
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 160, in <lambda>
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 168, in detect_syntax_change
AttributeError: 'NoneType' object has no attribute 'run_command'
68: [TID: 140736271856576] -> : pd: after: id: 4436892672, type: <class 'str'>
Traceback (most recent call last):
  File "/Users/rwols/Library/Application Support/Sublime Text 3/Packages/User/RepoThread.py", line 29, in on_done
    self.on_finished_callback( self.item )
  File "/Users/rwols/Library/Application Support/Sublime Text 3/Packages/User/RepoThread.py", line 69, in on_thread_done
    project_settings = project_data[ "settings" ]
TypeError: string indices must be integers
Traceback (most recent call last):
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 160, in <lambda>
  File "ansi in /Users/rwols/Library/Application Support/Sublime Text 3/Installed Packages/ANSIescape.sublime-package", line 168, in detect_syntax_change
AttributeError: 'NoneType' object has no attribute 'run_command'
syntax is none for <sublime.Settings object at 0x10bbb92d0>
syntax is none for <sublime.Settings object at 0x10bbbbed0>
reloading /Users/rwols/dev/gintonic/gintonic.sublime-project
0 Likes

#24

Sorry for the late reply I was too busy in the last few days. In any case I’ve reduced the repo case as much as I could and posted the problem in the general tech support forum given that it also happens in the released version. Thanks everybody for double checking that it’s not something just on my end.

0 Likes