Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Databrowser buffer: No history refresh with Epics Archiver Appliance

Ouverte
  • Quelque chose ne va pas ?
#3,922 17 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
À clarifier
Activité
Active
Stack technique
java
Domaine
backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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!

Langage dominant
Java
Étoiles
130
Forks
132
Merge moyen
2 j 11 h
PR mergées (30 j)
19

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ControlSystemStudio/phoebus

Toutes les issues de ControlSystemStudio/phoebus

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.