uudashr
Repos
77
Followers
64

Events

Created at 3 days ago
Created at 1 week ago
Some of Interactive query is broken

Description

The interactive query is broken

Steps to Reproduce

Go to https://graphql.org/learn/queries/

Expected Result

Should not shown error

Actual Result

It show error result Screen Shot 2022-11-16 at 17 50 07

Additional Context

Created at 2 weeks ago

Add slice map function

Created at 3 weeks ago

Fix the go version

Created at 3 weeks ago

Upgrade to go 1.9

Created at 3 weeks ago
[Bug] Output panel behavior affecting `vscode-go` extension behavior

Use https://github.com/uudashr/hello You need to install go extension

  1. Open the project code <the directory>
  2. Open any file (or just open hello_test.go)
  3. Open "Command Pallete" (cmd + shift + p on Mac) and choose "Go: Test Package". It will shows the test output
Created at 3 weeks ago
create branch
uudashr create branch master
Created at 3 weeks ago
create repository
uudashr create repository
Created at 3 weeks ago
issue comment
Unable to click/navigate to failed test location on the test error output

FYI I report the the issue here https://github.com/microsoft/vscode-react-native/issues/1854

Created at 3 weeks ago
[Bug] Output panel behavior affecting `vscode-go` extension behavior

🐛 What is the bug? How can we reproduce it?

Seems that react native extensions changing the original behavior of the output panel. It causing issues for another extension (vscode-go) and might be affecting the other extensions as well.

The output shown like this (this is output from vscode-go test feature). I can observed that:

  1. Some of the line are red colored (seems that it come from the stderr)
  2. The line /Users/nuruddin.ashr/temp/hello/hello_test.go:6 cannot be clicked. Screen Shot 2022-11-03 at 18 37 18

This is issue if you using both vscode-react-native and vscode-go installed.

Expected behavior

Without the vscode-react-native extension installed it shows like this. The line /Users/nuruddin.ashr/temp/hello/hello_test.go:6 can be clicked. Screen Shot 2022-11-03 at 18 36 53

Debug output

n/a

Environment

Please tell us about your system and your project:

  • npx react-native doctor or npx expo doctor if your project is using Expo: n/a

  • envinfo: n/a

  • React Native Tools extension version: v1.10.0

  • Expo SDK version (if applicable): n/a

Created at 4 weeks ago
issue comment
Unable to click/navigate to failed test location on the test error output

FUI I found that React Native Tools extension not working well with Go extension

Created at 4 weeks ago
issue comment
Unable to click/navigate to failed test location on the test error output

I disabled all extensions except Go extension. And it back works as expected. It seems that some of the extension causing the issue.

Created at 4 weeks ago
issue comment
Unable to click/navigate to failed test location on the test error output

I already update the info based on @suzmue findings, and reproduce the problem. @hyangah when you said you can't reproduce it means in your case the filepath shown on test error output is clickable?

Created at 1 month ago
issue comment
Unable to click/navigate to failed test location on the test error output

I've edited the details. But the result is the same, I still cannot click the filepath.

VSCode change its implementation so the filepath is not clickable anymore? Is there anything that we can do?

Created at 1 month ago

Update to go1.18

Refactor filters and formatters to enable support for JSON output Add JSON output (with pretty-print option)

Fix filters and extract default functions

Merge branch 'uudashr:master' into master

Implement feedback

Refactored, pulled os.Exit() into main method

Revert go.mod/go.sum

Merge pull request #14 from davidkroell/master

Add support for JSON output writing

Created at 1 month ago
pull request closed
Add support for JSON output writing

Adding a new flag -format to set the output writer formatting. The default behavior keeps the same, as text is the default format.

Adding this functionality required to refactor the code a bit. Logic for filtering (top/over) and writing is now moved to the gocognit package.

Also updated to go1.18

Created at 1 month ago
opened issue
Unable to click/navigate to failed test location on the test error output

What version of Go, VS Code & VS Code Go extension are you using?

  • Run go version to get version of Go from the VS Code integrated terminal.
    • go version go1.19.2 darwin/arm64
  • Run gopls -v version to get version of Gopls from the VS Code integrated terminal.
    • v0.9.5
  • Run code -v or code-insiders -v to get version of VS Code or VS Code Insiders.
    • 1.72.2 d045a5eda657f4d7b676dedbfa7aab8207f8a075
  • Check your installed extensions to get the version of the VS Code Go extension
    • v0.35.2
  • Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Locate Configured Go Tools command.

