[Integration] Publish Zulip App on Zapier Directory

Background
There is a Zapier integration as documented here: https://zulip.com/integrations/doc/zapier
Currently it requires the user to use the invite link listed on this page to gain access to the Zulip app in Zapier.
Compared to other apps where the user simply searches for them in Zapier's app directory.
Proposed Changes
It would make it significantly easier for future users to find the integration if it was listed in Zapier's app directory.
Here is the app publishing process, we are currently on step 2, with an open beta invite link.

The next step is detailed in here:
https://platform.zapier.com/partners/lifecycle-planning#3-publish-your-integration-to-the-app-directory
We would need to submit the app and once it is approved it will be publicly available.
The email listed on the zapier invite was<EMAIL_ADDRESS>so I suppose he has control over the zapier app.

Issue resolved
https://zapier.com/apps/zulip/integrations


non alpha characters in node-ids

I geht "syntax error in line ..." when putting non-alpha-characters like "-" (minus) oder äöü (german Umlaute) in the label text or the id of a node.

nb: the error shows in the browser on the place where the component should be rendered.

The reason for the problem you mention is that viz.js, which does the actual graph generation, thinks that the input is invalid.  However, those characters seems to work for me.
One thing that is important when using special characters is to ensure that they are enclosed with "", i.e. in Java use node1.setParam("label", "\"Label!\"");. By default viz.js should handle utf-8 encoded strings. If this has been changed somewhere that can cause problems. See [http://www.graphviz.org/doc/info/lang.html] for more info on accepted character encodings.

Thanks Pontus, this works like a charm! I'll close the issue.
Anyway it would be great if you could just hide this behaviour from viz.js and offer the possibility to pass plain strings in your methods. Thanks!

Great that it worked. Yes, you're right that it would be better if this was handled automatically. This is something that should be addressed in the next version.


luci-app-statistics: more extensibility

Hi all, hi @jow-,
I recently wrote my own collectd plugin and I wanted to be able to display the resulting data in OpenWrt using RRDtool. Of course luci-app-statistics doesn't support my collectd plugin, and there isn't currently a way to non-intrusively add support for new collectd plugins to luci-app-statistics. Therefore I decided to create this PR to make it possible to extend luci-app-statistics without modifying the source code.
Today there's a .lua file for every supported collectd plugin in /usr/lib/lua/luci/model/cbi/luci_statistics. To add support for a new plugin one needs to add a new model there, but one also needs to add a bit of extra information in some hard-coded tables in the luci-app-statistics source code. The idea is to load this information from files in /usr/lib/lua/luci/statistics/plugins instead. A third-party developer can then simply dump some .lua files in those directories and luci-app-statistics will pick them up; zero source code modifications are necessary. It should also work nicely with package managers: you can package your collectd plugin with these two lua files and things will just work.
What do you think about the idea? I haven't done a lot of Lua before, so I'd be grateful for any comments you might have!

Looks pretty good in principle.
But the translations for the labels are missing.
@jow Also I would rather write the configuration directly in future from the collectd because luci-app-statistics did hijack the config generation. I have already prepared add a uci binding to collectd. See https://github.com/openwrt/packages.

@feckert - feel free to implement these changes, I don't have enough time to take care of this at the moment.

Also please rebase your change with git rebase -i HEAD~5 and then add a fixup to the last 4 commits in the vi. After that make a git push --force. We do not need the extra commits.

@feckert - feel free to implement these changes, I don't have enough time to take care of this at the moment.

Ok i could/will do that. The configuration is on some corners of collected difference to the luci-app-statistics configuration. Is this a Problem? Do we need a upgrade script for this cases?

Also please rebase your change with git rebase -i HEAD~5 and then add a fixup to the last 4 commits in the vi. After that make a git push --force. We do not need the extra commits.

It should be OK now.

I like this change, LGTM.

I will do some test and if this is OK i will merge this in the next hours

I have made some test and it works as expected.
Thanks or your work

@mberndt123 I'm afraid I missed it!
Next time, please add a signed-off-by: to your work:
@jow- Sorry I was going too fast :-(
I think I need to do a checklist of what I need to consider.


Update react modal demo page

Summary:
React Community Modal Page doesn't have the updated details about closeTimeoutMS={n} and contentLabel="Modal"
Additional notes:
Please update the page to show the latest features

👍


oneDNN: 2.1 -> 2.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/oneapi-src/oneDNN/releases.
meta.description for oneDNN is: "oneAPI Deep Neural Network Library (oneDNN)"
meta.homepage for oneDNN is: "https://01.org/oneDNN"
meta.changelog for oneDNN is: "https://github.com/oneapi-src/oneDNN/releases/tag/v2.1.2"
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/2ae74414f5f68796a0c544804ca2821d

du listing: https://gist.github.com/f30f1f2d33527c1e3934b25a6f6d5cff

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
oneDNN

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3prkdwhwl6xqy9hpjs0jcq8m1f0chliw-oneDNN-2.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A oneDNN https://github.com/r-ryantm/nixpkgs/archive/9fdad32b5747daa6df170101386c324eaf7bcdd6.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3prkdwhwl6xqy9hpjs0jcq8m1f0chliw-oneDNN-2.1.2
ls -la /nix/store/3prkdwhwl6xqy9hpjs0jcq8m1f0chliw-oneDNN-2.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dnnl (oneDNN)

Maintainer pings
cc @alexarice @bhipple for testing.

Result of nixpkgs-review pr 116163 1

1 package built:
- oneDNN


UATv0.3.3 | Join a case , Complainant Advocate

In case a complainant advocate joins a case, on successful joining, he/she is prompted to 'Confirm Attendance in Summon.'
Steps to reproduce:

File a complaint as a complainant
Do not add an advocate
Complete payment
Complete scrutiny
Complete case registration
Join case as Litigant advocate
See success message of join a case flow

Expected behaviour:

For the complainant's advocate, button should read 'View Case'
Clicking on view case should redirect user to case.

Hi @Taherabharmal, when any person join the case after hearing is scheduled, they should also be party of the attendees list in the scheduled hearing. Confirm Attendance action let them to join hearing from the frontend after they join case.
cc: @anirudh-0 @Ramu-kandimalla

This should not shown for Complainant
Change label to "Confirm Summons Receipt" or "Confirm Notice Receipt"

Complainant Advocate - Add advocate silently, donot ask for "confirm receipt option"; directly take them to view case by clicking on view case button
Accused Advocate - Confirm Notice/Summons receipt - to exist

Hi @nitish-beehyv  Confirm receipt button is not showing for respondent & respondent Advocate.
Ref,
https://jam.dev/c/9e07d4db-a8ce-4905-b14a-f75e97c829c5
https://jam.dev/c/26f6d4de-e28d-4c97-9b6d-659a5e274f1d

Hi @Beehyv-Vinod please retest and verify it.

Hi @Ramu-kandimalla @rajeshcherukumalli As discussed with @nitish-beehyv Tested in Dpg-Dev, Below are working as expected,

Verify that Confirm Notice/Summons Receipts is showing for the respondent when respondent join the case --https://jam.dev/c/bc1977f2-ff22-4d15-822e-65142548daa2
Verify that Confirm Notice/Summons Receipts is showing for the Respondent Advocate when respondent join the case --https://jam.dev/c/47f6e80e-675f-498c-94e9-3387760cdfd9
Verify that Confirm Notice/Summons Receipts is showing for the Respondent's Advocate when New advocate replace existing Advocate -- https://jam.dev/c/46ce0311-4962-4d14-8c4a-5c87a62d5352
Verify that Primary advocate has the access to the case for which new advocate replaced primary one --https://jam.dev/c/77b1b817-8095-41f8-8e1f-0e7f387d315b
Verify that Confirm Notice/Summons Receipts button is showing for the Complainant when Complainant join the case -- https://jam.dev/c/16bf68f2-4132-45a6-baec-4ae3abeab7df
Verify that Confirm Notice/Summons Receipts button is showing for the Complainant Advocate when Advocate join the case --https://jam.dev/c/d4926f14-786f-4a34-b813-67f1f4bdcdf5

Hi @Ramu-kandimalla @rajeshcherukumalli  Tested in UAT environment, Working as Expected.


Dev mode for making AnnoMate Reviewer

Annoying to have to keep deleting the pickle file when developing a reviewer
Include some kind of reviewer environment that can override the pickle file

https://github.com/getzlab/AnnoMate/pull/26


I realise I can use the built-in Name component provided by Bevy.

I realise I can use the built-in Name component provided by Bevy.
Originally posted by @tqwewe in https://github.com/jakobhellermann/bevy-inspector-egui/issues/48#issuecomment-1038851775
Can you give an example?

        .insert(Name::new("player".to_string()))


[Feature request] Auto Sidebar Per Page

Clear and concise description of the problem
The auto sidebar feature of the default theme is quite useful, especially in cases where the pages are autogenerated documentation from something like TypeDoc.
Currently you can only use the auto feature on all pages or manually specify the sidebar for every page. It would be great if you could turn the feature on per page as well.
I was able to hack it to make it work for the data-grid-vue site using vue router nav guards but its not maintainable and would probably be pretty easy to implement in the theme unless the changes to not use the vue router are going to make the auto sidebar feature more difficult to implement in general.
https://github.com/nruffing/data-grid-vue/blob/main/vuepress/.vuepress/client.ts#L63
Suggested solution
Implement passing 'auto' to a SidebarConfigArray for a given page in the theme's config object.
We could also change SidebarConfigObject to allow a string directly.
export type SidebarAuto = 'auto'
export type SidebarConfigObject = Record<string, SidebarConfigArray | SidebarAuto>

sidebar: {
  '/guide/': [
    {
      text: 'Guide',
      children: [
        '/guide/README.md',
        '/guide/columns.md',
        '/guide/sorting.md',
        '/guide/filtering.md',
        '/guide/paging.md',
        '/guide/more-coming-soon.md',
      ],
    },
  ],
  '/generated/': 'auto'
  '/dotnet-generated/': 'auto',
},

Alternative
No response
Additional context
No response

@meteorlxy @Mister-Hope thoughts?  I can put up a PR for this if we want to try this out.

LGTM

You may check other features in.my theme hope, this feature is called heading in my theme.


Fix: WKWebview is release

Description
Fixes #774
We can not use structures and @Property to setter . And must use __block
Otherwise，wkwebview might deallocate before we ask for user Agent
Compatibility

OS
Implemented

iOS
✅

Checklist

[x] I updated the iOS files (RNDeviceInfo.m)

Thanks for working on this @RoJoHub ! I found that I was able to reproduce this by simply altering the example app from this repo to have a few calls to getUserAgent in a row, were you able to reproduce this first, and then verify it still works and you no longer reproduce it afterwards?
My only suggested change is really small - just to consolidate the nil of webview to one spot after the function call, what do you think?

Hi, I created a demo to reproduce this problem.
Demo is a very extreme example, and it is like a Black-Box Testing.
In the demo, I checked the reference count and broke the error.
Only the setWebViewWithBlock method runs normally.
Please experience my demo.
https://github.com/RoJoHub/wkviewDemo

released as 5.6.3 🚀  - thanks again

released as 5.6.3 🚀 - thanks again

WOW. Thanks


Using Adonis notification with Adonis permission package

Question
How can i use the notifications package with the permissions package. Particularly how will i be able to compose the extends behaviour on the user model for both the notifications mixin and the permissions mixin
Package version
2.0.3

Its done just by listing the Mixin in the compose function separated by a comma , . I just needed to do some reading. Sorry for the extra post


Initial page wrapper for the member Account page.

new Account page with:

header with basic info about user
sidebar with links to expected base pages

Includes:

new fields for the user profile
fixes for avatars to actually display the user's initials.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

13 of 18 (72.22%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 80.475%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/Entities/User.php
3
5
60.0%

app/Controllers/Account/AccountController.php
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

app/Entities/User.php
1
82.86%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
1084

Relevant Lines:
1347

💛  - Coveralls


TURN support/help?

Thank you for this wonderful code, by the way!
I'm trying to pass STUN and TURN servers, but WebRTCModule throws an exception about the TURN format, which is typically:
{
credential:"ivZhTedeY+XEMHZeB+ZayL70aoY=",
urls:["turn:my.turn.server:3478"],
username:"1461261865"
}

WebRTCModule borks on line 120, saying it can't find key "url" in dynamic object.
iceServers.add(new PeerConnection.IceServer(iceServerMap.getString("url")));

I think my TURN server format is right, but please correct me.
I've also tried reformatting it to add the URL key, but it isn't authenticating as it isn't passing username and password.
Thank you!
-Mike

this is because:

we are using url which is deprecated instead urls.

we only accept string instead array (we should accept both)

should fix it according to spec
now for your workaround, you should changed to:
url:"turn:my.turn.server:3478",

seems it doesn't support TURN authentication though. it just ignores all except URL.

@zxcpoiu agreed, it is only passing the url in, skipping username and credentials. This is seen on the TURN server as well: no credentials.
I'm going to look into a TURN support PR, but I'm having a bit of a time understanding PeerConnection.

 I will fix it instantly.

Looks like PeerConnection will happily accept all in its constructor:
public IceServer(String uri, String username, String password)

The URI only is a convenience function for STUN

@zxcpoiu @mgreer
Please help take a look this PR https://github.com/oney/react-native-webrtc/pull/56 to check if it's correct. Thanks.

Looks good!
On Wed, Apr 20, 2016, 1:00 PM Howard Yang<EMAIL_ADDRESS>wrote:

@zxcpoiu https://github.com/zxcpoiu @mgreer https://github.com/mgreer
Please help take a look this PR #56
https://github.com/oney/react-native-webrtc/pull/56 to check if it's
correct. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/oney/react-native-webrtc/issues/55#issuecomment-212580627

Tested, working. Thank you!


Error in autodiscover when no cameras discovered

I ran framegrab autodiscover and after it failed to discover any cameras, and I got this error message:
  File "/home/ubuntu/.cache/pypoetry/virtualenvs/facescream-0UmFQIc8-py3.10/lib/python3.10/site-packages/framegrab/cli/autodiscover.py", line 23, in autodiscover
    click.echo(f"Grabbed frame from {camera_name} with shape {frame.shape}", err=True)
AttributeError: 'NoneType' object has no attribute 'shape'

I tried to reproduce this just now, and this is what I got:
framegrab autodiscover
Discovering cameras...
---
# Auto-discovered 0 camera(s).
image_sources: []

The issue seems to have been fixed.


Add steps to use Cyberduck file browser with Minio

Cyberduck: https://trac.cyberduck.io/wiki/help/en/howto/s3#HTTPS

done closing it.


filters: allow filter installation for upstream connections

Needs some thinking around actual use cases but shouldn't be too difficult to write upstream filters and install them if needed.

#3415 requires upstream L3/L4 filter chains attached to connections opened by clusters.
I propose to add a simplified version of the listener filter-chain configuration on the cluster configuration. I think there's no need for filter matching logic in this case, since we know where the connection is going - just a simple list of filters. It looks like I could have the cluster manager pass the configured filters when creating a  HostImpl, which would create the filter chain on each client connection.

@alanconway yes that makes sense to me. Hopefully, you can reuse https://github.com/envoyproxy/envoy/blob/master/source/common/network/filter_manager_impl.h.

I'm am looking at copying simple filter list config from listener_manager_impl to upstream_manager_impl, and from server/connection_handler_impl.cc newConnection() to upstream_impl.cc createConnection(). I think re-use of filter_manager_impl is implied, because it is a member of ConnectionImpl, which is used by both. It isn't complex, I just need to study how things are structured so I put it in the right place. So far the layout of the code seems pretty clear and logical, hope to have something working today.

@mattklein123 question - re filter config:
I could move the listener.Filter proto type into the core package and import it into listener.proto and cds.proto. That would let me share all the code for building filter lists from the common config, upstream and downstream. However I'm not sure if that constitutes a breaking change for your config system.
Alternatively I can create a separate Cluster.Filter type in cds.proto with the same fields as listener.Filter. That will involve minor code duplication but it definitely won't break anything.
The choice also depends on whether upstream/downstream filters are the same type of thing or not. I lean towards treating them the same - there will be filter implementations that are only designed to work upstream or downstream and not both, but I don't think that requires they be different types for configuration or programming, and a single type means less to learn.
Preference?

For now I am leaving everything where it is and creating some dubious dependencies from upstream to server code, I'll mark them all clearly. Once I have something working I'll let you folks review it and decide what should be pulled up for re use and where it should live.  That's probably more efficient than me guessing at the re-org and then having to do it again if I get it wrong.

Another use case I'll probably need in the near to medium term: upstream proxy protocol. This would be straightforward with upstream network filters.

Here's what I've got so far, not complete, untested etc (it compiles!)
https://github.com/alanconway/envoy/tree/upstream-filter
Here's how it looks in YAML config:
clusters:

name: upstream_amqp
filters:

name: envoy.filters.network.amqp_bridge
connect_timeout: 0.25s
type: STATIC
hosts: [{ socket_address: { address: <IP_ADDRESS>, port_value: 5672 }}]

On Fri, Jun 1, 2018 at 12:16 PM, Greg Greenway<EMAIL_ADDRESS>wrote:

Another use case I'll probably need in the near to medium term: upstream
proxy protocol. This would be straightforward with upstream network filters.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/issues/173#issuecomment-393930753,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHa6XjfpKYdzgvwM9hY6ViZOTowthK2Rks5t4Wj5gaJpZM4KhTod
.

Initial pull request #3571 - this works for #3415 (AMQP/HTTP bridge) but is not complete. I'd like a review of the direction before continuing.

The client (cluster) and server (listener) filters are working, but I have an additional use case:
AMQP is a symmetric protocol, unlike HTTP. Since envoy is often a sidecar, I'd like many envoy sidecars to be able to connect to a single well-known dispatch rather than vice-versa. This trick is I'd like envoy to be able to receive requests from dispatch over those outbound connections. My amqp_client filter can do the translation and reverse the direction but I'm not sure how to route the resulting traffic in envoy.
I thought about a "reverse listener", a special address type for Listener which names a Cluster. Instead of listening, a reverse-listener would connect the cluster, flip the read/write sense of the connection, and  present it to the rest of envoy as a downstream connection.
Thoughts?

@alanconway I don't think I fully follow your previous comment. Can you describe in more detail?

In HTTP, the process (client) that opens the connection sends requests, the process (server) that listens for connections receives them - the direction of requests is always the same as the direction of establishing the connection.
In AMQP, once a connection is open, either side can create links and send messagse. Typically this is used in a client/server manner - the client sends requests, publishes to queues or subscribes to topics. However with Qpid Dispatch talking to Envoy, it's not really a client/server relationship - more a router-router peer relationship. The direction of making connections need not always match the direction of sending requests.
Specifically I anticipate deployments where there are a lot of Envoy sidecars sitting beside HTTP services and fewer dispatch routers, so it makes sense to have the sidecars "announce" themselves by making a connection to Dispatch, but then allow that connection to be used as if it were a listening connection - to receive requests from Dispatch that will be forwarded to local HTTP services.
This means reversing the sense of the connection since it was opened by envoy like a client but then is used as if it had been accepted like a server, which doesn't fit in Envoy's existing configuration - I'm wondering if there's a way it could be made to work. Does that make any sense?

This means reversing the sense of the connection since it was opened by envoy like a client but then is used as if it had been accepted like a server, which doesn't fit in Envoy's existing configuration - I'm wondering if there's a way it could be made to work. Does that make any sense?

Kind of. How is this connection going to be opened in the first place? I.e., how will Envoy know to make a reverse connection? Can this reverse connection then just do dispatch and loopback to a normal listener?

Kind of. How is this connection going to be opened in the first place? I.e., how will Envoy know to make a reverse connection? Can this reverse connection then just do dispatch and loopback to a normal listener?
That is probably the best way to start: can we configure a Cluster to make a connection even if there's no HTTP traffic to prompt it? Then we can have an amqp_reverse_server filter on the cluster which is configured to make it's own loopback connection to a normal listener. Or something - I'll have a think.

That is probably the best way to start: can we configure a Cluster to make a connection even if there's no HTTP traffic to prompt it? Then we can have an amqp_reverse_server filter on the cluster which is configured to make it's own loopback connection to a normal listener. Or something - I'll have a think.

Your filter can do singleton tasks on the main thread (there are examples of ones that do this to pull in data, perform computations, etc.), though this is not on the datapath/worker so not sure if this will meet your needs or not. I'm not familiar enough with the protocol to have more concrete ideas right now. If you want to discuss more design stuff can you potentially put together a drawing/flow chart that shows the required flows? That might help.

@alanconway Are you planning ton continue work on this anytime soon? If not, I may pick this up in order to implement upstream proxy_protocol.

@ggreenway that would be great; I want to get back to this but am juggling a bunch of other stuff so can't reliably promise to do this soon.
The pull request #3571 is working and tested by my AMQP prototype, but it lacks independent tests in the envoy test harness.

FYI I am working on finishing my initial pull request #3571, I'm adding tests, fixing the filter context and moving configuration to the proper place. If anyone knows of relevant changes or work that have happened since the pull request pop a note on here.

I've got PR #6173 in for this issue, needs review.

We would like to pass additional metadata to the upstream endpoint per individual connections. Ideally, we want to share the work between HTTP and TCP filters. HTTP filters apply per individual requests, so we don't have a good way to inject extra stuff per upstream connection for HTTP filters. For TCP, we have a similar problem of re-using upstream connection for downstream connection which prevents us to apply stuff per upstream connection within downstream network filters.
What's the current work-around for these issues?

My workaround is https://github.com/envoyproxy/envoy/pull/6173. I feel that is still a viable PR but it needs to be updated. I've had a change in circumstances so don't have much time to give to it.

Complete


Deprecation of this package?

Federation V2 is now fully supported by the official HotChocolate Federation package. Does this mean this package should be deprecated and no longer be recommeded? It seems like this is no longer maintained and only the official version support the latest HotChocolate version.
It seems very misleading seeing the recommendation in this package unless I misunderstood what's going on. Can you give some clarifications on the future of this library?
Thank you

Apologies for the long delay. Yes, this package is now officially deprecated in favor of the built-in HC Federation module.


[overflow menu] bug in live demo

The overflow menu in the dark themes should not be high contrast. The background color should be field-01.

Current bug:

Should be:

The overflow menu is also getting a partial wrong color inside of the square where the icon sits. The entire square background should be field-01. This is happening in all themes.

Current bug:

Should be:

Replaced with storybook demo https://github.com/carbon-design-system/carbon-website/pull/3716


Happy with Viseron but...

Is there a way to do add two detectors? I did use Codeproject.AI for objects and license plates. I don't want to lose the license plate function within Home Assistant, but the CPU load is too high at this moment. So I want to go back to Darknet for object detection but I don't want to lose the license plate because it will open the garagedoor for me when it detects my licenseplate.
Yes, there are other ways but I want to have it locally and not in the cloud.

You can simply use darknet as the object detector and codeprojectai for the licenseplate, small config example:
darknet:
  object_detector:
    cameras:
      camera_1:
        labels:
          - label: person
            confidence: 0.8
  ...

codeprojectai:
  ...
  license_plate_recognition:
    min_confidence: 0.4
    known_plates:
      - ASDFGH
    cameras:
      camera_1:
    labels:
      - person

Config example isnt complete but i think you get the point!


watchdog timer mismatched write access in soc rdl

Ran into an error with the soc ifc rdl while trying to update dev-goog.  Re-ran the following action against dev-msft:
https://github.com/chipsalliance/caliptra-rtl/actions/runs/4792143932/jobs/8523320077
It looks like there may be some sw read only fields defined that are conflicting with the swwel setting, which were added recently with the watchdog timer changes https://github.com/chipsalliance/caliptra-rtl/commit/51bf68d3c2e3a1499f53d31b1b45f144726041aa#diff-ada1721e8b45427d0903e9a396a2dc6fb6269b83d46c62403bc6c363b950631f
src/soc_ifc/rtl/soc_ifc_external_reg.rdl:246:24: error: Field's software access is 'sw=r' but property 'swwel' implies it can be written in some situations during runtime.
    field {sw=r; hw=r; swwel = soc_req; resetsignal = cptra_rst_b;} REV_ID[32]=1;
                       ^^^^^
src/soc_ifc/rtl/soc_ifc_external_reg.rdl:323:72: error: Field's software access is 'sw=r' but property 'swwel' implies it can be written in some situations during runtime.
    field {desc = "Timer1 timed out, timer2 enabled"; hw = rw; sw = r; swwel = soc_req; resetsignal = cptra_rst_b;} t1_timeout = 1'b0;
                                                                       ^^^^^
src/soc_ifc/rtl/soc_ifc_external_reg.rdl:324:56: error: Field's software access is 'sw=r' but property 'swwel' implies it can be written in some situations during runtime.
    field {desc = "Timer2 timed out"; hw = rw; sw = r; swwel = soc_req; resetsignal = cptra_rst_b;} t2_timeout = 1'b0;
                                                       ^^^^^

Sending out for the team to review since I'm not aware of the intended behavior

@howardtr I am investigating this now.


Scroll bar is needed

Path: Administrative Case >Create > বাদী
Issue: No scroll bar is given so can not see all the records name as well as can not select them.

fixed


Prioritize Python's standard tomllib library for later versions

Since the release of 3.11, Python officially supports parsing TOML files without the need of extra dependencies. I noticed that for all current versions of the project, the standard library is not used.
I'm happy to submit a PR that prioritizes the usage of the standard library for later versions of Python, just wanted to get an ok on this. Note that this proposal will not limit the project to a higher version that already assigned, as support for older versions can still be achieved with tomli.

Assuming that the API is the same, and tomlib can be imported as tomli when available (or vice versa), then that sounds like a fine change and a PR that I would accept.

I've gone ahead and opened a pull request. Are there any plans for a version bump when this change is accepted? If that's the case, the proposed PR can include the version bump.

Merged without bumping version as I'm not going to cut a new release for this right away—it will get lumped in with the next feature or bug fix release.


swift 5 support

I used your fork. Thank you!
It is a really awesome lib, it deserves to be maintained.

It is a pleasure. It really helped me save time.

Will always keep checking to see if it needs changes.
On Sun, Sep 27, 2020 at 1:25 PM Mohammad Ashour<EMAIL_ADDRESS>wrote:

I used your fork. Thank you!
It is a really awesome lib, it deserves to be maintained.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yabuzaki/YBAlertController/pull/10#issuecomment-699628676,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANGHK5XZDEKCPRG6TJD5OEDSH4VJ3ANCNFSM4OLO6SMA
.


Add support for "*" in zone automation trigger

Description:
This change lets you setup automation for ALL zones for a given device.  The zone parameter needs to be "zone.any".  Then, whenever the zone changes, enter and leave automations can be triggered.
In my sample, I use this to run a script whenever my phone enters or leaves ANY zone.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#1753
Example entry for configuration.yaml (if applicable):
shell_command:
  send_hangout_message: /home/me/hangouts/sendMessage.sh '{{text}}'

automation:
  - alias: 'Zone Enter'
    trigger:
      platform: zone
      event: enter
      zone: zone.any
      entity_id: device_tracker.owntracks_mys7
    action:
      service: shell_command.send_hangout_message
      data_template:
        text: 'Dad is at {{trigger.to_state.state}}'
  - alias: 'Zone Leave'
    trigger:
      platform: zone
      event: leave
      zone: zone.any
      entity_id: device_tracker.owntracks_mys7
    action:
      service: shell_command.send_hangout_message
      data_template:
        text: 'Dad is leaving {{trigger.from_state.state}}'

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[X ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Why not only 'any'?

I think that you can already achieve it today by using a state automation that is triggered when a state changes from "not_home". No need to extend the support.

Also, for wildcard we always use * (homeassistant.const.MATCH_ALL)

I used zone.any to avoid having to change the code that checks for valid entries.  The valid entry requires two values separated by a dot.
Balloob, if there is another way, please show sample config that would work with existing code.  Thanks.

What I believe balloob is getting at is looking for "not_home" in the state change.
So something like
- alias: Enter Zone
  trigger:
    platform: state
    entity_id: device_tracker.owntracks_mys7
    from: "not_home"

you would use "to" instead of "from" for Leave Zone.

nordlead2005,  Thanks.  Let me give that a try.

I tried using balloob's suggestion: "... use * (homeassistant.const.MATCH_ALL)"
However, using zone.* rather than zone.any makes the entity id pattern fail.  It is expecting alpha-numeric:
From core.py:
Pattern for validating entity IDs (format: .)
ENTITY_ID_PATTERN = re.compile(r"^(\w+).(\w+)$")

It should be just *, not zone.*. And yes, you'll have to update the config validation.

Will also require tests to be added.

balloob.  No problems adding the tests.
I'm wondering about the modifications to the core.py config validation.  Changes I would make there could cause problems in many other modules.  The if/then/else code to handle this particular case would be quite ugly.  All entity IDs are in the format domain.object.  This would be the only case where an entity ID would not be in that format.  zone.* would be cleaner.  I would only need to modify the regex to accept * as well as alphanumeric.

I've updated the core.py to allow for a * in the 'object' portion of the domain.object entity id format.  This could be useful for other scenarios too.  I've also made changes to use the MATCH_ALL constant.

Don't change entity_id format. Use vol here: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/automation/zone.py#L23
you can make a new check on helpers/config_validation.py like event_entity_id to convert * to MATCH_ALL

No need to add it to generic config validation, just add '*' support to the validation in zone.py. Don't update other code as you are impacting the whole system.

I've made the suggested changes to config_validation, removed changes from core.py and made this work with "" rather than zone. or zone.any.
The only thing is, in the configuration, the * needs to be in quotes or the yaml parsing doesn't seem to work.  Any suggestions on this or is "*" ok?
e.g.
automation:

alias: 'Zone Enter'
trigger:
platform: zone
event: enter
zone: "*"
entity_id: device_tracker.owntracks_mys7
action:
service: shell_command.send_hangout_message
data_template:
text: 'John is at {{trigger.to_state.state}}'

Hi @gravesjohnr,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @gravesjohnr,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @gravesjohnr,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @gravesjohnr,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

@gravesjohnr any updates on this PR?

Please reopen this PR if you want finisch that.

I've had nothing but problems trying to get the tox environment working.  I finally gave up.

it's closed this PR?


Check for zero retval of casecmp

@segiddins Did you those benchmarks @alexdowad asked about? I think we should do the changes you've proposed, but still it's good to know the impact.

What benchmarks?

@segiddens See my comment.

#!/usr/bin/env ruby

require 'benchmark'

x = 'sTrInG'

Benchmark.bm do |bm|
	bm.report("==    ") { 1_000_000.times { x.casecmp("string") == 0 } }
	bm.report(".zero?") { 1_000_000.times { x.casecmp("string").zero? } }
end

       user     system      total        real
==      0.200000   0.010000   0.210000 (  0.202799)
.zero?  0.200000   0.000000   0.200000 (  0.201177)

Thanks @segiddins. This is more what we were interested in:
5:57 ~prog/Ruby/rubocop % cat bench.rb                      [the_sky_loves_a_good_joke]
#!/usr/bin/env ruby

require 'benchmark'

x = 'sTrInG'

Benchmark.bm do |bm|
    bm.report("==      ") { 1_000_000.times { x.casecmp("string") == 0 } }
    bm.report(".zero?  ") { 1_000_000.times { x.casecmp("string").zero? } }
    bm.report("downcase") { 1_000_000.times { x.downcase == "string" } }
end
5:57 ~prog/Ruby/rubocop % ruby bench.rb                     [the_sky_loves_a_good_joke]
       user     system      total        real
==        0.170000   0.000000   0.170000 (  0.166126)
.zero?    0.170000   0.000000   0.170000 (  0.171633)
downcase  0.210000   0.000000   0.210000 (  0.216743)

It looks like there is still some (minor) performance benefit of using casecmp("string").zero? as opposed to downcasing/upcasing the string. So should we keep this Casecmp cop? Or do we dump it?

Let's keep this for now. Because of the release of 0.36.0, this now needs a changelog entry.

So is this cop going to be kept as a default? Do you find the casecmp style as readable as the downcase one?

Do you find the casecmp style as readable as the downcase one?

It's not as readable, unfortunately. I think that it should be disabled by default.

Agreed. Ruby really needs a similar method that returns a boolean value...

CHANGELOG'd

The entry name is not correct, therefore the failing test.


TestCaseFilter with custom properties

fix: https://github.com/microsoft/testfx/issues/731
fix: https://github.com/microsoft/testfx/issues/201

Nice work @engyebrahim :shipit:


Add Windows CNGCrypto AMD64 to dist and release assets.

PR Description
This adds windows executable for cngcrypto amd64 support.
PR Checklist

[x] CHANGELOG.md updated
[x] Documentation added
[x] Tests updated via drone step

@rfratto I agree with needing a plan on how to improve the sanity of our CI and builds. I had hoped to tackle a piece of this with the windows MSI work, but we probably need to lay out a logical plan of what things can be improved in order to get us where we want to end up.

Its totally fine to wait, I wanted it to be ready so it def makes 1.2.

More universally we could switch to almost one build image but it would be the Microsoft one and that concerns me a bit. It might be an unneeded concern since they are very prompt on updated it due to CVEs or releases.


Search does not work with more complex inflected forms (reduplication, non-lexicalized preverbs)

Searching some inflected forms (presumably in the inflected paradigms) yields lemmas, but for other more complex inflected forms, there is no match.
Examples:

Basic form: ninipan -> lemma match: nipâw (-> normative: ninipân) (+)
Reduplication: ninanipan -> lno result (lemma match should be nipâw; normative: nina-nipân) (-)
Productive preverb: nohte-nipaw -> lemma-match: nôhtê-nipâw (lexicalised; normative: nôhtê-nipâw) (+)
Productive preverb: kakwe-nipaw -> no result (lemma match should be: nipâw; normative: kakwê-nipâw) (-)

Also, missing a hyphen presents no match, though the descriptive model does recognize such forms (but marking them as orthographically nonnormative).
Example:

nikinipan -> no result (lemma match should be: nipâw; normative: nikî-nipân)
niki-nipan -> lemma match: nipâw (normative: nipâw)
ewapamat -> no result (lemma match should be: wâpamêw; normative: ê-wâpamat)
e-wapamat -> lemma match: wâpamêw (normative: ê-wâpamat)
nêpât (initial change) -> no result (lemma match should be: nipâw; normative: nêpât)

@Madoshakalaka, this means that word forms  must be looked up in the FST on each query; if it's only consulting the generated word forms, it's not doing enough :/

Potential solution/Question: might the spell-checker FST (crk.zhfst) combining a weighted error correction model and an FST acceptor be a possible solution?

let me look into it

@aarppe @eddieantonio
I just debugged the code and I have an idea what's happening
Long words short, these three have "Err/Orth" in their fst analyses, which is not handled correctly in the algorithm.
nikinipan 'nipâw+V+AI+Ind+Prt+1Sg+Err/Orth'
ewapamat: {'PV/e+wâpamêw+V+TA+Cnj+Prs+3Sg+4Sg/PlO+Err/Orth', 'PV/e+wâpamêw+V+TA+Cnj+Prs+2Sg+3SgO+Err/Orth
The last one though, I didn't know there exists "IC"
nêpât: {'IC+nipâw+V+AI+Cnj+Prs+3Sg'}
They will be a easy fix. I'll inform you when it's ready

I'm on it

Ok - when using the normative generator, one just has to remove the +Err/Orth tag (resulting from the descriptive analyzer). I believe this issue is related to #130.

Now it's implemented correctly such that analysis outside paradigm tables will also get matched.
I tested on all 9 examples @aarppe proposed and they all show as expected.
Note for ewapamat and e-wapamat you'll get two results:

as ewapamat matches two inflected forms:
{'PV/e+wâpamêw+V+TA+Cnj+Prs+3Sg+4Sg/PlO+Err/Orth', 'PV/e+wâpamêw+V+TA+Cnj+Prs+2Sg+3SgO+Err/Orth'}
We'll soon have UI that shows the original matched form and the details of the inflection (Preverb, reduplication IC...), @eddieantonio is working on it
@aarppe Please try out on sapir to see if there are other improvements

Great! I notice that my example cases weren't entirely complete, and I had overlooked the possibility of multiple normative forms of the same lemma matching one and the same fuzzy search string. While I corrected these above, this probably needs to be pursued as a separate issue.


Incorrect edit source link for balena-cli docs

The "Improve this Document" button on https://www.balena.io/docs/reference/balena-cli/ links to the wrong file as the CLI documentation is auto-generated through files.
@pdcastro How about we link it to this heading instead - https://github.com/balena-io/balena-cli/blob/master/CONTRIBUTING.md#editing-documentation-files-readme-install-reference-website
I mean, if we can't give them the direct file to edit. The next best thing is instructions to work with CLI docs, right?

The next best thing is instructions to work with CLI docs, right?

Right. 👍  I guess that most people will give up updating the CLI docs when see those instructions, 😞   but that's how it is at the moment.

I mean, it's way better than folks opening wrong PR's and leading to time wasted in fixing them both by contributor and maintainer.


Add deprecation warnings

closes #2720

This won't work. See https://github.com/woodpecker-ci/woodpecker/blob/main/pipeline/frontend/yaml/parse.go#L44

Good catch. Any idea how I could check it otherwise? Parsing the raw yaml string and checking for the key to exists?

Also, would it be possible to return multiple errors there so we can lint all three fields?

Definitely, that's why I introduced multierr support. Just forgot about it again


Use Apollo Link

It seems like it would be a pretty good idea to leverage Apollo Link to deal with how to interface with the Graphql endpoint, how to deal with subscriptions and more broadly standardize how to execute any Graphql ops in a more transparent / pluggable way.
People would be able to provide any composed link they want to Playground and it would work transparently.
This would simplify the code around subscriptions and make Playground integration a lot more agile.
For example, my use case is around how subscriptions are handled right now which is hardcoded to use subscriptions-transport-ws. In my case, our backend is written in Elixir using Absinthe which leverages Phoenix channels so a special client is needed to send ops over ws.
We have already an Apollo Link for it and should Playground support it, it would be trivial to have Playground works with Absinthe.
@timsuchanek what do you think ?

Passing in a Apollo Link when integrating the Playground in your own app sounds like a great idea to me!

Sounds like a great suggestion @tlvenn. Do you have any proposal on how to setup/configure a link? Should there be a JS snippet section in the settings for example? How should this snippet be persisted/shared across sessions/projects?

Hi @schickling, in my mind, this is defined at integration time so you can pass your composed link to Playground:
ReactDOM.render(<Playground link={myLink} />, document.body)

This makes total sense for code-based usage. However I was also thinking related to the standalone electron/web-app.

For the standalone app, I am thinking that custom apollo-link can be packaged as an Electon plugin and be discovered and used by the Playground app.

Sounds good to me. @timsuchanek can you provide some guidance on a potential PR?

So, I was looking into this a bit. I think following is a good path forwards to building this:

[ ] Add apollo-link and apollo-link-ws to packages.
[] Translate all subscriptions-transport-ws calls into apollo-link-ws calls and use the link client instead of transport directly.
[] Allow a createApolloLinkfunction  to be passed as a prop. This function should return an ApolloLink class or subclass of it.
[] Move the apollo-link-ws init code into a default function for the createApolloLink prop.

I think we can move on this without an answer for how plugins work. I think whatever the decision is for plugins may change this slightly. Once into apollo-link-ws there can be some extra stories to use apollo-link instead of fetch directly

Hi @DavidJFelix, this sounds like a great next step. Would you be willing to work on a PR for this?

@schickling I'm doing a little work on it right now. I'll see if I can get a POC and I'll come back if I need any help or guidance.

@tlvenn @schickling can we see if this issue can be closed?

@timsuchanek can you provide some updates?

@schickling : from the discussion I had with @timsuchanek , he completed my WIP patch, out of band of the pull request. The changes are visible past this commit and are accomplished with the previous 10 or so commits: https://github.com/graphcool/graphql-playground/commit/55fc961a1fbd6c96e7a6d086f22bd058c7930c11

Implemented in latest version.


onSelectEvent, how to get a time slot?

I try to align this very nice component for some specific needs. The story is quite simple. onSelectEvent I would like to take event data and clicked slot time (like 9:00 am, start time is enough)
Is this somehow possible to achieve?

hi there, the event select doesn't have the time slot. I'm not sure it makes sense there to have that info as you already have the even and so know what timeslots it's in. There are, however,  events that fire when selecting time slots (if the selectable prop is set) that gives this info


Hello world paraguay

What does the program do ?

In what programming language it is written?

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


support .markdown for Markdown files

some repos e.g https://github.com/google/WebFundamentals use .markdown for markdown files.
and this is what John Gruber endorses.

Thanks for this. It will be published in the next release! :+1:

1.6.6 is out!


Task already completed

I already used functional components in this repo as instructed in this activity. So this day 4 task is already completed.
I am submitting this issue for review as the day 4 task instructed.

Hi @LeslieAine ,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights
✅ Correct use of Gitflow
✅ No linter error
✅ README is okay
✅ App works as expected 👍
Optional suggestions
N/A
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Decouple prost from tonic.

Motivation
Prepare using tonic with other protocol buffer implement or flatbuffers.
Solution
Add trait to provide needed info to the code generator.
And, introduce new features to make using prost optional.

@LucioFranco Can you check some added commits?
Which way is preferred here to fix this check failure? Adding _ prefix or disabling the function by feature gate?

@Perlmint looks like there are a couple conflicts, I know some of the build code change, would you be able to update this? Then I can take another look. Thanks!

I rebased my commits. But, It looks like I should add more commits - make types that needed to describe schema public. After pushing the commits, I'll notify.

@LucioFranco Fix all checks and make possible implementing the service generator out of tonic-build.

Sorry for the delay on this, I am gonna take a longer look at this once tonic 0.1 is out because I would like to push this to 0.2 since there are still somethings to work out. Thanks for your patience.


MySQL strict mode

I am fed up with having to switch of MySQL strict mode on my servers because we keep sending integers as strings.
Can we have a diligent check to make sure that if we are sending IDs through to the database we convert them to integers? A varchar field will happily accept an integer, but not the other way around.

Closing, please raise a new issue if there are further instances of this occurring.

Will do if I spot them.


TaskRun failures dued to k8s PodSecurity

Expected Behavior
I can run the tutorial pipeline to clone a repo
Actual Behavior
The pipeline fails for PodSecurity configurations
Steps to Reproduce the Problem
1.Copy the files here
2. Apply them to k8s cluster (I'm using kubectl v1.25.1 on minikube)
3. watch as the pipelinerun fails
Additional Info

Kubernetes version:
v1.25.1

Tekton Pipeline version:
v.0.41.0

Quick update:
I succeded in making the PipelineRun running but I had to modify the labels on my namespace with
k label --overwrite ns tekton-pipelines \
  pod-security.kubernetes.io/audit=privileged \
  pod-security.kubernetes.io/warn=privileged pod-security.kubernetes.io/enforce=privileged

Have you tried applying the files in another namespace, e.g. default as in the tutorial? This should not be subject to the same restrictions.
I believe it's good practice not to run your pipelines in the tekton-pipelines namespace, it is intended for the Tekton controllers only.

Hi @AlanGreene thanks for your response, I've tried to change namespace into default and it worked as expected.
In general which is a good namespace in which I can run my Pipelines? Let's say I'm trying to deploy a project (so many k8s manifests):is the namespace the same in which I want to deploy? Or should I plan to create an ad hoc namespace for the Tekton resources to run?

In general I would use different namespaces for different purposes. So I would have my application deployed in one namespace and run my CI/CD pipelines in another (possibly multiple), in fact I may even use different clusters depending on the level of isolation required. It depends on your particular circumstances and requirements.

Crystal clear! Thank you for the explanation

Looks like a duplicate of https://github.com/tektoncd/pipeline/issues/5896


Fix - canvasid not working properly

In reference to issue #207
This fix restores the functionnality of the attribute "canvasid"

Thanks @JochenRousse for this PR! 😃
Can you please make a single commit with a detailed message?
Also having working tests it will be great!


Failed to resolve table or column expression named "SophosXGFirewall"

Azure Sentinel guidance
Am trying to connect my sophos firewall with azure sentinel but keep getting this error, What could be the cause of it
let timeframe = ago(1h);
let threshold = 50;
SophosXGFirewall
| where TimeGenerated >= timeframe
| where Log_Type =~ "Firewall"
| where not(ipv4_is_match("<IP_ADDRESS>",Src_IP,8) or ipv4_is_match("<IP_ADDRESS>",Src_IP,12) or ipv4_is_match("<IP_ADDRESS>",Src_IP,16))
| summarize dcount(Dst_Port) by Src_IP, bin(TimeGenerated, 5m)
| where dcount_Dst_Port > threshold
| extend timestamp = TimeGenerated, IPCustomEntity = Src_IP

Thanks for your question. Please provide us with the link to the documentation you are referring to so we can better assist.


Fixes #750. Ensure the correct focus order after call SetFocus.

For this to work it's needed to call SetFocus with one of the two methods:
view.SuperView.SetFocus (view)
or
view.SetFocus ()
This is a new method more simple and avoid focus order issues.

Call like SuperView.SetFocus (view) does not ensures that the entire parent hierarchy can really get focus and thus not updating the focus order.

In my opinion I think the original method shouldn't be public but only the new method. The problem is the backward compatibility.

In my opinion I think the original method shouldn't be public but only the new method. The problem is the backward compatibility.

We have not released 0.90 yet, so breaking backwards compat is an ok thing to do...as long is it isn't super-deep. In fact, if we really think something should be changed we should change it. I don't have a strong opinion on this particular issue myself (I have not dug in deep on how focus works). Your call.

Great I'll do the change so.

Feels so much more correct. Well done.

I think you need to rebase though...

I think you need to rebase though...

Done. Thanks @tig.

@tig I made some changes in the demo.cs. Sorry about that.


Tipbot is not providing enough information in raining and tipping commands

When some commands fail tipbot is not always clear enough, specially in the rain command. Sometimes could be due SOLANA congestion/fails, could be RPC's fault, could be due the tipper don't have enough SOL for gas fees, but the messages only shows how many people reacted and how many got the rain, if any.
Sometimes we see a rain with a lot of reactions and no one gets it. Sometimes it's like it's stuck and only some people receives it.
So, we need better error handling from tipbot. We may need to include in the confirmation message the transaction url to facilitate the review and towards better transparency.

Partially addressed with added transaction confirmation on tip commands. Rain command already have it but without notifying.
Added proper notification via Discord and also including transaction address in the message.


Display correct caseload and checkins when there is an active override

Fix bug where the actual user's caseload and checkins were displayed even when there was an active user override

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.132%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
314

Relevant Lines:
728

💛  - Coveralls


Sensitivity acting unexpectedly

Expected behavior
Word recognized with sensitivity of x should be recognized with sensitivities bigger than x.
Actual behavior
Word recognized for sensitivity of x might not be recognized for bigger sensitivities.
Steps to reproduce the behavior
Create multiple Porcupine classes with different sensitivities (0-1). Detect PCM and process it with all Porcupine classes. Sometimes, it will happen that word recognized with Porcupine with some sensitivity is not recognized for some Porcupine with bigger sensitivity.
I want to use sensitivity as a threshold, and to know if word is recognized with some sensibility that it will be recognized with bigger one. Can I do that? Am I doing something wrong? Or is your sensitivity description wrong?

I changed your python demo a bit to showcase this problem: https://pastebin.com/8w5UJhMw
You can start it with any keyword example, you can see that it is not true that increased sensitivity recognizes the word that is recognized with lower sensitivity (as shown in screenshot attached).

Had a look at your code. Debugging this in a live situation will be very hard. I suggest the following:
1- Record a WAV file with your keyword in it. You can say it multiple times.
2- Use the offline demo (it is a different file in the same folder) to process WAV with different sensitivity
Can you please do the above?
With current demo I am not sure if the problem is with the porcupine, running multiple instances of it at the same time (this should be OK), or a runtime issue (not being able to process in time).

I cannot reproduce, and I don't understand what might be the cause. This is what I tried:

In the same code I gave to you, I printed PCM data all the time until the bad porcupine state is reached
I inserted that same PCM data in the loop instead of listening to the mike
Porcupine is not giving wrong results anymore but meaningful ones

I totally don't understand what is happening here... How do you mean not able to process in time, I don't give it any time limit and wait until porcupine process finishes?
Code (with the PCM data, commented part is about taking PCM data): https://paste.ofcode.org/WpiichpQTwYWqkq8cb5gnc
First output (problematic cause bigger ): [False, False, True, True, False, False, False, False, False, False]
Repeated output (doesn't repro the issue): [False, False, False, False, True, True, True, True, True, True]

Yeah. This is good as the engine is working as expected.
Not being able to process on time means that maybe running ten instances of Porcupine at the same time is not possible on your machine in real-time. I am not sure what is the cause in your real-time test.
But the sensitivity is working as expected, right?
I am going to close the issue. If you can't figure the root cause in your first test open another issue with the relevant topic. Thanks!


Returning Path instead of str instances

As mentioned in https://github.com/ActiveState/appdirs/issues/79, I've been working on another fork of appdirs, but would rather hold off on publishing that and focus all efforts in one place.
I mostly have two changes in places:

Drop support for ancient python versions (there's little point in a new library supporting Pythons that re long past their EOL, and that just holds back on keeping the library alive).
Change the return type of directories to Path instance, to make usage on consumer libraries easier. This kinda means it's not a 100% drop-in replacement, but rather an upgrade (e.g.: like a major).

Maybe it would make sense to have a platformdirs==1.0.0 release, which is functionally identical to appdirs (to allow seamless switching), and then start merging in any non-backwards-compatible changes. Thoughts?

I absolutely agree with @WhyNotHugo that we need to stop supporting EOL versions of Python because it does not make sense
If we drop old Pythons support, it is logical to do everything in a modern way and follow PEP428
I'm not sure about platformdirs  ==1.0.0, because user can still use the original appdirs (judging because the project is frozen, we should not worry about it)

I'm not sure about platformdirs ==1.0.0, because user can still use the original appdirs (judging because the project is frozen, we should not worry about it)

You're right. No need to have a half-migration path.

virtualenv depends on appdirs (and as soon as we'd have a release, presumably on this module), so we can't drop support for 2.7 until one happens I think, and then we're free to presumably.
(The pedant in me will also mention that there are versions of 2.7 that are not EOL'ed, i.e. PyPy, but certainly if it causes even trivial extra effort, like requiring us to depend on pathlib2 for 2.7, I think at this point it's totally fine to drop after a release).
And as for the specific idea, yeah, returning Path objects seems like a good idea to me.

I'd never heard of pathlib2, but a quick lookup indicates it's unsupported since 2020-01-01.

The order of the two items in my original message is by design: dropping those versions is a blocker to adopting Pathlib. Python 3.6 also have some additional changes.
I believe that pre-3.6, open(Pathlib("/some/file")) did not work. I've no idea how to confirm that without building python3.5 though.

If I understood correctly, then we should make a release with the support of all Python (which virtualenv supports) to switch virtualenv to us, and then drop all EOL Pythons (include PyPy) and add support for pathlib? Or we will still have compatibility with EOL Pythons?

That makes sense to me.
I'm curious on whether virtualenv plans to drop python2. I haven't some any reference in the docs or their issue tracker.

As long as there's one python 2 compatible release virtualenv will be fine. virtualenv plans to support Python versions two years past their grace period - https://gaborbernat.github.io/euro_python_2019/#/55; so will not drop Python 2 support until January 1st.

providing a path type aware wrapper might be nice
so one could get a Appdirs(...., path_type=pathlib.Path/pathlib2.Path)

so one could get a Appdirs(...., path_type=pathlib.Path/pathlib2.Path)

That sounds a lot like https://adamj.eu/tech/2021/07/10/python-type-hints-how-to-avoid-the-boolean-trap/, I think it's better to have new method names for the path variant :blush:

@gaborbernat So, when it comes to naming the new methods, what do you think about adding a _as_path suffix?
user_data_dir_as_path
user_config_dir_as_path
user_cache_dir_as_path
user_state_dir_as_path
user_log_dir_as_path
site_data_dir_as_path
site_config_dir_as_path

user_data_path
user_config_path
user_cache_path
user_state_path
user_log_path
site_data_path
site_config_path

And yes.

@gaborbernat Those look great!
I intended to eventually handle Paths completely internally (e.g.: Path.home() / ".cache"). I guess that if the old methods are kept around then internally everything will continue to be handled as strings?

I would sit down later today and implement these. @WhyNotHugo I do not think there is much benefit of changing the internal representation. IIRC using pathlib can also be slower in some cases? Not sure about this, though. If I am wrong, and there are good arguments for changing the internal representation, I would be happy to give that a go, too.

It probably doesn't make sense to change it internally if the str methods will remain. Though I'm honestly very curious how both implementations would compare in terms of performance.

@gaborbernat Those look great! Was gonna mentioned the same thing :)
I intended to eventually handle Paths completely internally (e.g.: Path.home() / ".cache"). I guess that if the old methods are kept around then internally everything will continue to be handled as strings?

No, the str variant is the faster. That remains the internal default form.

I based my implementation on #26. I will wait with creating a PR until it is merged. If you have any feedback already, please let me know.
Am I missing anything else other than the documentation?
I am also waiting for https://github.com/MichaelAquilina/flake8-spellcheck/pull/50 to be merged such that the implementation passes the flake8 spellcheck.

@papr now you can open your PR; do remember to add changelog and handle multipath as discussed in #24

No, the str variant is the faster. That remains the internal default form.

Well that saves me the trouble of benchmarking it myself. Thanks for testing that.

Creating a class (which pathlib is) will always be slower than just a raw string. See https://github.com/psf/black/issues/1950 for a war story on this.

Sure, creating the class itself is slower, but operations on it can be faster due to... implementation.
Anyway, a benchmark is enough, if numbers show it to be slower, there's no point in discussing it further.

I'd be surprised if the core developers have one implementation for os.path and another for pathlib properties. Considering most of os.path is already written in C I don't think I see much opportunity for pathlib to be faster. IMHO pathlib is just a syntactic sugar for the end user (in some cases it's easier) but offers no performance benefits.

Done by #27.


Add pause and resume connector commands

Add two new commands to support pause and resume kafka connectors #1
1- kcctl pause connector connector-name-1
2- kcctl resume connector connector-name-1

Thanks, that's a great start! Could you:

rework the first commit using your e-mail linked to your GH account (as is the case with the second one), so to not have the "Octocat" commits
run mvn license:format for adding the missing license headers
update the output in README.md from running kcctl without any options

Thanks!

Great work, thanks a lot, @karim-elngr!


cargo rustc --version should print the version of rustc called by cargo

Problem
it is difficult to check if the version of rustc called by cargo and the version of rustc in the users environment are the same, either due to RUSTC or RUSTC_WRAPPER being set, or due to cargo being patched by a package manager such as nix.
Proposed Solution
when cargo rustc --version is run, cargo should invoke rustc --version following all the usual rules of how to find rustc, such as checking RUSTC and RUSTC_WRAPPER
Notes
you an kind of get the desired effect with RUSTFLAGS=--version, but it's a bit of a hack.
`cargo rustc -- --version also doesn't exist for some reason.

cargo rustc -- --version works for me. Did you get any error from that?

@weihanglo it works, but it also builds the project in the current dir, and it only prints the version number if the build is successful.
which is a problem, because the main reason you would want to run this is to debug issues that are causing your build to fail (in my case it was a strange problem, because just updating rustc wasn't enough, i had to also run cargo clean for the unsupported version error to go away)

but it also builds the project in the current dir, and it only prints the version number if the build is successful.

From what I understand, this seems to be a problem, and the build should not be performed if it only outputs the version.

From what I understand, this seems to be a problem, and the build should not be performed if it only outputs the version.

from cargo rustc --help:

Compile a package, and pass extra options to the compiler

it compiles the current package because that's what cargo rustc is supposed to do.

From reading the issue description, there seems to be two different output you want:

Get the version info of rustc, i.e. the output of rustc -vV.
Get the path to the rustc, i.e. the value of RUSTC, RUSTC_WRAPPER, and RUSTC_WORKSPACE_WRAPPER.

Before proposing a change to the entire Cargo team, I think we should flesh out the desired output that captures things people want. Also, rustdoc might also be bothered by the issue, so should be dealt with together.
However, before that, I'd like to have more background of situation you want to learn the rustc version. Also why cargo build --verbose + CRTL-C and read the rustc invocation didn't satisfy you, just because it's a bit hacky?

From reading the issue description, there seems to be two different output you want:
no, just the rustc version is enough for my usecase
* Get the version info of rustc, i.e. the output of `rustc -vV`.

just the output of rustc --version would be enough for my usecase.

* Get the path to the rustc, i.e. the value of `RUSTC`, `RUSTC_WRAPPER`, and `RUSTC_WORKSPACE_WRAPPER`.

could be useful for some, but it wasn't what i had in mind, no.

Before proposing a change to the entire Cargo team, I think we should flesh out the desired output that captures things people want. Also, rustdoc might also be bothered by the issue, so should be dealt with together.
However, before that, I'd like to have more background of situation you want to learn the rustc version. Also why cargo build --verbose + CRTL-C and read the rustc invocation didn't satisfy you, just because it's a bit hacky?

only works inside of a cargo crate, also not at all obvious that would print the rust version and not just build logs.

* Get the path to the rustc, i.e. the value of `RUSTC`, `RUSTC_WRAPPER`, and `RUSTC_WORKSPACE_WRAPPER`.

could be useful for some, but it wasn't what i had in mind, no.

This somehow contradicts to what I understood. RUSTC_WRAPPER could hijack and calls into the entire different rustc. If not handle correctly, the version info might not be useful or even absent. (A slightly relevant PR https://github.com/rust-lang/cargo/pull/13659 of this).

Not mean to turn this down, but Cargo is cautious of adding new flags, since once they've added they stay like forever. A specialized flag for only one purpose with no interaction with other parts is unlikely to be accepted by the team.
If people want to move things forward, somebody needs to drive this with a proposal considering different parts in Cargo holistically, and with some practical use cases. See RFC 3180 for reference. Not every flag needs to go through the RFC process, but still needs a fair amount of use cases. See --output-format for cargo rustdoc as another example.

Not mean to turn this down, but Cargo is cautious of adding new flags, since once they've added they stay like forever. A specialized flag for only one purpose with no interaction with other parts is unlikely to be accepted by the team.

i see.  i was under the impression that an isolated feature would be less likely to cause problems for other pieces of code later down the line, but i'm not the one designing toolchains.


App crash when extracting archive

When deploying some updates, the deploy service download and start extracting the archive then the app crash with error:
Application Error

The file or directory could not be found. (file:///data/data/com.compagny.appname/app_339070a214f611e5ae823e00dea088b8/index.html)

Reinstall the app and clear cache through Settings/Applications, doesn't help.
The crash happen on Android 5.1.1, I didn't test on iOS for the moment.
There is my informations:
$ ionic info

Your system information:

Cordova CLI: 5.0.0
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.0
Ionic CLI Version: 1.5.4
Ionic App Lib Version: 0.2.1
OS: Distributor ID:	Ubuntu Description:	Ubuntu 14.04.2 LTS
Node Version: v0.12.2

Any idea ? Thanks by advance !

I made a gist with my logcat: https://gist.github.com/eweap/e81bba67611542069d8a

+1

at line 890
I/IONIC.DEPLOY.UNZIP_STEP(32672): Exception: /data/data/com.alhena.planetagger/app_339070a214f611e5ae823e00dba088b8/css/main.css: open failed: ENOTDIR (Not a directory)
it is because css folder was not created

There is a problem with the unzip function.
During the while in line 429  there is no check if the entry is a dir or not.
i' put in a simple if else
just look at https://gist.github.com/crazystars/9fb26ca1966e6db24317
it is working for me now

@crazystars Thanks man ! It's working like a charm !

Your pull request fixed my issue on Android. Deploy works now.

Hey guys, this explanation might seem a bit confusing but here goes:
This is actually an issue with Ionic CLI 1.5.1. When you run ionic upload, we generate and upload a zip file -- this is what the plugin eventually downloads. In 1.5.1 an upgrade to the node archiver was included. Sparing all the details, it produces a semi-borked version of the zip that Android's ZipInputStream fails on.
We currently have a beta with the fix in place. you can test this new beta by installing npm install ionic@beta. The fix will make its way into a 1.6.x release.
Note: Because it's the zip file itself that is slightly corrupt, you'll need to upload a new version of your app to deploy and download on your device after you upgrade your CLI.

@ericb Great, the ionic@beta fix the problem ! Thanks man (and Ionic team) :)


Squished layout on iPad in multitasking

WhatsNewKit Environment

iOS version: 14.0
WhatsNewKit version: 1.3.6
Xcode version: 12.0
Swift version: 5.0
macOS version running Xcode: 10.15.6
Dependency manager (SPM, Carthage, CocoaPods, Manually): SPM

What did you do?
Displaying the WhatsNew view with default layout values on iPad in multitasking
What did you expect to happen?
The layout should consider the trait collection
What happened instead?
The layout is being squished
`private func showWhatsNew() {
// Initialize WhatsNew
let versionStore: WhatsNewVersionStore = KeyValueWhatsNewVersionStore()
    var configuration = WhatsNewViewController.Configuration(
        theme: .default
    )
    configuration.tintColor = UIColor(named: "someTintColor")!
    configuration.itemsView.imageSize = .preferred

    let whatsNew = WhatsNew(
        // The Title
        title: SSKLocalizedString("STR_WHATS_NEW"),
        // The features you want to showcase
        items: [
            WhatsNew.Item(
                title: "XYZ",
                subtitle: "Blah blah",
                image: UIImage(systemName: "bolt.fill")
            ),
            ...,
            ...,
        ]
    )

    // Initialize WhatsNewViewController with WhatsNew
    if let whatsNewViewController = WhatsNewViewController(
        whatsNew: whatsNew,
        configuration: configuration,
        versionStore: versionStore) {
        self.present(whatsNewViewController, animated: true)
    }
}`

Hey @lvandal
Thanks for your bug report and sorry for the delayed response I was on vacation.
Please checkout the feature branch trait-collection-fix and let me know if this resolves your issue.

Yes, it is now fixed. Thanks so much!

Perfect 👍
I will leave a comment as soon as the bug fix is available within a new release of WhatsNewKit

Hey @lvandal
The bug fix is now available with the new release of WhatsNewKit 1.3.7


Cocoapods

I'd be cool to also add Cocoapods support. I done this implementation myself last month for my library. Just follow this post and this checklist.

I'm waiting for Swift Package Manager 😆 But I will add when I have free time

@lfarah Added tnx

You're welcome! 😄


Added Additional API Support

Addresses issue #541
Before the API only supported talks and publications for the importtalks and importpubs command; however, now the api will also serialize and return the JSON data for News, Projects, Videos, and Person objects.

I’ve already included a comment in the publications serializer about the depth feature but I moved it to the top of serializers.py
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Jon Froehlich<EMAIL_ADDRESS>Sent: Friday, August 31, 2018 2:47:57 PM
To: jonfroehlich/makeabilitylabwebsite
Cc: johnsonkuang; Author
Subject: Re: [jonfroehlich/makeabilitylabwebsite] Added Additional API Support (#593)
@jonfroehlich requested changes on this pull request.
Can you provide comments that point to Django references for serialization and also that explains the depth field. Finally, please write in a comment how you would actually take out a field if you didn't want to do all--in other words, if you wanted to serialize all but one field in an object.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/jonfroehlich/makeabilitylabwebsite/pull/593#pullrequestreview-151557639, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AfdHHGYKClQvzittAYgJBoQDersxb2BIks5uWa8NgaJpZM4WV4tv.

Added comments in about serializers


Documentation outdated?

Hi there,
here it says the following (see yellow highlight):

But I can't find any documentation regarding the new lettable operators on http://reactivex.io/rxjs
I had to read the file on github (which was recommended not to do by the yellow highlight!) to learn about it.
From here I would have guessed that there should be an "overview.md" somewhere, linking to the sub-documentatoin md files. I couldn't find one:

This raises the question to me, how the current documentation (http://reactivex.io/rxjs) is generated in the first place?
If you need help regarding documentation, I'd be happy to contribute!
Regards,
Nicolas

please checkout current progress at https://github.com/ReactiveX/rxjs-docs for new documentation. outdated contents will be dealt with also.


Make use_analyzer: true the default for 4.0.0

Meta/tracking issue.
Blocked by https://github.com/dart-lang/angular2/issues/390.

Blocked by #390.


Special Characters

First of all: Thank you sooo much for the great Project!!
But as I am a german person and the german language uses some special characters such as ä, ö, ü or ß, I need to write the HTML version of those characters in my documentation: e.g. ä This is somehow annoying.
I also searched in the source code and found a solution. I inserted the following lines of code in the function MarkedPlugin.prototype.parseMarkdown = function (text, context) just at the beginning of the function:
text = text.replace(new RegExp('ä', 'g'), 'ä');
text = text.replace(new RegExp('ö', 'g'), 'ö');
text = text.replace(new RegExp('ü', 'g'), 'ü');
text = text.replace(new RegExp('Ä', 'g'), 'Ä');
text = text.replace(new RegExp('Ö', 'g'), 'Ö');
text = text.replace(new RegExp('Ü', 'g'), 'Ü');
text = text.replace(new RegExp('ß', 'g'), 'ß');

The file is located under lib/Output/plugins/MarkedPlugin.js
Best Regards
Thomas

I'm curious why you need to write the HTML entity version of these characters? That shouldn't be needed, it sounds like instead the correct encoding is not being used or declared.

Yes that's probably true...
But as far as I know, most (or all) of the Webpages use These characters to Display Special characters.
How should I declare the correct Encoding?

@Thomas-Sparber I expect you can just use a meta tag to declare it
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8"/>
...

The default theme has a meta tag, so these characters should work as intended. We have a test case now for Cyrillic characters, which should also cover the characters above.


feat(website): add link to Discussions on github?

Describe the feature request
Description of the feature request here.https://github.com/taikoxyz/taiko-mono/discussions
As of now the above discussion board is not active at all, I think we should promote the link on our website and also in our discord server.
Describe alternatives you've considered
No response
Additional context
No response

Yes, in addition to the website. It should be added to the discord official-links channel

Yes, in addition to the website. It should be added to the discord official-links channel

@odesium maybe a good time to use the carl-bot and add it to official-links

added here https://github.com/taikoxyz/taiko-mono/pull/436

Yes, in addition to the website. It should be added to the discord official-links channel

@odesium maybe a good time to use the carl-bot and add it to official-links

Added to Discord for more visability in Official Links.


Updated .pkgr.yml file to use rclone by default.

Hey Nick,
i updated my Packager.io yml file to look for rclone by default,  what i was doing was setting the path but further digging found that pkgr.io already has an golang based apps installed in /opt/.  for example rclone would be installed in /opt/rclone/bin/rclone.
Dedsec1

I've merged that - thanks!


Consistently uses LEB128 signed encoding for global constants

Global constants can be defined in wasm or in ModuleBuilder. In either
case, they end up being decoded and interpreted during instantiation.
This chooses signed encoding to avoid surprises. A more comprehensive
explanation was added to RATIONALE.md, but the motivation was a global
100 coming out negative.

Thanks for the help behind the scenes, @mathetake!


placeholders and sponge server

Does luckperms support placeholders on sponge server?
I would like use bungeeTablistPlus, but cannot get group placeholder to work.
https://www.spigotmc.org/resources/bungeetablistplus.313/updates

They're working here. Try updating to latest BTLP and BTLP-Sponge, and send the variable that you're using.

I have latest (2.7.2)

related issue on BTLP: https://github.com/CodeCrafter47/BungeeTabListPlus/issues/199

The BTLP author has replied on that ^^ issue with what the problem (probably) is.


Version pinning for meltano-map-transform

In follow-up to our slack discussion here, I realized the process did not account for matching up the version number in the tag with the version number in pyproject.toml. Since the version in pyproject.toml is 0.0.1, I think I will just delete the v0.1.0 tag and release and recreate as v0.0.1.
fyi @edgarrmondragon

I'll go ahead and take the immediate next action to recreate the release. Then we can discuss process here for keeping them aligned.

Update: I was able to "Edit" the release in the web UI, renaming the release and creating a new tag with the correct version number. Then I deleted the old tag (v0.1.0).
The link to the updated release is: https://github.com/MeltanoLabs/meltano-map-transform/releases/tag/v0.0.1

I've implemented the common version bump from the Meltano org: https://github.com/MeltanoLabs/meltano-map-transform/pull/56


rqt_graph: 0.4.9-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rqt_graph to 0.4.9-0:

upstream repository: https://github.com/ros-visualization/rqt_graph.git
release repository: https://github.com/ros-gbp/rqt_graph-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.2
previous version for package: null

rqt_graph
* fixes for Python 3 (#10 <https://github.com/ros-visualization/rqt_graph/issues/10>)
* only show namespaces if all entities have a common non-empty base path (#8 <https://github.com/ros-visualization/rqt_graph/issues/8>)

Enabled PR testing in 284e0211b9a440ae2b5e64c32fe0ccff714eb022.


test: Add test for S3 access points

Detail
Add test for read_parquet and to_parquet using S3 access points
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 98fece503dcd0acaf3d3f872aac38f0dcb9f68bf
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 98fece503dcd0acaf3d3f872aac38f0dcb9f68bf
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 98fece503dcd0acaf3d3f872aac38f0dcb9f68bf
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: fb08059be8dd12b40779e335f2a2153ac8b47719
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 66d6b62060d671cb16e1152bb9a39218db9c958d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 66d6b62060d671cb16e1152bb9a39218db9c958d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 66d6b62060d671cb16e1152bb9a39218db9c958d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 66d6b62060d671cb16e1152bb9a39218db9c958d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 66d6b62060d671cb16e1152bb9a39218db9c958d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Added one option as date in Automation

Description:  This will help in configuration with new trend. There is new way of setting time date in condition.:). This helps configuring on dates . if u want to check functionality go a head
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Please fill in the pull request template and include a description of this functionality. On top of that, include tests to show that the functionality works.

This PR seems to have gone stale. Closing it. You can reopen it when you're ready to finish it.


Fix client issues

This fixes multiple issues with the client that have been found during writing integration tests for the CLI.

Sorry. Today I won't care about diff coverage. Another day maybe.


domd: Fix list of installed packages

Acked-by: Volodymyr Babchuk<EMAIL_ADDRESS>

Acked-by is added.
@iusyk could you please merge this tested and reviewed PR?


Issue with configuration file: couldn't find any cluster

I read about this problem in other closed issues, but I really cannot understand what I'm doing wrong!
kafkahq:
  # list of kafka cluster available for kafkahq
  connections:
    test-1: # url friendly name for the cluster (letter, number, _, -, ... dot are not allowed here)
      properties: # standard kafka properties (optional)
        bootstrap.servers: "localhost:9092"

  # Basic auth configuration
  basic-auth:
    user: # Username
      password: pass # Password in sha256
      roles: # Role for current users
        - topic/read
        - group/read
        - group/delete

I launch the container in this way, because kafka is running locally.
docker run -d \
    --network="host" \
    -e MICRONAUT_CONFIG_FILES=/app/micronaut.properties \
    -v /data/kafkahq/micronaut/application.properties:/app/micronaut.properties \
    -v /data/kafkahq/application.yml:/app/application.yml \
    tchiotludo/kafkahq

I don't really understand why you use 2 different configurations files ?
As I know, micronaut can only have only 1 configuration file (except suffix with env).
Your docker exec let me think that only the first configuration file will be used.
Why not merging the 2 configuration file in 1 file ?

Because I didn't understand how to write correctly the configuration for micronaut...

I did it! Thank you!


[Erro create transaction with multi singature]

Describe the bug
when add more than one signature in transaction  don't open Phanton and have error :  ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
#Code
       var blockHash = await Web3.Instance.Wallet.ActiveRpcClient.GetRecentBlockHashAsync();
        Debug.Log($"{blockHash.Result.Value.Blockhash}");

        Account mintAccount = Web3.Instance.Wallet.Account;
        Debug.Log($"MintAccount: {mintAccount}");
        Account ownerAccount = new Account("", "9nQUWBRcxLH8d3UDD2e9vaRJcdGgR7rdZXGugZ9ES7FV");
        Debug.Log($"OwnerAccount: {ownerAccount}");
        Account initialAccount = new Account("", "87L945pDtH7LDP2fFugpDkQu8YdN2xXRLi5GxdQEnfqT");
        Debug.Log($"InitialAccount: {initialAccount}");

        var txBuilder = new TransactionBuilder()
            .SetRecentBlockHash(blockHash.Result.Value.Blockhash)
            .SetFeePayer(mintAccount)
            .AddInstruction(MemoProgram.NewMemo(mintAccount.PublicKey, "Hello Mehrdad :)"))
            .Build(new List<Account>() {mintAccount, ownerAccount, initialAccount});

        var sign = await Web3.Instance.Wallet.SignTransaction(Transaction.Deserialize(txBuilder));

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS:[android]
Browser [e.g. chrome, safari]
Version Solana [ 0.1]

@Mehrdadgame couple of issues, ownerAccount and initialAccount  have empty private keys, that will fail when signing.
Build method won't work for the same reason, if using an external wallet you should use Web3.Wallet.SignAndSendTransaction that will trigger the wallet signature.
Should be something like:
var blockHash = await Web3.Wallet.ActiveRpcClient.GetRecentBlockHashAsync();
Debug.Log($"{blockHash.Result.Value.Blockhash}");

Account mintAccount = Web3.Wallet.Account;
Debug.Log($"MintAccount: {mintAccount}");
Account ownerAccount = new Account();
Debug.Log($"OwnerAccount: {ownerAccount}");
Account initialAccount = new Account();
Debug.Log($"InitialAccount: {initialAccount}");

var txBuilder = new TransactionBuilder()
    .SetRecentBlockHash(blockHash.Result.Value.Blockhash)
    .SetFeePayer(mintAccount)
    .AddInstruction(MemoProgram.NewMemo(mintAccount.PublicKey, "Hello Mehrdad :)"))
    .Serialize();
var tx = Transaction.Deserialize(txBuilder);
tx.Sign(ownerAccount);
tx.Sign(initialAccount);
var sign = await Web3.Wallet.SignAndSendTransaction(tx);


Set query descending order from another class

I have this simple example in Parse.com Javascript SDK in the site that i'm building.
The Classes are the following
_User Structure:

objectId
username
password
name - string

Posts Structure:

objectId

postName - string

postMsg - string

postAuthor - Pointer< _User > (Pointer to the User Class)

Comments Structure:

objectId

msg - string

post - Pointer< Posts > (Pointer to the Posts Class)

user - Pointer< _User > (Pointer to User Class)

And i make this query to the Comments Class to take all the comments and also the Author's name and some other stuff.
var Comments= Parse.Object.extend("Comments");
var query = new Parse.Query(Comments);
/*Get the Post's Info*/
query.include("post");
/*Get the Post Author's Info*/
query.include("post.postAuthor");
/*Get the Comment's Author Info*/
query.include("user");
query.find().then(function(results){
    /* Go Through Each Comment*/
    var commentsArray = new Array();
    for(i in results){
        /* Set obj to current comment*/
        var obj = results[i];
        /* Get Post's Name */
        var postName = obj.get("post").get("postName");
        /* Get Post's Message */
        var postMsg = obj.get("post").get("postMsg");
        /* Get Post Author's Name */
        var authorName = obj.get("post").get("postAuthor").get("name");
        /* Get Comment's Message */
        var commentMsg = obj.get("msg");
        /* Get Comment's Author*/
        var commentAuthor = obj.get("user").get("name");

        /* Let's Put the Comment Information in an Array as an Object*/
        commentsArray.push({
            post:{
                name: postName,
                msg: postMsg
            },
            author: authorName,
            comment: {
                author: commentAuthor,
                msg: commentMsg
            }
        });
    }
})

So my question is, in this query how can i make the order of the results to be descending by "createdAt" from POSTS Class, and not from the Comments Class that the main query is?
Is there any way to do that?
Something like
query.descending("post.createdAt");

Any idea?

It could be better to do a
query.exists('post')
query.descending("post.createdAt");

just to guarantee that it will always work. But yes, that should definitely work.
p.s. The recommended way of initialising an array is with:
 var commentsArray = []

@Quaggie  nope its giving an 105 error that post.createdAt is not a valid field name

Yeah, this is a problem for me also. The Only solution i can think of personally is to use a cloud function, fetch everything, and the do sort, limit & skip "manually"


When versions mismatch, Bacalhau List reports no jobs

actually a mistake just because it defaults to only my jobs