Razvan-Nicolae Chichirau's activity
From 08/26/2025 to 09/24/2025
09/24/2025
- 06:53 AM User Interface Bug #9738 (Test): Infinite loop/memory leak caused by ENTRY trigger on current-window
- Branch 9738a was merged to trunk rev 16183 and archived.
- 06:37 AM User Interface Bug #9738: Infinite loop/memory leak caused by ENTRY trigger on current-window
- Razvan-Nicolae Chichirau wrote:
> I'll do:
> * Smoke-tests on 2 customer + demo apps on web
> * check some UI rela...
09/23/2025
- 06:55 AM User Interface Bug #9738: Infinite loop/memory leak caused by ENTRY trigger on current-window
- I'll do:
* Smoke-tests on 2 customer + demo apps on web
* check some UI related tests
* verify the unit tests from... - 03:38 AM User Interface Bug #9738 (Review): Infinite loop/memory leak caused by ENTRY trigger on current-window
- Commited on *9738a/rev. 16177*.
Hynek: Please review.
09/22/2025
- 02:56 AM User Interface Bug #9738 (WIP): Infinite loop/memory leak caused by ENTRY trigger on current-window
- Web GUI is stuck in @p2j.canvas_renderer.js -> replay()@ due to using the same variable for looping:...
09/19/2025
- 03:59 AM Database Bug #9383 (Review): Cache only the current delegate on transaction commit if a ProgressiveResults...
- Rev. 16144 should now hold the invariant from #9383-53. Please review.
09/18/2025
- 07:08 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I see. In this case, we need to change the whole @transactionCommiting()@ because it is already constructed to yield ...
- 04:35 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- In #9383-46, position 830 is actually @rows.get(0)@. The first record from @rows@ will always match the record under ...
- 04:19 AM Database Bug #9383 (Review): Cache only the current delegate on transaction commit if a ProgressiveResults...
- Please review rev. 16143.
- 02:27 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Alexandru Lungu wrote:
> If the bracket you are looking at is the 100th one generated with exponent 5, then techni...
09/17/2025
- 07:58 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- For example, the current position is 830:
* Old bracket = 3 (from 111 to 1010)
* new bracket = 10 (from 811 to 910)... - 07:43 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Alexandru Lungu wrote:
> > delegate = new SimpleResults(rows);
>
> Is a delegate with maybe 1M rows, but this i... - 07:31 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- I've just now realized that we don't actually need neither to call @moveTo@ because we already have the rows in cache...
- 06:46 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Yes. Executing @moveTo@ may be safer than manually updating the state at the cost of re-executing the query. The good...
- 06:18 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Alexandru Lungu wrote:
> ** Also, shouldn't it be @> 2@ instead of @>= 2@? If it is already equal to 2, the progress...
09/12/2025
- 04:29 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Alex, please review rev. 16142 when possible.
Note that #10172 sees only a reduction of 7.5k @load()@ calls out of...
09/10/2025
- 01:49 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- If the concern is on the bracket calculation, maybe when commiting a transaction we can convert the current bracket t...
09/09/2025
- 08:27 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- > For 1e9 - 1, if the forcedMaxExponent is 2, then the right bracket is around (1e9 - 100) and offset is 99 (size is...
- 04:25 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Also commited rev. 16141 to remove some unnecessary history entries.
- 04:14 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Alex: Please review *9383a/rev. 16138-16140*.
09/04/2025
- 08:21 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- > So, technically, it is right to cache records after commit only if it fits in this 1024 limit. Otherwise, with high...
- 07:34 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- > What are the sizes of brackets to be cached when COMMIT occurs? I am wondering if we reach brackets of size 1.000 (...
09/03/2025
- 03:35 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Increasing the lenient threshold does not solve #10172. Although all record properties are now cached, the problem st...
09/01/2025
- 08:42 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- With 9383a I get around 30k calls for the scenario from #10172 comparative with 34-35k calls with trunk. The reason f...
- 05:07 AM Base Language Bug #10352: Fix READ-JSON dataset handle method's behaviour
- Smoke-test for 10352a on another customer app showed no regressions.
08/28/2025
- 09:04 AM Database Bug #9383: Cache only the current delegate on transaction commit if a ProgressiveResults is used
- Danut, @transactionCommiting@ is not implemented as a no-op in all @Results@ classes after the rebase:...
Also available in: Atom