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

Purge All AI's Implementations #348

Open
hollowaykeanho opened this issue Jul 5, 2024 · 6 comments
Open

Purge All AI's Implementations #348

hollowaykeanho opened this issue Jul 5, 2024 · 6 comments
Assignees
Labels
Bug Case is about a glitch. In Progress Someone is working on the case.

Comments

@hollowaykeanho
Copy link
Member

Description

That's it. It's done. No more AI implementations. This ticket tracks all AI implementations purging from this repository.

Expected Behavior

All AI implementations are purged of the source codes. AI implementations for source codes shall be banned. Documentations is still usable.

Current Behavior

The ill-implementations (overconfident AI) is still within the source codes causing major CI tasks failed.

Steps to Reproduce [COMPULSORY]

Run through all the source codes.

Associated Data Files

No response

@hollowaykeanho hollowaykeanho added In Progress Someone is working on the case. Bug Case is about a glitch. labels Jul 5, 2024
@hollowaykeanho hollowaykeanho self-assigned this Jul 5, 2024
@github-project-automation github-project-automation bot moved this to Buckets in AutomataCI Jul 5, 2024
@hollowaykeanho hollowaykeanho moved this from Buckets to v3.0.0 in AutomataCI Jul 5, 2024
@corygalyna
Copy link
Contributor

? What's the story behind?

@lucirox
Copy link

lucirox commented Jul 13, 2024

Interesting.

@hollowaykeanho
Copy link
Member Author

hollowaykeanho commented Jul 24, 2024

2 AIs are recommending broken PowerShell codes confidently which broke the Package API and some critical libraries. I was debugging until fall sick and finally realized the project is so screwed.

Currently purging all of the traces.

@hollowaykeanho
Copy link
Member Author

hollowaykeanho commented Jul 29, 2024

Here's a case - AI confidently recommend the following:

on PowerShell:

if ([string]::IsNullOrEmpty($___target)) {
    ...
}

on POSIX Shell

if [ -z "$___target" ]; then
    ...
fi

with some non-sense reliability reasons so hestiaSTRING_Is_Empty is invented to unify the function for all shells.

However, after reading through all the specs, they can be done easily across all the shells:

On PowerShell

if ($___target -eq "") {
    ...
}

On POSIX Shell

if [ "$___target" = "" ]; then
    ...
fi

Affects: Entire project

@hollowaykeanho
Copy link
Member Author

hollowaykeanho commented Jul 29, 2024

Another case:

AI confidently recommend a list directory loop using multiple cmdlet in PowerShell:

Get-ChildItem -Path $path -File -Recurse
    | Where-Object { $_.Name -like ".pdf" }
    | ForEach-Object {
     ...
}

for POSIX Shell:

for ___file in "$path/"*; do
    if [ ! -f "$___file" ]; then
        continue
    fi

    ...
done

The problem from what the AI recommended is continue cannot be used in the loop due to multiple cmdlet. Moreover, there is no need to use so many cmdlet for this case. After reading the specs, this is the correct PowerShell:

foreach ($___file in (Get-ChildItem -Path $path -File -Recurse -Filter ".pdf")) {
     ...
}

Affects: Entire project - deeply damaged DEB library as well.

@corygalyna
Copy link
Contributor

That's the reason for re-writing all the libraries into Hestia? Yeah, I do agree with you. The AI screwed this up really bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Case is about a glitch. In Progress Someone is working on the case.
Projects
Status: v3.0.0
Development

No branches or pull requests

3 participants