Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
N
notifications-routing
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Notifications project
notifications-routing
Merge requests
!21
Error occurred when fetching sidebar data
[
#21
] Manual ack/nack implementation
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
[
#21
] Manual ack/nack implementation
21-implement-manual-ack-nack
into
master
Overview
1
Commits
3
Pipelines
7
Changes
3
Merged
Dimitra Chatzichrysou
requested to merge
21-implement-manual-ack-nack
into
master
4 years ago
Overview
1
Commits
3
Pipelines
7
Changes
3
Expand
Changes:
Set connections attribute inside the listerer in
__init__.py
Create ack_message/nack_message in
router.py
Update
read_message
method to get message id from message body on
router.py
Update
on_message
method on
router.py
to reflect these changes
Closes
#21 (closed)
Edited
4 years ago
by
Dimitra Chatzichrysou
0
0
Merge request reports
Activity
All activity
Filter activity
Deselect all
Approvals
Assignees & reviewers
Comments (from bots)
Comments (from users)
Commits & branches
Edits
Labels
Lock status
Mentions
Merge request status
Tracking
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Loading
Please
register
or
sign in
to reply
There was an error fetching the pipelines. Try again in a few moments or contact your support team.
Loading
