Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

this TBOMB UPDATE #462

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

thegreatpayload
Copy link

@thegreatpayload thegreatpayload commented Feb 16, 2024

Description

NOTE: For the PR to be reviewed it is compulsory to mention the reviewed issue.
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.

Fixes:

  • Mention issue using #

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration.

Checklist:

  • This PR fixes a reviewed issue.(If not create an issue first)
  • This PR points to dev branch
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have checked my code and corrected any misspellings

@0n1cOn3
Copy link
Contributor

0n1cOn3 commented Mar 3, 2024

This PR looks good.
But theres a minor issue:
TBomb doesnt support Python 3.10. Only supports up to 3.9.

@SOHAM-HIGHBOT
Copy link

Description

NOTE: For the PR to be reviewed it is compulsory to mention the reviewed issue.
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.

Fixes:

  • Mention issue using #

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration.

Checklist:

  • This PR fixes a reviewed issue.(If not create an issue first)
  • This PR points to dev branch
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have checked my code and corrected any misspellings

Some times the code wasn't work as well fix soon

@0n1cOn3
Copy link
Contributor

0n1cOn3 commented Mar 8, 2024

Description

NOTE: For the PR to be reviewed it is compulsory to mention the reviewed issue.
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.

Fixes:

  • Mention issue using #

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration.

Checklist:

  • This PR fixes a reviewed issue.(If not create an issue first)
  • This PR points to dev branch
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have checked my code and corrected any misspellings

Some times the code wasn't work as well fix soon

Ehh, this is a complete different story. Create a new issue tab for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants