bec/csaxs_bec
0
0
Fork 1
Code Issues 13 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

sastt_config #117

Merged
appel_c merged 3 commits from sastt_config into main 2026-01-05 09:16:12 +01:00
Conversation 3 Commits 3 Files Changed 2 +101 -5
appel_c commented 2025-12-11 07:24:05 +01:00
Owner
Copy Link

PR with a sastt config

PR with a sastt config
appel_c added 2 commits 2025-12-11 07:24:06 +01:00
new yaml file sastt for sastt setup
All checks were successful
CI for csaxs_bec / test (push) Successful in 1m24s
Details
34d055c9c6
add micfoc and change some motor settings
Some checks failed
CI for csaxs_bec / test (push) Failing after 1m18s
Details
CI for csaxs_bec / test (pull_request) Failing after 57s
Details
8784ae7073
appel_c added 1 commit 2025-12-11 07:50:13 +01:00
refactor(configs):Migrate deviceClass for EpicsMotorEX to EpicsUserMotorVME
Some checks failed
CI for csaxs_bec / test (pull_request) Failing after 57s
Details
CI for csaxs_bec / test (push) Failing after 1m0s
Details
a00273c472
appel_c force-pushed sastt_config from a00273c472 to d99b44b619 2025-12-11 07:53:06 +01:00 Compare
appel_c requested review from diaz 2025-12-11 08:07:23 +01:00
appel_c requested review from wakonig_k 2025-12-11 08:07:23 +01:00
diaz commented 2025-12-11 08:18:10 +01:00
Member
Copy Link

It's funny because I don't remember having changed the original bec_device_config_sastt.yaml config file... It seems the device ophyd has been updated there... But I guess that's OK. I wonder who did that change in my branch... In any case what I care about is the sastt.yaml and that one is fine for sure, so we can merge

It's funny because I don't remember having changed the original bec_device_config_sastt.yaml config file... It seems the device ophyd has been updated there... But I guess that's OK. I wonder who did that change in my branch... In any case what I care about is the sastt.yaml and that one is fine for sure, so we can merge
diaz commented 2025-12-11 08:19:18 +01:00
Member
Copy Link

We need o make a cleanup of yaml files. I will meet Andreas and Mirko to agree on a strategy and we will then do it

We need o make a cleanup of yaml files. I will meet Andreas and Mirko to agree on a strategy and we will then do it
appel_c commented 2025-12-11 08:28:16 +01:00
Author
Owner
Copy Link

It's funny because I don't remember having changed the original bec_device_config_sastt.yaml config file... It seems the device ophyd has been updated there... But I guess that's OK. I wonder who did that change in my branch... In any case what I care about is the sastt.yaml and that one is fine for sure, so we can merge

Hi Ana,
this change was added by me. I committed the adjustment for the changes I made to your PR. Sorry in case this confused you

Screenshot 2025-12-11 at 08.28.01.png

> It's funny because I don't remember having changed the original bec_device_config_sastt.yaml config file... It seems the device ophyd has been updated there... But I guess that's OK. I wonder who did that change in my branch... In any case what I care about is the sastt.yaml and that one is fine for sure, so we can merge Hi Ana, this change was added by me. I committed the adjustment for the changes I made to your PR. Sorry in case this confused you ![Screenshot 2025-12-11 at 08.28.01.png](/attachments/baaff481-97c6-4599-a671-5c839546e468)
Screenshot 2025-12-11 at 08.28.01.png
59 KiB
👍 1
appel_c merged commit d99b44b619 into main 2026-01-05 09:16:12 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
diaz
wakonig_k
Labels
Clear labels
issue::not confirmed
Used if an issue has not yet been confirmed by a developer
 issue::not reproducible
Used if an issue is not reproducible
 issue::reproducible
Used if a developer was able to reproduce the issue
 priority::critical
Should be done as soon as possible
 priority::needed
An important update to the code base
 priority::nice to have
Not really needed but a good improvement
 scope::backend
An issue regarding the backend services
 scope::frontend
An issue regarding the user-facing services
 stage::in development
This issue is currently being worked on
 stage::on hold
Something is blocking the development
 stage::pre_release
For issues that have been merged into a pre-release branch and are waiting for their release.
stage::ready for review
For issues that have been resolved and are ready for review
 stage::selected for development
This issue has been selected for development but has not been scheduled yet
 stage::weekly backlog
This issue has been selected for development for the next development cycle
 type::bug
It's a bug!
 type::discussion
A discussion is wanted/needed
 type::doc
Improvements to the documentation
 type::feature
A new feature
 type::improvement
Neither a feature nor a bug but an improvement to the code base
 type::test
Missing tests or improvements to the test suite
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acerbo_a appel_c bec_bl_push-gitea bec-gitea celcer_t debenjak_l diaz divall_e guizar_m holler lombosi_c menzel perl_d stubbs_s usov_i wakonig_k wang_x1 wyzula_j zamofing_t
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bec/csaxs_bec#117
Delete Branch "sastt_config"

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?