linting

Author: bollwyvl

atest/Keywords.robot

@@ -72,8 +72,8 @@ Lab Log Should Not Contain Known Error Messages
     ${test log} =    Set Variable    ${log[${PREVIOUS LAB LOG LENGTH}:]}
     ${length} =    Get Length    ${log}
     Set Global Variable    ${PREVIOUS LAB LOG LENGTH}    ${length}
-    Run Keyword If  ("${OS}", "${PY}") !\= ("Windows", "36")
-    ...     Should Not Contain Any    ${test log}    @{KNOWN BAD ERRORS}
+    Run Keyword If    ("${OS}", "${PY}") !\= ("Windows", "36")
+    ...    Should Not Contain Any    ${test log}    @{KNOWN BAD ERRORS}
 
 Wait For Splash
     Go To    ${URL}lab?reset&token=${TOKEN}

scripts/atest.py

@@ -29,7 +29,7 @@
     # everything else: https://github.com/krassowski/jupyterlab-lsp/pull/245
     ["language:yaml", "feature:config"],
     # TODO: restore when we figure out win36 vs jedi on windows
-    ["language:python", "py:36", "os:windows"]
+    ["language:python", "py:36", "os:windows"],
 ]
 
 

scripts/jedi_cache.py

@@ -8,22 +8,22 @@
   dependencies
 
 why is this needed:
-- Before we had this, a couple of browser tests appeared 
-  "consistently flakier" than they were, as they were 
+- Before we had this, a couple of browser tests appeared
+  "consistently flakier" than they were, as they were
   time-bounded by creating the jedi cache.
-- This was taking up to a minute to get a single 
+- This was taking up to a minute to get a single
   completion value back
-- Further, were this cache to get corrupted (perhaps due to 
+- Further, were this cache to get corrupted (perhaps due to
   killing a running test :P) things go very mysteriously bad.
 - We need a way for the cache to be right before testing
 
 how does it work:
 - When _using_ jedi for the first time, the cache gets
-  created in  `jedi.settings.cache_directory`, usually 
-  somewhere in $HOME. 
-- As different libriraries are inspected by jedi, they get 
-  added to the cache. 
-- This is very slow, especially on windows, and cannot 
+  created in  `jedi.settings.cache_directory`, usually
+  somewhere in $HOME.
+- As different libriraries are inspected by jedi, they get
+  added to the cache.
+- This is very slow, especially on windows, and cannot
   feasibly be cached, today.
 - This script accelerates this process, so it can be done
   in a controlled manner rather than during some other test