primordic/IssueDupesLite huggingface dataset:
Repository: gohugoio/hugo

Issue #7621: IPFS Deployment option
Created: 2020-09-04T22:38:49Z
hugo supports multiple deployers via hugo deploy
ipfs should be added to the deployment options.  With the following arguments:

ipfs api server url
ipns public key (optional)

Hugo could self-publish websites to an IPFS node. This would make the site content available through any public IPFS gateway node.
For those without IPFS knowledge, I made a "crash course" infographic here:
https://cloudflare-ipfs.com/ipfs/Qmbq5hoM4eCeCnSSTcXSyaYNjNHgCmeQ58VuqJxU1tu3ho/IPFS_For_Sysadmins.pdf
IPFS is attractive because it's literally "make your own cloud"
I published a "R1B2" release page for Haiku here as an example:

http://ipfs.haiku-os.org  A       209.94.90.1  (ip for ipfs.io gateway)
ipfs.haiku-os.org.	3600	IN	TXT	"dnslink=/ipfs/QmXtYCCM8Kt7Q9DbXYKHy8bUQve9zauNiKUZs57bnphBtw"

Essentially:

ipfs.haiku-os.org goes to ipfs.io (but it can go to any ipfs gateway)
ipfs.io checks for /ipns/ipfs.haiku-os.org, and looks at that TXT record
ipfs.io renders the site at /ipfs/QmXtYCCM8Kt7Q9DbXYKHy8bUQve9zauNiKUZs57bnphBtw

I made another example with https://terarocket.io   this site uses the free Cloudflare IPFS gateway and has HTTPS

Duplicate issue #8281: Permalinkable Content-Addressing for IPFS
Created: 2021-02-23T20:44:12Z
I am opening this issue after this forum topic
IPFS is a distributed system for storing and accessing files, websites, applications, and data, that uses a content identifier, or CID, as a label used to point to material in IPFS. Last month the Brave browser became the first browser to integrate the new protocol

Basically this is a feature request about offering Permalinkable Content Addressing through Hugo.

Calculate the SHA256 hash (and/or other hash functions) of a content page.
Use the generated value as a permalink for a Custom Ouput Format (in this case IPFS)


Currently IPFS documentation recommends that Hugo users set relativeURLS=true and only generate a CID for the folder that contains the data.
This feature would allow for a complete IPFS implementation.

Instead of being location-based, IPFS addresses a file by what's in it, or by its content. The content identifier above is a cryptographic hash of the content at that address. The hash is unique to the content that it came from, even though it may look short compared to the original content. It also allows you to verify that you got what you asked for — bad actors can't just hand you content that doesn't match.

source of quote

More on IPFS
IPFS Documentation
Article from the portal Decrypt.co regarding porting their website to IPFS
IPFS Wikipedia Page

Closing comment (2021-03-28T01:04:15Z): Just a note that this semi-duplicates #7621
Repository: gohugoio/hugo

Issue #8997: Auto-generated header ids can contain invalid CSS selectors
Created: 2021-09-27T13:47:02Z
What version of Hugo are you using (hugo version)?
$ 88.1


Does this issue reproduce with the latest release?
Yes - this is the latest version
If I have a markdown header which begins with a number Hugo generates an id beginning with a number. For example ## 1 Test generates <h2 id="1-test">1 Test…</h2>

