[go-nuts] Re: Go 1.16.7 and 1.15.15

[shan...@gmail.com]

Ok lazyreader (IRC) has discovered that the release has a  commit, relating 
to a CVE on handler panics that we think is the reason for the release 
(fixed my previously erroneous assertion of a single commit, and tidied up 
the wording a little)

The changeset is
https://go-review.googlesource.com/c/go/+/338551/2/src/net/http/httputil/reverseproxy.go


On Thursday, August 5, 2021 at 8:30:23 AM UTC+10 shan...@gmail.com wrote:

>
> Hi all
>
> My bot picked up that there was a release from github of Go for versions 
> 1.16.7, and 1.15.15
>
> But I cannot find any release notes or supporting documentation, and the 
> release hasn't (yet) made it to downloads
>
> Was this an unintentional release?
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/b218a633-a34d-4365-807c-982510d24a40n%40googlegroups.com.

[go-nuts] Re: Go 1.16.7 and 1.15.15

[shan...@gmail.com]

Ok lazyreader (IRC) has discovered that the release has a single commit, 
relating to a CVE relating to handler panics

The changeset is
https://go-review.googlesource.com/c/go/+/338551/2/src/net/http/httputil/reverseproxy.go

On Thursday, August 5, 2021 at 8:30:23 AM UTC+10 shan...@gmail.com wrote:

>
> Hi all
>
> My bot picked up that there was a release from github of Go for versions 
> 1.16.7, and 1.15.15
>
> But I cannot find any release notes or supporting documentation, and the 
> release hasn't (yet) made it to downloads
>
> Was this an unintentional release?
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/d29c3783-b974-4c0e-8c71-a4d581e829f7n%40googlegroups.com.

[go-nuts] Go 1.16.7 and 1.15.15

[shan...@gmail.com]

Hi all

My bot picked up that there was a release from github of Go for versions 
1.16.7, and 1.15.15

But I cannot find any release notes or supporting documentation, and the 
release hasn't (yet) made it to downloads

Was this an unintentional release?

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/4d51dbbc-53fc-4e5e-ac57-65ea1766ac43n%40googlegroups.com.

[go-nuts] [HIRING] Sr. Software Engineers - Developing & Scaling Applications in Go.

[JR Fent]

 

*The Role:*

We’re looking for talented and motivated engineers with 4+ years of 
experience as a professional software engineer.  Our engineers own entire 
features in our system. You'll influence the initial specs for the feature, 
build/modify the backend , write the front-end code to polish it up, and be 
responsible for ongoing improvements once the feature is deployed.

If this opportunity excites you, we encourage you to apply even if you do 
not meet all of the qualifications.

*How You Will Make an Impact:*

   - Own what you build as you architect, test, and refine our platform. 
   - Tackle a wide variety of technical problems up and down the stack and 
   contribute daily to all parts of our code base. 
   - Prototype, iterate, and deploy updates on a daily basis. 
   - Be surrounded by smart, highly motivated teammates with decades of 
   experience in the finance, technology, and payroll industries. 

*What You Bring to The Team:*

   - Strong ability to write idiomatic Go(lang). 
   - Experience in developing and scaling web/platform applications in Go. 
   - Successful track record of building and maintaining large, tested, 
   performant codebases. 
   - Understanding of RESTful frameworks and where their place is in API 
   development. 
   - Experience with orchestration tools (Docker, Kubernetes)  
   - Appreciation for a test-driven, code review culture. 
   - Ability to write well-structured, easily maintainable, well-documented 
   code that balances beauty and pragmatism. 
   - 4-year degree in Computer Science preferred (but not required). 
   - Occasional need to work outside of normal business hours as required 
   to support customers may be required. 

*What We Offer:*

   - Competitive compensation 
   - Opportunity for equity ownership 
   - Exceptional health, vision, and dental care 
   - Employee Resource Groups 
   - Fun company outings and events 
   - Unlimited books from Amazon 
   - Unlimited PTO 
   - 401K with company match 

If you have questions or interest - please let me know.  
jrf...@dailypayengineering.com

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/8fafaf24-6f5a-40f2-a85e-771db6b445f1n%40googlegroups.com.

[go-nuts] Go Doc Tip and Request

[Rich]

I've been dabbling in Go since 2009 -- I grew accustomed to godoc.com, and 
the way godoc formats the documentation. Not that the new pkg.go.dev isn't 
any good -- its a matter of preference because you're used to seeing it one 
way, and pkg.go.dev displays it another. I am not a full time developer, 
and therefore in the hour or so I actually get to write code per day -- 
well I just have not found the time to get to know pkg.go.dev.

