-
Notifications
You must be signed in to change notification settings - Fork 7
Resource temporarily unavailable on Windows #77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its m 10000 aintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks. Do you get it if you restart the computer? |
Same as #75 (comment). |
I am seeing this again after upgrade to latest as of today. |
Looking into it. I'm actually about to roll out a new version for both org-node and el-job. (where org-node gets features mentioned in #74.) Maybe that'll magically fix it. One reason is that it will not keepalive the subprocesses anymore, which sounds related to this error. Sorry for the inconvenience! A shot in the dark, but maybe you can eval this (it's just adding a (defun org-node--scan-all ()
"Arrange a full scan."
(unless (el-job-is-busy 'org-node)
(setq org-node--time-at-begin-full-scan (time-convert nil t))
(el-job-launch
:id 'org-node
:if-busy 'noop
:inject-vars (append org-node-inject-variables (org-node--mk-work-vars))
:load 'org-node-parser
:eval-once "(org-node-parser--init)"
:funcall #'org-node-parser--collect-dangerously
:inputs #'org-node-list-files
:wrapup #'org-node--finalize-full
:method 'reap))) |
Well, unless -- if you're still running Emacs 29.4 then it already uses |
It's odd because nothing has really changed for months in either el-job nor how org-node calls it. Just to check, you've restarted after upgrade? |
This issue may be fixed in this commit: emacs-mirror/emacs@e02466a |
Hope so! Thanks for link. |
@TomoeMami thanks for the heads-up! @meedstrom sorry for the late reply and thanks for looking into it. It does not affect me too much and I am looking forward to #74. Your call whether to keep this open or close and re-open in case. |
No worries. Others may have the same issue, so I'll keep it open. |
After upgrade today, on opening an Org mode buffer I see the backtrace below. I realize this might be related to my setup similar to #75. Just putting it out as another data point for Windows compatibility.
The text was updated successfully, but these errors were encountered: