merge staging into main #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Patch-Provides ~~ FIX: nitrond auto does not change mode (it just checks environment status for one time) Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
…l mode selection ~~ there is no way to make auto killer since it's unlogical, manual kill is required Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
Signed-off-by: UsiF <xprjkts@gmail.com>
This reverts commit bab3268.
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
…ument Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
~~ since we actually grabbing Kernel's archticture Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
~~ "all" is now available Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
…into nitrond-staging
Signed-off-by: UsiFX <xprjkts@gmail.com>
~~ this will help to get safe execution as it wont give the permission for some arguments to work if nitrond is already locked in background Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
~~ since we don't need to tell the user that we tracked shutdown signals just for removing lockfile... Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Patch-Provides:
~~ change the way how function works
~~ implement 3 types of status:
1- [ OK ]: Means process ended without any issue
2- [ DONE ]: Means process ended but cant identify exit code
3- [ FAIL ]: Means process ended with sure type of false code
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Patch-Provides: ~~ disable SC2116, SC2120, SC2116, SC2086, SC1001 ~~ major fixes Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
~~ this may be an identification that the kernel haven't been loaded natively or being somehow emulated. Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
~~ since `return' cannot be used unless at a function in bash Signed-off-by: UsiFX <xprjkts@gmail.com>
…into nitrond-staging
~~ super fast?, according to bash. Signed-off-by: UsiFX <xprjkts@gmail.com>
Patch-Provides: ~~ defining some CPU frequences grabber ~~ set variable `kernel.perf_cpu_time_max_percent' to "0" since we do not care about how much CPU is consumed ~~ fixup some ppm cpu limitations conflicting ~~ arranging up this also may fix the battery mode bug which causes audit limit exceedation which may also cause system instability Partially-Authored-by: Pedrozzz0 <guitopzika26@gmail.com> Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
~~ tool is now 99% stable and bugless Signed-off-by: UsiFX <xprjkts@gmail.com>
Signed-off-by: UsiFX <xprjkts@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.