Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Databrowser buffer: No history refresh with Epics Archiver Appliance

Offen
  • Stimmt etwas nicht?
#3,922 17 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
backend

Rechercherichtung

Start by checking how the databrowser uses org.csstudio.trends.databrowser3/automatic_history_refresh and how it transitions from the live buffer to historical data from EPICS Archiver Appliance. Reproduce the reported behavior with the settings described in the issue and compare the red plot with a newly added green plot. Done means the existing plot continues retrieving archived data instead of flatlining when older data leaves the live buffer.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Hello,

I'm researching an issue with our databrowser in combination with Epics Archiver Appliance, but until now, to no avail. Please take a look at the following screenshot. It displays twice the same plot. The red plot is running for a while, the green plot has been added a couple of moments before the screenshot has been made.

Image

As you can see, the red plot fails to retrieve data from the Archiver beyond the live buffer. At a certain point in time, the plot flatlines. As new data comes in, old data falls out. The starting point of the flatline never shifts, except when increasing or decreasing the buffer. When changing the buffer, as expected, the observable amount of live data increases or decreases aswell. The green plot, on the other hand, demonstrates that the data has been correctly archived and can, in principle, be accessed by the databrowser.

I was very glad to discover

org.csstudio.trends.databrowser3/automatic_history_refresh = true

convinced that this will solve the issue, but in fact, it did not change the behavior.

These are the settings I use:

Image

There is no firewall involved, neither on the archivers side nor on the side of Phoebus.

A look at this last screenshot confirms that the point in time where both plots start flatlining is in sync, further confirming that the issue seems to be with the transition from live buffer to historical data.

Image

I'd love to here your ideas what could be a reason for this issue and what a possible solution might look like!

Kind regards!

Vorherrschende Sprache
Java
Sterne
130
Forks
132
Ø Merge
2 T. 11 Std.
Gemergte PRs (30 T.)
19

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ControlSystemStudio/phoebus

Alle Issues in ControlSystemStudio/phoebus

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.