There are several issues here.
1. If you use fmt.Println to display a time.Time it will generate a
human readable output but this does _not_ accurately reflect all
technical internal details of a time.Time. It is often a bad idea to
simply dump stuff with fmt.Println.
2. time.Parse and timezones
Thank you for answering me. That makes sense.
The reason why I noticed that was because I have a test and wanted to
ensure that the time is properly parsed. But I can't construct the expected
value.
Imagine this test:
func TestTemp(t *testing.T) {
toTest := "20190211T103847+"
parsed,
what does it means "heavy load"? if not in "heavy load", it can work ? On
the other hand, do you want the tcp connections or the http req numbers?
>From the go package, it appears that getting the basic tcp connections in
http.server is impossible.
在 2019年2月12日星期二
As discuss above, i think the answer is decoupling the P and logger,
storing the logs when the logger is down.The push and pull pattern would be
better.The p sends all logs and the logger pulls all logs.Just keep a
bigger storage for un-consumed logs.Queue may be is a better way but using
a
> Does anyone know a way of getting current open connections?
You might consider using https://golang.org/pkg/net/http/#Server.ConnState
for this instead of a middleware for the http.Handler. The different
connection states are documented on
https://golang.org/pkg/net/http/#ConnState and the
On Sat, Dec 22, 2018 at 2:15 AM Dan Kortschak wrote:
> And yes. The curl option is -d, not -F, so
>
> curl -X POST -d "path=${IMPORTPATH}" https://godoc.org/-/refresh
>
> works and could easily be made into a post-push hook to be run in the
> root of the package like so:
>
> for pkg in $(go list
Thanks for setting this up!
On Tue, Feb 12, 2019 at 4:33 PM Daniel Theophanes
wrote:
> In order to help keep database/sql driver developers and the maintainers
> of database/sql on the same page, I'm going to start to posting issues and
> proposals to the following group:
>
>
I would love to be able to include your logo as part of our inventory
(sticker site) but aren’t sure of the restrictions regarding its use for
commercial purposes, so we would like to find out what your policy is
regarding this and if this would be a possibility?
We do not plan to modify or
14 Şub 2019 Per 01:58 tarihinde Michael Jones
şunu yazdı:
> Serhat,
>
> Some more ideas for you to consider: the expected number of collisions for
> an ideal random hash, the option of "folding in" the high bits of the hash
> rather than truncating, and finer control of operation.
>
>
Serhat,
Some more ideas for you to consider: the expected number of collisions for
an ideal random hash, the option of "folding in" the high bits of the hash
rather than truncating, and finer control of operation.
https://play.golang.org/p/92ERC4PJKAL
On Wed, Feb 13, 2019 at 12:20 PM Serhat
I have heard that the vendir dirctory is here to stay and also that it is
going away - can someone from the goteam give us a idea of the future of
that feature?
Thanks
p4tin
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from
On Wed, Feb 13, 2019 at 3:15 PM wrote:
>
> I would love to be able to include your logo as part of our inventory
> (sticker site) but aren’t sure of the restrictions regarding its use for
> commercial purposes, so we would like to find out what your policy is
> regarding this and if this would
That means that must give credit to author (Renee French)
AND
you must give credit to license itself
All CC licenses require users to attribute the creator of licensed
material, unless the creator has waived that requirement
On Tuesday, February 12, 2019 at 9:51:17 PM UTC+3, Michael Jones wrote:
>
> Serhat, some ideas for you...
> https://play.golang.org/p/7QPy5wa-9eO
>
Interestingly I found out input iteration order does matter :) 15,33 shift
version yields an amazing number of collisions (7_910_886_368 collisions
hi,
in recent days i have been working on fixing some issues with above
presented code
(https://github.com/clementauger/st/blob/master/examples/walkfiles/main.go#L38)
besides the fact the internal code uses a lot of reflection mechanisms to
implement the api, putting in de facto on the wrong
15 matches
Mail list logo