unresolved-proc-macro error on all proc macro usages #11150

dbeckwith · 2022-01-01T04:58:41Z

rust-analyzer version: 3d63abf1d 2022-01-01 nightly

rustc version: rustc 1.57.0 (f1edd0429 2021-11-29)

I've verified that proc macro support is enabled by looking at the client logs:

INFO [1/1/2022, 4:49:27 AM]: Extension version: 0.3.886
INFO [1/1/2022, 4:49:27 AM]: Using configuration {
  cargoRunner: null,
  runnableEnv: null,
  inlayHints: {
    enable: false,
    smallerHints: true,
    chainingHints: true,
    maxLength: 25,
    parameterHints: true,
    typeHints: true,
    hideNamedConstructorHints: false
  },
  server: { path: null, extraEnv: null },
  trace: { server: 'off', extension: false },
  debug: {
    engine: 'auto',
    sourceFileMap: {
      '/rustc/<id>': '${env:USERPROFILE}/.rustup/toolchains/<toolchain-id>/lib/rustlib/src/rust'
    },
    openDebugPane: false,
    engineSettings: {}
  },
  assist: {
    importGranularity: 'crate',
    importEnforceGranularity: false,
    importPrefix: 'crate',
    importGroup: true,
    allowMergingIntoGlobImports: true
  },
  cache: { warmup: true },
  callInfo: { full: true },
  cargo: {
    autoreload: true,
    allFeatures: false,
    unsetTest: [ 'core' ],
    features: [],
    runBuildScripts: true,
    useRustcWrapperForBuildScripts: true,
    noDefaultFeatures: false,
    target: null,
    noSysroot: false
  },
  checkOnSave: {
    enable: true,
    allFeatures: null,
    allTargets: true,
    command: 'clippy',
    noDefaultFeatures: null,
    target: null,
    extraArgs: [],
    features: null,
    overrideCommand: null
  },
  completion: {
    addCallArgumentSnippets: true,
    addCallParenthesis: true,
    snippets: {
      'Arc::new': {
        postfix: 'arc',
        body: 'Arc::new(${receiver})',
        requires: 'std::sync::Arc',
        description: 'Put the expression into an `Arc`',
        scope: 'expr'
      },
      'Rc::new': {
        postfix: 'rc',
        body: 'Rc::new(${receiver})',
        requires: 'std::rc::Rc',
        description: 'Put the expression into an `Rc`',
        scope: 'expr'
      },
      'Box::pin': {
        postfix: 'pinbox',
        body: 'Box::pin(${receiver})',
        requires: 'std::boxed::Box',
        description: 'Put the expression into a pinned `Box`',
        scope: 'expr'
      },
      Ok: {
        postfix: 'ok',
        body: 'Ok(${receiver})',
        description: 'Wrap the expression in a `Result::Ok`',
        scope: 'expr'
      },
      Err: {
        postfix: 'err',
        body: 'Err(${receiver})',
        description: 'Wrap the expression in a `Result::Err`',
        scope: 'expr'
      },
      Some: {
        postfix: 'some',
        body: 'Some(${receiver})',
        description: 'Wrap the expression in an `Option::Some`',
        scope: 'expr'
      }
    },
    postfix: { enable: true },
    autoimport: { enable: true },
    autoself: { enable: true }
  },
  diagnostics: {
    enable: true,
    enableExperimental: true,
    disabled: [],
    remapPrefix: {},
    warningsAsHint: [],
    warningsAsInfo: []
  },
  experimental: { procAttrMacros: true },
  files: { watcher: 'client', excludeDirs: [] },
  highlightRelated: {
    references: true,
    exitPoints: true,
    breakPoints: true,
    yieldPoints: true
  },
  highlighting: { strings: true },
  hover: { documentation: true, linksInHover: true },
  hoverActions: {
    debug: true,
    enable: true,
    gotoTypeDef: true,
    implementations: true,
    references: false,
    run: true
  },
  joinLines: {
    joinElseIf: true,
    removeTrailingComma: true,
    unwrapTrivialBlock: true,
    joinAssignments: true
  },
  lens: {
    debug: true,
    enable: false,
    implementations: true,
    run: true,
    methodReferences: false,
    references: false,
    enumVariantReferences: false,
    forceCustomCommands: true
  },
  linkedProjects: [],
  lruCapacity: null,
  notifications: { cargoTomlNotFound: true },
  procMacro: { enable: true, server: null },
  runnables: { overrideCargo: null, cargoExtraArgs: [] },
  rustcSource: null,
  rustfmt: {
    extraArgs: [],
    overrideCommand: [ 'rustfmt' ],
    enableRangeFormatting: false
  },
  workspace: { symbol: { search: { scope: 'workspace', kind: 'only_types' } } }
}
INFO [1/1/2022, 4:49:27 AM]: PersistentState: { serverVersion: '0.3.886' }

