From: eugenio gigante <giganteeugenio2@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, karthik nayak <karthik.188@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
kaartic.sivaraam@gmail.com
Subject: Re: [RFC][GSoC] Proposal: Refactor git-bisect(1)
Date: Mon, 25 Mar 2024 12:00:58 +0100 [thread overview]
Message-ID: <CAFJh0PTxhDSW1qsnVRrDxmMnp5k16nPGe6RAgrmWow0rgYV+dw@mail.gmail.com> (raw)
In-Reply-To: <ZgE1fxIFFQIdtIyN@tanuki>
> To further stress the point: the biggest challenge of this project is
> indeed to find an agreement with the community whether this refactoring
> will ultimately be worth it. This will require some good arguing on your
> part why exactly you think this is fine and how exactly this will
> interact with other implementations of Git like libgit2/JGit/Dulwich. It
> may very well happen that ultimately the community decides that this
> whole endeavour is not worth it.
Yeah, I'll try to expand a bit in this direction. Meanwhile, if you think
there are others tools to look into, besides the already cited
(libgit2/JGit/Dulwich),
like UI interfaces or something else, please let me know.
(Maybe GitLab is something to keep in mind?)
> I don't think that the unit testing framework would be a good fit. The
> intent of that new framework is mostly to test low-level functionality
> that otherwise cannot be easily tested. But here it should actually be
> quite easy to test things as part of our regular integration-style tests
> in "t/t*.sh", so it would be preferable to write those instead.
Oh ok, I thought the testing framework should have been used for all tests.
I'll change that.
> Thanks for your proposal. Please make sure you submit it as a PDF file
> to the GSoC website soonish, unless you already did that.
Thanks for the review!
Il giorno lun 25 mar 2024 alle ore 09:27 Patrick Steinhardt
<ps@pks.im> ha scritto:
>
> On Fri, Mar 22, 2024 at 11:26:48AM +0100, eugenio gigante wrote:
> > Hi all, this is my proposal for the GSoC 2024.
> >
> > ----------------------------------------------------------------------------------------------------
> >
> > Refactor git-bisect(1) to make its state self-contained
> >
> > Contacts
> > -------------------
> >
> > Full Name: Eugenio Gigante
> > Email: giganteeugenio2@gmail.com
> > Github: www.github.com/EuGig
> >
> >
> > Synopsis
> > ------------
> >
> > The git-bisect(1) tool is employed to pinpoint the exact commit within a
> > series of commits that introduced a particular bug. When initiating a
> > bisection session,
> > it generates a collection of state files within the Git repository,
> > documenting diverse
> > parameters such as ".git/BISECT_START". Instead of having different
> > files scattered
> > in the ‘.git’ directory, it has been suggested by Patrick to introduce
> > a new ‘.git/bisect-state’
> > directory which will contain the state files
> > (https://lore.kernel.org/git/Za-gF_Hp_lXViGWw@tanuki/).
> > The aim of the project is to implement this new layout for storing
> > git-bisect(1) related files.
> > The project will also handle backward compatibility issues that may
> > arise with such a change.
> > This is one of the project ideas suggested by the community of Git.
> > The difficulty for the project should be medium and it should take
> > somewhat between 175 to 350 hours.
> >
> >
> > Contributions
> > -------------------
> >
> > add.c: use unsigned integral type for collection of bits
> > (https://lore.kernel.org/git/20240224112638.72257-2-giganteeugenio2@gmail.com/)
> >
> >
> > Description:
> >
> > Since the MSB of signed integral type’ is special, ‘flags’ fields should be
> > declared of type ‘unsigned integral’. builtin/add.c:refresh() declares
> > 'flags' as signed,
> > and uses it to call refresh_index() that expects an unsigned value.
> > Fix this by modifying its type ‘unsigned int’.
> >
> > Although the code was easy, this patch gave me the opportunity to get
> > familiar with
> > the process of submitting patches. The lesson learned was not only
> > about understanding
> > git commands for formatting and sending patches to the mailing list;
> > but, most importantly,
> > was about how to interact with the community; i. e., how to interact
> > with reviewers,
> > to ask them questions and give them answers. That is why I chose a
> > micro-project idea
> > that explicitly required interaction with the community, before
> > writing any code.
> >
> > Status:
> >
> > Merged to master on: Thu Mar 7 15:59:41 2024
> > commit f46a3f143eba661b9eb2b1e741447d6709eb6e90
> >
> >
> > Deliverables
> > ------------------
> >
> > As soon as the acceptance to the program is communicated, I will start writing a
> > sort of Backlog of required changes which has to be shared with mentors.
> > This has the goal of better tracking progress and possible issues.
> > Already individuated changes and possible strategies are considered in
> > what follows:
> >
> > 1. First, one needs to inspect the possible impacts such a change could have
> > regarding Backward compatibility. There will be two possible situations in which
> > backward compatibility breaks:
> >
> > a. (Noted by Junio (https://lore.kernel.org/git/xmqqwms0ndvu.fsf@gitster.g/)).
> > People switch versions in the middle of a git-bisect session. Even
> > though I think this
> > case would not be that common, one should take this into consideration
> > nonetheless.
> >
> > b. (Noted by Patrick (https://lore.kernel.org/git/ZbDPqOnyLw4yhu--@tanuki/)).
> > Different implementations of Git could suffer backward
> > incompatibilities like Libgit2,
> > JGit and Dulwich. In this case, I will investigate if (and how) these
> > tools would suffer the change.
> >
> > In this phase it is important to find an agreement with the community
> > if the refactoring
> > would be worth it, and in case it is, to find the best solution to
> > guarantee backward compatibility.
> > The simplest way seems to be to teach Git how to recognise the old
> > style layout and move
> > the files by following the new one. This can be achieved by checking
> > the presence of state files
> > inside ‘.git’, just after the starting of a bisect session and by
> > moving them accordingly.
>
> To further stress the point: the biggest challenge of this project is
> indeed to find an agreement with the community whether this refactoring
> will ultimately be worth it. This will require some good arguing on your
> part why exactly you think this is fine and how exactly this will
> interact with other implementations of Git like libgit2/JGit/Dulwich. It
> may very well happen that ultimately the community decides that this
> whole endeavour is not worth it.
>
> > 2. After a strategy for backward compatibility is decided, I will
> > refactor the directory
> > where all the file states are created. This is done by changing the
> > function factory
> > ‘GIT_PATH_FUNC’ in ‘builtin/bisect.c‘’. The following is an example
> > for ‘BISECT_START’:
> >
> > - #static GIT_PATH_FUNC(git_path_bisect_start, “BISECT_START”)
> > + #static GIT_PATH_FUNC(git_path_bisect_start, “bisect-state/start”)
> >
> > Similarly for ‘bisect-state/terms’, etc. This kind of changes should
> > also be done in ‘bisect.c’
> > (which contains the binary searching algorithm git-bisect(1) uses).
> > Then, as noted by
> > Junio (https://lore.kernel.org/git/xmqqwms0ndvu.fsf@gitster.g/) this
> > path should be
> > marked per-worktree, since each worktree can have its own bisect sessions.
> > Probably, also files related to git-worktree use the directory of
> > state files somehow,
> > so one should also check them.
> >
> > 3. Write some tests for the new layout. The plan is to use the new
> > unit testing framework. First tests that come to mind are:
> >
> > a. Check that the state files are inside ‘.git/bisect-state’.
> > b. Check if the path pertains to GIT_DIR and not COMMON_DIR.
> > c. Check that after adding a worktree which was being bisected does
> > not somehow spoil the session and the state files.
> >
> > This can be taken as an example of test file for git-bisect(1) using
> > the new framework:
> >
> > #include test-lib.h
> > #include bisect.h
> >
> > // Write functions like:
> > // t_bisect_dir_init()
> > // t_worktree_init()
> > // t_test_layout()
> > // and include them in cmd_main
> >
> > int cmd_main(int argc, const char **argv)
> > {
> > if (!TEST(t_bisect_dir_init(), “bisect directory initialized”))
> > test_skip_all(“Bisect initialization failed”);
> > if (!TEST(t_worktree_init(), “worktree initialized”))
> > test_skip_all(“Worktree initialization failed”);
> > TEST(t_layout(), “new laypout”);
> >
> > return test_done();
> > }
>
> I don't think that the unit testing framework would be a good fit. The
> intent of that new framework is mostly to test low-level functionality
> that otherwise cannot be easily tested. But here it should actually be
> quite easy to test things as part of our regular integration-style tests
> in "t/t*.sh", so it would be preferable to write those instead.
>
> > 4. Implement strategy for backward compatibility and related tests such as:
> >
> > a. Check if Git correctly recognizes the old layout and in case
> > correctly moves the files according to the new one.
> >
> >
> > Timeline
> > ------------
> >
> > May 1 - 26:
> > Community bounding Period.
> > Read Documentation.
> > Write Backlog.
> >
> >
> > May 27 - July 8:
> > Implement a new layout for state files.
> > Write tests.
> >
> > July 12 - August 19:
> > Assess and implement backward compatibility.
> >
> > August 19 - Deadline :
> > Write documentation for the project.
> >
> > I can dedicate 3 hours a day during weekdays, and 5 hours during the weekends.
> >
> >
> > Benefits to the Community
> > -------------------------------------
> >
> > How state files dedicated for git-bisect(1) are stored is not ideal.
> > Having a single directory dedicated to these files, instead of having different
> > files spread in the Git directory during the bisecting session, is
> > better and facilitates
> > even the removal of them after bisecting. Moreover, as noted by
> > Phillip (https://lore.kernel.org/git/9c800cd5-8d20-4df7-8834-f74ab000695e@gmail.com/#t),
> > by aligning the organization of these files to that used for am,
> > rebase, cherry-pick, etc.,
> > the repo will have a more coherent and uniform layout.
> > This will enhance readability and maintainability in general.
> >
> > Karthik [1] also expressed the need of such refactoring as a prerequisite
> > to introduce new syntax checks for pseudoref in ‘is_pseudoref_syntax()’.
> >
> >
> > [1] See Karthik’s commit: 1eba2240f8ba9f05a47d488bb62041c42c5d4b9c
>
> Nicely summarized.
>
> >
> > Biographical information
> > ----------------------------------
> >
> > I’m a former student of Logic and Philosophy who turned to coding
> > after graduating.
> > I have been working as a Developer for NTT Data Italia for a year.
> > I hold a full-time job, but I've seen that it doesn't conflict with
> > the rules of GSoC
> > since I'm an open source beginner. I am fully capable of managing my
> > workload independently,
> > including my working hours. I know it is not ideal, but I can
> > definitely work around
> > my schedule and dedicate time to the project.
> >
> > Before, I have contributed small patches to two open source projects:
> > - Pydata/Sparse: https://github.com/pydata/sparse/pull/611
> > - Pennylane: https://github.com/PennyLaneAI/pennylane/pull/3959
>
> Thanks for your proposal. Please make sure you submit it as a PDF file
> to the GSoC website soonish, unless you already did that.
>
> Patrick
next prev parent reply other threads:[~2024-03-25 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 10:26 [RFC][GSoC] Proposal: Refactor git-bisect(1) eugenio gigante
2024-03-25 8:27 ` Patrick Steinhardt
2024-03-25 11:00 ` eugenio gigante [this message]
2024-03-25 11:24 ` Patrick Steinhardt
2024-03-28 3:23 ` Kaartic Sivaraam
2024-03-29 9:05 ` eugenio gigante
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFJh0PTxhDSW1qsnVRrDxmMnp5k16nPGe6RAgrmWow0rgYV+dw@mail.gmail.com \
--to=giganteeugenio2@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--cc=karthik.188@gmail.com \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.