Valérian Rousset
Valérian Rousset
While playing with some gcc warning flags, I ended up finding this weird code construct. `I_wacom_RequestData` accepts a last argument `char *p`, but in its body, we can see `p...
When enabling the "select" feature, it failed to build because of missing crate level imports. Found a bit more using [cargo-all-features](https://github.com/frewsxcv/cargo-all-features).
From the [CAS v2 documentation](https://apereo.github.io/cas/6.0.x/protocol/CAS-Protocol-V2-Specification.html#31-service-ticket), there is no need to validate the content of the ticket, the only relevant check is that it needs to begin with "ST-" (and "PT-"...
M4sh differs from the standard sh syntax by using `AS_IF` and `AS_CASE`, it is used to know when to initialize pkg-config for example. Here, some code are using the classic...
Followup of #39. Comment from @theckman > I think to support this, at a minimum, we would need to move the OpenFile error handling code into the platform-specific flock.go files....
Even though go 1.13 included some new features into the standard `errors` package, the trace feature available in `xerrors` is not there. For this reason all `errors.New` messages should be...
Currently, errors are signaled by logging then returning `nil`, the latter being also used to return a potential match. Either, drop the `log.Error` inside `darc.GetDarc` implementation or allow it to...
Serialisation by `protobuf.Encode` is not stable when using `map`. See https://github.com/dedis/protobuf/issues/72
Currently, `**/proto.go` are used to generate `.proto` files (using the `Makefile/proto.{awk,sh}` stack), which can (and did) induce discrepancies between message handling in each languages. Writing specifications in `.proto` and using...
Currently, many (72) classes extends Protobuf's `Message` instead of using as a data only structure. This leads to many weird work-arounds like having constructor taking an object as argument, having...