However, I'm still getting the unresolved-proc-macro error that macros are not being expanded. Is there something else that has to be enabled or installed to turn this on? The User Manual doesn't mention anything else. It does say "can also indicate project setup problems" but doesn't indicate what those might be.

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

lnicola · 2022-01-01T08:03:06Z

No, it should be enough. Is that your macro, or a public crate?

dbeckwith · 2022-01-01T14:54:36Z

I'm seeing the error from the derive macros from serde and thiserror, as well as function-like macros from sqlx.

dbeckwith · 2022-01-01T15:00:06Z

It might be worth mentioning that I'm on NixOS, using the mozilla/nixpkgs-mozilla overlay for my Rust environment, and I notice that the rust-analyzer VS Code extension sometimes does some NixOS-specific setup when it starts up.

lnicola · 2022-01-01T15:08:01Z

CC @matklad -- I'm not sure, maybe we can't load the compiled proc macro because of unresolved libraries?

dbeckwith · 2022-01-01T15:17:47Z

I found this in the "Log (Extension Host)" output panel:

[2022-01-01 15:13:46.756] [exthost] [error] Canceled: Canceled
    at Object.R [as canceled] (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:5:1157)
    at t._remoteCall (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:99:13876)
    at Proxy.O.<computed>.F.charCodeAt.O.<computed> (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:99:10271)
    at r._doExecuteCommand (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:95:30473)
    at r.executeCommand (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:95:29874)
    at Object.executeCommand (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:104:22022)
    at Ca ($HOME/.vscode/extensions/matklad.rust-analyzer-0.3.886/out/main.js:39:35807)
    at Object.Eg ($HOME/.vscode/extensions/matklad.rust-analyzer-0.3.886/out/main.js:85:1555)
    at v._deactivate (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:100:11513)
    at /nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:100:10061
    at Array.map (<anonymous>)
    at v.deactivateAll (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:100:10049)
    at p.terminate (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:104:735)
    at r (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:114:36400)
    at Socket.<anonymous> (/nix/store/78lswy0av2y6zdfv7vjrlpdz74ha1pi4-vscode-1.63.2/lib/vscode/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:114:34012)
    at Socket.emit (events.js:327:22)
    at Pipe.<anonymous> (net.js:673:12)

lnicola · 2022-01-01T15:20:39Z

That's harmless. You you search for a libserde_derive-*.so in your target directory and run ldd on it, what does it say?

dbeckwith · 2022-01-01T15:32:36Z

$ ldd target/debug/deps/libserde_derive-6408565b4f8262d0.so
	linux-vdso.so.1 (0x00007ffd7afea000)
	libgcc_s.so.1 => /nix/store/wl60dr9p15rwf53gxz61ijgisc1zdjc7-glibc-2.33-59/lib/libgcc_s.so.1 (0x00007f5704035000)
	libpthread.so.0 => /nix/store/wl60dr9p15rwf53gxz61ijgisc1zdjc7-glibc-2.33-59/lib/libpthread.so.0 (0x00007f5704015000)
	libm.so.6 => /nix/store/wl60dr9p15rwf53gxz61ijgisc1zdjc7-glibc-2.33-59/lib/libm.so.6 (0x00007f5703ed4000)
	libdl.so.2 => /nix/store/wl60dr9p15rwf53gxz61ijgisc1zdjc7-glibc-2.33-59/lib/libdl.so.2 (0x00007f5703ecf000)
	libc.so.6 => /nix/store/wl60dr9p15rwf53gxz61ijgisc1zdjc7-glibc-2.33-59/lib/libc.so.6 (0x00007f5703d0a000)
	/nix/store/wl60dr9p15rwf53gxz61ijgisc1zdjc7-glibc-2.33-59/lib64/ld-linux-x86-64.so.2 (0x00007f57047ea000)

