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

BrokenImport incorrectly showing #2607

Closed
TheGeordie opened this issue Jan 11, 2023 · 3 comments
Closed

BrokenImport incorrectly showing #2607

TheGeordie opened this issue Jan 11, 2023 · 3 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@TheGeordie
Copy link

TheGeordie commented Jan 11, 2023

Type: Bug

hello,

The Import statements are showing with the RED line under them in VSC, when I perform a run/debug/build all are working ok.

parent-child.go file:-
package main

// Below: Module name + Path to Package directory ## THIS WORKS EVEN THOUGH SHOWN IN RED
// Refer to go.mod for the Module Name - it does not need to be the same of the folder/directory
import (
"PC/pkg/logging"
"PC/pkg/logging2"
)

func main() {

logging.Logger("Print message in the Logger of Log Package")
logging2.Logger("Using another logger Package")

}

image

Extension version: 0.37.0
VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.19042
Modes:
Sandboxed: No

System Info
Item Value
CPUs AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx (8 x 1996)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 14.93GB (4.96GB free)
Process Argv --crash-reporter-id 3cd5318f-fe06-4145-a40c-6b0262f605f4
Screen Reader no
VM 0%
@gopherbot gopherbot added this to the Untriaged milestone Jan 11, 2023
@TheGeordie
Copy link
Author

Hello - When does this issue get triaged? Many thanks.

@hyangah hyangah added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jan 12, 2023
@hyangah
Copy link
Contributor

hyangah commented Jan 13, 2023

@TheGeordie Can you please capture the gopls trace? Instruction is here:
https://github.com/golang/vscode-go/wiki/troubleshooting#collect-gopls-information

--

I guess you opened the editor in the Go folder (vscode workspace folder), and
your go.mod is located in Go/My-Learning/My-Library/Modules/Parent-Child-WORKING folder (module root). Currently, the extension requires the vscode workspace folder and the module root folder to be aligned either by

  • open vscode from the go module root folder, or
  • use go.work from the Go folder.

We are working to remove this restriction, but for now, please read and follow the instruction in https://github.com/golang/vscode-go#setting-up-your-workspace and https://github.com/golang/tools/blob/master/gopls/doc/workspace.md.

@gopherbot
Copy link
Collaborator

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@golang golang locked and limited conversation to collaborators Feb 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

3 participants