Rebuild gumloop-celery on celery 5.6.3 (5.6.3+gumloop_0.2.0)

.bumpversion.cfg

@@ -0,0 +1,14 @@
+[bumpversion]
+current_version = 5.6.3
+commit = True
+tag = True
+parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(?P<releaselevel>[a-z\d]+)?
+serialize = 
+	{major}.{minor}.{patch}{releaselevel}
+	{major}.{minor}.{patch}
+
+[bumpversion:file:celery/__init__.py]
+
+[bumpversion:file:docs/includes/introduction.txt]
+
+[bumpversion:file:README.rst]

.dockerignore

@@ -0,0 +1,33 @@
+.DS_Store
+*.pyc
+*$py.class
+*~
+.*.sw[pon]
+dist/
+*.egg-info
+*.egg
+*.egg/
+*.eggs/
+build/
+.build/
+_build/
+pip-log.txt
+.directory
+erl_crash.dump
+*.db
+Documentation/
+.tox/
+.ropeproject/
+.project
+.pydevproject
+.idea/
+.coverage
+celery/tests/cover/
+.ve*
+cover/
+.vagrant/
+.cache/
+htmlcov/
+coverage.xml
+test.db
+.git/

.editorconfig

@@ -0,0 +1,15 @@
+# http://editorconfig.org
+
+root = true
+
+[*]
+indent_style = space
+indent_size = 4
+trim_trailing_whitespace = true
+insert_final_newline = true
+charset = utf-8
+end_of_line = lf
+max_line_length = 117
+
+[Makefile]
+indent_style = tab

.github/FUNDING.yml

@@ -0,0 +1,8 @@
+# These are supported funding model platforms
+
+github: celery
+patreon:
+open_collective: celery
+ko_fi: # Replace with a single Ko-fi username
+tidelift: "pypi/celery"
+custom: # Replace with a single custom sponsorship URL

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,4 @@
+<!--
+Please use one of our issue templates.
+We reserve the right to close bug reports or feature requests who don't use our templates.
+-->

.github/ISSUE_TEMPLATE/Bug-Report.md