dbeckwith · 2022-01-01T16:07:56Z

Just want to make it clear that the problem doesn't seem specific to any particular proc-macro, it seems to be affecting all of them. The attribute macro from async-trait is another example.

matklad · 2022-01-01T17:00:02Z

Things to check:

does it work with a trivial project (ie, where something like serde is the only dependency?)
are there any errors in the rust-analyzer log? Stuff from unresolved-proc-macro error on all proc macro usages #11150 (comment) is log for vscode extention, ra logs are in

(this tab will be present only if there are some logs)

dbeckwith · 2022-01-01T17:21:15Z

I have verbose logging enabled according to the manual. In my original project, I see lots of output in the "Rust Analyzer Language Server" logs but no errors.

I made a new test project with the same Rust version and configuration, added serde as a dependency, and a struct with #[derive(Serialize)]. When RA first started up, it was giving an error status:

rust-analyzer failed to run build scripts:
error: could not compile serde_derive due to 2 previous errors
error: build failed

Click to reload.

cargo check in my terminal showed no issue, and I was getting unresolved-proc-macro on the derive. Clicking to reload the extension gave the same status. I still didn't see any other errors in the "Rust Analyzer Language Server" logs besides:

[ERROR rust_analyzer::reload] failed to switch build data: rust-analyzer failed to run build scripts:
error: could not compile `serde_derive` due to 2 previous errors
error: build failed

And no other errors in "Rust Analyzer Language Server Trace" or "Rust Analyzer Client".

After reloading the VS Code window, the RA extension no longer shows an error status, but I'm still getting unresolved-proc-macro on the derive.

dbeckwith · 2022-01-11T22:48:38Z

If there's any additional information or investigation I can provide to help diagnose this issue please let me know.

rinconjc · 2022-03-04T06:23:07Z

I have the same issue with spacemacs + lsp RA

onichandame · 2022-03-18T07:02:13Z

I am experiencing the same issue

lnicola · 2022-03-18T07:08:56Z

Does anyone have a test case they make public?

onichandame · 2022-03-18T10:39:31Z

@lnicola I have filed another issue with reproduction repo. My case is slightly different as proc-macros from serde and all functional macros are working fine for me.

dbeckwith · 2022-03-18T20:05:19Z

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

unresolved-proc-macro error on all proc macro usages #11150

unresolved-proc-macro error on all proc macro usages #11150

dbeckwith commented Jan 1, 2022 •

edited

Loading

lnicola commented Jan 1, 2022

dbeckwith commented Jan 1, 2022

dbeckwith commented Jan 1, 2022

lnicola commented Jan 1, 2022

dbeckwith commented Jan 1, 2022

lnicola commented Jan 1, 2022

dbeckwith commented Jan 1, 2022 •

edited

Loading

dbeckwith commented Jan 1, 2022

matklad commented Jan 1, 2022

dbeckwith commented Jan 1, 2022 •

edited

Loading

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

dbeckwith commented Jan 11, 2022

rinconjc commented Mar 4, 2022

onichandame commented Mar 18, 2022

lnicola commented Mar 18, 2022

onichandame commented Mar 18, 2022

dbeckwith commented Mar 18, 2022

unresolved-proc-macro error on all proc macro usages #11150

unresolved-proc-macro error on all proc macro usages #11150

Comments

dbeckwith commented Jan 1, 2022 • edited Loading

lnicola commented Jan 1, 2022

dbeckwith commented Jan 1, 2022

dbeckwith commented Jan 1, 2022

lnicola commented Jan 1, 2022

dbeckwith commented Jan 1, 2022

lnicola commented Jan 1, 2022

dbeckwith commented Jan 1, 2022 • edited Loading

dbeckwith commented Jan 1, 2022

matklad commented Jan 1, 2022

dbeckwith commented Jan 1, 2022 • edited Loading

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

dbeckwith commented Jan 11, 2022

rinconjc commented Mar 4, 2022

onichandame commented Mar 18, 2022

lnicola commented Mar 18, 2022

onichandame commented Mar 18, 2022

dbeckwith commented Mar 18, 2022

dbeckwith commented Jan 1, 2022 •

edited

Loading

dbeckwith commented Jan 1, 2022 •

edited

Loading

dbeckwith commented Jan 1, 2022 •

edited

Loading