add status command for crictl

Signed-off-by: heartlock<EMAIL_ADDRESS>ref #33
@feiskyer @xlgao-zju

@heartlock Could update the PR by using same connection func introduced in #52

sure, I will update it.

updated it ! @feiskyer

Thanks. LGTM.


Add deserialization and validation of parameters - #67

Deserialized values can be accessed through static helper methods as below:

OpenApiHandler.getQueryParameters(exchange, true)
OpenApiHandler.getPathParameters(exchange, true)
OpenApiHandler.getHeaderParameters(exchange, true)
OpenApiHandler.getCookieParameters(exchange, true)

The below helper methods return all available parameter values:

OpenApiHandler.getQueryParameters(exchange)
OpenApiHandler.getPathParameters(exchange)
OpenApiHandler.getHeaderParameters(exchange)
OpenApiHandler.getCookieParameters(exchange)

Arrays and objects are validated against deserialized values when necessary. The deserialization is supported to the extent of the examples in the openapi serialization doc
Usage examples can be found in /openapi-validator/src/test/java/com/networknt/openapi/RequestValidatorTest.java.

@Dasanko Could you please review the fix? Thanks.

How can I go about testing this? It's not playing nicely as-is with light-codegen.

@Dasanko could you please elaborate? Do you mean that the light-codegen cannot generate a project from your specification?

@Dasanko, @dz-1 has updated the TestProject.yaml you have provided and I have checked it into the model-config repository. The light-codegen can generate the project successfully.
https://github.com/networknt/model-config/tree/master/rest/openapi/json-query-param
And here is the change. https://github.com/networknt/model-config/issues/52

Sorry, I've been busy.
Seems to be working fine now, thanks!
Here are my findings:
curl -k -X GET https://localhost:8443/api/testEndPoint?TestObject={testProperty=testing} (fails, as expected, it's not part of the standard)
curl -k -X GET https://localhost:8443/api/testEndPoint?TestObject=testProperty,testing (fails, should it be supported as well? Not very important)
curl -k -X GET https://localhost:8443/api/testEndPoint?testProperty=testing (passes)
curl -k -X GET https://localhost:8443/api/testEndPoint?TestObject[testProperty]=testing (passes)

@Dasanko I think you are testing from the master branch. The code is not merged into the master yet. I have tested all scenarios above and documented at https://doc.networknt.com/tutorial/rest/openapi/parameter-serialization/json-query-param/

@stevehu My bad, you're right. I had replaced light-codegen's (master branch) files with the new ones from model-config.
It is working fine, thank you!


CSS added for each jBox

For each call to new jBox('Image'), this is added to the head section:
<style>
@-webkit-keyframes jBox-animation-zoomOutOpen-open {0% {-webkit-transform:scale(1.1);}100% {-webkit-transform:scale(1);}}.jBox-animation-zoomOutOpen-open {-webkit-animation-duration: 180ms;-webkit-animation-name: jBox-animation-zoomOutOpen-open;}@-webkit-keyframes jBox-animation-zoomOutClose-close {0% {-webkit-transform:scale(1);}100% {-webkit-transform:scale(1.1);}}.jBox-animation-zoomOutClose-close {-webkit-animation-duration: 180ms;-webkit-animation-name: jBox-animation-zoomOutClose-close;}
</style>

I guess the performance could be better, if this would be added just once.

Actually, this is intended. In version 0.4.0 the CSS is customised for each instance of jBox. The animations will get the same animation speed as the fading duration, thats why each instance needs its own CSS.


chore: remove sr25519

The dependency seems unused, therefore removing it.
Fixes #29

LGTM. Thanks.


bug: vercel analytics is not working

Opening to keep track of ongoing issues getting Vercel Analytics to work. @Markkos89 implemented the required changes in #192 and again in #219 with no luck, so we have opened a support query with the team. For them to take a look.

This is still open with Vercel's support team, given their support team access to the repo and hoping for an answer soon

Update on this: it looks like it wasn't enabling analytics as there wasn't a card associated with the account. Hilarious that this wasn't an error that showed on screen. I am waiting for the Vercel team to clear up under what circumstances we'll be charged, and assuming they're not going to start charging us loads, I will add a card and then enable analytics

Updating here, Vercel are still having issues - I don't have time to do this today so kicking the todo back but if anyone else in the team has the permissions on Vercel here is the support thread - https://vercel.com/developdao/~/support/cases/00203579
cc @wolovim

closing this as solved


fix: Enable strict TypeScript settings

Sets TypeScript to strict
Biggest changes:

I made the webId field in Credentials optional. This way the CredentialsExtractor always returns a Credentials object, even if no credentials were found. (Instead of returning undefined in that case).
BodyParser now returns Representation | undefined. Not convinced that this is the best solution, but it is what is needed for now since the SimpleBodyParser also handles the case of there being no body. Perhaps this should be caught in the RequestParser instead. Related to #8 .
There are some cases where a check that was in the canHandle function was needed again in the handle function to prevent accessing potential undefined data since some input fields are optional. E.g. the method field in a HttpRequest. Another option would be to leave behind that duplicate check and tell TypeScript to trust us that the data is there (since it should have been checked in canHandle). Not that big of an issue but might become a problem in the future if more advanced checks are needed.
The ! operator was used in some cases to convince TypeScript that it shouldn't worry. Specifically in these cases:

In constructors where Object.assign was used to assign values to the class variables. The only way to get around that would be to assign them all manually which can get ugly if there are many. Related TypeScript issue with people complaining about this here (so far it has not been fixed).
One specific instance where an object was made right before the loop going over its keys to have cleaner code. Having a check there seems unnecessary.
Some tests since it just makes some things easier there.

Excellent!

* `BodyParser` now returns `Representation | undefined`. Not convinced that this is the best solution, but it is what is needed for now since the `SimpleBodyParser` also handles the case of there being no body.

I wonder if we want an EmptyRepresentation singleton.


Installing cli fails - '<EMAIL_ADDRESS>is not in the npm registry.

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Not that I can tell
Description

Installing the Angular CLI via yarn or npm on either a local machine or on a gitlab ci runner seems to error with the message that the package @angular-devkit/architect cannot be found.
🔬 Minimal Reproduction

Reproducing the issue seems as simple as trying to install the cli.
The node version used is LTS (v12.18.3) and I've tried running this with both yarn (v1.22.4) and npm (v6.14.6).
🔥 Exception or Error
npm:

[cfi@gravity ~]$ npm i -g @angular/cli
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@angular-devkit%2farchitect - Not found
npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of '@angular/cli'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/cfi/.npm/_logs/2020-08-06T09_35_02_383Z-debug.log

yarn:

[cfi@gravity ~]$ yarn global add @angular/cli
yarn global v1.22.4
[1/4] Resolving packages...
error Couldn't find package "<EMAIL_ADDRESS>required by "@angular/cli" on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
warning @angular/cli > universal-analytics ><EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
warning @angular/cli > universal-analytics > request ><EMAIL_ADDRESS>this library is no longer supported
Error: Couldn't find package "<EMAIL_ADDRESS>required by "@angular/cli" on the "npm" registry.
    at MessageError.ExtendableBuiltin (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:721:66)
    at new MessageError (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:750:123)
    at PackageRequest. (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:36539:17)
    at Generator.throw ()
    at step (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:310:30)
    at /home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:323:13
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error: Couldn't find package "<EMAIL_ADDRESS>required by "@angular/cli" on the "npm" registry.
    at MessageError.ExtendableBuiltin (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:721:66)
    at new MessageError (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:750:123)
    at PackageRequest. (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:36539:17)
    at Generator.throw ()
    at step (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:310:30)
    at /home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:323:13
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error: Couldn't find package "<EMAIL_ADDRESS>required by "@angular/cli" on the "npm" registry.
    at MessageError.ExtendableBuiltin (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:721:66)
    at new MessageError (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:750:123)
    at PackageRequest. (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:36539:17)
    at Generator.throw ()
    at step (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:310:30)
    at /home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:323:13
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error: Couldn't find package "<EMAIL_ADDRESS>required by "@angular/cli" on the "npm" registry.
    at MessageError.ExtendableBuiltin (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:721:66)
    at new MessageError (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:750:123)
    at PackageRequest. (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:36539:17)
    at Generator.throw ()
    at step (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:310:30)
    at /home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:323:13
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error: Couldn't find package "<EMAIL_ADDRESS>required by "@angular/cli" on the "npm" registry.
    at MessageError.ExtendableBuiltin (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:721:66)
    at new MessageError (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:750:123)
    at PackageRequest. (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:36539:17)
    at Generator.throw ()
    at step (/home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:310:30)
    at /home/cfi/.nvm/versions/node/v12.18.3/lib/node_modules/yarn/lib/cli.js:323:13
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

🌍 Your Environment

- cli is not installed

Anything else relevant?

The operating systems tried are the node:10 docker image for the gitlab runner and arch linux running nvm for the local machine.

I have the same issue while trying to update an application from Angular 9 to Angular 10.

Closing this in favour of #18460


Make Multi-line Field Exclude ending Newline

null
Microsoft Reviewers: Open in CodeFlow

Maybe an engineer should look at this, since it's a metadata only change - not sure how it made it past the scan in the first place

@wingetbot run

@wingetbot run


GenericCredentials is more opinionated than it should be

If you want to implement an auth based solution which uses a base 64 encoding none of the credentials classes will work at all.
For instance say I want the following Authorization header:Authorization: token t0s5DmvAr0wZP6mWdw/aTM0j3m9ES8dD6DOG+Z0JSYE=. I cannot use this because the parser thinks that the = in the base64 encoding is part of a map for the GenericCredentials.
I propose the following. Change to  GenericCredentials(authScheme: AuthScheme, value: String). If having a Key/Value solution is desired we could create KeyValueCredentials which behaves the same as the GenericCreditials today.

Fixed by #1184.


Add bbox annotator example

Description
As suggested by @jni in this image.sc thread, this PR adds an example of using napari to annotate t+2D images with bounding boxes.
Type of change

[x] New feature (non-breaking change which adds functionality)

References
image.sc post
How has this been tested?

[x] all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Pretty cool work @kevinyamauchi ! Could you add a couple of screenshots of this looks :)

posting a screenshot / movie would be great too! thanks!!

Pretty cool work @kevinyamauchi ! Could you add a couple of screenshots of this looks :)

No problem! Here's a quick screen capture. I'll updated it when I swap out the image as suggested by @sofroniewn .

One thing that i noticed is that after you finish drawing a rectangle it looks selected (at least in the hover) but it's not. We probably want to fix that, but that can be another PR!

Ah yeah, I just noticed that. I can make an issue.

Thanks again for the feedback, @goanpeca  and @sofroniewn  I've updated the example to use the skimage.data.camera()image.

@kevinyamauchi you should update your skimage version, that's an outdated camera picture. 😂 https://twitter.com/jnuneziglesias/status/1338857729264250882


