200 Matching Annotations
  1. Last 7 days
    1. This error indicated the failure of connection to the server. You can fix it by launching the Terminal App on your Mac and navigate to the Spotlight Search Glass option. Type' defaults delete com.microsoft.Outlook' in the search box. You can now erase the previous outlook preferences by using this command. To fix Outlook Error 3253, type' lillallcfprefsd' in the box to clear the cached preferences. Finally, start Outlook and check whether the problem is resolved. Related issues: Outlook not Working

    1. This line is incorrect. Multiplication does distribute over substraction as well eg: \(7 \times (3-4) ?= (7 \times 3) - (7 \times 4)\) $$ 7 \times (-1) ?= 21 - 28 $$ $$ -7 eq -7 $$

  2. Mar 2021
    1. often in error
    2. In logic, it is the practice of treating two distinct concepts as if they were one, which produces errors or misunderstandings as a fusion of distinct subjects tends to obscure analysis of relationships which are emphasized by contrasts
    1. ReconfigBehSci. (2020, November 18). @danielmabuse yes, we all make mistakes, but a responsible actor also factors the kinds of mistakes she is prone to making into decisions on what actions to take: I’m not that great with my hands, so I never contemplated being a neuro-surgeon. Not everyone should be a public voice on COVID [Tweet]. @SciBeh. https://twitter.com/SciBeh/status/1329002783094296577

    1. Sentry supports un-minifying JavaScript via Source Maps. This lets you view source code context obtained from stack traces in their original untransformed form, which is particularly useful for debugging minified code (e.g. UglifyJS), or transpiled code from a higher-level language (e.g. TypeScript, ES6).
    1. Scientists at the U.K.’s National Oceanography Centre have somewhat counterintuitively linked the cold blob in the North Atlantic with summer heat waves in Europe. In 2015 and 2018, the jet stream, a river of wind that moves from west to east over temperate latitudes in the northern hemisphere, made an unusual detour to the south around the cold blob. The wrinkle in atmospheric flow brought hotter-than-usual air into Europe, they contend, breaking temperature records.

      Here, the decadal-scale warming hole that is possibly linked to AMOC slowdown has been conflated with the shorter-term cold anomaly that featured record low North Atlantic sea surface temperatures in 2015.

      The authors of the NOC study are careful to make this distinction in their article:

      It is important to distinguish between this long-term warming hole and the short-term 2015 cold anomaly that is the focus of our study.

      The long-term warming hole that is the focus of this New York Times article is not the same thing as the short-term 2015 cold anomaly. The two phenomena have very different timescales and different causes. Current understanding suggests that the short-term 2015 cold anomaly was caused by successive winters with extreme heat loss, i.e. it was largely driven by changes in air-sea heat exchange. The longer-term warming hole may have been caused by the AMOC slowdown, as discussed in this article.

      For more information on the 2015 cold anomaly and its causes, see this review article led by Simon Josey.

  3. Feb 2021
    1. Gmail error 007 occurs when you try to send an email but Gmail get stuck while sending the message and Error 007 is displayed. How to fix Gmail Server error 007? First, check your browser for any new updates – update if available. Second, enable all disabled extensions on your browser. Third, clear all cookies, cache memory, registry, and prefetch files. If this solution does not work, wait till Gmail resolves the issue itself.

    1. the ability to “error out” when something goes wrong
    2. The “error path” or “failure track” is the lower path going the the failure terminus.
    3. If anything here did fail in “validate omniauth”, all other steps in the chain would be skipped as the flow would follow the path leading to the failure terminus.
    4. Things could go wrong in two places here. First, the validation could fail if Github sends us data we don’t understand. Second, we might not know the user signing in, meaning the “find user” logic has to error-out
    1. Return None. That’s evil too! You either will end up with if something is not None: on almost every line and global pollution of your logic by type-checking conditionals, or will suffer from TypeError every day. Not a pleasant choice.
    2. we also wrap them in Failure to solve the second problem: spotting potential exceptions is hard
    3. exceptions are not exceptional, they represent expectable problems
    4. So, the sad conclusion is: all problems must be resolved individually depending on a specific usage context. There’s no silver bullet to resolve all ZeroDivisionErrors once and for all. And again, I am not even covering complex IO flows with retry policies and expotential timeouts.
    1. Maybe T can be understood as a "wrapping" type, wrapping the type T into a new type with built-in exception handling
    2. Undefined values or operations are one particular problem that robust software should prepare for and handle gracefully.
    1. Other filters will ignore blocks when given to them.

      Would be better to raise an error if block isn't allowed/expected!

    2. Note that it's perfectly fine to add errors during execution. Not all errors have to come from type checking or validation.
    3. Inside the interaction, we could use #find instead of #find_by_id. That way we wouldn't need the #find_account! helper method in the controller because the error would bubble all the way up. However, you should try to avoid raising errors from interactions. If you do, you'll have to deal with raised exceptions as well as the validity of the outcome.

      What they're referring to:

      Account.find('invalid') will raise an error but Account.find_by(id: 'invalid') will not.

    1. You may face many issues while using Gmail. One of the main issues that you may encounter is Gmail Temporary Error 500. This error is caused by any technical issue in the application itself or some configuration issue in the Gmail server. You need to clear all the cookies and cache files from storage or disable the antivirus and firewall to fix this issue.

  4. Jan 2021
  5. Dec 2020
    1. Turmeric Spice, Ground

      They are 10 times off based on several samples from this study. Turmeric only has 10 to 15 thousand ORAC, not 127 thousand. This error is likely either a typo or they are citing the value of curcumin rather than turmeric.

      See here for google sheet version of study cited above.

      EDIT: I checked their source. They appear to have represented the source accurately. Why, then, the ten fold difference?

    1. the best way to ensure you've handled all errors in your run() function is to use run().catch(). In other words, handle errors when calling the function as opposed to handling each individual error.
    2. // The `.then(v => [null, v], err => [err, null])` pattern // lets you use array destructuring to get both the error and // the result
  6. Nov 2020
    1. At the extreme ends of the concentration range (for example, fewer than ten copies of target in a well or more than 120,000 copies of target in a well), fewer droplets in a well will lead to slightly larger error bars.
  7. Oct 2020
    1. Issue grooming: There appears to be a variety of different failure modes and user error/misconfiguration scenarios (all largely historic) described here.
    1. (One can already destructure the loop variable but using a store obtained that way currently throws an error - Stores must be declared at the top level of the component (this may change in a future version of Svelte))
    1. so both will confess and end up serving sentences of five years

      Where did the 5 years come from? Two sentences back it said "If each confesses and implicates the other, both will be sentenced to three years." Not surprising that people find it hard to get their head around this stuff.

  8. Sep 2020
    1. DX: start sapper project; configure eslint; eslint say that svelt should be dep; update package.json; build fails with crypt error; try to figure what the hell; google it; come here (if you have luck); revert package.json; add ignore error to eslint; Maybe we should offer better solution for this.
    2. When the message say function was called outside component initialization first will look at my code and last at my configuration.
    3. We could at least try to offer better error message for this, before it becomes our next NullPointerException, Segmentation Fault or Kernel Panic
    4. It looks like the issue stems from having "svelte" as a dependency instead of a devDependencies in package.json within the sapper project. This causes import 'svelte' to load the rollup excluded npm package's set_current_component instead of from within the sapper generated server.js.
  9. Aug 2020
  10. Jul 2020
    1. JSON parsing is always pain in ass. If the input is not as expected it throws an error and crashes what you are doing. You can use the following tiny function to safely parse your input. It always turns an object even if the input is not valid or is already an object which is better for most cases.

      It would be nicer if the parse method provided an option to do it safely and always fall back to returning an object instead of raising exception if it couldn't parse the input.

    1. An estimate of par-titioning error can be found based on the analysis of Dube et al.,39 which models the partitioning as a binomial process.
    2. Digital assays have two sources of error: subsampling error and partitioning error
    3. Subsampling error sets the lower detection limit at low concentrations and is independent of the instrument, while partitioning error domi-nates at high concentrations and may depend on the sampling and partitioning instrument
  11. Jun 2020
    1. Saltelli, A., Bammer, G., Bruno, I., Charters, E., Di Fiore, M., Didier, E., Nelson Espeland, W., Kay, J., Lo Piano, S., Mayo, D., Pielke Jr, R., Portaluri, T., Porter, T. M., Puy, A., Rafols, I., Ravetz, J. R., Reinert, E., Sarewitz, D., Stark, P. B., … Vineis, P. (2020). Five ways to ensure that models serve society: A manifesto. Nature, 582(7813), 482–484. https://doi.org/10.1038/d41586-020-01812-9

  12. May 2020
  13. developer.mozilla.org developer.mozilla.org
    1. in the absence of an immediate need, it is simpler to leave out error handling until a final .catch() statement.
    2. Handling a rejected promise too early has consequences further down the promise chain.   Sometimes there is no choice, because an error must be handled immediately.
  14. Apr 2020
    1. The translated model name, translated attribute name, and value are always available for interpolation as model, attribute and value respectively.
  15. Mar 2020
    1. To be just a bit polemic, your first instinct was not to do that. And you probably wouldn't think of that in your unit tests either (the holy grail of dynamic langs). So someday it would blow up at runtime, and THEN you'd add that safeguard.
    2. I want to raise errors with more context
    3. As many would guess: ... catch StandardError => e raise $! ... raises the same error referenced by $!, the same as simply calling: ... catch StandardError => e raise ... but probably not for the reasons one might think. In this case, the call to raise is NOT just raising the object in $!...it raises the result of $!.exception(nil), which in this case happens to be $!.
    1. It is recommended that a library should have one subclass of StandardError or RuntimeError and have specific exception types inherit from it. This allows the user to rescue a generic exception type to catch all exceptions the library may raise even if future versions of the library add new exception subclasses.
    1. The pattern below has become exceptionally useful for me (pun intended). It's clean, can be easily modularized, and the errors are expressive. Within my class I define new errors that inherit from StandardError, and I raise them with messages (for example, the object associated with the error).
  16. Feb 2020
    1. In this simulation complete random assignment led to a -0.59% decrease in sampling variability. This decrease was obtained with a small design tweak that costs the researcher essentially nothing.

      This is not visible in the html. You specified too few digits.

      Also, the results would be more striking if you had a smaller data set.

    1. docker-compose up -d

      Error for me here...

      ➜ hello-world docker-compose up -d zsh: command not found: docker-compose

  17. Jan 2020
    1. стремление

      0:3.24 (NY) Ошибка перевода, в английском не "intention" (стремление), а "intension" (напряжение или суть). Отличие в одну букву, а какая большая разница в смысле...

    2. , уровнях

      0:3.22 (NY) ошибка перевода, запятая, пробел и второе слово "уровнях" не нужно. (в UF переводе правильно)

  18. Dec 2019