Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ivan Malison
    @IvanMalison
    @sondr3 polling label can definitely do what you want
    you might have to do a tiny bit of haskell coding
    polling label lets you run an arbitrary io action to get your text, if you just want some constant text in front of the actual io action you want to run you could do something like:
    ("my prefix text: " ++) <$> actualAction
    Evan Stoll
    @evanjs
    ☝️ figured as much. So there isn’t any sugar for eg command + label, but you can just do that on the callback side of things.
    Ivan Malison
    @IvanMalison
    I mean the above is pretty simple, I guess I don't see the need
    but I guess it could be helpful for those that aren't super haskell literate
    Evan Stoll
    @evanjs
    No no I totally agree, just takes looking at it from a different perspective at times, and I’ve been in that position plenty of times before. @sondr3, hopefully that will work for you
    Speaking of which... I should try out a CPU label. Taffybar CPU graph has been killing mem/CPU usage during compile time lately x_x
    Sondre Nilsen
    @sondr3
    @IvanMalison alright, thanks, that looks fine
    SolarAquarion
    @SolarAquarion
    @IvanMalison it seems certain depends needs to be added to extra-deps

    In the dependencies for Cabal-2.4.1.0:
    binary must match >=0.7 && <0.9, but this GHC boot package has been pruned (issue #4510); you need to add the package explicitly to extra-deps (latest matching version is 0.8.7.0) needed due to taffybar-3.2.1 -> Cabal-2.4.1.0

    In the dependencies for dyre-0.8.12:
    binary needed, but this GHC boot package has been pruned (issue #4510); you need to add the package explicitly to extra-deps (latest matching version
    is 0.8.7.0)
    needed due to taffybar-3.2.1 -> dyre-0.8.12

    In the dependencies for scientific-0.3.6.2:
    binary must match >=0.4.1, but this GHC boot package has been pruned (issue #4510); you need to add the package explicitly to extra-deps (latest matching
    version is 0.8.7.0)
    needed due to taffybar-3.2.1 -> scientific-0.3.6.2

    In the dependencies for text-1.2.3.1(-integer-simple):
    binary needed, but this GHC boot package has been pruned (issue #4510); you need to add the package explicitly to extra-deps (latest matching version
    is 0.8.7.0)
    needed due to taffybar-3.2.1 -> text-1.2.3.1

    In the dependencies for unix-time-0.4.4:
    binary needed, but this GHC boot package has been pruned (issue #4510); you need to add the package explicitly to extra-deps (latest matching version
    is 0.8.7.0)
    needed due to taffybar-3.2.1 -> unix-time-0.4.4

    In the dependencies for uuid-types-1.0.3:
    binary must match >=0.4 && <0.9, but this GHC boot package has been pruned (issue #4510); you need to add the package explicitly to extra-deps (latest matching version is 0.8.7.0) needed due to taffybar-3.2.1 -> uuid-types-1.0.3

    i guess i'll do a PR?
    Evan Stoll
    @evanjs

    So uhhh I think found a way to reproduce(?) my runaway taffybar size issue?
    Opening the link in the main post on this thread seems to trigger it
    https://www.reddit.com/r/rust/comments/egpw7g/announcing_sqlx_a_fully_asynchronous_pure_rust/

    Hopefully somebody else can reproduce? Unless it has something to do with my configuration

    Okay that is weird. Just having that tab active seems to trigger it.
    Interestingly enough, this doesn't happen on the GitHub homepage
    wait... the repo has emoji in the description, which is displayed in the title, and xmonad, for example, is just displaying boxes in their place...
    Could it be..?
    Evan Stoll
    @evanjs
    Sorry for the brain-dump :D it doesn't seem to happen on -- note that the emoji in the description are actually images, whereas the sqlx repo contains raw emoji in text. Going to assume that's related to the issue?
    Evan Stoll
    @evanjs
    Ivan Malison
    @IvanMalison
    @evanjs this is a known issue
    I haven't had time to look in to it and I'm not entirely sure what the cause is
    Evan Stoll
    @evanjs
    Right right. I suppose I’ll post my findings there. So far I’ve lowered it down to “emoji in the title bar”
    Michael Leuchtenburg
    @dyfrgi
    Should "stack setup; stack build" work on a fresh taffybar checkout? It gives me errors about binary. In the dependencies for Cabal-2.4.1.0:
    binary-0.10.0.0 from stack configuration does not match >=0.7 && <0.9 (latest matching version is 0.8.8.0) needed due to taffybar-3.2.2 -> Cabal-2.4.1.0
    That is certainly the Cabal version in the snapshot nightly-2019-06-19 specified in the stack.yaml in the repo
    I've yet to be able to construct a stack.yaml that will allow me to build it, in fact. Is building with allow-newer: true just required, or am I missing something?
    If I change the binary version, I get yet more conflicts, and so on.
    Ivan Malison
    @IvanMalison
    @dyfrgi yeah i would try allow newer
    i havent really been maintaining the stack.yaml super well anymore
    i really recommend using a nix build
    Michael Leuchtenburg
    @dyfrgi
    Alright, thanks, I'll try allow newer and see if that works. NixOS isn't an option for me unfortunately.
    Ivan Malison
    @IvanMalison
    nix != nixos
    you can build with nix instead of stack
    Michael Leuchtenburg
    @dyfrgi
    Finally got a build with allow newer and some fiddling. Had to use taffybar-3.2.1 since 3.2.2 doesn't work with ghc 8.6.5 due to needing a newer version of time - addLocalTime and diffLocalTime are new in time-1.9.0. Oddly I have to run it in /usr/share/pixmap since it's trying to load just the icon for rxvt from cwd, not sure if that's a taffybar bug or a non-absolute filename given for that app somewhere.
    Ivan Malison
    @IvanMalison
    @dyfrgi Couldn't you just make time-1.9.0 an extra-dep?
    I don't think that version is incompatible with ghc 8.6.5
    Evan Stoll
    @evanjs
    But boy, does Nix/NixOS make this and package management way easier :D thank you Ivan for using/providing Nix support in general!
    Ivan Malison
    @IvanMalison
    @evanjs yeah its a game changer for sure.
    P.S. For those who had noticed that taffybar was broken in the latest nixpkgs recently, it is now fixed as of NixOS/nixpkgs#81436
    and no longer requires the overlay in the taffybar repo
    To avoid having taffybar break in the future, we should really try to get it into stackage
    I tried this once here: commercialhaskell/stackage#4630 , but it got reverted because of something involving gir and the docker image they use for ci
    I started commercialhaskell/stackage#5222 but that didnt quite end up working
    @dyfrgi if you're a stack user and could figure it out would appreciate
    Evan Stoll
    @evanjs
    @IvanMalison I noticed that, and thank you! The top-level taffybar wasn’t broken, but the haskellPackages version was, so that was a source of confusion for me
    Aleksandar Dimitrov
    @adimit
    @IvanMalison Adding time-1.9.0 as an extra-dep doesn't work, because a whole lot of deps have a dependency on time < 1.9:
    WARNING: Ignoring HStringTemplate's bounds on time (>=1.4.2 && <1.9); using time-1.9.3.
    WARNING: Ignoring rate-limit's bounds on time (>=1.5.0.1 && <1.9); using time-1.9.3.
    WARNING: Ignoring aeson's bounds on time (>=1.4 && <1.9); using time-1.9.3.
    Aleksandar Dimitrov
    @adimit
    Stack then tries all manner of contortions to make it work somehow, and you end up with a build plan with lots of conflicts.
    That said, I'm absolutely unsure how constructions of Stack build plans even work. Getting a working stack.yml for taffybar is much like the Cabal Hell days of old I remember so fondly.
    Aleksandar Dimitrov
    @adimit
    I've managed to get it to work, and added a PR for the new stack.yaml
    Ivan Malison
    @IvanMalison
    @adimit I think you'd need to use a different resolver to get time 1.9.0
    Aleksandar Dimitrov
    @adimit
    @IvanMalison I'll try to update the resolver to something more recent at some point. I'll open another PR when/if I'm successful.