According to w3.org (https://www.w3.org/TR/CSS21/syndata.html#characters) In CSS, identifiers (including element names, classes, and IDs in selectors) … cannot start with a digit, two hyphens, or a hyphen followed by a digit.
This causes the error  Uncaught DOMException: Failed to execute 'querySelector' on 'Document': '#1-test' is not a valid selector. if I try to do a document.querySelector() on this selector. In tests, this seems to be caused by the leading digit.

The querySelector code is used, for example, in a recent Pull Request on the Docsy theme (google/docsy#506)
This format of anchor is produced with both Blackfriday and Goldmark as the markup generator and is independent of the setting of autoHeadingIDType.

Duplicate issue #9834: Invalid id attribute in heading
Created: 2022-04-27T14:07:30Z
What version of Hugo are you using (hugo version)?
$ hugo version
hugo v0.97.3-078053a43d746a26aa3d48cf1ec7122ae78a9bb4+extended linux/amd64 BuildDate=2022-04-18T17:22:19Z VendorInfo=gohugoio

Does this issue reproduce with the latest release?
Yes.
Issue
The following markup (individual occurrences, only combined for this report):
#### `{{ break }}` - break out of a range (leaving it completely for all subsequent items)
#### `{{ continue }}` - leave the current loop of a range (step to the next item)
results in the following HTML:
<h4 id="-break----break-out-of-a-range-leaving-it-completely-for-all-subsequent-items"><code>{{ break }}</code> - break out of a range (leaving it completely for all subsequent items)</h4>
<h4 id="-continue----leave-the-current-loop-of-a-range-step-to-the-next-item"><code>{{ continue }}</code> - leave the current loop of a range (step to the next item)</h4>
which is invalid (ID must start with a character).
I think it might be an issue with Goldmark but have seen notes on issue reports there to report it first in the implementing software.
If the config is relevant:
[goldmark.parser]
autoHeadingID = true
autoHeadingIDType = "github"

Closing comment (2022-04-27T15:05:15Z): GitHub produces the same ID.
See:
https://html.spec.whatwg.org/multipage/dom.html#global-attributes:the-id-attribute-2

There are no other restrictions on what form an ID can take; in particular, IDs can consist of just digits, start with a digit, start with an underscore, consist of just punctuation, etc.

This is a duplicate of #8997.
Repository: gohugoio/hugo

Issue #7296: Error building site: plain HTML documents not supported
Created: 2020-05-20T07:31:32Z
Hugo Static Site Generator v0.70.0/extended linux/amd64 BuildDate: unknown
When using a valid markdown file: https://s.natalian.org/2020-05-20/Nexus_One.md
I get plain HTML documents not supported and Hugo errors out.
You can have HTML in Markdown. I've even gone through the hoop jump of
markup:
  goldmark:
    renderer:
      unsafe: true

Duplicate issue #9482: plain HTML documents not supported error for Markdown content that starts with HTML
Created: 2022-02-09T18:53:43Z
If one has some Markdown content that starts with HTML and has no front matter, Hugo will throw the error "plain HTML documents not supported" regardless of whether or not markup.goldmark.renderer.unsafe = true is set in the configuration. If one adds any non-HTML content or even an empty front matter to the document, the error goes away.
What version of Hugo are you using (hugo version)?
First v0.91.2 that is shipped in the Debian repos, then the latest v0.92.1 from Homebrew. Both have the same issue.
$ hugo version
hugo v0.91.2-1798BD3F linux/amd64 BuildDate=2021-12-23T15:33:34Z VendorInfo=gohugoio

$ hugo version
hugo v0.92.1+extended linux/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?
Yes

Closing comment (2022-02-09T19:27:35Z): Duplicate of #7296. See also #6098.
Repository: gohugoio/hugo

Issue #6650: Markdownify function does not call render-link hook
Created: 2019-12-20T17:01:05Z
Not an urgent bug, but I have an image shortcode capable of passing a markdown caption that's retrieved by .Inner. Everything renders correctly as HTML (same as v0.61) but my render-link.html hook doesn't seem to be called by it.
This might be a bigger problem with markdownify not calling the new hooks?
Hugo Static Site Generator v0.62.0-DEV-8A58EBB3/extended darwin/amd64 BuildDate: 2019-12-20T11:59:39-0500


shortcodes/image.html:
{{ with .Inner }}
<figcaption>{{ . | markdownify | safeHTML }}</figcaption>
{{ end }}

_default/_markup/render-link.html:
testing....this doesn't appear <a href="{{ .Destination | safeURL }}" target="_blank">{{ .Text | safeHTML }}</a> 


test.md:
{{< image >}}A caption [linking to Google](https://google.com).{{< /image >}}

renders...
A caption <a href="https://google.com">linking to Google</a>.

instead of...
A caption testing....this doesn't appear <a href="https://google.com" target="_blank">linking to Google</a>.


Hope this makes sense!

Duplicate issue #8669: markdownify doesn't respect custom render hooks
Created: 2021-06-19T11:29:29Z
When using markdownify in a template it does not use the markup rendering hooks (e.g. render-link.html), whereas in normal content it does.
What version of Hugo are you using (hugo version)?
$ hugo version
hugo v0.83.1-5AFE0A57+extended windows/amd64 BuildDate=2021-05-02T14:38:05Z VendorInfo=gohugoio 

Does this issue reproduce with the latest release?
Yes

Closing comment (2021-06-19T14:31:51Z): Use .RenderString instead of markdownify.
https://gohugo.io/functions/markdownify

Note: if you need Render Hooks, which markdownify doesn’t currently support, use .RenderString instead.

https://gohugo.io/functions/renderstring

Note that this method is more powerful than the similar markdownify function as it also supports Render Hooks and it has options to render other markup formats.

Duplicate of #6650.
Repository: golang/lint

Issue #415: New import path breaks functionality
Created: 2018-10-11T17:06:41Z
So the changes from this commit breaks functionality for one of my projects:
package github.com/golang/lint/golint: code in directory /go/src/github.com/golang/lint/golint expects import "golang.org/x/lint/golint"

Are we supposed to use the path golang.org/x/lint/golint?

Duplicate issue #417: Cannot use go get 
Created: 2018-10-12T08:03:28Z
Hello
When I try to go get the project I got
$ go get -u github.com/golang/lint/golint
package github.com/golang/lint/golint: code in directory /go/src/github.com/golang/lint/golint expects import "golang.org/x/lint/golint"
It's probably due to commit 5906bd5

Closing comment (2018-10-12T18:14:58Z): Duplicate of #415
Repository: golang/lint

Issue #152: Warnings with Block Comments—Spacing, and Extra Asterisks
Created: 2015-08-03T12:01:58Z
If you begin a block comment with a space, golint does not recognize that it begins with the exported function name.
/* TestFunction does ... */
func TestFunction() {}


comment on exported function TestFunction should be of the form "TestFunction ..."

The following passes without any warnings.
/*TestFunction does ...*/

Some people also prefer using multiple asterisks.
/***TestFunction does ...***/


comment on exported function TestFunction should be of the form "TestFunction ..."

Duplicate issue #157: Warning on multiline package comments with CRLF line endings on Linux.
Created: 2015-09-17T14:35:05Z
I'm using golint 7b7f436 on Ubuntu 15.04.
The following script causes unexpected output.
#!/bin/sh
cat <<EOF > doc.go
/*
Package pkg is a package that does things.
With another line.
*/
package pkg
EOF
unix2dos doc.go
golint doc.go
rm -f doc.go

This outputs:

unix2dos: converting file doc.go to DOS format ...
doc.go:4:1: package comment is detached; there should be no blank lines between it and the package statement

Removing the unix2dos conversion makes golint execute without warning.
So it looks like the inserted CR character is considered as a blank line by itself, which should arguably not be the case.
Also note that removing the "With another line." line instead also silences golint.

Closing comment (2015-09-28T23:14:52Z): This is probably related to #152. Godoc seems to do some amount of post-processing after getting the text from the AST, and we're not matching that.
Repository: golang/lint

Issue #89: Remove or relax rule for "struct field Id should be ID"
Created: 2014-12-10T06:04:09Z
The use of "ID" rather than "Id" breaks the rule about abbreviations vs initialisms. "ID" is an initialism for "Identifying Documents", whereas "Id" is an abbreviation for "identifier". Typically, in software engineering, we are referring to the latter.
I understand that in Google and with a lot of Go code, the use of "ID" is considered the correct style. However, there are cases where code cannot follow this convention, such as when avoiding API breakage.
It would be nice to have the ability to disable this rule, such that we continue using golint for some of its better advice, such as documentation.

Duplicate issue #323: ID is not necessarily an abbreviation / Freudian code
Created: 2017-08-30T23:20:10Z
The linter currently requires variables like GatewayId to be named GatewayID because of this.
The thing is, "Id" in cases like the above is not an initialism/abbreviation/acronym. It is just a shortening from "identifier" or "identification" — not "identity document" or any other two-word term.
I therefore suggest removing ID from that map, because requiring to rename GatewayId to GatewayID does not make any sense.

Closing comment (2017-08-30T23:50:19Z): Duplicate of #89.
Repository: golang/lint

Issue #429: proposal: x/lint: type omission lint fires even when type is necessary for documentation purposes
Created: 2019-01-07T15:10:44Z
I wasn't sure whether to file this as a bug or a proposal, but I would like to remove or disable-by-default the type omission lint. It is the most common false positive I have, and fires often even when the type is necessary for the identifier to show up in the correct place in the documentation.
For example, in mellium.im/xmpp/compress this lint fires for the following:
var (
    // LZW implements stream compression using the Lempel-Ziv-Welch (DCLZ)
    // compressed data format.
    LZW Method = lzwMethod
)
However, without the type, the list of supported compression methods does not show up under the Method type. Instead it shows up at the top of the package level docs and it is no longer obvious that these are existing methods that can be passed to New. In such a small package it doesn't really matter, but in larger packages it can be absolutely necessary to group values under their type.
This isn't technically a problem with Go code (which is what the linter is made to find), but I do think the lint is often encouraging bad practice and unreadable docs, which seems like a good enough reason to get rid of it since it doesn't really provide any benefit that I can see but does have this down side.
Moved from golang/go#26274

Duplicate issue #307: Golint wants to elide type that can be inferred, but this breaks docs
Created: 2017-07-09T18:43:15Z
I found a number of closed issues about golint wanting to elide types that couldn't actually be inferred, but I'd like to dispute that this warning is necessary; it can actually be harmful (eg. it's not just a matter of style). For example, consider the following API:
package foo

type Foo string

var (
    // Bar is some common, predeclared Foo.
    Bar Foo = Foo("one")

    // Baz is some other common Foo.
    Baz Foo = Foo("two")   
)
If we godoc foo against this package, our common Foo vars are grouped under the Foo type. However, golint complains about the unnecessary type, but if we remove it to make golint happy, then the list of common Foos appears in a vars section at the top of the document which may be nowhere near Foo in a large package, and is very confusing.
Maybe golint could warn about mixed inferred types (probably only in lists where all the RHS types were the same) instead, so it would not warn on the above, but would warn on:
var (
    // Bar is some common, predeclared Foo.
    Bar Foo = Foo("one")

    // Baz is some other common Foo.
    Baz = Foo("two")   
)
An experimental implementation of this idea can be found in 1426a3b

Closing comment (2019-08-22T15:25:08Z): Oops, made a duplicate somehow. Closing this as a duplicate of #429
Repository: golang/lint

Issue #239: Avoid generated files
Created: 2016-09-07T18:43:14Z
Generated source files are not generally expected to follow proper Go style. For example, running lint on a protobuf-generated Go file reports hundreds of lint issues.
With the upcoming generator disclaimer headers, we should consider having lint ignore these types of source files: golang/go#13560

Duplicate issue #268: Golint should ignore files with `DO NOT EDIT` in comments
Created: 2017-01-12T10:42:39Z
I sometimes ran into golint errors on generated files and have to manually ignore those files from CI scripts.
Generated files often have DO NOT EDIT in comments. So I suggest to make golint smarter by ignoring files which have DO NOT EDIT in comments.

Closing comment (2017-01-12T16:36:26Z): Closing as duplicate of #239.
Repository: golang/lint

Issue #415: New import path breaks functionality
Created: 2018-10-11T17:06:41Z
So the changes from this commit breaks functionality for one of my projects:
package github.com/golang/lint/golint: code in directory /go/src/github.com/golang/lint/golint expects import "golang.org/x/lint/golint"

Are we supposed to use the path golang.org/x/lint/golint?

Duplicate issue #419: Error getting package
Created: 2018-10-12T17:07:06Z
I have a project that uses golint and installs it inside the docker container. It have been working ok for month (and have been built multiple times), but today when I build the container again I get the following error:
go get -u github.com/golang/lint/golint
package github.com/golang/lint/golint: code in directory  /a-go-path/golang/lint/golint expects import "golang.org/x/lint/golint"
I can replicate the issue locally on my computer by typing go get github.com/golang/lint/golint. I am using go 1.11.0

Closing comment (2018-10-12T18:12:42Z): Duplicate of #415
Repository: golang/lint

Issue #415: New import path breaks functionality
Created: 2018-10-11T17:06:41Z
So the changes from this commit breaks functionality for one of my projects:
package github.com/golang/lint/golint: code in directory /go/src/github.com/golang/lint/golint expects import "golang.org/x/lint/golint"

Are we supposed to use the path golang.org/x/lint/golint?

Duplicate issue #414: Code in directory expects import "golang.org/x/lint/golint"
Created: 2018-10-11T15:53:20Z
package github.com/golang/lint/golint: code in directory /Users/username/src/github.com/golang/lint/golint expects import "golang.org/x/lint/golint"

Closing comment (2018-10-11T21:02:08Z): Duplicate of #415
Repository: golang/lint

Issue #47: Allow underscores in variable names between numbers
Created: 2014-07-25T18:15:08Z
One reason to have an underscore in a variable name is to simulate a decimal in a number, for example
case3_1
Golint suggests a correction to case31 which does not have the same feel. One could argue about the merits of case3_1 as a variable name, but in any event the correction should not be to elide the underscore.

Duplicate issue #56: Go lint should not flag underscores between numbers
Created: 2014-08-30T19:45:14Z
Right now, the linter flags symbols like AutoISO14443_4 as not conforming to the Go naming conventions and suggests removing the underscore. I expect that removing an underscore between numbers is almost never a good suggestion as the underscore usually separates different numbers from one another. I request the linter to not issue a warning for such occurances of underscores.

Closing comment (2014-09-01T06:13:14Z): Duplicate of #47.
Repository: golang/lint

Issue #68: lint test packages
Created: 2014-09-16T12:15:11Z
I know there's a TODO item for this
https://github.com/golang/lint/blob/master/golint/golint.go#L116
but after the switch to package mode, it's hard to lint the whole package at one go if tests include both pkg and pkg_test without seeing X is in package pkg, not pkg_test, so IMO this is more of a necessity now.

Duplicate issue #200: golint doesn't check xtest files
Created: 2016-04-01T03:00:39Z
Consider the following shell session:
dominikh-pc ~ $ GOROOT=~/go golint ~/go/src/net/http/serve_test.go        
/home/dominikh/go/src/net/http/serve_test.go:1070:6: don't use underscores in Go names; func testAutomaticHTTP2_ListenAndServe should be testAutomaticHTTP2ListenAndServe
dominikh-pc ~ $ GOROOT=~/go golint net/http | grep serve_test     
dominikh-pc 1? ~ $ 
$ GOROOT=~/go golint net/http | grep _test
/home/dominikh/go/src/net/http/export_test.go:26:2: var ExportHttp2ConfigureTransport should be ExportHTTP2ConfigureTransport
/home/dominikh/go/src/net/http/export_test.go:27:2: var ExportHttp2ConfigureServer should be ExportHTTP2ConfigureServer
/home/dominikh/go/src/net/http/readrequest_test.go:29:24: should drop = nil from declaration of var noTrailer; it is the zero value

When checking the net/http package, there are no linter warnings for the serve_test.go file. When checking that file individually, there are warnings. The third invocation is there to prove that it's looking in the right directory and that it does check tests, so that rules out two possible causes.

Closing comment (2016-04-04T14:59:11Z): I would be happy to finish up #153. We are using the PR in production for a very long time now but I haven't got the time to test it with Go 1.6 since we are still on 1.4 (looking forward to reduced build times in 1.7). Also, why does nobody here mention the lack of build tag support in golint which is also fixed by this PR? ;-)
Btw. isn't this a duplicate of #68 ?
Repository: golang/vscode-go

Issue #2816: gopls: automated issue report (initialization)
Created: 2023-06-12T08:54:22Z
gopls version: v0.12.2
gopls flags:
extension version: 0.23.0
environment: Visual Studio Code darwin
initialization error: Error: JSON RPC parse error: json: cannot unmarshal bool into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type protocol.PrepareSupportDefaultBehavior
manual restart count: 0
total start count: 1
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

Starting client failed
  Message: JSON RPC parse error: json: cannot unmarshal bool into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type protocol.PrepareSupportDefaultBehavior
  Code: -32700 
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

Duplicate issue #2817: gopls: automated issue report (initialization)
Created: 2023-06-12T08:54:54Z
gopls version: v0.12.2
gopls flags:
extension version: 0.23.0
environment: Visual Studio Code darwin
initialization error: Error: JSON RPC parse error: json: cannot unmarshal bool into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type protocol.PrepareSupportDefaultBehavior
manual restart count: 0
total start count: 2
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.

Failed to auto-collect gopls trace: unrecognized crash pattern.
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

Closing comment (2023-06-12T14:59:08Z): Duplicate of #2816
Repository: golang/vscode-go

Issue #1772: testExplorer/go1.18: support running multiple subtests
Created: 2021-09-10T20:52:55Z
CL 343883 has been merged and presumably will be available in Go 1.18. When the user is using Go 1.18, this should allow us to run multiple subtests simultaneously.

Given -run 'A/B|C/D'
Go ≤ 1.17 interprets this as "Match test A → subtest B|C → subtest D"
Go ≥ 1.18 should interpret this as "Match test A → subtest B or test C → subtest D"

Now that the precedence (at the top level) of alternation | is higher than the precedence of the test/subtest separator /, it is easy to construct a regex that will strictly match the requested tests and subtests (once 1.18 is released).

Duplicate issue #122: parse test output and suggest re-running failed subtests
Created: 2020-05-28T22:13:17Z
microsoft/vscode-go#2850 contains the discussion that lead to the conclusion that there is a need to re-run failed tests from the last test run.
This feature request is to parse the test output, identify failed tests and provide a command to re-run just the failed tests.
Code Pointers from the old repo:

Set up local dev environment for the extension
goTest() is the function that calls go test and parses the output. It is here that you will need to keep track of the failed test names and return them in the rejected promise.
Use the code for the Go: Test Previous command at https://github.com/microsoft/vscode-go/blob/0.12.0/src/goTest.ts#L226-L237 as a reference to have a new command Go: Test Previously failed tests.
You will need a copy of the latestTestConfig which has its functions updated to be reflect the name of the failed tests.

Closing comment (2021-09-22T23:18:58Z): I confirm that v0.28.0 dynamically finds subtests and provides UI to rerun the subtests.
Running multiple subtests is tracked in #1772.
Thanks @firelizzard18 for the awesome work!
Debugging support is in progress AFAIK.
Repository: golang/vscode-go

Issue #2717: gopls: automated issue report (initialization)
Created: 2023-04-01T06:53:42Z
gopls version: v0.11.0 (go1.20.2)
gopls flags: --cache-style=always
update flags: proxy
extension version: 0.38.0
go version: 1.20.2
environment: Visual Studio Code darwin
initialization error: Error: Pending response rejected since connection got disposed
issue timestamp: Sat, 01 Apr 2023 06:53:26 GMT
restart history:
Sat, 01 Apr 2023 06:53:07 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.

Failed to auto-collect gopls trace: no gopls log.
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

Duplicate issue #2718: gopls: automated issue report (initialization)
Created: 2023-04-01T07:15:14Z
gopls version: v0.11.0 (go1.20.2)
gopls flags: --cache-style=always
update flags: proxy
extension version: 0.38.0
go version: 1.20.2
environment: Visual Studio Code darwin
initialization error: Error: Pending response rejected since connection got disposed
issue timestamp: Sat, 01 Apr 2023 07:15:11 GMT
restart history:
Sat, 01 Apr 2023 07:07:18 GMT: activation (enabled: true)
Sat, 01 Apr 2023 07:15:00 GMT: installation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.

Failed to auto-collect gopls trace: no gopls log.
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

Closing comment (2023-04-03T17:03:16Z): Dupe of #2717.
Repository: golang/vscode-go

Issue #2049: ui: view for `go env` and important settings that affects go's functionality
Created: 2022-02-02T16:34:17Z
There are dozens of settings and environment variables affecting how go command works.
go env or commands to inspect environment variables is a typical way to inspect them,
but often the environment the extension (or vscode extension host) is different from what
users see from their terminals (e.g. users use shell config that does not get invoked when
vscode launches, etc.). That causes confusions numerous times.
We added some of the info in the Go: Locate Configured Tools command output, but
the output is verbose and text-heavy. It's time to think about better UI. An option is View.
Info to included in the new Go Env view

go env output

GOWORK (related to #2032)
GOMOD
GOOS
GOARCH
GOENV
GOFLAGS
GOPRIVATE
GOBIN
GOPATH
GOROOT
...


Path to the go command (or GOROOT)
List of tools

Name, path, version


settings affecting build/test (e.g. go.buildFlags, or tags)

Future work
This view may be extended in the future to have associated commands

to open the associated resources (e.g. open go.mod file)
to trigger setting changes (e.g. Allow setting GOOS via UI)
to update tools

Remarks


The info in the view may need to change depending on the workspace root folder the open file belongs to.


I cannot think of a good existing default container (explorer/scm/debug/test) where this new view belongs to yet. We may need to create a custom view container for Go - where we can organize more go-project specific information (Module/Package dependencies, Package doc, ...)


cc @jamalc @golang/tools-team

Duplicate issue #1630: ui: make it clear to present the environment setting the extension is using
Created: 2021-07-19T15:00:12Z
As discussed in #1595 and other bug reports,
VSCode Go inherits the environment variables the vscode window is launched with.
And then, go.toolsEnvVars can be used to override some of them more explicitly.
Go: Locate Configured Go Tools provide a hacky way of showing the list of env vars
but that doesn't show how the extension picked them up. That leads confusion.
Improve the UI/UX and clearly display

what environment variables are in effect
why (e.g. extension host's env var, go.toolsEnvVars setting, go, or the extension's manipulation)

and, ideally an interface to override them easily.

Closing comment (2022-02-18T15:17:19Z): Duplicate of #2049
Repository: golang/vscode-go

Issue #1300: 📌  v0.23.1+ requires gopls 0.6.6 or newer
Created: 2021-03-12T01:27:24Z
Please update gopls if you see errors like the following
Starting client failed
  Message: JSON RPC parse error: json: cannot unmarshal number into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type bool: JSON RPC parse error
  Code: -32700 
 
or

Choose to update it.
If the above popup didn't appear (maybe because GOPROXY isn't reachable)
Run Ctrl+Shift+P -> "Go: Install/Update Tools" -> Select gopls -> OK

Or, if you want to install it manually,
  GO111MODULE=on go get golang.org/x/tools/gopls@latest

Duplicate issue #1326: gopls: automated issue report (initialization)
Created: 2021-03-12T14:01:56Z
gopls version: v0.6.4
gopls flags:
extension version: 0.23.1
environment: Visual Studio Code darwin
initialization error: Error: JSON RPC parse error: json: cannot unmarshal number into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type bool: JSON RPC parse error
manual restart count: 1
total start count: 2
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

Starting client failed
  Message: JSON RPC parse error: json: cannot unmarshal number into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type bool: JSON RPC parse error
  Code: -32700 
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

Closing comment (2021-03-12T14:17:41Z): Thanks for the report. @nitronick600
This is a duplicate of #1300
Please update gopls following the instruction.
Repository: golang/vscode-go

Issue #1300: 📌  v0.23.1+ requires gopls 0.6.6 or newer
Created: 2021-03-12T01:27:24Z
Please update gopls if you see errors like the following
Starting client failed
  Message: JSON RPC parse error: json: cannot unmarshal number into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type bool: JSON RPC parse error
  Code: -32700 
 
or

Choose to update it.
If the above popup didn't appear (maybe because GOPROXY isn't reachable)
Run Ctrl+Shift+P -> "Go: Install/Update Tools" -> Select gopls -> OK

Or, if you want to install it manually,
  GO111MODULE=on go get golang.org/x/tools/gopls@latest

Duplicate issue #1349: gopls: automated issue report (initialization)
Created: 2021-03-16T01:09:16Z
gopls version: v0.6.5
gopls flags:
extension version: 0.23.2
environment: Visual Studio Code linux
initialization error: Error: JSON RPC parse error: json: cannot unmarshal number into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type bool: JSON RPC parse error
manual restart count: 0
total start count: 1
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

Starting client failed
  Message: JSON RPC parse error: json: cannot unmarshal number into Go struct field RenameClientCapabilities.capabilities.textDocument.rename.prepareSupportDefaultBehavior of type bool: JSON RPC parse error
  Code: -32700 
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

Closing comment (2021-03-16T01:38:11Z): Duplicate of #1300
Repository: golden-layout/golden-layout

Issue #146: Dragging Single Programatically-Added Tab is Frozen Or Disappears Completely
Created: 2016-09-28T14:43:02Z
I'm reporting this issue, but need it fixed so will post my solution, the Pull Request or at least relevant code in our fork once I figure out the solution.
You can actually see the issue with an existing GL demo: https://www.golden-layout.com/examples/#cdcb9de8e7b305d2ec81b4ae4e392832
When the example page loads:

Delete both existing tabs
Click one of the buttons to add a new tab to the now empty GL
Try to drag the tab created in step 2.  Notice how the 'dropzone' is NOT created and when you release the mouse button, the tab just disappears.

Here's an image (notice no dashed drop target):

Here's what happens when you release the mouse button (tab just disappears and doesn't re-dock)

I believe the issue resolves around Adding/Removing items to the root panel and dragging them.
Once you have 1 or more tabs in the "root" container, drag and drop works fine because the element structure becomes:


<stack 1></stack 1>
<stack 2></stack 2>


But when you only have 1 tab in the "root" container, the element structure is:

<stack 1></stack 1>

And dragging the stack 1 element fails b/c there's no "parent contentItem" because it's the root panel (as opposed to another contentItem type).
Will report back as I work on a solution.

Duplicate issue #55: Unable to drag a drag source back out of a layout.
Created: 2015-04-29T15:08:38Z
When you drag a drag source into a layout, then you drag it out of a layout without dropping, the component will still build inside the layout.
Expected Behavior:
Dragging a drag source or a pane outside the layout will remove it from the layout.

Closing comment (2017-04-03T18:05:06Z): This is similar to #146.  The workaround I am using is detecting when this occurs, and then regenerating the entire layout.
Repository: golden-layout/golden-layout

Issue #260: TypeScript definition for GoldenLayout should extend EventEmitter
Created: 2017-04-28T10:14:44Z
At the moment, the TS definition for the GoldenLayout class does not have the 'on' function to subscribe to events.  Shouldn't this extend from EventEmitter?

Duplicate issue #300: Unexpected event behavior in particular when used with TypeScript
Created: 2017-06-21T15:52:47Z
Current behavior
If you create a layout using TypeScript you can not call the event methods on the layout like you should be able to, and if you use the eventHub it doesn't work.
e.g.
let myLayout = new GoldenLayout(config);
myLayout.on('initialised' function() { do stuff; }); // TypeScript complains that property "on" does not exist on type GoldenLayout.
myLayout.eventHub.on('initialised', function() { do stuff; }); //This event never gets triggered when myLayout is initialised. It only gets triggered if manually emitted using something like the line below.
myLayout.eventHub.emit('initialised'); //This does hit the event above.
Expected behavior:
I would expect that myLayout.eventHub.on('initialised'.... would get hit when myLayout is initialised, or that the eventHub would be removed from the GoldenLayout object and the event methods would be added in the typescript typings.
Related issue #260

Closing comment (2020-01-29T21:32:04Z): Duplicate of #260
Repository: golden-layout/golden-layout

Issue #77: How to change the layout runtime without creating new layouts content or config.
Created: 2016-01-20T15:45:24Z
I created the new layout content on button click and bind with existing page but it emits event multiple times because of existing emit in golden layout.
can you please give an example to change the layout on button click in same page.

Duplicate issue #140: Is there a way to re run the config after init()
Created: 2016-09-20T09:53:43Z
Hi,
I'm new to golden-layout, is there a way to re run the config after init(). We want to start with a clean design but the user should be able to activate the golden layout magic.
The golden layout works fine within a angular based ui-route ng-view :-)
sincerely
Johannes

Closing comment (2020-01-23T22:44:05Z): Duplicate of #77
Repository: golden-layout/golden-layout

Issue #68: Popup windows are not supported natively
Created: 2015-09-08T06:34:03Z
My company is currently analysing GL for a future project and wondered whether popup windows could be supported (we know Pop-Out windows are supported). At present this is not built in behaviour and so we are using another solution along side GL to provide this functionality (i.e. ngPopup), is it possible to implement this functionality ???

Duplicate issue #132: Support for un-docked components?
Created: 2016-09-08T00:11:56Z
I need the ability to undock a tab/component and leave it as a floating "window" on the webpage. Is it possible?

Closing comment (2020-01-28T06:16:54Z): Duplicate of #68 .
Repository: golden-layout/golden-layout

Issue #180: Is there a way to collapse a panel to just the tab?
Created: 2016-12-18T04:25:40Z
Wanted to use this to do a left panel that can collapse to a bar with the tab text rotated 90 deg. Is that possible and is there a sample somewhere like that?

Duplicate issue #247: collapsible panels like visual studio
Created: 2017-04-07T08:30:38Z
I have a requirement to collapse a panel, with the tab text rotated 90 degree and make some space for other panels and again collapse the panel.
Any quick pointers will be helpful so that I can implement it if its not there

Closing comment (2017-04-07T09:03:33Z): Duplicate
#180
#245
Repository: golden-layout/golden-layout

Issue #151: Popout dont work with angular ngview
Created: 2016-09-30T14:27:17Z
I am using Golden layout my angularJS project. index.htm is my main page, whereas main.htm is my default partial page containing golden layout. I am loading main.htm in index.htm using ng-view routing.
Everything work perfect, but when i click on popout button it loads new window with all content of index.htm inspite of just poping out a single tab.

Duplicate issue #246: Electron pop-in/pop-out
Created: 2017-04-05T14:10:14Z
I'm using golden-layout with angular on Electron. The layout is working more or less okay but I can't pop-win a window after a pop-out occurred.
Does anyone know how to solve this?

Closing comment (2020-01-28T19:45:44Z): Duplicate of #151
Repository: golden-layout/golden-layout

Issue #239: Elements inserted are not immediately jQuery selectable
Created: 2017-03-30T21:15:43Z
I'm not quite sure if you'll regard this as a bug or not, since this is a matter of defined correct behaviour, but it is very annoying, and it has arisen because it breaks my jQuery plugin which I wanted to bang into a golden-layout window, which I thought would be easy...
Current behaviour
Adding elements to container during the registerComponent callback does not make them immediately selectable. I presume, though I've not confirmed this, that this is because the container is not in the DOM at the time.
Current behaviour is that appending an element with id "foo" to the container works, but then evaluating $('#foo') does not find it.
myLayout.registerComponent( 'example', function( container, state ){
  var jq_container = $(container.getElement());
  jq_container.append('<div id="'+state.text+'"></div>');
  $('#'+state.text).append($('<div style="color:white">This is '+state.text+'</div>'));
});

Also, and a little more to my surprise, even evaluating $('#foo') immediately after the myLayout.registerComponent() returns and after myLayout.init() has completed, it can still find no elements.
Expected behaviour:
Adding an element should cause it to be there and selectable.
Codepen example:
This demonstrates the issue: https://codepen.io/mjwright/pen/ryoVJG
Note, I have commented out 2 lines, which, when uncommented, resolves the problem (white text is now shown in the goldenlayout windows), presumably because it is deferred long enough for the elements to be inserted into the DOM. Not entirely sure if this would always be a reliable fix though, even with an actual delay.
This is the relevant code:
myLayout.registerComponent( 'example', function( container, state ){
  var jq_container = $(container.getElement());
  jq_container.append('<div id="'+state.text+'"></div>');
  //setTimeout(function () {
  $('#'+state.text).append($('<div style="color:white">This is '+state.text+'</div>'));
  //});
});

Duplicate issue #273: DOM is not ready when open event is called
Created: 2017-05-15T22:42:52Z
Current behavior
Adding a component at runtime causes the open event to be emitted before the DOM is ready
Expected behavior:
The component to be added to the DOM to be accessible by document.getElementById
As per documentation:
Open
Emitted after the item has been sized and added to the DOM. Useful if you're working with an UI library that measures its container on startup.
Codepen example:
codepen.io/victus/pen/XRYQRL

Closing comment (2020-01-29T13:57:42Z): duplicate of #239
Repository: golden-layout/golden-layout

Issue #114: Hide headers (hasHeaders) for certain components (not global)
Created: 2016-06-21T13:57:32Z
Hi DeepstreamIO,
I've found configuration parameter 'hasHeaders', but it's a global parameter for all components. We need to hide headers from certain components only. Is there a way to accomplish this?
Thank you,
Best regards,
Bastiaan

Duplicate issue #388: How to hide the particular tab header..?
Created: 2017-12-12T12:19:53Z
myLayout.config.settings.hasHeaders=false
I used above one but these hiding all headers i need to hide only particular header using above code

Closing comment (2017-12-13T09:45:25Z): Closing as duplicate of #114
Repository: golden-layout/golden-layout

Issue #534: Reloading (F5) in a popup window cause an error.
Created: 2019-08-07T15:52:28Z
Current behavior
Press F5 in a popup window. It fails to reload.
Expected behavior:
It should reload the popup using the current configuration for this popup.
Codepen example:
https://codepen.io/ButchMonkey/pen/GzGZey

Duplicate issue #578: Refreshing popout causes empty screen
Created: 2020-05-01T00:48:21Z
I'm using GoldenLayout with React and I'm unable to refresh any popout windows from this. Console shows this error message whenever I try to.
Uncaught TypeError: Cannot read property '0' of undefined
    at push../node_modules/golden-layout/dist/goldenlayout.js.lm.LayoutManager._adjustToWindowMode (goldenlayout.js:1282)
    at push../node_modules/golden-layout/dist/goldenlayout.js.lm.LayoutManager.init (goldenlayout.js:699)

Current behavior
Refreshing a popout window made from GoldenLayout showcases an empty screen. Console shows this crypted error message
Expected behavior:
Should reload the page and display the component.

Closing comment (2020-05-01T04:59:24Z): this issue is a duplicate of #534
Repository: golden-layout/golden-layout

Issue #513: Update NPM Packages
Created: 2019-05-18T21:01:48Z
To fix a couple of small issues and security issues, I will look into upgrading npm packages as long as they don't affect functionality.
This will be an ongoing list until release

  webpack-dev-server
  handlebars

More TBC

Duplicate issue #517: npm package and typescript definitions out of date?
Created: 2019-05-24T10:45:44Z
Hi,
I noticed that the npm package has last been updated in 2017.
(https://www.npmjs.com/package/golden-layout)
Since then several updates have been made to golden-layout according to the list of commits.
Shouldn't the changes be made available over npm too?
Additionally I noticed that the typescript definitions in index.d.ts do not reflect the current state of the project. For example: according to index.d.ts there is no such field as 'reorderEnabled' on item level although it can be used. When calling GoldenLayout.toConfig 'reorderEnabled' is present on item level.
This also applies to the documentation (http://golden-layout.com/docs/ItemConfig.html) where there is no mention of 'reorderEnabled' in ItemConfig.
Are there any plans to update this?

Edit: I have seen that the latest release matches the one on npm. But it is also from 2017.
When is the next release planned?

Closing comment (2020-01-30T14:44:09Z): Duplicate of #513.
Repository: google/accompanist

Issue #730: Provide a method to make the bottom sheet non-cancellable for some use-cases.
Created: 2021-09-17T14:14:11Z
Describe the bug
Provide a method to make the bottom sheet non-cancellable for some use-cases.
Expected behaviour
When a user clicks the back button or the outside content of the bottom sheet, then it dismisses. However, there should be a way to control that behaviour based on a flag that the bottom sheet should not dismiss. It should only dismiss via calling navGraph.navigateBack().
Environment:

Android OS version: [Android 11.0]
Device: [Samsung M20]
Accompanist version: [0.17.0]

Duplicate issue #1512: [Navigation Material] Disable dismissing a bottom sheet route
Created: 2023-02-11T05:49:35Z
Description
Is there a way to make a certain bottom sheet route not dismissible when tapping on the area outside the sheet?

Closing comment (2023-02-17T16:50:08Z): This is a duplicate of #730, please follow along. Unfortunately, we are working on other high-priority items at the moment and can not provide an ETA.
Repository: google/accompanist

Issue #657: [Idea] Add ability to fully expanded BottomSheetNavigator by default
Created: 2021-08-17T07:28:33Z
Is your feature request related to a problem? Please describe.
I'm trying to migrate some bottom sheets from "ScafoldBottomSheet" to the new Navigation Compose Material, however, I cannot find a way to start the sheet as fully expand — similar to the behaviour of ScafoldBottomSheet —, so it always starts as HalfExpanded which is not ideal for some use cases.
Describe the solution you'd like
The solution is to lock the expansion to Expanded and skip HalfExpanded when the size of the sheet content is over half of the screen height.
Describe alternatives you've considered
The class "SheetContentHost" contains a method called "ModalBottomSheetState.internalShow()" which could control if the initial expansion is the default behaviour (half expanded if the sheet is over half of the screen height) or it should lock to the full height of the content.
The "rememberBottomSheetNavigator" could receive the extra parameter controlling the expansion and pass it down to the SheetContentHost when appropriate.
Thanks

Duplicate issue #1732: [Navigation Material] 
Created: 2023-12-01T11:25:29Z
Description
Is it possible to show the bottomSheet navigator's destination with fully opened bottom sheet?
I expect to find the skipHalfExpanded: Boolean parameter here as it is in ModalBottomSheet

Closing comment (2023-12-04T04:48:41Z): Duplicate of #657