Charles

To properly understand how to use Digga in the context of the general nix/os ecosystem and properly integrate with other non-digga tooling, it would be very helpful to provide in...

tasks left pending because dependency run by other worker

5

Hi! I'm using luigi in production. The luigi version used on the worker side is `2.8.13`. The luigi version used for the central scheduler is `3.0.2`. I have some top...

Weird hover diagnostic buffer behavior

5

Hi! Thanks for this great tool! I'm using latest version(12.1.0-snapshot). I'm seeing flaky behavior with hover fifo buffers, working on python code(pyls). Diagnostics/doc info often don't manage to stay in...

### Description Django channels implements the ASGI spec. Many other frameworks also implement that spec, and any ASGI-compliant "app" can be *mounted* as part of another ASGI app(though usually framework-specific...

I'm using the graphql context to pass (potentially) shared resources, like database connections, to the schema resolvers. These resources eventually need to be cleaned up(i.e. closing connections). What's the best...

What's the appropriate way to inject values into the context on a per-request basis? That is, I can statically set context values when I add the route, but is there...

protonmail-bridge

1

### Description Hi wonderful nixers. Seeking to integrate my protonmail account. Proton provides a smtp bridge service running in the background that takes care of mail encryption/decryption. It supports IMAP....

setting 'index' option for package doesn't guarantee package will be installed from index

4

### Issue description Not sure if this is to be considered a bug, but it's unexpected behavior for me given the documentation. If I specify the 'index' option for a...

The documentation entries for `dateGranularity` in `reportDescription`, and for the field's data type( https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/reporting-api/data_types/r_reportDescriptionDateGranularity.md, https://github.com/AdobeDocs/analytics-1.4-apis/blob/master/docs/reporting-api/data_types/r_reportDescription.md) are confusing: The data type description describes each granularity value as relating to the "current"...

For the reporting api, the ReportDescription documentation doesn't specify if `DateFrom` and `DateTo` are inclusive(i.e. if data for `DateTo` is considered in the report).