Re: [go-nuts] Re: Auto-renew letsencrypt cert with standard library code

Hi Mike, > >> Given how complex your file is, let me suggest you a simpler alternative: >> ... >> >> > Thanks, Marko, but I'm not sure that's simpler. My unit file has exactly > one line devoted to cert renewal. > > ExecStartPre=+/usr/bin/certbot renew > After a second look on a wider screen, I

Re: [go-nuts] Re: Auto-renew letsencrypt cert with standard library code

Hi Michael, > So I ended up biting the bullet and learning how to use systemd. The unit > file I ended up with is below. > Given how complex your file is, let me suggest you a simpler alternative: use either caddy or revproxyry as a reverse proxy. You start two processes, the reverse proxy and

Re: [go-nuts] Auto-renew letsencrypt cert with standard library code

Hi, FWIW, The Caddy web server is written in Go and handles this scenario. So > you might consider using it or at least looking at its source to understand > how to implement this feature. > We implemented an alternative in case you need more examples: https://github.com/Parquery/revproxyry Chee

Re: [go-nuts] Include tests in binary and run them

Hi Farid, If I understood your question correctly, you can play with build flags. Alternatively, you can add a "-diagnostics" flag. Consider also design-by-contract with contracts tested at run time (e.g., we use our own implementation https://github.com/Parquery/gocontracts; see also other imple

Re: [go-nuts] go in cloud server

Hi Shyaka, > >1. is it a good idea to deploy go in cloud server if go is compiled to >machine binaries, what can happen if the cloud provider changes the >physical server to different processor architecture. > > I don't think this could ever be a problem. You normally choose the archit

Re: [go-nuts] [ANN] PipeHub: A programmable proxy server

Hi Diego, Thanks for sharing, looks very interesting! Please keep us posted and let us know when it's production-ready. We also implemented a simple reverse proxy at the company since we wanted it to be easy to automatically set up and configure. This helped us to add a simple reverse proxy to mic

Re: [go-nuts] Deferring a close that can fail

Hi Dave, Separate logic makes sure I have passed the point at which the data is > committed before I commit my reading of input, so eventually the data will > be reread and rewritten. > I don't understand fully what you mean here. Maybe you could write a snippet of pseudo-code to illustrate the s

[go-nuts] Re: [ANN] gocontracts 1.3.0 released

P.S. Here's the link that I forgot to include in the previous email: https://github.com/Parquery/gocontracts On Sat, 26 Jan 2019 at 08:56, Marko Ristin-Kaufmann wrote: > Hi, > We have just released gocontracts 1.3.0. > > Gocontracts now support arbitrary function preamb

[go-nuts] [ANN] gocontracts 1.3.0 released

Hi, We have just released gocontracts 1.3.0. Gocontracts now support arbitrary function preambles and condition initialization. Function preambles are especially important if you model state transitions: // increaseFirst increases the first element of the array. increaseFirst requires:// *

Re: [go-nuts] GitHub go-formal ownership

(Pardon, please ignore the previous message, it should have been private.) Le mer. 23 janv. 2019 à 13:58, Marko Ristin-Kaufmann a écrit : > Hi Scott, > Could you describe a bit in more detail what needs to be done and how > often? Are there any knowledge requirements? > > I

Re: [go-nuts] GitHub go-formal ownership

Hi Scott, Could you describe a bit in more detail what needs to be done and how often? Are there any knowledge requirements? I already develop github.com/Parquery/gocontracts and I am quite interested in the topic so I might be a potential candidate. Cheers Marko Le mer. 23 janv. 2019 à 10:20, S

Re: [go-nuts] Koazee vs Go-Linq vs Go-Funk

Thanks, Ivan! These numbers are very helpful! Could you at least give us a hint why your library is faster than the other two? As far as I can see, all three libraries in the benchmark use reflection. On Tue, 4 Dec 2018 at 08:49, Iván Corrales Solera < ivan.corrales.sol...@gmail.com> wrote: > Hey

Re: [go-nuts] [ANN] Koazee a library inspired by functional programming and lazy evaluation that takes the hassle out of working with arrays

my tests! > > Benchmark report can be found here: > https://github.com/wesovilabs/koazee/wiki/Benchmark-Report > > > > > > > > > On Monday, November 12, 2018 at 8:59:20 AM UTC+1, Marko Ristin wrote: >> >> Hi Ivan, >> Any performance comparisons

Re: [go-nuts] contracts thought experiment: dimension checks

, Marko Ristin-Kaufmann a écrit : > What is the zero value of a >> non-optional pointer? (If I were doing a clean-slate Go, I'd probably >> leave zero-values out, but I'm not). >> > > I haven't really spent much thought about it. I suppose that would also

Re: [go-nuts] contracts thought experiment: dimension checks

> > What is the zero value of a > non-optional pointer? (If I were doing a clean-slate Go, I'd probably > leave zero-values out, but I'm not). > I haven't really spent much thought about it. I suppose that would also fall in the realm of static or run-time checks of behavioral contracts. > -- Y

Re: [go-nuts] contracts thought experiment: dimension checks

Hi Ian, I'm actually not in favor of dependent types -- this might have come wrong "over the line". I find them limiting and confusing in practice (but I have limited experience, mostly in C++ if you could call template hacks really dependent types...). I expect most applications to need wider fam

Re: [go-nuts] contracts thought experiment: dimension checks

@Dan: P.S. Sorry, I probably should have addressed the email to Tamas Gulacsi. On Tue, 27 Nov 2018 at 10:41, Dan Kortschak > wrote: > >> Yes, this was raised as a possibility by Ian. But this negates a very >> valuable aspect of matrices that I completely failed to consider in >> writing the qu

Re: [go-nuts] contracts thought experiment: dimension checks

Hi Dan, What you are referring to is called *behavioral types* (see, *e.g., * https://www2.ccs.neu.edu/racket/pubs/fse01-flf.pdf). If you want to go that route, you need (usually arbitrarily complex) behavioral contracts (not to be mistaken with the term type contracts used here) and static checks

Re: [go-nuts] go language sensitive editor?

We use GoLand at our company. I used vim with plugins, but Goland is far superior when it comes to refactoring. Le mar. 20 nov. 2018 à 21:52, Pat Farrell a écrit : > I know, this is both a FAQ and an unanswerable question. I'm an old > programmer who has used nearly every editor known to man. I

Re: [go-nuts] [ANN] Koazee a library inspired by functional programming and lazy evaluation that takes the hassle out of working with arrays

tb/go-linq > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fahmetb%2Fgo-linq&sa=D&sntz=1&usg=AFQjCNHG4JEY4oprhvHToz-Man5NHQuwdQ> > for example this one > > https://github.com/wesovilabs/koazee/issues/2 > > In fact any new issues or suggestion will be

Re: [go-nuts] [ANN] Koazee a library inspired by functional programming and lazy evaluation that takes the hassle out of working with arrays

Hi! Could you give a comparison to other similar libraries such as https://github.com/clementauger/st https://github.com/ahmetb/go-linq ? Cheers Marko -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiv

Re: [go-nuts] database for protobuf - profanedb or similar

Hi Robert, I'm just curious: why did you develop yet another key/value store? Cheers Marko -- 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..

Re: [go-nuts] database for protobuf - profanedb or similar

We are using LMDB with string or numerical keys and protobufs as values. Be careful with the encoding of numerical keys, though: complement of two is not in lexicographical order. We are almost done with open-sourcing a python/go library: https://github.com/Parquery/pynumenc (see the pull reques

Re: [go-nuts] Re: Regarding contracts

Hi Hay, There's already a tool for formal contracts in Go: https://github.com/Parquery/gocontracts Cheers Marko Le dim. 28 oct. 2018 à 00:19, hay a écrit : > Hello, > > Code contracts are needed for safety critical applications but they would > help other applications too. I hope code contracts

Re: [go-nuts] microservices framework

Hi Vasiliy, We use our own swagger-to code generator for external communication and zeromq & protobufs for internal components. We foung the code generated by go-swagger to be a bit too complex. Swagger-to: https://github.com/Parquery/swagger-to Cheers Marko Le mar. 23 oct. 2018 à 19:02, Vasili

Re: [go-nuts] A utility package to aid in writing end-to-end tests for Go servers

Hi Agis, Thanks for sharing the package! A couple of more general thoughts re testing: * We (at Parquery) define our server/clients in Swagger spec and then use swagger-to to generate the code (https://github.com/Parquery/swagger-to). Having client and server code automatically generated made test

Re: [go-nuts] Re: Implementing Design by Contract (DbC) paradigm in Go?

Hi, I'd like to point you to a go tool that implements contracts (pre and postconditions) as part of documentation. The tool translates the contracts into code by adding it to the function body. It can also automatically remove the checks once you don't need them any more (e.g. in production).

[go-nuts] gocontracts with type invariants

Hi, We implemented a tool to allow design-by-contract in Go by automatically generating pre and postcondition checks in code: https://github.com/Parquery/gocontracts. However, the most interesting part of the design-by-contract, namely invariants, is still missing and I'd like to hear your fee

[go-nuts] gocontracts: tool for design-by-contract

Hi, We've implemented a small tool to facilitate design-by-contract by generating code from the conditions described in the function descriptions. While others have implemented Go libraries (e.g., [1]), we wanted something that gives us readable code with no extra dependencies. Moreover, we fou