IEP Process: Common Errors

This episode's transcript was produced by an AI. If you notice any errors, please get in touch.

Arber also suggests to Murray in this letter that he should use atypewriter. ‘I am quite certain’, he wrote, ‘that the only way to keep down thecost of corrections is to type-write the copy’, suggesting a model called theIdeal Caligraph, no. 2 price £18. Murray did read The Snake Dance of theMoquis of Arizona but he did not buy a typewriter.

two small flaws in the Dictionary’s compilation process

Accuracy of the slide rule. From thediscussion of § 2 it appears that we read fourfigures of a result on one part of the scaleand three figures on the remaining part.Assuming that the error of a reading is onetenth of the smallest interval following theleft-hand index of D, we conclude that theerror is roughly 1 in 1000 or one tenth of oneper cent. The effect of the assumed errorin judging a distance is inversely propor-tional to the length of the rule. Hencewe associate with a 10-inch slide rule anerror of one tenth of one per cent, with a20-inch slide rule an error of one twentiethof one per cent or 1 part in 2000, and withthe Thacher Cylindrical slide rule an errorof a hundredth of one per cent or one part.in 10,000. The accuracy obtainable withthe 10-inch slide rule is sufficient for manypractical purposes; in any ease the sliderule result serves as a check.

There are common errors experienced by beginners when getting started with asyncio in Python.

next stage is parsing (also known as syntactic analysis) and the parser reports the first error in the source code. Parsing the whole file happens before running the first line of code which means that Python does not even see the error on line 1 and reports the syntax error on line 2.

I haven’t done a deep dive into the source code of the CPython interpreter to verify this, but I think the reason that this is the first error detected is because one of the first steps that Python 3.12 does is scanning (also known as lexical analysis). The scanner converts the ENTIRE file into a series of tokens before continuing to the next stage. A missing quotation mark at the end of a string literal is an error that is detected by the scanner—the scanner wants to turn the ENTIRE string into one big token, but it can’t do that until it finds the closing quotation mark. The scanner runs first, before anything else in Python 3.12, hence why this is the first error message.

Python reports only one error message at a time—so the game is which error message will be reported first?

The fact that error messages are generated by different stages of the compiler, and compilers generally issue errors from earlier stages before continuing also means that you can discover the stages of your compiler by deliberately creating errors in a program.

Why do Direct Leaders decentralize when they issue a token? Decentralization imposes costs on an organization — decisions are made more slowly by lower context people who are not held accountable for bad decisions — this is why companies don’t operate this way. These costs are being felt across the industry. Kevin Owocki, who left as Direct Leader of Gitcoin to later return, described a broader trend of “founders boomeranging” back into leadership to solve the organizational dysfunction caused by decentralization. As the impetus for governance changes, Rune Christensen wrote of MakerDAO in 2022, “The governance processes and political dynamics… fundamentally aren’t compatible with the reality of effectively processing complicated real-world financial deals.”

TheCalculagraph

Note though, that this only works when you're already using git for your dependency

Transcriptions taken from Goitein’s publications were corrected according to handwrittennotes on his private offprints. The nature of Goitein’s “typed texts” is as follows. Goitein tran-scribed Geniza documents by hand from the originals or from photostats. These handwrittentranscriptions were later typed by an assistant and usually corrected by Goitein. When Goiteindied in 1985, the transcriptions were photocopied in Princeton before the originals were sentto the National Library of Israel, where they can be consulted today. During the followingdecades, the contents of most of these photocopies were entered into a computer, and period-ically the files had to be converted to newer digital formats. The outcome of these repeatedprocesses of copying and conversion is that transcription errors and format glitches are to beexpected. As the Princeton Geniza Project website states: “Goitein considered his typed texts‘drafts’ and always restudied the manuscripts and made revisions to his transcriptions beforepublishing them.” See also Goitein, “Involvement in Geniza Research,” 143. It is important tokeep in mind that only the transcriptions that were typed were uploaded to the project website.Therefore, e.g., Goitein’s transcriptions of documents in Arabic scripts are usually not foundthere. The National Library of Israel and the Princeton Geniza Lab also hold many of Goitein’sdraft English translations of Geniza documents, many of which were intended for his plannedanthology of Geniza texts in translation, Mediterranean People.

This was originally disallowed because #5907 was opened asking for different behavior in this situation that we didn't want to allow, and so we decided to make it a compiler error rather than have confusing behavior in that situation.

The console needs to be readable in development and to provide the best DX I have to design my libraries in ways that prevent these warnings. This results in design decisions that are detrimental to functionality and/or code readability/simplicity.

I just spent a day dismantling a model, trying to find the cause of the silent rollback - taking out every association, every validation, every callback, whittling down all the code in the transaction, only to finally discover that it was return true that was the cause of it all. Or yes, an exception!

Indeed, if MoneySerializer was reloadable, starting with Rails 7 such initializer would raise a NameError.

Zeitwerk raises Zeitwerk::UnsynchronizedReloadError if any of these situations are detected. This is a fatal exception that signals a fundamental bug, you cannot rescue it and expect things to work.

In her 2002 dissertation, and then in a series of articles published in medicaljournals, Pape made a case for imitating this practice. “The key to preventingmedication errors lies with adopting protocols from other safety-focusedindustries,” Pape wrote in the journal MEDSURG Nursing in 2003. “The airlineindustry, for example, has methods in place that improve pilots’ focus andprovide a milieu of safety when human life is at stake.”

the Institute of Medicine had released a landmark report on patientsafety, To Err Is Human. The report found that as many as 98,000 Americanswere dying each year as a result of preventable medical errors occurring inhospitals—more people than succumbed to car accidents, workplace injuries, orbreast cancer. And some significant portion of these deaths involved mistakes inthe dispensing of drugs.

She frequently cites authors second-hand(“as quoted by”, “see,” etc.) rather than primary texts, and in some instancesthis practice results in the kinds of errors for which earlier compilations werecriticized. The most egregious of these occurs when Blair cites Ann Moss on

This is something akin to fan fiction at an online appreciation site—the kind of site, it’s worth noting, where Fifty Shades of Grey got its start, before becoming the first book of pornography to make the bestseller list.

But Google also uses optical character recognition to produce a second version, for its search engine to use, and this double process has some quirks. In a scriptorium lit by the sun, a scribe could mistakenly transcribe a “u” as an “n,” or vice versa. Curiously, the computer makes the same mistake. If you enter qualitas—an important term in medieval philosophy—into Google Book Search, you’ll find almost two thousand appearances. But if you enter “qnalitas” you’ll be rewarded with more than five hundred references that you wouldn’t necessarily have found.

digital methodo collect

stated in section 2.2

If you forget to define x in the object you pass as the second argument, or if there's some similar bug or confusion, you won't get an error -- just unexpected results.

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