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

Add AIA workflow to automate MSI/EXE binary creation #50

Closed
3 tasks done
DefinetlyNotAI opened this issue Sep 2, 2024 · 0 comments · Fixed by #52
Closed
3 tasks done

Add AIA workflow to automate MSI/EXE binary creation #50

DefinetlyNotAI opened this issue Sep 2, 2024 · 0 comments · Fixed by #52
Assignees
Labels
progress/Won't Fix This will not be worked on, further info will be added to why. request/Important New feature or request, top priority, for next update type/System Related to System Code for Logicytics
Milestone

Comments

@DefinetlyNotAI
Copy link
Owner

Prerequisites

Proposal

Use this to add workflow bot

Motivation and context

No response

What is the importance for implementing this idea?

High

@DefinetlyNotAI DefinetlyNotAI self-assigned this Sep 2, 2024
@DefinetlyNotAI DefinetlyNotAI added the request/Important New feature or request, top priority, for next update label Sep 2, 2024
@DefinetlyNotAI DefinetlyNotAI moved this to Todo in Issue Board Sep 2, 2024
@DefinetlyNotAI DefinetlyNotAI moved this from Todo to In Progress in Issue Board Sep 2, 2024
DefinetlyNotAI added a commit that referenced this issue Sep 2, 2024
### Description

<!-- Describe your changes in detail -->

### Motivation & Context

<!-- Why is this change required? What problem does it solve? -->

### Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Refactoring (non-breaking change)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] My change introduces changes to the documentation (only docs are
affected)

### Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md)
- [x] I have updated the documentation accordingly
- [ ] I have added tests to cover my changes, and they have passed
- [ ] I have tested my code with the `--dev` flag
- [ ] I have followed the instructions in the `--dev` flag
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki)

### Related issues

#50
DefinetlyNotAI added a commit that referenced this issue Sep 2, 2024
DefinetlyNotAI added a commit that referenced this issue Sep 2, 2024
DefinetlyNotAI added a commit that referenced this issue Sep 2, 2024
DefinetlyNotAI added a commit that referenced this issue Sep 2, 2024
@DefinetlyNotAI DefinetlyNotAI linked a pull request Sep 2, 2024 that will close this issue
11 tasks
DefinetlyNotAI added a commit that referenced this issue Sep 2, 2024
### Description

Fixing #50 and implementing #26 

### Motivation & Context

LOL

### Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Refactoring (non-breaking change)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] My change introduces changes to the documentation (only docs are
affected)

### Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md)
- [x] I have updated the documentation accordingly
- [ ] I have added tests to cover my changes, and they have passed
- [ ] I have tested my code with the `--dev` flag
- [ ] I have followed the instructions in the `--dev` flag
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki)

### Related issues
#50 and #26
@DefinetlyNotAI DefinetlyNotAI reopened this Sep 2, 2024
@DefinetlyNotAI DefinetlyNotAI added progress/Won't Fix This will not be worked on, further info will be added to why. and removed WIP labels Sep 2, 2024
@DefinetlyNotAI DefinetlyNotAI moved this from In Progress to Rejected / Duplicate in Issue Board Sep 2, 2024
DefinetlyNotAI added a commit that referenced this issue Sep 2, 2024
body:
  - type: checkboxes
    attributes:
      label: Prerequisites
description: Take a couple minutes to help our maintainers work faster
by checking of the pre-requisites.
      options:
- label: I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
          required: true
- label: I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
          required: true
- label: I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
          required: true
- label: I have updated the documentation accordingly, if required (If
not leave this unchecked)
          required: false
- label: I have added tests to cover my changes, and they have passed,
if required (If not leave this unchecked)
          required: false
- label: I have tested my code with the `--dev` flag, if required (If
not leave this unchecked)
          required: false
- label: I have followed the instructions in the `--dev` flag, if
required (If not leave this unchecked)
          required: false
  - type: checkboxes
    attributes:
      label: PR_Type
description: Take a couple minutes to help our maintainers work faster
by telling us what is the PR guided on.
      options:
        - label: Bug fix (non-breaking change which fixes an issue)
          required: false
- label: New feature (non-breaking change which adds functionality)
          required: false
        - label: Refactoring (non-breaking change)
          required: false
- label: Breaking change (fix or feature that would change existing
functionality)
          required: false
- label: My change introduces changes to the documentation (only docs
are affected)
  - type: textarea
    id: description
    attributes:
      label: Describe the PR
description: Provide a summary of the pr and what you expected to
happen.
    validations:
      required: true
  - type: textarea
    id: motivation-context
    attributes:
      label: Motivation and Context
      description: Why is this PR required? What problem does it solve?
    validations:
      required: true
  - type: input
    id: issues
    attributes:
      label: What issues will be fixed?
placeholder: "Please link any related issues here. Give them in this
format `#50, #23` etc"
    validations:
      required: true
@DefinetlyNotAI DefinetlyNotAI closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2024
@DefinetlyNotAI DefinetlyNotAI added the type/System Related to System Code for Logicytics label Sep 18, 2024
DefinetlyNotAI added a commit that referenced this issue Sep 24, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [ ] I have added tests to cover my changes, and they have passed, if
required.
- [ ] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [ ] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [ ] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

AIP now is faster by ~50% by making builds able to be duo-build on exe
and msi - So from 8 separate build, to 4 separate builds

### Motivation and Context

To increase development speed

### Binaries

<!-- If you have any binaries built from the AIP, Upload them here -->
<!-- OPTIONAL for patch updates - To leave empty just type _N/A_ -->
Already linked

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

_N/A_

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->

_N/A_
DefinetlyNotAI added a commit that referenced this issue Oct 28, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [ ] I have updated the documentation accordingly, if required.
- [ ] I have added tests to cover my changes, and they have passed, if
required.
- [ ] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [ ] New feature <!-- Non-Breaking Change that adds a new feature -->
- [ ] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

Fixed some issues, deprecated website, made minor changes

### Motivation and Context

Bug issues, and security vulnerabilities

### Binaries

<!-- If you have any binaries built from the AIP, Upload them here -->
<!-- OPTIONAL for patch updates - To leave empty just type _N/A_ -->

_N/A_

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->
_N/A_
<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
[Security Advisory
GHSA-5wvr-vvqf-668m](GHSA-5wvr-vvqf-668m)
DefinetlyNotAI added a commit that referenced this issue Nov 11, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [ ] I have added tests to cover my changes, and they have passed, if
required.
- [ ] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [ ] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [ ] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [x] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

Removed deprecated website

### Motivation and Context

This will allow us to get the GOLD SSF badge

### Binaries

<!-- If you have any binaries built from the AIP, Upload them here -->
<!-- OPTIONAL for patch updates - To leave empty just type _N/A_ -->

_N/A_

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->

_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->

_N/A_
DefinetlyNotAI added a commit that referenced this issue Nov 12, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [ ] I have added tests to cover my changes, and they have passed, if
required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [x] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
Just update 2.4.0 - too many things, so check the commit history

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
To make it easier to use, and more widely accepted

### Binaries

<!-- If you have any binaries built from the AIP, Upload them here -->
<!-- OPTIONAL for patch updates - To leave empty just type _N/A_ -->
I have deprecated this.

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->

_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_
DefinetlyNotAI added a commit that referenced this issue Nov 13, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [x] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->

Ehh, fixed bugs that made half of the program not run

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->

Many minor and major bugs

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->

_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->

_N/A_
DefinetlyNotAI added a commit that referenced this issue Nov 20, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [ ] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
Just did part of the PLANS.md

Refactored redocumented some code, and optimised imports as well as
fixed a minor bug

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
Part of the PLANS.md

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_
DefinetlyNotAI added a commit that referenced this issue Nov 21, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [ ] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
Added a new `log.function` decorator, this allows to debug time run by a
function as well as debug the function name for development purposes,
also fixed minor bugs and removed redundant feature

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
Solves plans and fixes minor bugs

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_
DefinetlyNotAI added a commit that referenced this issue Nov 25, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [x] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
Added new tools, tested code AND fixed minor bugs

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
For the plans.md - v2.5.0

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
 _N/A_
### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
 _N/A_
