search: Add is:public-stream to search entire history of public streams.

Add ability to search entire message history of all public streams at
once. It includes all subscibed, non subscribed public streams messages
and even historical public stream messages sent before user had joined
an organization or stream.
Fixes: #8859.
Testing Plan:

Created two public streams. Sent some messages to it. Add a new user to stream after sending messages.
Created private stream. Added same user that was added in step 1.
Logged in to newly added user. Searched for : is:public-stream Ensured typeahead was working and message list contained only messages (including history) of public streams and not private streams or private messages. Also tried to search for keyword and it was also working properly.
Searched for: -is:public-stream Ensured typeahead was working and message list contained only messages of private streams and private messages. Also tried to search for keyword and it was also working properly.

GIFs or Screenshots:
**Note: ** -is:public-stream doesn't allow to include history on private messages (not applicable anyway) and private streams (possible on some but current implementation of negation of public stream doesn't support it.)
@timabbott
Me and @YagoGG are curious how current sql queries approach you mentioned in https://github.com/zulip/zulip/issues/8859#issuecomment-377266113 and implemented in this PR will perform for large organisation with large messages ?

Awesome, thanks for working on this @thedeveloperr!  After seeing it, I think this isn't the only reasonable semantics, mainly because one can have a private stream that allows all subscribers to access full history, and guest users don't generally get access to even public streams from before they joined.  After some reflection, I think this means a few things:

We'll want a different name for this in is:public-stream.  I think maybe a reasonable concept would be  to have a new all: parameter, with eventually values of history:subscribed (which would do all streams you're subscribed to, including private streams with history public to subscribers) vs. history:public (which would do all public streams in the organization).  The history: operator would be mutally exclusive with stream: and pm-with:.  So this feature would be accessed by history:public, and if we later add.
The history: operator should return an error for guest users; they will never be able to use it.
We should start with just implementing history:public, doing at most a comment of work towards history:subscribed.
If/when we choose to add history:subscribed, we'd want a new function in zerver/lib/streams.py, recipients_with_full_history_access(user_profile).  We can add this, with tests in a new first commit; it should return the set of recipient_id values for which the current user can access the full history, which we can feed into the next stage.

@rishig what are your thoughts?  I'm not 100% confident that history:public is the right operator name, but I think in any case we do want a new operator (history:) for controlled the top-level source of what messages are searched.  I'll also note that I like the history:public concept because it's then clear that it's not going to search your PMs or private streams; and history:subscribed is I think clear that it won't search your PMs either.
If we do history:subscribed, we'll need to think more about how to handle private streams without public history... I assume we'll still want to, so the database query will end up being a union of two queries (there's some precedent for that with is:private, so not a big deal).  But that's part of my motivation for thinking of that as a follow-up project.

Me and @YagoGG are curious how current sql queries approach you mentioned in #8859 (comment) and implemented in this PR will perform for large organisation with large messages ?

I think we shouldn't worry about this.  My view is that we should just write this to get the recipient_ids:
recipients_ids = Recipient.objects.filter(type=Recipient.STREAM, type_id__in=Stream.objects.filter(realm=realm, invite_only=False))

and then feed that result into the sqlalchemy query.  It wouldn't be super hard to write whatever the standard sqlalchemy code that does this same thing (and save a round-trip to the database), but this will never be an expensive part of the overall query operation, so it's probably not worth doing.

@timabbott  Your comment was exact things I discussed with @YagoGG while developing this issue 😅 But you the issue thread already had a plan so implemented like this. I agree we need more controlled and better syntax.
Another problem with current syntax is negation. -is:public-stream should ideally return private stream but it's not super clear whether it will include history or not.

As of now history is not included because, while developing the feature i followed the maybe_negate() pattern to get negation and implementing negation + including history while following this pattern had some potential security problems so finally I decided not to try and include history for negation is:public-stream.

I have already thought of plan to tackle if there would be new semantic change and stuff while working on current PR so it won't be super difficult to make changes to existing PR.
I need some clarification on negation part....Can you please elaborate how negations will behave for each new proposed filter ? Will it be straight forward NOT IN (id1, id2....) existing maybe_negate strategy we are following for other filters?

@timabbott  can guests be added to a public or private stream by another user ? And can the guest after being added access history of private stream ? Seeing the source code I have some confusion so wanted to clear the spec.

I think we shouldn't worry about this. My view is that we should just write this to get the recipient_ids:
recipients_ids = Recipient.objects.filter(type=Recipient.STREAM, type_id__in=Stream.objects.filter(realm=realm, invite_only=False))

@timabbott
Right now I first fetch stream ids and then using bulk_get_recipients (as it uses cache)  to fetch recipients. Is current approach wrong ?

After chatting with Tim, I think our current plan for names is streams:subscribed and streams:public.
The messaging around this can be "any stream or streams restriction searches all history, otherwise it just searches received messages" and "you're only allowed one stream or streams operator at a time".

Right now I first fetch stream ids and then using bulk_get_recipients (as it uses cache) to fetch recipients. Is current approach wrong ?

Your approach works; the alternative proposal I suggested will just be faster.

Just to be clear I should just replace those 4 lines with this single line ? recipients_ids = Recipient.objects.filter(type=Recipient.STREAM, type_id__in=Stream.objects.filter(realm=realm, invite_only=False))
I thought cache will be faster for subsequent searches. Also in chat application like zulip what is cache hit rate ?

@thedeveloperr caching is more complicated than just hit rates.  The key issue here is we're already going to the database to fetch the set of streams in any case; a join against Recipient will be cheap since we have a database index there, so effectively we're saving the query on Recipient to the cache altogether.  (Also, if we add a .values("id") sort of thing, we save constructing Python objects we won't use)

(Let me know when you have an updated version ready!)

@timabbott I am having problem in getting different frontend typeaheads to work together. backend implementation of streams:public is done already. streams:subscribed is left. Should I send commits for both together or first get streams:public to get reviewed and merged ?

@timabbott streams:public work is ready for review.

This is great; I merged this with the following changes:

Reordered so streams: is not high in the documentation lists, since it's a rare use case.
Simplified docs.
Removed some accidentally added whitespace.

diff --git a/templates/zerver/app/search_operators.html b/templates/zerver/app/search_operators.html
index 4b1147e306..a71e27dac6 100644
--- a/templates/zerver/app/search_operators.html
+++ b/templates/zerver/app/search_operators.html
@@ -8,10 +8,6 @@
                     {{ _('Effect') }}

-

-                streams:public
-                {{ _('Narrow to all historical messages in all public streams, both subscribed and unsubscribed.') }}
-

                 stream:stream
                 {{ _('Narrow to messages on stream') }} stream
@@ -44,6 +40,10 @@
                 id:id
                 {{ _('Narrow to just message ID') }} id

+

+                streams:public
+                {{ _('Search all public streams in the organization.') }}
+

                 is:alerted
                 {{ _('Narrow to messages with alert words.') }}
diff --git a/templates/zerver/help/search-for-messages.md b/templates/zerver/help/search-for-messages.md
index 70133c7818..2f0ce13d1d 100644
--- a/templates/zerver/help/search-for-messages.md
+++ b/templates/zerver/help/search-for-messages.md
@@ -25,10 +25,6 @@ Here is the **full list of search operators**.

 * `stream:design`: Search within the stream `#design`.
 * `stream:design topic:emoji+picker`: Search within the topic `emoji picker`.
-* `streams:public`: Any `stream` or `streams` restriction searches all history,
-  otherwise it just searches received messages" and "you're only allowed one `stream`
-  or `streams` operator at a time. Search within all `public` streams
-  (both subscibed and unsubscribed).
 * `is:private`: Search all your private messages.
 *<EMAIL_ADDRESS>Search 1-on-1 messages with Ada.
 *<EMAIL_ADDRESS>Search group private messages that
@@ -37,6 +33,8 @@ Here is the **full list of search operators**.
 * `sender:me`: Search sent messages.
 * `near:12345`: Show messages around the message with ID `12345`.
 * `id:12345`: Show only message `12345`.
+* `streams:public`: Search the history of all [public
+  streams](/help/change-the-privacy-of-a-stream) in the organization.

 * `is:alerted`: See [alert words](/help/add-an-alert-word).
 * `is:mentioned`: See [mentions](/help/mention-a-user-or-group).
diff --git a/zerver/lib/actions.py b/zerver/lib/actions.py
index 2ec700bac2..6e6ba0c67c 100644
--- a/zerver/lib/actions.py
+++ b/zerver/lib/actions.py
@@ -5233,7 +5233,7 @@ def get_web_public_streams(realm: Realm) -> List[Dict[str, Any]]:
 def do_get_streams(
         user_profile: UserProfile, include_public: bool=True,
         include_subscribed: bool=True, include_all_active: bool=False,
-        include_default: bool=False, include_owner_subscribed: bool=False,
+        include_default: bool=False, include_owner_subscribed: bool=False
 ) -> List[Dict[str, Any]]:
     if include_all_active and not user_profile.is_api_super_user:
         raise JsonableError(_("User not authorized for this query"))
diff --git a/zerver/lib/streams.py b/zerver/lib/streams.py
index 3d0e52c477..d76f216861 100644
--- a/zerver/lib/streams.py
+++ b/zerver/lib/streams.py
@@ -92,8 +92,9 @@ def access_stream_by_id(user_profile: UserProfile,
                                             allow_realm_admin=allow_realm_admin)
     return (stream, recipient, sub)

-def access_stream_by_invite_only(realm: Realm, invite_only: bool) -> 'QuerySet[Stream]':
-    return Stream.objects.filter(realm=realm, invite_only=invite_only)
+def get_public_streams_queryset(realm: Realm) -> 'QuerySet[Stream]':
+    return Stream.objects.filter(realm=realm, invite_only=False,
+                                 history_public_to_subscribers=True)

 def get_stream_by_id(stream_id: int) -> Stream:
     error = _("Invalid stream id")
diff --git a/zerver/views/messages.py b/zerver/views/messages.py
index 76f6992b1e..b81508c5a2 100644
--- a/zerver/views/messages.py
+++ b/zerver/views/messages.py
@@ -30,7 +30,7 @@ from zerver.lib.message import (
 )
 from zerver.lib.response import json_success, json_error
 from zerver.lib.sqlalchemy_utils import get_sqlalchemy_connection
-from zerver.lib.streams import access_stream_by_id, access_stream_by_invite_only, \
+from zerver.lib.streams import access_stream_by_id, get_public_streams_queryset, \
     can_access_stream_history_by_name, can_access_stream_history_by_id, \
     get_stream_by_narrow_operand_access_unchecked
 from zerver.lib.timestamp import datetime_to_timestamp, convert_to_UTC
@@ -246,13 +246,13 @@ class NarrowBuilder:
         if operand == 'public':
             # Get all both subscribed and non subscribed public streams
             # but exclude any private subscribed streams.
-            public_streams_queryset = access_stream_by_invite_only(self.user_profile.realm,
-                                                                   invite_only=False)
-            recipients = Recipient.objects.filter(type=Recipient.STREAM,
-                                                  type_id__in=public_streams_queryset).values('id')
-            cond = column("recipient_id").in_([recipient['id'] for recipient in recipients])
+            public_streams_queryset = get_public_streams_queryset(self.user_profile.realm)
+            recipient_ids = Recipient.objects.filter(
+                type=Recipient.STREAM,
+                type_id__in=public_streams_queryset).values_list('id', flat=True)
+            cond = column("recipient_id").in_(recipient_ids)
             return query.where(maybe_negate(cond))
-        raise BadNarrowOperator('unknown streams ' + operand)
+        raise BadNarrowOperator('unknown streams operand ' + operand)

     def by_topic(self, query: Query, operand: str, maybe_negate: ConditionTransform) -> Query:
         if self.user_profile.realm.is_zephyr_mirror_realm:
@@ -595,6 +595,7 @@ def ok_to_include_history(narrow: OptionalNarrowListT, user_profile: UserProfile
         for term in narrow:
             if term['operator'] == "is":
                 include_history = False
+
     return include_history

 def get_stream_from_narrow_access_unchecked(narrow: OptionalNarrowListT, realm: Realm) -> Optional[Stream]:
@@ -692,6 +693,7 @@ def add_narrow_conditions(user_profile: UserProfile,
             operand=' '.join(search_operands)
         )
         query = builder.add_term(query, search_term)
+
     return (query, is_search)

 def find_first_unread_anchor(sa_conn: Any,

For follow-ups:

@rishig you probably will want to do another pass on them, but this feels pretty clean to me.  Though maybe we should add a reference to this on /for/open-source?  I could see this being a thing that sort of community is excited about ("Search entire organization's public history") or whatever.
We may need to do something to fix the typeahead ordering; I think this is getting sorted earlier than it should.  @aero31aero may be able to help @thedeveloperr debug, but we should consider fixing that the top priority technical follow-up.
I'm opening an issue for is:subscribed with details on how that should work.

https://github.com/zulip/zulip/issues/13052 is the follow-up issue.

I'm confused. I see this locally:

What is the expected sort order here?

This is the way I programmed it and wrote tests for. No specs were give for
the order in typeaheads. I can change it if needed. I usually search across
multiple streams so gave it top position.
On Fri, 23 Aug, 2019, 2:43 AM Rohitt Vashishtha<EMAIL_ADDRESS>wrote:

I'm confused. I see this locally:
[image: image]
https://user-images.githubusercontent.com/8033238/63550095-8f5f8180-c54f-11e9-9f91-7532bd2a897e.png
What is the expected sort order here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/12999?email_source=notifications&email_token=AFTAFNECZPSH6TBP2CIXKE3QF36PBA5CNFSM4ILNZK2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD46NGFA#issuecomment-524079892,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFTAFNHDCWEGDQ3ZPHXJKULQF36PBANCNFSM4ILNZK2A
.

Okay. If you do need help with this, PM me on CZO.
On Fri, Aug 23, 2019 at 3:17 AM Mohit Gupta<EMAIL_ADDRESS>wrote:

This is the way I programmed it and wrote tests for. No specs were give for
the order in typeaheads. I can change it if needed. I usually search across
multiple streams so gave it top position.
On Fri, 23 Aug, 2019, 2:43 AM Rohitt Vashishtha<EMAIL_ADDRESS>
wrote:

I'm confused. I see this locally:
[image: image]
<
https://user-images.githubusercontent.com/8033238/63550095-8f5f8180-c54f-11e9-9f91-7532bd2a897e.png
What is the expected sort order here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/zulip/zulip/pull/12999?email_source=notifications&email_token=AFTAFNECZPSH6TBP2CIXKE3QF36PBA5CNFSM4ILNZK2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD46NGFA#issuecomment-524079892
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AFTAFNHDCWEGDQ3ZPHXJKULQF36PBANCNFSM4ILNZK2A
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/12999?email_source=notifications&email_token=AB5JHVSMCN3STBTVK5KVNMLQF4CQ7A5CNFSM4ILNZK2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD46P2ZA#issuecomment-524090724,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB5JHVQ2HLNYYKWQELACL43QF4CQ7ANCNFSM4ILNZK2A
.

@timabbott please clarify on the expected ordering of typeaheads in different situations?

@timabbott In the commit log I noticed that the commit that is merged with master is showing failed test due to some kind of timeout. But the commits in this PR are passing the tests. Why is the test failing ?

@thedeveloperr you should link to errors if you want someone to investigate, but generally timeouts in CI reflect a thing unrelated to Zulip (e.g. the host running the tests losing its network access temporarily).

@timabbott Commit: https://github.com/zulip/zulip/commit/e5482adec0b4e49f1619fb0b3069929fa9893400
This is the failing test link https://circleci.com/gh/zulip/zulip/30676?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link .
I am still new to testing infrastructure so was unsure about this.

If you scroll to the bottom of it, you'd realize there are no errors in the test log. Circle states that the test suite timed out so we should assume there's a limit that Circle places on individual test suites that our tests failed to complete under.
More importantly, it appears that all backend tests and node tests did manage to run.


get volume handle

Signed-off-by: Santosh Pillai<EMAIL_ADDRESS>

@sp98 please update the PR description and commit message to provide more details.


is this an abandonware?

Seems unmaintained for years and nobody is answering here.
it also says on the README that version 2 is in progress, which doesn't seem so

Looks like it. If people don't have the time to maintain it someone (read not me) should step up and ask to take the reigns.

Hi there, I'm also using this software, and have just faced a bug that was reported and solved #107, but not commited to the master...
Since july 2014 the code isn't updated, and also I think people still donating money for the maintainer of the code at http://textextjs.com....

I've gotten exactly 3 donations so far in 4 years that his code was public. A "popular" open source project is a blessing and a curse. I did the original work over 2 week break that I had and never anticipated that people would actually use it :) I'm very glad however that many found this useful. I'm sure we all know how difficult it is to find time for real life, hobbies and try to keep up with open source projects.
I've been meaning to find time to do some house keeping on this project as it definitely has been neglected.

Its awesome software and did everything I needed, I just had to put in some extra effort of my own to get exactly what I wanted out of it. Thanks though, it helped alot =)


longhorn multi-cluster app - longhorn should be deployed to longhorn-system namespace.

What kind of request is this (question/bugt):
bug
Steps to reproduce (least amount of steps as possible):
deploy longhorn as multi-cluster app
Result:
namespace with name longhorn-prefix .
Other details that may be helpful:
the namespace should be named longhorn-system
Environment information

Rancher version: v2.2.2
Installation option: single node

Cluster information

Cluster type: Imported
Machine type: cloud
Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:           18.09.5
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        e8ff056
 Built:             Thu Apr 11 04:43:57 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.5
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       e8ff056
  Built:            Thu Apr 11 04:10:53 2019
  OS/Arch:          linux/amd64
  Experimental:     false

@alena1108 pointed me to https://github.com/rancher/rancher/issues/17913

Linked to https://github.com/rancher/longhorn/issues/487

@yasker

pointed me to #17913 , though not sure if it's the exactly same

It is exactly the same issue. Once the fix for 17913 is in, you would be able to specify a namespace. If the namespace exists, it will be used. If not, it will be created. Closing as a duplicate of #17913.


Add ElemRV from May 2024 tape-out

25 MHz MCU with a 5 stage RISC-V CPU. Loads code from an external SPI NOR-Flash and uses a HyperBus interface for external HyperRAM. Has a UART IP for debug communication and 4 GPIO pins.

Missing bondpad_70x70.lef / .gds ?

Missing bondpad_70x70.lef / .gds ?

No, those files are located here https://github.com/dnltz/OpenROAD-flow-scripts/commits/IHP-May24

Thanks

Thanks

This is the environment we used to build: https://github.com/dnltz/ElemRV-init


Choose "best" engine automatically?

I understand if you don't select an engine, it uses Math.random(). Would it be possible to have a mode that uses the best engine for the currently running environment instead, i.e. window.crypto in modern browsers, node.js crypto in node, or fall back to Math.random()?

If there's a possibility of having the Mersenne Twister be a part of this, or any new engine that may get created for it, that would be great too


use espeak cmd instead of espeak-ng on macOS

I made 3 changes in Line#35, Line#48 and Line#110~#126.
other changes are white space auto trimmed by my sublime-text, please ignore

Thanks for your review, I realize it's not the best solution to switch from espeak-ng to espeak on mac, since espeak is no longer developed on. but you get my point.
Feel free to close this PR if you don't like it. I hacked it for my project, since it's only on init.py file

Thanks for your review, I realize it's not the best solution to switch from espeak-ng to espeak on mac, since espeak is no longer developed on. but you get my point.
Feel free to close this PR if you don't like it. I hacked it for my project, since it's only on init.py file


Intel® Python XGBoost Performance sample readme update

Existing Sample Changes
Description
Restructured to match new template. Updated some formatting. Removed images since they reference a different sample. Added section on running the python script in local environment. Corrected some branding. Added information about looking at notebook to determine how to configure the two conda environments.
Fixes Issue#
External Dependencies
N/A
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[x] Documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] VSCode

Adding @jimmytwei for notices.


Keeping Homebridge Running

Hi There. I Have homebridge setup on my raspberry pi and ssh into it via a mac to execute it . However, If i quit terminal homebridge stops. If i leave terminal running then after a while it returns ssh lost: broken pipe and it stope homebridge. i have tried so many tutorials and none work . Please help!

you have to autostart homebridge
`Start at boot
Install PM2 module:
sudo npm -g install pm2
Now when PM2 is installed, it should work starting Homebridge with the following command:
pm2 start homebridge
Check if Homebridge is running by:
pm2 list
Or for a more detailed description of the process:
pm2 show homebridge
In the detailed description the logs are shown, where you can check if everything went as intended. Or use the log function of PM2
pm2 logs homebridge
Of course you want Homebridge to autostart on boot. PM2 has a command making this easy:
pm2 startup
And this would give you a command to run, depending on your system setup. This is an example from a standard PI Jessie dist.
You have to run this command as root. Execute the following command:
sudo env PATH=$PATH:/usr/bin /usr/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi
It is important that you save the current PM2 process list, it is done by the following command:
pm2 save
After this you should be able to reboot, and hopefully you have working Homebridge-installation starting at boot.
sudo reboot`

Im useing ffmpeg, sonos zp, and sony bravia
Heres the config:
{
"bridge": {
"name": "HomeBridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [
{
"platform": "Camera-ffmpeg",
"name": "Camera",
"cameras": [
{
"name": "OfficeCam",
"videoConfig": {
"source": "-f v4l2 -r 30 -s 1280x720 -i /dev/video0",
"maxStreams": 2,
"maxWidth": 1280,
"maxHeight": 720,
"maxFPS": 30,
"vcodec": "h264_omx"
}
}
]
},
{
"platform": "ZP",
"service": "speaker",
"brightness": true,
"speakers": false
},
{
"platform": "SonyBravia",
"name": "Living Room TV",
"ipadress": "xxxxxxxxx",
"psk": "xxxxxxx"
}
]
}

Did u try running homebridge as systemd daemon?
https://gist.github.com/johannrichard/0ad0de1feb6adb9eb61a/
You can run the service as root too if any specific plugin requires it

tried that. nothing happens

@aswathraja ^^^

if you are running as the systemd as in the gist, use the  command :
systemctl status homebridge
or extensive logs by
journalctl -a -u homebridge

systemctl status homebridge returns this
● homebridge.service - Node.js HomeKit Server
Loaded: loaded (/etc/systemd/system/homebridge.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2018-05-16 16:57:01 UTC; 8s ago
Process: 3843 ExecStart=/usr/bin/homebridge $HOMEBRIDGE_OPTS (code=exited, status=203/EXEC)
Main PID: 3843 (code=exited, status=203/EXEC)
May 16 16:57:01 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-7/7 (END)
journalctl -a -u homebridge returns this:
-- Logs begin at Wed 2018-05-16 08:49:59 UTC, end at Wed 2018-05-16 16:57:53 UTC. --
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homeb
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/E
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homeb
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/E
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homeb
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/E
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebrid
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebrid
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebrid
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file o
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file o
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file o
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or d
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or d
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or d
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or di
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or di
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or di
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or dire
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or dire
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or dire
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or direc
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or direc
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or direc
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or directo
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or directo
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or directo
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:49:59 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:09 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:09 raspberrypi systemd[2759]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or directory
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:09 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:19 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:19 raspberrypi systemd[2783]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or directory
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:19 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Service hold-off time over, scheduling restart.
May 16 08:50:29 raspberrypi systemd[1]: Stopped Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[1]: Started Node.js HomeKit Server.
May 16 08:50:29 raspberrypi systemd[2812]: homebridge.service: Failed at step EXEC spawning /usr/bin/homebridge: No such file or directory
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Main process exited, code=exited, status=203/EXEC
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Unit entered failed state.
May 16 08:50:29 raspberrypi systemd[1]: homebridge.service: Failed with result 'exit-code'.
lines 2-24

i would guess you didnt install hombridge using -g. Your homebridge is not installed in the specified path of usr/bin/homebridge please check where your homebridge is installed using the command :
which homebridge
and change the path of the ExecStart in homebridge.service file which you would have copied to the path : /etc/systemd/system/
You might want to change the User to root as well if it still fails to keep the state running

which homebridge returns this: /usr/local/bin/homebridge
How do i do the rest?

Navigate to the folder using
 cd /etc/systemd/system/
Then type sudo nano homebridge.service
Then in the text editor screen change theExecStart path to the correct path you found above
You can change the user too as I stated above in the same file, (if you didn’t create a new user for homebridge)

journalctl -a -u homebridge confirms it is now working but I get 'No Response' on my Home app.

Remove homebridge from ur home app and add it again as this a different instance of homebridge when the config.json is at /var/lib/homebridge/

now i removed it from the app it wont add it back

I had problems similar to this before but i am not really sure  if it would work
Possible Solutions : 1) Power Cycle my Pi (Plug out, and wait a few seconds and plug in back on)
2) Restart your phone and wait for home app to sync with all your devices on the apple id.

FWIW, I setup daemontools for this (https://cr.yp.to/daemontools.html) a couple of years ago and haven't had a single problem yet.  Keeps it running and restarts, no matter the underlying reason.


Latest Pull ALTER TABLE payment Error +  PayTo: pq: unexpected Parse response 'C'

There is a bug on the migration because its not compatible with the latest version of PostgreSQL version on type numeric that does not allow NOT NULL
Fix  SQL Migration from v0.1.0-beta2 to v0.1.1
Change:
ALTER TABLE payment ADD COLUMN total NUMERIC(18,8) NOT NULL;
To:
ALTER TABLE payment ADD COLUMN total NUMERIC(18,8) DEFAULT 0;
After that Im getting the error, still did not debugged why
2023/10/27 17:42:18 BalanceKeeper: ListPayments 'DDrHK26acgqY2f4bsSNR1bCyfcatmt8zP6': PostgresStore error: getPaymentOutputs: querying PayTo: pq: unexpected Parse response 'C'

I checked the Postgres docs, and I can't find anything saying a NUMERIC column cannot be NOT NULL, however, it's true that this will not work if you have any rows in the table (since in that case the added column would have NULL values)
I've re-written the migration now, because it actually didn't attempt to migrate existing data, which means it's not very useful as a migration.


[SHB] Setup serializable

Implement methods to serialize and de-serialize the components in a setup to and from json.

working on this on


Update CodeCov integration

CodeCov complains:
"❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more."
We need to start using https://github.com/apps/codecov instead, which I think can only be configured by @MichMich

The Codecov integration is useless at the moment because the reports are not correct, see e.g. discussion in this PR.
So as long there is no progress here in updating the integration we should disable the workflow for Codecov.
@MichMich @rejas

[2023-10-12T08:31:38.919Z] ['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
Error: Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 255

as CodeCov now fails with every run I will remove this integration.

With integration you mean the codecov github action? Yes to that. Would like to keep the npm script for creating that locally for now.

Closing this for now


Duplicate email welcome email and abandoned cart email

When I finished "Welcome Email" and "Load Abandoned Cart Email" sections in Amazon Pinpoint workshop, I can receive email but two email each.
https://github.com/aws-samples/retail-demo-store/blob/master/workshop/4-Messaging/4.1-Pinpoint.ipynb

Should be fixed by #450 .  Please reopen if you continue to see problems


feat: add image builder and dash cart

Added Service

EC2 Image Builder
Dash Cart

:tada: This PR is included in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can you add the interface to set the font path as external or internal file path instead of assets?

Hello,
Its very fantastic library I have ever used. Thanks for your hard works.
I am going to create the solution to replace the font in the application and this font will be downloaded from the server. Unfortunately, there is only interface to set the font path based on  assets folder. I think there is a way to load the font from the storage in Android SDK. I am guessing Typeface.createFromFile is the interface to use it.
Do you have plan to add such interface at this library? It will be so appreciated if you have the plan to add such useful interface. Please let me know your thoughts.
Thanks
LiuLei

dup #96


empty strings for env bools

I think empty strings should be the same as not defined, e.g.:
$ COLOR= mycli

Users commonly use an empty string in env vars like this since it's easier than removing them. I think potentially this could be configurable (somehow) like viper does.

as an example, if I want to set MISE_DEBUG and MISE_TRACE to the default I'd like to do the following:
MISE_DEBUG= MISE_TRACE= mise ...

but with the way confique deals with booleans currently I can't do this, I have to pick true or false


How I can use GPU mediapipe python

OS Platform and Distribution
20.04
Compiler version
No response
Programming Language and version
Python
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
No response
Bazel version
No response
XCode and Tulsi versions (if iOS)
No response
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
How I can use GPU mediapipe python?
Complete Logs
I can run mediapipe via pip install in Python env.

But it can be seen the `INFO: Created TensorFlow Lite XNNPACK delegate for CPU.`

How can I utilize my GPU? My platform is Jetson AGX Orin.

Any instruction?

Thanks.

HI @FunnyWii,
Currently, GPU support is available only on regular Linux and macOS (both Intel and Silicon). We do not support GPU on Jetson AGX Orin and other platforms.
To use the GPU on supported platforms, install the latest version of the MediaPipe package (0.10.14) with the command:
pip install mediapipe
Then, specify the GPU as the delegate in your code, as shown below for example Gesture Recognizer:
base_options = python.BaseOptions(model_asset_path='gesture_recognizer.task', delegate=python.BaseOptions.Delegate.GPU)
This ensures the example runs on the GPU.
Thank you!!

HI @FunnyWii,
Currently, GPU support is available only on regular Linux and macOS (both Intel and Silicon). We do not support GPU on Jetson AGX Orin and other platforms.
To use the GPU on supported platforms, install the latest version of the MediaPipe package (0.10.14) with the command:
pip install mediapipe
Then, specify the GPU as the delegate in your code, as shown below for example Gesture Recognizer:
base_options = python.BaseOptions(model_asset_path='gesture_recognizer.task', delegate=python.BaseOptions.Delegate.GPU)
This ensures the example runs on the GPU.
Thank you!!

Thanks for your reply.
Currently I've changed the platform into x86 Ubuntu.
import cv2
import mediapipe as mp
import Utils
import time
import socket

mp_holistic = mp.solutions.holistic
holistic = mp_holistic.Holistic()
mp_drawing = mp.solutions.drawing_utils

while cap.isOpened():
    success, image = cap.read()
    if not success:
        break
    start_time = time.time()

    image = cv2.resize(image, (1280, 720), interpolation=cv2.INTER_AREA)
    image = cv2.cvtColor(image, cv2.COLOR_BGR2RGB)
    image.flags.writeable = False
    results = holistic.process(image)

    image.flags.writeable = True
    image = cv2.cvtColor(image, cv2.COLOR_RGB2BGR)

  if results.pose_landmarks:
        mp_drawing.draw_landmarks(image, results.pose_landmarks, mp_holistic.POSE_CONNECTIONS)
    if results.left_hand_landmarks:
        mp_drawing.draw_landmarks(image, results.left_hand_landmarks, mp_holistic.HAND_CONNECTIONS)
    if results.right_hand_landmarks:
        mp_drawing.draw_landmarks(image, results.right_hand_landmarks, mp_holistic.HAND_CONNECTIONS)

My codes is shown below, but I don't know where to add the code you mentioned:base_options = python.BaseOptions(model_asset_path='gesture_recognizer.task', delegate=python.BaseOptions.Delegate.GPU)

Hi @FunnyWii,
The standalone code you shared uses the legacy holistic solution, which does not support GPU via pip. Support for legacy solutions has ended as they are now part of our new Task API. You can find the documentation here.
The holistic solution is now part of the Holistic Landmarker Task API. However, there is a known issue with GPU support for the new Holistic Landmarker Task API, so GPU can not be used with it. GPU support is available for other Task APIs. For more details on how to use GPU with Python, see this thread.
Thank you!!

Hi @FunnyWii,
The standalone code you shared uses the legacy holistic solution, which does not support GPU via pip. Support for legacy solutions has ended as they are now part of our new Task API. You can find the documentation here.
The holistic solution is now part of the Holistic Landmarker Task API. However, there is a known issue with GPU support for the new Holistic Landmarker Task API, so GPU can not be used with it. GPU support is available for other Task APIs. For more details on how to use GPU with Python, see this thread.
Thank you!!

https://colab.research.google.com/github/googlesamples/mediapipe/blob/main/examples/pose_landmarker/python/[MediaPipe_Python_Tasks]_Pose_Landmarker.ipynb#scrollTo=OMjuVQiDYJKF
https://colab.research.google.com/github/googlesamples/mediapipe/blob/main/examples/hand_landmarker/python/hand_landmarker.ipynb
Thank you!
I see the new solution for both Hand & Pose landmarker.
As the Holistic detection can't work with GPU, can I combine above codes in colab into one .py file  and input a same image to conduct the both Hand & Pose landmarker using GPU?

Hi @FunnyWii,
We have not tested this scenario and are unsure if it will work. We recommend using the CPU version of the Holistic Landmarker for now. We will inform you once we receive any updates about a fix.
Thank you!!


where am I wrong when using equation environment

Following this TeX.SE question, it was a good occasion to try your package !
However, when I simply try to apply it to equation environement, I get an error.
\documentclass{article}
\usepackage{atendofenv}

\begin{document}

 \begin{equation}
 G(s) = {X(s) \over U(s)} = {5 \over s^2 + 2 s + 3}
 \end{equation}

\AtEndOfEnv{equation}{$\square$}

\end{document}

Hi, it looks like you didn't include amssymb for the \square command.
\documentclass{article}
\usepackage{atendofenv}
\usepackage{amssymb}
\AtEndOfEnv{equation}{$\square$}

\begin{document}

 \begin{equation}
 G(s) = {X(s) \over U(s)} = {5 \over s^2 + 2 s + 3}
 \end{equation}

\end{document}

Please reopen this issue if there are other errors.

thank you for your answer !
now when i try with equation* env I get an error.
\documentclass{article}
\usepackage{atendofenv}
\usepackage{amssymb}
\AtEndOfEnv{equation*}{$\square$}

\begin{document}

 \begin{equation*}
 G(s) = {X(s) \over U(s)} = {5 \over s^2 + 2 s + 3}
 \end{equation*}

\end{document}

You forgot to include amsmath package, which provides the equation* environement


Connectors in Redux store proposal

We are planning to restructure the redux store for connectors as we have to access different data states to get all necessary values to e.g. display a connector card correctly.
We are getting all values from components.list, components.get and client.config.
For the frontend are the most important ones:

enabled from client.config
healthy from client.config
installed from components.list
configured from components.get

Right now we store the responses as followed:

client.config in data.config.components
components.list in data.catalog
components.get in data.connector

which means to get all needed values we need to access three different data states.
Current structure:

To keep the future of the frontend team easier and more efficient I would love to feed the connector data state with all necessary values so we just access connectors to get needed values.
e.g. suggested structure:

This suggestion misses the "installed" value as we discussed to remove the repository name from the response of components.list so we are more aligned with components.get and client.config.
Please feel free to add all your thoughts and suggestions 🙏

Hey @thorstenairy thanks for identifying and summarising the issue for us 🚀

To keep the future of the frontend team easier and more efficient I would love to feed the connector data state with all necessary values so we just access connectors to get needed values.

By this, you mean merging all action payloads from the other API calls into the connector data state, right?
This works for me, but I was wondering what you think about using redux selectors to create aggregate views the same way that we already do for conversations?

@chrismatix yes, exactly.
tbh, I like the redux selectors approach, totally forgot about that.
What you think about that @AudreyKj?

yes, I agree 👍
we're already using redux selectors in the Control Center to get components and connectors by source, so this is in line with our current approach

@thorstenairy in which PR was this completed? :)


Coord trafo

added a module that contains some low-level coordinate transformation functions to bring various coordinate systems into the convention that is expected by my reconstruction tools -- i.e. right-handed x-y-z coordinate system with z->upwards and phi and theta in the standard (?) definitions: theta, angle to z-axis and phi, angle in the x-y-plane from the x-axis towards the y-axis.
By this approach, assuming that azimuth is measured from north towards east, the x-axis points north and y points west, so phi = -azimuth.
The camera coordinates are mirrored along the x-axis, so that y points "up" and x to the "right", as it is expected by pixel_position_to_direction.

could you move the /utils/coordinate_transformations.py file to /coordinates/? It makes more sense there


Errors in running posix filesystem conformance tests

While running the posix filesystem conformance tests (https://github.com/pjd/pjdfstest), we are getting the following errors
Test Summary Report
-------------------
./tests/chmod/12.t          (Wstat: 0 Tests: 14 Failed: 6)
  Failed tests:  3-4, 7-8, 11-12
./tests/link/00.t           (Wstat: 0 Tests: 202 Failed: 10)
  Failed tests:  135-136, 142-143, 149-150, 156-157, 163-164
./tests/mkdir/00.t          (Wstat: 0 Tests: 36 Failed: 2)
  Failed tests:  33-34
./tests/mkfifo/00.t         (Wstat: 0 Tests: 36 Failed: 2)
  Failed tests:  33-34
./tests/mknod/00.t          (Wstat: 0 Tests: 36 Failed: 2)
  Failed tests:  33-34
./tests/mknod/11.t          (Wstat: 0 Tests: 28 Failed: 4)
  Failed tests:  12-13, 25-26
./tests/open/00.t           (Wstat: 0 Tests: 47 Failed: 2)
  Failed tests:  33-34
Files=232, Tests=8789, 704 wallclock secs ( 1.69 usr  1.17 sys + 21.37 cusr 276.72 csys = 300.95 CPU)
Result: FAIL

This is the setup that I am using:
# `kata-env`

Output of "`/usr/local/bin/kata-runtime kata-env`":
```toml
[Meta]
  Version = "1.0.18"

[Runtime]
  Debug = true
  Path = "/usr/local/bin/kata-runtime"
  [Runtime.Version]
    Semver = "1.3.0"
    Commit = "d00742f43f3fb1177e74d864e47a1bae697c2d73"
    OCI = "1.0.1"
  [Runtime.Config]
    Path = "/usr/share/defaults/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 2.11.0\nCopyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-lite-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = true
  UseVSock = false

[Image]
  Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.3.0_agent_042c3ebd71c.img"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-4.14.67-13"
  Parameters = "agent.log=debug"

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.3.0-6ddb006ad3f709cab018af9dc0bf9e756c3ce2cd"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = true

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.3.0-5fbf1f0919ce0bb1f2b7e85692cdf3058023926f"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = true

[Agent]
  Type = "kata"

[Host]
  Kernel = "4.15.0-1023-azure"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = false
  [Host.Distro]
    Name = "Ubuntu"
    Version = "16.04"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz"

[Netmon]
  Version = "kata-netmon version 1.3.0"
  Path = "/usr/libexec/kata-containers/kata-netmon"
  Debug = true
  Enable = false

Thanks for the report @GabyCT - are you going to dig into those to work out why they fail?

@grahamwhaley yes, I will take a look

Just to be clear then, we are noting that 9pfs has a lot more failures than devicemapper, yes?
(which, is not unexpected I think, and possibly not something we can do too much about ;-) )

Yes, overlay2 has 34 failures and devicemapper only 2 failures

@jodh-intel , I already submitted a PR https://github.com/kata-containers/tests/pull/815 :)

@GabyCT - thanks!


The use element now can point to an external file

Just added a second argument to the method, the SVG file path/url.

Please add specs. I will accept it then.

@Fuzzyma
Sorry for the delay, specs created and update the Readme.

meeh - its not mergeable anymore :/. Can you do a rebase to the current working state?

@Fuzzyma
I was in doubt on doing this in the right way, but when I discard the dist and merged there was no conflict, and then I generate the dist and commit again.
Hope is the right move.

Actually I have no idea :D. I am no git pro either.
I saw that you merged the current master branch into you branch. In my opinion it should be the opposite. You merge your branch into the master and not the other way round.
When I create a PR I usually create a new feature-branch where I put my changes so that I can pull the newest master every time and have my changes in a different branch. But I am sure there are 100 other ways doing this.
I dont know what will happen when I merge this now. Thats why I have to doublecheck that.
Maybe its the best possible solution when I just do the changes on the code and mention you in the changelog instead (?). That would save me from merging something without knowing what will happen

If you look at the files changed, it just have the changes that I made, not removing any additional code, besides that, all tests are ok to. If you really are in doubt, you can rollback after the merge.


Microsoft/users/nikhilku/taskhelpcleanup

Updating Help Text for Tasks as per PM feedback

Signedoff on Code flow


[FEATURE] Implement pull-to-refresh and sync authman groups

This issue is related to https://github.com/rokwire/illinois-app/issues/2059.

Done


docs: package-name needs to be quoted if scoped

The README.md example release-please.yml sets package-name: release-please-action.  This is good for unscoped packages but for package-name: "@myorg/package" it is mandatory to quote the scoped package name.  This tripped me up the first time I attempted to use this package.  Partly because I'm not super familiar with yaml parse rules so creating yaml files is often copy-pasta for me.
I'm not sure if you want to just quote the release-please-action in your example or add a comment?  I can post a PR if you let me know how you want this handled.

@coreyfarrell perhaps we could add a note that both mentions that package-name is optional for some types of releasers, e.g., node which reads it from package.json, and that you my want to use a quoted string if you have special characters.


fix: connect to ledgers on startup in iOS release environments

Signed-off-by: James Ebert<EMAIL_ADDRESS>Summary of Changes
As I mentioned in this morning's Bifold User Group call, here's the fix we've identified for allowing us to connect to multiple ledgers at agent initialization in iOS release environments (AFJ issue #647). This should improve the first issuance time performance (to match that of subsequent issuances). I've got more documentation and notes to add (hence the draft status), but if I could get a test to ensure this works on your end first @jleach that'd be really helpful.
Related Issues
https://github.com/hyperledger/aries-framework-javascript/issues/647
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

Akiff has verified this is working as expected, and appropriate documentation is being added to AFJ


Added some phpdocs comments to emotion controller

1. Why is this change necessary?
It helps IDEs to provide better autocompletion.
2. What does this change do, exactly?
Adds two lines of phpdoc and two use statements.
3. Describe each step to reproduce the issue or behaviour.
None.
4. Please link to the relevant issues (if any).
None.
5. Which documentation changes (if any) need to be made because of this PR?
None.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-19751.
Please use this issue to track the state of your pull request.

Hi @jkrzefski, your PR just got merged (https://github.com/shopware/shopware/commit/1a4d7bfbf686b8273b4a88b4910bd24ea71d8aa9) , thank you for your help making Shopware better! 💙


Values link  typo

templates/_helpers.tpl:
Line 82:
.Values.externalDatabase.config.auth.user
should be:
.Values.externalDatabase.config.auth.username
Just additional question - do we really need .Values.externalDatabase.config.auth.password ? It isn't used anywhere.

Yes you're right regarding the user -> username part, feel free to submit a PR, if not, I can fix when I'm free (which shouldn't be too long)
On the password point, is also a good point, I think there's just a missing condition here that checks if the .Values.externalDatabase.config.auth.password field is present, and if so, to use it.


Decals only show up when the gbuffer pass is enabled.

To reproduce: Comment out #define TRACE_FROM_GBUFFERS in SPLASH/res/shaders/dxr/Basic.hlsl

Decals might be able to show with pure Ray Tracing but requires a different approach. Current implementation uses depth, color and normals from G-buffer pass.


Reopen With on the Welcome Page causes an error toast

Testing https://github.com/microsoft/vscode/issues/81698
Unable to open 'vs_code_welcome_page': No file system provider found for walkThrough:/c%3A/Users/alros/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/workbench/contrib/welcome/page/browser/vs_code_welcome_page?%7B%22moduleId%22%3A%22vs%2Fworkbench%2Fcontrib%2Fwelcome%2Fpage%2Fbrowser%2Fvs_code_welcome_page%22%7D.

Same goes for the settings editor.

Interesting.
In addition to fixing this case, we should only show the reopen with command if there is at least one custom editor available. Marking for October


Multi cast use case

now that multi cast support is added we should include it in the use cases

closed with #521


bot: expose ProcessUpdate and add Synchronous mode to support AWS Lambda

(Please review individual commits. The last one that adds offline testing mode is incidental.)
AWS Lambda is well suited for running a Telegram bot. (See Go examples.) To use it I need to make a function that handles one Telegram update and returns. It has to handle the update until completion since Lambda can kill the program as soon as the function passed to lambda.Start returns: this is why we need the synchronous mode that waits for the user handler. This PR makes telebot suitable for such a use:
package main

import (
	"github.com/aws/aws-lambda-go/lambda"
	tb "gopkg.in/tucnak/telebot.v2"
)

func main() {
	bot, _ := tb.NewBot(tb.Settings{Synchronous: true})
	lambda.Start(func(u tb.Update) error {
		bot.ProcessUpdate(&u)
		return nil
	})
}

I really liked you added the offline mode! Seems pretty useful.
But do we actually need additional closures like here?
func(b *Bot, handler func(*Message), m *Message) {
     b.runHandler(func() { handler(m) })
}(b, handler, m)

I've remove the closures, and changed the signature of ProcessUpdate to take Update instead of *Update since in asynchronous mode it would not be safe to capture the pointer if the user calls ProcessUpdate multiple times with a pointer to the same Update struct (with different content). (I could have keep func (b *Bot) incomingUpdate(upd *Update) and added func (b *Bot) ProcessUpdate(upd Update) { incomingUpdate(&upd) }, but this does not seem useful enough.)

Could you point out the changes that do not feel quite right, so that I would think about them some more?

I have added a fully functional minimal example (extracted from my bot): this seems more useful than just an outline. For example, the value that the function started with lambda.Start receives depends on the kind of AWS API Gateway (HTTP, REST, v1 or v2), so it helps to have a declarative and reproducible AWS configuration alongside the code.

That said, how does Lambda work for you?

This is my first Lambda project, perhaps I shall tell how it works out in a few months. Lambda seems perfect for my use case because I do not maintain a dedicated server where I could co-host my bot, and because I expect very low usage. It may cost under a cent per month.

I have added Synchronous=true to TestBotIncomingUpdate: now all settings are tested and the asserts in its handlers run within the test.

It is solid. Thank you so much and sorry for the wait!

I want to give this a try - but I don't quite understand how the lambda is being called.
It's not like I we are telling telegram the URL - and there is no poller.


Snapping window to top extends window beyond screen

Snapping window to top extends window beyond screen. Also, the program won't recognize snapping as "extending window to full screen" and after clicking Maximize button, program resize window to full screen (this time properly).

https://github.com/newbiedeveloper9/sharpdj/commit/f3d45bf3bc39f92c85f0f62b19792b86463f383b


people tracking skeleton

Hi,
First off, I appreciate for good solid people tracking system! I am enjoying working with it now! :) Although it wasn't easy for novice, beginner to install despite of its well written description.
Since it's running very smoothly, I want to do something more with it. more challenging. 2 questions:

Can it detect for z-axis? people jumping for instance?
Is it possible to integrate with gesture detection like what normal Kinect do?
(I saw from one of your movie showing tracked data of skeleton people walking around. )

This seems more like requests and question rather than an issue, but I didn't know where to put it.
Thank YOu! :)
rcp

Can it detect for z-axis? people jumping for instance?

yes - provided you have set the ground plane, it will report centroid shifts. IE - jumping.

Is it possible to integrate with gesture detection like what normal Kinect do?

not out of the box. By design, OPT reports centroid, not skeleton or hands. Even if one did the (significant) development effort to integrate the skeletal detection, the range of the 'gesture' detection would be smaller than the overall integrated tracking area for OPT.
If you really want a skeleton or gesture, fastest path is to set up a 2nd kinect, and use a different codebase to do feature detection. The UDP of centroid, and coordinate space of the kinect, could indeed be manually calibrated for gesture.

@nanodust,
Thanks for the reply! I have provided ground plane(something that has been done during calibration). I was wondering if there is any setting to enable z-axis data.
according to data description,
"{"header":{"seq":71251,"stamp":{"sec":1415305737,"nsec":110138944},"frame_id":"world"},"tracks": [{"id":387,"x":-0.89131,"y":2.41851,"height":1.55837,"age":29.471,"confidence".0500193}]}"
it only provides x,y coordinate. use height? perhaps?

Yes, height
On Feb 16, 2016 8:08 PM, "cherltte"<EMAIL_ADDRESS>wrote:

@nanodust https://github.com/nanodust,
Thanks for the reply! I have provided ground plane(something that has been
done during calibration). I was wondering if there is any setting to enable
z-axis data.
according to data description,
"{"header":{"seq":71251,"stamp":{"sec":1415305737,"nsec":110138944},"frame_id":"world"},"tracks":
[{"id":387,"x":-0.89131,"y":2.41851,"height":1.55837,"age":29.471,"confidence".0500193}]}"
it only provides x,y coordinate. use height? perhaps?
—
Reply to this email directly or view it on GitHub
https://github.com/OpenPTrack/open_ptrack/issues/72#issuecomment-184975763
.


No sort objects

The code is checked:
if (!is_array($content)) {
throw new \InvalidArgumentException('Variable passed to the sortByField filter is not an array');
}
and no sort objects

I'm not quite sure what you are trying to tell me. The filter do support sorting of objects https://github.com/victorhaggqvist/Twig-sort-by-field/blob/master/test/SortByFieldExtensionTest.php#L106.

I'm not quite sure what you are trying to tell me. The filter do support sorting of objects https://github.com/victorhaggqvist/Twig-sort-by-field/blob/master/test/SortByFieldExtensionTest.php#L106.


[elixir] fix: processing of ODS loads without snapshot load

This PR addresses 2 bugs:

Stop any queries from running for tables that haven't had any loads come through.
Prevent the ingestion of loads that don't have a snapshot load. Due to deployment (one container coming online and the other offline), some sort of race condition has occurred where some tables lost out on their snapshot loads being inserted. I believe it has to do with this filtering logic. I haven't been able to reproduce locally, but this bug fix addresses this bad state, which can also occur by Cubic sending over data that we don't understand, such as an update in the name of the snapshot load file. Currently, CT loads are going to the error bucket because they don't have they don't have have destination, due to the missing snapshot.

Lastly, I'm planning on addressing the filtering logic of the new load objects to have it be more inclusive, and look back further (maybe an hour). This will be in another PR.

If you can't reproduce the issue, and everything is working with the smaller Qlik batches, do you still need to make this change?

If you can't reproduce the issue, and everything is working with the smaller Qlik batches, do you still need to make this change?

This code protects the integrity of the process further, so I'd like to deploy it.


fix(config): add metadata to 0x0258: Shenzhen Neo Siren Alarm

PR description here
0x0258 - Shenzhen Neo Siren Alarm.txt
Adds values for Alarm and Doorbell Sound Selection

Sorry about the mistake.  I am totally new to this and am trying to contribute the additional details contained in the file I attached.  If you can guide me in the right direction, I will be happy to create an actual merge file or fix whatever error I made... or please pass the info to someone who knows how to do it correctly.

Ok, I'm assuming you actually wanted to add the mapRootReportsToEndpoint compat flag? Can you share some details why this is necessary?

Below is the stuff I wanted to add to 0x0258: Shenzhen Neo Siren Alarm.  It appears like I made the pull request in the wrong place?  My additions aren't to compatibility flag but to the configuration file.  What I attached was the entire modified file.  Sorry about the ignorance.
	{
		"#": "2",
		"label": "Alarm Duration",
		"valueSize": 1,
		"minValue": 0,
		"maxValue": 255,
		"defaultValue": 2,
		"options": [
			{
				"label": "Off",
				"value": 0
			},
			{
				"label": "30 seconds",
				"value": 1
			},
			{
				"label": "1 minute",
				"value": 2
			},
			{
				"label": "5 minutes",
				"value": 3
			},
			{

NEW:					"label": "Always on",
"value": 255
}
]
},
ALL VALUES BELOW ARE NEW:
{
"#": "5",
"label": "Alarm Sound Selection",
"valueSize": 1,
"minValue": 1,
"maxValue": 10,
"defaultValue": 9
"options": [
{
"label": "Doorbell",
"value": 1
},
{
"label": "Fur Elise",
"value": 2
},
{
"label": "Westminster Chimes",
"value": 3
},
{
"label": "Ding Dong",
"value": 4
},
{
"label": "William Tell",
"value": 5
},
{
"label": "Rondo Alla Turca",
"value": 6
},
{
"label": "Police Siren",
"value": 7
},
{
"label": "Evacuation",
"value": 8
},
{
"label": "Beep Beep",
"value": 9
},
{
"label": "Beep",
"value": 10
}
]
},
{
"#": "6",
"label": "Doorbell Sound Selection",
"valueSize": 1,
"minValue": 1,
"maxValue": 10,
"defaultValue": 10
"options": [
{
"label": "Doorbell",
"value": 1
},
{
"label": "Fur Elise",
"value": 2
},
{
"label": "Westminster Chimes",
"value": 3
},
{
"label": "Ding Dong",
"value": 4
},
{
"label": "William Tell",
"value": 5
},
{
"label": "Rondo Alla Turca",
"value": 6
},
{
"label": "Police Siren",
"value": 7
},
{
"label": "Evacuation",
"value": 8
},
{
"label": "Beep Beep",
"value": 9
},
{
"label": "Beep",
"value": 10
}
]
},

Looks like you selected the wrong branch to merge:

This is a branch our bot created last August and edits an entirely different file.

Oh... I just realized you attached a file in the OP. A pull request is usually done in separate steps:

you fork the repository into your account
you make the edits in your fork, ideally in a new branch
you create a pull request from your branch

https://docs.github.com/en/get-started/quickstart/contributing-to-projects has a beginner-friendly explanation of the process.

Also, I recommend starting in the config browser and using Gitpod to edit files:

OMG.  I think I got it!  at least I hope...  Thanks for the help


Core: Use Multiple Parse Results

This PR is a work of progress and currently blocked by #2045
As preparation for the plugins system, we need to change the parser trait signature and the producer stream to return multiple parse results at once instead of returning them one by one.
The idea behind that to let the parsers plugins parse all the available bytes and return all the results to the host at once.
The changes include:

Parser::parse() returns impl IntoIter<Item = ParseResult> + Send to avoid affect the performance of current parsers, because we can use iter::once() with them, which help the compiler to do more optimization since it knows at compile time that the results are one item only.
Producer Stream returns a vector of results because there is one possible implementation for it and it's using vectors to store the results.

Road Map:

[x] Change Parser::parse() and Producer::as_stream() signatures to return multiple results ate once.
[ ] Make sure all parsers stop on the first potential error they encounter.
[ ] Cover all edge cases with unit-tests after #2045 is merged
[ ] Apply benchmarks on the this PR to make sure there is no performance loss

This PR can be closed because it will be replaced with new implementation based on unit tests & local benchmarks


Use assisted installer admin kubeconfig if exists

Currently the deployment manager service uses the admin kubeconfig that was used to register the cluster with ACM. But this will not exist if the cluster was created with assisted installer. To avoid that problem this patch changes the service so that it first check if the secret used by the assisted installer exists. If it does exist then it will use it.

/lgtm

/lgtm


[Branch-0.7] Support for Zeppelin Context redefinition on Python

Fixes a build problem in Zeppelin branch0.7.
Hotfix.
same pr #2207

I'll merge it as hotfix into branch-0.7

Merged. Please close this PR manually


Suggestion: add an option to show line numbers in editor

This would aid in debugging.

it exists already! see help->keyboard shortcuts: Esc L (small or large L without shift key).


non-Bearer token schema

Your environment:

Python version: 3.6
Operating System: Ubuntu 16.04

Problem description
I'm not sure it is an issue or not.
With the credentials_required=False flag, the client is allowed to send the non-Bearer token schema.
Steps to reproduce
Run the login_required.py.
Make a request:
$ curl \
--header "Authorization: InvalidSchema eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VybmFtZSI6InVzZXIwIn0.-zSBJbSBFhESOcrfPCzHkoHIMJ653jcBcUwodNR0Ko8"\
localhost:8080/protected

Yes it is an issue. Would you like to send a pr? Fix is easy.


Update course dates web fragment link.

LEARNER-2923
Description

Introduced a separate course dates fragment

Please refer to jira story for more details.
Future plans
After implementation of following server side story we shall stop to apply javascript on course dates fragment url.
LEARNER-3206

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6368e96). Click here to learn what that means.
The diff coverage is 0%.

@@           Coverage Diff            @@
##             master   #1024   +/-   ##
========================================
  Coverage          ?   17.9%
  Complexity        ?    1043
========================================
  Files             ?     472
  Lines             ?   19375
  Branches          ?    2199
========================================
  Hits              ?    3469
  Misses            ?   15510
  Partials          ?     396

Impacted Files
Coverage Δ
Complexity Δ

.../java/org/edx/mobile/view/CourseDatesFragment.java
0% <0%> (ø)
0 <0> (?)

.../java/org/edx/mobile/view/CourseDatesActivity.java
0% <0%> (ø)
0 <0> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6368e96...27146db. Read the comment docs.

forgot to tag you, cc: @staubina


remove partial duplicate eigen3 rosdep rule

Both of these rules are defined above in the eigen tag. The eigen3 tag looks to have been added in a sweeping update for gentoo and then changed in a sweeping fedora update where it should have been merged with the existing entry.
From this question

This will probably break some packages for some users, right (as in: rosdep will not be able to resolve their build_depend on the eigen3 key)? Should this be announced, or too minor?

This would only effect purely fedora and gentoo users. And anything released or with CI will have already failed due to the lack of ubuntu and debian rules. Clearly it could break a few, but the fix is easy and relatively easy to discover so I don't think it's worth a large broadcast that won't effect most people.
We should find a way to make these sorts of discussions more visible and with better history.

A post in the release category on the discourse site doesn't seem overly 'broadcast'?

Yeah, that's probably a good location. Maintainers are a good target audience as they're the most likely to be affected.

+1; looks good to me

Here's the post I made 3 days ago.
@ros/rosdistro-maintainers for review?


Added missing error check

Description
Added missing error check
Fixes #242
Type of change

Bug fix (non-breaking change which fixes an issue)

Codecov Report

Merging #262 into master will decrease coverage by 0.08%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #262      +/-   ##
==========================================
- Coverage   45.52%   45.43%   -0.09%
==========================================
  Files          15       15
  Lines        1518     1521       +3
==========================================
  Hits          691      691
- Misses        818      821       +3
  Partials        9        9

Impacted Files
Coverage Δ

storage/storage.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fd18831...6a73e89. Read the comment docs.


New volunteer, register, then see sign confidentiality agreement call to action at top of page.

Feature Description

During registration, once the user account is created, the user can only go to the pending page until their volunteer account is approved by an admin.
Once their account is approved, and they can login, if they have not signed the agreement they should see a call to action to sign the confidentiality agreement at the top of the page.
Expected solution

Testing

Closing this, it can be handled by #207