My solution is to run my own godoc server on my Mac.  First fire it 
up, godoc -http=localhost:6060 -play.  Then go in to Microsoft Edge, and go 
to http://localhost:6060. Click on the 'packages' button.  Once you've done 
this you can stop the godoc server. Next click on the three dots on the far 
upper right of 'Edge'. Select 'Apps'-->'Install This Site As An App'.  I 
called it 'GoDoc'. 

Open Terminal, go to ~/Applications/Edge\ 
Apps.localized/GoDoc.app/Contents/MacOS.  Move app_mode_loader to 
appGoDoc.  Edit a file in this directory called app_mode_loader.  Put the 
following in that file:
```
#!/bin/bash

nohup /Users/youruser/go/bin/godoc -http=localhost:6060 -play &
/Users/youruser/Applications/Edge\ 
Apps.localized/GoDoc.app/Contents/MacOS/appGoDoc
```

The first line starts the godoc server and listens on port 6060. The second 
line launches Microsoft Edge in App mode for your page.  If you close the 
window -- godoc still runs in the background, I've not found this to be a 
problem. On the first start you do have to give it a second or two as the 
page loads faster than godoc can start to serve. Just refresh. 

The request I have is that if at some point Go Doc takes on a new look like 
pkg.go.dev, consider that some may like the older format, maybe have godoc 
and godoc-old or something like that. 

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/7ef6d703-801e-46e0-a698-0969922cc7c7n%40googlegroups.com.

Re: [go-nuts] Behavior to copy the value of pointer inside another pointer

[Olivier Szika]

Oh Yes,

Thanks!

Le mercredi 4 août 2021 à 17:25:39 UTC+2, bse...@computer.org a écrit :

> On Wed, Aug 4, 2021 at 9:18 AM Olivier Szika  wrote:
>
>> Hi all,
>>
>> I am surprised by the behavior of "&(*var)".
>>
>
> According to the language spec, pointer indirection is addressable:
>
> https://golang.org/ref/spec#Address_operators
>
> Thus, taking the address of an indirection yields the original pointer, 
> not a pointer to a copy of its contents.
>  
>
>>
>> https://play.golang.org/p/CK522lRkddd
>>
>> It is expected?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "golang-nuts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to golang-nuts...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/golang-nuts/5f265699-ed67-4798-92d0-88832a7444d1n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/0e155de2-c0e1-4389-86df-8d83c047a440n%40googlegroups.com.

Re: [go-nuts] Behavior to copy the value of pointer inside another pointer

['Axel Wagner' via golang-nuts]

Yes. From the spec :

For an operand x of pointer type *T, the pointer indirection *x denotes *the
> variable* of type T pointed to by x.


Emphasis mine. "The variable", means it really denotes the storage location
that `x` points to. Not the value or anything like that. Further, then:

For an operand x of type T, the address operation  generates a pointer of
> type *T to x. The operand must be addressable, that is, either a variable, 
> *pointer
> indirection*, or slice indexing operation; or a field selector of an
> addressable struct operand; or an array indexing operation of an
> addressable array. *As an exception to the addressability requirement, x
> may also be a (possibly parenthesized) composite literal*.


Emphasis mine, again. This tells you that the behavior of `&` with
composite literals to allocate a new variable is an exception - in general,
`&` just gives you the address of whatever expression you apply it to. In
this case, specifically, a pointer-indirection denoting, as we've seen
above, the *variable* that x points to.

So, it is completely expected that `&(*p) == p`.

On Wed, Aug 4, 2021 at 5:18 PM Olivier Szika 
wrote:

> Hi all,
>
> I am surprised by the behavior of "&(*var)".
>
> https://play.golang.org/p/CK522lRkddd
>
> It is expected?
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/5f265699-ed67-4798-92d0-88832a7444d1n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAEkBMfGYofdV4cd%3DZXC%2B5itONTKog9KP7ELQHNBGBjoQ8yENYw%40mail.gmail.com.

Re: [go-nuts] Behavior to copy the value of pointer inside another pointer

[burak serdar]

On Wed, Aug 4, 2021 at 9:18 AM Olivier Szika 
wrote:

> Hi all,
>
> I am surprised by the behavior of "&(*var)".
>

According to the language spec, pointer indirection is addressable:

https://golang.org/ref/spec#Address_operators

Thus, taking the address of an indirection yields the original pointer, not
a pointer to a copy of its contents.