Checking configured tools.... GOBIN: undefined toolsGopath: gopath: /Users/nuruddin.ashr/go GOROOT: /opt/homebrew/Cellar/go/1.19.2/libexec PATH: /Users/nuruddin.ashr/.yarn/bin:/Users/nuruddin.ashr/.config/yarn/global/node_modules/.bin:/Users/nuruddin.ashr/.nvm/versions/node/v18.10.0/bin:/opt/homebrew/lib/ruby/gems/3.1.0/bin:/opt/homebrew/opt/ruby/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/nuruddin.ashr/.cargo/bin:/Users/nuruddin.ashr/Applications/flutter/bin:/Users/nuruddin.ashr/go/bin

go:	/opt/homebrew/bin/go: go version go1.19.2 darwin/arm64

gotests:	/Users/nuruddin.ashr/go/bin/gotests	(version: v1.6.0 built with go: go1.19.2)
gomodifytags:	/Users/nuruddin.ashr/go/bin/gomodifytags	(version: v1.16.0 built with go: go1.19.2)
impl:	/Users/nuruddin.ashr/go/bin/impl	(version: v1.1.0 built with go: go1.19.2)
goplay:	/Users/nuruddin.ashr/go/bin/goplay	(version: v1.0.0 built with go: go1.19.2)
dlv:	/Users/nuruddin.ashr/go/bin/dlv	(version: v1.9.1 built with go: go1.19.2)
staticcheck:	/Users/nuruddin.ashr/go/bin/staticcheck	(version: v0.3.3 built with go: go1.19.1)
gopls:	/Users/nuruddin.ashr/go/bin/gopls	(version: v0.9.5 built with go: go1.19.1)

go env Workspace Folder (numongo): /Users/nuruddin.ashr/Projects/ddd/numongo GO111MODULE="" GOARCH="arm64" GOBIN="" GOCACHE="/Users/nuruddin.ashr/Library/Caches/go-build" GOENV="/Users/nuruddin.ashr/Library/Application Support/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="arm64" GOHOSTOS="darwin" GOINSECURE="" GOMODCACHE="/Users/nuruddin.ashr/go/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="darwin" GOPATH="/Users/nuruddin.ashr/go" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/opt/homebrew/Cellar/go/1.19.2/libexec" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/opt/homebrew/Cellar/go/1.19.2/libexec/pkg/tool/darwin_arm64" GOVCS="" GOVERSION="go1.19.2" GCCGO="gccgo" AR="ar" CC="clang" CXX="clang++" CGO_ENABLED="1" GOMOD="/Users/nuruddin.ashr/Projects/ddd/numongo/go.mod" GOWORK="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/jb/7d_d4kn14pd26s66z0f7ds6w0000gr/T/go-build2955823023=/tmp/go-build -gno-record-gcc-switches -fno-common"

Share the Go related settings you have added/edited

Run Preferences: Open Settings (JSON) command to open your settings.json file. Share all the settings with the go. or ["go"] or gopls prefixes.

{
    "go.useLanguageServer": true,
    "go.toolsManagement.autoUpdate": true,
    "gopls": {
        "ui.semanticTokens": true
    },
}

Describe the bug

The failed test file path and the line number shown on the test output, but it can't be clicked. Doesn't work with cmd+click either. I remember it we should be able to click the file path so we can easily navigate to the location of the failed test.

Steps to reproduce the behavior:

  1. Use this below code
package hello_test

import "testing"

func TestHello(t *testing.T) {
	t.Error("Opps")
}

  1. Run Ctrl+Shift+P (Cmd+Shift+P on Mac OS) > Go: Test package command.
  2. See output
Running tool: /opt/homebrew/bin/go test -timeout 30s -coverprofile=/var/folders/jb/7d_d4kn14pd26s66z0f7ds6w0000gr/T/vscode-goK6TihG/go-code-cover github.com/uudashr/hello

--- FAIL: TestHello (0.00s)
    /Users/nuruddin.ashr/temp/hello/hello_test.go:6: Opps
FAIL
coverage: [no statements]
FAIL	github.com/uudashr/hello	0.231s
FAIL

Screenshots or recordings

If applicable, add screenshots or recordings to help explain your problem.

https://user-images.githubusercontent.com/166053/198441014-bf98b17a-a26d-4cbf-b717-71a2c7092ee9.mov

Created at 1 month ago
Created at 1 month ago

Add xid

Created at 1 month ago

Context override

Created at 1 month ago
issue comment
Add support for JSON output writing

@davidkroell May I know why you need this json format?

Created at 1 month ago
issue comment
Add support for JSON output writing

Change back the go to 1.16 should make it work

Created at 1 month ago
issue comment
Add support for JSON output writing

Your test is fail on 1.16. Do you have any specific reason why you upgrade the go version to 1.18?

Created at 1 month ago

Upgrade go 1.18

Upgrade go 1.17

Created at 1 month ago

Add go 1.19

Created at 1 month ago