bug(core/ui): missing date in device view from devices discovered by sync service #561
Labels
No labels
1week
2weeks
Failed compliance check
IP cameras
NATS
Possible security concern
Review effort 1/5
Review effort 2/5
Review effort 3/5
Review effort 4/5
Review effort 5/5
UI
aardvark
accessibility
amd64
api
arm64
auth
back-end
bgp
blog
bug
build
checkers
ci-cd
cleanup
cnpg
codex
core
dependencies
device-management
documentation
duplicate
dusk
ebpf
enhancement
eta 1d
eta 1hr
eta 3d
eta 3hr
feature
fieldsurvey
github_actions
go
good first issue
help wanted
invalid
javascript
k8s
log-collector
mapper
mtr
needs-triage
netflow
network-sweep
observability
oracle
otel
plug-in
proton
python
question
reddit
redhat
research
rperf
rperf-checker
rust
sdk
security
serviceradar-agent
serviceradar-agent-gateway
serviceradar-web
serviceradar-web-ng
siem
snmp
sysmon
topology
ubiquiti
wasm
wontfix
zen-engine
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
carverauto/serviceradar#561
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Imported from GitHub.
Original GitHub issue: #1765
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1765
Original created: 2025-10-14T23:05:07Z
Describe the bug
When the sync service initially runs and starts populating the database with devices learned from an integration, the DB is not getting populated with a good date. If the sweep service is configured and these devices eventually get updated/enriched with that data, we finally get a good date. After the next sync interval, the serviceradar-sync service will send us bad data again, which we override the good date with and then shows up as invalid until the sweep service update comes through with a correct update, and then the cycle continues.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.