Comments (3)
Workarounds/solutions:
- Specify a different hspec formatter that doesn't print to stdout while the test is running, but it's unintuitive for the test passing to depend on which test framework formatter you're using.
- The test could run in a subprocess so that it has a different stdout. That's a pretty heavyweight solution.
- Put the test behind a flag like
--enable-stdout-tests
and default to disabled. - Always run
stack test conduit | cat
to trick hspec into disabling progress since it checks forNO_COLOR
and a terminal
from conduit.
stdoutC
is a thin wrapper around sinkHandle
. It's probably best to simply skip this test and rely on tests of sinkHandle
instead. I'd accept a PR for this. However, I've never experienced this behavior myself, and it may indicate that there are issues elsewhere. I don't think conduit is the culprit here.
from conduit.
The timer ticks at 0.05s intervals, so slower machines are more likely to encounter the error (maybe yours is fast). It's moreso the conflicting uses of stdout between hspec and the conduit tests than one or the other individually that's causing this issue. PR: #480
from conduit.
Related Issues (20)
- What is ReleaseType for? HOT 2
- `ResourceT` is subject to the `forever` space leak
- slidingWindowC makes consuming tail elements inconvenient HOT 3
- Quadratic performance on left-associated binds HOT 6
- resourcet needs unliftio-core >=0.1.1.0 lower bound
- Implementing delay operator HOT 3
- Clarification regarding `sinkFile` and `sinkFileBS` HOT 1
- Compatibility with mtl-2.3 HOT 5
- Lots of inline-rule-shadowing warnings
- Accumulate ByteStrings into single result HOT 3
- bracketP with custom monad stack HOT 1
- Flaky test suite failure with GHC 9.4.2 / text-2.0.1 HOT 6
- *> leaks space where >> doesn't - so should the *> implementation be optimized? HOT 1
- Confusion with `sourceProcessWithStreams` and `takeExactly` HOT 1
- `sourceProcessWithStreams` without hijacking `stderr`? HOT 2
- Support incrementally feeding into Conduits HOT 1
- Better performance with a left associative `.|`? HOT 2
- Functor instance causes memory leak when used with Shake
- Running a conduit in a function with an unrelated parameter twice leaks memory
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from conduit.