@@ -0,0 +1,166 @@
+---
+name: Bug Report
+about: Is something wrong with Celery?
+title: ''
+labels: 'Issue Type: Bug Report'
+assignees: ''
+
+---
+
+<!--
+Please fill this template entirely and do not erase parts of it.
+We reserve the right to close without a response
+bug reports which are incomplete.
+-->
+# Checklist
+<!--
+To check an item on the list replace [ ] with [x].
+-->
+- [ ] I have verified that the issue exists against the `main` branch of Celery.
+- [ ] This has already been asked to the [discussions forum](https://github.com/celery/celery/discussions) first.
+- [ ] I have read the relevant section in the
+  [contribution guide](https://docs.celeryq.dev/en/main/contributing.html#other-bugs)
+  on reporting bugs.
+- [ ] I have checked the [issues list](https://github.com/celery/celery/issues?q=is%3Aissue+label%3A%22Issue+Type%3A+Bug+Report%22+-label%3A%22Category%3A+Documentation%22)
+  for similar or identical bug reports.
+- [ ] I have checked the [pull requests list](https://github.com/celery/celery/pulls?q=is%3Apr+label%3A%22PR+Type%3A+Bugfix%22+-label%3A%22Category%3A+Documentation%22)
+  for existing proposed fixes.
+- [ ] I have checked the [commit log](https://github.com/celery/celery/commits/main)
+  to find out if the bug was already fixed in the main branch.
+- [ ] I have included all related issues and possible duplicate issues
+  in this issue (If there are none, check this box anyway).
+- [ ] I have tried to reproduce the issue with [pytest-celery](https://docs.celeryq.dev/projects/pytest-celery/en/latest/userguide/celery-bug-report.html) and added the reproduction script below.
+
+## Mandatory Debugging Information
+
+- [ ] I have included the output of ``celery -A proj report`` in the issue.
+    (if you are not able to do this, then at least specify the Celery
+     version affected).
+- [ ] I have verified that the issue exists against the `main` branch of Celery.
+- [ ] I have included the contents of ``pip freeze`` in the issue.
+- [ ] I have included all the versions of all the external dependencies required
+  to reproduce this bug.
+
+## Optional Debugging Information
+<!--
+Try some of the below if you think they are relevant.
+It will help us figure out the scope of the bug and how many users it affects.
+-->
+- [ ] I have tried reproducing the issue on more than one Python version
+  and/or implementation.
+- [ ] I have tried reproducing the issue on more than one message broker and/or
+  result backend.
+- [ ] I have tried reproducing the issue on more than one version of the message
+  broker and/or result backend.
+- [ ] I have tried reproducing the issue on more than one operating system.
+- [ ] I have tried reproducing the issue on more than one workers pool.
+- [ ] I have tried reproducing the issue with autoscaling, retries,
+  ETA/Countdown & rate limits disabled.
+- [ ] I have tried reproducing the issue after downgrading
+  and/or upgrading Celery and its dependencies.
+
+## Related Issues and Possible Duplicates
+<!--
+Please make sure to search and mention any related issues
+or possible duplicates to this issue as requested by the checklist above.
+
+This may or may not include issues in other repositories that the Celery project
+maintains or other repositories that are dependencies of Celery.
+
+If you don't know how to mention issues, please refer to Github's documentation
+on the subject: https://help.github.com/en/articles/autolinked-references-and-urls#issues-and-pull-requests
+-->
+
+#### Related Issues
+
+- None
+
+#### Possible Duplicates
+
+- None
+
+## Environment & Settings
+<!-- Include the contents of celery --version below -->
+**Celery version**:
+<!-- Include the output of celery -A proj report below -->
+<details>
+<summary><b><code>celery report</code> Output:</b></summary>
+<p>
+
+```
+```
+
+</p>
+</details>
+
+# Steps to Reproduce
+
+## Required Dependencies
+<!-- Please fill the required dependencies to reproduce this issue -->
+- **Minimal Python Version**: N/A or Unknown
+- **Minimal Celery Version**: N/A or Unknown
+- **Minimal Kombu Version**: N/A or Unknown
+- **Minimal Broker Version**: N/A or Unknown
+- **Minimal Result Backend Version**: N/A or Unknown
+- **Minimal OS and/or Kernel Version**: N/A or Unknown
+- **Minimal Broker Client Version**: N/A or Unknown
+- **Minimal Result Backend Client Version**: N/A or Unknown
+
+### Python Packages
+<!-- Please fill the contents of pip freeze below -->
+<details>
+<summary><b><code>pip freeze</code> Output:</b></summary>
+<p>
+
+```
+```
+
+</p>
+</details>
+
+### Other Dependencies
+<!--
+Please provide system dependencies, configuration files
+and other dependency information if applicable
+-->
+<details>
+<p>
+N/A
+</p>
+</details>
+
+## Minimally Reproducible Test Case
+<!--
+Please provide a reproducible test case.
+Refer to the Reporting Bugs section in our contribution guide.
+
+We prefer submitting test cases in the form of a PR to our integration test suite.
+If you can provide one, please mention the PR number below.
+If not, please attach the most minimal code example required to reproduce the issue below.
+If the test case is too large, please include a link to a gist or a repository below.
+
+Alternatively, the pytest-celery plugin can be used to create standalone reproduction scripts
+that can be added to this report. See the pytest-celery documentation for more information at
+pytest-celery.readthedocs.io
+-->
+
+<details>
+<p>
+
+```python
+```
+
+</p>
+</details>
+
+# Expected Behavior
+<!-- Describe in detail what you expect to happen -->
+
+# Actual Behavior
+<!--
+Describe in detail what actually happened.
+Please include a backtrace and surround it with triple backticks (```).
+In addition, include the Celery daemon logs, the broker logs,
+the result backend logs and system logs below if they will help us debug
+the issue.
+-->

.github/ISSUE_TEMPLATE/Documentation-Bug-Report.md

@@ -0,0 +1,56 @@
+---
+name: Documentation Bug Report
+about: Is something wrong with our documentation?
+title: ''
+labels: 'Category: Documentation, Issue Type: Bug Report'
+assignees: ''
+
+---
+
+<!--
+Please fill this template entirely and do not erase parts of it.
+We reserve the right to close without a response
+bug reports which are incomplete.
+-->
+# Checklist
+<!--
+To check an item on the list replace [ ] with [x].
+-->
+
+- [ ] I have checked the [issues list](https://github.com/celery/celery/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3A%22Category%3A+Documentation%22+)
+  for similar or identical bug reports.
+- [ ] I have checked the [pull requests list](https://github.com/celery/celery/pulls?q=is%3Apr+label%3A%22Category%3A+Documentation%22)
+  for existing proposed fixes.
+- [ ] I have checked the [commit log](https://github.com/celery/celery/commits/main)
+  to find out if the bug was already fixed in the main branch.
+- [ ] I have included all related issues and possible duplicate issues in this issue
+      (If there are none, check this box anyway).
+
+## Related Issues and Possible Duplicates
+<!--
+Please make sure to search and mention any related issues
+or possible duplicates to this issue as requested by the checklist above.
+
+This may or may not include issues in other repositories that the Celery project
+maintains or other repositories that are dependencies of Celery.
+
+If you don't know how to mention issues, please refer to Github's documentation
+on the subject: https://help.github.com/en/articles/autolinked-references-and-urls#issues-and-pull-requests
+-->
+
+#### Related Issues
+
+- None
+
+#### Possible Duplicates
+
+- None
+
+# Description
+<!--
+Please describe what's missing or incorrect about our documentation.
+Include links and/or screenshots which will aid us to resolve the issue.
+-->
+
+# Suggestions
+<!-- Please provide us suggestions for how to fix the documentation -->

.github/ISSUE_TEMPLATE/Enhancement.md

@@ -0,0 +1,94 @@
+---
+name: Enhancement
+about: Do you want to improve an existing feature?
+title: ''
+labels: 'Issue Type: Enhancement'
+assignees: ''
+
+---
+
+<!--
+Please fill this template entirely and do not erase parts of it.
+We reserve the right to close without a response
+enhancement requests which are incomplete.
+-->
+# Checklist
+<!--
+To check an item on the list replace [ ] with [x].
+-->
+
+- [ ] I have checked the [issues list](https://github.com/celery/celery/issues?q=is%3Aissue+label%3A%22Issue+Type%3A+Enhancement%22+-label%3A%22Category%3A+Documentation%22)
+  for similar or identical enhancement to an existing feature.
+- [ ] I have checked the [pull requests list](https://github.com/celery/celery/pulls?q=is%3Apr+label%3A%22Issue+Type%3A+Enhancement%22+-label%3A%22Category%3A+Documentation%22)
+  for existing proposed enhancements.
+- [ ] I have checked the [commit log](https://github.com/celery/celery/commits/main)
+  to find out if the same enhancement was already implemented in the
+  main branch.
+- [ ] I have included all related issues and possible duplicate issues in this issue
+      (If there are none, check this box anyway).
+
+## Related Issues and Possible Duplicates
+<!--
+Please make sure to search and mention any related issues
+or possible duplicates to this issue as requested by the checklist above.
+
+This may or may not include issues in other repositories that the Celery project
+maintains or other repositories that are dependencies of Celery.
+
+If you don't know how to mention issues, please refer to Github's documentation
+on the subject: https://help.github.com/en/articles/autolinked-references-and-urls#issues-and-pull-requests
+-->
+
+#### Related Issues
+
+- None
+
+#### Possible Duplicates
+
+- None
+
+# Brief Summary
+<!--
+Please include a brief summary of what the enhancement is
+and why it is needed.
+-->
+
+# Design
+
+## Architectural Considerations
+<!--
+If more components other than Celery are involved,
+describe them here and the effect it would have on Celery.
+-->
+None
+
+## Proposed Behavior
+<!--
+Please describe in detail how this enhancement is going to change the behavior
+of an existing feature.
+Describe what happens in case of failures as well if applicable.
+-->
+
+## Proposed UI/UX
+<!--
+Please provide your ideas for the API, CLI options,
+configuration key names etc. that will be adjusted for this enhancement.
+-->
+
+## Diagrams
+<!--
+Please include any diagrams that might be relevant
+to the implementation of this enhancement such as:
+* Class Diagrams
+* Sequence Diagrams
+* Activity Diagrams
+You can drag and drop images into the text box to attach them to this issue.
+-->
+N/A
+
+## Alternatives
+<!--
+If you have considered any alternative implementations
+describe them in detail below.
+-->
+None