aggrea
I kept getting the below error
Math that I believed should always end up with an integer was sometimes not, I am still not sure if its a weird floating point thing or an actual mistake in my logic but either way casting to an int eliminated the error
const int_index = Math.floor((page - 1) * pageSize);
const { key } = await timeline_aggregate.at(ctx, int_index);
@lee thought you'd like to know that
Oops!
Sorry, an unexpected error has occurred.
[CONVEX
Q(page_timeline:pageOfTimeline)] [Request ID: 46915a3b4d2c7ff3] Server
Error
Uncaught ConvexError: Uncaught ConvexError: offset exceeded count by
-5.000000000001819 (in node j979aarwny50526j9thqpjy8g97bgp1a)
at atOffsetInNode
(../../../../node_modules/@convex-dev/aggregate/src/component/btree.ts:725:0)
at async atOffsetInNode
(../../../../node_modules/@convex-dev/aggregate/src/component/btree.ts:719:63)
at async atOffsetInNode
(../../../../node_modules/@convex-dev/aggregate/src/component/btree.ts:719:63)
at async atOffsetInNode
(../../../../node_modules/@convex-dev/aggregate/src/component/btree.ts:719:63)
at async atOffsetInNode
(../../../../node_modules/@convex-dev/aggregate/src/component/btree.ts:719:63)
at async atOffsetHandler
(../../../../node_modules/@convex-dev/aggregate/src/component/btree.ts:379:0)
at async at [as at]
(../../../../node_modules/@convex-dev/aggregate/src/client/index.ts:114:6)
at async handler (../../convex/page_timeline.ts:175:23)
Called by client
3 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
awesome! yeah i figured it was probably a rounding issue on the user-code side, where it should have been rounded but wasn't. It took a while to confirm that the internal library couldn't cause this issue (we asked deep research) https://chatgpt.com/share/67c9cb50-aa30-8008-bfb6-bd5a30551529
GitHub
assert that offset is an integer by ldanilek · Pull Request #26 · g...
users in discord are reporting errors that look like
offset exceeded count by -3.9999999999990905
https://discord.com/channels/1019350475847499849/1347058269528526878/1347058269528526878
which cou...