Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • tezos tezos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,213
    • Issues 1,213
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 185
    • Merge requests 185
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Tezos
  • tezostezos
  • Merge requests
  • !5078

toru: prevent depositing/withdraw tickets with 0 quantity

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Sylvain R. requested to merge nomadic-labs/tezos:sylvain@tx_rollup@prevent_0_amount_tickets into master Apr 20, 2022
  • Overview 21
  • Commits 1
  • Pipelines 10
  • Changes 3

Context

There is a possibility to deposit/withdraw 0 tickets currently. This fixes by checking the deposit/dispatch and tranfer tickets that it is not possible to uses them with amount 0

Manually testing the MR

Checklist

  • Document the interface of any function added or modified (see the coding guidelines)
  • Document any change to the user interface, including configuration parameters (see node configuration)
  • Provide automatic testing (see the testing guide).
  • For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR
Edited Apr 21, 2022 by Sylvain R.
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: sylvain@tx_rollup@prevent_0_amount_tickets