It's definitely hashable. Here's a minimal failing test case: https://gist.github.com/gregorycollins/5748445
On Sat, May 18, 2013 at 11:38 PM, Roman Cheplyaka <r...@ro-che.info> wrote: > Indeed it looks like a bug in hashable — it goes away with > hashable-1.1.2.5. > > Building with -f-sse2 results in a linker error > > Loading package hashable-1.2.0.7 ... linking ... ghc: > /home/feuerbach/tmp/aeson/.cabal-sandbox/lib/i386-linux-ghc-7.6.3/hashable-1.2.0.7/libHShashable-1.2.0.7.a: > unknown symbol `hashable_siphash24_sse2' > ghc: unable to load package `hashable-1.2.0.7' > > Roman > > * Gregory Collins <g...@gregorycollins.net> [2013-05-18 22:19:38+0200] > > First off, everyone reporting results to this thread: your bug report > would > > be much more helpful if you included your OS/architecture/GHC version > > combo, as well as the results of re-running the tests if you build > > "hashable" with "cabal install -f-sse2". > > > > I have a funny feeling that this is a bug in hashable or > > unordered-containers. I'm guessing hashable, especially because of this: > > > > https://github.com/tibbe/hashable/issues/66 > > > > and because hashable has had subtle bugs in its C code before (see > > https://github.com/tibbe/hashable/issues/60). > > > > G > > > > On Sat, May 18, 2013 at 6:25 PM, Roman Cheplyaka <r...@ro-che.info> > wrote: > > > > > I am observing a non-deterministic behaviour of aeson's parser. > > > > > > I'm writing here in addition to filing a bug report [1] to draw > > > attention to this (pretty scary) problem. > > > > > > To try to reproduce this problem, do this: > > > > > > git clone https://gist.github.com/5604887.git aeson > > > cd aeson > > > ghc aeson.hs > > > ./aeson | sort | uniq -c > > > > > > This is my result: > > > > > > 32 Left "key \"module\" not present" > > > 55 Left "When parsing the record SymValue of type Main.SymValueInfo > > > the key fixity was not present." > > > 1913 Right () > > > > > > Can others reproduce this in their environments? > > > > > > Does anyone have ideas about where the bug may lie? > > > Many aeson's dependencies do unsafe IO stuff that could lead to > > > such consequences. > > > > > > Roman > > > > > > [1]: https://github.com/bos/aeson/issues/125 > > > > > > _______________________________________________ > > > Haskell-Cafe mailing list > > > Haskell-Cafe@haskell.org > > > http://www.haskell.org/mailman/listinfo/haskell-cafe > > > > > > > > > > > -- > > Gregory Collins <g...@gregorycollins.net> > -- Gregory Collins <g...@gregorycollins.net>
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe