Hi James, Yes, I am a GSoC candidate.
I have caught up on your recent emails to the list and the new guidelines established in the Matrix channel. Apologies for the noise here. I am halting all early implementation and will keep further technical discussions off this main list until the official application period opens and mentors are assigned, as instructed. Best regards, Mohammed Saifulhuq On Sun, Mar 1, 2026 at 10:27 PM James Dailey <[email protected]> wrote: > Mohammed > > Are you a GSOC candidate for Fineract? If so, please see our several > emails in recent days. > > > > Sent from Gmail Mobile > > > On Wed, Feb 25, 2026 at 3:07 AM Mohammed Saifulhuq < > [email protected]> wrote: > >> Hi everyone, >> >> Following up on the Transaction Idempotency POC. Based on feedback from >> Aleks on the ticket, we are pivoting away from patching individual modules >> and moving towards a system-wide, generic interceptor approach aligned with >> FINERACT-2169 <https://issues.apache.org/jira/browse/FINERACT-2169>. >> >> I have just posted the revised technical architecture on the Jira ticket: >> FINERACT-2485 >> <https://issues.apache.org/jira/projects/FINERACT/issues/FINERACT-2485?filter=allissues&orderby=level+ASC%2C+priority+DESC%2C+updated+DESC> >> >> The proposed mechanics involve a Spring OncePerRequestFilter and a >> dedicated DB table for atomic locking via unique constraints. >> >> I am starting the implementation now but would appreciate any immediate >> red flags regarding the database constraint approach for the atomic lock. >> >> Best, Mohammed Saifulhuq >> >
