-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sprint 1 #5
Comments
@ArneTR I want to collect all bug reports here for power hog v0.2 |
Bug #1 happened while the Hog.app was already on the system and I was following the install instructions from the welcome screen. First step failes:
|
The problem might be that the unzip operation will unzip also to a folder that is only sudo writeable. Somehere there needs to be a sudo call in the file at least |
Next up I tried to manually go through the install file one by one to install the hog. I encountered the sed command, which does not work for me. I have the default BSD sed. The following change was necessary:
Otherwise I get |
Mini Note: Maybe change type from PATH_PLASE_CHANGE to PATH_PLEASE_CHANGE |
Bug #3: The settings in my settings file in the HOME directory are not picked up. I did not create a settings file in In my firewall I see that the requests actually go out wrongly to the live domain |
Bug #4: I blocked the request to the online domain and the power logger crashed. Even after 10 Minutes it is not coming back up. The service is still running, but apparently in an endless loop. If I unload the service I can see again data in the Hog macOS panel. However only until the next data upload is tried and blocked. In order for you to reproduce it I then tried disabling my Wifi. Here the same issue happens, after 5 Minutes and no Internet the hog power logger crashes |
The installer pipes the script to sudo bash
should be the command that is show in the hog? Can you please recheck?
It could be that it really depends on what core the process is running. Performance cores take up to 10 times more energy. I am currently looking into the |
You see in my CLI paste here that the pipe is as said to To answer your follow up question: In the hog it shows correctly as |
Can you try:
|
curl -s https://api.github.com/repos/green-coding-berlin/hog/releases/latest | grep '/hog_power_logger.zip' | cut -d\" -f4
=> https://api.github.com/repos/green-coding-berlin/hog/releases/121866552
… On 25. Sep 2023, at 11:22 AM, Didi Hoffmann ***@***.***> wrote:
Can you try:
curl -s https://api.github.com/repos/green-coding-berlin/hog/releases/latest | grep '/hog_power_logger.zip' | cut -d\" -f4
—
Reply to this email directly, [view it on GitHub](#5 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAB5GL2JA353LNXGNOSLSPLX4FEMRANCNFSM6AAAAAA44QCQFI).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hmmm? Why am I getting
it seems like the |
For the record: |
For the record. The curl download was not working as GitHub once in while as an error, that delivers a different version of the json without newlines and the json double. |
eMail feedback
Bugs
cpu_time
-d
The text was updated successfully, but these errors were encountered: