!!MISSING: command!! is intermittently displayed instead of type class function signatures

Your environment

Which OS do you use?

Macbook Air M2 15" (Ventura 13.6)
Intel x86_64 (Ubuntu 20.04.6 LTS)

Same issue on both systems.

Which version of GHC do you use and how did you install it?

Installed with ghcup:

$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 9.6.3

$ cabal --version
cabal-install version 3.10.1.0
compiled using version 3.10.1.0 of the Cabal library

How is your project built (alternative: link to the project)?

https://github.com/konnik/haskell-json-parser

Which LSP client (editor/plugin) do you use?

VSCode + haskell.haskell

Which version of HLS do you use and how did you install it?

$ haskell-language-server-wrapper --version
haskell-language-server version: 2.3.0.0 (GHC: 9.2.8) (PATH: /Users/niklas/.ghcup/hls/2.3.0.0/lib/haskell-language-server-2.3.0.0/bin/haskell-language-server-wrapper)

Installed by ghcup

Have you configured HLS in any way (especially: a hie.yaml file)?

no

Steps to reproduce

Really don't know how to reproduce it. It's very intermittent and resolves itself.

Expected behaviour

The code lens (don't know if this is the correct termiology) in vscode should show the type class signatures on my instance:

instance Monad Parser where
    return :: a -> Parser a             // this is shown by vscode, not part of the source
    return = pure
    (>>=) :: Parser a -> (a -> Parser b) -> Parser b                   // this is shown by vscode, not part of the source
    pa >>= fab = Parser $ \input -> do
        (input', a) <- runParser pa input
        runParser (fab a) input'

Actual behaviour

instance Monad Parser where
    !!MISSING: command!!            // this is shown by vscode, not part of the source
    return = pure
    !!MISSING: command!!                  // this is shown by vscode, not part of the source
    pa >>= fab = Parser $ \input -> do
        (input', a) <- runParser pa input
        runParser (fab a) input'

If i click on the text "!!MISSING: command!!" the error message "command 'missing' not found" is shown in bottom right of vscode

Debug information

Some things from the logs. Don't know if its relevant:

2023-10-03T17:41:54.161080Z | Info | Typechecking reverse dependencies for NormalizedFilePath "/Users/niklas/devel/haskell-json-parser/src/Json.hs": [ NormalizedFilePath "/Users/niklas/devel/haskell-json-parser/test/Test.hs" ]
2023-10-03T17:42:08.500584Z | Warning | Typechecked a file which is not currently open in the editor: /Users/niklas/devel/haskell-json-parser/src/Json.hs
This can indicate a bug which results in excessive memory usage.
This may be a spurious warning if you have recently closed the file.
If you haven't opened this file recently, please file a report on the issue tracker mentioning the HLS version being used, the plugins enabled, and if

Ok, have made some more investigations and found this in the server logs (verbose):

2023-10-03T18:15:13.162899Z | Info | Live bytes: 71.49MB Heap size: 743.44MB
[Trace - 20:15:15] Sending request 'codeLens/resolve - (280)'.
Params: {
    "range": {
        "start": {
            "line": 46,
            "character": 4
        },
        "end": {
            "line": 46,
            "character": 53
        }
    },
    "data": {
        "resolvePlugin": "class",
        "resolveURI": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs",
        "resolveValue": 1658
    }
}


[Trace - 20:15:15] Received response 'codeLens/resolve - (280)' in 4ms. Request failed: class: Stale Resolve (-32801).

I'm not able to reproduce it consistently yet but the issue seems to occur more often when I constantly scroll the source from top to bottom and back.

Here is a longer part of the log. I'm not sure but it seems that the issue occurs in combination of:

makes small change
save with ctrl-s
formatOnSave triggers formatting of source file
scroll source to move a code lens into view



[Trace - 20:23:16] Received response 'codeLens/resolve - (338)' in 5ms.
Result: {
    "command": {
        "arguments": [
            {
                "commandEdit": {
                    "newText": "pure :: a -> Parser a\n    ",
                    "range": {
                        "end": {
                            "character": 4,
                            "line": 52
                        },
                        "start": {
                            "character": 4,
                            "line": 52
                        }
                    }
                },
                "commandUri": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs"
            }
        ],
        "command": "81255:class:classplugin.typelens",
        "title": "pure :: a -> Parser a"
    },
    "data": 2017,
    "range": {
        "end": {
            "character": 51,
            "line": 52
        },
        "start": {
            "character": 4,
            "line": 52
        }
    }
}


[Trace - 20:23:16] Received response 'codeLens/resolve - (339)' in 4ms.
Result: {
    "command": {
        "arguments": [
            {
                "commandEdit": {
                    "newText": "(<*>) :: Parser (a -> b) -> Parser a -> Parser b\n    ",
                    "range": {
                        "end": {
                            "character": 4,
                            "line": 53
                        },
                        "start": {
                            "character": 4,
                            "line": 53
                        }
                    }
                },
                "commandUri": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs"
            }
        ],
        "command": "81255:class:classplugin.typelens",
        "title": "(<*>) :: Parser (a -> b) -> Parser a -> Parser b"
    },
    "data": 2018,
    "range": {
        "end": {
            "character": 27,
            "line": 56
        },
        "start": {
            "character": 4,
            "line": 53
        }
    }
}


[Trace - 20:23:17] Sending request 'textDocument/formatting - (341)'.
Params: {
    "textDocument": {
        "uri": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs"
    },
    "options": {
        "tabSize": 4,
        "insertSpaces": true
    }
}


[Trace - 20:23:17] Received request 'window/workDoneProgress/create - (85)'.
Params: {
    "token": 14
}


[Trace - 20:23:17] Sending response 'window/workDoneProgress/create - (85)'. Processing request took 0ms
No result returned.


2023-10-03T18:23:17.601393Z | Info | fourmolu: No fourmolu.yaml found in any of:
  "/Users/niklas/devel/haskell-json-parser/src/Json.hs"
  "/Users/niklas/devel/haskell-json-parser/src/"
  "/Users/niklas/devel/haskell-json-parser/"
  "/Users/niklas/devel/"
  "/Users/niklas/"
  "/Users/"
  "/"
  "/Users/niklas/.config"
[Trace - 20:23:17] Received notification '$/progress'.
Params: {
    "token": 14,
    "value": {
        "cancellable": true,
        "kind": "begin",
        "title": "Formatting Json.hs"
    }
}


[Trace - 20:23:17] Received notification '$/progress'.
Params: {
    "token": 14,
    "value": {
        "kind": "end"
    }
}


[Trace - 20:23:17] Received response 'textDocument/formatting - (341)' in 67ms.
Result: []


[Trace - 20:23:17] Sending notification 'textDocument/didSave'.
Params: {
    "textDocument": {
        "uri": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs"
    }
}


2023-10-03T18:23:17.693359Z | Info | Typechecking reverse dependencies for NormalizedFilePath "/Users/niklas/devel/haskell-json-parser/src/Json.hs": [ NormalizedFilePath "/Users/niklas/devel/haskell-json-parser/test/Test.hs" ]
[Trace - 20:23:17] Received request 'window/workDoneProgress/create - (86)'.
Params: {
    "token": "2037"
}


[Trace - 20:23:17] Sending response 'window/workDoneProgress/create - (86)'. Processing request took 0ms
No result returned.


[Trace - 20:23:17] Received notification '$/progress'.
Params: {
    "token": "2037",
    "value": {
        "kind": "begin",
        "title": "Processing"
    }
}


[Trace - 20:23:17] Received request 'window/workDoneProgress/create - (87)'.
Params: {
    "token": "2038"
}


[Trace - 20:23:17] Sending response 'window/workDoneProgress/create - (87)'. Processing request took 0ms
No result returned.


[Trace - 20:23:17] Received notification '$/progress'.
Params: {
    "token": "2038",
    "value": {
        "kind": "begin",
        "title": "Indexing"
    }
}


[Trace - 20:23:17] Received notification '$/progress'.
Params: {
    "token": "2038",
    "value": {
        "kind": "report",
        "message": " (0/1)..."
    }
}


[Trace - 20:23:17] Received notification '$/progress'.
Params: {
    "token": "2037",
    "value": {
        "kind": "end"
    }
}


[Trace - 20:23:17] Received notification '$/progress'.
Params: {
    "token": "2038",
    "value": {
        "kind": "end",
        "message": "Finished indexing 1 files"
    }
}


[Trace - 20:23:18] Sending notification 'workspace/didChangeWatchedFiles'.
Params: {
    "changes": [
        {
            "uri": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs",
            "type": 2
        },
        {
            "uri": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs",
            "type": 2
        },
        {
            "uri": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs",
            "type": 2
        }
    ]
}


[Trace - 20:23:19] Sending request 'codeLens/resolve - (342)'.
Params: {
    "range": {
        "start": {
            "line": 63,
            "character": 4
        },
        "end": {
            "line": 65,
            "character": 32
        }
    },
    "data": {
        "resolvePlugin": "class",
        "resolveURI": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs",
        "resolveValue": 2015
    }
}


[Trace - 20:23:19] Sending request 'codeLens/resolve - (343)'.
Params: {
    "range": {
        "start": {
            "line": 71,
            "character": 4
        },
        "end": {
            "line": 71,
            "character": 34
        }
    },
    "data": {
        "resolvePlugin": "class",
        "resolveURI": "file:///Users/niklas/devel/haskell-json-parser/src/Json.hs",
        "resolveValue": 2013
    }
}


[Trace - 20:23:19] Received response 'codeLens/resolve - (342)' in 3ms. Request failed: class: Stale Resolve (-32801).
[Trace - 20:23:19] Received response 'codeLens/resolve - (343)' in 2ms. Request failed: class: Stale Resolve (-32801).

@joyfulmantis

cc @joyfulmantis , this seems like a resolve issue?

I believe this is a vscode issue. We can't respond to stale resolve requests, and in those cases we respond with the correct error code. Instead of displaying no command vscode shouldn't display the lens at all.

I've been able to reproduce it on Intel x86_64 / Ubuntu also.

I can open an issue on vscode-haskell if you think it's a problem on the client side.

I've been able to reproduce it on Intel x86_64 / Ubuntu also.

I can open an issue on vscode-haskell if you think it's a problem on the client side.

I believe the place where you want to open an issue is either vscode's official language server client package or the vscode repository .

Closing as we believe this is not our fault and needs to be raised in vscode.

I'm unsure about this. Maybe we should instead return the original item without new fields filled in in this case? It's unclear.

I'm unsure about this. Maybe we should instead return the original item without new fields filled in in this case? It's unclear.

I doubt doing that would fix it in that case, as it still would be a lens without a command

I guess you're right. The only thing we could do would be to back out the resolve support, or somehow make it possible for stale resolve requests to be more likely to work.

I found the corresponding code in vscode and opened an issue: microsoft/vscode#197643

@michaelpj

@michaelpj Do we need to remove resolve here or rework it to be more successful because of vscodes's position vis a vis resolve failure? microsoft/vscode#197643 (comment)

I don't know what to do tbh. It seems like their position is "resolve should be very reliable", and I'm not sure that that's something we can promise...

FWIW, I haven't observed this happening to me much (but then I use emacs not vscode, and I'm not sure how emacs deals with it). Perhaps we can leave this open and see if we get more people complaining.

One thing we might want to do is offer some configuration options about whether to use resolve. That's somewhat consistent with what we do for other features, you can generally e.g. turn off code lenses for a plugin, maybe you should also be able to turn off code-lens-resolve 🤔 That way at least if it's really misbehaving for people they can turn it off...

@joyfulmantis

Another thought: could we use a more robust key for some of the resolve functions? e.g. for type lenses we could probably use something like the combination of line-in-file and binding-name to identify a lens target. Then when we resolve we can get the fresh information about the file, see if there is still a binding with that name on that line, and if so continue resolving it.

WDYT @joyfulmantis ?

I'm quite new to the Haskell community.
I've been running into this and have been reloading the window as I thought something had broke.

But it sounds like it's actually "reloading" these lenses.
And indeed, just waiting a bit longer, it eventually comes back with the expected code lens.

At least I now know what is actually happening when I see !!MISSING: command!!.
If a solution may take a while, maybe a note somewhere about this would be nice?

@joyfulmantis

Another thought: could we use a more robust key for some of the resolve functions? e.g. for type lenses we could probably use something like the combination of line-in-file and binding-name to identify a lens target. Then when we resolve we can get the fresh information about the file, see if there is still a binding with that name on that line, and if so continue resolving it.

WDYT @joyfulmantis ?

I think that is an idea we can explore. I think the reason why I originally chose to have these transient keys that we currently have, was to avoid having to process information multiple times. However, we could keep the current keys, and then add more information that allows us to compute the new lens if the key is stale.

I guess I was hoping that we still wouldn't have to redo work? We can still use basically the same structure, I'm really just proposing a different key type. i.e. what if we actually just used (LineNumber, OccName) as the key for code lens resolve?

If a solution may take a while, maybe a note somewhere about this would be nice?

Generally we don't have a good way of doing this in a way that's actually visible to users. For now, I think having something visible on the issue tracker is the best thing we can do...

Navigation Menu

Repository navigation

!!MISSING: command!! is intermittently displayed instead of type class function signatures #3827

Your environment

Steps to reproduce

Expected behaviour

Actual behaviour

Debug information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

!!MISSING: command!! is intermittently displayed instead of type class function signatures #3827

Description

Your environment

Steps to reproduce

Expected behaviour

Actual behaviour

Debug information

Activity

konnik commented on Oct 3, 2023

konnik commented on Oct 3, 2023

michaelpj commented on Oct 4, 2023

joyfulmantis commented on Oct 4, 2023

konnik commented on Oct 4, 2023

joyfulmantis commented on Oct 5, 2023

fendor commented on Oct 18, 2023

michaelpj commented on Nov 7, 2023

joyfulmantis commented on Nov 7, 2023

michaelpj commented on Nov 7, 2023

michaelpj commented on Nov 7, 2023

joyfulmantis commented on Dec 4, 2023

michaelpj commented on Dec 4, 2023

michaelpj commented on Dec 13, 2023

han-tyumi commented on Dec 26, 2023

joyfulmantis commented on Dec 28, 2023

michaelpj commented on Dec 28, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions