-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge_strict_job exception: Utils_js.Key_not_found #3147
Comments
i have seen this error also multiple times but usually after making changes in libdefs and especially if i had a syntax error in them previously. |
Does this happen when the Flow server starts up (when you run We did introduce a bunch of these kinds of errors in v0.37.0, as part of the recheck optimization. By 0.37.4 we've fixed a bunch of them, but are still aware of a couple. So any repros would be greatly appreciated! |
Always when I'm running Another thing that seems to normally happen at the same time is that flow complains that at least one of my It does seem to mostly occur when editing code in the files referenced by |
I have the same issue, usually happens about the third time running flow. Not always caused by This is new as of An example of some:
|
@avikchaudhuri is investigating and will get a fix into 0.38.0 |
Unfortunately this is still happening in 0.38.0 :( |
@STRML - do you have a repository that we could look at? Given a repo and Flow's logs during the exception, @avikchaudhuri has had success in the past reproducing the issue. Long story short, starting in v0.37.0, Flow tries to avoid rechecking a module if none of its dependencies have substantially changed. However if Flow is wrong about the "substantially changed" part, it can cause trouble like this. |
I can't seem to reproduce this yet. It's a very large/complicated project and I can't trade it down yet to a single file or circular dep. To give some background, we usually keep a lot of our large/complicated types in a single file so they are easy to import into other modules. Things like the shape of the data tree (React project), collections, models, action definitions, and so on. So when changing some much depended-upon modules (such as a Flux Store or one of the base classes) I see Flow actually fall back from |
I got the same exception with // Exception
function likeObject(item: any): Boolean {
return (item !== null && typeof item === 'object' && !Array.isArray(item));
}
// Ok
function likeObject(item: any): Boolean {
const notArray = !Array.isArray(item);
return notArray && item && typeof item === 'object';
} Exception message:
|
@Shok211 That appears to be related to your use of |
Thanks for the concise test case! On it.
…On Tue, Jan 31, 2017 at 6:28 AM, Samuel Reed ***@***.***> wrote:
@Shok211 <https://github.com/Shok211> That appears to be related to your
use of Boolean (rather than boolean). Fixing the type fixes the error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3147 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFFNMeT-IiSCgOfiKm1fzcGRsnfkBMZSks5rX0UPgaJpZM4LdaY_>
.
|
Summary: We use BoolT.t in various places. When these are part of errors, their locationlessness causes an assertion failure. Will follow up with a more thorough audit of the locationless Primitive type constructor `t` (also available on NumT, StrT, ...). Ref #3147 Reviewed By: samwgoldman Differential Revision: D4490639 fbshipit-source-id: 23f6531e24acf0bd7f8f36fbe9defd5876736ee4
I'm seeing this sort of thing as well, with Flow 0.39.0. Restarting the Flow server has no effect.
I don't have a minimal test case, but if you want to repro you can check out the code from here: https://github.com/CityOfBoston/311/tree/flow-internal-error LMK if there’s other info I can provide. This popped up when I was moving things around in the components directory, renaming some of the subdirectories and moving 2 containers to be index.js files. There may be typechecking errors in there, but I assume you'd rather report those than have an internal error. :) EDIT: The issues seem to be around checking whether EDIT: I narrowed it down to the presence of By replacing the definition of This code had worked before, however. There must be something new in the changes I've made in the components directory that's exposing the bug. |
@finneganh In my case, the error occurs when using |
In my case it was removing |
In my case was a node_modules accidentally added to flow-typed dir |
please reopen a fresh issue if this is still an issue! |
I get errors like this when I run flow:
The text was updated successfully, but these errors were encountered: