HISE Logo Forum
    • Categories
    • Register
    • Login

    Bug/Feature tracker

    Scheduled Pinned Locked Moved General Questions
    bug trackerfeature tracker
    30 Posts 6 Posters 2.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • d.healeyD
      d.healey @Christoph Hart
      last edited by d.healey

      I like it!

      @christoph-hart said in Bug/Feature tracker:

      A HISE Snippet as formatted code block. If the example needs external resources

      Would it be difficult for snippets to inline included js files?

      Oh might be a good idea to setup an issue template for bug reports - https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

      Libre Wave - Freedom respecting instruments and effects
      My Patreon - HISE tutorials
      YouTube Channel - Public HISE tutorials

      Christoph HartC 1 Reply Last reply Reply Quote 0
      • Christoph HartC
        Christoph Hart @d.healey
        last edited by

        @d-healey yes that templates thingie is a good idea, I'll check it out.

        1 Reply Last reply Reply Quote 0
        • ustkU
          ustk @Christoph Hart
          last edited by

          @christoph-hart I PM'ed you to help finding a solution recently with no answer, I hope now we're getting somewhere reliably 馃檮

          Can't help pressing F5 in the forum...

          Christoph HartC 1 Reply Last reply Reply Quote 1
          • Christoph HartC
            Christoph Hart @ustk
            last edited by

            @ustk yeah sorry I forgot to respond but you definitely laid the seed in my brain for this subject ;)

            Christoph HartC 1 Reply Last reply Reply Quote 2
            • Christoph HartC
              Christoph Hart @Christoph Hart
              last edited by Christoph Hart

              Alright, I've added an example issue for one of the most recent bugs (plus I'll post a "moved to GitHub Issues" to the forum topic so we know it was taken to the next level...

              Link Preview Image
              SliderPack does not update when invisible 路 Issue #250 路 christophhart/HISE

              Forum discussion https://forum.hise.audio/topic/5074/sliderpack-issue/4 Commit ecd5f15 Conditions to reproduce the bug OS: both macOS / Windows HISE: yes Compiled Project: yes Problem Description Knob from interface to a sliderpack in a ...

              favicon

              GitHub (github.com)

              1 Reply Last reply Reply Quote 2
              • d.healeyD
                d.healey @Christoph Hart
                last edited by

                @christoph-hart said in Bug/Feature tracker:

                you can add the label Valid Bug report

                I think only the repo owner can add labels

                Libre Wave - Freedom respecting instruments and effects
                My Patreon - HISE tutorials
                YouTube Channel - Public HISE tutorials

                Christoph HartC 1 Reply Last reply Reply Quote 0
                • Christoph HartC
                  Christoph Hart @d.healey
                  last edited by

                  @d-healey Nice, even more power for me!

                  ustkU 1 Reply Last reply Reply Quote 2
                  • ustkU
                    ustk @Christoph Hart
                    last edited by

                    @christoph-hart So this system is adopted?
                    Your are lucky I don't have much time at the moment but the list is ready, right there... 馃敟 :)

                    Can't help pressing F5 in the forum...

                    Christoph HartC 1 Reply Last reply Reply Quote 1
                    • Christoph HartC
                      Christoph Hart @ustk
                      last edited by

                      Keep thinking about this and maybe it's a good idea to still report a bug first in the forum and then if it's really confirmed, we move it to GitHub.

                      I'm just trying to think of ways to keep the GitHub issues a super clean list of (rather high priority) bugs I need to work through, because I can imagine that if everybody just writes every bug ever there we're back at square one.

                      Dan KorneffD ustkU 3 Replies Last reply Reply Quote 1
                      • Dan KorneffD
                        Dan Korneff @Christoph Hart
                        last edited by

                        @christoph-hart said in Bug/Feature tracker:

                        maybe it's a good idea to still report a bug first in the forum

                        Maybe back to the Mantis idea so issues can be organized?

                        Dan Korneff - Producer / Mixer / Audio Nerd

                        1 Reply Last reply Reply Quote 1
                        • ustkU
                          ustk @Christoph Hart
                          last edited by

                          @christoph-hart That's what I imagined. Bug have to be confirmed by the community first as eligible to open an issue, so the git isn't cluttered by false alarms.
                          I agree that a priority tag should be attached to the issue. If it isn't a problem with a small list it becomes to be a problem with 30 lines, where high priority bugs have the risk to be drowned.

                          Can't help pressing F5 in the forum...

                          1 Reply Last reply Reply Quote 0
                          • ustkU
                            ustk @Christoph Hart
                            last edited by

                            @christoph-hart Low priority should also be listed so they aren't lost, and people can see it as already been raised at a glance. So definitely a more adapted tool would be better (I don't know Mantis).

                            Can't help pressing F5 in the forum...

                            Christoph HartC 1 Reply Last reply Reply Quote 0
                            • Christoph HartC
                              Christoph Hart @ustk
                              last edited by

                              Alright, then we have a Confirmed Bug label for each bug report that goes through the "bug vetting process" (issue raised in the forum and confirmed by multiple parties). When a bug report is raised in the forum, we'll discuss it and decide whether to stick a Low Priority label or a High Priority label to it. When this is done, the forum topic will be closed and I'll move it to GitHub issues.

                              Sounds good? This gives us enough flexibility to talk and discuss while keeping the issue list clean and organized.

                              d.healeyD 1 Reply Last reply Reply Quote 5
                              • d.healeyD
                                d.healey @Christoph Hart
                                last edited by

                                @christoph-hart said in Bug/Feature tracker:

                                the forum topic will be closed

                                Closed = still viewable and no new replies?

                                Libre Wave - Freedom respecting instruments and effects
                                My Patreon - HISE tutorials
                                YouTube Channel - Public HISE tutorials

                                Christoph HartC 1 Reply Last reply Reply Quote 0
                                • Christoph HartC
                                  Christoph Hart @d.healey
                                  last edited by

                                  @d-healey yes. You can comment on the issue from then on if there鈥榮 something to add but this will prevent that the conversation is split between the places.

                                  Christoph HartC 1 Reply Last reply Reply Quote 1
                                  • Christoph HartC
                                    Christoph Hart @Christoph Hart
                                    last edited by

                                    Also maybe we can tag the forum topics that are supposed to lead to a GitHub issue with a certain tag (eg. "BUG TRACKER"), then it's easier to keep track of them.

                                    Lots of rules :)

                                    ustkU 1 Reply Last reply Reply Quote 2
                                    • C
                                      crd
                                      last edited by

                                      This is great! I am happy to see this happening.

                                      1 Reply Last reply Reply Quote 0
                                      • ustkU
                                        ustk @Christoph Hart
                                        last edited by

                                        @christoph-hart And either mark the thread as FIXED or even delete it, unless there's a good reason to keep it if the issue is fixed?

                                        Can't help pressing F5 in the forum...

                                        Christoph HartC 1 Reply Last reply Reply Quote 1
                                        • Christoph HartC
                                          Christoph Hart @ustk
                                          last edited by

                                          @ustk not sure if we need to delete the topic - when its locked it will automatically be buried by other topics.

                                          I would also suggest to not marking the forum topic fixed - if you want the information of which bugs are still active, just use the Github issue list (Closed issues will automatically be removed from the list).

                                          LindonL 1 Reply Last reply Reply Quote 1
                                          • C
                                            crd
                                            last edited by crd

                                            @Christoph-Hart

                                            so just to be clear on how best to report a bug:

                                            1. open a thread, make sure it's valid and other people can reproduce it
                                            2. make an issue report on GitHub
                                            3. post the GitHub issue link in the forum thread

                                            Correct?

                                            Christoph HartC 1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post

                                            29

                                            Online

                                            1.7k

                                            Users

                                            11.9k

                                            Topics

                                            103.7k

                                            Posts