Exception Using Master release (mono) with emacs-fsharp #331

paytonrules · 2019-01-29T03:27:08Z

I'm trying to build FSAutoComplete from master and use it with emacs-fsharp-mode, and it currently appears to throw an exception on loading fsharp files. I've got the exception information below:

Unexpected internal error. Please report at https://github.com/fsharp/FsAutoComplete/issues, attaching the exception information:
System.InvalidOperationException: object_op ---> System.EntryPointNotFoundException: SystemNative_RealPath
  at (wrapper managed-to-native) Interop+Sys.RealPath(string)
  at System.IO.CoreFX.FileSystemWatcher+RunningInstance.Start () [0x00000] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at System.IO.CoreFX.FileSystemWatcher.StartRaisingEvents () [0x00067] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at System.IO.CoreFX.FileSystemWatcher.StartRaisingEventsIfNotDisposed () [0x00019] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x0001d] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at (wrapper remoting-invoke-with-check) System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents(bool)
  at System.IO.CoreFXFileSystemWatcherProxy+<>c.<StartDispatching>b__9_0 (System.IO.CoreFX.FileSystemWatcher internal_fsw, System.IO.FileSystemWatcher fsw) [0x00048] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action‘4[T1,T2,T3,T4] map_op, System.Action‘2[T1,T2] object_op, System.Object handle, System.Action‘2[T1,T2] cancel_op) [0x00184] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
   --- End of inner exception stack trace ---
  at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action‘4[T1,T2,T3,T4] map_op, System.Action‘2[T1,T2] object_op, System.Object handle, System.Action‘2[T1,T2] cancel_op) [0x001a6] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at System.IO.CoreFXFileSystemWatcherProxy.StartDispatching (System.Object handle) [0x00004] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at System.IO.FileSystemWatcher.Start () [0x0001b] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at System.IO.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x0003d] in <783f9ec99b954b3081ca4c67bd3306c7>:0 
  at (wrapper remoting-invoke-with-check) System.IO.FileSystemWatcher.set_EnableRaisingEvents(bool)
  at FsAutoComplete.Project..ctor (System.String projectFile, Microsoft.FSharp.Core.FSharpFunc‘2[T,TResult] onChange) [0x000e2] in <59ba4889f78c97f6a74503838948ba59>:0 
  at <StartupCode$FsAutoComplete-Core>[email protected] (Microsoft.FSharp.Core.Unit _arg1) [0x00001] in <59ba4889f78c97f6a74503838948ba59>:0 
  at <StartupCode$FsAutoComplete-Core>[email protected] (Microsoft.FSharp.Core.Unit unitVar) [0x00043] in <59ba4889f78c97f6a74503838948ba59>:0 
  at Microsoft.FSharp.Control.AsyncBuilderImpl+callA@851[b,a].Invoke (Microsoft.FSharp.Control.AsyncParams‘1[T] args) [0x00047] in <561d4e1d904cf4daa74503831d4e1d56>:0

The text was updated successfully, but these errors were encountered:

luis3m · 2019-02-03T20:39:12Z

I got exactly the same error. Any update @paytonrules?

paytonrules · 2019-02-04T03:58:53Z

Not so far, but I haven't tried to debug much, at least not at the code level.

enricosada · 2019-02-21T09:24:29Z

hi @paytonrules @luis3m

what OS and mono version?

juergenhoetzel · 2019-03-04T18:10:15Z

I'm trying to build FSAutoComplete from master and use it with emacs-fsharp-mode, and it currently appears to throw an exception on loading fsharp files. I've got the exception information below:

I can't confirm this issue. I just did a build using make install ac_from_src=yes (fsharp/emacs-fsharp-mode#192).

Arch Linux
Mono 5.18.0

paytonrules · 2019-03-04T18:47:34Z

I'm currently using the release @juergenhoetzel made this morning and it's working great. I had given up trying to self-build (which is why I never got back to you @enricosada ).