interplate method for DOS

fixes #141

The first two commits were about the interp method. The rest were fixes of CI.


Switch rsync for fs-extra

Turns out the rsync package still requires rsync to be available locally. We can just use fs.copy here, which does not have shell.cp's issue with dot files.
Test Plan:
Ran publish script, confirmed .circleci files are published, without pushing .DS_Store files.

Can this get a publish? The rsync dependency (not mentioned in the docs as far as I can see) broke Jest's website deploy

@SimenB Hi! Sorry for the delay here. I took a little time off over the holidays. I need to fix one more thing before I publish, or else I am going to break another site. I will work on that today. In the meantime, I see you are adding rsync to your config.yml as a workaround at this point.
You can alternatively do it this way under deploy-website:
 - run:
 -          name: Install Dependencies
 -          command: sudo apt install rsync

Time off during holidays is perfectly acceptable, enjoy the holidays! 😀
Have you got any idea on the new issue (git push rejected) https://github.com/facebook/jest/pull/5184#issuecomment-354106633?

@SimenB I think I might know what is happening - I will comment on that issue directly.


server error talking to controller when launching during a git push based deploy

On a git push from the example-go repo (a buildpack build), the following output results:
ENG000656:example-go aaronschlesinger$ git push deis master
The authenticity of host '[deis.micro-kube.local]:2222 ([<IP_ADDRESS>]:2222)' can't be established.
ECDSA key fingerprint is SHA256:0ZiwB2heubH7jTpArCHN6Mf009u6TtgDDS99ZwUg/KM.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[deis.micro-kube.local]:2222,[<IP_ADDRESS>]:2222' (ECDSA) to the list of known hosts.
Counting objects: 75, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (40/40), done.
Writing objects: 100% (75/75), 18.20 KiB | 0 bytes/s, done.
Total 75 (delta 30), reused 75 (delta 30)
Added host ‘http://<IP_ADDRESS>:9000’ successfully.
mc: <ERROR> Unable to make bucket ‘http://<IP_ADDRESS>:9000/git’. The requested bucket name is not available.
‘wicker-radiator.tar.gz’ -> ‘http://<IP_ADDRESS>:9000/git/home/wicker-radiator:git-5450cbcd/tar’
Total: 2.76 KB, Transferred: 2.76 KB, Speed: 820.28 KB/s
-----> stored tarfile in http://<IP_ADDRESS>:9000/git/home/wicker-radiator:git-5450cbcd/tar
-----> creating builder pod in namespace deis
pod "wicker-radiator-git-5450cbcd" created
Waiting for build to complete...
............................................................
Build complete.
-----> Launching...
2015/12/16 19:29:58 failed retrieving config from controller:
Server Error (500)

To ssh://git@deis.micro-kube.local:2222/wicker-radiator.git
 * [new branch]      master -> master

Note the following:

I was able to successfully push and launch a new app yesterday evening
This push was done on a fresh deis cluster, fresh app
The first two pushes failed, and I saw a traceback in workflow logs (see below), but subsequent pushes seem to succeed.

