kjuulh/nodata
1
0
Fork 0
Code Issues 1 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

chore(release): v0.1.0 #8

Open
kjuulh wants to merge 1 commits from cuddle-please/release into main
pull from: cuddle-please/release
merge into: kjuulh:main
Conversation 0 Commits 1 Files Changed 1 +66
kjuulh commented 2024-11-17 20:59:59 +01:00
Owner
Copy Link

Added

  • with updated notmad

  • added please and release

  • change order of grpc host

  • add replicas 1

  • add s3 and deployment

  • add prometheus and protobuf messages

  • increase size of index

  • add indexes

  • set notification to 4mb

  • add storage backend

  • remove more partitions

  • cleanup

  • remove keys and ids

  • working dagger engine

  • should listen on public endpoint

  • with sdk

  • with dagger engine

  • do cleanup

  • add broker setup
    this is mainly to decouple the actual sending of events, from the ingest.

    we now ingest the data, and update consumer groups with the new offset. Consumer groups now in the background continously send out data from the update. they tick 1 second between checks, but if something takes long than a second, the next run just continues from where we left off

  • update

  • add basic streaming data

  • add ingest layer

  • extract handler

  • add offset to consumers

  • add complexity

  • added v1 files

  • add operations endpoint to get topics

  • add staging

  • add data ingest

  • add docs

  • add base

Fixed

  • (deps) update rust crate aws-sdk-s3 to v1.76.0
  • (deps) update aws-sdk-rust monorepo
  • (deps) update aws-sdk-rust monorepo
  • (deps) update rust crate aws-sdk-s3 to v1.70.0
  • (deps) update aws-sdk-rust monorepo
  • (deps) update aws-sdk-rust monorepo
  • (deps) update rust crate serde to v1.0.216
  • (deps) update rust crate aws-sdk-s3 to v1.65.0
  • (deps) update rust crate aws-sdk-s3 to v1.63.0
  • (deps) update rust crate serde to v1.0.215
  • (deps) update all dependencies
  • offset be inclusive end

Other

  • (deps) update tokio-prost monorepo to v0.13.5
  • (deps) update tokio-prost monorepo to v0.13.4
  • (deps) update rust crate tracing-subscriber to v0.3.19
  • (deps) update rust crate tracing to v0.1.41
  • into files
### Added - with updated notmad - added please and release - change order of grpc host - add replicas 1 - add s3 and deployment - add prometheus and protobuf messages - increase size of index - add indexes - set notification to 4mb - add storage backend - remove more partitions - cleanup - remove keys and ids - working dagger engine - should listen on public endpoint - with sdk - with dagger engine - do cleanup - add broker setup this is mainly to decouple the actual sending of events, from the ingest. we now ingest the data, and update consumer groups with the new offset. Consumer groups now in the background continously send out data from the update. they tick 1 second between checks, but if something takes long than a second, the next run just continues from where we left off - update - add basic streaming data - add ingest layer - extract handler - add offset to consumers - add complexity - added v1 files - add operations endpoint to get topics - add staging - add data ingest - add docs - add base ### Fixed - *(deps)* update rust crate aws-sdk-s3 to v1.76.0 - *(deps)* update aws-sdk-rust monorepo - *(deps)* update aws-sdk-rust monorepo - *(deps)* update rust crate aws-sdk-s3 to v1.70.0 - *(deps)* update aws-sdk-rust monorepo - *(deps)* update aws-sdk-rust monorepo - *(deps)* update rust crate serde to v1.0.216 - *(deps)* update rust crate aws-sdk-s3 to v1.65.0 - *(deps)* update rust crate aws-sdk-s3 to v1.63.0 - *(deps)* update rust crate serde to v1.0.215 - *(deps)* update all dependencies - offset be inclusive end ### Other - *(deps)* update tokio-prost monorepo to v0.13.5 - *(deps)* update tokio-prost monorepo to v0.13.4 - *(deps)* update rust crate tracing-subscriber to v0.3.19 - *(deps)* update rust crate tracing to v0.1.41 - into files
kjuulh force-pushed cuddle-please/release from 60e523aeb9 to c07a562ace 2024-11-19 17:32:37 +01:00 Compare
kjuulh force-pushed cuddle-please/release from c07a562ace to 4a1cbf33c7 2024-11-28 03:09:29 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 4a1cbf33c7 to dbbf93b1b3 2024-11-30 07:32:43 +01:00 Compare
kjuulh force-pushed cuddle-please/release from dbbf93b1b3 to 13e30721c6 2024-12-05 02:54:50 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 13e30721c6 to e00dcd353d 2024-12-07 02:53:37 +01:00 Compare
kjuulh force-pushed cuddle-please/release from e00dcd353d to 82b9b7f978 2024-12-11 06:45:41 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 82b9b7f978 to 1444874801 2024-12-29 02:51:47 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 1444874801 to 41d43172a0 2025-01-16 02:57:28 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 41d43172a0 to 05cd618b57 2025-01-22 02:56:41 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 05cd618b57 to 2fe1a81fea 2025-01-30 03:08:15 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 2fe1a81fea to e5a6eeca36 2025-02-07 02:56:56 +01:00 Compare
kjuulh force-pushed cuddle-please/release from e5a6eeca36 to 042d78c03f 2025-02-13 02:58:49 +01:00 Compare
kjuulh force-pushed cuddle-please/release from 042d78c03f to 984e127c5e 2025-02-15 02:51:42 +01:00 Compare
Some checks failed
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/pr Build is failing
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin cuddle-please/release:cuddle-please/release
git checkout cuddle-please/release
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/nodata#8
No description provided.
Delete Branch "cuddle-please/release"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?