Conduitry

Results 38 issues of Conduitry

**Describe the bug** Hydra Admin endpoints do not appear to be aware of when a login request has already expired. Depending on OpenID client configuration, this will result in an...

### Describe the bug Throwing an exception (or returning a rejecting promise) from a `load` function should be equivalent to returning `{ status: 500, error }` (apart from the former...

bug
error handling
p1-important

### Describe the problem Currently, the Node adapter will not bundle any external server side dependencies. This means that you need to make all of the dependencies you might need...

enhancement
pkg:adapter-node
p1-important

### Describe the problem The handling of error responses from page endpoints is currently a bit confusing and unflexible. If a GET page endpoint returns a 4xx or 5xx response,...

enhancement

- Temporary Containers Version: 1.9.2 - Firefox Version: 101.0.1 ### Actual behavior When enabling Multi-Account Containers integration and also enabling "Automatically create Deletes History Temporary Containers", links from one of...

bug

Closes #10163. No test yet because I want to first get some feedback on whether this seems like the correct approach. I _think_ `state.depth > 0` will tell us what...

### Describe the problem There is not currently a good way to know whether a given `event` corresponds to a real request coming in to the server, or a synthetic...

enhancement
p2-nice-to-have

The LICENSE and package.json files were updated, which are (probably?) the more legally binding ones, but the reference in the readme was not.

I have an object I'd like to run through Decoders, and I'd like to log the errors that it throws when there are validation issues - but there's one field...

With the introduction of the `page` store in Svelte v3 Sapper, the `segment` prop passed to `_layout.svelte` components feels somewhat vestigial. I don't think there's anything that can be done...

proposal
breaking