"Flag provided but not defined" doesn't give enough details for end users who aren't specifically aware of how CLIs work. I get a lot of bug reports that are "I got this obscure error message, and I'm not sure what to do".

See also

• urfave/cli#663
• urfave/cli#744

APIs working with offsets, like CommitOffsets , StoreOffsets, does not specify what offset means. I recently found out offset means next offset to consume, not last offset just processed.

I think it's a common trap that many users fall into, some examples are:

• confluentinc/confluent-kafka-go#286
• confluentinc/confluent-kafka-go#195

The link to Django version compatibility 1.7 in the README's Development status section is broken, it looks like this version is not supported anymore: https://docs.djangoproject.com/en/1.7/ref/templates/builtins/

I suggest to either include a reference of actually implemented filters in your project's documentation, or ensure support for Django 1.8 or higher so you can link to their document

I know I can just go to Releases, or go get things, but I'm having a hard time finding any install instructions on pdfcpu.io.

At present we can run the load generator for a set amount of time or a certain number of requests.
I would like to a mode --reconnetRequests=1000 where fortio client will reconnect after 1000 requests.

Use case: We are testing SDS cert rotation using an https fortio client (std client).
For cert rotation to be exercised fortio should reconnect periodically to fetch the new cert.
In

DM API has changed on september, 17th : https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/guides/direct-message-migration
is there any work in progress to change anaconda soon ?

I think ghw has become sufficiently feature-rich to warrant a real docs solution other than the README.md page. I'm thinking of using Docsy for this.

See https://github.com/mailgun/gubernator/blob/master/architecture.md#side-effects-of-global-behavior

It states: Using GLOBAL can increase the amount of traffic per rate limit request if the cluster is large enough

I assume that with 'the cluster' you mean the cluster of gubernator instances.

Can you give a more detailed indication what you mean with '_large'? Are we talking about te

A potentially useful feature for the included CLI (and library) could be converting DICOMs (frames + metadata) into neat tf.Example protocol buffers for downstream use in Tensorflow.

This operations will be used to drop elements in the steam on the right of the given element

var elements = []int{10,12,7,41,5,6}
res:=koazee.StreamOf(elements).DropRight(12).Out().Val()
fmt.Println(res)

// [10,12]

I'm hoping to work on forgefed integration in gitea, or a standalone go forge.

As there is a lot of prior work done here already it only makes sense to improve the overall community by contributing to this and related work under go-fed.

I'm not really sure where to start at the moment so just wanted to drop in here and see if there is something you would recommend to start with or somewhere