Giter VIP home page Giter VIP logo

bytestring-progress's People

Contributors

acw avatar felixonmars avatar peaker avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

bytestring-progress's Issues

Invalid Haddock comments

Discovered during a Stackage run:

Unpacking to bytestring-progress-1.0.3/
Resolving dependencies...
Configuring bytestring-progress-1.0.3...
Running Haddock for bytestring-progress-1.0.3...
Preprocessing library bytestring-progress-1.0.3...
Warning: The documentation for the following packages are not installed. No
links will be generated to these packages: base-unicode-symbols-0.2.2.4,
stm-2.4.3, stm-chans-3.0.0.2, terminal-progress-bar-0.0.1.4

dist/build/tmp-26483/System/ProgressBar/ByteString.hs:21:42:
    parse error on input `-- ^ The ByteString to track.'
Haddock coverage:
 100% (  6 /  6) in 'Data.ByteString.Lazy.Progress'

Support terminal-progress-bar 0.1.0

The latest version of bytestring-progress on hackage is constrained to terminal-progress-bar-0.0.1.*, but the latest terminal-progress-bar is version 0.1.0.

updateProgressBar arguments and System.ProgressBar.State.Progress type conflict

I am receiving the following build error while trying to install this package with cabal-install:

$ cabal install bytestring-progress
Resolving dependencies...
Configuring bytestring-progress-1.0.8...
Building bytestring-progress-1.0.8...
Failed to install bytestring-progress-1.0.8
Build log ( /home/george/.cabal/logs/ghc-8.2.2/bytestring-progress-1.0.8-4EygrPelU7JD7WuoH2mM3P.log ):
cabal: Entering directory '/tmp/cabal-tmp-6187/bytestring-progress-1.0.8'
Configuring bytestring-progress-1.0.8...
Preprocessing library for bytestring-progress-1.0.8..
Building library for bytestring-progress-1.0.8..
[1 of 2] Compiling Data.ByteString.Lazy.Progress ( Data/ByteString/Lazy/Progress.hs, dist/build/Data/ByteString/Lazy/Progress.dyn_o )
[2 of 2] Compiling System.ProgressBar.ByteString ( System/ProgressBar/ByteString.hs, dist/build/System/ProgressBar/ByteString.dyn_o )

System/ProgressBar/ByteString.hs:36:15: error:
    • Couldn't match expected type ‘ℤ -> String’
                  with actual type ‘[Char]’
    • The function ‘updateProgressBar’ is applied to two arguments,
      but its type ‘System.ProgressBar.State.Progress -> [Char]’
      has only one
      In the second argument of ‘($)’, namely
        ‘updateProgressBar (fromIntegral now) size’
      In the expression:
        tracker $ updateProgressBar (fromIntegral now) size
   |
36 |     tracker $ updateProgressBar (fromIntegral now) size
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cabal: Leaving directory '/tmp/cabal-tmp-6187/bytestring-progress-1.0.8'
cabal: Error: some packages failed to install:
bytestring-progress-1.0.8-4EygrPelU7JD7WuoH2mM3P failed during the building
phase. The exception was:
ExitFailure 1

I tried both versions 1.0.8 and 1.0.7 and received essentially the same error message.

I have recently had some hiccups with general ghc compilations (due to the arch linux change to dynamic libraries); I think I have worked that out now, and this doesn't seem to be related. But I wanted to mention that just in case this compilation problem I am having is potentially an outside issue.

Consider integrating terminal-progress-bar

The terminal-progress-bar package provides nicely formatted progress bars. It would be convenient if your package would support that, relieving the user from writing some of the following code:

timelog <- BS.readFile (optLogFile flags)
sze <- fileSize <$> getFileStatus (optLogFile flags)

hSetBuffering stderr NoBuffering
trackedTimelog <- trackProgressWithChunkSize (fromIntegral size `div` 100) (\_ b -> do
  hPutChar stderr '\r'
  hPutStr stderr $
      mkProgressBar (msg "Processing data") percentage 80 (fromIntegral b) (fromIntegral size)
  when  (fromIntegral b >= fromIntegral size) $ do
      hPutChar stderr '\r'
      hPutStr stderr (replicate 80 ' ')
      hPutChar stderr '\r'
  ) timelog

Haddock generation error

Discovered in Stackage:

Registering bytestring-progress-1.0.3...
Running Haddock for bytestring-progress-1.0.3...
Running hscolour for bytestring-progress-1.0.3...
Preprocessing library bytestring-progress-1.0.3...
Preprocessing library bytestring-progress-1.0.3...
Warning: The documentation for the following packages are not installed. No
links will be generated to these packages: base-unicode-symbols-0.2.2.4,
stm-2.4.3, stm-chans-3.0.0.2, terminal-progress-bar-0.0.1.4

System/ProgressBar/ByteString.hs:21:42:
    parse error on input ‘-- ^ The ByteString to track.’
Haddock coverage:
 100% (  6 /  6) in 'Data.ByteString.Lazy.Progress'

time-1.5 compatibility

Hi,

now that GHC-7.10.1 is out, please consider uploading a version compatible with time-1.5.

Thanks,
Joachim

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.