izzy
/
Adebar
5
37
Fork 4
Code Issues 8 Pull Requests 1 Releases 35 Wiki Activity
Labels Milestones
New Issue

stderr treated as app names #4

Closed
opened 7 years ago by tukusejssirs · 8 comments
tukusejssirs commented 7 years ago (Migrated from github.com)
Owner

I just noticed that my disable file looks like this – the error output is treated as stdout with the disabled apps. In my opinion you should work only with stdout not the whole terminal output. :)

More info on the error is here. :)

The stderr output is also visible in $backup/sysbackup file, too (pastebin),

And it also affects $backup/sysrestore (pastebin), $backup/userbackup (pastebin) and $backup/userrestore (pastebin) files.

I just noticed that my disable file looks like [this](http://pastebin.com/U2g9Dj8M) – the error output is treated as stdout with the disabled apps. In my opinion you should work only with stdout not the whole terminal output. :) More info on the error is [here](http://stackoverflow.com/a/23712546). :) The stderr output is also visible in `$backup/sysbackup` file, too ([pastebin](http://pastebin.com/3MiLT6qm)), And it also affects `$backup/sysrestore` ([pastebin](http://pastebin.com/4tFQJwsh)), `$backup/userbackup` ([pastebin](http://pastebin.com/Wthk8K6u)) and `$backup/userrestore` ([pastebin](http://pastebin.com/UXk4QCsw)) files.
izzy commented 7 years ago
Owner

Thanks for pointing this out! I wonder why this doesn't happen here (I have Xposed installed as well on some devices). However: should be solved with 83c5286 (devel branch), could you please verify?

Thanks for pointing this out! I wonder why this doesn't happen here (I have Xposed installed as well on some devices). However: should be solved with 83c5286 (devel branch), could you please verify?
tukusejssirs commented 7 years ago (Migrated from github.com)
Owner

File sysbackup is exactly the same.

The output of of $ adb shell pm list packages -3 is here. I think grep-ing out only lines with ^package: pattern would be a solution. (Or even piping the output to sed '/^WARNING/d' - would be the solution, too.)

File `sysbackup` is exactly the same. The output of of `$ adb shell pm list packages -3` is [here](http://pastebin.com/TEPJ43V8). I think `grep`-ing out only lines with `^package:` pattern would be a solution. (Or even piping the output to `sed '/^WARNING/d' -` would be the solution, too.)
izzy commented 7 years ago
Owner

Are you sure you've pulled the latest code _from the "devel" branch_ and used that? I cannot find a single pm list packages in the code which doesn't end with 2>/dev/null – so either those messages are not from STDERR, or you didn't update. Unfortunately I cannot test this myself, as none of the devices I have here show this behavior. If those messages are not from STDERR, I'd really have to check all places and "grep for `^package:", which I prefer to avoid if possible.

Are you sure you've pulled the latest code **_from the "devel" branch**_ and used that? I cannot find a single `pm list packages` in the code which doesn't end with `2>/dev/null` – so either those messages are not from STDERR, or you didn't update. Unfortunately I cannot test this myself, as none of the devices I have here show this behavior. If those messages are not from STDERR, I'd really have to check all places and "grep for `^package:", which I prefer to avoid if possible.
tukusejssirs commented 7 years ago (Migrated from github.com)
Owner

Well, I am sure. I tried even to run adb shell pm list packages -3 2>/dev/null in terminal on its own, but somehow the warnings are still there.

Well, I am sure. I tried even to run `adb shell pm list packages -3 2>/dev/null` in terminal on its own, but somehow the warnings are still there.
izzy commented 7 years ago
Owner

Ah, OK – thanks for that detail; so those "warnings" are not printed to STDERR but to STDOUT. Then it seems we've got no other choice but filtering each returned line separately. I will see to that.

Ah, OK – thanks for that detail; so those "warnings" are not printed to STDERR but to STDOUT. Then it seems we've got no other choice but filtering each returned line separately. I will see to that.
izzy commented 7 years ago
Owner

Should be solved now with 2267b0f – could you please retry and confirm?

Should be solved now with 2267b0f – could you please retry and confirm?
tukusejssirs commented 7 years ago (Migrated from github.com)
Owner

I confirm there are no warning now. Nice job! :)

I confirm there are no warning now. Nice job! :)
izzy commented 7 years ago
Owner

Thanks a lot! So I'm closing this now. Leaves the "some files not found" as only show-stopper for the pending v1.3.0 release – before I can go after your Dual-SIM support :)

Btw: last commit also solved the probably unwanted "progress output" for "Remove apps" :) To see those again, you've had to rise PROGRESS to at least level 4 now. I might even decide to push that up to level 5, as it's really just a "forgotten debug message" (I've never encountered any app in that section, and so left it out of curiosity)

Thanks a lot! So I'm closing this now. Leaves the "some files not found" as only show-stopper for the pending v1.3.0 release – before I can go after your Dual-SIM support :) Btw: last commit also solved the probably unwanted "progress output" for "Remove apps" :) To see those again, you've had to rise `PROGRESS` to at least level 4 now. I might even decide to push that up to level 5, as it's really just a "forgotten debug message" (I've never encountered any app in that section, and so left it out of curiosity)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
devel
master
Labels
Apply labels
Clear labels
bug documentation duplicate enhancement help wanted invalid question wontfix
No Label bug documentation duplicate enhancement help wanted invalid question wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: izzy/Adebar#4
Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(<nil>)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes