Support TCP socket HealthCheck

Similar to HTTP Path HealthCheck, add support for TCP socket HealthCheck.
This is useful for use in Providers like Marathon or Docker, where a particular health check via HTTP might be hard to configure or determine.

+1

Additionally, this would be very useful for us given that we would really like to use AWS' new Network Load Balancer instead of a classic load balancer. By default, the NLB wants to use a TCP health check.

Any update on this issue? It would be really nice to have and it's critical to us from a reliability point of view before going into production. Thanks!

Any possible workaround for the healthcheck? Stuck trying to get AWS NLB talk to traefik. ELB works fine, but really would like to switch....

You can use the http health checks on an NLB if you are configuring the NLB manually. Just be sure you have enabled the /ping endpoint on Traefik in the configuration. Then configure the NLB to hit the /ping endpoint over http.
    [ping]
      entrypoint = "http"

If you're on Kubernetes you'd have to do something like the following: https://github.com/ImagineLearning/node-nlb-sync.

I would love to see this too.

How has this not been implemented yet? Shouldn't this be a simple ping command to whatever port is configured to be health checked with TCP? We need this.


Automated cherry pick of #5483: Do not delete IPv6 link-local route in reconciler

Cherry pick of #5483 on release-1.13.
#5483: Do not delete IPv6 link-local route in reconciler
For details on the cherry pick process, see the cherry pick requests page.

/skip-all


[ENG-2472] Updating CODEOWNERS

Description

Setting backend team as code owners

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


WOCCatalog [ARM]: Accelerate 1 takes several seconds to refresh.

Phone: Lumia 640 device (14393 build)
Master commit: https://github.com/Microsoft/WinObjC/commit/2e0afafbf36d23b1cee7bd09f1dc8cf230c5c8a1
Build/run WoCCatalog in Debug or Release.
Go to Accelerate 1.
Move the value of RGB, etc to a different value.
Expected: the color values update on the mountain.
Actual: the color values update after about 3-5 seconds.
Is this expected behavior?

Its usually not a good idea to measure perf on debug build.  Does this repro on retail?

It does indeed. I'll update the name of the issue to reflect it.

@andrejo-msft I compared to last release of this.  When you change the slider, the entire image has to be processed.  on ARM, we don't use any ARM optimization to speed this up (of x86, we have the optimized code).  So this is performing as expected and is not a regression.  I'll close this issue as such.


Peer-to-peer code review

Status: Required Changes :recycle:
Hi @AbayomiOlaoye
Good job so far!
There are some issues that you still need to work on to prepare your project for the final evaluation but you are almost there!
Top Highlight

No linter errors. :heavy_check_mark:
Adherence to GitHub Flow. :heavy_check_mark:
Great UI for the project. :heavy_check_mark:
Meaningful commit messages. :heavy_check_mark:

Suggested changes
Check the comments under the review.
You can use as many of my suggestions as you want. If there is anything you would like to skip - feel free to do that. However, I strongly recommend you to take them into account as they can make your code better._
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.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

[ ] Great job for pushing it this far. You've done pretty well on this project and I must commend you for that. :tada: . However, there are few things you need to work on before your project could be due for approval.
[ ] I think base on the requirement the  Live Presentation Video Link in the readme file is supposed to be in the PR write up.

Alright, thanks.


Able to create a AddHistCommand that takes in multiple variables and is shown on PersonCard

Issue has been resolved when pull request has been merged a few days ago.


submitting ruby quiz

Score: 4/5
Great job. The only errors you made were adding the ?'s leaving out the end statements in your if...else statements. The syntax goes as follows:
if foo
   bar
else
   baz
end


Added code to Print the common Sub Sequence.

Hi Tushar,
I have added small piece of code to print common sub sequence.
Thanks
Randheer

I dont think thats correct logic to print lcs. I think you should maintain the i at which max was found. And then just move from i to i - max in str1 and that should give you lcs.

HI Tushar,
Thanks for your response.
After watching your video on youtube, I came up with this observation. that this approach also works well. I have tested it. and it is working fine.
i will try with logic suggested by you .
Thanks A lot .


certificatesigningrequests/v1beta1 to v1

Issue #, if available:
Description of changes:
Kube 1.22 drops support for certificatesigningrequests/v1beta1. Update vendor/k8s.io/client-go and migrate to certificatesigningrequests/v1.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jqmichael would you be able to (find some one to) review this? Thanks!

is there any updates on this?

@micahhausler @nckturner ?

@jyotimahapatra @wongma7 ?

Kubernetes v1.23 is out now, so this project is now 2 minors behind the latest Kubernetes release.
The fact that the system:node: prefix is required means that something is being done incorrectly I believe.. the CSR API is intended for grabbing certificates that the whole cluster trusts, but webhooks don't need that level of certificate. They just need to have their caBundle put into the MutatingWebhookConfiguration resource. It's still good IMO to get csr/v1 merged to work on newer Kubernetes but there will be future work to be a better Kubernetes citizen and not need kubectl certificate approve just to register a webhook.

but webhooks don't need that level of certificate. They just need to have their caBundle put into the MutatingWebhookConfiguration resource.

I agree. I think it's good to support cert-manager based deployments in the future. Refs: https://github.com/aws/amazon-eks-pod-identity-webhook/issues/94

With this patch the CSRs for the pod-identity-webhook are now created (where as before they failed to be created at all).
However when you go to approve them they end up in an Approved,Failed state:

I have the same issue, and it is solved by that change. The system:node prefix is required as long as we continue to use the kubernetes.io/kubelet-serving  as a signer.
So could you please add that change in this PR, @joelddiaz ? Or shall I do it with a new PR?

Yes it seems like requesting kubelet-serving with system:node prefix is the path of least resistance for maintaining roughly the same functionality/behavior in 1.22 as if legacy-unknown were allowed. So I am inclined to merge this with the system:node prefix change. I understand the sentiment about it being "wrong", it does feel a bit to me like abuse of the API since obviously the webhook is not a kubelet. But it seems also like other solutions require third party software and/or more significant changes.
It might be "wrong" for the webhook to be getting its own serving cert in the first place...it is mimicking what kubelet does. From what I have seen, it is more common a pattern to have the cert generation be the responsibility of the deployer as a prerequisite to webhook deployment. So for example, another aws maintained webhook https://github.com/kubernetes-sigs/aws-iam-authenticator has an optional step where certs are generated before deployment. As mentioned in https://github.com/aws/amazon-eks-pod-identity-webhook/issues/94 if the webhook could just read the cert from file and reload then it could be ignorant of how certs are generated, by cert-manager, manually or whatever.
Another complication is that AWS EKS does NOT run the kubernetes default signer. So having the webhook create a kublet-serving cert might not work on EKS. But EKS 1.22 is not released yet so that's not really a problem yet

But EKS 1.22 is not released yet so that's not really a problem yet

Oh, sure...

:joy: don't worry, it's on AWS's radar to fix the problem before release.
If you have time to submit a PR with the change if @joelddiaz is not available (to be fair, we took very long to review this PR!) I can approve it. Thanks

Actually I have time to submit a PR now, will link to it in a minute and appreciate reviews. thx.

https://github.com/aws/amazon-eks-pod-identity-webhook/pull/133

#133 is up for review , (sorry for noise, I sent previous comment with just hte link )
and btw when I said 'not a problem' yet I meant for EKS users specifically. Obviously this repository has a wider audience and I'll try to prioritize the cert-manager fix even if EKS doesn't necessarily officially support that as an add-on or whatever.

Solution I'm thinking of is (cross-posting from https://github.com/aws/amazon-eks-pod-identity-webhook/pull/133#issuecomment-1017907120 for awareness, apologies again for all the noise):

if --in-cluster=true then you must provide signerName (and common name and org, as new arguments). So for non-EKS users they can set these to kubelet-serving and system:node accordingly. And for other distros that have their custom signer they might support other signerNames and such.
if --in-cluster=false then #134 should fix the bug where cert never gets reloaded if it's renewed so that fixes the cert-manager use-case

Looks like AWS released EKS 1.22 3 days ago, but noticed this did not make it. Is a different work around for getting this deployed with 1.22? Not sure if you would know @wongma7

Any update on this? The solution below seems pretty reasonable to me

Solution I'm thinking of is (cross-posting from #133 (comment) for awareness, apologies again for all the noise):
* if --in-cluster=true then you must provide signerName (and common name and org, as new arguments). So for non-EKS users they can set these to kubelet-serving and system:node accordingly. And for other distros that have their custom signer they might support other signerNames and such.