<IP_ADDRESS> "POST /v2/hooks/build HTTP/1.1" 500 27 "deis-builder"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/register/ HTTP/1.1" 400 43 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "GET /v2/ HTTP/1.1" 401 58 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/auth/login/ HTTP/1.1" 200 52 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/keys/ HTTP/1.1" 201 983 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/keys/ HTTP/1.1" 400 41 "Deis Client v2.0.0-dev"
INFO wicker-radiator: config wicker-radiator-fe4aa59 updated
INFO wicker-radiator: release wicker-radiator-v1 created
INFO [wicker-radiator]: arschles created initial release
<IP_ADDRESS> "POST /v2/apps/ HTTP/1.1" 201 208 "Deis Client v2.0.0-dev"
<IP_ADDRESS> "POST /v2/hooks/push HTTP/1.1" 201 448 "curl/7.39.0"
<IP_ADDRESS> "POST /v2/hooks/config HTTP/1.1" 200 203 "deis-builder"
INFO wicker-radiator: build wicker-radiator-630cd8a created
INFO wicker-radiator: release wicker-radiator-v2 created
INFO [wicker-radiator]: arschles deployed 5450cbc
INFO Pulling Docker image <IP_ADDRESS>:5000/wicker-radiator:git-5450cbcd
INFO wicker-radiator: 500 Server Error: Internal Server Error ("invalid registry endpoint https://<IP_ADDRESS>:5000/v0/: unable to ping registry endpoint https://<IP_ADDRESS>:5000/v0/
v2 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v2/: tls: oversized record received with length 20527
 v1 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v1/_ping: tls: oversized record received with length 20527. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry <IP_ADDRESS>:5000` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/<IP_ADDRESS>:5000/ca.crt")
INFO [wicker-radiator]: 500 Server Error: Internal Server Error ("invalid registry endpoint https://<IP_ADDRESS>:5000/v0/: unable to ping registry endpoint https://<IP_ADDRESS>:5000/v0/
v2 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v2/: tls: oversized record received with length 20527
 v1 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v1/_ping: tls: oversized record received with length 20527. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry <IP_ADDRESS>:5000` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/<IP_ADDRESS>:5000/ca.crt")
INFO wicker-radiator: arschles scaled containers web=1
INFO [wicker-radiator]: arschles scaled containers web=1
DEBUG scale wicker-radiator_v2.web, img wicker-radiator:v2, params {u'num': 1, u'tags': {}, u'aname': u'wicker-radiator', u'version': u'v2', u'memory': {}, u'cpu': {}}, cmd "start web"
DEBUG create wicker-radiator_v2.web, img wicker-radiator:v2, params {u'version': u'v2', u'tags': {}, u'aname': u'wicker-radiator', u'num': 1, u'memory': {}, u'cpu': {}}, cmd "start web"
ERROR wicker-radiator: wicker-radiator_v2.web (scale): u'containerID'
ERROR [wicker-radiator]: wicker-radiator_v2.web (scale): u'containerID'
ERROR Internal Server Error: /v2/hooks/build
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 112, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 57, in wrapped_view
    return view_func(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/rest_framework/viewsets.py", line 85, in view
    return self.dispatch(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/rest_framework/views.py", line 407, in dispatch
    response = self.handle_exception(exc)
  File "/usr/lib/python2.7/site-packages/rest_framework/views.py", line 404, in dispatch
    response = handler(request, *args, **kwargs)
  File "/app/api/views.py", line 403, in create
    super(BuildHookViewSet, self).create(request, *args, **kwargs)
  File "/app/api/views.py", line 129, in create
    return super(BaseDeisViewSet, self).create(request, *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/rest_framework/mixins.py", line 21, in create
    self.perform_create(serializer)
  File "/app/api/viewsets.py", line 21, in perform_create
    self.post_save(obj)
  File "/app/api/views.py", line 410, in post_save
    build.create(self.user)
  File "/app/api/models.py", line 738, in create
    self.app.deploy(user, new_release)
  File "/app/api/models.py", line 466, in deploy
    self._default_scale(user, release)
  File "/app/api/models.py", line 510, in _default_scale
    self.scale(user, structure)
  File "/app/api/models.py", line 296, in scale
    self._scale_containers(scale_types, to_remove)
  File "/app/api/models.py", line 329, in _scale_containers
    **kwargs
  File "/app/scheduler/k8s.py", line 295, in scale
    self.create(name, image, command, **kwargs)
  File "/app/scheduler/k8s.py", line 406, in create
    self._create_service(name, app_name, app_type, data)
  File "/app/scheduler/k8s.py", line 436, in _create_service
    container_id = actual_pod['status']['containerStatuses'][0]['containerID'].split("//")[1]
KeyError: u'containerID'
<IP_ADDRESS> "POST /v2/hooks/build HTTP/1.1" 500 27 "deis-builder"
<IP_ADDRESS> "POST /v2/hooks/push HTTP/1.1" 201 448 "curl/7.39.0"
<IP_ADDRESS> "POST /v2/hooks/config HTTP/1.1" 200 203 "deis-builder"
INFO wicker-radiator: build wicker-radiator-52947c0 created
INFO wicker-radiator: release wicker-radiator-v3 created
INFO [wicker-radiator]: arschles deployed 6b2d12b
INFO Pulling Docker image <IP_ADDRESS>:5000/wicker-radiator:git-6b2d12b8
INFO wicker-radiator: 500 Server Error: Internal Server Error ("invalid registry endpoint https://<IP_ADDRESS>:5000/v0/: unable to ping registry endpoint https://<IP_ADDRESS>:5000/v0/
v2 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v2/: tls: oversized record received with length 20527
 v1 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v1/_ping: tls: oversized record received with length 20527. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry <IP_ADDRESS>:5000` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/<IP_ADDRESS>:5000/ca.crt")
INFO [wicker-radiator]: 500 Server Error: Internal Server Error ("invalid registry endpoint https://<IP_ADDRESS>:5000/v0/: unable to ping registry endpoint https://<IP_ADDRESS>:5000/v0/
v2 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v2/: tls: oversized record received with length 20527
 v1 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v1/_ping: tls: oversized record received with length 20527. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry <IP_ADDRESS>:5000` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/<IP_ADDRESS>:5000/ca.crt")
DEBUG deploy wicker-radiator_v3.web, img wicker-radiator:v3, params {u'version': u'v3', u'tags': {}, u'aname': u'wicker-radiator', u'num': 0, u'memory': {}, u'cpu': {}}, cmd "start web"
INFO wicker-radiator: arschles scaled containers web=1
INFO [wicker-radiator]: arschles scaled containers web=1
<IP_ADDRESS> "POST /v2/hooks/build HTTP/1.1" 200 65 "deis-builder"

is this possibly a registry issue?
INFO [wicker-radiator]: 500 Server Error: Internal Server Error ("invalid registry endpoint https://<IP_ADDRESS>:5000/v0/: unable to ping registry endpoint https://<IP_ADDRESS>:5000/v0/
v2 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v2/: tls: oversized record received with length 20527
 v1 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v1/_ping: tls: oversized record received with length 20527. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry <IP_ADDRESS>:5000` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/<IP_ADDRESS>:5000/ca.crt")

yes, it looks like the docker daemon cannot pull from your registry. Can you output kubectl get svc deis-registry --namespace=deis, as well as sudo cat /etc/sysconfig/docker for us? Your daemon should have something like --insecure-registry <IP_ADDRESS>/8 on there by default so docker can communicate with a registry in a pod.

e.g. https://github.com/kubernetes/kubernetes/blob/master/cluster/vagrant/config-default.sh#L77

@bacongobbler see below.
ENG000656:workflow aaronschlesinger$ kubectl get svc deis-registry --namespace=deis
NAME            CLUSTER_IP   EXTERNAL_IP   PORT(S)    SELECTOR             AGE
deis-registry   <IP_ADDRESS>   <none>        5000/TCP   name=deis-registry   32m
core@micro-kube ~/example-go $ sudo cat /etc/sysconfig/docker
cat: /etc/sysconfig/docker: No such file or directory

For my next trick, I've tried restarting docker after running export EXTRA_DOCKER_OPTS="--insecure-registry <IP_ADDRESS>/8" on the minion. Will update here with result when done.

@bacongobbler same issue. should I try running https://github.com/kubernetes/kubernetes/blob/master/cluster/vagrant/config-default.sh on the minion?

Setting an envvar for your user session won't add it to EXTRA_DOCKER_OPTS. Since it looks like you're on micro-kube, you'll likely have to follow https://coreos.com/os/docs/latest/registry-authentication.html and add it to the user-data that micro-kube adds to the Vagrantfile. From looking at the code it doesn't seem to set up the box with --insecure-registry <IP_ADDRESS>.

should I try running https://github.com/kubernetes/kubernetes/blob/master/cluster/vagrant/config-default.sh on the minion?

That won't work with micro-kube. I'd recommend following the official documentation on getting set up with Vagrant.

demoting as a bug/showstopper. This is a third party issue (micro-kube).

thanks @bacongobbler

Running into this one as well. My k8s came from coreos-kubernetes, running on AWS.

Need to doc the requirements that the k8s cluster be provisioned with insecure registry. in deis/workflow#6 or otherwise

@slack wanna file an issue for that and mark it showstopper?

Good point. If it's more than just one non-official project I'll document it.

Yeah, we're not going to be able to document this for every non-official. Probably just pointing out how it is to be done using the official k8s.io versions is enough.

Actually, this is already documented: https://github.com/deis/workflow/blob/master/docs/src/installing-deis/system-requirements.md#network

Running into this one as well. My k8s came from coreos-kubernetes, running on AWS.

Same here.

From looking at the code it doesn't seem to set up the box with --insecure-registry <IP_ADDRESS>.

fwiw, that is accounted for in the active-dev branch:
https://github.com/krancour/micro-kube/blob/active-dev/user-data#L54

@krancour awesome. thanks for letting me know

I think since we have docs in place and this is not a bug with deis, we can close. thoughts?

I'm interested in knowing how we plan to address this long term.  Do we intend on running secure registries eventually?  If not, this will be a very limiting factor in terms of what k8s clusters we can actually run on.
I opened an issue against coreos-kubernetes, for instance, because @slack and I both ran into this there.  I figured out on my own how to work around this:
https://github.com/coreos/coreos-kubernetes/issues/210
But considering that your average user might not have had the foresight to enable insecure registries at the time they provision their cluster, or they may not want to for security reasons, should we have a more bullet-proof answer to this problem?

Do we intend on running secure registries eventually?

We've talked randomly and informally about coming up with a holistic problem to issuing certificates, and if we had something in place to do so I think we could, and should run secure registries fairly easily. Our minio component, and I think router would also benefit.

your average user might not have had the foresight to enable insecure registries at the time they provision their cluster

I agree. Maybe we should put another sentence or two under https://github.com/deis/workflow/blob/master/docs/src/installing-deis/system-requirements.md#network

should we have a more bullet-proof answer to this problem?

IMO yes, but I don't know what it is. Listing instructions on how to enable insecure registries for every provisioning tool doesn't seem like the answer.

Reopening... I am still encountering the issue described in the OP, and I'm long past any insecure registry issues.

fwiw I'm on a 5-node AWS cluster, and I haven't seen this issue pop up.

Okay, this issue got re-opened, but without any additional information about what the problem is. Please either post logs showing the current error or remove this from the showstopper list.
Are we hunting for a big stack trace or a registry issue?

And again, SSL issues are not showstoppers for alpha. Insecure registry is an SSL issue.

Sorry for not posting additional logs.  I wasn't seeing anything that wasn't in the OP.  I am no longer encountering this now.


Remove NormalizeFilePath() method from CommandLineParameterParser.cs

We could remove NormalizeFilePath() method from CommandLineParameterParser.cs and exclude extra try-catch
to address comment https://github.com/PowerShell/PowerShell/pull/7449/files/777f5eb1e2ee65201356a2f499586dc7c6039422#r207770391

The method is used once and then we call File.Exist() where Path.GetFullPath() is called again.
https://source.dot.net/#System.IO.FileSystem/System/IO/File.cs,119
We could simplify the TryParseSettingFileHelper() method - remove try-catch there (line 429), move the line 574 to TryParseSettingFileHelper()  before File.Exist()

CommandLineParameterParser was refactored for performance and the refactoring makes no sense now.

CommandLineParameterParser was refactored for performance and the refactoring makes no sense now.


Table don't refresh when add new row in push array

We make fresh install and a lot of tests with Vue 3.3.4 and 3.3.7 versions.
We try the versions from vue3-datatable 1.0.1 to the 1.1.3
This tests using only a clean install, and one using Nuxt 3.8 and 3.6.2.
We made server-side and client-side, with no sucess.
We don't get any issue in console from Chrome or console server side.
We inspect the Vue array, and all data is updated, but no in the DOM.
All the test we made, when we push a data to the const with ref, the data don't update on the table in DOM.

Hi Alexandre Brandao,
Can you please provide sample demo code for that, so we can reproduce that easily and solve if any issue.

Hello Mr. Bhavesh Patel,
Yesterday I have some time and restart all my folders projects and clear all my caches in instances.
Then all the issue was solved.
I have a impression that is my instance cache that block some functions to REF components.. etc..
Thanks a lot for your attention and help.
Have a nice day!

Great, Thanks.


This is very cool

https://help.github.com/articles/disabling-issues/

I will reopen issue tracking once the datasets and the code is available.


Initial basic CSS reset completed #2

Basic reset to remove default browser stylings is done according to issue #2
Please review and merge

Thank you!


fix: non wikipedia links don't work

All Wikipedia sister projects are linked using hyperlinks with the class 'extiw,' so a special case has been created to handle them accordingly.
@steezeburger

@steezeburger Does this resolve this issue

@vr-varad which formatter did you use? I will probably add biome to the project soon and use its default linting and formatting rules.

@steezeburger I am using just prettier.


PNP tsconfig references resolution fix

Fixes https://github.com/yarnpkg/berry/issues/3231 by implementing the fix suggested in this comment - https://github.com/microsoft/TypeScript/pull/35206#discussion_r683139533
Also slightly makes it easier for nx repositories to adopt yarn 3 (https://github.com/nrwl/nx/issues/2386)
CC: @arcanis

cc @andreialecu as the author of that patch

@andreialecu your review on this would be much appreciated. This is trying to address breaking scenarios for monorepos where tsconfig files and references are deep within the root of the workspace.
Thank you.

Interesting. I'm using yarn 3 and project references but I don't remember noticing anything wrong.
How does the problem manifest exactly?

@andreialecu here is an example repo where this can be reproduced - https://github.com/sushruth/berry-issue
Especially when the tsconfig.json and referenced project's tsconfig file are within the same workspace but deep in the directory structure of the application.
This is the error we see in vscode on the tsconfig.json that references other project tsconfigs -

where the path inferred is clearly incorrect. and hence further intellisense depending on that reference fails.

Hey @sushruth I just took this for a test spin.
Unfortunately all it does is to essentially undo #4 because all paths going through that function are absolute.
You can verify in my original repro at: https://github.com/andreialecu/repro-yarn-pnp-composite which I just update to yarn 3.
Run ./test-refs.sh or look inside packages/app/src/index.ts. It should NOT show this:

But with this patch, the behavior above happens.

To clarify, when did you first see this problem occuring? Did the behavior or pnpApi.resolveToUnqualified() change recently? Perhaps the problem lies there?

The problem appears to be that the current patch resolves the root of the locator but in the repro provided in https://github.com/yarnpkg/berry/issues/3231 the reference isn't pointing to a folder (workspace root) so we're effectively turning the reference ./tsconfig.app.json into ../../

@andreialecu Those errors seem to be expected behavior in yarn 2 with TS 4.3.5 - https://github.com/sushruth/repro-yarn-pnp-composite

@andreialecu Those errors seem to be expected behavior in yarn 2 with TS 4.3.5 - sushruth/repro-yarn-pnp-composite.

Not sure I understand what you mean. The behavior is not expected, because it works properly without PnP, or when virtuals are not involved, so it should definitely work. It's the most idiomatic way to use project references as well. The patch I made in #4 fixed that.
The change made by this PR simply undoes it which incidentally makes your scenario work.

I'm a bit confused by how the setup in your repro translates into a real world scenario because I'm not sure why your tsconfig would look like that in practice. It seems a bit odd. :)
Even so though, I see that your repro works properly with node_modules, so there's definitely a bug in there somewhere, but this fix isn't the correct one.

Can you clarify if this is a regression and when did it start appearing? Did yarn 3 introduce it or TS 4.3.5? What's the last combo of versions when it was working?

@andreialecu Turns out I was wrong. I just realized that I had completely ignored the fact that your repro repo is a yarn workspace monorepo. Now I realize what might be the actual issue that was breaking my scenario (mostly for all nx repos for reference)
I think it might actually be that the current typescript-patch is not considering the scenario when references are files and not folders with tsconfig.json in them.

Can you clarify if this is a regression and when did it start appearing? Did yarn 3 introduce it or TS 4.3.5? What's the last combo of versions when it was working?

basically upgrading to the latest typescript-patch broke all nx monorepos due to this issue. It was not necessarily introduced in TS or Yarn3.
I am now working on a different solution for this issue. Thanks @andreialecu.

I think it might actually be that the current typescript-patch is not considering the scenario when references are files without a workspace and not workspace folders with tsconfig.json in them.

Exactly, that's what I was hinting at in https://github.com/arcanis/TypeScript/pull/10#issuecomment-894769332. The patch needs to be changed to preserve the part of the path that comes after the packageLocation but still run through the same code path

@merceyz that sounds right. One way I though about this is - any path that directly resolved to be from the root workspace would mean PnP may not need to handle the virtual directory. I made a change to reflect that. What do you think about the current diff of this PR?

@andreialecu pinging for your attention on latest update to this PR.

@merceyz @andreialecu @arcanis  pinging to bring attention to this

Hey! I'm sorry I'm a little lost 😅 can you make a quick summary of why this is needed? I'm worried about adding a special case just for workspace:., I'm not sure why we need that.

What I said in https://github.com/arcanis/TypeScript/pull/10#issuecomment-894769332 still stands, I pushed the generic fix here https://github.com/merceyz/TypeScript/commit/3f4e1516e0a956e1e0d46d9caf2a1f896fb77aaa, will update https://github.com/yarnpkg/berry/pull/3297 to include it


Profile description and interest tags not showing in profile edit sections

When I try to edit Profile description orr interest tags, they dont show.


Improve MissingRequiredArguments

MissingRequiredArguments is renamed to MissingRequiredArgument (breaking change).
CommandError is now raised instead of MissingRequiredArgument(s) when self or ctx is missing.
MissingRequiredArgument now has a param attribute with the missing argument's inspect.Parameter.
The message for MissingRequiredArgument has been changed to use the parameter name instead of the command name. The command name can still be obtained through the Context parameter in event_command_error.

[X] Tests have been conducted on the PR
[X] Docs have been added / updated

Thanks again. :+1:


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Codecov Report

Merging #453 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #453   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          29     29
=====================================
  Hits           29     29

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 63acf31...5edcb57. Read the comment docs.

Coverage remained the same at 97.619% when pulling 5edcb57bbe14f09913ae6b943a09ba088c9ef876 on template-sync-1 into 63acf312d7e1e73e0f211e2ec6a52e039b6e3e47 on master.


Open source Opus::Enum

Problem

Sorbet has support for declaring enums. The runtime component is implemented in Stripe's monorepo, not in sorbet-runtime.

This is done, right?

Yup, it's T::Enum.
Thank you for finding!


[DI] Fix layout extracting issues

This PR:

Fixed a customer issue(#35912 ) about not able to extract complete data by following the code in sample_analyze_layout.py. Here I uploaded the docx file that we used to reproduce the customer issue, and added code for extracting paragraphs data so that customers will see "complete" data in output.
"word" should get from page.words.

API change check
API changes are not detected in this pull request.

@esther-tsai Can you help to review? Thanks

/azp run python - documentintelligence - ci


[BUGFIX!!!!!] TO ALL WHOSE EXE'S WONT OPEN EZ FIX!

Its most likely that its not opening because you moved the game to other harddrive or else using steam.
FIX: Move the game to your internal storage. The exe expects the normal (C) gamepath. It crashed before for me, now by moving from my external to my internal harddrive, it works
thank me later ;D
Enjoy cs2!

The application does not have the CS2 path hardcoded into it. As it can be seen on ApplicationSetup.cs the app looks on all the library folders a user has and then tries to find the game in them.

it did fix it for me tho


A command line argument to mark a directory as trusted (follow-up to issue #191772)

I would be very interested in having the feature requested in issue #191772. Is there any hope to have a way of adding trusted folder through a command?

Alternatively, if you would tell me where the info is stored, most likely inside the .config/Code folder, I could write a few lines of script to modify the proper file so that a specific folder is trusted without asking the students to add it manually. To give a bit of context, we are using the Lean4 extension of VSCode to do some Lean during labs for first year university students. Since, for many, it is the first time they use VSCode I would want them to be able to start working on their lab right after executing a script that sets up the working environment for them.

Sorry to insist but I created this issue more than a month ago and I am yet to receive a reply.

@Boutry, at the moment we have no plans on enabling the capability to control the list of trusted workspace through the VS Code CLI. It seems to me that this is a tightly controller environment so what you can do is setup a VS Code profile in which workspace trust is disabled.


Add 'Add Block' menu item to area tab

#1915 This is an oddly brief change that add support for an "Add Block" menu item in area tabs.

This is an elegant solution to this issue and works nicely. One thing we're
gonna need, though: we do have pass the area handle into the add panel. we
don't need to pass it out and act on it, but we do need to use it to limit
block types by permission.
$area = \Area::getByHandle($page, 'Area Handle');
$permissions = new \Permissions($area);
if ($permissions->canAddBlockType($blocktype)) {
...
}
On Mon, Mar 30, 2015 at 2:34 PM, Korvin Szanto<EMAIL_ADDRESS>wrote:

#1915 https://github.com/concrete5/concrete5-5.7.0/issues/1915 This is
an oddly brief change that add support for an "Add Block" menu item in area
tabs.
You can view, comment on, or merge this pull request online at:
https://github.com/concrete5/concrete5-5.7.0/pull/2128
Commit Summary

Add 'Add Block' menu item to area tab

File Changes

M web/concrete/elements/block_area_footer.php
https://github.com/concrete5/concrete5-5.7.0/pull/2128/files#diff-0
(9)
M web/concrete/js/build/core/app/edit-mode/area.js
https://github.com/concrete5/concrete5-5.7.0/pull/2128/files#diff-1
(10)
M web/concrete/js/build/core/app/edit-mode/blocktype.js
https://github.com/concrete5/concrete5-5.7.0/pull/2128/files#diff-2
(27)
M web/concrete/js/build/core/app/edit-mode/duplicateblock.js
https://github.com/concrete5/concrete5-5.7.0/pull/2128/files#diff-3
(6)
M web/concrete/js/build/core/app/edit-mode/editmode.js
https://github.com/concrete5/concrete5-5.7.0/pull/2128/files#diff-4
(18)
M web/concrete/js/build/core/app/edit-mode/stackblock.js
https://github.com/concrete5/concrete5-5.7.0/pull/2128/files#diff-5
(4)
M web/concrete/js/build/core/app/panels.js
https://github.com/concrete5/concrete5-5.7.0/pull/2128/files#diff-6
(14)

Patch Links:

https://github.com/concrete5/concrete5-5.7.0/pull/2128.patch
https://github.com/concrete5/concrete5-5.7.0/pull/2128.diff

—
Reply to this email directly or view it on GitHub
https://github.com/concrete5/concrete5-5.7.0/pull/2128.

I added a commit that makes Concrete.BlockType check against the list of acceptable block types and hide itself if it isn't allowed.

Hah sweet. I forgot about the data attribute with the block type handles, which I added myself about a million years ago.


HDDS-8245. Info log for keyDeletingService when nonzero number of keys are deleted.

What changes were proposed in this pull request?
The directory deleting service has an info log that displays a summary of the run when some amount data is deleted. The key deleting service only logs this at the debug level. It should have an info log that prints a summary of the number of keys deleted if it is nonzero.
For reference, the corresponding line in directory deleting service is here
What is the link to the Apache JIRA
HDDS-8245
How was this patch tested?
No tests added since this is a simple logging change.

Thanks for the review @jojochuang


Update QEDm conformance resources to R4

Do not merge until after committee review

ITI has reviewed and approved from their perspective this branch. PCC should approve or defer to ITI.


[C/CPP]: NP Completeness

Description
Description of NP Complement
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


add: .vscode settings folder to .gitignore

This adds the .vscode folder to the .gitinore file in order to ignore local settings when this project is opened by VsCode and you have some local changes that automatically write settings to it

Thanks for picking up on this and submitting the PR!


[Feature Request] Auto-approve unreleased movies

Description
It would be nice to have the option for users to auto approve unreleased movies
Desired Behavior
Any unreleased movies requested by users with this setting on would be directly monitored
Additional Context
I hope this is a typical use case, as settings are still quite light in Jellyseerr
Code of Conduct

[X] I agree to follow Overseerr's Code of Conduct

There is auto-approval already. Does it not work? You need to make sure you give that permission to the users

@Fallenbagel I don't want them to be able to have just any movie auto-approved, only unreleased ones, if it makes sense


@ #404 | should add dev-setup for teracy-dev

connect #404

@hoat le please help me check this pr!

@phuonglm please review

@hoatle please help me check this PR!

assigned to @phuonglm

This PR is ok for me, @hoavt please review https://github.com/teracyhq/dev/pull/407/files#diff-205ebbec5c138cdbef078a3f0edcd650 for me.

@hoavt i updated! please help me check this PR


CB-5353 Add runtime to datalake

The code looks ok, although what I have seen is:

the template picker on DataHub is greyed out
the DataHub templates are not filtered out


[T4A2][F10-B2] Shi Xiyue

Ready for review

@shixiyue : Some comments added. Please close the PR after reading comments


Updated all electron calls for proper interactions

With the latest electron update, there were a few issues with the ipc calls and misc require.
I went ahead and cleaned a lot of it out, which hopefully isn't wasted efforts.
Signed-off-by: French Ben<EMAIL_ADDRESS>

@jeffdm PTAL

LGTM, though travis is failing


Render all carousel images

This reverts #1835 😬 That PR was fine, it's just that to really squash this bug I want to try a different approach. This PR achieves the same effect of preloading all carousel images, but while also rendering all images.
After talking to @alloy I became convinced that preloading alone would not solve the issue we have seen, and that the problem is almost certainly FlatList which has been allegedly quite buggy historically, especially around whether or not lazily-rendered items appear.
The evidence I have for this is that both times when this kind of bug has appeared and I have seen it with my own eyes, the loading 'placeholder' background was not being show. It was just white. If this issue were caused by not prefetching images, we would expect to see a grey box with a loading spinner instead of a pure white background.
So it seems that FlatList is fine with rendering N items up-front, but occasionally chokes when pulling in more items as the user scrolls. It will be impossible for me to debug FlatList when I can't reproduce the issue locally and other people can't seem to reproduce it on-demand, so instead this PR introduces a workaround.
As already mentioned, that workaround is simply rendering all images up front. We have the luxury of being able to do that since the images are quite small, and we could get up to about 30 thumbnails before we need to even think about memory usage.
Network usage is a different thing. Here we set the first image to be a 'high pritority' download, which pushes it to the front of the SDWebImage download queue. That should help with the artwork page feeling snappy, but not as much as if we could force the images to download sequentially.
Another minor issue is that image downloads can't be cancelled with our current implementation of OpaqueImageView so if the user is on a bad connection and is navigating between pages faster than the thumbnails can load, they'll build up a queue of image downloads which will further hurt their network performance. This was an issue with the previous approach too. I'm not sure if SDWebImage supports cancelling downloads but if it does we should probably update OpaqueImageView to take advantage of it.
#skip_new_tests
#trivial

Warnings

:warning:
Missing Test Files:

src/lib/Components/OpaqueImageView/__tests__/OpaqueImageView-tests.tsx

If these files are supposed to not exist, please update your PR body to include "#skip_new_tests".

  Generated by :no_entry_sign: dangerJS

Makes sense, this looks good to me and good call on the high priority 👍
As for your question, SDWebImage can cancel downloads.


New version: Manifolds v0.3.12

Registering package: Manifolds
Repository: https://github.com/JuliaManifolds/Manifolds.jl
Created by: @kellertuer
Version: v0.3.12
Commit: 54e55eed118bf479a97ddacb6146257b534f6b76
Reviewed by: @kellertuer
Reference: https://github.com/JuliaManifolds/Manifolds.jl/commit/54e55eed118bf479a97ddacb6146257b534f6b76#commitcomment-42650982

It was just a typo and is fixed in #21848 (sorry, that that's a new PR), so this can be closed.


Model event doesn't get triggered during tests

Laravel Version: 5.4.25
PHP Version: 7.1.2-3
Database Driver & Version: sqlite :memory:

I came across a strange problem where model does not call the updated event on update.
All other models work fine, if model is being injected to the controller's method, but when model is instantiated manually from within the controller and then updated - it fails - but only via cli (during tests) - it works fine over http.
Here's the scenario:
Setting model
<?php

namespace App\Models;

use App\Events\SettingUpdated;

use Illuminate\Database\Eloquent\Model;

class Setting extends Model
{
    protected $table = 'settings';

    protected $fillable = [
        'name',
        'address',
        'telephone',
        'email',
        'facebook_app_id',
        'twitter_username',
        'script_header',
        'script_footer'
    ];

    protected $events = [
        'updated' => SettingUpdated::class
    ];
}

Controller method
public function update(UpdateSettingRequest $request) : JsonResponse
{
    Setting::first()->update($request->data());

    return new JsonResponse([
        'message' => 'Record has been updated successfully'
    ]);
}

Test
/**
 * @test
 */
public function update_triggers_update_event()
{
    Event::fake();

    $setting = factory(Setting::class)->create();

    $data = $setting->toArray();
    $data['script_header'] = '<script></script>';

    $this->postAjax(
            route('admin.settings.update'),
            $data
        )
        ->assertStatus(Response::HTTP_OK)
        ->assertExactJson([
            'message' => 'Record has been updated successfully'
        ]);

    Event::assertDispatched(
        SettingUpdated::class,
        function(SettingUpdated $event) use($setting) {
            return $event->setting->id === $setting->id;
        }
    );
}

The output of the tests
1) Tests\Feature\Admin\SettingTest::update_triggers_update_event
The expected [App\Events\SettingUpdated] event was not dispatched.
Failed asserting that false is true.

/Users/Sebastian/Code/cms/vendor/laravel/framework/src/Illuminate/Support/Testing/Fakes/EventFake.php:28
/Users/Sebastian/Code/cms/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:221
/Users/Sebastian/Code/cms/tests/Feature/Admin/SettingTest.php:146

On the other hand - another model, which works just fine:
Page model
class Page extends Model
{
    protected $table = 'pages';

    protected $fillable = [
        'is_draft',
        'is_locked',
        'is_active',
        'slug',
        'name',
        'body',
        'meta'
    ];

    protected $events = [
        'updated' => PageUpdated::class,
        'deleted' => PageDeleted::class,
    ];
}

Controller method
public function update(Page $page, UpdatePageRequest $request) : JsonResponse
{
    $page->update($request->data());

    return new JsonResponse([
        'message' => 'Record has been updated successfully'
    ]);
}

Test
/**
 * @test
 */
public function update_triggers_update_event()
{
    Event::fake();

    $page = factory(Page::class)->create([
        'slug' => 'services'
    ]);

    $data = $page->toArray();
    $data['slug'] = 'about-us';

    $this->postAjax(
            route('admin.pages.update', $page->id),
            $data
        )
        ->assertStatus(Response::HTTP_OK)
        ->assertExactJson([
            'message' => 'Record has been updated successfully'
        ]);

    Event::assertDispatched(
        PageUpdated::class,
        function(PageUpdated $event) {
            return $event->page->slug === 'about-us';
        }
    );
}

Is that how it's suppose to behave or is it something I do?

What is postAjax() can't seem to find this method anywhere.

public function testBasicTest()
{
    Event::fake();

    $response = $this->get('/');

    Event::assertDispatched(
        TestEvent::class
    );
}

Route::get('/', function () {
    User::first()->update([
        'name' => str_random()
    ]);

    return view('welcome');
});

This works for me.

postAjax() is just a simple post() request with XMLHttpRequest added:
/**
 * Post ajax call.
 *
 * @param string $url
 * @param array $data
 * @param array $headers
 * @return \Illuminate\Foundation\Testing\TestResponse
 */
protected function postAjax(string $url, array $data = [], array $headers = []) : TestResponse
{
    return $this->post(
        $url,
        $data,
        $this->mergeHeaders($headers)
    );
}

/**
 * Merge headers.
 *
 * @param array $headers
 * @return array
 */
private function mergeHeaders(array $headers = []) : array
{
    return array_merge(
        [
            'HTTP_X-Requested-With' => 'XMLHttpRequest'
        ],
        $headers
    );
}

@sebastiansulinski I still can't replicate your issue, check my comment above, the code there works for me, the event is fired.

Setting::first()->update($request->data());

This doesn't feel right to me, the failure you see might be because of:
function(SettingUpdated $event) use($setting) {
            return $event->setting->id === $setting->id;
        }

Remove the callback or make sure you're comparing the IDs correctly.

Thanks @themsaid. The callback is fine - I've no idea what's happened, I just tried to run the code again after leaving it for a few hours, and guess what - now it passes! I've spent literally hours trying to figure out what might be causing it to fail and out of nowhere this.
Anyway - thanks very much for looking into it - appreciate it.

¯_(ツ)_/¯


[Feature Request] Accessibility support?

I'm not sure how easy this would be for an immediate-mode UI, but I thought I'd ask. There is a library called AccessKit that simplifies this task a lot and abstracts away the platform-specific things you'd need to normally use. The API documentation is mostly in Rust (as the library is written in Rust) but there are C examples. I can help if we can figure out the problem of "it's an immediate-mode UI", but it would be amazing if this could be done. A prerequisite is issue #385 as it will be a requirement for screen readers and individuals who cannot use the mouse.

@ethindp I'm afraid this is really out-of-scope for raygui project. AccessKit seems to be a lower level library, like GLFW (that is integrated into raylib).

@raysan5 May I ask why such a critical feature like this would be out-of-scope? AccessKit might not be the most high-level library but it's much higher level than the OS accessibility abstractions (UIA, AT-SPI2, whatever MacOS implements).

@ethindp Mostly two reasons:

raygui is a very small self-contained library, I don't want to add an humungus external dependency.
I can't maintain it.

Thanks for your comprehension.

@ethindp Note that raygui is a free and open source project. If you think that feature is crucial for your target project, you can fork it and implement it yourself.

Ah okay, thank you for your explanations.


Add Allow HTTP headers

This pull request sets the Allow HTTP response headers with the methods that this service supports.

👍 :shipit:


netty close client connection

Netty version: 5.0.0.Alpha2
use this for server test
bossGroup = new NioEventLoopGroup(1);
workerGroup = new NioEventLoopGroup();
ServerBootstrap bootstrap = new ServerBootstrap();
bootstrap.option(ChannelOption.SO_BACKLOG, 1024);
bootstrap.option(ChannelOption.SO_REUSEADDR, true);
bootstrap.option(ChannelOption.TCP_NODELAY, true);
bootstrap.option(ChannelOption.SO_KEEPALIVE, true);
bootstrap.group(bossGroup, workerGroup).channel(NioServerSocketChannel.class).handler(new LoggingHandler(LogLevel.INFO)).childHandler(new ChannelInitializer() {
}
client use asynhttpclient
client send async request to this server ，but sometime server close the connection
and the client get the  “java.io.IOException: Remotely closed” exception
at the same time ,i find LoggingHandler which log the message  lose same data
for example : client send 100 request  and get 3 “java.io.IOException: Remotely closed” exception
and the LoggingHandler only log 97 "RECEIVED" message in the channelRead method

maybe related to issue: https://github.com/netty/netty/issues/3709#issuecomment-98141356

@bobwenx Could be. The client is AHC but the user didn't provide enough information, like the version. There was a bug that could produce such failure, but it was fixed and release a month ago.

i find the red frame don't deal the real ，for example client sent 150 request but in the red frame only get the 137

@rjbhewei Do you 150 frames on the server side with Wireshark?

AHC version

com.ning
async-http-client
1.9.17

use  like this

AHC use 5 thread and one thread loop send async http request  30 count

i get the red frame deal num used intellij breakpoints like this

@rjbhewei A Java debugger won't tell you what's on the wire.
Then, please read my above comment: there was an issue that was fixed in AHC 1.9.18 (latest is 1.9.20)!

but the LoggingHandler only 137 same with the debugger

So what? The client only sent 137 requests because of the mentioned issue.

my project server use netty5  which version is 5.0.0.Alpha2
i use AHC test the server  for pressure test
i use 10 thread and one thread loop 10000 ,i find the netty5 server sametimes had same request, and take exception
so AHC config builder.setMaxRequestRetry(0); find  "│java.io.IOException: Remotely closed" exception

client sent 150 and only get 137

You're getting me nuts. Giving up. Bye.

issue example is client send 100  and server get 97
my poject is client send 10 10000
and just now i said client send 530 and server get 137

@rjbhewei please can you move this to the AHC project as this looks more like an AHC bug (if any) then a Netty one.

@normanmaurer   https://github.com/AsyncHttpClient/async-http-client/issues/872 is close by @slandelle
he said mybe server bug  and you said is AHC client bug
both issues are closed

@normanmaurer @rjbhewei No, I first said that this was a possible normal HTTP behavior because I assumed you properly did some basic checks before reporting an issue:

check latest version
check release notes

When you finally provided the version of AHC you were using, I told you here and in the issue you opened in AHC that it WAS a AHC that has already been fixed and that you have to upgrade. Period.

@slandelle  check out the latest AHC (2.0.0-SNAPSHOT) version ,the bug still appear

i will still find why tomorrow


Bump Facebook Business SDK version

After receiving a notice that Facebook will begin deprecating any requests from versions 14 and under beginning January 25 2023, this should be updated asap to remain current.

Thanks, @zacksmash. Do you know the impact of this and if the API will still function as it was before? I have not tested with latest facebook API.

@timothymarois
So, I just ran through all the basic methods for Facebook (fetch() and reports()) and didn't receive any errors. I also typically use this package in a more custom way, which also returns the proper results that I'm expecting.
I would say it all looks good from my end!

@timothymarois
Just wanted to ping again on this. That date is creeping up, and I wanted to see if you had a chance to review and get this merged.
Thanks!

@zacksmash I am sorry about the delay on this one. Question for, I'm am busy with many other projects these days, and since the google deprecation, I haven't continued this development. Do you want access to push changes to continue this?

@timothymarois Yeah, if there's anyway for me to collaborate with you on this repo, I'd be more than happy to. I'm using this every day, so I'm pretty familiar with the nuts and bolts of it.


Will restclient use CONNECT when talking to a https endpoint via a proxy?

I am trying to configure proxy with restclient and the endpoint that I am trying to access is https, the docs for the proxy says something like this:

You can access HTTPS services via the HTTP proxy whilst still getting full SSL/TLS security. When you make a request via the proxy to an HTTPS endpoint your client should transparently issue a CONNECT request rather than a basic GET request.
On receipt of this CONNECT request the proxy will open a tunnel between your client and the endpoint, allowing your client to negotiate a standard SSL session with the endpoint. Once negotiated all traffic sent between your client and the endpoint will be encrypted as if you had connected directly with them.

So my doubt is will the restclient do this automatically? How can I go about doing this?
I am sorry if I am being naive. Thanks.

Yes, rest-client uses Ruby Net::HTTP under the hood, which will automatically issue a CONNECT request for HTTPS over an HTTP proxy.
You can set this by setting the environment variable https_proxy or setting RestClient.proxy.
Testing this by running a fake local proxy:
$ nc -v -l 5000
Listening on [<IP_ADDRESS>] (family 0, port 5000)

>> RestClient.proxy = 'http://localhost:5000'
>> RestClient.get('https://example.com/')

The netcat server will now show the CONNECT request
Connection from [<IP_ADDRESS>] port 5000 [tcp/*] accepted (family 2, sport 42916)
CONNECT example.com:443 HTTP/1.1
Host: example.com:443


Edit Command Bug

Incorrect error message: for index > list size + 1

Block other commands: for index = list size + 1

Edit IssueList.length() + 1, in this case 2. The command won't execute and enter seems to be "switch to next line" instead a ENTER command. Therefore all the following command won't be executed after edit 2 ... is entered.
I circled some parts which may be relevant. I didn't test IssueLevel but based on the code, the same problem may occur.

thank you, fixed will pushed with my next PR


IXP DB support to collect data from peers available at an IXP

The IXP database https://ixpdb.euro-ix.net/en/ provides a lot of information about peers available from an IXP. The data is more complete compared to PeeringDB as the data is maintained by the IXP instead of individual peers.
IXP DB also provides an API.

Do you know if IXP DB's API is freely available like PeeringDB's?

Yes, the API is freely available: https://api.ixpdb.net/docs/On 28 Aug 2021 17:42, Guillaume Mazoyer @.***> wrote:
Do you know if IXP DB's API is freely available like PeeringDB's?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.


Tooltips for tags on hover

Hi Ben,
I have been using ng-tags input for sometime, I would like to add tooltips for it when I hover on tags that are added. Can you let me know how to do it? And help would be appreciated.
Thanks,
-/Sammi

Why don't you just use custom tags template ?
Like this : https://plnkr.co/edit/bz1CtAHrnvjJxucRP4GP


Question about asynchronous requests

At the time of asynchronous communication, do you have registration process inside fulfilled or after the pool of requests completed?
$client = new Client();
$requests = function ($total) {
$uri = 'http://<IP_ADDRESS>:8126/guzzle-server/perf';
for ($i = 0; $i < $total; $i++) {
yield new Request('GET', $uri);
}
};
$pool = new Pool($client, $requests(100), [
'concurrency' => 5,
'fulfilled' => function ($response, $index) {
// Is it better to have registration process here?
},
'rejected' => function ($reason, $index) {
// this is delivered each failed request
},
]);
// Initiate the transfers and create a promise
$promise = $pool->promise();
// Force the pool of requests to complete.
$promise->wait();
// Is it better to have registration process here?

It's not clear from the description, what "registration process" stands for.
If you need to do something with the responses, you have only one place to do that: in the 'fulfilled' callback. If you don't rely on the response data and want to do something in the end, after the pool is over, do it after ->wait().
P.S. IMO StackOverflow is suited better for such type of questions.

StackOverflow is suited better for such type of questions.


make the openshift / local deployment easier to customize

At the moment the deployment script deploys kafka and other component from predefined versions and there is for example no way to attach Drogue to an already exisiting kafka installation.
This is an issue because in terms of CRD on K8S it could conflict with the currently installed strimzi CRD
Same goes for keycloak or grafana

It is possible to do that. You can choose between using an existing Kafka installation elsewhere, deploy Strimzi during the default installation, or re-use an existing Strimzi installation:
https://github.com/drogue-iot/drogue-cloud-helm-charts/blob/0c947c10afa82c462a5da15861e3b221fbd003c4/charts/drogue-cloud-core/values.yaml#L314-L316
However, we might not have documented that well enough (at all). Same goes for Keycloak and Grafana.
With Keycloak the issue however is, that Keycloak CRDs don't live up to their API versioning. So it just breaks between releases. Which means you need to disable the Keycloak installation we provide and do your own. Which also works:
https://github.com/drogue-iot/drogue-cloud-helm-charts/blob/0c947c10afa82c462a5da15861e3b221fbd003c4/charts/drogue-cloud-core/values.yaml#L221-L222


IndexOutOfRangeException on calling WriteLineFormatted()

So if you pass List<> as args argument, you'll get the exception.
It can be easily fixed using List<>.ToArray(), but anyway consider to take a look at this

I think this could be improved upon as a whole, I'd be interested in taking on some refactoring to allow more dynamic and generic uses. ConTabs is a great example of such.

Thanks for reporting this -- @Chandler-Davidson has just made a contribution that allows for any implementor of IEnumerable to be supplied to WriteLineFormatted.  Thanks to both of you!


#495 Add x/act integration test for adding/removing owners

Fixed import of spaces from Genesis.
Generated a new snapshot with many users.
Implemented an integration test.

Notes: I found out that the rule must be in the format any(2, warden.space.owners) (including the warden. prefix). That wasn't obvious, even after reading the documentation.
https://github.com/warden-protocol/wardenprotocol/issues/495

Summary by CodeRabbit

New Features

Introduced a snapshot setup for multiple user accounts.

Bug Fixes

Improved error handling during space owners update in the Keeper struct.

Tests

Added a new test scenario for owner approval actions within a permission framework.

after reading the documentation

Does format mentioned somewhere in docs? If it is so, I think it better to edit it then

after reading the documentation

Does format mentioned somewhere in docs? If it is so, I think it better to edit it then

It looks like my bad actually..

It looks like my bad actually..

i agree that it's not particularly clear from the docs how to use shield in general, and what variables are available, we'll need to improve it

thanks, looks good to me!
please merge it using "squash and merge", or alternatively you can manually edit your commits (I think the minimum number is two: one for fixing genesis import, one for adding test+snapshot) and then you can "rebase and merge" 🙌

It looks like squash isn't enabled here


Installation complete but flynn command not found.

The installation logs show as bellow:
===> 10:07:08.674 installing runtime dependencies
===> 10:07:08.676 running "apt-get install --yes aufs-tools iptables libvirt-bin ubuntu-zfs"
Reading package lists... Done
Building dependency tree
Reading state information... Done
iptables is already the newest version.
aufs-tools is already the newest version.
libvirt-bin is already the newest version.
ubuntu-zfs is already the newest version.
The following packages were automatically installed and are no longer required:
  libjansson4 sqlite3 uwsgi-core
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 105 not upgraded.
===> 10:07:09.404 downloading flynn-host binary to tmp dir
===> 10:09:36.954 verifying flynn-host binary checksum
===> 10:09:36.999 moving verified flynn-host binary to /usr/local/bin
===> 10:09:37.003 running "gunzip /tmp/tmp.RrqFFY1NZJ/flynn-host.gz"
===> 10:09:37.325 running "mv /tmp/tmp.RrqFFY1NZJ/flynn-host /usr/local/bin/flynn-host"
===> 10:09:37.341 running "chmod +x /usr/local/bin/flynn-host"
===> 10:09:37.346 downloading Flynn components
10:09:37.520270 host.go:122: tuf: no root keys found in local meta store
===> 10:09:37.524 installing Upstart job
cp: cannot stat ‘/etc/flynn/upstart.conf’: No such file or directory
===> 10:09:37.589 installation complete!
root@i-aoggstf5:~# flynn
flynn: command not found
root@i-aoggstf5:~# flynn-host
usage: flynn-host [-h|--help] <command> [<args>...]

@jeffkit was this the first time you ran the script? If not, what was the previous output?

The last 4 lines of log is the same, no matter the first time or the second time, third time.  After first time, the installation is more quickly.
My OS is ubuntu 14.04. install script is:
bash < <(curl -fsSL https://dl.flynn.io/install-flynn)

@jeffkit do you by any chance have the complete output from the first time you ran the installer? It looks like the first install failed in some way and left your system in an odd state where further attempts will also fail. Seeing the complete output of the first install will help me understand what went wrong.

@lmars OK, I just copy the complete output and paste it here, I found some strange log like:
W: Duplicate sources.list entry http://ppa.launchpad.net/saltstack/salt/ubuntu/ trusty/main i386 Packages (/var/lib/apt/lists/ppa.launchpad.net_saltstack_salt_ubuntu_dists_trusty_main_binary-i386_Packages) W: You may want to run apt-get update to correct these problems
I am not sure if it is the reason fail to install.
 Done
W: Duplicate sources.list entry http://ppa.launchpad.net/saltstack/salt/ubuntu/ trusty/main amd64 Packages (/var/lib/apt/lists/ppa.launchpad.net_saltstack_salt_ubuntu_dists_trusty_main_binary-amd64_Packages)
W: Duplicate sources.list entry http://ppa.launchpad.net/saltstack/salt/ubuntu/ trusty/main i386 Packages (/var/lib/apt/lists/ppa.launchpad.net_saltstack_salt_ubuntu_dists_trusty_main_binary-i386_Packages)
W: You may want to run apt-get update to correct these problems
===> 14:45:09.027 installing runtime dependencies
===> 14:45:09.029 running "apt-get install --yes aufs-tools iptables libvirt-bin ubuntu-zfs"
Reading package lists... Done
Building dependency tree
Reading state information... Done
iptables is already the newest version.
aufs-tools is already the newest version.
aufs-tools set to manually installed.
The following packages were automatically installed and are no longer required:
libjansson4 sqlite3 uwsgi-core
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
augeas-lenses bridge-utils dkms ebtables iproute libaugeas0
libboost-system1.54.0 libboost-thread1.54.0 libnetcf1 libnvpair1
libpciaccess0 librados2 librbd1 libuutil1 libvirt0 libx86-1 libxen-4.4
libxenstore3.0 libxml2-utils libyajl2 libzfs2 libzpool2 mountall pm-utils
spl spl-dkms vbetool zfs-dkms zfs-doc zfsutils
Suggested packages:
augeas-doc debhelper augeas-tools qemu-kvm qemu radvd lvm2 cpufrequtils
radeontool zfs-auto-snapshot samba-common-bin nfs-kernel-server
zfs-initramfs
The following NEW packages will be installed:
augeas-lenses bridge-utils dkms ebtables iproute libaugeas0
libboost-system1.54.0 libboost-thread1.54.0 libnetcf1 libnvpair1
libpciaccess0 librados2 librbd1 libuutil1 libvirt-bin libvirt0 libx86-1
libxen-4.4 libxenstore3.0 libxml2-utils libyajl2 libzfs2 libzpool2 pm-utils
spl spl-dkms ubuntu-zfs vbetool zfs-dkms zfs-doc zfsutils
The following packages will be upgraded:
mountall
1 upgraded, 31 newly installed, 0 to remove and 105 not upgraded.
Need to get 8,048 kB of archives.
After this operation, 42.3 MB of additional disk space will be used.

Preparing to unpack .../mountall_2.53-zfs1_amd64.deb ...
Unpacking mountall (2.53-zfs1) over (2.53) ...
Selecting previously unselected package libboost-system1.54.0:amd64.
Preparing to unpack .../libboost-system1.54.0_1.54.0-4ubuntu3.1_amd64.deb ...
Unpacking libboost-system1.54.0:amd64 (1.54.0-4ubuntu3.1) ...
Selecting previously unselected package libboost-thread1.54.0:amd64.
Preparing to unpack .../libboost-thread1.54.0_1.54.0-4ubuntu3.1_amd64.deb ...
Unpacking libboost-thread1.54.0:amd64 (1.54.0-4ubuntu3.1) ...
Selecting previously unselected package libpciaccess0:amd64.
Preparing to unpack .../libpciaccess0_0.13.2-1_amd64.deb ...
Unpacking libpciaccess0:amd64 (0.13.2-1) ...
Selecting previously unselected package librados2.
Preparing to unpack .../librados2_0.80.7-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking librados2 (0.80.7-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package librbd1.
Preparing to unpack .../librbd1_0.80.7-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking librbd1 (0.80.7-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libx86-1:amd64.
Preparing to unpack .../libx86-1_1.1+ds1-10_amd64.deb ...
Unpacking libx86-1:amd64 (1.1+ds1-10) ...
Selecting previously unselected package libyajl2:amd64.
Preparing to unpack .../libyajl2_2.0.4-4_amd64.deb ...
Unpacking libyajl2:amd64 (2.0.4-4) ...
Selecting previously unselected package dkms.
Preparing to unpack .../dkms_<IP_ADDRESS>-1.1ubuntu5.14.04+zfs9~trusty_all.deb ...
Unpacking dkms (<IP_ADDRESS>-1.1ubuntu5.14.04+zfs9~trusty) ...
Selecting previously unselected package spl-dkms.
Preparing to unpack .../spl-dkms_0.6.3-3~trusty_all.deb ...
Unpacking spl-dkms (0.6.3-3~trusty) ...
Selecting previously unselected package zfs-doc.
Preparing to unpack .../zfs-doc_0.6.3-5~trusty_amd64.deb ...
Unpacking zfs-doc (0.6.3-5~trusty) ...
Processing triggers for ureadahead (0.100.0-16) ...
Processing triggers for man-db (<IP_ADDRESS>-1ubuntu1) ...
Setting up dkms (<IP_ADDRESS>-1.1ubuntu5.14.04+zfs9~trusty) ...
Setting up spl-dkms (0.6.3-3~trusty) ...
Loading new spl-0.6.3 DKMS files...
First Installation: checking all kernels...
Building only for 3.13.0-36-generic
Building initial module for 3.13.0-36-generic
Done.
spl:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

splat.ko:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

Running the post_install script:
depmod......
DKMS: install completed.
Selecting previously unselected package zfs-dkms.
(Reading database ... 102108 files and directories currently installed.)
Preparing to unpack .../zfs-dkms_0.6.3-5~trusty_amd64.deb ...
Unpacking zfs-dkms (0.6.3-5~trusty) ...
Selecting previously unselected package augeas-lenses.
Preparing to unpack .../augeas-lenses_1.2.0-0ubuntu1.1_all.deb ...
Unpacking augeas-lenses (1.2.0-0ubuntu1.1) ...
Selecting previously unselected package bridge-utils.
Preparing to unpack .../bridge-utils_1.5-6ubuntu2_amd64.deb ...
Unpacking bridge-utils (1.5-6ubuntu2) ...
Selecting previously unselected package ebtables.
Preparing to unpack .../ebtables_<IP_ADDRESS>-3ubuntu1_amd64.deb ...
Unpacking ebtables (<IP_ADDRESS>-3ubuntu1) ...
Selecting previously unselected package iproute.
Preparing to unpack .../iproute_1%3a3.12.0-2_all.deb ...
Unpacking iproute (1:3.12.0-2) ...
Selecting previously unselected package libaugeas0.
Preparing to unpack .../libaugeas0_1.2.0-0ubuntu1.1_amd64.deb ...
Unpacking libaugeas0 (1.2.0-0ubuntu1.1) ...
Selecting previously unselected package libnetcf1.
Preparing to unpack .../libnetcf1_1%3a0.2.3-4ubuntu1_amd64.deb ...
Unpacking libnetcf1 (1:0.2.3-4ubuntu1) ...
Selecting previously unselected package libvirt0.
Preparing to unpack .../libvirt0_1.2.2-0ubuntu13.1.9_amd64.deb ...
Unpacking libvirt0 (1.2.2-0ubuntu13.1.9) ...
Selecting previously unselected package libxenstore3.0.
Preparing to unpack .../libxenstore3.0_4.4.1-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking libxenstore3.0 (4.4.1-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libxen-4.4.
Preparing to unpack .../libxen-4.4_4.4.1-0ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking libxen-4.4 (4.4.1-0ubuntu<IP_ADDRESS>) ...
Selecting previously unselected package libvirt-bin.
Preparing to unpack .../libvirt-bin_1.2.2-0ubuntu13.1.9_amd64.deb ...
Unpacking libvirt-bin (1.2.2-0ubuntu13.1.9) ...
Selecting previously unselected package libxml2-utils.
Preparing to unpack .../libxml2-utils_2.9.1+dfsg1-3ubuntu4.4_amd64.deb ...
Unpacking libxml2-utils (2.9.1+dfsg1-3ubuntu4.4) ...
Selecting previously unselected package pm-utils.
Preparing to unpack .../pm-utils_1.4.1-13ubuntu0.1_all.deb ...
Unpacking pm-utils (1.4.1-13ubuntu0.1) ...
Selecting previously unselected package spl.
Preparing to unpack .../spl_0.6.3-3~trusty_amd64.deb ...
Unpacking spl (0.6.3-3~trusty) ...
Selecting previously unselected package libuutil1.
Preparing to unpack .../libuutil1_0.6.3-5~trusty_amd64.deb ...
Unpacking libuutil1 (0.6.3-5~trusty) ...
Selecting previously unselected package libnvpair1.
Preparing to unpack .../libnvpair1_0.6.3-5~trusty_amd64.deb ...
Unpacking libnvpair1 (0.6.3-5~trusty) ...
Selecting previously unselected package libzpool2.
Preparing to unpack .../libzpool2_0.6.3-5~trusty_amd64.deb ...
Unpacking libzpool2 (0.6.3-5~trusty) ...
Selecting previously unselected package libzfs2.
Preparing to unpack .../libzfs2_0.6.3-5~trusty_amd64.deb ...
Unpacking libzfs2 (0.6.3-5~trusty) ...
Selecting previously unselected package zfsutils.
Preparing to unpack .../zfsutils_0.6.3-5~trusty_amd64.deb ...
Unpacking zfsutils (0.6.3-5~trusty) ...
Selecting previously unselected package ubuntu-zfs.
Preparing to unpack .../ubuntu-zfs_8~trusty_amd64.deb ...
Unpacking ubuntu-zfs (8~trusty) ...
Selecting previously unselected package vbetool.
Preparing to unpack .../vbetool_1.1-3_amd64.deb ...
Unpacking vbetool (1.1-3) ...
Processing triggers for man-db (<IP_ADDRESS>-1ubuntu1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-36-generic
Setting up mountall (2.53-zfs1) ...
Setting up libboost-system1.54.0:amd64 (1.54.0-4ubuntu3.1) ...
Setting up libboost-thread1.54.0:amd64 (1.54.0-4ubuntu3.1) ...
Setting up libpciaccess0:amd64 (0.13.2-1) ...
Setting up librados2 (0.80.7-0ubuntu<IP_ADDRESS>) ...
Setting up librbd1 (0.80.7-0ubuntu<IP_ADDRESS>) ...
Setting up libx86-1:amd64 (1.1+ds1-10) ...
Setting up libyajl2:amd64 (2.0.4-4) ...
Setting up zfs-doc (0.6.3-5~trusty) ...
Setting up zfs-dkms (0.6.3-5~trusty) ...
Loading new zfs-0.6.3 DKMS files...
First Installation: checking all kernels...
Building only for 3.13.0-36-generic
Building initial module for 3.13.0-36-generic
Done.
zavl:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

zcommon.ko:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

znvpair.ko:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

zpios.ko:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

zunicode.ko:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

zfs.ko:
Running module version sanity check.

Original module

No original module exists within this kernel

Installation

Installing to /lib/modules/3.13.0-36-generic/updates/dkms/

depmod....
DKMS: install completed.
Setting up augeas-lenses (1.2.0-0ubuntu1.1) ...
Setting up bridge-utils (1.5-6ubuntu2) ...
Setting up ebtables (<IP_ADDRESS>-3ubuntu1) ...
Setting up iproute (1:3.12.0-2) ...
Setting up libaugeas0 (1.2.0-0ubuntu1.1) ...
Setting up libnetcf1 (1:0.2.3-4ubuntu1) ...
Setting up libvirt0 (1.2.2-0ubuntu13.1.9) ...
Setting up libxenstore3.0 (4.4.1-0ubuntu<IP_ADDRESS>) ...
Setting up libxen-4.4 (4.4.1-0ubuntu<IP_ADDRESS>) ...
Setting up libvirt-bin (1.2.2-0ubuntu13.1.9) ...
Adding group `libvirtd' (GID 117) ...
Done.
libvirt-bin start/running, process 1359
Setting up libvirt-bin dnsmasq configuration.
Setting up libxml2-utils (2.9.1+dfsg1-3ubuntu4.4) ...
Setting up pm-utils (1.4.1-13ubuntu0.1) ...
Setting up spl (0.6.3-3~trusty) ...
Setting up libuutil1 (0.6.3-5~trusty) ...
Setting up libnvpair1 (0.6.3-5~trusty) ...
Setting up libzpool2 (0.6.3-5~trusty) ...
Setting up libzfs2 (0.6.3-5~trusty) ...
Setting up zfsutils (0.6.3-5~trusty) ...
Setting up vbetool (1.1-3) ...
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-36-generic
Processing triggers for ureadahead (0.100.0-16) ...
Setting up ubuntu-zfs (8~trusty) ...
Processing triggers for libc-bin (2.19-0ubuntu6.4) ...
===> 14:53:55.768 downloading flynn-host binary to tmp dir
===> 14:54:25.563 verifying flynn-host binary checksum
===> 14:54:25.610 moving verified flynn-host binary to /usr/local/bin
===> 14:54:25.612 running "gunzip /tmp/tmp.hRIJecRpvu/flynn-host.gz"
===> 14:54:25.820 running "mv /tmp/tmp.hRIJecRpvu/flynn-host /usr/local/bin/flynn-host"
===> 14:54:25.825 running "chmod +x /usr/local/bin/flynn-host"
===> 14:54:25.828 downloading Flynn components
14:54:55.902154 host.go:122: tuf: failed to download root.json: Get https://dl.flynn.io/tuf/root.json: dial tcp <IP_ADDRESS>:443: i/o timeout
===> 14:54:55.907 installing Upstart job
cp: cannot stat ‘/etc/flynn/upstart.conf’: No such file or directory
===> 14:54:55.989 installation complete!

@jeffkit thanks for that output, the original error was this:
14:54:55.902154 host.go:122: tuf: failed to download root.json: Get https://dl.flynn.io/tuf/root.json: dial tcp <IP_ADDRESS>:443: i/o timeout

I will open an issue so that this error does not prevent further installs to fail, and I have also opened #1144 to update the script so that those types of failures halt the installation with an error.
For now, to complete the installation run sudo rm -rf /etc/flynn and re-run the installation script.

@lmars Cool!  thanks!


Not working under Windows 11

Can't get it to work in Windows 11:
failed to get ticket
It's working fine with exactly the same settings under Windows 10.
Best Regards,
Michael

hi - thats strange I'll test it here on a w11 machine.


Change directory structure of Flyway CLI archive to make it compatible with SDKMAN!

Which version and edition of Flyway are you using?
Flyway 7.2.0 Community Edition
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
PostgreSQL 13
Which operating system are you using?
MacOSX Catalina
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
The SDKMAN! team received a PR (sdkman/sdkman-db-migrations#414) to add Flyway CLI to SDKMAN!.
While SDKMAN! would gladly add Flyway to the list of available candidates, there is one problem:
SDKMAN! expects the archive to contain a bin folder with the executable binaries (in your case flyway and flyway.cmd) under the root folder, which is then added to the PATH.
Something like this:
flyway-7.2.0 3/
  bin/
    flyway
    flyway.cmd

But looking at the Flyway CLI archive, it seems the binaries (flyway and flyway.cmd) are directly placed in the root folder.
flyway-7.2.0 3/
  flyway
  flyway.cmd

Would it be possible for Flyway to package the CLI differently, i.e. move the binaries to a bin subfolder?
We think that Flyway would be a great addition to SDKMAN!. If you have any questions or suggestions, feel free to ask!
What did you expect to see?
What did you see instead?

Changing the directory structure in this way isn't something we want to do. One reason is because flyway and flyway.cmd aren't actually binaries, but scripts that call into a JAR.
Is this something you could handle on your end? It doesn't feel right to require every software package to contain a bin folder

Agreed, we will think about options to handle that differently. Thank you for your quick answer!


Table 3

Hello,

What does underlines in table 3 mean?
You have mentioned "results in significant improvements on all three datasets". How did you calculate significance? I would like to know the details of the approach.

Thank you,

Underlined values usually highlight the second highest score in each column.
We did not do any specific significance testing, we will change the wording in future versions.


BUG : alert always in pending state

Proposal
I'm encountering a bug with one or more alerts that stay in pending state, and never go firing.
Pretty annoying since when an alert isn't firing, the sysadmins don't get notified :')
Bug Report
What did you do?
I created an alert :
- alert: vm_mem_usage_critical
    expr: ((vmware_vm_mem_usage_average / 100) >= on(vm_name) group_left() (vm_mem_high_threshold_critical or on(vm_name) count by(vm_name) (vmware_vm_mem_usage_average) * 0 + scalar(vm_mem_high_threshold_critical_DEFAULT)))
    for: 5m
    labels:
      severity: critical
    annotations:
      title: 'Critical : very High memory usage on {{ $labels.vm_name }}: {{ $value | printf "%.2f" }}%'

And it's always in "pending" state, cannot figure out why. I've spoke about it on irc and we couldn't find out why either.
I've checked other similar issues, usually this issue is when an alert has a variable inside a label, in my case I do not have this.
Note : this alert is just an example of one that stays in pending state, but this bug happens on other alerts too, it seems pretty random, instead of having usually ~450 firing alerts I only have ~200 and ~250 pending that always stay pending.
Here is a screenshot of the webui showing it's in pending state :

The "Active since" resets after every scrape to the time of the scrape.
Here is another screenshot of the webui graph of the same element showing it value stays the same and above the threshold (95), but still doesn't go firing :

I expect the alert to be in firing state instead.
A while ago I had this issue and resolved it by restarting the prometheus process, but now I have it again and a processus restart doesn't change anything, even after I wait a few hours.
Environment

System information:

Linux 3.10.0-957.27.2.el7.x86_64 x86_64

Prometheus version:

Had the issue with 2.11.0 and 2.12.0
prometheus, version 2.11.0 (branch: HEAD, revision: 4ef66003d9855ed2b7a41e987b33828ec36db34d)
build user:       root@0dc27cf95f36
build date:       20190709-09:54:35
go version:       go1.12.7
prometheus, version 2.12.0 (branch: HEAD, revision: 43acd0e2e93f9f70c49b2267efa0124f1e759e86)
build user:       root@7a9dbdbe0cc7
build date:       20190818-13:53:16
go version:       go1.12.8

Prometheus configuration file:

global:
  evaluation_interval: 15s
  scrape_interval: 15s
  scrape_timeout: 10s

  external_labels:
    environment: preproduction

rule_files:
  - /etc/prometheus/rules/*.rules

alerting:
  alertmanagers:
  - scheme: http
    static_configs:
    - targets:
      - <IP_ADDRESS>:9093

scrape_configs:
  - job_name: prometheus
    scrape_interval: 10s
    static_configs:
    - targets:
      - localhost:9090
  - job_name: VMWare
    metrics_path: /metrics
    relabel_configs:
    - source_labels:
      - __address__
      target_label: __param_section
    - source_labels:
      - __param_target
      target_label: instance
    - replacement: localhost:9272
      target_label: __address__
    scrape_interval: 5m
    scrape_timeout: 30s
    static_configs:
    - targets:
      - vc1
      - vc2
      - vc3
      - vc4
      - vc5
      - vc6

scrape_interval: 5m => this is too high, the maximum recommended value is 2 minutes to deal with staleness.

Thanks. I changed it to 2m and I don't get any more alerts that stay in pending state for now. Will re-open if it happens again

Hi,
Even with scrape_interval to 2m - I still get alarms that get stuck in pending state forever, please see :

All 44 are stuck in 'pending' state. It also happens for some other alerts.
I still don't know why it's happening, could 2m still be too high ?

@jdelvecchio
I suggest checking all time series which are referenced in the affected alerts. Are they stable over time? Are they all available consistently over time? Are there maybe recording rules with very long evaluation times?
If checking this does not yield a result yet, I recommend posting to the prometheus-users list (or IRC) so that we can track this down and provide more details in this bug tracker if it turns out to be an actual bug.

@jdelvecchio please use the prometheus users mailing list which is more relevant to answer this type of question.

It seems that the problem is your scrape_interval being higher than your evaluation_interval.
So if your scrape takes more than 15 seconds, your alert will be evaluated and will disappear from pending alerts.
And when your scrape is done, there is no pending alert so a new one is created as pending.
Safe thing to do is to set your evaluation_interval to the same value as your scrape_interval.

We looked at this as part of the bug scrub, and this appears to be a handled support request so closing.


chore(requirements): update jmespath to 0.9.1

See https://github.com/jmespath/jmespath.py/blob/develop/CHANGELOG.rst#091

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bdb5acd).

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 bdb5acd...6a497df. Read the comment docs.


feat: update to use python3.12

This fixes https://github.com/SirRender00/texasholdem/issues/251

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 90.97%. Comparing base (a09521f) to head (103b455).

Files
Patch %
Lines

texasholdem/game/move.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #254   +/-   ##
=======================================
  Coverage   90.97%   90.97%
=======================================
  Files          18       18
  Lines        1174     1174
=======================================
  Hits         1068     1068
  Misses        106      106

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Delete suspend parameter

Which issue(s) this PR fixes:
What this PR does / why we need it:
introduced in
https://github.com/fluent/fluentd/commit/c612e64a637012da946e2b2fa7bbf746bc44b798
and no need since https://github.com/fluent/fluentd/commit/7a547624b36bb0c4c20b3b9b6c91ac4235362df0
Docs Changes:
no need
Release Note:
no need

7a54762 This commit?

right! I fixed an commit message  and description of this PR.


Training without Lidar points

Hi,
I have a quick question:
You method seems to rely on Lidar points to intialize the gaussian blobs. Conventional 3DGS method works on randomly initialised point-cloud, I wonder if PVG can do that as well ? How does it affect the rendering results.

Hi, we have tested to train PVG with randomly initialized point cloud. It may produce bad depth map, while the rendering PSNR decrease slightly .

Hi, I wonder how can I do that with the current codebase ?


Examples README samples are broken

What seems off:
The include of example sample seems to break the readme layout:

What you expected to be:
The layout to be nice and clean.

Hey @JBBianchi thanks for reporting it! Are you willing to fix it? :D

Yes, it's just a line return that needs to be added.

It's broken again

@JBBianchi is this fixed?

It looks like the workflow to hydrate the readme is broken: https://github.com/serverlessworkflow/specification/actions/workflows/examples-readme-hydration.yml
Either because the BOT_PAT secret is missing or the bot doesn't have the rights one the repository.

That's weird, I'll take a look later

I think it would be a good thing to fix the bot config. Even if the examples are dropped with the next version, we'll still need a functioning bot in the future.

@ricardozanini Can you please address that?

Closing this since we don't have this pipeline nor the examples README anymore.

I think this must be fixed on 0.9.0

@cdavernas I'll reopen but it might stale. I'd keep it close and if there's momentum we'll notice since the CI will fail, then we can fix it. I'm investing my time on 1.0.0 atm. Feel free to reopen.


Support dilated transposed convolutions in the conv_transpose op.

Plug the argument through to the underlying conv_general_dilated method as well as updating how the padding is created in order to deal correctly with the rhs_dilation.
Added test as well to ensure it is implemented correctly.
PiperOrigin-RevId: 284155973

@jekbradbury are you able to review this one as well?


Update extensions documentation

Update
https://docs.google.com/document/d/1orlYWGlHOY0hmAC0zjadQ4DET2K8U34C8hv5zmuxZLU/edit#heading=h.q0qxs8avzosb
The version currently there is from the pre-release

@halatmit  I made an update to this document on June 9th to address changes to the extension mechanisms made as part of the IoT release. I also removed some of the references to earlier methods, such as checking out the CDK branch. Please make a pass and note any places where you think updates still need to be made.


chore: delete item in dependentsMap if is empty

was it to do that?
all tests passed
😥

Good Luck. You are amazing! 💖

you are awesome @dai-shi 🤗
thank you very much for your work in the react community


Fixed #24127 -- Changed the default current_app to the current namespace.

Changed the url template tag to use request.resolver_match.namespace as a
default for the current_app argument if request.current_app is not set.
https://code.djangoproject.com/ticket/24127

It doesn't hurt to properly document request.current_app, so I made #4920. That should fix the doc error here.

tests to be added?

Don't forget to tick the appropriate flags on the ticket when updating so the ticket appears in the review queue. Thanks!

merged in bc7923beffea3c51271935cad1371a67c5fcc71b, thanks!