sourcecred/.flowconfig

# If modifying this file, please modify .flowconfig-ci too!
[ignore]

[include]

[libs]
flow-typed

[lints]

[options]
suppress_comment=\\(.\\|\n\\)*\\$ExpectFlowError
include_warnings=true

[strict]
Attempt to fix CI flakes (#1243) (#1282) This is my latest salvo in trying to fix the persistent CI flakes we've been having. They center on flow failing with `Out of retries, exiting!`. Here's a representative failure [1]. My approach here is based on a discussion in a [GitHub thread] which suggests that setting `server.max_workers=1` in the config can fix it. Unfortunately, since it's in the flowconfig and is not a command line option, I needed to fork the flowconfig into a CI and non-CI version. Test plan: Merge it, and see if the flake goes away. [1]: https://circleci.com/gh/sourcecred/sourcecred/1609?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link [GitHub thread]: https://github.com/atlassian/react-beautiful-dnd/issues/1007 2019-08-13 18:22:03 +02:00			`# If modifying this file, please modify .flowconfig-ci too!`
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion 2018-02-16 14:32:24 -08:00			`[ignore]`

			`[include]`

			`[libs]`
			`flow-typed`

			`[lints]`

			`[options]`
Flow: enable `//$ExpectFlowError` (#315) As of this commit, adding the comment `//$ExpectFlowError` in flow-typed code asserts that the next line must cause a flow error. If it does, no error or warning is generated. If it does not, then this produces a flow warning, which is visible to developers running `yarn flow` and additionally causes travis to fail. Test plan: - As committed, `yarn travis` passes. - I added `//$ExpectFlowError` above some line of flow-checked code which does not currently throw an error. Afterwards, `yarn travis` failed (and a helpful message was displayed in console on running `yarn flow`) - I added the following bad code into one of our files: ```javascript //$ExpectFlowError const foo: string = 3; ``` As expected, `yarn flow` and `yarn travis` both passed. 2018-05-29 13:56:36 -07:00			`suppress_comment=\\(.\\\|\n\\)*\\$ExpectFlowError`
			`include_warnings=true`
Frontend setup (#13) * Initial infrastructure for sourcecred-explorer. Setup npm, yarn, flow, jest using scaffolding from create-react-app. - used create-react-app to get the basic pieces - added support for flow via instructions in the create-react-app user guide - added flow-typed so that flow+jest will work well * Add some additional resources * Add index.css * Remove .DS_STORE per @wchargin's suggestion 2018-02-16 14:32:24 -08:00
			`[strict]`