Envoy Proxy Issue

Envoy Proxy Issue
Envoy Proxy Issue
Description:

I am trying to deploy envoy as a front proxy for tls termination and http-https redirection, in my kubernetes setup. Every external request is then frowarded to a backend service. Here are my envoy pods and the backend service pod(parp-82-594747ff67-z456h).
[root@kaas-adm-idev-rtp-master-0 ~]# kubectl get pods -n envoylayer
NAME                                READY   STATUS    RESTARTS   AGE
envoy-deployment-68b9474d48-dskrs   1/1     Running   0          22h
envoy-deployment-68b9474d48-jqdmz   1/1     Running   0          22h
envoy-deployment-68b9474d48-l9ml5   1/1     Running   0          22h
parp-82-594747ff67-z456h            1/1     Running   0          6d18h

The services are
[root@kaas-adm-idev-rtp-master-0 ~]# kubectl get svc -n envoylayer
NAME                  TYPE           CLUSTER-IP    EXTERNAL-IP    PORT(S)                      AGE
envoy-admin-service   NodePort       <IP_ADDRESS>            80:30684/TCP                 22h
envoy-service         LoadBalancer   <IP_ADDRESS>    <IP_ADDRESS>   80:32607/TCP,443:30820/TCP   22h
parp-82-service       ClusterIP      <IP_ADDRESS>            81/TCP
when i try to curl the Cluster Ip of the envoy-service. I dont see the request go to the backend service(parp-82-service) I see a 503 error instead.
[root@kaas-adm-idev-rtp-master-0 ~]# curl -kv https://<IP_ADDRESS>

About to connect() to <IP_ADDRESS> port 443 (#0)
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 443 (#0)
Initializing NSS with certpath: sql:/etc/pki/nssdb
skipping SSL peer certificate verification
SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Server certificate:

GET / HTTP/1.1
User-Agent: curl/7.29.0
Host: <IP_ADDRESS>
Accept: /

< HTTP/1.1 503 Service Unavailable
< content-length: 95
< content-type: text/plain
< date: Wed, 26 Jun 2019 14:48:56 GMT
< server: envoy
<

Connection #0 to host <IP_ADDRESS> left intact
upstream connect error or disconnect/reset before headers. reset reason: connection termination

My envoy.yaml has the following configuration
static_resources:
listeners:

address:
socket_address:
address: <IP_ADDRESS>
port_value: 80
filter_chains:

filters:

name: envoy.http_connection_manager
config:
codec_type: auto
stat_prefix: ingress_http
route_config:
virtual_hosts:
- name: backend
domains: ["*"]
routes:
- match:
prefix: "/"
redirect:
path_redirect: "/"
https_redirect: true
http_filters:

name: envoy.router
config: {}

address:
socket_address:
address: <IP_ADDRESS>
port_value: 443
filter_chains:

filters:

name: envoy.http_connection_manager
config:
codec_type: auto
stat_prefix: ingress_http
route_config:
name: local_route
virtual_hosts:
- name: backend
domains: ["*"]
routes:
- match:
prefix: "/"
route:
cluster: ping-service
http_filters:

name: envoy.router
config: {}
tls_context:
common_tls_context:
tls_certificates:

certificate_chain:
filename: "/etc/example-com.crt"
private_key:
filename: "/etc/example-com.key"
clusters:

name: ping-service
connect_timeout: 3.00s
type: strict_dns
lb_policy: round_robin
http2_protocol_options: {}
load_assignment:
cluster_name: ping-service
endpoints:

lb_endpoints:

endpoint:
address:
socket_address:
address: parp-82-service.envoylayer
port_value: 81
admin:
access_log_path: "/dev/null"
address:
socket_address:
address: <IP_ADDRESS>
port_value: 8001

Also when i check the logs on the envoy pod,I see this
[2019-06-25 16:29:56.842][8][info][upstream] [source/common/upstream/cluster_manager_impl.cc:137] cm init: all clusters initialized
[2019-06-25 16:29:56.842][8][info][main] [source/server/server.cc:462] all clusters initialized. initializing init manager
[2019-06-25 16:29:56.842][8][info][config] [source/server/listener_manager_impl.cc:1006] all dependencies initialized. starting workers
[2019-06-25 16:42:52.880][18][info][client] [source/common/http/codec_client.cc:118] [C6] protocol error: The user callback function failed
[2019-06-25 16:44:56.842][8][info][main] [source/server/drain_manager_impl.cc:63] shutting down parent after drain
[2019-06-25 18:56:35.493][14][info][client] [source/common/http/codec_client.cc:118] [C24] protocol error: The user callback function failed
[2019-06-25 20:29:52.818][16][info][client] [source/common/http/codec_client.cc:118] [C28] protocol error: The user callback function failed
If I login into one of the nvoy pods and try to curl to the backend service using the dns of the service, it works.
root@envoy-deployment-68b9474d48-dskrs:/# curl -kv http://parp-82-service.envoylayer:81

Rebuilt URL to: http://parp-82-service.envoylayer:81/
Trying <IP_ADDRESS>...
Connected to parp-82-service.envoylayer (<IP_ADDRESS>) port 81 (#0)

GET / HTTP/1.1
Host: parp-82-service.envoylayer:81
User-Agent: curl/7.47.0
Accept: /

< HTTP/1.1 404 Not Found
< Date: Wed, 26 Jun 2019 14:55:07 GMT
< Server: Apache/2.4.27 (Red Hat) OpenSSL/1.0.2k-fips
< content-length: 2500
< content-type: text/html;charset=UTF-8
< cache-control: private,no-cache,no-store,max-age=0
< X-Frame-Options: DENY
<

Could you please send me some pointers on how to debug further! Thanks!

It works once i remove the 'http2_protocol_options: {}' option. When i tried to send curl with the options --http1.1 or --http2. Neither worked. So not sure why removing the 'http2_protocol_options: {}' from the config worked.

@shwetaap http2_protocol_options applied on the outbound connection to the upstream, which might not have had H2 support (in particular for plaintext H2).

@htuch - I see. Thanks!


Create Video ++

ApexMarkt_de

Brief Description

Kindly briefly explain the changes you made here.
Requirements / Checklist

[ ] I have read the PR Guidelines.
[ ] I have read the Documentation.
[ ] I have updated the documentation accordingly(if required).

Related Issue

Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Screenshots (if available):

sdc

What is this?


Command to send quotes using API

Originally posted by @darkbits018 in https://github.com/KieranRobson/Clarence-Bot/issues/26#issuecomment-1278573021

Thank you Assign please

Hi @darkbits018
I was just wondering if you were still interested in completing this issue. No worries if not and ill unassign it!

Implemented in #80


IE 11 import problem

No import button:

Bumping this to current Milestone

Spent a lot of time today trying to make it work in IE - no luck.
Let's cease IE support until we have time and resources to fix it.

OK, let's detect for it and present a banner to the user. I'll UX it.

Some browsers do not offer full support for the BitShares wallet. ...

We recommend the chrome browser.

Correction, like you have it: "the Google Chrome Browser"

Updated.

Duplicate #474


webhooks: Add Buildbot integration.

With some minor changes by Eeshan Garg.
Fixes: #5639.
@mayankmadan: I had to make a few tweaks to your code that would have been harder to communicate via a review! Thanks for working on this! :)
@timabbott: Could you please take a brief look at the code that adds more information to the context dict? Thanks! :)

Posted some quick comments; where is the code for the builtbot-side project?  If it's a GitHub repo (and ot a PR to a main repo), we should move it into the zulip/ organization.

The zulip reporter for buildbot was implemented in this PR

@timabbott: Okay, so the code for the reporter is officially merged into the Buildbot's official GitHub repo now. As far as I can tell, the code @mayankmadan wrote for the reporter on Buildbot's end does expect the server URL. @mayankmadan: Would it be possible to change the argument name to server_url? I'm guessing since the argument isn't really optional, we can also just omit the name and pass in a positional value, right? :)

Yeah, making it a positional argument would also be very reasonable (in addition to changing the name in buildbot's repo).

@timabbott: Okay, so the code for the reporter is officially merged into the Buildbot's official GitHub repo now. As far as I can tell, the code @mayankmadan wrote for the reporter on Buildbot's end does expect the server URL. @mayankmadan: Would it be possible to change the argument name to server_url? I'm guessing since the argument isn't really optional, we can also just omit the name and pass in a positional value, right? :)

It does expect the server URL and not the whole API url. I named it 'endpoint' because I was using it to build the endpoint(if that makes any sense). That was a mistake on my part. I can open a PR to change the name  if you want. But how can it be optional? What could be the default value of the server URL?

@mayankmadan: Yes, if you could please change it to server_url and open a corresponding PR in Buildbot's repo, that would be great!

But how can it be optional? What could be the default value of the server URL?

No, it isn't optional. What I meant was that instead of passing the arguments by keyword (as one does for optional arguments to a function/constructor),
reporters.ZulipStatusPush(endpoint='{{ zulip_url }}', ...

we could just pass it as a positional argument and omit the keyword altogether, like so:
reporters.ZulipStatusPush('{{ zulip_url }}', ...)

The above code would eliminate confusion from the naming scheme! :)

No, it isn't optional. What I meant was that instead of passing the arguments by keyword (as one does for optional arguments to a function/constructor),

Oh, okay. I'm just wondering that won't it be better to use the keyword in this case to improve the readability?

Oh, okay. I'm just wondering that won't it be better to use the keyword in this case to improve the readability?

Yes, but making it positional allows us to merge this PR regardless of when the argument name change is merged in Buildbot upstream! :)
@timabbott: FYI, just updated this to pass that particular argument positionally, should be good to merge now! Thanks!

I think there's probably some minimum version of Builtbot needed that needs to be included here...

I think there's probably some minimum version of Builtbot needed that needs to be included here...

Buildbot 2.2.0 is the minimum version required

Cool, @eeshangarg can you tweak the text to mention the integration requires Buildbot 2.2.0?

@timabbott: Just updated this! :)

Merged, thanks @eeshangarg and @mayankmadan!  It's nice to close out an issue as old as #5639 :).


cache headers

Cache headers not yet used (for now the cache is hardcoded to 1 week, the same of what suggested for rpsl).

This is done.


Add readme, requirements.txt

Readme.md, requirement.txt is added now user can easy setup the project locally and run and able to work over it

requirements file itself as mentioned in the issue description after
understanding the python code is now added after careful reading the python
code sir now you can check and review my contributions
On Tue, Oct 10, 2023 at 10:11 AM Priyav K Kaneria @.***>
wrote:

@.**** requested changes on this pull request.
Readme is good, please add the requirements file itself as mentioned in
the issue description after understanding the python code
—
Reply to this email directly, view it on GitHub
https://github.com/ContriHUB/Binod-Merchandise/pull/7#pullrequestreview-1666136005,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXUFZN6BQ7KW2VTPFORTAGTX6TGXJAVCNFSM6AAAAAA5Y2PGN2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMNRWGEZTMMBQGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Any updates on this? The requirements.txt file is not yet pushed

Sir I created that txt file and pushed it as well but may be some technical
issue it's not showing up so I am going tho push once again by evening
after my classes
On Fri, Oct 13, 2023, 13:17 Priyav K Kaneria @.***>
wrote:

Any updates on this? The requirements.txt file is not yet pushed
—
Reply to this email directly, view it on GitHub
https://github.com/ContriHUB/Binod-Merchandise/pull/7#issuecomment-1761061814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXUFZN4YGUFWRWWWHPN7AZDX7DWZBANCNFSM6AAAAAA5Y2PGNY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Sir now is this in the right position?

Fixes #1


[WIP] Change type parameter order in Auth to trigger partial unification

Should fix #1506
I hope I haven't forgotten anything, and that sbt ci on my machine is reliable. We shall see :)

Hold on on this, a small git ****up. Will fix soon, apologies

Yeah, I had missed AuthenticationStore, so more work to do

The changes thus far look right.  It feels a bit unnatural to have the higher-kinded type last, but I'm for making partial unification work as expected.

Yeah I'm not really fond the aesthetics of it either, but can't think of any other way to make partial unification work in the current setting (type synonyms)

Just to confirm this is expected behavior that we care about the order of our types? I understand we need to, but this feels a little like a lesser authority and introducing oddness because of what I personally understand to be a compiler problem. Should we consider creating an issue on this topic in regards to partial-unification with scalac?

Good question.  Partial unification is always left-to-right, like a curried function.  I like this explanation for why it can't go both ways.

Yep, it definitely can't go both ways or you will have ambiguities, and the left to right order is consistent with the view of type constructors as curried type-level functions (which ofc they aren't in Scala, but it's a nice model to think in).
I think at some point there was talk of an annotation to signal that an F[A, B] should be unified right to left (it was also for aesthetic reasons, Bill Venners had a use case in ScalaTest iirc), but that didn't materialise, which I think is ultimately a good idea: you don't want something so fundamental to rely on a definition site annotation, it would be really hard to reason about what's going on in general.
The downside is that some constructs will look ugly: this is arguably one such case.

This also raises some questions on what types should be [F[_], A] and which must be [A, F[_]], and where to draw the line without confusing more than necessary.
If you fix the . in this PR, you still have that AuthedService.apply[F[_], A] returns an AuthedService[A, F].
There's also BasicAuth[F, A], DigestAuth[F, A] and AuthenticationStore[F, A] (and probably more), that I don't think needs to be [A, F], but it might be more intuitive to have all the *Auth* stuff be [A, F].

Where to draw the line is ambiguous enough to me I'm going to be deferential to those with more hands-on experience with our auth middlewares.

@aeons I'm in the process of doing the changes for everything (emacs broken, so kinda manually...) just for the sake of consistency. I think the immediate issue is solved by AuthedService alone

Assuming this builds now (I think it does), I think all that's left is changing AuthedService lift and empty. Anything else you can think of?

At this point, I think just changing AuthedService looks right.  I wanted to be consistent, but we could argue that flipping so many of these is so inconsistent with general expectation that we just have to live with the fact that AuthedService is the outlier.  I'd flip that alias, leave a scaladoc on why it's flipped, and call it a day.
I remain highly deferential on this, but there's my tiny stake in the ground.

@rossabaker I have actually come around to pretty much the same position while in the process of doing this. So unless anyone has a strong counterargument, I will revert and:

change the AuthedService alias (+ scaladoc)
The apply AuthedService
I'm not sure about AuthedService#empty and the deprecated  AuthedService#lift
Don't touch the rest of the Auth stuff (although I share your position of being deferential on this)

I also hope you're ok with all the rebasing...

I think empty should follow apply.  I'd flip that.
I think lift is deprecated so it's best not to touch that.  We want to catch people who used to use it, not make it work better.
I am perfectly fine with all the rebasing. :)

@rossabaker Will @deprecated on lift still trigger, since I will have to change the return type (I can choose not to change the type variables, as you suggested)

I think it will still trigger, but I'd have to try it.  I doubt it was frequently called, so I would not spin wheels over that.  I feel strongest about apply and empty.


Change Fail to Ignore on failurePolicy for Admission Controller

Summary
Changing failurePolicy from Fail to Ignore to match 2.5.0 and newer KIC version defaults.
Reason
In KIC 2.5.0 and higher, we changed the Admission Controller to use a new default of Ignore instead of Fail, so just bringing the docs into alignment too. Ref: https://github.com/Kong/kubernetes-ingress-controller/issues/2501

@d19dotca We've changed how we author docs to ensure that when we fix bugs like this, all versions are updated.
Unfortunately it adds a little bit of complexity to how we make changes that occur from a specific version. I've updated this PR to show you how it works. If you want a hand in the future, let me know and we can run through it together


Additional claims for all users signing from different IP's via B2C Ad

I have a requirement, wherein I provide multiple IP's (Identity Providers) to login with and after successful authentication, I must get additional claims to my application that are only in B2C AD. Is it possible?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fc5e148d-b7cf-92e7-4cc7-a65d20d037b6
Version Independent ID: 2ba6e31b-5899-f35a-0f08-d280110ded13
Content: Frequently asked questions for Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-faqs.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@nkumars Thanks for your feedback! We will investigate and update as appropriate.

@nkumars Please refer to Azure Active Directory B2C: Use custom attributes in a custom profile edit policy to add custom claims to ID token sent back from the application.

@nkumars We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Weight and cosine norm

Adds two layer_regularizers:

Weight normalization https://arxiv.org/abs/1602.07868
Cosine normalization https://arxiv.org/abs/1702.05870

Also adds linear_type that can be set to either weight, cosine or regular.  Defaults to regular if unspecified
TODO:

[ ] decide upon a weightnorm implementation
[ ] weightnorm linear_type
[ ] unit test
[ ] example config
[ ] extract least squares commit beb1787

I think it's fine to have weight_norm and weight_norm2 for now.  weight_norm2 seems to work better in my testing.
I've been using this so it's probably safe to merge in.


Possible improvement course

