-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
IPC GUI todo #732
Comments
Mark 2 is still an issue but I guess it's because the bots thing is currently not fully implemented so it'll always show 0 / 0 / 0 on bots until it's fully implemented? Mark 5 is fixed, no more errors in the chrome dev console window. See you moved the log update function to the log.html, had me confused at first on why I couldn't find it in app.js file to change the url bit to how I have things laid out for ASF. |
mm still shows 0 / 0 / 0 for me, have tried with and without Edit: |
@MrBurrBurr You shouldn't use any ASF strings being used for display purposes - this includes e.g. parsing
That's what |
Version yes - there is no endpoint for that yet. I'll add it once I get some time. You can open a separate issue so I won't forget. |
@MrBurrBurr Still shows 0 / 0 / 0 for bot status, as for the log function it now looks to be working on it updating the log without intervention. |
like in the picture I put above, in the normal status page I see
which indicated that the status is being seen somewhat, but the green/orange/red status things on the "bots" tab just continue to show as the 0 / 0 / 0 |
Yes I have values for
Don't think there is anything bad in that to throw it on here..but if there is let me know so I can take it down..though I'll have to have @JustArchi delete the #github-updates notification on discord that corresponds with this message.. |
There is no sensitive info in any API call, if by sensitive we understand passwords or other login details. |
Good to know! ^^ kinda figured that was the case as I didn't see any login details in the api call anyways |
|
@JustArchi you can remove
for the most part as everything has been squashed in #733 for all that other than the layout options bug. You can replace it with
if you want, as they are things that should/will be added over time. |
What stats? |
That's not |
|
No, you should use |
Everything that |
You're designing the web UI and what exactly it provides. You don't have to use all data that API provides, you can cherry-pick the information you're interested in. Personally I see no reason for doing that - I'd instead add basic overview of active bots in the panel, like now, and provide more info (e.g. about currently farmed game/games, and remaining ones, even with fancy banners or anything) when user asks about that, e.g. on-hover as a popup, or some detailed bot info. In any case, that's your choice. |
like the little tweaks you did to our todo list @MrBurrBurr :p btw you know you can checkmark them on there, instead of deleting them when they are done lol xD |
For main account usage, a one-click As an option, people might not want the Nice-to-have would be a command history accessible via keyboard up & down arrows (like this) - this one definitely is a candidate to keep the last 25 commands or so in |
@MrBurrBurr Btw even if one doesn't show more than one reply at a time by wiping the |
Just gonna list some features I'm missing still in the UI or don't find very useful as-is @MrBurrBurr . Hope you don't mind 👍
|
@MrBurrBurr Time remaining doesn't work when |
@MrBurrBurr For the first suggestion is yes, you are right. As for the second: I ment that user needs to press arrowUp key 15 times, for example, to repeat a command he used 14 commands back. So the list of 10-20 last commands in form of clickable links or buttons would be easier. |
@MrMarble do you use an adblocker of any sorts? |
@JourneyOver Yes, I'm using uBlock Origin, but I already tried to disable it and still the same error |
firewall, router, anything else that could be blocking it? I know someone else was having this issue as well on discord with the log throwing an error for them, dunno if they fixed it or not though :x |
I don't think so, I'm currently abroad in a different country with my laptop, also is the first time i'm installing it in that system, I had the same problem at home with my main windows pc
|
Then I'm not sure, sorry :/ since it works fine on my end on both windows and a raspberry pi then I am unable to help troubleshoot much further since I can't produce it. |
WebSocket stuff (ASF Log) isn't supported on Win 7 clients. I assume it's that, @MrMarble |
oh yes, I totally forget that is a thing xD guess I could of helped him troubleshoot with just one more question. |
@Luckz My main pc is Windows 10 and currently I have it running in my server with Debian 8 and my laptop is Ubuntu 17, I'm using Firefox if it helps |
@MrBurrBurr Yes, this is the response I got: |
Is there any settings needed to enable IPC GUI command execution? I got a |
@mxalbert1996 You can wait until #759 gets merged and ASF updates to include the changes, or if you want for now until then you can go in to the app.js file in the www/js folder, and change line 201 from
to
if you update ASF before the pull request gets merged in, you'll of course have to go in and change that line again any time you update until the pull request gets merged. |
|
@JourneyOver I am currently using windows 7 and got the same error while it works flawlessly on my laptop running OS X. Please check, thank you. |
@oubeichen WebSocket stuff (ASF Log) isn't supported on Win 7, you'll either have to upgrade to windows 8/8.1/10 or live without seeing the log in the IPC GUI on machines that are using windows 7 and below. |
@JourneyOver No, the ASF server is running on my VPS, using CentOS 7 with Docker. |
@oubeichen yet above you said
so make up your mind on what you are running. Either way it doesn't really matter what OS you are running the server on, it all depends on what OS you are using to access the IPC GUI on, which is why it works when you view the log on |
Currently I'm using ASF version 3.1.1.8 in a docker container running in Debian 8.
|
But this is not IPC GUI support page, this is IPC GUI development. You already reported your bug, it's pointless to spam about it. |
@JustArchi Oh sorry, it was only because I didn't saw it in the current bug list so I was reporting is still failing in the new version. Sorry for the spam |
@MrBurrBurr Can you open new issue on ASF GitHub as lead IPC GUI developer, so you could keep track of IPC GUI todo list and edit it accordingly without a need of my help? I can edit the issue if needed anyway. Thanks. |
Thanks! From now on please use #773 issue instead for IPC GUI development. |
I'm opening a single issue for this one, as most tasks won't be coded by me.
IPC GUI source code is available here. Feel free to make appropriate modifications and send a PR.
Best practice
Bugs
Suggestions
The text was updated successfully, but these errors were encountered: