near-lake-framework-js icon indicating copy to clipboard operation
near-lake-framework-js copied to clipboard

JS Library to connect to the NEAR Lake S3 and stream the data

Results 11 near-lake-framework-js issues
Sort by recently updated
recently updated
newest added

See Feature Request https://github.com/near/queryapi/issues/366 * successfulFunctionCalls * socialOperations This is more specific than other methods in the class. However, this specificity helps users. In future we could add additional "more...

No redirection limit when, for example, a connector drops to a custom Minio repository, there is no way to catch a bug, there is an eternal reconnection to the repository

_This issue was automatically created by [Allstar](https://github.com/ossf/allstar/)._ **Security Policy Violation** Security policy not enabled. A SECURITY.md file can give users information about what constitutes a vulnerability and how to report...

allstar

_This issue was automatically created by [Allstar](https://github.com/ossf/allstar/)._ **Security Policy Violation** Dismiss stale reviews not configured for branch main --- This issue will auto resolve when the policy is in compliance....

allstar

Hey near team i have been facing the following issue from time to time and would like to know what could be causing it ? is it a local issue...

So after running the near indexer for a extended period of time, while going thru the logs i realized there are time periods where indexer errors out , for e.g...

Hey near team, I have integrated the near indexer into my project but I am running into a issue where sometimes the chunk property returned by the lake indexer seems...

During the #1 review, we had a suggestion from @luixo > Shouldn't we let users stop streaming? > I believe we can reuse [AbortController interface]([https://developer.mozilla.org/en-US/docs/Web/API/AbortController](https://developer.mozilla.org/en-US/docs/Web/API/AbortController)) (though I'm not aware if...

help wanted

It would also be a good idea to look in to the [Changeset GitHub Action](https://github.com/changesets/action), which automatically releases packages to their registry. _Originally posted by @morgsmccauley in https://github.com/near/near-lake-framework-js/pull/18#pullrequestreview-1268396987_

Ideally, we'd have a single config which is accessible to all packages, each package config would then `extend` that config to inherit those rules, meaning the whole repo is consistent....