This kind of error handling does express error state (either via HTTP 500 or by the top-level "errors" key), but it doesn’t take advantage of GraphQL’s type system and can only express one error at a time.

It works, but a stronger solution is to treat errors as data.

In mutations, when errors happen, the other fields may return nil. So, if those other fields have null: false, but they return nil, the GraphQL will panic and remove the whole mutation from the response, including the errors!

Then, client apps can show the error messages to end users, so they might correct the right fields in a form, for example.

In general, top-level errors should only be used for exceptional circumstances when a developer should be made aware that the system had some kind of problem. For example, the GraphQL specification says that when a non-null field returns nil, an error should be added to the "errors" key. This kind of error is not recoverable by the client. Instead, something on the server should be fixed to handle this case. When you want to notify a client some kind of recoverable issue, consider making error messages part of the schema, for example, as in mutation errors.

We’ve enabled deprecation warnings by default when running specs. Making these warnings more visible to developers helps upgrading to newer Ruby versions.

wanted to surface to the user during SSR if the client-side call would likely fail due to cross-origin fetching, credentials, etc.

If you are working on a codebase within which you lint non-TypeScript code (i.e. .js/.jsx), you should ensure that you should use ESLint overrides to only enable the rule on .ts/.tsx files. If you don't, then you will get unfixable lint errors reported within .js/.jsx files.

I would argue though that crashing is better than quietly providing unexpected behavior.

I should note that the issue with deletions being skipped has been fixed (the file-has-vanished errors were changed into warnings).

Already Signed InThis session has ended because the account has been signed into from another browser window on 04/11/2021 04:30:09 PM. This happens when you sign in to your account on more than one browser screen. You can't be signed into your account on two or more browser windows at the same time. Just close your browser and sign back into your account.

IFN signalling

Since we're not passing any inputs to ListAccounts, it makes sense to use .run! instead of .run. If it failed, that would mean we probably messed up writing the interaction.

ActiveInteraction also supports merging errors. This is useful if you want to delegate validation to some other object. For example, if you have an interaction that updates a record, you might want that record to validate itself. By using the #merge! helper on errors, you can do exactly that.

ActiveInteraction provides detailed errors for easier introspection and testing of errors. Detailed errors improve on regular errors by adding a symbol that represents the type of error that has occurred.

Inside #execute, we merge errors. This is a convenient way to move errors from one object to another.

WE ARE CURRENTLY WORKING ON A UNIFIED API FOR ERRORS (FOR DRY AND REFORM).

As a workaround, I guess I'll have to disable my strict CSP in development, but I'd prefer to keep it strict in development as well so that I ran into any CSP issues sooner...

certainly I wouldn't want it to start telling me that I'm not catching these!

I have a Post object that has_one :schedule with accepts_nested_attributes_for :schedule as well. The latter method sets autosave: true, which unfortunately has the effect of hoisting up errors into the parent object so that the errors object on Post looks like this: (byebug) post.errors.details {:"schedule.publish_at"=>[{:error=>:blank}]}

There is no worse way to screw up data than to let a single human type it in.

You should default to the most permissive option imo and there really is no reason to check anything until you really need to If it were left to me I'd just use optional chaining, as it also eliminates the need for no-ops

Get told in big red letters when the dependency changed and you need to check that your fix is still valid.

You can determine which openssl.cnf is being used by adding a spurious XXX to the file and see if openssl chokes.

Certs have been working well with docker cli to remote docker server.

To be clear: this setup works great with just docker daemon, but something about -compose is amiss.

Using the docker client I have good success accessing the remote docker server. We call the remote server up to a hundred thousand times a day with good success. Attempting to use docker-compose, installed either via curl OR pip install --upgrade with python 2.7, we get an SSL error:

docker --tlsverify ps executes just fine, while docker-compose --tlsverify up -d --force-recreate gives me an error: SSL error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed

I only have one set of certs. And I can't see how they can be different because docker commands work using the endpoint. It's just the docker-compose command that fails