I suspect I wasn't including all the necessary assemblies when moving fsautocomplete in with the emacs plugin.

enricosada · 2019-03-04T18:51:46Z

Np :)

I’ll check later with editor maintainers about how to allow easier testing of new FSAC builds

My idea is like:

get zip from ci/localbuild (both net/net core)
unzip in a dir and set an config/envvar to enable it

TOTBWF · 2019-04-19T00:24:39Z

I'm trying to build from master, also using emacs-fsharp-mode, and I'm getting the same error.

I'm using

OSX
mono 5.20

enricosada · 2019-04-19T13:01:56Z

@TOTBWF let me reopen this so.

I'll add now mono 5.20 to travis build matrix to check

@TOTBWF can you try run it in debug to check what is the issues? seems a file watcher failure, so dunno if will repro in ci

TOTBWF · 2019-04-19T17:24:39Z

I think this may have to do with the difference in-between the version of emacs-fsharp-mode on elpa (which comes from https://github.com/rneatherway/emacs-fsharp-mode-bin) and what building from source results in.

enricosada · 2019-04-19T17:27:19Z

that's strange, ideally emacs should:

or use FSAC as paket repo, and build LocalRelease and bundle built binaries
or use new releases. i think is fixed now after your PR

juergenhoetzel · 2019-04-19T17:39:20Z

I'm trying to build from master, also using emacs-fsharp-mode, and I'm getting the same error.

You are trying to build fsautocomplete.exe (i.e. this project) and get an build error?

Or you can successfully build but get the same runtime-exception as the OP when using it from within Emacs/fsharp-mode ?

I think this may have to do with the difference in-between the version of emacs-fsharp-mode on elpa

I suspect you mean melpa? fsharp-mode isn't on elpa.

(which comes from https://github.com/rneatherway/emacs-fsharp-mode-bin) and what building from source results in.

Coul'd you verify fsharp-mode is using the correct version of fsautocomplete.exe via flycheck-verify-setup?

fsharp-mode on melpa ships fsautocomplete-0.36.0.zip (I need to update).

TOTBWF · 2019-04-19T17:45:43Z

I was working on emacs-fsharp-mode, using the ac_from_src option in the makefile. However, I tried using the version from melpa, and I got the same issue. As for flycheck-verify-setup, it does appear to be using the correct version. Output is here:

  fsharp-fsautocomplete
    - may enable:                  yes
    - predicate:                   nil
    - FSharp.AutoComplete process: mono /Users/reedmullanix/.emacs.d/.local/packages/elpa/fsharp-mode-20190304.1317/bin/fsautocomplete.exe
    - F# Project:                  None
    - Loaded Projects:             No projects loaded

  fsharp-fsautocomplete-lint
    - may enable:                  yes
    - predicate:                   nil
    - FSharp.AutoComplete process: mono /Users/reedmullanix/.emacs.d/.local/packages/elpa/fsharp-mode-20190304.1317/bin/fsautocomplete.exe
    - F# Project:                  None
    - Loaded Projects:             No projects loaded

juergenhoetzel · 2019-04-19T17:51:01Z

I was working on emacs-fsharp-mode, using the ac_from_src option in the makefile. However, I tried using the version from melpa, and I got the same issue. As for flycheck-verify-setup, it does appear to be using the correct version. Output is here:

Would you mind sharing a minimal project designed to reproduce the error?

TOTBWF · 2019-04-19T18:01:22Z

It fails for every project, so any project ought to work.

TOTBWF · 2019-04-19T18:14:37Z

So it turns out that the version of mono installed via brew is subtly broken. Installing mono directly works.

paytonrules · 2019-05-04T03:50:30Z

@TOTBWF Can you clarify how mono is broken on the brew install?

kqr · 2019-05-21T13:03:59Z

@paytonrules do you have any suggestion on how I can check how it's broken? I had the same issue on Mono installed from homebrew, and managed to solve it by installing Mono from www.mono-project.com instead.

paytonrules · 2019-05-21T13:12:28Z

No clue - I did the same thing. The versions appear to be the same.

kqr · 2019-05-21T13:23:15Z

I have submitted this to Homebrew: Homebrew/homebrew-core#40138

If anyone knows how to reproduce in a more minimal example than the entire FSAC, please do contribute to that issue!

wanderley · 2019-05-31T16:15:23Z

I had the same problem in MacOS, and it was solved by installing mono from the official download page.

Krzysztof-Cieslak · 2019-06-13T09:36:38Z

@TOTBWF managed to get latest master working with emacs lsp-mode - emacs-lsp/lsp-mode#880

enricosada closed this as completed Mar 4, 2019

enricosada reopened this Apr 19, 2019

enricosada self-assigned this Apr 19, 2019

kqr mentioned this issue May 21, 2019

Add workaround for file watcher issue in FSAC on OS X fsharp/emacs-fsharp-mode#205

Closed

kqr mentioned this issue May 21, 2019

Issues with kqueue in Mono for filesystem watching on OS X 10.14.1 Homebrew/homebrew-core#40138

Closed

kqr mentioned this issue May 21, 2019

Fails loading project created with "dotnet new classlib -lang f#" fsharp/emacs-fsharp-mode#204

Open

Krzysztof-Cieslak closed this as completed Jun 13, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Exception Using Master release (mono) with emacs-fsharp #331

Exception Using Master release (mono) with emacs-fsharp #331

paytonrules commented Jan 29, 2019

luis3m commented Feb 3, 2019

paytonrules commented Feb 4, 2019

enricosada commented Feb 21, 2019

juergenhoetzel commented Mar 4, 2019

paytonrules commented Mar 4, 2019

enricosada commented Mar 4, 2019

TOTBWF commented Apr 19, 2019 •

edited

Loading

enricosada commented Apr 19, 2019 •

edited

Loading

TOTBWF commented Apr 19, 2019

enricosada commented Apr 19, 2019

juergenhoetzel commented Apr 19, 2019 •

edited

Loading

TOTBWF commented Apr 19, 2019

juergenhoetzel commented Apr 19, 2019

TOTBWF commented Apr 19, 2019 •

edited

Loading

TOTBWF commented Apr 19, 2019

paytonrules commented May 4, 2019

kqr commented May 21, 2019

paytonrules commented May 21, 2019

kqr commented May 21, 2019

wanderley commented May 31, 2019

Krzysztof-Cieslak commented Jun 13, 2019

Exception Using Master release (mono) with emacs-fsharp #331

Exception Using Master release (mono) with emacs-fsharp #331

Comments

paytonrules commented Jan 29, 2019

luis3m commented Feb 3, 2019

paytonrules commented Feb 4, 2019

enricosada commented Feb 21, 2019

juergenhoetzel commented Mar 4, 2019

paytonrules commented Mar 4, 2019

enricosada commented Mar 4, 2019

TOTBWF commented Apr 19, 2019 • edited Loading

enricosada commented Apr 19, 2019 • edited Loading

TOTBWF commented Apr 19, 2019

enricosada commented Apr 19, 2019

juergenhoetzel commented Apr 19, 2019 • edited Loading

TOTBWF commented Apr 19, 2019

juergenhoetzel commented Apr 19, 2019

TOTBWF commented Apr 19, 2019 • edited Loading

TOTBWF commented Apr 19, 2019

paytonrules commented May 4, 2019

kqr commented May 21, 2019

paytonrules commented May 21, 2019

kqr commented May 21, 2019

wanderley commented May 31, 2019

Krzysztof-Cieslak commented Jun 13, 2019

TOTBWF commented Apr 19, 2019 •

edited

Loading

enricosada commented Apr 19, 2019 •

edited

Loading

juergenhoetzel commented Apr 19, 2019 •

edited

Loading

TOTBWF commented Apr 19, 2019 •

edited

Loading