Skip to content

Suggest fully qualified path on method name collision #202434

Suggest fully qualified path on method name collision

Suggest fully qualified path on method name collision #202434

Triggered via pull request April 15, 2026 01:08
Status Success
Total duration 1h 27m 21s
Artifacts 1

ci.yml

on: pull_request
Calculate job matrix
36s
Calculate job matrix
Matrix: job
publish toolstate
0s
publish toolstate
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 6 warnings
PR - x86_64-gnu-tools
unexpected closing delimiter: `}`
PR - x86_64-gnu-tools
this file contains an unclosed delimiter
PR - x86_64-gnu-tools
unexpected closing delimiter: `}`
PR - x86_64-gnu-tools
unexpected `if` in the condition expression
PR - x86_64-gnu-tools
mismatched closing delimiter: `}`
PR - x86_64-gnu-tools
lifetimes cannot start with a number
PR - x86_64-gnu-tools
this file contains an unclosed delimiter
PR - x86_64-gnu-tools
missing type for `static` item
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `server`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `client`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `appservice-api-s`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `appservice-api-c`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `foo-method`
PR - x86_64-gnu-tools
unexpected `cfg` condition value: `foo-method`

Artifacts

Produced during runtime
Name Size Digest
doc-153662-c53fc09c Expired
20.4 MB
sha256:338eafe21b9cffdce731d72bb583b322030ee55c12c7a8726feb0fc1ee3ad89e