Skip to content

active 2024-01-042024-01-11 (UTC)

Partial coverage20,147 / 25,876 hourly files (78%) · 2 absent upstream · 5,726 failed, retryable2023-08-302026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
15
Pushes
1
Pull requests
3
Issues
4
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 8 days from 2024-01-04 to 2024-01-11. Pushes: 1 total, peak 1 in a day. Pull requests: 3 total, peak 2 in a day. Issues: 4 total, peak 2 in a day. Comments: 3 total, peak 3 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
karimra6130
henderiw5003

Recent activity

Latest issues, pull requests and releases

  • Pull request#60karimra2024-01-11 01:27
  • Issue#59karimra2024-01-10 22:15
    Support both gNMI and netconf at the same time for a datastore
  • Issue#55karimra2024-01-10 01:18
    Add a ttlcache to the remote schema client
  • Issue comment#37henderiw2024-01-08 22:59
    Do we need a way (RPC) to manually trigger a sync ?
  • Issue comment#39henderiw2024-01-08 22:49
    Reflect target reachability state in the RPC response
  • Issue#40henderiw2024-01-08 22:34
    reflect back what the data-server sends southbound in the SetIntentResponse
  • Issue comment#40henderiw2024-01-08 22:33
    reflect back what the data-server sends southbound in the SetIntentResponse
  • Pull request#46karimra2024-01-05 19:51
  • Pull request#46karimra2024-01-05 19:49
  • Issue#45henderiw2024-01-04 17:29
    When creating a datastore with a - in the name of the referenced schema; the lookup to the schema fails

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.