Show mask data on the first exercise, cell classification,  in addition of the bounding boxes

Add in between some task for the students. For instance plot an additional image for looking at the data

Resize and padding. A resize of images is probably not a good idea if a phenotype makes very obligated cells instead of round.
this could be a small idea of thinking about it for the students

May be a little confusing on how training loss and validation loss plot. One is running average per iteration the other is per epoch

The weight exercises should be more explained. Also the syntax on how to do
something like
w1 =1 w2 =1 torch.tensor([w1, w2])
The student should modify w1 and w2 in a meaningful way.

Exercise for the segmentation with self-trained model could be to adapt image size to match the network

Exercise of the U-Net receptive field could be to input a pixel and look how it propagates

Add more image analysis to exercise 3: also apply classification model and measure the serum intensities of infected and non-infected cells.

Make listing of files OS independent. For instance do not use ls but more os or glob


Query optimization throughout site

Why u no respond quickly?

I went through the site (with 5000 packages in place), captured all SQL statements executed, ran them in SQL Management Studio, reviewed their execution plans, and added a few indexes.  We should be good for now.


Improve primary interface

This branch will

Add a full primary client object structure to the client
Read more data from the primary interface
Show users when they send malformed script code to the robot
Inform users when they are trying to send script code to an e-Series robot which is not in remote control mode
Output any error messages coming up on the robot

I am not sure yet, to which extent all of those things will be tackled in this MR, but it will definitely be a start from which such features could easily be implemented.

Closing this in favor of #186


Creating observers on frozen objects?

Our Aurelia application is using Redux. We have everything hooked up and we're looking at different immutability options. The ones we can find are immutable.js and redux-freeze. With immutable.js, the API makes it really complicated for simple data objects we get from an API. Combine that with TypeScript, and it makes for a lot of extra work to just get typings to work properly as well. We love the idea of using redux-freeze, as Object.freeze will just make everything immutable, and leave it up to the developers to create new instances of their models.
The problem, however, is that we can't add observers to a frozen object, since Reflect.defineProperty will fail to add the __observers__ property.
This isn't specifically an aurelia issue, since you can easily reproduce this with:
let obj = {};
Object.freeze(obj);
console.log('Added property?', Reflect.defineProperty(obj, 'test', {})); // false

But I was wondering if there's any way to work around this problem? Would a custom ObserverLocator that returns new instances of the object instead of mutating its properties work? We'd like to avoid immutable.js if possible.
Thanks!

One solution is to replace the methods on the ObserverLocator with alternate implementations, yes. You use a WeakMap. In the future, this may be what we switch to internally as well. Since it's not universally implemented across the browsers we support, we use the hidden property.

Hello,
Implementation with WeakMap should be default behavior with fallback using the hidden property, in my opinion. This would allow full usage of Immutable structures (that are popular these days) with Aurelia.
Tomáš

I think WeakMap polyfills use the hidden property method so it is safe to switch to WeakMap assuming there are no other regressions.

I was further thinking about the issue and I think I was wrong. There is no need for an observer in case of immutable structures in a first place (besides getting rid of warnings).


v1.24 release

Signed-off-by: Tom Zhang<EMAIL_ADDRESS>

