Skip to content

Issues: near/near-lake-indexer

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

7 Open 17 Closed
7 Open 17 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

When trying to put a block into a custom bucket, considers the block to be the name of the bucket
#100 opened Jul 15, 2024 by TheRegent
Security Policy violation SECURITY.md allstar
#81 opened Oct 22, 2023 by allstar-app bot
1
Update version of nearcore to the latest 1.35.0 version and have automated version update system in future good first issue Good for newcomers help wanted Extra attention is needed
#78 opened Sep 7, 2023 by anthony-near
2
Lake Indexer should not get stuck bug Something isn't working
#56 opened Oct 28, 2022 by frol
3
Data is lost in block 22633808 bug Something isn't working
#47 opened Jul 12, 2022 by telezhnaya
@khorolets @telezhnaya
15
Ensure stability of the structure of block and shard serialization enhancement New feature or request
#34 opened Apr 21, 2022 by frol 1.0
@telezhnaya
docs: Add curl or similar examples of how to use near-lake data from S3
#26 opened Feb 22, 2022 by khorolets 1.0
@khorolets
ProTip! Add no:assignee to see everything that’s not assigned.