Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers 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

request-backend set to 'curl causes error (wrong-type-argument number-or-marker-p nil) #490

Open
danielkrizian opened this issue Feb 21, 2019 · 5 comments

Comments

@danielkrizian
Copy link

Hi, I just wanted to report/share an observation that when request-backend is set to 'curl, following error is thrown every time I move up/down the c++-mode buffer and Emacs freezes until I press C-g (making it unfeasible to use ycmd).

I narrowed the triggering condition down to simply calling (ycmd-semantic-completer-available-p)

Backtrace:

ebugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)                                                                                
  request--curl-callback(#<process request curl> "finished\n")                                                                                            
  accept-process-output(nil 0.01)                                                                                                                         
  ycmd-deferred:sync!(#s(deferred :callback #f(compiled-function (response) #<bytecode 0x1145e2d>) :errorback deferred:default-errorback :cancel deferred      $
  ycmd--send-completer-available-request(c++-mode)                                                                                                        
  ycmd-semantic-completer-available-p()                                                                                                                   
  eval((ycmd-semantic-completer-available-p) nil)                                                                                                         
  eval-expression((ycmd-semantic-completer-available-p) nil nil 127)                                                                                      
  funcall-interactively(eval-expression (ycmd-semantic-completer-available-p) nil nil 127)                                                                
  call-interactively(eval-expression nil nil)                                                                                                             
  command-execute(eval-expression) 

Workaround:
When I set request-backend to 'url-retrieve, error no longer pops up and ycmd works as expected.

Question:
What would be the fix to allow me to use 'curl as request-backend ? Thanks


I have Emacs 26.1 and Spacemacs 0.300.0 (develop branch) on Debian Jessie.

@danielkrizian danielkrizian changed the title request-backend set to 'curl causes error (wrong-type-argument number-or-marker-p nil) request-backend set to 'curl causes error (wrong-type-argument number-or-marker-p nil) Feb 21, 2019
@luluman
Copy link

luluman commented Jul 7, 2019

Yes, the same issue to me.

@abingham
Copy link
Owner

abingham commented Jul 7, 2019

I'm no longer maintaining this project. Sorry.

@luluman
Copy link

luluman commented Jul 7, 2019

I'm sorry to hear that. But thanks a lot for your great work on this project. Emacs-ycmd is amazingly fast, stable and easy to get started. Also, the plugins, such as company-ycmd, flycheck-ycmd, eldoc-ycmd, you provided make Ycmd works together with other great projects seamlessly. I have got a lot of help from this project, so thanks again.

@dvzubarev
Copy link

I think it is related with this issue tkf/emacs-request#157

@dickmao
Copy link

dickmao commented Nov 12, 2019

tkf/emacs-request#85 (comment)

This is continued fallout from an indiscretion some months ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants