Skip to content
This repository was archived by the owner on Sep 8, 2024. It is now read-only.

Feat/self.gui.connected #2682

Merged
merged 6 commits into from
Sep 16, 2020
Merged

Feat/self.gui.connected #2682

merged 6 commits into from
Sep 16, 2020

Conversation

JarbasAl
Copy link
Contributor

@JarbasAl JarbasAl commented Aug 27, 2020

@JarbasAl JarbasAl requested review from forslund and AIIX August 27, 2020 01:07
@devops-mycroft devops-mycroft added the CLA: Yes Contributor License Agreement exists (see https://github.com/MycroftAI/contributors) label Aug 27, 2020
@JarbasAl JarbasAl changed the title Feat/gui status Feat/self.gui.connected Aug 27, 2020
@devops-mycroft
Copy link

Voight Kampff Integration Test Succeeded (Results)

JarbasAl added a commit to OVOSHatchery/ovos-skill-euronews that referenced this pull request Aug 27, 2020
@forslund
Copy link
Collaborator

forslund commented Aug 27, 2020

Looks nice and simple! Will test it properly tonight or tomorrow

Two things:

  • Docstrings are missing
  • is there a reason you're using a custom response message type and not message.response(...) to generate the default response message with the default type? (assuming it has something to do with using reply...)

@penrods
Copy link
Contributor

penrods commented Aug 27, 2020

Nice! Are you guys still trying to maintain anything like this list of messages that traverse the messagebus?
https://docs.google.com/spreadsheets/d/1RsBpMOGx4o8A_zF_UELYQSLK8DlIScHGnfzJ3iSN0AE/edit#gid=0

I never loved using a Google Sheet for this (outside of the repo), but having something like this seems useful.

@krisgesling @chrisveilleux

@krisgesling
Copy link
Contributor

Hey @penrods I have moved that list of message types to the public documentation and trying to keep it updated there instead:
https://mycroft-ai.gitbook.io/docs/mycroft-technologies/mycroft-core/message-types

It's a good point that we need to add in the gui.* messages though

@JarbasAl
Copy link
Contributor Author

* is there a reason you're using a custom response message type and not `message.response(...)` to generate the default response message with the default type? (assuming it has something to do with using reply...)

because of message context, needs to use .reply for proper targeting/hivemind routing, but i would argue that message.response should be refactored to use this internally self.reply(xxxx) instead of ```response_message = Message(xxxx)``.

@forslund
Copy link
Collaborator

forslund commented Sep 1, 2020

It can't always do that, since it is sometimes used within a service (I did change it briefly when merging your updates for the reply but it broke things severely when chained messages were emitted). I do think we should have an optional reply flag to the response however.

For now can maybe we can change the response message type to match the default response? gui.status.request.response?

@devops-mycroft
Copy link

Voight Kampff Integration Test Succeeded (Results)

@krisgesling
Copy link
Contributor

Should also have said, beyond the little question above, I think this is great. Definitely going to be needed very soon.

@devops-mycroft
Copy link

Voight Kampff Integration Test Succeeded (Results)

@JarbasAl
Copy link
Contributor Author

Should also have said, beyond the little question above, I think this is great. Definitely going to be needed very soon.

i already need it xD

@devops-mycroft
Copy link

Voight Kampff Integration Test Failed (Results)

@devops-mycroft
Copy link

Voight Kampff Integration Test Succeeded (Results)

Copy link
Contributor

@krisgesling krisgesling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Working great 👍

@krisgesling krisgesling merged commit 4d3cd33 into dev Sep 16, 2020
@JarbasAl JarbasAl deleted the feat/gui_status branch September 16, 2020 07:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CLA: Yes Contributor License Agreement exists (see https://github.com/MycroftAI/contributors)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants