Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content
Snippets Groups Projects
Select Git revision
  • 784-get-pyopal-opal-t-working
  • 794-multipolet-cleanup-and-placement
  • master default protected
  • 795-regression-test-broken-string-constant-duplicated
  • 793-outputplane
  • 792-opal-monitor-memory-usage
  • 790-opalringdefinition-max_r-min_r-options
  • OPAL-2023.1
  • 789-compile-error
  • 787-variablerf-ffa-and-offset-unify-units-internally
  • 786-unused-degrader-attributes
  • 788-pyopal-cmake-option
  • 780-regression-tests-broken
  • 785-h5-file-initialization
  • 783-define-amr-refinement-criteria-as-scoped-enum
  • 781-segmentation-fault-running-opal-cycl-with-boundary-geometry
  • 782-single-particle-simulation-gets-stuck
  • 779-no-lbal-output-file-with-enable_amr
  • 773-cyclotron-unify-units-internally
  • 765-momentum-tolerance-in-opal-t
  • OPAL-2022.1.0
  • OPAL-2021.1.0
  • OPAL-2.4.0
  • OPAL-2.2.1
  • OPAL-2.2.0
  • OPAL-21.11.2019
  • OPAL-2.0.2
  • OPAL-15-12-2018
  • OPAL-10-12-2018
  • OPAL-2.0.1
  • OPAL-2.0.0rc2
  • OPAL-2.0.0rc1
  • OPAL-1.6.2
  • OPAL-1.6.1
  • OPAL-1.6.0
  • OPAL-1.9.0
  • OPAL-1.5.2
  • OPAL-1.5.1
  • OPAL-1.4.0
  • OPAL-1.4.0rc3
40 results
Compare
Forked from OPAL / src
Source project has a limited visibility.
kraus's avatar
Merge branch '585-opal-t-fails-to-write-lossdatasink-if-executed-in-parallel-2' into 'master'
kraus authored 
Resolve "Opal-T fails to write LossDataSink if executed in parallel"

Closes #585

See merge request OPAL/src!439
a48c0f81
History
kraus's avatar a48c0f81
History
Name Last commit Last update