* if --in-cluster=false then [Use certwatcher to support mounting cert-manager certificates. #134](https://github.com/aws/amazon-eks-pod-identity-webhook/pull/134) should fix the bug where cert never gets reloaded if it's renewed so that fixes the cert-manager use-case

Any update on this? The solution below seems pretty reasonable to me

I believe that everything's in place for this. The deployment YAML in https://github.com/prasita123/amazon-eks-pod-identity-webhook/tree/master/deploy has been updated to use cert-manager with --in-cluster=false and I've been running this configuration in production for two years.


Update goreleaser

What did you implement:
Easy way to push updated binaries to S3 for distribution.
How did you implement it:
Updated the .goreleaser.yaml config file and added an upload.sh script.
Goreleaser will build the various binaries, then the post-hook will upload them to S3. It will upload them in two places: /<COMMIT-HASH>/<build>/event-gateway plus /master/<build>/event-gateway.
We can run this after merges to master. Then users can download the latest binary at https://s3.amazonaws.com/eg-binaries/master/${BUILD}/event-gateway.
Is this ready for review?: YES
Is it a breaking change?: YES

Closing this for now as it's not needed.


prepare release

add instructions on how to release the code

@kiuby88 could you please review just to see if the instructions are clear enough?

As an alternative to sed, we can use http://www.mojohaus.org/versions-maven-plugin/
mvn versions:set -DnewVersion=0.1.0-M19 && mvn versions:commit

@rosogon thanks for your suggestion


Geo Aggregation Integration Tests

In gitlab by @sylvaingaudan on Apr 26, 2017, 12:14

In gitlab by @sylvaingaudan on Apr 26, 2017, 12:24
added ~1918367 label

In gitlab by @sfalquier on Apr 27, 2017, 09:59
added ~1918368 and removed ~1918367 labels

In gitlab by @sfalquier on Apr 27, 2017, 10:00
added ~1918367 and removed ~1918368 labels

In gitlab by @sfalquier on Apr 27, 2017, 10:00
assigned to @sfalquier

In gitlab by @sfalquier on Apr 27, 2017, 10:01
added ~1918368 and removed ~1918367 labels

In gitlab by @sylvaingaudan on Apr 28, 2017, 13:32
changed milestone to %3

In gitlab by @sfalquier on May 3, 2017, 17:37
removed ~1918368 label

In gitlab by @sfalquier on May 3, 2017, 17:37
closed


make prompt indicators configurable

This is supposed to allow prompt indicators to be configurable.
You should be able to set these env vars in your config.nu and e-q applies them.
let-env PROMPT_INDICATOR = "A "
let-env PROMPT_INDICATOR_VI_INSERT = "I "
let-env PROMPT_INDICATOR_VI_VISUAL = "V "
let-env PROMPT_MULTILINE_INDICATOR = "- "

nice!

nice!


Enhancing tests for unescaping strings

These tests enhance the coverage of CUnescapeInternal method from absl/strings/escaping.cc.
I want to start contributing, so this first pull request serves more as experience.
I took the CUnescapeInternal method and systematically inserted small bugs to check the test coverage. From that experience, I found a few modifications that went undetected and added tests specifically for them.
I'm not sure how valuable this is since this function looks very stable. But I believe the PR would still be a good addition to the test suite in case this is changed for optimizations in the future.
See below a set of changes that would go undetected (if done individually).
--- a/absl/strings/escaping.cc
+++ b/absl/strings/escaping.cc
@@ -95,6 +95,7 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
   const char* p = source.data();
   const char* end = source.end();
   const char* last_byte = end - 1;
+//const char* last_byte = end - 0;

   // Small optimization for case where source = dest and there's no escaping
   while (p == d && p < end && *p != '\\') p++, d++;
@@ -131,9 +132,11 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
           const char* octal_start = p;
           unsigned int ch = *p - '0';
           if (p < last_byte && is_octal_digit(p[1])) ch = ch * 8 + *++p - '0';
+//        if (p <= last_byte && is_octal_digit(p[2])) ch = ch * 8 + *++p - '0';
           if (p < last_byte && is_octal_digit(p[1]))
+//        if (p <= last_byte && is_octal_digit(p[1]))
             ch = ch * 8 + *++p - '0';      // now points at last digit
           if (ch > 0xff) {
+//        if (ch >= 0xff) {
             if (error) {
               *error = "Value of \\" +
                        std::string(octal_start, p + 1 - octal_start) +
@@ -155,11 +158,14 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
         case 'x':
         case 'X': {
           if (p >= last_byte) {
+//        if (p > last_byte) {
             if (error) *error = "String cannot end with \\x";
             return false;
+//        /*return false;*/
           } else if (!absl::ascii_isxdigit(p[1])) {
             if (error) *error = "\\x cannot be followed by a non-hex digit";
             return false;
+//        /*return false;*/
           }
           unsigned int ch = 0;
           const char* hex_start = p;
@@ -194,6 +200,7 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
                        std::string(hex_start, p + 1 - hex_start);
             }
             return false;
+//        /*return false;*/
           }
           for (int i = 0; i < 4; ++i) {
             // Look one char ahead.
@@ -205,6 +212,7 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
                          std::string(hex_start, p + 1 - hex_start);
               }
               return false;
+//          /*return false;*/
             }
           }
           if ((rune == 0) && leave_nulls_escaped) {
@@ -227,6 +235,7 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
                        std::string(hex_start, p + 1 - hex_start);
             }
             return false;
+//        /*return false;*/
           }
           for (int i = 0; i < 8; ++i) {
             // Look one char ahead.
@@ -235,12 +244,14 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
               // is within the Unicode limit, but do advance p.
               uint32_t newrune = (rune << 4) + hex_digit_to_int(*++p);
               if (newrune > 0x10FFFF) {
+//            if (newrune >= 0x10FFFF) {
                 if (error) {
                   *error = "Value of \\" +
                            std::string(hex_start, p + 1 - hex_start) +
                            " exceeds Unicode limit (0x10FFFF)";
                 }
                 return false;
+//            /*return false;*/
               } else {
                 rune = newrune;
               }
@@ -250,6 +261,7 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
                          std::string(hex_start, p + 1 - hex_start);
               }
               return false;
+//          /*return false;*/
             }
           }
           if ((rune == 0) && leave_nulls_escaped) {
@@ -265,6 +277,7 @@ bool CUnescapeInternal(absl::string_view source, bool leave_nulls_escaped,
         default: {
           if (error) *error = std::string("Unknown escape sequence: \\") + *p;
           return false;
+//      /*return false;*/
         }
       }
       p++;                                 // read past letter we escaped

Thanks for the pull request and glad to hear you want to start contributing!  This is definitely a stable interface, but adding tests is still a good thing.
The tests all seem reasonable, so I think I'm just going to have some comments about naming and organization.

Sorry for the delay here. I'll need another week or so. It's software release week back at the office. :)

No worries, take your time :)


3body

Additions to the votca package in order to parametrize 3-body interactions of the SW type with csg_fmatch and calculate additional properties with csg_stat
Needs votca/tools#65

job is failing quite badly
https://api.travis-ci.org/v3/job/458693975/log.txt

You can just comment below.and do not have to edit my comment :) There was also a second error
https://api.travis-ci.org/v3/job/458693979/log.txt

Travis is failing as we need to merge votca/tools#65 first

I have now added regression tests for csg_stat for the 2-body potential of mean force, and the 3-body angular distribution, as well as, csg_fmatch for the 2-body + 3-body SW interaction based on the frame.dump file in src/tools/references/spce

@schererc merge https://github.com/votca/votca/pull/94 then this should build.

