-
Notifications
You must be signed in to change notification settings - Fork 158
Feature/snaps events v2 integration #1492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
…to limits and quotas
…es. Source app identifiers are now set using env variables
…s, added FileGroup
moratom
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Aljaz!
Left a few questions, comments
| uint64_t size; | ||
| std::string checksum; | ||
| proto::event::PrepareFileUploadClass classification; | ||
| friend class EventsManager; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does the EventsManager need to be a friend here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the current implementation it's accessing FileData's private members directly
| # Properties | ||
| # Enter you hub team's api-key | ||
| eventMan = dai.EventsManager() | ||
| eventMan.setToken("") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left it here to "alert" the user that the token must be set - specifically in the peripheral mode. I can remove it, if this doesn't make sense
Purpose
Update snaps and events to V2
Specification
None / not applicable
Changes in the uploading of the events and snaps to the Luxonis Hub, the protobuf definition used in connection to events and snaps, examples in C++ & Python
Dependencies & Potential Impact
None / not applicable
Deployment Plan
None / not applicable
Testing & Validation
This was tested using the stg and prod versions of the Hub, by uploading different snaps and events