DefinetlyNotAI added a commit that referenced this issue Dec 6, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [ ] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [ ] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [x] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
Made v3, incorporated many features, more on this in a comment
coderabbit will add.

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
To migrate to v3 and test my abilities

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced a packet sniffing application that captures and logs
network packets.
	- Added functionality for backing up Windows registry and media files.
- Implemented sensitive data mining capabilities for file searching and
copying.
- Enhanced scanning for sensitive content using machine learning models.

- **Bug Fixes**
- Improved error handling and logging across various scripts for better
clarity on execution flow.

- **Documentation**
- Updated README and PLANS files to reflect changes in configuration and
project structure.
- Revised SECURITY and requirements documentation to clarify supported
versions and dependencies.

- **Chores**
- Removed deprecated configuration file and Docker-related files to
streamline the project.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
DefinetlyNotAI added a commit that referenced this issue Dec 11, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [ ] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
CodeRabbit will supply this

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
To maintain v3
### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced a framework for visualizing neural network models and their
features.
	- Added functionality to capture and log system memory information.
- Enhanced scanning functionality for files and directories for
sensitive content.
- Added new entries to the `.gitignore` file for improved file
management.
- Implemented a global locking mechanism for thread safety during model
and vectorizer usage.
	- Added a new section in the configuration file for study parameters.

- **Bug Fixes**
	- Improved error handling and logging in various scripts.

- **Documentation**
- Updated documentation for VulnScan to include new repository details
and resources.
	- Enhanced the `README.md` for better clarity and usability.

- **Chores**
- Updated configuration file to reflect new settings for model and
vectorizer paths.
- Modified `requirements.txt` to add and remove several package
dependencies.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
DefinetlyNotAI added a commit that referenced this issue Dec 12, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [ ] I have updated the documentation accordingly, if required.
- [ ] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [ ] New feature <!-- Non-Breaking Change that adds a new feature -->
- [ ] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
Rem torch from requirements due to Dependabot support'

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
Fixes GH action @dependabot

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Removed the dependency on `torch` version `2.5.1+cu124` from the
project requirements.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
DefinetlyNotAI added a commit that referenced this issue Dec 16, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

Retrieves and logs detailed information about Bluetooth devices on the
system.

The function connects to the Windows Management Instrumentation (WMI)
service and queries for devices
whose names contain the term 'Bluetooth'. It writes the information to a
text file named 'Bluetooth Info.txt'.

    Information for each device includes:
    - Name
    - Device ID
    - Description
    - Manufacturer
    - Status
    - PNP Device ID

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->

### Motivation and Context

I thought that giving logicytics bluetooth capabilities would be a
really good addition.

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced a script to retrieve and log detailed information about
Bluetooth devices on Windows.
- Added functionality for collecting and logging Bluetooth-related data,
including paired devices and event logs.

- **Bug Fixes**
	- Enhanced error handling and logging in packet sniffing functionality.

- **Chores**
	- Updated version number in configuration file.
	- Modified dependencies in requirements by adding new packages.
	- Excluded virtual environment folder from project configuration.
- Assigned code ownership for `bluetooth_details.py` and
`bluetooth_logger.py`.
- Updated documentation to reflect new Bluetooth data handling
capabilities.
	- Removed outdated CSV editor configuration file.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
DefinetlyNotAI added a commit that referenced this issue Dec 18, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [ ] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [ ] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

This pull request includes several changes to the `CODE/_debug.py` and
`CODE/logicytics/Checks.py` files to improve logging and refactor code.
The most significant changes involve modifying methods to use logging
instead of returning status messages, adding new methods for checking
Python version and execution policy, and removing the return of status
messages from several methods.

#### Logging improvements:
*
[`CODE/_debug.py`](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L6-L36):
Modified the `HealthCheck.check_files`, `HealthCheck.compare_versions`,
and `DebugCheck.sys_internal_binaries` methods to use logging instead of
returning status messages.
[[1]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L6-L36)
[[2]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L71-L78)
[[3]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L95-L135)
[[4]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L148-R144)
*
[`CODE/_debug.py`](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061R161-R174):
Added a new method `python_version` to log the Python version and its
compatibility status.

