gopkg | io os os/exec os/signal_user path path

You have to export the fields in your struct. As stated in the api-documentation:

Struct fields are only unmarshalled if they are exported (have an upper case first letter), and are unmarshalled using the field name lowercased as the default key.

(https://github.com/go-yaml/yaml/blob/496545a6307b/yaml.go#L88)

Changing your Target-struct to:

Moving Comment to answer

I see a problem in your code the link you have shared is https://github.com/go-playground/validator but in the code, import is gopkg.in/validator.v2 If you are using the go-playground validator Use below code to validate

If you don't specify the mapping between labels used in the YAML source and Go struct fields, by default they will only be matched if only changing the first letter to lower matches.

E.g. the struct field Name will match name, but not NAME.

Specify the mapping for the HTTP field:

According to the documentation you should make the struct fields public in order for unmarshal to correctly populate the data.:

Struct fields are only unmarshalled if they are exported (have an upper case first letter)

Your code works as expected after changing the type definitions as follows:

Now that we found the error, let's have a post mortem about what happened:

The library you used, github.com/ghodss/yaml, says that

this library first converts YAML to JSON using go-yaml and then uses json.Marshal and json.Unmarshal to convert to or from the struct.

It doesn't particularly help that the linked blog post about why this would be a good idea vanished. Anyway, let's see what the code there actually does:

I like to share also the answer here for a template that builds a go modules package correctly. Maybe this is just for your inspiration what needs to be considered. It took me some time to get there.

The main pain point is that the the default template sets the GOPATH to the pipeline workingdirectory which is just wrong if you will download modules via go mod download into it. This would lead to inaccesible files in the next pipeline run, making the pipeline failing during repository checkout.

The following approach just sets GOPATH to the Agent.HomeDirectory which also makes downloaded modules available for subsequent pipeline runs.

Maybe it helps someone

No, it is not possible to search package descriptions with conda search. The query results of conda search, including those with the --info|-i flag, do not include package description info.

There is limited functionality for retrieving package summaries from Anaconda Cloud. This is provided by the anaconda show command in the package anaconda-client and only provides exact matching (channel and package). For example,

The issue is that different tools you use produce binary in (or run binary from) different place. Path to config.ini in your code is specified as relative to process' current working directory. If you want non-invasive solution you'd need to change your workflow (where you build and run the main binary, debugger or go test) or you can implement some fallback mechanism or environment variable that will override default path to config file.

In VSCode there should be cwd variable in launch.json configuration that allows you to set working directory. You should be able to set cwd: "${workspaceFolder}" and that should work as if you run commands from the root of repository.

See https://code.visualstudio.com/docs/editor/variables-reference for variables reference.

The gist of this error is that the version of binary used to generate the code isn't compatible with the current version of code. A quick and easy solution would be to try updating the protoc-gen-go compiler and the gRPC library to the latest version.

go get -u github.com/golang/protobuf/protoc-gen-go

then regen the proto

heres a link to a reddit thread that discusses the issue