I will merge after master is promoted (GA'd)


Let's finish them ASAP. @fengjiachun @MichaelScofield @nicecui

All the tasks are already done.


[Feature] Support full statistics as default collect strategy

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

run starrocks_admit_test

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 4 / 16 (25.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/statistic/StatisticAutoCollector.java
0
1
00.00%
[64]

:large_blue_circle:
com/starrocks/statistic/StatisticsCollectJobFactory.java
0
4
00.00%
[83, 84, 86, 111]

:large_blue_circle:
com/starrocks/statistic/StatisticsMetaManager.java
0
2
00.00%
[354, 355]

:large_blue_circle:
com/starrocks/statistic/AnalyzeManager.java
0
4
00.00%
[142, 143, 158, 159]

:large_blue_circle:
com/starrocks/statistic/StatisticExecutor.java
2
3
66.67%
[65]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
2
2
100.00%
[]


[dart:html] Streams from window.on[...] emit 'NativeJavaScriptObject', not Event$

If you aren't sure, file the issue here and we'll find the right home for it.
In your issue, please include:

Dart SDK Version 2.3.0-dev.0.3
MacOSX Mojave (or whatever the newest update was, haha)
Chrome 73.x

I have a case where I create a separate window using window.open. This secondary window performs an OAuth2 flow, and then runs a small JS script that sends a CustomEvent to window.opener.
I listen for this event using window.on:
window.on['token'].listen((Event ev) {
  if (ev is CustomEvent) {
     // ... Do stuff here...
  }
});

Unfortunately, though, I get this error:
dart_sdk.js:5844 Uncaught Error: Expected a value of type 'Event$', but got one of type 'NativeJavaScriptObject'
    at Object.dart.throw (dart_sdk.js:4556)
    at Object.dart.castError (dart_sdk.js:4516)
    at Object.dart.as (dart_sdk.js:4856)
    at Function.check_C [as _check] (dart_sdk.js:4036)
    at Object.dart._checkApply (dart_sdk.js:4666)
    at Object.dart._checkAndCall (dart_sdk.js:4748)
    at Object.dart.dcall (dart_sdk.js:4756)
    at dart_sdk.js:98030
    at :3001/auth/myapp/callback?code=6c3e3a96274a4bab9b5a8410d425befa&state:8

This is my JS script:
var ev = new CustomEvent("token", {"detail":"<the jwt>"});
window.opener.dispatchEvent(ev);
window.close();

It seems that my function isn't being passed an Event. Any idea what could be happening here?

So what I'm getting from this is, window.on is useless without interop? And CustomEvent is only for dispatching events, not receiving them?


Not working while crawling

playing tnp limitless 6, the auto walk keybind does nothing while crawling, not sure which mod adds the crawling, but while crawling through a 1x1 tunnel auto-walking doesn't work at all

nvm, different mod adding this auto walk


Add OnePlan Connector

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@microsoft-github-policy-service agree company="OnePlan Solutions LLC"

@vmanoharas Hi, we've updated the PR to ensure paconn validate succeeds. Please review.

Hello @Abdul-Sen,
Readme.md file is not yet updated with all the required sections, please update.

Hello @Abdul-Sen,
Readme.md file is not yet updated with all the required sections, please update.

Hello @Abdul-Sen,
I am following up on my previous request, kindly resolve review comments.

Hello @Abdul-Sen,
I am following up on this PR to resolve review comments, kindly resolve.

Hi @vmanoharas , we'll try and update it by today


Render when state changes

I have simple component that shows the UserName.  Another authentication js library displays an IFrame and in the OnLogin Method I update the UserName.  But because no event in the UI triggers this, the component does not Re-Render.
How can I get this to re-render when the state changes?
Just to confirm to myself the UserName was set I added the button which when clicking will trigger a re-render and properly show the UserName.
@inherits AppHeaderModel

  @UserName
  <button class="btn btn-primary" onclick="@StateHasChanged">Click me</button>

If you're updating the UserName from JS, you should be able to use the Javascript interop to call back to .NET and have it re-render using StateHasChanged().
If you are updating UserName from C#, can't you just call StateHasChanged() directly after?
If I'm not fully understanding the context, let me know.

It is via Js Interop that I call back to .Net and from there I update the UserName.  But the code that updates the UserName doesn't know which components are display its value.  So you don't know where to call StateHasChanged().
I am not using SignalR but it is a good example.  Say SignalR sends a message to change some value and that value is being displayed in a component.  How could the SignalR handler know which components to update and even if it did know how could it get an instance of them?
So you have to do some pub sub type option I think.  Just wondering how others are solving this.

I use a client service component with events to address this scenario. So in your example the service would have a UsernameChanged event handler which your username module would subscribe to. The service also has a RaiseUsernameChanged() method that you would call after the username is updated. RaiseUsernameChanged() fires (Invokes) the UsernameChanged handler(s) and your username component calls StateHasChanged(). Blazor services are implemented using the built-in DI support. Here's some good docs on Blazor DI and services: https://learn-blazor.com/architecture/dependency-injection/

Thanks guys for the input.  I will give it a go.

@JoelW187 Would you be kind enough to share an example? I have been trying to figure it out for the past couple of days but no luck.


feat: implement chr, ord, and hex

Type of change

New feature or functionality (change which adds functionality) #418

Relevant documentation has been updated

Test plan

New test cases added

Another nit: how did we decide on string.bzl as the public API rather than strings.bzl ?

Another nit: how did we decide on string.bzl as the public API rather than strings.bzl ?

we haven't actually. open to suggestions. strings.bzl sounds more appropriate to me.

to get this going; assuming Alex and I agree on strings.bzl, should I rename this to strings.bzl?

yes please, let's go with that. Unless you can find some other starlark implementation that already has a name for a module that provides these (but I expect there isn't since they're proposed as builtin keywords)

but I expect there isn't since they're proposed as builtin keywords

true. renamed to strings


Add generated catalogue models

This PR adds modules generated from the catalogue endpoint's openapi definition.
Changes included:

Add api definition and generator config in ./SourcesCatalogue/openapi
Add generated models in ./Sources/Generated/Models
Exclude Generated folder from swiftlint checks

This is only part of the code generated by openapi-generator. But as there are still open questions as to what the final catalogue module should look like, only the models will be added at this point - the rest to follow once we have the full design spec.

Unfortunately @bkdl is out, but he already tried to use the openapi-generator for the Creator content project and ran into some issues.
I think it was something about a module depending on another module that auto generated the code not having access to the code (had not been generated yet)
In this case, as you are committing the generated code, I think it should be fine.  Is not the default recommendation in their FAQ
https://swiftpackageindex.com/apple/swift-openapi-generator/1.2.1/documentation/swift-openapi-generator/frequently-asked-questions#Do-I-commit-the-generated-code-to-my-source-repository

Unfortunately @bkdl is out, but he already tried to use the openapi-generator for the Creator content project and ran into some issues.
I think it was something about a module depending on another module that auto generated the code not having access to the code (had not been generated yet)
In this case, as you are committing the generated code, I think it should be fine.  Is not the default recommendation in their FAQ https://swiftpackageindex.com/apple/swift-openapi-generator/1.2.1/documentation/swift-openapi-generator/frequently-asked-questions#Do-I-commit-the-generated-code-to-my-source-repository

This is a super early-stage commit. We agreed that for now, we would just exposer the model classes so they can be used if needed, for preparing the integration.
We need to first figure out what exactly the final result is supposed to look like, and hopefully the code generation will play along. So in the future they might be removed again in favor of an automated step.

Unfortunately @bkdl is out, but he already tried to use the openapi-generator for the Creator content project and ran into some issues.
I think it was something about a module depending on another module that auto generated the code not having access to the code (had not been generated yet)
In this case, as you are committing the generated code, I think it should be fine.  Is not the default recommendation in their FAQ swiftpackageindex.com/apple/swift-openapi-generator/1.2.1/documentation/swift-openapi-generator/frequently-asked-questions

This PR is using a different open api generator. It doesn't provide a plugin and besides I think not polluting the build step with building the files every time makes sense.
the generated files from this generator also are nicer split apart


separate packages for envoy v1/v2 code

This is a non functional code move PR. We can extract reusable components over time. Sorry about the code churn, but wanted to get this over with early in the release cycle when things are more relaxed.
This is not just a cleanliness move. As we start adding code for v2, we need to make sure that any addition to v1 in the interim gets reflected in v2.
@costinm while we decided to keep v1 code as is in our offline convo, I realized that folks not using Goland (vim/emacs/etc) are prone to confusion when they see v1 code under proxy/envoy, and v2 code under proxy/envoy/v2/. Especially when working on v2 functionality, they are likely to touch something in the proxy/envoy/config.go, but not realize that it will be v1 only.
I have been through other open PRs. There is only one that gets impacted potentially.
All existing code in proxy/envoy/ is now in proxy/envoy/v1 (watcher.go could be reused but thats for another separate PR).
New code that is v2 specific (discovery servers, etc.) will be in proxy/envoy/v2. I also got rid of the pilot/pkg/dataplane since we now have v2. This atleast ensures that folks familiar with the code base under proxy/envoy will be able to easily adapt to the slightly modified structure.
@nmittler I have moved the mock package into proxy/envoy/v1/mock as it has v1 based discovery servers. If we can abstract it, then mock could move to proxy/envoy/.

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
7b440b633b019a627458ee49953292acdb585f4c
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
9d13e518d2bea1d942a33cfd1b11af99d938ae9d
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
131410d70026fcbf0b9737062ac91eaebbf5e23c
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
984ffc11a9f9256cf23e2252912e9ddbf0b73a9c
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
984ffc11a9f9256cf23e2252912e9ddbf0b73a9c
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
984ffc11a9f9256cf23e2252912e9ddbf0b73a9c
link
/test e2e-smoke

prow/istio-pilot-e2e.sh
984ffc11a9f9256cf23e2252912e9ddbf0b73a9c
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
984ffc11a9f9256cf23e2252912e9ddbf0b73a9c
link
/test istio-pilot-e2e

prow/e2e-smoke.sh
2b7176d57f4bb01a3f5bcde196955573886ff69a
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
2b7176d57f4bb01a3f5bcde196955573886ff69a
link
/test e2e-smoke

prow/istio-pilot-e2e.sh
2b7176d57f4bb01a3f5bcde196955573886ff69a
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Prow is still failing.. I am looking for circleci failures..

Did we wanna do envoy->dataplane?

I thought about it and I left it as such, so that people working on the code don't get disoriented when the see a new folder, but lose the old one. I have no strong preferences through. Neutral on the front. Happy to rename if you feel so.


[Bug]: ToList python examples are broken

What happened?
page: https://beam.apache.org/documentation/transforms/python/aggregation/tolist/
context: https://lists.apache.org/thread/4g97cqmd2vh68x5k8mp65wztpgdocffb
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[X] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[X] Component: Website
[ ] Component: Infrastructure
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

Duplicate of: https://github.com/apache/beam/issues/32544


[cbuild] extend the orchestration to include the csolution convert step for "configuration"

Objective: Orchestrate the build of a pre-configured csolution format project to the build of the artifacts of all contexts belonging to the same build- and target-type

command to list all build- and target-type combinations of a csolution := configurations.

command to build all artifacts of the contexts of the specified build- and target-type combination (projects of a solution configuration)
cbuild -s <mysolution>.csolution.yml -c .<myBuild>+<myTarget>

if --packs is specified missing packs should be installed automatically:
csolution -s <mysolution>.csolution.yml  list packs -m > packlist.txt
cpackget add -f packlist -a

to find out which project contexts belong to the solution context run
`csolution -s .csolution.yml  list contexts

From the contexts.txt all projects with the selected .<myBuild>+<myTarget> are converted and then fed into cbuildgen
Note: In the absence of dependency resolution the project contexts are built in the order the projects are listed in the *.csolution.yml file.

CMSIS-Toolbox 1.5.0


(GH-651) Improve Tile View

So that the latest Version do not overlap the current Version when an update is available.
Version numbers now in lower left corner. Also move the package name on top and the Out of Date/Installed overlays on the bottom right hand corner.

Closes #651

@punker76 this looks amazing to me!  Thank you very much for taking the time to do this!

@punker76 I have rebased and merged this here: https://github.com/chocolatey/ChocolateyGUI/commit/2cb89c563a5bd5933a8bbb0ed197639f011457cd

@punker76 your changes have been merged, thanks for your contribution 👍


guzzle classes missing

i tried to use guzzle in SS4 rc1, but some classess (client) are missing. Error is Class 'Client' not foundHere's the code:
    public function getArticles() {
        $client = new GuzzleHttp\Client(array('base_uri' => 'http://jsonplaceholder.typicode.com/'));
        $res = $client->request('GET', 'posts');
        print_r($res->getStatusCode());
        print_r($res->getHeader('CONTENT-TYPE'));
        print_r($res->getBody()->getContents());
    }

@guyvanbael you’ll need to install guzzle yourself (http://docs.guzzlephp.org/en/stable/overview.html#installation). I believe an older 4.0.0-alpha release would’ve had it bundled (we used to use embed/embed: ^2.6 which would’ve included guzzle), but that’s no longer the case.

@guyvanbael generally you shouldn't rely on implied dependencies; if you use a class/lib make sure to include that in your own project's requirements

it's working now. Thanks guy's!


Remove Kerberos functionality from the Directory Server

Is this removing all support for using Apache DS as a KDC?

IF the PR is approved, then yes. It's not maintained, and we have another project (Apache Kerby) that handles KDC support.

Thank you, we have quite a few projects using ApacheDS for testing, I will have a look at Apache Kerby.

First remarks:
I get a compile error:
[ERROR] server-integ/src/test/java/org/apache/directory/server/operations/bind/SaslBindIT.java:[195,9] cannot find symbol
  symbol:   variable KerberosTestUtils
  location: class org.apache.directory.server.operations.bind.SaslBindIT

Otherwise I see that there's still lot of Kerberos related code and config left, (grep for kerberos and krb) e.g. in kerberos-codec, protocol-shared, and interceptor-kerberos. Is that intentional? I must admit I don't have an overview which parts are used for what, and if we .e.g. want to keep GSSAPI authentication.

@darranl should be obvious for Apache projects: volunteers are welcomed :-)

@seelmann I accidentally forgot to commit KerberosTestUtils, the build should be passing now.
Regarding interceptor-kerberos, I didn't remove this because it's used in the @CreateDS part, and not in the old KDC server annotation:
additionalInterceptors =
    {
        KeyDerivationInterceptor.class
})

If someone tells me it should be removed as well, then it can be removed for sure. The kerberos stuff in protocol-shared is used by the Gssapi classes in protocol-ldap. Both these rely on kerberos-codec in turn.

I'm not against removing the Kerberos Server from Apache DS. It lags behind, and I do think Kerby is way more avanced and up to date.
I understand that we offer a convenient testing environment for Kerberos, and it would be cool to write down how Kerby could be used to do the same thing.
In any case, I'm +1 for the removal (it's in git anway, would we want to revive it, it  would be a breeze).
Note: we will have to get rid of the Studio part that deals with Kerberos too. One good thing would be to make it so that Studio can handle Kerby config, but that is a lot of work...

@darranl should be obvious for Apache projects: volunteers are welcomed :-)

So many projects so little time :-)  Will see what kind of things we start to find when we migrate.

@seelmann Should that commit have gone straight to master? Not sure why it was merged to this PR? By the way on master, the "apacheds-core-integ" tests are now running very slowly on my machine with the latest junit changes.

I think the PR should be merged with trunk.
The reason the tests are slow is probably because of an issue in teh way
we deal with 'rollbacks' in tests. Let me explain:

when we start a test in a class containing many, we set a mark, and at
the end of the test - whether it's a success or a failure - we rollback
the modifications that have been applied during the test (we have an
interceptor that registers every modification and compute the reverse
operation).
for some reason, I suspect that we don't move the mark forward after
each test (we should), and the consequence is that we replay all the
reverse operation for all the already run tests. This is cumulative.
I have fixed the issue but have had to rollback it due to some other
test failures my push has induced.

Note that this is an hypothesis, which I see confirmed on master before
my reverted fix.
I will try to get master fixed this week.
 Not sure why it was merged to this PR? By the way on
master, the "apacheds-core-integ" tests are now running /very/ slowly on
my machine with the latest junit changes.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/apache/directory-server/pull/46#issuecomment-827348940,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWJQFOTLVTKLTM66MGHTXDTKZKVJANCNFSM43MFZAFA.

--
Emmanuel Lécharny - CTO 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
@.*** https://www.busit.com/

Note: we will have to get rid of the Studio part that deals with Kerberos too. One good thing would be to make it so that Studio can handle Kerby config, but that is a lot of work...

Yeah it will be a shame to loose the studio part, over the years that has been very useful to start up the studio and have an environment up and running with a directory server and KDC to develop against - but as you say it sounds like that would be a lot of work.

Hi Daranl, you can still use a version of Studio that can launch the ApacheDS Kerberos server until we have Kerby embedded. I don't think any change made on Studio in the coming months (years) will require you to switch.
As mentionned by Colm, The ApacheDS Kerberos server hasn't evolved for years, and is very likely to be at best not complete.

One thing I was thinking about in the past @elecharny is if I could embed Apache DS (and now also Apache Kerby) into the WildFly application server so we could have a directory server and KDC directly available.  We have undertaken quite a bit of work to allow users to dynamically define the features they want in their server so maybe these could features our users would be interested in adding.

A long time ago, we did some experiment:
https://cwiki.apache.org/confluence/display/DIRxSBOX/ApacheDS+as+a+Tomcat+Realm
Ok, 12 years ago ! Time flies...
Technically speaking, that should be easy. Now, I'm afraid that the 'glue' will be the JNDI layer - which is still present in ApacheDS - but that a ugly one.
Certainly something to consider.

yes, Colm, the FrameworkRunner class does not exist anymore, it's replaced by Junit5 extensions.
Some tests in Master are still referring this class, and that are the tests I have to fix.

OK I will wait before merging this PR until master is properly fixed, as otherwise it is a pain to rebase branches.

@coheigea Sorry for the confusion. It was meant for this PR to be able to run the tests. Reverted it again.

Junit5 migration status:

I have fixed the slowliness of core-integ tests (it was exactly what I described). All are now passing green
I'm fixing the server-integ tests. It's not complicated, just a matter of replacing @RunWith with @ExtendWith andd a few other changes like that. Should be done tonite.

Most of the server-integ test are now ok, still a bit of work with:

CreateLdapConnectionPoolRule that has to be removed
The MultiThreadedMultiInvoker @Rule has to be removed

Replication tests are likely to be reviewed after my changes

a few tests aren't passing, most certainly because of some bug in the ApacheDSTestExtention class I wrote to replace theh FrameworkRunner.

I will continue later today.

Btw, I would be grateful if someone has an idea on how to replace the MultiThreadedMultiInvoker @Rule in Junit5.

Btw, I would be grateful if someone has an idea on how to replace the MultiThreadedMultiInvoker @rule in Junit5.

Just remove it. Most places use it in the default config with 1 thread and 1 invocation so it's pointless. Replacement for repeated invocations would be the @RepeatedTest annotation

Done.
[ERROR] Tests run: 539, Failures: 13, Errors: 9, Skipped: 15
Still have 22 errors to fix in server-integ, which is not too bad (~4%).

Making progress. Still a few errors in server-integ tests.
I have some concern about the {{SaslBindIT.testSaslGssApiBind}} which expect the Kerberos server to be up and running:
{code:java}
/**
* Tests to make sure GSS-API binds below the RootDSE work.
*/
@Test
public void testSaslGssApiBind() throws Exception
{
Dn userDn = new Dn( "uid=hnelson,ou=users,dc=example,dc=com" );
LdapNetworkConnection connection = new LdapNetworkConnection( Network.LOOPBACK_HOSTNAME, getLdapServer().getPort() );
    kdcServer.getConfig().setPaEncTimestampRequired( false );

    SaslGssApiRequest request = new SaslGssApiRequest();
    request.setUsername( userDn.getRdn().getValue() );
    request.setCredentials( "secret" );
    request.setRealmName( ldapServer.getSaslRealms().get( 0 ).toUpperCase( Locale.ROOT ) );
    request.setKdcHost( Network.LOOPBACK_HOSTNAME );
    request.setKdcPort( 6088 );
    BindResponse resp = connection.bind( request );
    assertEquals( ResultCodeEnum.SUCCESS, resp.getLdapResult().getResultCode() );

    Entry entry = connection.lookup( userDn );
    assertEquals( "hnelson", entry.get( "uid" ).getString() );

    connection.close();
}

{code}
atm, I can @Ignore this test, but this is quite a interesting test to have. Is there a way to have Kerby used instead ?

I can look into using Kerby with this test. I'll wait until you push your changes to master though, because right now on my branch the tests aren't run in this module.

Server-integ tests are now all passing (I have @Disabled the SASL test atm).
I have to fix the LDAP API tests errors, and I think I'll be done.
BTW, I had to get rid of some of the Kerberos parts as I didn't want to put any effort in migrating the Kerberos Server init in the extensions, so part of the Kerberose riddance will be done in trunk.

Update: I have 9 tests failures in ldap client API tests, all of them being caused by the lack of the connection pool Rule being ported. The following modules are all passing green, which means I'm close to completion.

I'm afraid that Apache Directory Server cannot be used as an opensource alternative of microsoft active directory.
It is quite useful to operate it as an authentication server for both ldap and kerberos because it will use the same account for both protocols without additional password synchronization between ldap and kerberos.


upload when image is loading ，change router ,error: Cannot read property 'unsubscribe' of undefined

Version
1.6.0
Environment
google 浏览器
Reproduction link
https://ng-zorro-antd-start.stackblitz.io
Steps to reproduce
core.js:1673 ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'unsubscribe' of undefined
TypeError: Cannot read property 'unsubscribe' of undefined
at ng-zorro-antd.js:36961
at Array.forEach ()
at NzUploadBtnComponent.push../node_modules/ng-zorro-antd/fesm5/ng-zorro-antd.js.NzUploadBtnComponent.abort (ng-zorro-antd.js:36960)
at NzUploadBtnComponent.push../node_modules/ng-zorro-antd/fesm5/ng-zorro-antd.js.NzUploadBtnComponent.ngOnDestroy (ng-zorro-antd.js:37010)
What is expected?
解决
What is actually happening?
暂无
Other?

我也出现了这个问题，请问是如何解决的？🙏


HTMLElement.shadowRoot is deprecated.

The contents of atom-text-editor elements are no longer encapsulated
within a shadow DOM boundary. Please, stop using shadowRoot and access
the editor contents directly instead.
HTMLElement.shadowRoot (/usr/share/atom/resources/app/src/text-editor-element.js:13:10)
MarkdownScrlSync.getVisTopHgtBot (/home/Ting/.atom/packages/markdown-scroll-sync/lib/utils.coffee:20:33)
MarkdownScrlSync.setMap (/home/Ting/.atom/packages/markdown-scroll-sync/lib/map.coffee:25:14)
MarkdownScrlSync.startTracking (/home/Ting/.atom/packages/markdown-scroll-sync/lib/main.coffee:75:12)
<unknown> (/home/Ting/.atom/packages/markdown-scroll-sync/lib/main.coffee:58:23)
Function.module.exports.Emitter.simpleDispatch (<embedded>:63490:20)

duplicate of #94


The meaning of each image in the preprocessed objaverse-lvs dataset

Hi, @Colin97
Could you please explain the meaning of each image in your preprocessed objaverse dataset? BTW, how can I have the mask which contains only the foreground for each image?

view_i_j_10_gt.png is the $i^{th}$ view's $j^{th}$'s nearby view, where $i \in { 0,...,7 }; j \in { 0,...,3 }$. 10 means the nearby view is $10$ degrees away. view_i_j_10_gt_depth_mm.png stores its corresponding depth image in millimeters.


Fix error message claiming non-regular files are directories

Fixes #4834
How was this PR tested?
Not at all, simple string update.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Suggestion: "update" command

To pull the latest files from GitHub and install them automatically.

@RamiLego4Game

I didn't forget about this suggestion, I did even add the "ZIP drive" functionality for easier installation from github repos.
The problem is that I'll have to place DiskOS in a separate repo, and do some engine version tests.
If you mean you want to update whole LIKO-12, that would be like an option in the BIOS setup, but what if I decided to update LÖVE or change some native libraries ?


Terminate Session takes too much time

Created by: @marvinkite Mar 14 2021 at 10:00 CET
Last updated: Dec 02 2021 at 21:55 CET
ClickUp ID: IK-700
Selena -> Hera -> Hermes communication takes too much time for unknown reason.

Commented by: @marvinkite Mar 30 2021 at 08:30 CET
Neo4j Health Check is activated and it restarts the service if database is not responding. The distributed tracing also trace every request not to catch the reason if it occurs again.

Closed: Mar 30 2021 at 13:49 CET


Create the C# Guide Overview index page

This new page will be formed from the existing "Tour of C#" introductory page. It should include the opening, up to "Hello World", and the links following the sample.
The content from "Introduction to C# and .NET" topic under Getting Started needs to be moved to the "Overview" section and updated in the following ways:

Cross platform and .NET Core.
New workloads (mobile, web jobs, unity)
New language comparisons, including JavaScript, Ruby and Python.

I'm pushing this back into the backlog.  I'm starting work on planning that may change the tasks here somewhat. It will resurface once that work is done.

Upping the priority because it's been bumped several times.

Closing. This page doesn't fit the new TOC.


Add a way to inter-call(msg and query) using protobuf messages (stargate msg, stargate query)

Research Report
Almost all messages in https://github.com/line/cosmwasm/blob/main/packages/std/src/results/cosmos_msg.rs correspond to SDK's message and are handled by https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/handler_plugin.go#L368-L411 except BankMsg::Burn and IbcMsg::SendPacket. Other than these two messages have proto form and can use CosmosMsg::Stargate.
How to encode and decode data of IbcMsg::SendPacket is on each contract, so can be a proto message.
BankMsg::Burn and IBCMsg::SendPacket are handled by https://github.com/line/lfb-sdk/blob/7214594363f82d35245b7a0ea6d98397dfa3a78f/x/wasm/keeper/handler_plugin.go#L413-L523 part. These two messages request sdk/x/wasm using a handler chain to handle msgs from contracts. If we remake the interface of cosmwasm contract's response and separate these two messages and other messages into two vectors (arrays), it can be more simple. I think it should be discussed in another issue.


Library crashes build time on iOS

Could not find "/Users/schadenfreude/.gradle/caches/modules-2/files-2.1/app.softwork/kotlinx-uuid-core-iosx64/0.0.16/8ec27f37d3e7e7ecae239da2390b131b3b09417/kotlinx-uuid-core.klib" in [/Users/schadenfreude/StudioProjects/project/mobile, /Users/schadenfreude/.konan/klib, /Users/schadenfreude/.konan/kotlin-native-prebuilt-macos-aarch64-1.6.21/klib/common, /Users/schadenfreude/.konan/kotlin-native-prebuilt-macos-aarch64-1.6.21/klib/platform/ios_x64]
I'm getting this when I try to compile my iOS project with version 0.0.16 and 0.0.17 (tested only these 2). The Android project runs without problem.

Hey, I didn't see this issue. What Kotlin version do you use?

Kotlin plugin and stlib version used was 1.7.10

0.0.16 and 0.0.17 are identical, 0.0.17 only adds watchOS and tvOS support. Both versions use Kotlin 1.7.10 too.
Could you create a reproducer or more logs? Because I can't reproduce it with this sample:
untitled.zip

Sorry, I don't have a committed version of this to git. We decided not to use the library and I just wrote a simple expect/actual function that provides us with a random NSUUID or a Java UUID in the respective platforms.

Okay.
Yeah using expect/actual is a good alternative too.


Basic structure changes to improve the layout

@AwesomeKesler did you get a chance to commit your changes? It looks like @amandamarg just pushed a bunch. Hopefully, you don't have too many merge conflicts 🙈

@amandamarg - I'm not sure if tagging you in a commit description actually makes it to you as expected. FYI, I pushed some structure updates after yours last week, when you get a chance please review the newest version and make sure I didn't break anything of yours. I am so sorry if I did!

Side by side


Issue with settings factory

This error:
 Cannot autowire service "MonsieurBiz\SyliusSettingsPlugin\Factory\SettingFactory": argument "$class
  Name" of method "__construct()" is type-hinted "string", you should configure its value explicitly.

? :smile:


#2625 Create sequence screen and load all triggers

Create sequence screen and load/display all triggers.
Since all triggers are actually "root" events, as shown in the service screen, the root events are polled regularly and distributed to the entities for the sequence and the service screen.
The project-board component will be reduced in to smaller components and is part of #1989
The detail view in the Sequence-Tab is part of #2627 and the tiles will show more details which is part of #2628

Looks good, I'll give the final approval once the linter issue is fixed.

Looks good, I'll give the final approval once the linter issue is fixed.


TextEncryptorLocator not configured - "No key was installed for encryption service"

I'm using the latest milestone release of Spring Cloud 2020.0.0 (M6) and I get the "No key was installed for encryption service" error even though I have the encrypt.key property set in bootstrap.properties.  When I change the version back to Hoxton.SR9, it works.
There isn't much in the way of configuration or extra code, outside of port settings and config location.  I've tried multiple milestone releases on 2020.0.0 and they all seem to have this problem, but not the previous release.
Environment:
JDK 15
SpringBoot 2.4.0
SpringCloud 2020.0.0-M6
I did a bit of digging during startup and it appears as though the TextEncryptorLocator does not get loaded because of an unresolved condition @ConditionalOnBean(TextEncryptor).  The startup logs seem to indicate the same thing:

SingleTextEncryptorConfiguration:
Did not match:
- @ConditionalOnBean (types: org.springframework.security.crypto.encrypt.TextEncryptor; SearchStrategy: all) did not find any beans of type org.springframework.security.crypto.encrypt.TextEncryptor (OnBeanCondition)

DefaultTextEncryptorConfiguration matched:
- @ConditionalOnMissingBean (types: org.springframework.security.crypto.encrypt.TextEncryptor; SearchStrategy: all) did not find any beans (OnBeanCondition)

In Hoxton, I see:

SingleTextEncryptorConfiguration matched:
- @ConditionalOnBean (types: org.springframework.security.crypto.encrypt.TextEncryptor; SearchStrategy: all) found bean 'defaultTextEncryptor'; @ConditionalOnMissingBean (types: org.springframework.cloud.config.server.encryption.TextEncryptorLocator; SearchStrategy: all) did not find any beans (OnBeanCondition)

and

DefaultTextEncryptorConfiguration:
Did not match:
- @ConditionalOnMissingBean (types: org.springframework.security.crypto.encrypt.TextEncryptor; SearchStrategy: all) found beans of type 'org.springframework.security.crypto.encrypt.TextEncryptor' defaultTextEncryptor (OnBeanCondition)

I didn't notice any differences in the auto-config logic, so I'm not sure why the behavior has changed.

Is this still an issue in 2020.0.1?

Verified this has been fixed in 2020.0.1


Fix flow types for firestore

The flow type declarations for the firestore module import QuerySnapshot but then try to use it as firestore.QuerySnapshot.

Good spot, thanks for this.
I'm planning a release in the next couple of days with a few new hooks so this will be included.

This has been released as part of https://github.com/CSFrequency/react-firebase-hooks/releases/tag/v1.2.0.  Thanks again for the contribution.


Properties under BotFrameworkAdapter.ConversationReference (and others) are settable

Are all of these properties supposed to be settable? It seems like they (at least many of them) should be read-only.

In most cases you can both send and receive instances of types like Activity and ConversationReference. Given that just about all of the properties have to be settable otherwise we'd need a totally different schema for outgoing types versus incoming types.

We have two primary scenarios:

Request / Response pattern (aka: the common pattern), where the bot just responds to incoming messages. It's not 1:1, but the bot gets a message, then sends some number of outbound messages in response.

The Proactive case where somethign happens (timer / event / whatever) and the Bot decides it needs to send a message.

In both cases we could:

Add a ctor to the ConversationReference that took an Activity. From there it could extract the relevant properties and populate itself. This would cover the Request / Response pattern and would allow the properties to be read-only.

Add a ctor that has the relevant properies and just accepts them as arguments. This would cover the Proactive scenario and let us make the properties read-only.

I'm not really sure it matters, especially as the Conversation Reference is auto-generated from the Swagger file. Leaving it as just a pure POCO seems the best choice.


FluxComponent

Implement a convenience component for ReactJS that lets you use a component instead of mixins to hook up stores, joins and actions. Much like FluxComponent from Flummox.
Simplest possible is a component that looks like this in jsx code:
var App = React.createClass({
  return (<MainLayout>
    <Reflux.Component connect={
      "my": MyStore,
      "another": AnotherStore
    }>
      { /* All props.children will be connected using Reflux.Component's props.connect object */ }
      <Toast />
      <Whatever />
    </Reflux.Component>
  </MainLayout>);
});

and what you think something like that:
// it will pass my and another as properties (just remove store from end)
<Component myStore anotherStore>...</Component>

// it will pass my1 and another1 as properties
<Component myStore='my1' anotherStore='my2'>...</Component>

// it will pass my and another as properties and use function data filter
<Component myStore={myFilter1} anotherStore={myFilter2}>...</Component>

// when need to config property name and filter
<Component myStore={{name: 'model1', filter: myFilter}} anotherStore={{name: 'model2', filter: myFilter2}}>...</Component>

A question, what happens when you have something like that:
<NeedMyStore><NeedAnotherStore /></NeedMyStore>

// will you end up with something like that??
<Component myStore>
  <NeedMyStore>
    <Component anotherStore><NeedAnotherStore /></Component>
  </NeedMyStore>
</Component>

@maxguzenski I believe components should do store registration by themselves. So if a nested component needs a store that the parent doesn't need to know about, they should do it instead of the parent.
In other words NeedMyStore will do the following render:
<Reflux.Component connect={"myStore": MyStore}>
  <AnotherStore />
</Reflux.Component>

... and AnotherStore will do the following render:
<Reflux.Component connect={"anotherStore": AnotherStore}>
....

You are right about parent component...
I think this component can be a nice feature of reflux (and for any flux framework). But I just no sure if I agree with Flummox arguments about this component.
1º - Re-render just what needed
But this all what React is about, isn't? Just let re-render. With immutable data time difference between re-render all page and just a small scope will be very small, no?
2º - Make react component truly reusable
I dont know about other projects, by in my case, top root elements (thats one connect with store) not "born" to be reusables (they are a role page, or page specific)

I think this is an optional convenience... like most other things Reflux has.

@spoike so I started writing an implementation of this as specified by you but got stuck because there doesn't seem to currently be a dom-based testing environment setup for this repo. Yet I can see phantomjs mentioned somwhere in the karma config file.
Can you shed some light on this? Do you have plans to integrate jest or anything that helps test react components? I'd really like to help but think it would really make sense to test with actual react components in this case.

@juliankrispel At the moment only unit tests on reflux functionality is available (w. mocha and karma), but no actual integration tests with dom-based environment.
I recently got the karma tests running on sauce labs and am under way to integrate reflux-core into reflux/refluxjs. Once that's done I should be able to add a dom-based testing environment with jest if time persists. I would like some help on these tests though, so pull requests are greatly appreciated.

@spoike
After using reflux in some projects,
feel a little painful for testing the Components which are subscribed to stores or call actions inside.
Stores have will keep state, we have to mock lots of things.
So learning from redux, I made reflux-connect to solve the pain point.
import React from 'react';
import refluxConnect from 'reflux-connect';

import storeA from '../stores/storeA';
import storeB from '../stores/storeB';
import commonActions from '../actions/commonActions';

const componentConnect = refluxConnect({
  storeA: storeA,
  storeB: storeB
})((state) => {
  // connectFilter can did here
  return {
    storeA: state.storeA,
    storeB: state.storeB
  }
}, {
  fetchData: commonActions.fetchData
});

class Component extends React.Component {
  static propTypes = {
    storeA: React.PropTypes.object
    storeB: React.PropTypes.object
    fetchData: React.PropTypes.func.isRequired
  }

  render() {
    return null;
  }
}

export default componentConnect(Component)

Then in our testing, we can test Component with pure props, by import { WrappedComponent as Component } from '../Component'.
However, we only support Reflux.connect to createStore.
It is similar like this issue mentioned, but use function to create.
How do you think ?
Thanks.

:+1: Thanks for your insight @morlay
I'll have to refer to this in the documentation among other HOC/ES6 plugins that have popped up lately on npm, which I'm very happy for, since I'd like to keep reflux and reflux-core small. See e.g. reflux/reflux-core#5, #420 and #225 for other examples.

Not solved in the ways outlined here, but the general concept of ES6 style component implementation instead of mixins is now solved.


Error: pod: Command failed with exit code 31

cordova platform add ios fails with the error below. Is that something you've seen before and know of a workaround for?
I'm running OS X El Capitan with ruby 2.5.1p57, gem 2.7.6, and cocoapods 1.5.3.
Thanks!

Installing "cordova-plugin-firebase-messaging" for ios
Failed to install 'cordova-plugin-firebase-messaging': Error: pod: Command failed with exit code 31
    at ChildProcess.whenDone (/Users/buu700/cyph/cyph-phonegap-build/platforms/ios/cordova/node_modules/cordova-common/src/superspawn.js:169:23)
    at ChildProcess.emit (events.js:180:13)
    at maybeClose (internal/child_process.js:936:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
(node:50695) UnhandledPromiseRejectionWarning: Error: pod: Command failed with exit code 31
    at ChildProcess.whenDone (/Users/buu700/cyph/cyph-phonegap-build/platforms/ios/cordova/node_modules/cordova-common/src/superspawn.js:169:23)
    at ChildProcess.emit (events.js:180:13)
    at maybeClose (internal/child_process.js:936:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
(node:50695) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:50695) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Not sure what the problem was or what exactly fixed it, but I'm not seeing this error anymore after a brew update ; brew upgrade; pod repo update.

Not sure what the problem was or what exactly fixed it, but I'm not seeing this error anymore after a brew update ; brew upgrade; pod repo update.

Thanks for your answer @buu700. The only thing I had to add was to update cocoapods.
brew update; brew upgrade; sudo gem install cocoapods; pod repo update;

pod repo update alone fixed the Error: pod: Command failed with exit code 31 error I seen with another package. Updating cocoapods it self via brew update; brew upgrade; sudo gem install cocoapods; is probably not necessary.


[SD CHANGE] <IP_ADDRESS>.3 test 2 formatting

What is the change request for the SD? Please describe.
Test 2 is improperly lined up with the left margin instead of the normal indent
Describe the solution you'd like
correct the formatting

Resolved with asciidoc migration.


STM32U5 improvements

Improves support for the STM32U5 device family.
Changes made:

Strip peripheral prefixes from register names
ADC, DMA2D, EXTI, FMC, GPIO, I2C, OCTOSPI, PWR, RCC and UCPD peripheral support

I think this is more or less ready for review now. Of course there are still many peripherals missing, but I think this a good amount for now.
A few points:

The UCPD peripheral exists in some other STM32 devices, but I thought it would probably be better to keep the scope of this PR to just the STM32U5 family. Let me know if you'd prefer me adding them to those other devices as well.
I made separate commits for each peripheral (apart from those where I just had to add the existing definitions). Would you prefer me squashing it all into one commit?
For fields which can take any arbitrary value (e.g. OSR in ADC_CFGR2), I always explicitly wrote out the range in the yaml - is that what I should have done or is it unnecessary to do that?

Please, split it on several PRs. It is too big.

OK, will do. If that's alright with you, I'll put the smaller changes (DMA2D + GPIO + I2C + FMC + EXTI) all in one PR (~200 additions) and the remaining ones (RCC, UCPD, OCTOSPI, PWR and ADC) in separate ones. Or would you prefer one PR for every peripheral?

Let's try. If it is not enough I'll say.

First part is in #982, will wait with opening PRs for the remaining peripherals.


[Feature request] Deploy pacti on conda-forge

Desired feature
Add a conda recipe and open a feedstock to deploy pacti as a conda package on conda-forge.
Reference
https://github.com/conda-forge

@elac-safran, many thanks for the suggestion!
Could you please say a little more about the benefits of doing this to conda users?
Currently, we have one package export to PyPi. Can conda users install Pacti using pip pacti? If so, how would it benefit users if Pacti were also available as a conda recipe?


added auto assign reviewers workflow

Added workflows we have in other repos to auto assign reviewers PRs.

Sorry wrong place...


Near future directions, follow-up

We have made good progress on our current directions, with the introduction of automated shape inference. Here's a recap to help synchronize our community efforts.
What should be our priority right now:

abstracting Theano functionality into a modular Keras back-end.

What should be our number 2 priorities:

Stricter checks of assumptions throughout the codebase.
Proper docstrings everywhere as per @matsuyamax's remarks.
As a follow-up, autogenerated docs (all classes / functions specifications).
Simpler, faster unit tests.
Faster compilation of complex graphs via tensor caching (see https://github.com/fchollet/keras/issues/666).

What we need to work on, but isn't as urgent:

New, simpler API for the Graph model (still TBD).
Recurrent Container (@EderSantana, you seemed to be pretty close to this).
Stateful RNNs.
Ability to reinitialize weights without recompiling.
Simpler way of handling loss weighting and masking (I though @EderSantana's objective function decorator was a great idea).
A proper parameter naming system (might be introduced as part of the backend).
Caffe model importing (@pranv).

Recurrent Container (@EderSantana, you seemed to be pretty close to this).

It seems to work, as long as you are willing to do everything inside the scan loop. I tried that common GRU optimization of precomputing input outside the loop, but there is no way to pass multiple named inputs to containers yet. Also, the new shape inference API may require me to change the logic a bit. So, progress here depends a lot on these other two choices. But be assured this is the feature I want the most and I'll work on it as soon as I see these other two parts mature enough.

Stateful RNNs.

I have a working example of this: https://github.com/fchollet/keras/issues/763
I've also a way to of training the initial states, for cases when we don't need to go stateful. I believe that trainable initial states should be the new default. All that is needed here is to define how to change the recurrent layers. I believe we don't want a separate class for each stateful version.

Simpler way of handling loss weighting and masking (I though @EderSantana's objective function decorator was a great idea).

Ok, so while I wait for the API choices mentioned above, I'll work on this since it seems to be independent.

abstracting Theano functionality into a modular Keras back-end.

Just to get things started, how a Dense layer would look like without direct Theano reference? Is anybody already working on this?

@endersantana, you'd improt tensor or dot from something like keras.backends.

New, simpler API for the Graph model (still TBD)

@fchollet Are you sure you want to get rid of Graph's add_input method? What about changing it to add_inputs which woudl take a dict of name:ndim pairs? I use it in my code and IMO it's quite convenient.

@pranv That is what I imagined. Don't you think such a thing, if done well, would have uses that could benefit more projects than just Keras? Keep that in mind for the possibility of making backends an independent project.

@EderSantana I definitely agree with the idea of having backends be a separate project. I think there is a whole slew of new backend options, abstracting that into separate package would make the whole autodiff+symbolic math + GPU space a bit more manageable for new projects.

@fchollet Are you sure you want to get rid of Graph's add_input method? What about changing it to add_inputs which woudl take a dict of name:ndim pairs? I use it in my code and IMO it's quite convenient.

No, I am not sure at all, add_input obviously has value that isn't readily replaceable. I think being to add all inputs at once is a good suggestion. But there are actually 2 parameters we need to specify for all inputs: input_shape and dtype. So an inputs dict would end up being a complicated interface (mapping names to dictionaries?)

@pranv That is what I imagined. Don't you think such a thing, if done well, would have uses that could benefit more projects than just Keras? Keep that in mind for the possibility of making backends an independent project.

Yes, basically I would expect to import the backend via: from keras import backend as K which would import a different set of files based on the type of backend you configured in your Keras config file (another feature we need to add). Then you would call K.dot(), K.function(), etc.
I agree that such a project could potentially become a lingua franca of Python tensor manipulation (write your projects in K, run them on any tensor framework), specifically useful for projects like Keras that don't want to be dependent on any single framework / platform [*]. However that is beyond our scope for now. Let's just implement it internally for now (with generality in mind), and if there's interest in splitting it up later we can do that. In time.
[*] About "platforms": in the future, fast hardware clouds like Nervana Systems' ASIC cloud will be available to the public (Amazon will most likely have a Deep Learning AWS service, etc). Think 100x faster than today's high-end Nvidia GPUs. But they will require using custom tensor frameworks (e.g. Neon) due to the tight coupling between low-level code and hardware. If you want to run on any platform you will need to write generic code (in K) that will compile to a given target framework (Neon).

Ok, so while I wait for the API choices mentioned above, I'll work on this since it seems to be independent.

Awesome, let me know if you need any help. The shape inference stuff is already in master, and the Graph API changes will hopefully be settled soon.

Can I just say caffe integration would be amazing


Review background polling title when an analysis and an import are present in the element

What does "review" mean?

Fix? :D. Connecting analyzing dataset... doesn't sound so good.

Haha, sorry, I read to fast and missed the key word "table" :shame:

:dancer:


Explicit attribute accessor methods on settings objects

Right now with settings objects, we can do stuff like
default_val = setting.get_attr("default")
allowed = str_setting.get_attr("allowed-values")
We also want:
default_val = setting.default_value( )
allowed = str_setting.allowed_values( )
Only the supported methods get created. So, default_value only
exists on properties; allowed_values only exists on strings and string lists,
and so on.

Specific requirements

all nodes (i.e. available in class Base just as is_active is now:

read_only (fluent name "read-only?")

all properties and arguments (i.e. all classes such as Integer, ..., RealVector, ..., so inheritance might be the best solution, possibly via mixin)

default_value (fluent name "default")

all strings and string lists (again using inheritance)

allowed_values ("allowed-values")

all numerical values (again using inheritance)

min ("min")

max ("max")

Sean:

https://github.com/pyansys/pyfluent/pull/701


charts: upgrade d3 to version 4

v4 is a new major version that has a more modular structure and some additional features that might be useful.
Also some linting.

Current coverage is 56.05% (diff: 100%)

Merging #353 into master will not change coverage

@@             master       #353   diff @@
==========================================
  Files            12         12
  Lines          1008       1008
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            565        565
  Misses          443        443
  Partials          0          0

Powered by Codecov. Last update 20cb7d8...0dd949e


No Internet connection when in STATIONAP mode

I'm struggling with sta+ap mode and SNTP. When I upload sketch with ap+sta mode I can't connect to remote NTP server. DNS of server gets resolved (LAN connectivity works fine), but after DNS resolving station calls udp_sendto with with result ERR_RTE (so no route to host). When I upload the same FW but with STATION mode I can connect to NTP server without any problem. Is it bug or feature? I mean, is just Internet connection from station forbidden when AP is working simultaneously?

With lwip v2 https://github.com/SuperHouse/esp-open-rtos/pull/389 it is now possible to bind a pcb to an interface and doing so might be a solution, so adding the following to sntp_init gets this working in sta+ap mode:
    udp_bind_netif(sntp_pcb, sdk_system_get_netif(0));