#### Code refactoring:
*
[`CODE/_debug.py`](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L6-L36):
Removed the return of status messages from the
`HealthCheck.check_files`, `HealthCheck.compare_versions`,
`DebugCheck.sys_internal_binaries`, and `DebugCheck.execution_policy`
methods.
[[1]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L6-L36)
[[2]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L71-L78)
[[3]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L95-L135)
[[4]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L148-R144)
*
[`CODE/_debug.py`](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L204-R194):
Simplified the `debug` method by removing redundant logging calls and
using the new `python_version` method.
[[1]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L204-R194)
[[2]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L225-R208)

#### New method addition:
*
[`CODE/logicytics/Checks.py`](diffhunk://#diff-83131f7977935512c18a758ef3ff85db0152c6f8277d99eb94b0bb6830c70a08R25-R33):
Added a new method `Check.execution_policy` to check if the execution
policy is unrestricted.

These changes enhance the logging capabilities and simplify the code by
removing unnecessary return values and redundant logging calls.

Now its better and more efficient, as well as less redundant, new
function added to Checks.py which allows you to check the execution
policy

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
Fixing huge bug with `--dev` and `--debug` where the logic was both
broken and failed

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **New Features**
  - Enhanced logging for health and debug checks.
  - Added a new function to check the Python version.
- Introduced a method to retrieve and check the system's execution
policy.

- **Bug Fixes**
- Removed return values from several methods to streamline
functionality.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
DefinetlyNotAI added a commit that referenced this issue Dec 18, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [ ] I have updated the documentation accordingly, if required.
- [ ] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [ ] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [ ] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

This pull request introduces several new GitHub workflows for
ClusterFuzzLite and refactors the `CODE/_debug.py` file to improve
logging and error handling. The most important changes include adding
new workflows for batch fuzzing, continuous builds, and cron tasks, as
well as refactoring methods in `_debug.py` to enhance readability and
functionality.

#### New GitHub Workflows:

*
[`.github/workflows/cflite_batch.yml`](diffhunk://#diff-949fc2996b2e6e5c6eaba884cacc65e708f97a3863d9c1771a9977bb900c0562R1-R37):
Added a workflow for batch fuzzing with ClusterFuzzLite, scheduled to
run every 6 hours.
*
[`.github/workflows/cflite_build.yml`](diffhunk://#diff-6a380eaf4eb765b7f8021b58c945424b0cef11356e166e1a5b223e6792572bacR1-R28):
Added a workflow for continuous builds with ClusterFuzzLite, triggered
on pushes to the main branch.
*
[`.github/workflows/cflite_cron.yml`](diffhunk://#diff-eeb1dc17caf046b9bba9036c2503d3884a1ed2fde3e7c832e9f5d26d3397a8d4R1-R27):
Added a workflow for daily cron tasks with ClusterFuzzLite, scheduled to
run once a day at midnight.

#### Refactoring in `CODE/_debug.py`:

* Improved logging and error handling in `HealthCheck` and `DebugCheck`
classes, including adding detailed docstrings and restructuring methods
for better readability.
[[1]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L6-L36)
[[2]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L71-L135)
[[3]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L148-R163)
[[4]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061R180-R233)
[[5]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061L225-R247)
* Moved the `execution_policy` method from `DebugCheck` to `Check` class
in `CODE/logicytics/Checks.py` for better organization.
[[1]](diffhunk://#diff-83131f7977935512c18a758ef3ff85db0152c6f8277d99eb94b0bb6830c70a08R5)
[[2]](diffhunk://#diff-83131f7977935512c18a758ef3ff85db0152c6f8277d99eb94b0bb6830c70a08R25-R47)

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
CI Testing, added fuzzing and fixed bugs

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
  - Introduced three new GitHub Actions workflows for automated tasks: 
    - Batch fuzzing
    - Continuous integration builds
    - Daily cron tasks for fuzz testing

- **Bug Fixes**
- Enhanced logging in health and debug checks to streamline error
tracking.

- **Documentation**
- Updated method signatures and added new methods for improved
functionality and clarity.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
DefinetlyNotAI added a commit that referenced this issue Dec 19, 2024
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [ ] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] Deprecation Change <!-- Removing a deprecation -->
- [ ] New feature <!-- Non-Breaking Change that adds a new feature -->
- [ ] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [ ] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [ ] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

This pull request includes several changes to deprecate outdated
features, improve code organization, and update documentation. The most
important changes include deprecating the `extra` and `unzip-extra`
features, updating the `VulnScan` documentation, and removing the
`_extra.py` file.

#### Deprecation of outdated features:

*
[`CODE/Logicytics.py`](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0R138-R147):
Deprecated the `extra` and `unzip-extra` features and added warnings for
their usage.
[[1]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0R138-R147)
[[2]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0R179-R186)
*
[`CODE/logicytics/Flag.py`](diffhunk://#diff-28c69e4247379f685aaf5eb5f582b0641d3247f99db1730a04e10170f6f2497dL134-L148):
Moved the `--extra` and `--unzip-extra` flags to a deprecated section
and added a method to display the help menu.
[[1]](diffhunk://#diff-28c69e4247379f685aaf5eb5f582b0641d3247f99db1730a04e10170f6f2497dL134-L148)
[[2]](diffhunk://#diff-28c69e4247379f685aaf5eb5f582b0641d3247f99db1730a04e10170f6f2497dR171-R186)
[[3]](diffhunk://#diff-28c69e4247379f685aaf5eb5f582b0641d3247f99db1730a04e10170f6f2497dR277-R284)

#### Documentation updates:

*
[`CODE/VulnScan/README.md`](diffhunk://#diff-334cc7dff881eaa0e3d249719b5478f9970bcd2b865157abc058c0c88f50389aR3-R8):
Added a warning about the upcoming move of `VulnScan` to a different
repository.

#### Code organization:

*
[`CODE/VulnScan/v3/_generate_data.py`](diffhunk://#diff-954f866569d6c0606ee08ff8d601030d0224e2190aa90761c7b1bed0099082c5R3-R10):
Reorganized imports and added a deprecation warning for the `SenseMacro`
feature.
[[1]](diffhunk://#diff-954f866569d6c0606ee08ff8d601030d0224e2190aa90761c7b1bed0099082c5R3-R10)
[[2]](diffhunk://#diff-954f866569d6c0606ee08ff8d601030d0224e2190aa90761c7b1bed0099082c5R188-R192)
[[3]](diffhunk://#diff-954f866569d6c0606ee08ff8d601030d0224e2190aa90761c7b1bed0099082c5L195-L200)

#### Removal of deprecated files:

*
[`CODE/_extra.py`](diffhunk://#diff-31b299e38dccd5bfbb4c369ed2336200d55bc112b5d0e46ee7f0e6ad33f2bbccL1-L58):
Removed the `_extra.py` file as part of the deprecation process.

### Motivation and Context

Removal of many deprecated functions, to reorganise Logicytics

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
 _N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
 _N/A_

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Added a checkbox option for "Deprecation Change" in the pull request
template.
- Introduced a new static method to display the help menu in the Flag
class.

- **Bug Fixes**
- Enhanced error handling for deprecated features and improved logging
during script execution.

- **Documentation**
- Updated VulnScan documentation to include a warning about migration to
a different repository.
- Made textual and structural improvements in the README.md for clarity.

- **Chores**
	- Removed deprecated files and tasks from the project.
	- Updated version number in the configuration file.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
DefinetlyNotAI added a commit that referenced this issue Jan 4, 2025
## Pull Request Template

### Prerequisites

<!-- Take a couple of minutes to help our maintainers work faster by
checking of the pre-requisites. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] I have
[searched](https://github.com/DefinetlyNotAI/Logicytics/pulls) for
duplicate or closed issues.
- [x] I have read the [contributing
guidelines](https://github.com/DefinetlyNotAI/Logicytics/blob/main/CONTRIBUTING.md).
- [x] I have followed the instructions in the
[wiki](https://github.com/DefinetlyNotAI/Logicytics/wiki) about
contributions.
- [x] I have updated the documentation accordingly, if required.
- [x] I have tested my code with the `--dev` flag, if required.

### PR Type

<!-- Take a couple of minutes to help our maintainers work faster by
telling us what is the PR guided on. -->
<!-- To tick the checkboxes replace the space with an 'x', so [ ]
becomes [x] . -->

- [x] Bug fix <!-- Non-Breaking Bug Fix - Usually relates to fixing an
issue -->
- [x] Deprecation Change <!-- Removing a deprecation -->
- [x] New feature <!-- Non-Breaking Change that adds a new feature -->
- [x] Refactoring <!-- Non-Breaking Change that modifies existing code
to refactor it to become more organised -->
- [x] Documentation
update <!-- Non-Breaking Change that modifies existing documentation to
refactor it or add extra comments - either wiki, md files or code is
included here -->
- [x] ⚠️ Breaking change ⚠️ <!-- Breaking Bug Fix / New Addition that
changes how Logicytics works -->

### Description

<!-- REQUIRED: Provide a summary of the PR and what you expected to
happen. -->
<!-- Made by copilot -->

This pull request includes significant changes to the `Logicytics`
project, focusing on code refactoring, logging improvements, and the
removal of deprecated features. The most important changes include the
refactoring of flag handling, the addition of detailed logging, and the
cleanup of deprecated features.

#### Code Refactoring and Improvements:

*
[`CODE/Logicytics.py`](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L78-R87):
Refactored `get_flags` function to simplify flag retrieval and logging.
Removed deprecated features `extra` and `unzip_extra` from
`handle_special_actions`. Added the `Logicytics` main function to
encapsulate the main process logic.
[[1]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L78-R87)
[[2]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L138-L145)
[[3]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L176-L183)
[[4]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L370-R359)
[[5]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0R373-R376)

#### Logging Enhancements:

*
[`CODE/_debug.py`](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061R181-R188):
Added detailed logging to `python_version` and `debug` functions.
[[1]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061R181-R188)
[[2]](diffhunk://#diff-cddd7a4c003554a2fce729e954458aa39d397bf2910c94cdd093f39747848061R222)
*
[`CODE/_dev.py`](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09L50-R51):
Enhanced `_prompt_user` function with more user-friendly prompts and
added logging to `dev_checks` function.
[[1]](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09L50-R51)
[[2]](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09R65)
[[3]](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09L90-R106)
[[4]](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09L127-R133)
*
[`CODE/bluetooth_details.py`](diffhunk://#diff-d15430c77b28ebd438edeec503e4666192dd9e256cc386ebcdc6a5012b398d59L1-R12):
Improved logging in `get_bluetooth_device_details` and
`_query_bluetooth_devices`.
[[1]](diffhunk://#diff-d15430c77b28ebd438edeec503e4666192dd9e256cc386ebcdc6a5012b398d59L1-R12)
[[2]](diffhunk://#diff-d15430c77b28ebd438edeec503e4666192dd9e256cc386ebcdc6a5012b398d59L30-R39)
[[3]](diffhunk://#diff-d15430c77b28ebd438edeec503e4666192dd9e256cc386ebcdc6a5012b398d59L52-R74)
[[4]](diffhunk://#diff-d15430c77b28ebd438edeec503e4666192dd9e256cc386ebcdc6a5012b398d59L97)
*
[`CODE/bluetooth_logger.py`](diffhunk://#diff-1876b6113c2e2b1d8fa0dfe09ab9a1b20d3fb52852256fd0bbdd1f8bfc9ce27aL1-R4):
Added detailed logging and documentation to functions `save_to_file`,
`run_powershell_command`, `parse_output`,
`get_paired_bluetooth_devices`, and `log_bluetooth`.
[[1]](diffhunk://#diff-1876b6113c2e2b1d8fa0dfe09ab9a1b20d3fb52852256fd0bbdd1f8bfc9ce27aL1-R4)
[[2]](diffhunk://#diff-1876b6113c2e2b1d8fa0dfe09ab9a1b20d3fb52852256fd0bbdd1f8bfc9ce27aL12-R23)
[[3]](diffhunk://#diff-1876b6113c2e2b1d8fa0dfe09ab9a1b20d3fb52852256fd0bbdd1f8bfc9ce27aL24-R47)
[[4]](diffhunk://#diff-1876b6113c2e2b1d8fa0dfe09ab9a1b20d3fb52852256fd0bbdd1f8bfc9ce27aL38-R95)
[[5]](diffhunk://#diff-1876b6113c2e2b1d8fa0dfe09ab9a1b20d3fb52852256fd0bbdd1f8bfc9ce27aR117-R128)
[[6]](diffhunk://#diff-1876b6113c2e2b1d8fa0dfe09ab9a1b20d3fb52852256fd0bbdd1f8bfc9ce27aR143-R149)

#### Deprecated Feature Removal:

*
[`CODE/Logicytics.py`](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L138-L145):
Removed deprecated features `extra` and `unzip_extra` from
`handle_special_actions`.
[[1]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L138-L145)
[[2]](diffhunk://#diff-44a988332704ab86171610dcfe391d08df0f70f8177c3463e6e089aec9c5baa0L176-L183)

#### Miscellaneous Changes:

*
[`.github/ISSUE_TEMPLATE/bug_report.yml`](diffhunk://#diff-637f7b97bba458badb691a1557c3d4648686292e948dbe3e8360564378b653efL47-R49):
Renamed `flags` to `flags_list` for consistency.
*
[`CODE/_dev.py`](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09L3-R6):
Reorganized imports and added `EXCLUDE_FILES` to `dev_checks` function.
[[1]](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09L3-R6)
[[2]](diffhunk://#diff-8789fb31b28e15638e2117ffc4916c7d17b62b207559877dce4b69ffcfcfaa09L90-R106)
*
[`CODE/cmd_commands.py`](diffhunk://#diff-7422c369c3c1828e52aa953e050cf03d003b07f6f0a244908eb117002bbc4be1R30):
Added `__main__` check to execute commands.

These changes aim to enhance code readability, improve logging for
debugging purposes, and remove outdated features to maintain code
quality.

### Motivation and Context

<!-- REQUIRED: Why is this PR required? What problem does it solve? Why
do you want to do it? -->
To move in version 3.3.0 and fix many bugs and improve Logicytics

### Credit

<!-- If this PR is a contribution, please mention the contributors here
using the appropriate syntax. -->

<!--
### File-Created/CONTRIBUTION by MAIN-Username
What you did, created, removed, refactored, fixed, or discovered.
- [Your GitHub Username](https://github.com/YourGitHubLink)
- [Your GitHub Username](https://github.com/YourGitHubLink) etc...
-->
_N/A_

### Issues Fixed

<!-- REQUIRED: What issues will be fixed? (Format: "#50, #23" etc.) if
none exist type _N/A_ -->
_N/A_


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Release Notes for Logicytics v3.3.0

### New Features
- Enhanced flag suggestion system with historical data tracking.
- Improved Bluetooth data collection and logging.
- Added support for more file types in sensitive data mining.
- Expanded system information and memory snapshot capabilities.
- New configuration options for user preferences and accuracy settings.
- Added a new XML configuration file for CSV file handling.

### Improvements
- Refined error handling across multiple modules.
- Enhanced logging and debugging mechanisms.
- Updated configuration management.
- Improved thread-based execution for certain operations.
- Streamlined control flow to prevent unintended execution during
imports.

### Bug Fixes
- Resolved issues with file parsing and system checks.
- Improved compatibility with various system configurations.

### Dependency Updates
- Added `sentence-transformers` for advanced flag suggestions.
- Added `WMI` for improved Windows system interactions.
- Restored `scapy` package.
- Removed `transformers` and `pathlib` packages.

### Security
- Updated supported version statuses.
- Enhanced logging for better tracking and debugging.

### Deprecations
- Removed some deprecated actions and methods.
- Streamlined code structure for better maintainability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@DefinetlyNotAI DefinetlyNotAI added this to the Suggestions milestone Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
progress/Won't Fix This will not be worked on, further info will be added to why. request/Important New feature or request, top priority, for next update type/System Related to System Code for Logicytics
Projects
Status: Rejected / Duplicate
Development

Successfully merging a pull request may close this issue.

1 participant