32/56 Test #55: unit_test_nblist_3body .............***Failed    0.02 sec
unit_test_nblist_3body: /home/votca/votca/csg/include/votca/csg/moleculeitem.h:36: votca::csg::Molecule* votca::csg::MoleculeItem::getMolecule(): Assertion `_mol != nullptr' failed.
Running 2 test cases...
unknown location(0): fatal error: in "nblist_3body_test/test_nblist_3body_generate_list": signal: SIGABRT (application abort requested)
/home/votca/votca/csg/src/tests/test_nblist_3body.cc(41): last checkpoint: "test_nblist_3body_generate_list" test entry
*** 1 failure is detected in the test module "nblist_3body_test"
      Start 56: unit_test_nblistgrid_3body
33/56 Test #56: unit_test_nblistgrid_3body .........***Failed    0.02 sec

it seems the assertion in /home/votca/votca/csg/include/votca/csg/moleculeitem.h:36 is failing in the debug build.

@schererc you can do a debug build locally by add -DCMAKE_BUILD_TYPE=Debug to your cmake options.

I assume, I found and corrected now the problems in test_nblist_3body.cc and test_nblistgrid_3body.cc

Ping @JensWehner @JoshuaSBrown

Thanks, I will then merge the pull request now


Revert "Staging: Migration for V2"

Reverts OlympusDAO/olympus-frontend#881

closed in favor of https://github.com/OlympusDAO/olympus-frontend/pull/891


New Formula: Libggz

This is retry of the #532 and #534 .

Could you squash this into one commit?  Thanks!

@BrewTestBot test this please

Merged. Thank you for your contribution to Homebrew!


adding couple and decouple functions - SLIM-637 and SLIM-638

All is well.

All is well.

All is well.


Event handlers

What will our event API look like? Currently there's just bot.on(PacketType, handler).

[x] received packets
[ ] physics tick end
[ ] window opened / slot changed - after updating client state
[ ] player joined/left - after updating client state
[ ] respawned, health change, etc. - after updating client state
[ ] kicked/disconnected - also cancel any ongoing actions in physics/dig/etc.

Some events should be triggered only after the client state has updated, eg. player list or window state, so the state can be used by the handler. A simple packet handler may trigger too early.
Some events could also just be checked by the user script after each physics tick.

I think bot.once will be useful


test: allow running locally in isolated environment

Running ./scripts/test.sh would:

[ ] Install necessary plugins (e.g. nui.nvim, plenary.nvim) if not already installed
[ ] Run the tests in an environment isolated from regular vim setup (i.e. plugins should be used from ./.testcache directory)

Running ./scripts/test.sh --clean would:

[ ] Clean ./.testcache directory before running the test and resintall plugins

This is pretty nice. My only concern is that it does not support Windows and we do get contributions from Windows users. I'm not sure if they run the tests or not, or maybe just rely on the Action anyhow.
Are there any Windows users watching this that want to comment?

Maybe use something like Python?

or maybe use a docker container to run the tests? Is docker as ubiquitous as python yet?

or maybe use a docker container to run the tests? Is docker as ubiquitous as python yet?

Docker on windows runs in WSL, so you wouldn't actually be testing "on Windows", you'd be testing "on Linux"

Duh, that would not be all that helpful, now would it?
The script is simple enough that we could probably just add a ps1 or bat script that copies the functionality. I'm leaning towards that. @MunifTanjim could you add that or convert it to python? If you don't have an environment setup on Windows I can write it from memory and let the next windows contributor actually test it out. We can also add an "is windows" switch in the test setup that reverts to the old code on Windows.

My only concern is that it does not support Windows and we do get contributions from Windows users. I'm not sure if they run the tests or not, or maybe just rely on the Action anyhow.

If we want to support running it on powershell (or whatever the default is on windows), I think that is a separate piece of work? I'm not motivated/equipped to work on that. Maybe somebody using windows can add another small script for windows later?

Maybe use something like Python?

or maybe use a docker container to run the tests? Is docker as ubiquitous as python yet?

Those would just be increasing the complexity. The simpler solution would be to:

Provide another script that runs on windows (test.bat or something)
Or if the windows user has Git Bash installed, the test.sh should run normally
Or if WSL is used, the test.sh should run normally

could you add that or convert it to python?

I would like to avoid it very much, if I can 😂

We can also add an "is windows" switch in the test setup that reverts to the old code on Windows.

I'm not sure what you mean by "old code". The script just clones the plugins in a specific directory. If another script does the same thing on windows, shouldn't everything just work? 🤔

btw, I just wanted to run the tests locally without any hassle. That's the motivation behind this PR.
Adding python or docker in the mix would increase the hassle instead of decreasing it. Python or Docker has nothing to do with this project. And I don't think we should be forcing the contributors to have those installed just to run the tests locally. If we want to support Windows, there are simpler ways.
Also it was not supported to run the tests locally at all. So not supporting windows probably shouldn't be a blocker for now? 🤔

btw, I just wanted to run the tests locally without any hassle. That's the motivation behind this PR.

Adding python or docker in the mix would increase the hassle instead of decreasing it. Python or Docker has nothing to do with this project and I don't think we should be forcing the contributors to have those installed just to run the tests locally. If we want to support Windows, there are simpler ways (mentioned https://github.com/nvim-neo-tree/neo-tree.nvim/pull/413#issuecomment-1180629056).

I agree about python or docker. A bat or ps1 would probably be easiest if git bash doesn't work.

Also it was not supported to run the tests locally at all. So not supporting windows probably shouldn't be a blocker for now?

The test did run locally before. It used to be make test in the repo root. Maybe it didn't work for everyone, particularly if you didn't use packer. I just thought you added this because wanted to isolate the downloaded requirements from your installed plugins.


Relying party needs to pull verifier public key from environment

When the relying party pulls the EAR from the verifier, its first action is to verify the JWT against the verifier's public key. This public key is currently a hard-coded one that matches the mocked verifier. The key needs to be consumed from the environment instead, probably stored in a file and addressed using a command-line parameter into the ssl_server2 application.

Note that the EAR verification key can be also pulled from the Veraison discovery API.

Interesting. I was only aware of the endorsement and verification APIs. Are there some docs for the discovery API? Is it plumbed into any of the client libraries?

Fantastic, thanks. This being the case, I think that's a much better way to obtain the key. I could add this API to the mock and then look at plumbing it through the Rust and C API clients.

I could add this API to the mock and then look at plumbing it through the Rust and C API clients.

awesome!

@paulhowardarm I think, we have resolved this issue, isn't it?

@yogeshbdeshpande Its status is "Done" on the Scrum board, although that alone does not seem to close the issue. We should probably look at the whole set of issues in "Done" and decide whether we want to fully close them, or leave them open until the whole PoC project is closed.


Unable to monitor peripheral on android

I've created an android app to make it easy to emulate behavior of target ble device. I've configured it in following way:
        UUID CHAR_UUID = UUID.fromString(uuid);
        BluetoothGattCharacteristic tempChar = new BluetoothGattCharacteristic(
                CHAR_UUID,
                BluetoothGattCharacteristic.PROPERTY_NOTIFY |
                        BluetoothGattCharacteristic.PROPERTY_INDICATE |
                        BluetoothGattCharacteristic.PROPERTY_READ |
                        BluetoothGattCharacteristic.PROPERTY_WRITE_NO_RESPONSE |
                        BluetoothGattCharacteristic.PROPERTY_WRITE,
                BluetoothGattCharacteristic.PERMISSION_READ
        );
        BluetoothGattDescriptor gD = new BluetoothGattDescriptor(
                CHAR_UUID,
                BluetoothGattDescriptor.PERMISSION_READ
        );
        gD.setValue(BluetoothGattDescriptor.ENABLE_NOTIFICATION_VALUE);
        tempChar.addDescriptor(gD);
        this.servicesMap.get(serviceUUID).addCharacteristic(tempChar);

So I'm able to locate this device, locate services and characteristics. I'm also able to read from characteristic:

But if I try to monitor it, I get
Error: Characteristic $myCharId notify change failed for device ? and service $myServiceId

Android application invokes my mock function for mtu:
        @Override
        public void onMtuChanged(BluetoothDevice device, int mtu) {

        }

after that ios application (that I'm using as master, receive error in callback I've passed to monitor). I'm not sure if I need to handle somehow in onMtuChanged or in react-native-ble-plx configuration. Any advices are welcome.
Thanks.

You probably would like to ask Google about an example of how to implement Android BLE Server
From what I can quickly see you have setup permissions wrong. Either way this is not a problem with the library


Adds Website docs for cloudflare_static_route

My bad, I forgot the website docs for static routes in the other PR. Here they are :-D

👏


Nanoid default value

This just got merged: https://github.com/prisma/prisma-engines/pull/3556
We should document it in a similar way as we document cuid et.al. To here:
https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#cuid
ping @rintaun

Here is a list of all the places where we mention uuid() and cuid() in relevant ways:
https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#cuid
https://www.prisma.io/docs/concepts/components/introspection#introspection-with-an-existing-schema
https://www.prisma.io/docs/concepts/components/prisma-schema/data-model#using-functions
https://www.prisma.io/docs/concepts/components/prisma-client/database-polyfills
https://www.prisma.io/docs/concepts/components/prisma-schema/features-without-psl-equivalent#when-to-use-a-database-level-function
https://www.prisma.io/docs/concepts/components/prisma-migrate/supported-types-and-db-features
That should give you enough places to mention nanoid() @rintaun

@janpio thanks for looking all of those places up! I hope to be able to get to this tomorrow after work

Note: this is blocked by some work that still needs to happen but is currently not planned, see https://github.com/prisma/prisma/issues/17199

Hi @pimeys 👋,
Thank you for opening this issue! We're in the process of tidying up our documentation-related issues. Since this is still blocked by #17199, I’ll be closing it for now. Rest assured, we’ll have the info in the docs once #17199 is merged.
Appreciate your understanding! 🙏


bug: Syncer not working as expected

Describe the bug
i could see error in syncer pod logs
kubectl logs kcp-syncer-dp-8568db4-1a1jng80-6b6f958b48-7kcxn | grep E0
E0111 18:02:32.387938       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource
E0111 18:02:32.388423       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource
E0111 18:02:32.388707       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource
E0111 18:02:32.426879       1 controller.go:240] failed to sync "dp-8568db4": Operation cannot be fulfilled on synctargets.workload.kcp.io "dp-8568db4": the object has been modified; please apply your changes to the latest version and try again
E0111 18:02:33.374780       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource

versions:
my kcp version :  kcp version v1.24.3+kcp-v0.10.0-429-g8568db4b5eb633
syncer image used : ghcr.io/kcp-dev/kcp/syncer:8568db4
Steps To Reproduce
kcp version :  kcp version v1.24.3+kcp-v0.10.0-429-g8568db4b5eb633
syncer image used : ghcr.io/kcp-dev/kcp/syncer:8568db4
user this and try to add workload cluster
Expected Behaviour
the syncer should be able to work succesfully
Additional Context
No response

cc @davidfestal

these lines
E0111 18:02:32.387938       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource
E0111 18:02:32.388423       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource
E0111 18:02:32.388707       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource

are not very helpful and possibly not the cause of the error at all.
Could you provide more logs of the Syncer ?
Could you provide more information about what doesn't work ? And more details about the steps you use to create:

your synctarget
your workloads
?

@davidfestal  i hope this is the error
E0111 18:02:32.426879       1 controller.go:240] failed to sync "dp-8568db4": Operation cannot be fulfilled on synctargets.workload.kcp.io "dp-8568db4": the object has been modified; please apply your changes to the latest version and try again
i tried to run kubectl kcp workload sync  command and then applied he yaml generated on my kind cluster.
later when i tried to apply deployments it could not find the resource .. the deployments are not registered with kcp so went ahead and checked the syncer logs and i could see the above log.
let me know if i am doing it wrong

@davidfestal i hope this is the error
E0111 18:02:32.426879 1 controller.go:240] failed to sync "dp-8568db4": Operation cannot be fulfilled on synctargets.workload.kcp.io "dp-8568db4": the object has been modified; please apply your changes to the latest version and try again

I would be surprised it to be the root cause.

when i tried to apply deployments it could not find the resource

That would be more the cause of the problem I assume. Can you provide more details about the steps you used ?

nothing much ..
started kcp  (versioned mentioned above)
generated workload   kubectl kcp workload sync dp-8568db4 --syncer-image ghcr.io/kcp-dev/kcp/syncer:8568db4 -o syncer-8568db4-kind-main.yaml
yaml is generated applied that yaml and saw those error in logs

But does the Syncer POD crashes or not ?

kcp-syncer-dp-8568db4-1a1jng80-6b6f958b48-7kcxn   1/1     Running   0          25h

FYI
just restated the pod  the total logs
 kubectl logs kcp-syncer-dp-8568db4-1a1jng80-6b6f958b48-njmv2 I0112 19:06:03.955087       1 syncer.go:83] "syncing" resource-types=[] I0112 19:06:03.963238       1 syncer.go:85] "starting syncer" syncTarget.workspace="root" syncTarget.name="dp-8568db4" I0112 19:06:03.965074       1 syncer.go:113] "attempting to retrieve the Syncer virtual workspace URL" syncTarget.workspace="root" syncTarget.name="dp-8568db4" I0112 19:06:04.264370       1 syncer.go:261] "Creating spec syncer" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" I0112 19:06:04.265325       1 namespace_downstream_controller.go:166] "Set up downstream namespace informer" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-workload-syncer-namespace-downstream" I0112 19:06:04.268615       1 syncer.go:279] "Creating status syncer" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" I0112 19:06:04.269022       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=secrets" I0112 19:06:04.269398       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=secrets" I0112 19:06:04.269506       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=namespaces" I0112 19:06:04.269602       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=namespaces" I0112 19:06:04.281038       1 controller.go:196] "queueing SyncTarget" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:04.370459       1 status_controller.go:171] "Starting syncer workers" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-workload-syncer-status" I0112 19:06:04.370566       1 apiimporter.go:174] "Starting API Importer" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" I0112 19:06:04.370566       1 spec_controller.go:305] "Starting syncer workers" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-workload-syncer-spec" I0112 19:06:04.370808       1 shared_informer.go:255] Waiting for caches to sync for kcp-ddsif-gvr-source I0112 19:06:04.370814       1 shared_informer.go:255] Waiting for caches to sync for kcp-ddsif-gvr-source I0112 19:06:04.370857       1 shared_informer.go:262] Caches are synced for kcp-ddsif-gvr-source I0112 19:06:04.370873       1 shared_informer.go:262] Caches are synced for kcp-ddsif-gvr-source I0112 19:06:04.370873       1 apiimporter.go:227] "Importing APIs" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" resourcesToImport=[deployments.apps ingresses.networking.k8s.io services.] I0112 19:06:04.370928       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=configmaps" I0112 19:06:04.371042       1 shared_informer.go:255] Waiting for caches to sync for kcp-ddsif-gvr-source I0112 19:06:04.371131       1 shared_informer.go:262] Caches are synced for kcp-ddsif-gvr-source I0112 19:06:04.371184       1 controllermanager.go:117] "Starting controller manager" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="syncer-controller-manager-upstream-upsyncer" I0112 19:06:04.371254       1 controllermanager.go:117] "Starting controller manager" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="syncer-controller-manager-upstream-syncer" I0112 19:06:04.371448       1 controllermanager.go:117] "Starting controller manager" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="syncer-controller-manager-downstream-syncer" I0112 19:06:04.371507       1 controller.go:208] "Starting controller" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" I0112 19:06:04.371523       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=configmaps" I0112 19:06:04.371131       1 namespace_downstream_controller.go:204] "Starting controller" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-workload-syncer-namespace-downstream" I0112 19:06:04.371724       1 controller.go:233] "processing key" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:04.382603       1 controller.go:196] "queueing SyncTarget" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:04.409541       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=services" I0112 19:06:04.409605       1 informer.go:314] "adding dynamic informer for gvr" gvr="/v1, Resource=services" I0112 19:06:04.409654       1 informer.go:314] "adding dynamic informer for gvr" gvr="networking.k8s.io/v1, Resource=ingresses" I0112 19:06:04.409714       1 informer.go:314] "adding dynamic informer for gvr" gvr="apps/v1, Resource=deployments" I0112 19:06:04.409541       1 controller.go:233] "processing key" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:04.410239       1 informer.go:314] "adding dynamic informer for gvr" gvr="networking.k8s.io/v1, Resource=ingresses" I0112 19:06:04.410867       1 informer.go:314] "adding dynamic informer for gvr" gvr="apps/v1, Resource=deployments" I0112 19:06:04.411653       1 controllermanager.go:152] "waiting for the informer to be synced before starting controller" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" gvr="/v1, Resource=services" controller="syncer-endpoint-controller" I0112 19:06:04.414597       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=services" W0112 19:06:04.415599       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:04.415675       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:04.415741       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:04.415614       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:04.415786       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:04.415803       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource I0112 19:06:04.422794       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="networking.k8s.io/v1, Resource=ingresses" I0112 19:06:04.425895       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="apps/v1, Resource=deployments" I0112 19:06:04.428823       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=configmaps" I0112 19:06:04.433551       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=secrets" W0112 19:06:05.290755       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:05.291145       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:05.495052       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:05.495188       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:05.584174       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:05.584252       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource I0112 19:06:05.622775       1 request.go:601] Waited for 1.046215s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/discovery.k8s.io/v1beta1?timeout=32s I0112 19:06:07.222433       1 request.go:601] Waited for 1.0454483s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/discovery.k8s.io/v1?timeout=32s I0112 19:06:07.675144       1 discovery.go:186] "processing discovery" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" groupVersion="v1" resource="services" kind="Service" crd="services.core" I0112 19:06:07.683124       1 discovery.go:186] "processing discovery" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" groupVersion="apps/v1" resource="deployments" kind="Deployment" crd="deployments.apps" I0112 19:06:07.692123       1 discovery.go:186] "processing discovery" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" groupVersion="networking.k8s.io/v1" resource="ingresses" kind="Ingress" crd="ingresses.networking.k8s.io" I0112 19:06:07.701672       1 apiimporter.go:271] "updating APIResourceImport" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" group="apps" version="v1" resource="deployments" apiResourceImport="deployments.dp-8568db4.v1.apps" I0112 19:06:07.754085       1 apiimporter.go:271] "updating APIResourceImport" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" group="networking.k8s.io" version="v1" resource="ingresses" apiResourceImport="ingresses.dp-8568db4.v1.networking.k8s.io" I0112 19:06:07.762320       1 apiimporter.go:271] "updating APIResourceImport" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" resources=[] reconciler="api-importer" group="" version="v1" resource="services" apiResourceImport="services.dp-8568db4.v1.core" W0112 19:06:07.825158       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:07.825254       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:07.953574       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:07.953624       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:08.695425       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:08.695539       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:12.862075       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:12.862161       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:12.899413       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:12.899497       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:13.298070       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:13.298172       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:21.304522       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:21.304607       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:21.363398       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:21.363483       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource I0112 19:06:24.391125       1 controller.go:196] "queueing SyncTarget" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:24.391317       1 controller.go:233] "processing key" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:24.402117       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="apps/v1, Resource=deployments" I0112 19:06:24.406742       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=secrets" I0112 19:06:24.411319       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=configmaps" I0112 19:06:24.415566       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=services" I0112 19:06:24.419516       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="networking.k8s.io/v1, Resource=ingresses" W0112 19:06:25.134675       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:25.134867       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:34.917471       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:34.917531       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource W0112 19:06:42.098530       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:42.098687       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource I0112 19:06:44.363748       1 controller.go:196] "queueing SyncTarget" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:44.363929       1 controller.go:233] "processing key" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" I0112 19:06:44.370392       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=configmaps" I0112 19:06:44.374857       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=secrets" I0112 19:06:44.378804       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="/v1, Resource=services" I0112 19:06:44.383200       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="networking.k8s.io/v1, Resource=ingresses" I0112 19:06:44.387301       1 controller.go:420] "Informer is started already" syncTarget.workspace="root" syncTarget.name="dp-8568db4" syncTarget.key="cKK89Yvux7z7kBVBj3oVPIY9VBlLrL97v8mjtz" reconciler="kcp-syncer-synctarget-gvrsource-controller" key="dp-8568db4" gvr="apps/v1, Resource=deployments" W0112 19:06:46.572773       1 reflector.go:324] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: the server could not find the requested resource E0112 19:06:46.572889       1 reflector.go:138] k8s.io/client-go@v0.24.4/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource

I'm not sure if my issue is related but I also have issues getting syncer to run.
KCP version

Error in syncer pod on the physical kind cluster
      Message:   I0116 16:21:30.652098       1 syncer.go:83] "syncing" resource-types=[]
I0116 16:21:30.673366       1 syncer.go:85] "starting syncer" syncTarget.workspace="root" syncTarget.name="kind"
I0116 16:21:30.678380       1 syncer.go:113] "attempting to retrieve the Syncer virtual workspace URL" syncTarget.workspace="root" syncTarget.name="kind"
E0116 16:21:30.749586       1 run.go:74] "command failed" err="synctargets.workload.kcp.io \"kind\" is forbidden: User \"system:serviceaccount:default:kcp-syncer-kind-29c7eyul\" cannot get resource \"synctargets\" in API group \"workload.kcp.io\" at the cluster scope: access denied"

Manifest generated by the command for ClusterRole
kubectl kcp workload sync kind --syncer-image ghcr.io/kcp-dev/kcp/syncer:9358474@sha256:da59b1438fc38cddea8eed3ecc00ea35cb60de9780d38f83714908f578da6e3d -o syncer-kind-main.yaml

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: kcp-syncer-kind-29c7eyul
rules:
- apiGroups:
  - ""
  resources:
  - namespaces
  verbs:
  - "create"
  - "get"
  - "list"
  - "watch"
  - "delete"
- apiGroups:
  - "apiextensions.k8s.io"
  resources:
  - customresourcedefinitions
  verbs:
  - "get"
  - "watch"
  - "list"
- apiGroups:
  - ""
  resources:
  - configmaps
  - secrets
  - services
  verbs:
  - "*"
- apiGroups:
  - "apps"
  resources:
  - deployments
  verbs:
  - "*"
- apiGroups:
  - "networking.k8s.io"
  resources:
  - ingresses
  verbs:
  - "*"

I'm not sure if my issue is related but I also have issues getting syncer to run.
KCP version
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3+kcp-v0.10.0", GitCommit:"25254541", GitTreeState:"clean", BuildDate:"2022-12-13T17:11:33Z", GoVersion:"go1.19.3", Compiler:"gc", Platform:"darwin/arm64"}

Error in syncer pod on the physical kind cluster
      Message:   I0116 16:21:30.652098       1 syncer.go:83] "syncing" resource-types=[]
I0116 16:21:30.673366       1 syncer.go:85] "starting syncer" syncTarget.workspace="root" syncTarget.name="kind"
I0116 16:21:30.678380       1 syncer.go:113] "attempting to retrieve the Syncer virtual workspace URL" syncTarget.workspace="root" syncTarget.name="kind"
E0116 16:21:30.749586       1 run.go:74] "command failed" err="synctargets.workload.kcp.io \"kind\" is forbidden: User \"system:serviceaccount:default:kcp-syncer-kind-29c7eyul\" cannot get resource \"synctargets\" in API group \"workload.kcp.io\" at the cluster scope: access denied"

Manifest generated by the command for ClusterRole
kubectl kcp workload sync kind --syncer-image ghcr.io/kcp-dev/kcp/syncer:9358474@sha256:da59b1438fc38cddea8eed3ecc00ea35cb60de9780d38f83714908f578da6e3d -o syncer-kind-main.yaml

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: kcp-syncer-kind-29c7eyul
rules:
- apiGroups:
  - ""
  resources:
  - namespaces
  verbs:
  - "create"
  - "get"
  - "list"
  - "watch"
  - "delete"
- apiGroups:
  - "apiextensions.k8s.io"
  resources:
  - customresourcedefinitions
  verbs:
  - "get"
  - "watch"
  - "list"
- apiGroups:
  - ""
  resources:
  - configmaps
  - secrets
  - services
  verbs:
  - "*"
- apiGroups:
  - "apps"
  resources:
  - deployments
  verbs:
  - "*"
- apiGroups:
  - "networking.k8s.io"
  resources:
  - ingresses
  verbs:
  - "*"

The syncer pod keeps crashlooping.
@smalleni  i had this issue when i was using a different version of syncer for a given kcp version. the pod crash status went by   but then the above mentioned issue is still exsiting.

workload.kcp.io

My issue seems to be from the fact that the ClusterRole generated does not include the apiGroup workload.kcp.io, is that what you are also experience?

workload.kcp.io

My issue seems to be from the fact that the ClusterRole generated does not include the apiGroup workload.kcp.io, is that what you are also experiencing?

Never mind, using the syncer image with the same tag as the KCP version resulted in the syncer pod running, but i see similar errors as @yogesh-reddy in the syncer pod logs and am unable to create a deployment on the physical cluster through kcp

@smalleni to be able to create a deployment, you would need to do as below. There have been some changes with respect to the workflow in v0.10.0

Run the command kubectl kcp bind compute "<Full_path_of_your_workspace>"
Now try to create deployment and it should work.

p.s: If you are trying to add deployment as a normal user you might hit issue described in here https://github.com/kcp-dev/kcp/issues/2597 follow steps in here https://github.com/kcp-dev/kcp/issues/2597#issuecomment-1380862841 to workaround. If you are trying to add deployment as an admin user may be things will be smooth for you

I have ran in the same issues ... this new workflow should be documented (e.g. in https://docs.kcp.io/kcp/main/ )

@smalleni to be able to create a deployment, you would need to do as below. There have been some changes with respect to the workflow in v0.10.0

Run the command kubectl kcp bind compute "<Full_path_of_your_workspace>"
Now try to create deployment and it should work.

p.s: If you are trying to add deployment as a normal user you might hit issue described in here #2597 follow steps in here #2597 (comment) to workaround. If you are trying to add deployment as an admin user may be things will be smooth for you

Thanks this resolution worked for me.

I was able to successfully sync the deployments on a CRC openshift cluster. But when I do the same setup on a ROSA cluster. The syncer is not working. Below is the error I am facing.
I0122 16:08:44.082978       1 syncer.go:83] "syncing" resource-types=[]
I0122 16:08:44.083874       1 syncer.go:85] "starting syncer" syncTarget.workspace="2mer96r01qmt2xrj" syncTarget.name="ocp-ztp"
I0122 16:08:44.084061       1 syncer.go:113] "attempting to retrieve the Syncer virtual workspace URL" syncTarget.workspace="2mer96r01qmt2xrj" syncTarget.name="ocp-ztp"
E0122 16:09:14.087668       1 run.go:74] "command failed" err="Get \"https://<IP_ADDRESS>:6443/clusters/2mer96r01qmt2xrj/apis/workload.kcp.io/v1alpha1/synctargets/ocp-ztp\": dial tcp <IP_ADDRESS>:6443: i/o timeout"

Any idea on how do we go about a resolution for this error?  I couldn't understand from which source ip my ROSA cluster is trying to hit my destination endpoint <IP_ADDRESS>:6443. Any help on this issue would be much appreciated.
Reference for how I resolved the same issue on CRC cluster:  https://github.com/kcp-dev/kcp/issues/2623
Thank You.

/transfer-issue contrib-tmc


Polymorphic relationships

What about polymorphic relationships?
Is there any way to manage them?

Voyager does not currently support polymorphic relationships.  You're still free to use them in parallel to Voyager, but Voyager will not be able to maintain/control them.


TS-4883: Fix Thread::start call in EventProcessor::start

TS-4883

Looks good to me

[approve ci]

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/843/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/738/ for details.

@PSUdaemon @masaori335 Let's get another Jira open to remove or refactor the thread startup options so that this kind of error can't happen. It looks to me like the thread function arguments are not ever used.


Introduce TypeScript for developer performance.

The TypeScript is a language for application-scale JavaScript. It provides many things for developer convenience such as TypeSystem and access modifiers and so on. We are already using Babel transpiler to cover ECMA 6 and 7 but the standard is still lacking. So, we can consider to introduce TypeScript for developer performance and convenience.

Close this issue, you can re-open it if you want.


Failure: cannot instantiate ctype 'EVP_MD_CTX' of unknown size.

I reported this issue in https://code.google.com/p/google-cloud-sdk/issues/detail?id=1105 and I was redirected here.
When I upgraded python-cryptography Debian package from version 1.4-2 to version 1.5-1, the above error occurs (Failure: cannot instantiate ctype 'EVP_MD_CTX' of unknown size. ). Downgrading python-cryptography to 1.4 resolves the issue. So there is problem either in python-cryptography or in oauth2client.
Result from python -c "import OpenSSL; print(OpenSSL.__version__)" is 16.0.0.
Python stack trace follows:
DEBUG: Exception stack trace:
    Traceback (most recent call last):
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/__main__.py", line 577, in _RunNamedCommandAndHandleExceptions
        collect_analytics=True)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/command_runner.py", line 299, in RunNamedCommand
        return_code = command_inst.RunCommand()
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/commands/ls.py", line 446, in RunCommand
        bucket_fields=bucket_fields):
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/wildcard_iterator.py", line 456, in IterBuckets
        for blr in self._ExpandBucketWildcards(bucket_fields=bucket_fields):
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/wildcard_iterator.py", line 375, in _ExpandBucketWildcards
        provider=self.wildcard_url.scheme):
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/gcs_json_api.py", line 519, in ListBuckets
        global_params=global_params)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/third_party/storage_apitools/storage_v1_client.py", line 423, in List
        config, request, global_params=global_params)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/apitools/apitools/base/py/base_api.py", line 701, in _RunMethod
        http, http_request, **opts)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/apitools/apitools/base/py/http_wrapper.py", line 351, in MakeRequest
        max_retry_wait, total_wait_sec))
      File "/usr/lib/google-cloud-sdk/platform/gsutil/gslib/util.py", line 1596, in WarnAfterManyRetriesHandler
        http_wrapper.HandleExceptionsAndRebuildHttpConnections(retry_args)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/apitools/apitools/base/py/http_wrapper.py", line 341, in MakeRequest
        check_response_func=check_response_func)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/apitools/apitools/base/py/http_wrapper.py", line 391, in _MakeRequestNoRetry
        redirections=redirections, connection_type=connection_type)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/oauth2client/oauth2client/client.py", line 616, in new_request
        self._refresh(request_orig)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/oauth2client/oauth2client/client.py", line 885, in _refresh
        self._do_refresh_request(http_request)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/oauth2client/oauth2client/client.py", line 900, in _do_refresh_request
        body = self._generate_refresh_request_body()
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/oauth2client/oauth2client/client.py", line 1611, in _generate_refresh_request_body
        assertion = self._generate_assertion()
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/oauth2client/oauth2client/service_account.py", line 396, in _generate_assertion
        key_id=self._private_key_id)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/oauth2client/oauth2client/crypt.py", line 97, in make_signed_jwt
        signature = signer.sign(signing_input)
      File "/usr/lib/google-cloud-sdk/platform/gsutil/third_party/oauth2client/oauth2client/_openssl_crypt.py", line 100, in sign
        return crypto.sign(self._key, message, 'sha256')
      File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2563, in sign
        md_ctx = _ffi.new("EVP_MD_CTX*")
    TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size

This smells like not directly are issue. Can you try using a virtualenv and see if this still happens? I'm worried that the OpenSSL package in dist-packages (owned by debian) is causing the conflict.

While looking at the problem, I noticed that a new python-openssl Debian package was released for new version 16.1.0-1 while I was on 16.0.0-2. After upgrading to it, and also upgrading python-cryptography to latest version 1.5-1 (from 1.4-2), and upgrading google-cloud-sdk to latest 125.0.0-0, the problem disappeared.


Fixed: BaseBuilder increment/decrement do not reset state after a query

Description
https://github.com/codeigniter4/CodeIgniter4/issues/6145
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[x] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

@MGatner After each query, the state of the object is reset so that the next query does not include data from the previous one. There was no such state reset for increment/decrement methods.
The resetWrite() and resetSelect() methods are responsible for resetting the state for queries that change data and selects, respectively.

Thanks for the explanation!


added bucket sort algorithm

Hi sir/madam,
I am Ming Liang and I have implemented a sorting algorithm called Bucket sort.
I hope you can take a moment to read the algorithm. Thank you in advance.
Best regards,
Ming Liang

@DrakonDarquesse to make the tests possible, you have to add BucketSort! to the export list in the TheAlgorithms.jl file.

@DrakonDarquesse Hello. Sorry for the ping. What is the progress of this PR?

Will complete it asap

@DrakonDarquesse I have finished to fix the PR if you want

If you merge https://github.com/DrakonDarquesse/Julia/pull/1 it should fix this PR

Any reasons why the CodeCoverage is failing? thinking

Not all the code introduced was tested.  A couple of line were not hit by the tests, thus not covered.
I think it is okay in this case. On the long run, it is likely that we should implement extensive testing for sorting algorithms.


error on fedora

I am getting this error on fedora 39. I have installed all dependencies.
init_dialog: dlg_parse_rc
use_scrollbar:27: unknown variable

I commented out use scrollbar in ~/.dialogrc and it seems to launch now.

Interesting, that seems to be specific to the fedora package of dialog.
Just out of curiosity, could you post a default generated dialogrc?
Simply execute dialog --create-rc test
Also, is the dialog black/white theme being displayed correctly?


Manual rebuild for python310

The migrator seems to have gotten stuck in resolving this somehow. See how far we get manually.
Edit: migrator came by after all:
Closes #105

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@wolfv
This looks like a bit of a weird resolver error:
RuntimeError: Solver could not find solution.Mamba failed to solve:
 - [...]
 - qt 5.12.5.* h1b46049_0
 - [...]
 - pyqt-impl 5.12.3.* py39he44290a_8

The reported errors are:
- Encountered problems while solving:
-   - package pyqt-impl-5.12.3-py39he44290a_8 requires qt >=5.12.9,<5.13.0a0, but none of the providers can be installed

In particular, I don't understand why pyqt-impl sometime pulls in qt 5.12.5 instead of 5.12.9. In any case, forcing the host dep to be up to date fixes it (see CI for last 2 commits).

@conda-forge/pyqt - aside from the long runtime on aarch (same as before), I think this should ready. Not sure why things didn't work without the last commit, happy to adapt if necessary, but I don't think it's bad per se.

Hm, seems cross-compilation needs more work. I suggest to tackle it after the 3.10 migration; will remove the last two commits again.

From the CI in #105 (of the cross-compile commits now cherry-picked here):
import: 'PyQt5.sip'
import: 'PyQt5.QtCore'
import: 'PyQt5.QtGui'
Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/pyqt_split_1636582680613/test_tmp/run_test.py", line 8, in <module>
    import PyQt5.QtGui
ImportError: libXext.so.6: cannot open shared object file: No such file or directory

Do we need {{ cdt('libxext-devel') }} as a host dep on aarch, or what's happening here (since it was working in emulation...)?

Got further now; still failing though:
+ DISPLAY=localhost:1.0
+ xvfb-run -a bash -c 'python pyqt_test.py'
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, vnc, webgl, xcb.

/usr/bin/xvfb-run: line 181: 11484 Aborted                 (core dumped) DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@" 2>&1

Unfortunately, the xcb error remains:
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.

@isuruf @ocefpaf
I realised this still has an automerge-label on it. It's perhaps better to remove this for now, because I don't claim that my debugging of the cross-compilation - even though it might lead to green CI - is necessarily correct.

@isuruf, I'm playing a very trivial form of whack-a-mole here. If there's a more systematic way to add the requirements (e.g. all the libX for which there are cdt's in the host reqs), then I'm happy to do it. Right now I'm trying to not add more than necessary, hence the slow iterations.

Seems I whacked all the moles by now! 😅
PTAL if the yum_requirements-approach is correct @isuruf

LGTM now :-)
Merge?

go!


Support mix-encodings file search.

Vs-code file search supports only-one encoding only.

I am planning to add support for users of vs Code with an optional advanced search capability that supports multiple file codes.

This is https://github.com/microsoft/vscode/issues/34315 and we won't be able to support it, sorry.

@roblourens
ripgrep supports searching files in text encodings other than UTF-8, such as UTF-16, latin-1, GBK, EUC-JP, Shift_JIS and more. (Some support for automatically detecting UTF-16 is provided. Other text encodings must be specifically specified with the -E/--encoding flag.)
https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#file-encoding
We can guess the file's encoding and provide it to riggrep.

We can't do that without massively slowing down search.

We can't do that without massively slowing down search.
This will slowing down search,so i only want it to be an optional advanced


New component [Message]

ref: https://ant.design/components/message.
I think it is different with Notification. like : https://ant.design/components/notification.
In my use case, messages are often used as feedback on user actions, such as success or failure.
example : Delete record success
Notifications are often used as an unsolicited message from the server to the client (Websocket)
example: There has a new registered user need to approve
They are show in different position and with different styles

While I understand the potential differences between both, it seems to be the same component logic, with a slightly different style. IMO, rather than building another component, it would make more sense to keep a single one, with more styling options. In the meantime, I guess you can easily tweak the UI prop to have the "message" styling.

How to use these two components both?

I fail to see where this differs from the Notification component as you can use it without the whole toasting system: https://ui.nuxt.com/overlays/notification#title. You also have access to the Alert component which differs a bit in term of styling.

@benjamincanac It has different position.Is there a way to use them at the same time?

Not sure to really understand what you're looking for but yes, you can put a Notification component everywhere you want and have multiple at the same time as it's basically a Card with a title and a description.

In my project, I want to have a notification component at the bottom right corner and another message component at the top of the page.How to use them together?Do I need to pass parameters in useToast?

Oh I see, unfortunately you can choose only one position at a time for now: https://ui.nuxt.com/overlays/notification#usage when using the useToast composable.

That is why I open this issue.
I think there should has a Toast component with useToast and a Notification component with useNotification
Or there could has easy way to change the position at runtime, like an option in useToast


fix(ui): improve playground error message readability

Summary
The playground error message readability can be improved. It currently looks like:

Most of the error messages will come in a JSON-RPC format (default error response returned by the snapshot.js SDK), we should pretty print the JSON like

How to test

Go to the playground
Trigger any scenario with error messages (test this one: https://snapshot-git-improve-playground-error-ui-snapshot.vercel.app/#/playground/erc20-balance-of?query=eyJwYXJhbXMiOnsic3ltYm9sIjoiQlJQIiwiYWRkcmVzcyI6IjB4QUI3ODExODhkNEY0MWYzNmVmRmY1MDc3OERDODczZjY4Rjk3ZTkzOSIsImRlY2ltYWxzIjo0fSwibmV0d29yayI6IjgwMDAxIiwic25hcHNob3QiOiIifQ..)
The error messages should shown pretty printed

@samuveth what do you think ?


Add first-class support for testing workers

💡 Feature request
I would like to see first-class support for unit testing CF workers.
Describe the feature
Provide testing framework/integration to tests workers with unit and integration tests. I would like to see support for Jest or another testing feature provided out of the box by Cloudflare, right now this missing even documentation is lacking. This should cover all runtime APIs. I created this issue here because I don't know where these kinds of issues should be reported.
Describe the alternatives
There is @dollarshaveclub/cloudworker, which is not maintained anymore. You can create your own setup, but it's a little bit hard to mock all features workers provide because the implementation of workers is not open sourced.

Have you tried using wrangler dev?

Have you tried using wrangler dev? or wrangler preview?

I don't see how this going to solve testing. How you would test accessing to KV store and then resetting data? I can see that you are going to call some cleanups functions after these tests run, but with that in mind you are going to completely go through the roof and relying on network request in tests are not a great idea.

Thanks so much for submitting this feedback! Local and unit testing is definitely something we are investigating and recognize need to do better.
@huv1k Would it matter to you whether the code was actually running locally (e.g. emulation) or actually running on our edge? (e.g. script/resources get sent, in the background, to our edge)

I would prefer to have it running locally because the network is not always reliable and could fail in CI. I could see there would be a mocking function for each feature.

I agree fully! There should be a way to develop and run tests locally without the requests being routed to the Cloudfare edge..
Never really understood why Cloudflare neglected this and usually points to 'wrangler preview/dev' as a replacement for a proper local environment. Back in the day there was support by the community but it is not maintained any more: https://github.com/dollarshaveclub/cloudworker
Other cloud providers such as Azure have support for local development environments. There should be an official support maintained by Cloudflare @rita3ko :)
In the mean time you can look into jdanyow's packages collection:
https://github.com/cloudflare/wrangler/issues/1321
https://github.com/cfworker/cfworker
Thanks!

We now have an officially supported solution with miniflare https://miniflare.dev/ We will integrate this more deeply with wrangler in the future, but this is usable today.

We now have an officially supported solution for this with miniflare https://miniflare.dev/ We'll be integrating this with wrangler more deeply in the future, but this is usable today.
I'm going to close this issue for now, but feel free to drop feedback!


RFP — Tesseract

1. Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages
[x] There is no open issue for this package
[x] The issue title starts 'RFP — '
[x] The download URL is public and not locked behind a paywall/login

2. Package details

Software project URL: https://github.com/tesseract-ocr/tesseract
Direct download URL for 64-bit Windows installer: https://digi.bib.uni-mannheim.de/tesseract/tesseract-ocr-w64-setup-v5.0.0-alpha.20190708.exe (links from here, that described in official Tesseract wiki)
Direct download URL for 32-bit Windows installer: https://digi.bib.uni-mannheim.de/tesseract/tesseract-ocr-w32-setup-v5.0.0-alpha.20190708.exe
Have this software command-line interface (CLI)? Yes
If «yes» for previous question, what folder(s) must be added to the PATH environment variable? .
Software summary/short description: popular (29214 GitHub stars for 19 August 2019) open source optical character recognition (OCR) engine for different operating systems; read Wikipedia article for more details.

3. Notes
In installation process user need to select Additional script data and Additional language data, if he need OCR not solely for English texts.
Thanks.

Status: Review
https://chocolatey.org/packages/tesseract
Hi @Kristinita, I have just submitted a Chocolatey package but it will install tesseract with default options, so in english. I tried to use an Autohotkey script but the problem is when you select all languages and scripts, 2 languages files are not available and you have to click on OK button to continue anyway the installation.

A solution can be to unselect options corresponding to missing files but:

The package will fail if another language file disappears or is renamed.
It doesn't allow to easily add another languages which are not included in the installer.

Under Linux, there are packages for each language (131) and script (35) but I don't know if we can also create 166 Chocolatey packages.  On other hand, keepass is a popular software and its Chocolatey package doesn't integrate other languages than english.
So, suggestions are welcome...

Note: Languages and scripts can't be embedded in the package as their total size exceed 200 MB.

@chtof,
**Type: Clarifying question ❔ **

I tried to use an AutoHotkey script but the problem is when you select all languages and scripts, 2 languages files are not available and you have to click on OK button to continue anyway the installation.

Is it a problem of Tesseract installer? If yes, maybe we will create issue to Tesseract issue tracker?
Thanks.

@Kristinita Issue opened.

Instead of using the installer to download the Tesseract models (*.traineddata files), it might be easier to get them directly from https://github.com/tesseract-ocr/tessdata_fast.

The package description is outdated. So is the README of Tesseract which was used as the source of that description. Maybe I can update it soon.

I suggest updating the installer to the October version.

Hi @stweil,

Thank you for your help so I understand the issue with missing files should be solved soon. I think it's easier to install all language and script directly from the installer instead of to search after the URL where the files should be downloaded, download the language file(s), search in which directory the language file(s) should be copied, download the script file(s), search in which directory the script file(s) should be copied.
Yes, the package description come from https://github.com/tesseract-ocr/tesseract/blob/master/README.md
I suggest updating the installer to the October version. <IP_ADDRESS>91010-alpha has just been just submitted (files are also missing in this version as I wrote in the opened issue).
As a suggestion, an installer option to choose to install all languages and scripts data can help us also to have a cleaner and more robust Chocolatey package (because currently, when the issue with the 2 missing files will be solved, we would have to use an Autohotkey script to be able to install silently Tesseract with all languages and scripts data options enabled in the installer).


Keep redirecting and add up new 'state' in the session

Middleware stack:
(-> app-route
  (friend/authenticate {:allow-anon?          true
                       :default-landing-uri  "/console"
                       :login-uri "/login"
                       :workflows [(workflows/interactive-form
                                    :login-uri "/email-login"
                                    :credential-fn email->user)
                                   (oauth2/workflow
                                    {:client-config fb-client-config
                                    :uri-config fb-uri-config
                                    :access-token-parsefn get-access-token-from-params
                                    :login-uri "/fb-login"
                                    :credential-fn fb-token->user})]})

 wrap-multipart-params
 wrap-keyword-params
 wrap-external-webhooks
 wrap-nested-params
 wrap-params
 wrap-session)

Symptom - 'token' and 'state' entry in 'session' keep adding up. I.e.,
:session
{:vChUz4SvABgQBgjDvrpQERPo1UFyWYwRNimP81aSrCGZ3leug-AC2sNVLGgBqSzEe0giQ1TrvAGwg9mT "state",

:-kxHImqfWVN3z7brZOIQePKdpC29oxDnSBAscu38l1AUStAVP-hLu3fR8qD9thzosqEXnlMEGqJQtD-p "state",

....}

Maybe I am doing something wrong. Or it is a bug. If it is a bug, I can fix it by changing following two functions - making 'state' key and token value not other way around.
(ns friend-oauth2.workflow)

(defn- redirect-to-provider!
  "Redirects user to OAuth2 provider. Code should be in response."
  [{:keys [uri-config]} request]
  (let [anti-forgery-token    (util/generate-anti-forgery-token)

        session-with-af-token (assoc (:session request) :state anti-forgery-token)]
    (-> uri-config
        (util/format-authn-uri anti-forgery-token)
        ring.util.response/redirect
        (assoc :session session-with-af-token))))

(ns friend-oauth2.util)

(defn extract-anti-forgery-token
  "Extracts the anti-csrf state key from the response"
  [{session :session}]
  (:state session))

If the 'state' is in friend's ::identity map, it would be better. Because when logout get called it will be cleared from session by friend's logout function (just a thought, not sure if this is possible).

Hey, sorry I've been slow to respond.  I'm in the process of doing some serious refactoring now and this'll get updated to work in the way you're suggesting as part of it.  Will update here when that's in!


Folder refactor

Issue
Working on this issue #230
Moved folders

[x] Modules
[x] Tests
[x] Utils

Tests

[x] Passing

Suggestions
If you think @ageddesi that more files should be added, please tell me :)

Hi @headStyleColorRed Sorry we have just released a new version. So now is a perfect time to merge back in the branch and resolve the conflict issues. Once that is done I will make sure this is the only one merged in next.

Hi @headStyleColorRed Sorry we have just released a new version. So now is a perfect time to merge back in the branch and resolve the conflict issues. Once that is done I will make sure this is the only one merged in next.

Perfect!! Yesterday i was struggling with all the conflicts xd I'll get on it :D

Alright @ageddesi! The pr has been updated

Hi @headStyleColorRed Thanks for the massive refactor. :) 👍 Happy Hacktoberfest


feat: added search, refactored how plugins are added. Added hashes to…

Refactored Plugins
Added search and filter by plugin status
Added ability to link to plugins
Added github link to repo

Wow! Thank you so much for this ❤
The refactoring looks great, and search will help a lot to make this list more usable.
Some things to discuss:

Checking PluginDsv, we are now importing the asset file both in the Component and in the Plugin description to do the status test. I think it would be good to be able to get the test from the result of building the demo component. What do you think if we use defineComponent in the description file directly instead of doing a SFC .vue file? I also like that in this way adding a new plugin for contributors only involve touching one file (even when there is a test)
The search is sleek, but I am getting some strange results. Search for inject for example, and it will show a lot of unrelated plugins. Maybe a different and simpler strategy would produce better results
Thanks for implementing the anchoring also! When the user press the button, we should push the hash in the current URL so there is feedback that it worked. I was thinking that when a user loads a url with a hash, we should show that plugin info expanded, what do you think? About the button style, nice idea with the floating button. What do you think if we do it a bit smaller, using the # symbol as icon (so it looks like pressing an anchor) and aligned vertically with the plugin name. Something like this https://v3.vuejs.org/api/global-api.html#definecomponent, but with the circle button style you used.

Sure thing, I'll make those changes, I'll also check what is going on with the search. It is also searching the description and uses fuzzy search, so that it probably what causes weird results. I think I can reduce the tolerance to get more specific results

@matias-capeletto We could also use functional components instead of defineComponent like this https://v3.vuejs.org/guide/migration/functional-components.html#_3-x-syntax. What do you think?

Also do you want to use the defineComponent and functional component for every demo or just where there is overlap with their tests?

Let's be consistent and have only one file per plugin, so this should be for every demo.
About using functional components, sure! What do you think about using something like developit htm, https://twitter.com/youyuxi/status/1298674352989364225

Sure, sounds good to me

This is amazing @jacobclevenger, thanks a lot again, publishing now 🙌🏼


add link-walking support

We need a way to add links to an object, and to query them
; starts with a bucket/key
; and then a list of bucket/link-tags
; specs
(link-walk conn "bucket" "key"
  [("other-bucket" "tag1" :keep true)
   ("second-bucket" "tag2")])

Thinking of something like this in sumo.client/put:

{:content-type "application/json"
 :value {:foo "bar" :baz "quux"}
 :links [{:bucket "b" :key "k0" :tag "t"}
         {:bucket "b" :key "k1" :tag "t"}]}

Thinking of something like this in sumo.client/put:
+1


Slimes spawned via Witchwater+mushrooms have 10 hearts instead of a half

Seriously Mojang, EntitySlimes don't calculate their max health correctly?

Seems like even the jump strength is like the bigger ones

Are you sure that's not just because they can spawn in an area around the barrel including off the ground?
Health fix is included in version 0.4.1 on curse.

The health problem has been fixed in <IP_ADDRESS>.
Fixing the health problem has even fixed the jump strenght.


Dockerize

Added glide for package management and docker files to run app in development.
README has the commands necessary to bootstrap(migrate db) and start application.

Hey @jhsc it looks good 👍  give me until tomorrow to go through the changes :)

@jhsc Thanks while I checked the code I had some small things I would change or add, e.g. ports to the redis in the docker-compose.yml just for consistency :)
instead of hardcoding the host and port change the mysql config (like I did in my docker branch(docker_setup)
Otherwise great job man! I see you added this TODO about cleaning up the migrations I would like to hear what you think how I/We should proceed on that.
I sent you an email as well but I just renamed my old golang.zone folder in my $gopath and cloned yours then did a git checkout dockerize.


Ground items plugin

Describe the bug
A clear and concise description of what the bug is.
ground items plugin doesnt hide Red spiders' eggs at section "Hidden Items"

The issue tracker is not a support forum. Please join the Discord for questions of support.


fix the typings location define

fix the #3373  issue

Codecov Report

Merging #3374 into master will increase coverage by 1.42%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3374      +/-   ##
==========================================
+ Coverage   12.39%   13.81%   +1.42%
==========================================
  Files         267      267
  Lines       10271    10449     +178
  Branches     1337     1255      -82
==========================================
+ Hits         1273     1444     +171
- Misses       8899     8936      +37
+ Partials       99       69      -30

Impacted Files
Coverage Δ

src/util/dev/builder-cache.ts
83.33% <0%> (+4.16%)
:arrow_up:

src/util/dev/router.ts
73.68% <0%> (+4.29%)
:arrow_up:

src/util/dev/yarn-installer.ts
89.09% <0%> (+5.36%)
:arrow_up:

src/util/dev/builder.ts
72.62% <0%> (+5.74%)
:arrow_up:

src/util/dev/server.ts
64.11% <0%> (+5.86%)
:arrow_up:

src/util/get-update-command.ts
11.76% <0%> (+6.88%)
:arrow_up:

Continue to review full report at Codecov.

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

Actually this is a duplicate of #3344.