DUNE-DAQ / DUNE-DAQ/connectivityserver

[Feature]: Discussion - should we be able to validate what session IDs are in use?

Open
#28 0 comments 0 reactions 1 assignee View on GitHub

@PawelPlesniak is already working on this.

Since Mar 19, 2026.

enhancement
Dominant language
Python
Stars
0
Forks
1
Avg merge
5m
Merged PRs (30d)
2

Description

Description

When testing running two test sessions at the same time, they were both using the EHN1 connectivity service. As such, when I used the same session name in both configs (testsession in both cases)

# In shell 1
drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml ehn1-local-1x1-config testsession
# In shell 2
drunc-unified-shell ssh-standalone config/daqsystemtest/example-configs.data.xml ehn1-local-1x1-config testsession

The second session connected to the applications running from the first session. A simple flask endpoint to verify that the session name is unused could be useful.

Note - for FD, this is intended to be handled by the session manager, but this safety catch would be helpful too.

Potential impact radius

Small/Isolated

Reason for change

Session safety.

Suggested implementations

No response

Testing suggestions

No response

Anything else?

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.