>
> https://play.golang.org/p/CK522lRkddd
>
> It is expected?
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/5f265699-ed67-4798-92d0-88832a7444d1n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAMV2Rqpi9WBCX1%3D4H2DGVbXCf%3DyQgWPGkUZn%3DiqH52TsfTas-g%40mail.gmail.com.

[go-nuts] Behavior to copy the value of pointer inside another pointer

[Olivier Szika]

Hi all,

I am surprised by the behavior of "&(*var)".

https://play.golang.org/p/CK522lRkddd

It is expected?

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/5f265699-ed67-4798-92d0-88832a7444d1n%40googlegroups.com.

[go-nuts] Re: go list -u -m -json all

[Jérôme LAFORGE]

Go 1.17RC2 fixes this issue.
Thanks all contributors.

Le lundi 26 juillet 2021 à 09:11:53 UTC+2, Jérôme LAFORGE a écrit :

> FYI, I just seen an issue has been already opened : 
> https://github.com/golang/go/issues/47377
>
> Le dimanche 25 juillet 2021 à 21:02:29 UTC+2, Jérôme LAFORGE a écrit :
>
>> Unfortunately, it didn't help me.
>> I ran `go mod download` before `go list -u -m -json all` without change.
>>
>>
>> Le dimanche 25 juillet 2021 à 10:35:55 UTC+2, Tamás Gulácsi a écrit :
>>
>>> go mod download
>>> helped me.
>>>
>>> jerome@gmail.com a következőt írta (2021. július 25., vasárnap, 
>>> 9:49:40 UTC+2):
>>>

 Hello,
 I am currently testing `go1.17rc1 linux/amd64` in my dev env.

 With this version `go list -u -m -json all` seems not work anymore (I 
 use it to know which module is outdated thanks to 
 https://github.com/psampaz/go-mod-outdated#usage)

 I have this error even if I do `go mod tidy` before to do `go list -u 
 -m -json all`
 go: updates to go.sum needed, disabled by -mod=readonly


 I don't know if it can be considered as issue with this rc.

 Jérôme




-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/a36e6649-ae89-458a-8522-40ccb0979354n%40googlegroups.com.

Re: [go-nuts] How to use errors.As with sentinel errors?

[Andreas Götz]

Opened https://github.com/golang/go/issues/47528

On Monday, August 2, 2021 at 6:30:04 PM UTC+2 Andreas Götz wrote:

> > Because both are of type `*errors.errorString`, so the types match and 
> it copies over the value.
> Arguably, `errors.errorString` should implement `As()` and return `false`, 
> unless the pointers match. I suggest filing an issue.
>
> Will do. It could also be a vet check to highlight errors.As used on 
> sentinel errors which is most likely wrong as I demonstrated.
>
> On Monday, August 2, 2021 at 10:09:48 AM UTC+2 axel.wa...@googlemail.com 
> wrote:
>
>> On Mon, Aug 2, 2021 at 10:02 AM cpu...@gmail.com  
>> wrote:
>>
>>> Consider this example: https://play.golang.org/p/16cU0kc8Lku, basically
>>>
>>> var Err = errors.New("sentinel")
>>> err := errors.New("foo")
>>> if errors.As(err, ) {
>>>   fmt.Println("why?")
>>> }
>>>
>>> I'm wondering why this matches the sentinel error
>>>
>>
>> Because both are of type `*errors.errorString`, so the types match and it 
>> copies over the value.
>> Arguably, `errors.errorString` should implement `As()` and return 
>> `false`, unless the pointers match. I suggest filing an issue.
>>  
>>
>>> or rather how to properly use sentinel errors.
>>>
>>
>> Use `errors.Is`, instead of `errors.As`.
>>  
>>
>>> However, if thats the case, how should I construct a sentinel error that 
>>> would be usable with errors.As? I don't want to rely on errors.Is as errors 
>>> could be wrapped.
>>>
>>
>> And? They can be wrapped for `As` as well. `errors.As` is only useful if 
>> you want to get additional information out of the error (e.g. it's useful 
>> for use with `os.PathError`). By definition, it's pointless to use it with 
>> a sentinel error.
>>  
>>
>>> So to "break" the assignability- would that mean that I'd need to define 
>>> sentinel errors as e.g. struct types?
>>>
>>> Seem's I'm still lacking the level of understanding for go errors that 
>>> I'd aspire to :/
>>>
>>> Cheers,
>>> Andi
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "golang-nuts" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to golang-nuts...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/golang-nuts/4d8969b4-dd5a-4834-893b-3e01174570bfn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/e97882af-4c3f-4a0b-ab54-277cc53ae1b0n%40googlegroups.com.