1. 2

    OP mentions GPU issues and that he was hoping avoid dealing with a proprietary driver. I wonder if he tried the proprietary driver in the end, though and if the issues went away.

    1. 4

      Likely his issues would be alleviated by running a newer (non-LTS) kernel with the appropriate drivers mainlined.

      I have never had a good experience with the AMD proprietary drivers.

      1. 2

        I always buy one-generation-older-than-current graphic cards for this reason. If something doesn’t work out of the box I’ll just return it for something else.

        1. 2

          That was my original plan, but I got greedy at the end and went the for a newer GPU from the current generation. I just assumed that with all the praise amdgpu was getting, this wouldn’t matter as it did in the past.

        2. 1

          I’ve been trying newer kernels over the course of several months, but they didn’t help either. Probably they fixed the problem by now, though.

        3. 2

          I tried the proprietary drivers as well, but they didn’t help. From what I gathered they are pretty close to the the FOSS drivers (both are developed by AMD themselves), so it’s not very likely that you’d get different results https://wiki.archlinux.org/title/AMDGPU#AMDGPU_PRO

        1. 7

          I don’t know, I think this might make me want to kill myself: http://0x0.st/-zeS.png

          1. 7

            Don’t worry. Help is near: https://github.com/Annihil/github-spray

            1. 2

              From the feedback we got so far, many people seem to have the same problem.

              Here are a few reasons:

              • Private commits are missing. As a workaround you could temporarily enable them for the print.
              • Only one year is busy, the rest is mostly empty. For that case we’re working on a layout for a single year.
              • People are more active on Gitlab/Bitbucket. Technically we could write an API integration for that.
              • People aren’t interested in their own commits but they do care about a project. We’re considering to add repo support so that you could print rust-lang/rust or facebook/react if you wanted. Would anyone be interested?

              Thoughts on the above would be appreciated.

              1. 2

                I don’t think I’d buy one of these for my own commit history, but others will. Mainly I can see it being marketed to companies & teams, so making it work at the project level should be useful.

                If there were repo support, and if you could annotate the history with some text bubbles, then users could mark important milestones, and tell the story of the project. You could make it optional to auto-render things like tags for version numbers. You could make it more personal by adding the avatars & stats of the contributors somewhere in the layout.

                Being able to select an arbitrary timescale would enable more use cases. Similar to shopkeepers who frame their first dollar bill earned, a team could enshrine their first week or month of commits. They could show off the crunch time (however long it was) when everyone made tons of commits and everything got finished just before launch.

                1. 1

                  Thanks for the feedback. That’s all great advice. We also considered prints for teams (with discounts for larger volumes) before and I’m glad others think alike. Support for annotations and custom time-ranges sounds very reasonable.

                  If you don’t mind me asking, why wouldn’t you order one for yourself? Is it that you don’t like the layout, don’t have many public commits, or you don’t want to make a fuzz around it? I’m asking because we’re always interested in new visualizations for different sorts of users.

              1. 3

                Whelp, you could print 2015 to 2020. Looks pretty busy to me. :)

                1. 1

                  Yeah, of course! It’s interesting to reflect on my life and the changes that happened in it that caused it, is all :)

              1. 3

                Does it work properly with stdin and EOFs sent with ^D?

                1. 6

                  Yes.

                  1. 1

                    I didn’t know this was an issue. :-) tail -f - hitting ctrl+d does not quit the program, but cat - does.