Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: openebs/mayastor
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.9.1
Choose a base ref
...
head repository: openebs/mayastor
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.9.2
Choose a head ref
  • 4 commits
  • 5 files changed
  • 3 contributors

Commits on Aug 8, 2025

  1. chore: spdk-rs submodule update

    Signed-off-by: Diwakar Sharma <diwakar.sharma@datacore.com>
    dsharma-dc committed Aug 8, 2025
    Configuration menu
    Copy the full SHA
    dd100ac View commit details
    Browse the repository at this point in the history

Commits on Aug 11, 2025

  1. Merge #1891

    1891: chore: spdk-rs submodule update r=dsharma-dc a=dsharma-dc
    
    
    
    Co-authored-by: Diwakar Sharma <diwakar.sharma@datacore.com>
    mayastor-bors and dsharma-dc committed Aug 11, 2025
    Configuration menu
    Copy the full SHA
    2ef980b View commit details
    Browse the repository at this point in the history

Commits on Aug 20, 2025

  1. fix: exit with error if gRPC port is busy

    By default, the panic behaviour is to unwind, meaning we don't exit.
    In case we fail to even start gRPC we should exit, as there's nothing
    to do.
    
    In this commit, we now internally raise a signal SIGUSR1 which then
    triggers the shutdown of the reactor et all.
    
    todo:
    We should also consider catching any panic and do the same, or is
    there any case where we'd want to unwind and remain running?
    
    Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
    tiagolobocastro committed Aug 20, 2025
    Configuration menu
    Copy the full SHA
    b80aaa9 View commit details
    Browse the repository at this point in the history
  2. Merge #1901

    1901: fix: exit with error if gRPC port is busy r=tiagolobocastro a=tiagolobocastro
    
    By default, the panic behaviour is to unwind, meaning we don't exit. In case we fail to even start gRPC we should exit, as there's nothing to do.
    
    In this commit, we now internally raise a signal SIGUSR1 which then triggers the shutdown of the reactor et all.
    
    todo:
    We should also consider catching any panic and do the same, or is there any case where we'd want to unwind and remain running?
    
    Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
    mayastor-bors and tiagolobocastro committed Aug 20, 2025
    Configuration menu
    Copy the full SHA
    c94de54 View commit details
    Browse the repository at this point in the history
Loading