you'll run into the error you've run into if your remote Docker host has a certificate signed by something other than the ca.pem that you've got at that location.

This is for a time picker. If you're picking times for today, you may pick a time that is 15 minutes from now. It's valid now because it's currently in the future. If you don't touch the form for the next 20 minutes then click submit, the submission should be prevented because your selected time is now 5 minutes in the past.

`Module ${a.id} may be unable to evaluate without ${b.id}, but is included first due to a cyclical dependency. Consider swapping the import statements in ${parent} to ensure correct ordering`

However, IMO, having the conditional in the detach function is necessary, because there are other manifestations of this error. For example, if the DOM element in a component is removed from software outside of svelte, detach will have the same error.

IMO, the conditional needs to be added to detach to fix all manifestations of this error.

Since this issue seems to pop up periodically, it would be useful to turn this into a warning. It may not be elegant, but it prevents surprise blank screens due to a navigation error.

It is showed as an error, but it is a warning as it doesn't break anything. I hate having warning/error in my console not coming from me. It is not justified as it's not bad practice imho

The node-resolve plugin doesn't like failing to resolve module IDs (because it usually indicates a bug, like you forgot to install the package in question), so it will throw an error rather than letting Rollup print a warning.

using modulesOnly behaves exactly as expected when it warns you that the listed npm libraries do not use the ES6 format and are in fact ignored. This option is meant as a way to determine if you still have commonjs libraries in your dependencies that require special treatment via rollup-plugin-commonjs. Your code will probably not work since the listed dependencies will be missing. You should remove modulesOnly and instead add rollup-plugin-commonjs.

You oftentimes see packages list react as a peer dependency. Since this prevents react from being installed into that package's node_modules, this is another way of preventing Rollup from bundling the module. This is also nice _if_ you want the application to install react from npm, because if an application forgets to install a peer dependency, npm will issue a warning.

When the message say function was called outside component initialization first will look at my code and last at my configuration.

i feel it should get a runtime warning / error, if it returns something besides function or undefined.

type: "javascript/auto

First, what would it look like for a social media platform to re-establish perspective?

Browsing Twitter the other day, I once again found myself sucked into a far-off event that truly does not matter, and it occurred to me that social media is an orthographic camera.

A category mistake, or category error, or categorical mistake, or mistake of category, is a semantic or ontological error in which things belonging to a particular category are presented as if they belong to a different category,[1] or, alternatively, a property is ascribed to a thing that could not possibly have that property.

In discussing the appeal of the News Feed in that same interview with Kirkpatrick, Zuckerberg observed, “A squirrel dying in front of your house may be more relevant to your interests right now than people dying in Africa.” The statement is grotesque not because it’s false — it’s completely true — but because it’s a category error. It yokes together in an obscene comparison two events of radically different scale and import. And yet, in his tone-deaf way, Zuckerberg managed to express the reality of content collapse. When it comes to information, social media renders category errors obsolete.

Note that the usec for the time passed will be set to 0 to prevent rounding errors with external services, like MySQL (which will round instead of floor, leading to off-by-one-second errors).

TypeScript will see that the a property of A & B is incompatible with that of C: Type 'A & B' is not assignable to type 'C'. Types of property 'a' are incompatible. Type 'number' is not assignable to type 'boolean | undefined'.

P can't be assigned {}, since the Generic Type P can be a more defined (or restricted) type.

The value 10 is assignable to the constraint of T, but it is not assignable to this particular instantiation of T. If there was no error I would passing 10 where 3 is expected!

tes

weeks

In looking at the meaning of the term “suburbia,” the definitions

has argued journalism is

Bois’

sudo apt-get install libxml2-dev libxslt-dev python-dev lib32z1-dev

Shakespeare followed in 1594, in The Comedy of Errors: “There’s not a man I meet but doth salute me/As if I were their well-acquainted friend”

1. Install the TidalCycles pattern engine