Inconsistent quit notification when frame limit is off

Mind you this apparently only works on certain hardware, possibly low-end.
When my 'target_fps' option is turned off, the quit notification does not always trigger. Maybe 1/3 of the time it works. It does not even enter the function because it does not give a '7' for the notification when I press the close button.
It is a medium size program and I followed this tutorial to the exact: https://github.com/okamstudio/godot/wiki/tutorial_quit  so there is little need to share code. It does not get past the conditional when it doesn't work.
I had romulox look at it and it works consistently on his computer. It is possible our hardware difference (his computer is much better) is causing the difference, but I am not certain.
romulox_x: i took out the tree.quit line so i could click the x a bunch, and it prints every time

Linux Mint 64bit with XFCE

Is it still reproducible in the current master branch?

I hope so, maybe I will test this someday. The tutorial link above is gone, but this seems to be the equivalent if you want to test it sooner: http://docs.godotengine.org/en/latest/tutorials/engine/handling_quit_requests.html

No, actually I should do it with that same hardware. I'll get it set up to test with latest stable again.

Pretty bump, aka did you manage to test it?

Oh, it's been so long, but I'll be sure to check out that part of the code when I port the utility to 3.0!
It should work, but I'm not certain it fully does. You see, it saves all the user files on quit (as I intended it to do) without corruption of the file ever. However I believe the queue for printing stuff gets eliminated, which is the actual issue.

It appears that this issue also extends to Windows 10 as well. This is my code for testing.

For me, the "Closed!" text only prints about 50% of the time.

I couldn't reproduce it on Windows 10 device with latest master.

I tested this in 3.2.2 stable with similar code to Please Be Gentle's. The notification works for Alt+F4 and clicking the close button 100% of the time for me now. I am going to close this. Thanks to aaronfranke for pointing out this was still open.


Apply fix to wxWidgets for copy and paste macOS

Fixes copy and paste on macOS. See wxWidget's Trac #18553. Patch has long been applied wxWidgets master, this just backports it to the released development version. I've tested the fix locally and it works correctly.

Which triplets are supported/not supported? Have you updated the CI baseline?

No changes though the fix only affects for macOS builds.

Does your PR follow the maintainer guide?

I hope so.

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

Alright, this looks good to me! Thanks @brad-anderson :)


HoloToolkit's WorldAnchorManager does not exist in MRTK and the Porting Guide doesn't offer any guidance for replacing it

Describe the bug
We are currently using the WorldAnchorManager provided in HoloToolkit, and it's not clear how to replace it as we transition to MRTK.
Expected behavior
Either MRTK contains a version of WorldAnchorManager, or the Porting Guide gives an explanation of how it can be replaced.
Target Platform
HoloLens
HoloLens 2
WMR immersive
Additional context
Admittedly WorldAnchorManager does not provide a lot beyond Unity's WorldAnchor/AnchorStore, but I think it does add a bit of convenience - and I think we'd end up duplicating/re-implementing some of the same code otherwise so it's nice to have it in shared code.

Agree. I've been looking for WorldAnchorManager in MRTK Version 2.0.0-RC1 with no luck and found no info about what happened to it.
@naostranMS have you tested WorldAnchorStore in MRTK Version 2.0.0-RC1? Either I'm doing something wrong or it doesn't work.

@sebastianpietraszek-wi I haven't used WorldAnchorStore directly as we're still using HTK's WorldAnchorManager at the moment, but that does use Unity's WorldAnchorStore under the hood - as far as I can tell it is working fine still (on unity 2018.3.1f1 if that helps).

partner reported same thing

@naostranMS are you working on MRTK Version 2.0.0-RC1?

@sebastianpietraszek-wi I'm working out of the mrtk_development branch on a commit from sometime last week iirc

They can still get the implementation copied from HTK, and it still works. However it is not available in MRTK v2 package. We can create a package to include this in MRTK v2 as a workaround for now.
Step 2 is to clean this up and understand the story with AR Foundation and XR SDK in 2019

Urgency soon is only for getting this into MRTK v2 package or updating porting guide

I've brought the class itself over, though with a few caveats:
Some things that were public/protected were made private. I wanted to go with the smaller API surface and then open things up as we got more information on what people needed, rather than blasting out with a larger surface without a good understanding of the needs.
So to this end, feel free to open other issues or PRs if we need to open up the visibility of some of the fields


Connect chrome without GUID

Steps to reproduce
While connecting remote chromium headless instances behind Loadbalancer(lb) puppeteer needs proper guid to connect.
I know there is a way through service discovery /json but since i would be having few chromium running behind my lb. I would like the lb to redirect dynamically without worrying about GUID matching issues.
Tell us about your environment:

Puppeteer version: 1.9.0-post
Platform / OS version: Chromium 69.0.3497.81 Built on Ubuntu , running on Ubuntu 16.04
Node.js version:10.12.0

Please include code that reproduces the issue.
const puppeteer = require('puppeteer');

(async () => {
    try {
        const browser = await puppeteer.connect({ browserWSEndpoint: 'ws://load-balancer-url:9222' });
        const page = await browser.newPage();
        await page.goto('https://google.co.in');
        let content = await page.content();
        console.log(content.length);
        await page.close();
        await browser.disconnect();
    }
    catch (exception){
        console.error(exception);
    }
})();

What is the expected result?
It should connect dynamically and print the content length.
What happens instead?
It fails with some unrelated error
(node:7520) UnhandledPromiseRejectionWarning: #<ErrorEvent>
(node:7520) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:7520) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Possible Solution
This issue is somewhat related to #940
A friend of mine made some changes to the core puppeteer library and gave it to me and it seems working. I would like to know if it is the right approach.
Check this out.
https://github.com/GoogleChrome/puppeteer/compare/master...uniquerockrz:master

@ja8zyjits what are you load balancing - chrome instances, browser contexts or pages? Given the patch your friend did, it looks like you're actually dealing with Pages - is this the case?

@aslushnikov Iam trying to load balance chromium instance machines. I are running 1 chromium instance per machine.
Basically I wanted to perform a selenium-grid kind of distribution of chromium running machines.

@ja8zyjits I see. Once you launch a chromium, you can get its endpoint using browser.wsEndpoint. So every machine would launch a browser instance and report the endpoint to the master node - would this work?
The puppeteer-cluster is doing something similar.

@aslushnikov really appreciate your support but Iam not sure if puppeteer-cluster does something similar.
It runs chromium in same system concurrently and not in a distributed manner.
What I would like to do?
I am certainly aware distributed chromium handling is not the main objective of puppteer project, yet I would like to know if there is any way to connect to chromium via a single request.
Presently an HTTP request is sent 1st and later a websocket request is sent based on the details returned(response) from the 1st request.
This makes it difficult to run behind a load balancer.

It runs chromium in same system concurrently and not in a distributed manner.

@ja8zyjits that's right; I was referring to the way it targets chromium instances and gets their remote debugging websockets.

Presently an HTTP request is sent 1st and later a websocket request is sent based on the details returned(response) from the 1st request.

I don't think I follow this. Why do you need an HTTP request?

If you launch chrome instances with puppeteer, you have their websocket URLs with browser.wsEndpoint().
If you launch instances manually, you can read the websocket URL from chrome's stdout.

Can you explain more on how you manage chromium instances?

I don't think I follow this. Why do you need an HTTP request?

Well when you call pupeteer.connect() this is how it happens. I checked my haproxy log.

If you launch instances manually, you can read the websocket URL from chrome's stdout.

This can work locally. But not in case of remote connection.
In remote connections we would initiate the chromium instance with supervisor and keep it running and restarting if it crashes.
I was trying to send the request without the guid information await puppeteer.connect({ browserWSEndpoint: 'ws://load-balancer-url:9222' });

Well when you call pupeteer.connect() this is how it happens. I checked my haproxy log.

@ja8zyjits This is one is a WebSocket handshake, isn't it? You can't avoid it unless you use pipe option and organize your own transport between load balancer and controlled chromium instances.

I was trying to send the request without the guid information await puppeteer.connect({ browserWSEndpoint: 'ws://load-balancer-url:9222' });

This won't work auto-magically; you can load-balance websocket connections, but you'll still need to get the URL of an open websocket of the controlled chromium instance. That's the only way to connect to chromium.

@aslushnikov ok I understand. Thanks for your time.

@ja8zyjits hello! Could you please say how you resolved this issue? I faced with the same problem, but use several chrome instances in Kubernetes


[KOGITO-169] - Introducing kogito install operator

See:
https://issues.jboss.org/browse/KOGITO-169
In this PR:

Huge refactoring on CLI. Was impracticable to add more commands to the older code
Introducing the possibility to install the operator. If the operator deployment is not there, then:
a. First check for OLM and CSV available in the cluster ~(install from there)~.
b. Install via deploy/*.yaml files

This command it's just a shortcut to have the Operator deployed on clusters that don't have the Operator Catalog deployed by default (OCP 3.x, others kube distributions).
Once we have our operator on Operatorhub, we'll look for it on the catalog and alert the user that the operator is there and they should use it to deploy the operator in their namespace.
Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Your feature/bug fix has a unit test that verifies it
[x] You've tested the new feature/bug fix in an actual OpenShift cluster

Will fix this error on the CI, it's a problem with the config file.

@xiezhang7 I honestly don't know what's happening with the:
FAIL	github.com/kiegroup/kogito-cloud-operator/cmd/kogito/command/deploy [build failed]

Do you know how do we can see the inner error in this build?
Of course the test "works on my machine" :(

Just run the CI using their own container:
=== RUN   Test_DeleteServiceCmd_WhenWeSuccessfullyDelete
--- PASS: Test_DeleteServiceCmd_WhenWeSuccessfullyDelete (0.00s)
=== RUN   Test_DeleteServiceCmd_WhenServiceDoesNotExist
--- PASS: Test_DeleteServiceCmd_WhenServiceDoesNotExist (0.00s)
=== RUN   Test_DeployCmd_WhenThereAreNoOperator
--- PASS: Test_DeployCmd_WhenThereAreNoOperator (0.00s)
=== RUN   Test_DeployCmd_WhenThereAreAnOperator
--- PASS: Test_DeployCmd_WhenThereAreAnOperator (0.02s)
=== RUN   Test_DeployCmd_CustomDeployment
--- PASS: Test_DeployCmd_CustomDeployment (0.01s)
=== RUN   Test_DeployCmd_CustomImage
--- PASS: Test_DeployCmd_CustomImage (0.03s)
PASS
ok  	github.com/kiegroup/kogito-cloud-operator/cmd/kogito/command/deploy	0.201s

@ricardozanini I don't have any problem with the tests for deploy. But a test failed for project when it is executed for the first time.

--- FAIL: TestUseProjectCmd_WhenWhatIsTheNamespace (0.00s)
use_project_test.go:81:
Error Trace:	use_project_test.go:81
Error:      	Received unexpected error:
Project 'kogito' not found. Try running 'kogito new-project kogito' to create your Project first
Test:       	TestUseProjectCmd_WhenWhatIsTheNamespace
use_project_test.go:83:
Error Trace:	use_project_test.go:83
Error:      	"Error: Project 'kogito' not found. Try running 'kogito new-project kogito' to create your Project first
Usage:
kogito use-project NAME [flags]
    	            	Aliases:
    	            	  use-project, use-ns

    	            	Flags:
    	            	  -h, --help          help for use-project
    	            	  -n, --name string   The project name

    	            	Global Flags:
    	            	      --config string   config file (default is $HOME/.kogito.json)
    	            	  -v, --verbose         verbose output
    	            	      --version         display version

    	            	" does not contain "f9ada603-466e-4b68-bcf2-64f1a73f2c4d"
    	Test:       	TestUseProjectCmd_WhenWhatIsTheNamespace

FAIL
FAIL	github.com/kiegroup/kogito-cloud-operator/cmd/kogito/command/project	0.043s

@ricardozanini I don't have any problem with the tests for deploy. But a test failed for project when it is executed for the first time.

This is odd. It could be related to the config file, but even removing it and running only this test I can't reproduce this same error.

Looks like our Go container run out of resources:
https://stackoverflow.com/questions/52129612/golang-circleci-2-0-test-failing-with-signal-killed

@xiezhang7 @spolti could you guys take a look?

@xiezhang7 @spolti @sutaakar talking with @porcelli about this feature, we found out that would be nice to have the CLI to check and install the operator in those features as well:
kogito new-project
kogito use-project
kogito install data-index
kogito deploy-service

What do you guys think about it?

@xiezhang7 @spolti @sutaakar talking with @porcelli about this feature, we found out that would be nice to have the CLI to check and install the operator in those features as well:
kogito new-project
kogito use-project
kogito install data-index
kogito deploy-service

What do you guys think about it?

kogito new-project
we could add some labels on kogito projects to help to identify projects created by the CLI
kogito use-project
maybe only kogito project? ( I like the way the oc command does)
kogito install data-index
deploy data-index?
kogito deploy-service
is this deploy service meant to be used to deploy kogito apps? if so, looks good to me.

kogito new-project
we could add some labels on kogito projects to help to identify projects created by the CLI

We already add the "app" label and "org.kie/managed-by" annotation to every object created by the operator. The CLI is just a proxy for it, I don't think we need any more label/annotation, but I don't think this could cause any harm. Could you please one a minor JIRA for this?

kogito use-project
maybe only kogito project? ( I like the way the oc command does)

Was only "project", but we changed in this JIRA after having a discussion with @porcelli about this.

kogito install data-index
deploy data-index?

We had this discussion in the dev list and we decided to use install

kogito deploy-service
is this deploy service meant to be used to deploy kogito apps? if so, looks good to me.

Yes, and the kogitoapp CR will be changed to kogitoservice in the near future.

@spolti @sutaakar @xiezhang7 I know I'm asking too much, but I've implemented the feature to install the operator after those commands. Feels great from the dev point of view:
$ kogito new-project kogito-operator2
Project 'kogito-operator2' created successfully
Kogito Operator not found in the namespace 'kogito-operator2', trying to deploy it
Kogito Operator successfully deployed in 'kogito-operator2' namespace

Could you please take a final look before I merge this?


Enable chromecast for ios

Related issue: https://github.com/flexn-io/renative/issues/1456

Ech ty


ci: add yq shim for v3/v4 support

yq3 (installed in kata builds as a side effect) and yq4 are different in cli and query syntax. the shim should abstract from those differences

So the workflow is failing with:
Makefile.defaults:6: *** "/work/cloud-api-adaptor/hack/yq-shim.sh not found, consider doing snap install yq".  Stop.

So maybe there is an issue with the $(ROOT_PATH)/hack/yq-shim.sh not having src/cloud-api-adaptor in the path, or the workflow running in the wrong directory?
Anyway I can confirm that pulling this into my switch to main branch it allows me to install the yq v3 that the kata-agent in main needs, so thanks so much!

So maybe there is an issue with the $(ROOT_PATH)/hack/yq-shim.sh not having src/cloud-api-adaptor in the path, or the workflow running in the wrong directory?
Anyway I can confirm that pulling this into my switch to main branch it allows me to install the yq v3 that the kata-agent in main needs, so thanks so much!

The shim wasn't present in the Dockerfile, I pushed a fix. The steps pass docker build step now, let's see whether the podvm build also works.
I'm running a non-docker build on a fork at the moment that will build kata-agent (and hence intall yq v3) and then later CAA binaries that used to rely on v4, so we'll see whether the fallback works.

Hi @mkulke I got it! :) :You was talking about the caa side, not kata side!
Apart from introducing another "shim", lgtm.

I somehow thought that kata had an abstraction over yq queries, but I must have misremembered. For CAA it's easier to deal with the version ambiguity, as it's only a couple of queries.

ok the worklfow in which the kata-build installs v3 and things still work passed
the libvirt tests also seem to execute now, so that's good. i'll merge after the libvirt tests hopefully pass

BTW, one question, we should use the yq-shim only when dealing with stuff related to kata or everywhere in CAA now we should use yq-shim?

The amd-64 podvm image build failures look like a network flake:
#17 139.3 ==> qemu.ubuntu: Retrieving ISO
#17 139.3 ==> qemu.ubuntu: Trying https://cloud-images.ubuntu.com/releases/focal/release-20230107/ubuntu-20.04-server-cloudimg-amd64.img
#17 139.3 ==> qemu.ubuntu: Trying https://cloud-images.ubuntu.com/releases/focal/release-20230107/ubuntu-20.04-server-cloudimg-amd64.img?checksum=sha256%3A3895e38566e5c2c019f5c6f825ab7570ee34dac6b9142fab0c7e5a78084c4280
#17 1409.3 ==> qemu.ubuntu: Download failed read tcp <IP_ADDRESS>:49390-><IP_ADDRESS>:443: read: connection reset by peer
#17 1409.3 ==> qemu.ubuntu: error downloading ISO: [read tcp <IP_ADDRESS>:49390-><IP_ADDRESS>:443: read: connection reset by peer]
#17 1409.3 Build 'qemu.ubuntu' errored after 21 minutes 10 seconds: error downloading ISO: [read tcp <IP_ADDRESS>:49390-><IP_ADDRESS>:443: read: connection reset by peer]

so I've re-run them

BTW, one question, we should use the yq-shim only when dealing with stuff related to kata or everywhere in CAA now we should use yq-shim?

kata will mandate v3 for the time being, and it will even install it on you machine, overriding v4. so the yq-shim adds a compatibility layer that will make v4 queries (CAA) work with v3 and v4
this allows you to build kata + caa on the same machine. so you'd use the yq-shim when v3 is required (e.g. the azure build)


Automated cherry pick of #1529: fix create image with userCred issue

Cherry pick of #1529 on release/2.11.0.
#1529: fix create image with userCred issue

/lgtm
/approve


[ClangImporter] Fix another lifetime extension issue.

The StringRef here referred to a temporary std::string.
rdar://problem/28699869

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge

@jrose-apple Do you know what's going on with Linux here?

Hm, no, that doesn't look related. @ddunbar, does this look familiar?

@swift-ci Please smoke test

@shahmishal This one flagged the wrong commit again. https://ci.swift.org/job/swift-PR-Linux-smoke-test/1783/


Update to the new empack

Problem
A few projects in the emscripten forge organization have now been updated to use the new empack >=3.0.0:

https://github.com/emscripten-forge/pyjs-code-runner
https://github.com/emscripten-forge/sample-python-repl

Proposed Solution
Update the xeus python kernel to empack>=3.0.0.
This will likely require the next version of jupyterlite-xeus-python to be 0.9.0.
Additional context

This may help me finish https://github.com/conda-forge/staged-recipes/pull/22492 as well, because it may help supporting Windows

for that, we need a new release /tag in  of xeus python (with this in https://github.com/jupyter-xeus/xeus-python/pull/588)
Then we can put that version on emscripten-forge
Once we have that we can use the whole empack >= 3.0.0 stack here

for that, we need a new release /tag in of xeus python (with this in jupyter-xeus/xeus-python#588)

@martinRenou or @DerThorsten would you be able to make a new release of Xeus Python? Thanks!

for that, we need a new release /tag in of xeus python (with this in jupyter-xeus/xeus-python#588)

@martinRenou or @DerThorsten would you be able to make a new release of Xeus Python? Thanks!

xeus-python 0.15.9 is out!

Nice thanks!
Just opened https://github.com/emscripten-forge/recipes/pull/449

is the reason why I met this error on the jupyter lite build command: FileNotFoundError: [Errno 2] No such file or directory<EMAIL_ADDRESS>

@JeongJun-Lee I think this is unrelated, would you be able to open your own issue with more in-depth information about your setup, like the empack version and how you installed it?

Closing as fixed by https://github.com/jupyterlite/xeus-python-kernel/pull/134, thanks!


unable to rotate camera

camera wont rotate with plugin active as of 1/12/23. keeps camera faced North

just noticed only happens at 100% smoothness. also zoom smoothness enabled in bugged and zooms in and out in flashes

I could have prevented users from using 100% smoothness but I figured some people might find fun challenges to do with it, so I left it in.


Entering VR does not work if Oculus runtime is not installed

Stereo mode should be entered if I don't have the Oculus runtime installed. Right now clicking "Enter VR" does nothing if so.

Work done by @ngokevin as referenced above fixes this.


use get_url instead of base_url

Implements idea formulated in #49.

Nice!  This looks like the right way to do it.  I assume it works so will do it.

I also think this is much nicer than carrying around the base_url. Thanks again for pointing this out!


Improve Readme.md file.

Hello I am from GSSoC'24. I want to work on this issue please assign me.

I would like to do the work, and improve it so that other contributors can understand better and contribute with there skills

I would like to work on it

Hello I am from GSSoC'24. I want to work on this issue please assign me.

Welcome Rajkumar, assigned


Can we install editors such as nano?

It seems like in the default environment editor vi is available for use. Would it be possible to install another editor nano, which is easier to use? Thanks very much for considering my request!
Yutian Wu

Hi @yutianwuldeo, thanks for raising this question. Unfortunately we don't have clear-cut guidelines for what to include and what not to :(
Are you using these images on the Pangeo JupyterHub or on your own infrastructure? You can always fork this repository to create customized images. I'd be curious to know how much extra space adding nano takes?
It looks like it is available from conda-forge, so you can either add it for a particular image (e.g. pangeo-notebook):
https://github.com/pangeo-data/pangeo-docker-images/blob/master/pangeo-notebook/apt.txt
Or for all images:
https://github.com/pangeo-data/pangeo-docker-images/blob/4552cca5fcd4377ca3a6806f7cc7ef33d96abd63/base-notebook/environment.yml#L5-L8

about 0.5 Mb looking at the footprint on my ubuntu
also vote for this, nano is a lifesaver

Nano is now in pangeo-notebook 2024.10.11 and later


[NBS Docs] Added SingIn Resolvers Config Details

Hey, I just made a Pull Request!
This adds the signIn.resolvers details to the auth docs for the following providers:

Atlassian
GCP IAP
GitHub
GitLab
Google
Microsoft
oauth2 Proxy
Okta
VMware Cloud

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks for the reviews @camilaibs @benjdlambert and @Rugvip for getting this merged! 🚀


Position is wrong when body overflow is hidden and page is scrolled down

CodePen demo
http://codepen.io/donnysim/pen/NjdoEb
Steps to reproduce the problem

Scroll down and click on the button

What is the expected behavior?
The dropdown is below select.
What went wrong?
Dropdown is way below of where it should be and jumps when the window height is adjusted.

May you please simplify the codepen to include only the minimum amount of code needed to reproduce the problem?
From my tests I noticed that if I set .modal-open .modal to overflow: hidden instead of     overflow-x: hidden; overflow-y: auto; everything works properly. But I need a more concise test case to better debug the problem.

I tried replicating what bootstrap does, but I'll see what I can change.

Well, this is the correct behavior. If you set .modal-open .modal to overflow: hidden then the modal itself will not be scrollable when the height is greater than window, so there's nothing else I can do.

I think I didn't explain myself clearly.
Your example includes a lot of 3rd party code (Bootstrap) and a lot of custom markup and CSS.
To be able to debug the problem I need an example as simple as possible, without any external dependency and with just the minimum code needed to reproduce the problem.

by the way, I tried to reproduce it from scratch. I think it's a dupe of #224

Removed bootstrap, but yeah, seems like it is :(


Get error in IE11

I get and error in ie11.
I found that you use new Event() which not support in ie in line 315(version 1.1.5).
How can I fix it?

Verified bug. Will slot in the fix for the 1.1.6 milestone.

https://msdn.microsoft.com/en-us/library/dn905219(v=vs.85).aspx

Ok,thanks.

Fixed by #34

I could do with this fix being deployed, is there anything stopping 1.1.6 being tagged?

Done. Change log updated, 1.1.6 available through bower and npm.


Problems with changing passwords when using social login accounts

Version: 0.23.0
Describe the bug
If you attempt to change your password on an account that you have subscribed to as a social login, an error such as "internal system error" will occur.
Steps To Reproduce
The above error occurs when a user attempts to change the password on an account that he or she subscribed to as a social login.
Expected behavior
I expected a message to the user that the password of an account that you logged in to social media cannot be changed, or an action that allows you to change the password.
Screenshots

Desktop (please complete the following information):

OS: Mac
Browser: Chrome
Version: 103

Additional context

@hmmhmmhm can you share detail about the follow
example,
you tried fogot-password flow
or you tried update-profile api?

I had this experience in the process of updating profile page.
Users who signed up for social login want to set a password
(I belatedly found it impossible. Maybe this is the problem.)

@hmmhmmhm thank you for sharing this.
I will fix this today and share a release

@hmmhmmhm released a fix as part of 0.37.0

if you user has not signed up with basic auth, they will need to set new password and confirm password to update using that method.

Note: earlier this was possible with forgot password

Thank you! It's a great patch!


interventions: associate with person and default to Derrida

As an interventions data editor, I want to associate an intervention with the person who wrote it so that I can document the author when that information is known; I want “Derrida, Jacques” to be the default intervention author, and I want to be able to add or edit this information.

I think in the foreign key for intervention author should have a callable set as the default value.  The callable will look up Derrida and return person or null.  Needs to be a callable since Derrida might not be in the database.
This covers django admin, but doesn't handle setting a default in the annotator interface.  We might need to extend the default canvas detail view so we can pass in custom context data (it seems like a poor idea to have the name hardcoded in more than one place).  I thought about doing that for the list of languages but worked around it.   If we don't want to go that route, maybe we could provide an annotation default via json view.

This is working and unit-tested, though I did not yet hook up an autocomplete for annotators (not sure what criteria we might be using to sort people usefully).


Fails to compile on UE 4.26

Seems that UE 4.26 has added some incompatible changes so the plugin fails to compile now. Here is a log:
[2/5] Module.GlobalEventSystem.cpp
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GESDataTypes.h(32): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GESDataTypes.h(78): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GESDataTypes.h(118): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESDataTypes.cpp(6): error C2039: 'AddToRoot': is not a member of 'FProperty'
  C:\Program Files\Epic Games\UE_4.26\Engine\Source\Runtime\CoreUObject\Public\UObject/UnrealType.h(101): note: see declaration of 'FProperty'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESDataTypes.cpp(17): error C2039: 'IsValidLowLevelFast': is not a member of 'FProperty'
  C:\Program Files\Epic Games\UE_4.26\Engine\Source\Runtime\CoreUObject\Public\UObject/UnrealType.h(101): note: see declaration of 'FProperty'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESDataTypes.cpp(19): error C2039: 'RemoveFromRoot': is not a member of 'FProperty'
  C:\Program Files\Epic Games\UE_4.26\Engine\Source\Runtime\CoreUObject\Public\UObject/UnrealType.h(101): note: see declaration of 'FProperty'
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Private\GESHandler.h(83): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(8): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(21): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(27): error C2664: 'bool FFieldClass::IsChildOf(const FFieldClass *) const': cannot convert argument 1 from 'UClass *' to 'const FFieldClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(27): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  C:\Program Files\Epic Games\UE_4.26\Engine\Source\Runtime\CoreUObject\Public\UObject/Field.h(92): note: see declaration of 'FFieldClass::IsChildOf'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(45): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(47): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(51): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(113): error C2039: 'RemoveFromRoot': is not a member of 'FProperty'
  C:\Program Files\Epic Games\UE_4.26\Engine\Source\Runtime\CoreUObject\Public\UObject/UnrealType.h(101): note: see declaration of 'FProperty'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(328): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(334): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(336): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(336): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(328): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(328): error C2664: 'bool FGESHandler::FunctionHasValidParams(UFunction *,UClass *,const FGESEmitData &,const FGESEventListener &)': cannot convert argument 2 from 'FFieldClass *' to 'UClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(328): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(57): note: see declaration of 'FGESHandler::FunctionHasValidParams'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(334): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(336): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(336): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(363): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(363): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(363): error C2664: 'bool FGESHandler::FunctionHasValidParams(UFunction *,UClass *,const FGESEmitData &,const FGESEventListener &)': cannot convert argument 2 from 'FFieldClass *' to 'UClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(363): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(57): note: see declaration of 'FGESHandler::FunctionHasValidParams'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(374): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(374): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(374): error C2664: 'bool FGESHandler::FunctionHasValidParams(UFunction *,UClass *,const FGESEmitData &,const FGESEventListener &)': cannot convert argument 2 from 'FFieldClass *' to 'UClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(374): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(57): note: see declaration of 'FGESHandler::FunctionHasValidParams'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(387): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(387): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(387): error C2664: 'bool FGESHandler::FunctionHasValidParams(UFunction *,UClass *,const FGESEmitData &,const FGESEventListener &)': cannot convert argument 2 from 'FFieldClass *' to 'UClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(387): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(57): note: see declaration of 'FGESHandler::FunctionHasValidParams'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(398): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(398): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(398): error C2664: 'bool FGESHandler::FunctionHasValidParams(UFunction *,UClass *,const FGESEmitData &,const FGESEventListener &)': cannot convert argument 2 from 'FFieldClass *' to 'UClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(398): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(57): note: see declaration of 'FGESHandler::FunctionHasValidParams'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(409): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(409): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(409): error C2664: 'bool FGESHandler::FunctionHasValidParams(UFunction *,UClass *,const FGESEmitData &,const FGESEventListener &)': cannot convert argument 2 from 'FFieldClass *' to 'UClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(409): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(57): note: see declaration of 'FGESHandler::FunctionHasValidParams'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(421): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(421): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(421): error C2664: 'bool FGESHandler::FunctionHasValidParams(UFunction *,UClass *,const FGESEmitData &,const FGESEventListener &)': cannot convert argument 2 from 'FFieldClass *' to 'UClass *'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(421): note: Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(57): note: see declaration of 'FGESHandler::FunctionHasValidParams'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(440): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(457): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(459): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(462): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(457): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(459): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(462): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(478): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(480): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(480): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(480): error C2665: 'ExactCast': none of the 2 overloads could convert all the argument types
  C:\Program Files\Epic Games\UE_4.26\Engine\Source\Runtime\CoreUObject\Public\Templates/Casts.h(319): note: could be 'const T *ExactCast<FStructProperty>(const UObject *)'
          with
          [
              T=FStructProperty
          ]
  C:\Program Files\Epic Games\UE_4.26\Engine\Source\Runtime\CoreUObject\Public\Templates/Casts.h(223): note: or       'T *ExactCast<FStructProperty>(UObject *)'
          with
          [
              T=FStructProperty
          ]
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(480): note: while trying to match the argument list '(FProperty *)'
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(484): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(486): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(486): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(491): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(493): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(493): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(498): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(500): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(500): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(514): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(516): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(516): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(521): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(523): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GESHandler.cpp(523): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Intermediate\Build\Win64\UE4Editor\Inc\GlobalEventSystem\GlobalEventSystemBPLibrary.generated.h(14): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(41): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(84): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(95): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(96): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(97): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(98): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(102): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(102): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(121): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(125): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:\Projects\AVcity\Plugins\global-event-system-ue4\Source\GlobalEventSystem\Public\GlobalEventSystemBPLibrary.h(125): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(50): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(77): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(79): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(79): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(101): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(103): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(103): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(125): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(127): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(127): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(140): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(142): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(142): warning C4996: UStrProperty has been renamed to FStrProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(151): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(153): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(153): warning C4996: UNumericProperty has been renamed to FNumericProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(163): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(165): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(165): warning C4996: UBoolProperty has been renamed to FBoolProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(175): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(177): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(177): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(180): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(182): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(182): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(186): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(188): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(188): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(204): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(206): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(206): warning C4996: UNameProperty has been renamed to FNameProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(217): warning C4996: UProperty has been renamed to FProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(225): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(225): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(227): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(227): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(228): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(228): warning C4996: UStructProperty has been renamed to FStructProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(241): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(243): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
  D:/Projects/AVcity/Plugins/global-event-system-ue4/Source/GlobalEventSystem/Private/GlobalEventSystemBPLibrary.cpp(243): warning C4996: UObjectProperty has been renamed to FObjectProperty Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.

It appears you haven't pulled the 4.25 version (currently merged in master branch) as it does currently compile without code changes for 4.26 (FProperty changes happened in 4.25). Clean your plugin and replace with current master branch or use https://github.com/getnamo/global-event-system-ue4/releases/tag/0.5.0 release in c++ project that recompiles it.

There's now a 4.26 release too: https://github.com/getnamo/global-event-system-ue4/releases/tag/0.6.0


Region when called lambda functions ...

I am trying to call a lambda function.
user configuration file:
[default]
region = us-west-2

ARN:
arn:aws:lambda:us-west-2:468131460318:function:sct_mail_20161103144602
I use the following code:
...
Aws::SDKOptions options;
Aws::InitAPI(options);
LambdaClient client;
InvokeRequest invokeRequest;
invokeRequest.SetFunctionName("arn:aws:lambda:us-west-2:468131460318:function:sct_mail_20161103144602");
invokeRequest.SetInvocationType(InvocationType::RequestResponse);
InvokeOutcome invokeOutcome = client.Invoke(invokeRequest);
...

I receive an error:
Functions from 'us-west-2' are not reachable in this region ('us-east-1')
Region which is specified in the configuration is not used when working with lambda?
How to use region settings from config file?
EC2 instance,  Amazon Linux, AWS_SDK_VERSION_STRING "1.0.24"
Thanks!

You need to set the client configuration in your LambdaClient constructor. See Aws::Client::ClientConfiguration. If you want to load the config from your profile config file or from EC2 Metadata service, see: https://sdk.amazonaws.com/cpp/api/LATEST/class_aws_1_1_config_1_1_a_w_s_profile_config_loader.html

Here's a full writeup:
https://medium.com/@samstern_58566/how-to-use-cloud-firestore-on-aws-lambda-4bf6d3a473d9


Usage with Grape

Does anyone have experience using this and ng-token-auth with Grape? I'm looking to access the helpers such as current_user in my Grape endpoints.

I also have the same setup as you are. I am wondering where in the grape you have before and after blocks defined?
I know you mentioned /lib/api.rb but I don't have that file.

My app/api/api.rb:
class API < Grape::API
  format :json
  formatter :json, Grape::Formatter::ActiveModelSerializers
  logger Rails.logger

  mount ::V1::Base
end

My app/api/v1/base.rb:
require 'authenticated_request'

module V1
  class Base < Grape::API

    version 'v1', using: :path

    before do
      next if @resource
      @req = ::AuthenticatedRequest.new(
        uid:      request.headers['Uid'],
        token:    request.headers['Access-Token'],
        client:   request.headers['Client'],
        resource: @resource
      )
      @resource = @req.begin
      if @resource
        env['warden'].set_user(@resource, scope: :user)
      else
        h = {'Access-Control-Allow-Origin' => "*", 'Access-Control-Request-Method' => %w{GET POST OPTIONS}.join(",")}
        error!('You need to log in to use the app.', 401, h)
      end
    end

    mount V1::Something

    after do
      headers = @req.finish
      next if headers.nil?
      env['warden'].authenticate(scope: :user)

      headers.each{|k,v| header(k,v)}
      header 'Access-Control-Allow-Origin', "*"
      header 'Access-Control-Request-Method', %w{GET POST OPTIONS}.join(",")
    end
  end
end

The code from authenticated_request is pasted into app/lib/authenticated_request.rb
I hope that helps!

Thanks @rajaaa92!! When I get a chance, I'll add a Grape case to the test suite.
I don't have much Grape experience - let me know if there's anything this gem can do to provide better support for Grape.

this is so great, thanks for sharing @rajaaa92!

:+1:, it would be nice to use this w/ grape.

Hi everybody,
I created a gem that allows grape to authenticate using an existing devise_token_auth installation and rails app. Its called grape_devise_token_auth and you can also find an example setup of jToker + devise + devise_token_auth + grape_devise_token_auth here.

Hi again,
So I've created a full port of devise_token_auth for grape. It can be found here at grape_token_auth. This is different from the above gem in that it is purely dependent on grape and does not depend on rails, devise, or devise_token_auth.
I'm approaching an initial 0.1.0 release and I'd love it if @lynndylanhurley or @booleanbetrayal could give it a review and tell me what they think.
Cheers!

Fantastic work @mcordell! I'll make a note in the README that directs grape users to your project.

:+1:


KAFKA-12891: KIP-749 Add --files and --file-separator options to the ConsoleProducer (WIP)

Implementation of KIP-749
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

KIP-749 currently has only one binding vote and only one non-binding vote. Not enough to support us in having this change.

@guozhangwang @tombentley Could you kindly have a look when you are free? :)


Service page - featured case study block - BE

Link to Ticket
Description of Changes Made
This PR updates the ServiceStoryBlock so that it now includes a FeaturedCaseStudyBlock. It picks up from the work done in #60. Additional, the template and pattern library is updated to ensure everything works as before. The stylesheet is also updated to ensure that the featured image and logo are displayed -- Kudos to @chris-lawton for this (See e20aaad)
The Featured case study block allows content editors to

add a tagline
specify a work page or historical work page, which is used as the basis for both the featured case study image and logo (this can be overriden by the editor, as indicated in the next  item below)
specify optional image and logo to override what the specified page above provides
add optional rich text

Note
The Work Page is supposed to have a logo field. This is already being handled in #72, so here we just have a placeholder to prevent breaking the functionality:

https://github.com/torchbox/torchbox.com/blob/f429a8f0d93e5b3af0f51c8d73d58bf6248b9660/tbx/work/models.py#L167
How to Test

Create a Service Page
In the body StreamField, you should be able to add a Featured Case Study Block (with different combinations of link, tagline, text, image, logo), and it should render as expected on the template

Screenshots

Expand to see more

MR Checklist

[x] Add a description of your pull request and instructions for the reviewer to verify your work.
[x] If your pull request is for a specific ticket, link to it in the description.
[x] Stay on point and keep it small so the merge request can be easily reviewed.
[x] Tests and linting passes.

Unit tests

[ ] Added
[x] Not required

Documentation

[ ] Updated build docs
[x] Updated editor guidelines (https://docs.google.com/document/d/1PAWccdQ4tfaZsrEWmpDhvP3GH5RRmBOARFVp4b-kje8/edit?usp=sharing)
[ ] Not required

Browser testing

[x] I have tested in the following browsers and environments (edit the list as required)

Latest version of Chrome on Linux
Latest version of Firefox on Linux

Data protection

[ ] Not relevant
[x] This adds new sources of PII and documents it and modifies Birdbath processors accordingly

Accessibility

[ ] Automated WCAG 2.1 tests pass
[ ] Manual WCAG 2.1 tests completed
[ ] I have tested in a screen reader
[ ] I have tested in high-contrast mode
[ ] Any animations removed for prefers-reduced-motion
[x] Not required

Sustainability

[ ] Images are optimised and lazy-loading used where appropriate
[ ] SVGs have been optimised
[ ] Perfomance and transfer of data considered
[ ] If JavaScript is needed alternatives have been considered
[x] Not required

Pattern library

[x] The pattern library component for this template displays correctly, and does not break parent templates
[ ] The styleguide is updated if relevant
[ ] Changes are not relevant the pattern library

@engineervix sorry for the confusion in stand-up - this doesn't overlap with what I am working on at all, and does need to be merged.


ENG-740 Use Amplify Security Github Action

Updates workflow to use https://github.com/amplify-security/runner-action.

Oh wait, is juice-shop not added to prod anyway? I can just keep this workflow only on lab if we want to keep it that way (and have our other real projects on prod).

0: Failed to mint a run token from Amplify. Please ensure that this repository is configured in Amplify.

Yes juice-shop is not in prod because we use prod as a production environment for our application code. I completely forgot. Let's go ahead and remove the call to prod and just run it on lab.


Client-side image verification not detecting wrong file type

When submitting an image of a type which the system doesn't support, the server-side verification will reject it, but the client-side will not.

The validation in HTML is an accept="image/png,image/jpeg" attribute on the image upload form input and a file size check in JS, followed by a similar server-side check in PHP (but mostly based on extensions rather than MIME types). I don't have an example image to hand which caused this problem, so need to put this on hold til it happens again and I can find an image which triggers the problem.


bot not respond

after a few days working bot not respon to command
nothing change every thing stable but bot dont get command in telegram
btw colleting is ok

Hello, I've been running the bot on the server for almost 3 days now and it's been working fine, responding and collecting coins. In the update, I will try to optimize the code to solve any potential issues.


Limited passing second param in orWhereRaw

Laravel Version: 5.4.19

Description:
Why in method whereRaw second param is not strict array ($bindings = []), and in method orWhereRaw second param is strict array (array $bindings = [])?

Feel free to submit a PR 😄

This is an actual bug, why was this closed ? o_O
Leading to
FatalThrowableError
Type error: Argument 2 passed to Illuminate\Database\Query\Builder::orWhereRaw() must be of the type array, string given


Save container logs as artifacts and output linked container logs on failure

This adds a step at the end of the run process that will show the output of containers if the main command fails, or if any of those containers have non-zero exit codes.
Container output is uploaded as artifacts for easier viewing as well as the last 500 lines tailed in the output.

Nice!
I haven't had a chance to use it yet, but how big are container logs? I wonder if they're better piped to a .log file and uploaded as a build artifact? Or is putting it inline heaps nicer/faster for debugging? Or you we could tail the last 500 lines, and put the rest in a build artifact.
It'd be great to get this to the point that it could be onfail by default.

Yup, I think I'm going to make it always save container output as artifacts, and then tail -n 500 any of those logs where the container has failed.
This ditches any configuration and makes for sane behaviour I think. Thoughts @toolmantim?

Nice!
On third review, I think perhaps it might be too aggressive to always post the container logs as artifacts? It could be a lot of unnecessary artifact storage, and mess up people's own artifact counts. Perhaps only on failure?

Any objections to me merging this @toolmantim @sj26 ?


Center score in post-processing

Hi, I am looking into the post-processing code and most of the code seems logical to me. But I don't understand why the centers are of size [128, 128] this line. Shouldn't the center position relate to map size otherwise the center score will be greater than 1 sometimes?

I realized that the output from the models are fixed at 256


Feature: add search support for sha512

Summary
This commit introduces the possibility to search via sha512 digests. Example of how this could be useful is for the npm ecosystem. npm often relies on sha512 digests, and provenance attestations in intoto format may use sha512 digests as the subject. Subjects are extract during uploads and added as index keys, which are then stored in Redis. This feature lets the cli accept sha512 digests, and the server to accept them to use when searching in the Redis cache.
Signed-off-by: Fredrik Skogman<EMAIL_ADDRESS>Release Note
Rekor entries can now be searched by SHA512 digests (if they appear as subjects in an intoto attestation).
Documentation
Don't think so. The rekor cli help is updated for search.

Hm, I don't get any updates to the generated files when I'm running things locally. I'm using a mac, not Linux, but that shouldn't matter? The differences in the files are mostly on how the comments are formatted.
$ ./hack/tools/bin/swagger generate client -f openapi.yaml -q -r COPYRIGHT.txt -t pkg/generated --additional-initialism=TUF
$ ./hack/tools/bin/swagger generate server -f openapi.yaml -q -r COPYRIGHT.txt -t pkg/generated --exclude-main -A rekor_server --flag-strategy=pflag --default-produces application/json --additional-initialism=TUF
$ git status
On branch feat_search_sha512
nothing to commit, working tree clean

$ touch openapi.yaml
$ make
/Users/kommendorkapten/git/rekor/hack/tools/bin/swagger validate openapi.yaml
2022/10/21 13:53:05
The swagger spec at "openapi.yaml" is valid against swagger specification 2.0
...
CGO_ENABLED=0 go build -trimpath -ldflags "-X sigs.k8s.io/release-utils/version.gitVersion=v0.12.0-67-g39562d2 -X sigs.k8s.io/release-utils/version.gitCommit=39562d2a3e3d0133e3aa3a042b2882d83432691a -X sigs.k8s.io/release-utils/version.gitTreeState="clean" -X sigs.k8s.io/release-utils/version.buildDate=2022-10-21T11:30:17Z" -o rekor-server ./cmd/rekor-server
$ git status
On branch feat_search_sha512
nothing to commit, working tree clean

try make clean-gen followed by make?

Booted a linux container (ubuntu) and ran the commands:
$ uname -a
Linux 0f0cec2ab8f3 5.10.104-linuxkit #1 SMP PREEMPT Wed Mar 9 19:01:25 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
$ go version
go version go1.18.1 linux/arm64
$ make clean-gen && make
rm -rf dist
rm -rf hack/tools/bin
rm -rf rekor-cli rekor-server
rm -f *fuzz.zip
...
$ git status
On branch feat_search_sha512
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   hack/tools/go.sum

So no changes to the generated files, only the go.sum for the tool. Will dig deeper into what version(s) the runner is using.

the builder is using go 1.19.2 vs your ubuntu container using 1.18.1.
on my mac with go 1.19, when I do make clean && make i do get the changes shown in the CI test so I think its that.

and +1 to @asraa 's comment about adding a cli test, otherwise code LGTM

Great find @bobcallaway, thanks.
Yes, I'll add an cli test too as @asraa proposed!

Nice work!


EKF2 use solution status for publication and validity

See https://github.com/PX4/Firmware/pull/8771#issuecomment-383756360 for details.

Additionally using the solution status flags should remove the synchronization issues.

676 = 0b 1 0 1 0 1 0 0 1 0 0

677 = 0b 1 0 1 0 1 0 0 1 0 1

831 = 0b 1 1 0 0 1 1 1 1 1 1            <- good flight with GPS

551 = 0b 1 0 0 0 1 0 0 1 1 1            <- flight after GPS stopped

677 = 0b 1 0 1 0 1 0 0 1 0 1

	 j i h g f e d c b a

a 0 - attitude
b 1 - velocity_horiz
c 2 - velocity_vert
d 3 - pos_horiz_rel
e 4 - pos_horiz_abs
f 5 - pos_vert_abs
g 6 - pos_vert_agl
h 7 - const_pos_mode
i 8 - pred_pos_horiz_rel
j 9 - pred_pos_horiz_abs
k 10- gps_glitch
l 11- accel_error

I was also wondering about not publishing attitude until it's valid, but I suppose it's better than nothing. At a minimum I'll come back to it later as a condition for arming if you're in anything other than acro or manual.

This still isn't quite right. Should pos_horiz_rel be valid during the portion of flight after GPS was killed was the error was still under control?


Updated the README.md for fixing the lack of route in middlewares.

Ping @gabriel403
Closes #4

Thanks!


Update migration with down method

@Z3d0X faced an issue when I rollback my migration since it is missing down().
I would like to discuss and confirm the following enhancement with you.

add new config 'page-table-name'  => 'pages'
use above config in migration and model
If you agreed, I can create another PR for it.

* add new config `'page-table-name'  => 'pages'`

* use above config in migration and model
  If you agreed, I can create another PR for it.

Okay. You can  continue your work on this PR

@Z3d0X sorry for the delay. I have updated and pushed.


Fix: Resolve fuel code increment and row duplication order issue - #1303

This PR fixes the issue where the fuel code number does not increment after using the duplicate row function and ensures the duplicated row is placed below the existing record, caused by a conflict with #1446.
Closes #1303

@AlexZorkin Thank you for the code review! Do you think it would be a good idea to cover this with e2e tests? If so, should I create a new ticket for it?

Sure I will create a followup ticket.

Thank you, Alex!


Fetch as Google can't read ion-router-outlet ( router-outlet is read )

Ionic version:  (check one with "x")
[ ] 2.x
[ ] 3.x
[ x ] 4.x
I'm submitting a ...  (check one with "x")
[ x ] bug report
[ ] feature request
Current behavior:

We can know Google sends out a robot to scan the page using by Fetch as Google.
Fetch as Google can't read ion-router-outlet (Ionic v4 Routing Element).
Fetch as Google can read router-outlet (Angular Native Routing Element) .
If it keeps like this Ionic's PWA will be weak against SEO.

Expected behavior:

Fetch as Google can read ion-router-outlet (Ionic v4 Routing Element).

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (/Users/sakakibara/dev/ionic-cli/packages)

   @ionic/cli-utils  : 2.0.0-rc.5
   ionic (Ionic CLI) : 4.0.0-rc.5

local packages:

   @angular-devkit/core       : 0.6.0
   @angular-devkit/schematics : 0.6.0
   @angular/cli               : 6.0.0
   @ionic/schematics-angular  : 1.0.0-rc.5
   Ionic Framework            : @ionic/angular 4.0.0-alpha.3

System:

   NodeJS : v8.9.3
   npm    : 5.8.0
   OS     : macOS High Sierra

Sorry. This was problem of polyfills.
import 'core-js/es6/symbol';
import 'core-js/es6/object';
import 'core-js/es6/function';
import 'core-js/es6/parse-int';
import 'core-js/es6/parse-float';
import 'core-js/es6/number';
import 'core-js/es6/math';
import 'core-js/es6/string';
import 'core-js/es6/date';
import 'core-js/es6/array';
import 'core-js/es6/regexp';
import 'core-js/es6/map';
import 'core-js/es6/weak-map';
import 'core-js/es6/set';


Use dashing on dashing branch

Signed-off-by: Lander Usategui<EMAIL_ADDRESS>

LGTM.

Following at https://github.com/AcutronicRobotics/gym-gazebo2/pull/34


Regression: 1.15.2 SIGSEGVs when run on Wayland unless started with SDL_VIDEODRIVER=x11

I'm upgrading the Fedora packaging to 1.15.2, and when testing the local builds, noticed this SIGSEGV.
Relevant part of the gdb session:
Thread 1 "lagrange" received signal SIGSEGV, Segmentation fault.
0x00007ffff79accaf in XInternAtom (dpy=dpy@entry=0x5555556cd690, name=name@entry=0x555555631c6f "_GTK_THEME_VARIANT", onlyIfExists=onlyIfExists@entry=0) at /usr/src/debug/libX11-1.8.1-2.fc37.x86_64/src/IntAtom.c:175
175	    LockDisplay(dpy);
(gdb) bt
#0  0x00007ffff79accaf in XInternAtom
    (dpy=dpy@entry=0x5555556cd690, name=name@entry=0x555555631c6f "_GTK_THEME_VARIANT", onlyIfExists=onlyIfExists@entry=0)
    at /usr/src/debug/libX11-1.8.1-2.fc37.x86_64/src/IntAtom.c:175
#1  0x0000555555584016 in setDarkWindowTheme_SDLWindow (setDark=true, d=<optimized out>)
    at /usr/src/debug/lagrange-1.15.2-1.fc37.x86_64/src/x11.c:39
#2  handleCommand_X11 (cmd=<optimized out>) at /usr/src/debug/lagrange-1.15.2-1.fc37.x86_64/src/x11.c:51
#3  handleCommand_X11 (cmd=<optimized out>) at /usr/src/debug/lagrange-1.15.2-1.fc37.x86_64/src/x11.c:47
#4  processEvents_App (eventMode=<optimized out>) at /usr/src/debug/lagrange-1.15.2-1.fc37.x86_64/src/app.c:2111
#5  0x000055555561e623 in init_App_.constprop.0 (argc=<optimized out>, argv=<optimized out>, d=<optimized out>)
    at /usr/src/debug/lagrange-1.15.2-1.fc37.x86_64/src/app.c:1341
#6  0x0000555555577941 in run_App (argv=0x7fffffffdf98, argc=1) at /usr/src/debug/lagrange-1.15.2-1.fc37.x86_64/src/app.c:2404
#7  main (argc=1, argv=0x7fffffffdf98) at /usr/src/debug/lagrange-1.15.2-1.fc37.x86_64/src/main.c:90

When started as SDL_VIDEODRIVER=x11 lagrange it works fine; lagrange 1.14.2 works fine in Wayland

I can confirm that compiling with -DENABLE_X11_XLIB:BOOL=NO mitigates the issue

I should add some runtime checks to detect if Wayland is in use and change the behavior accordingly.

Could you give v1.15.9 a try and see if the situation has improved? At least in my testing, things work better on Wayland.


How much data is used to finetune the model on segmentation task?

Great work!
From this page, there some instruction about preparing data for segmentation.
https://github.com/Beckschen/ViTamin/blob/main/vitamin_fcclip/GETTING_STARTED.md
So your model also needs to be finetuned to do segmentation task, right?
I want to know if you use all the segmentation dataset mentioned https://github.com/Beckschen/ViTamin/blob/main/vitamin_fcclip/datasets/README.md to finetune your model? Or you just finetune the model on a subset? And show great open-vocabulary capability?
Looking forward to your reply!

Thanks for your interests!
(1) For the first question "So your model also needs to be finetuned to do segmentation task":
We transfer our ViTamin models to open-vocabulary segmentation tasks, keeping the ViTamin frozen as the CLIP image encoder. Consequently, the ViTamin model remains unchanged during the transfer to the segmentation tasks.
What does the Frozen mean? Please refer to the paper: "Convolutions Die Hard: Open-Vocabulary
Segmentation with Single Frozen Convolutional CLIP" (https://arxiv.org/pdf/2308.02487.pdf)
(2) For the second question "if you use all the segmentation dataset mentioned":
Following FC-CLIP paper, we only train the open-vocab segmentation model on coco dataset and zero-shot evaluate it on the other datasets.

Thanks for your interests! (1) For the first question "So your model also needs to be finetuned to do segmentation task": We transfer our ViTamin models to open-vocabulary segmentation tasks, keeping the ViTamin frozen as the CLIP image encoder. Consequently, the ViTamin model remains unchanged during the transfer to the segmentation tasks. What does the Frozen mean? Please refer to the paper: "Convolutions Die Hard: Open-Vocabulary Segmentation with Single Frozen Convolutional CLIP" (https://arxiv.org/pdf/2308.02487.pdf)
(2) For the second question "if you use all the segmentation dataset mentioned": Following FC-CLIP paper, we only train the open-vocab segmentation model on coco dataset and zero-shot evaluate it on the other datasets.

Thank you so much for your early reply!
May I know how many epochs the model is trained on COCO dataset?
Thank you!

I am happy to answer this! The training pipeline is here. We follow FC-CLIP and adopt the same training recipe and losses without any special
design. The training batch size is 16, and the model is trained for 50 epochs on COCO panoptic training
set.

Let me know if you have further questions.


Update grpc error codes in Kingdom Internal Services

Parent not found -> FAILED_PRECONDITION  and furthermore have PreconditionFailure set in the error details (see https://github.com/googleapis/api-common-protos/blob/37d5125da5c90f2124d15908a54a32ed3f470bc2/google/rpc/error_details.proto#L140)
self not found -> NOT_FOUND
some resource other than parent or self not found -> INVALID_ARGUMENT

some resource other than parent or self not found -> INVALID_ARGUMENT

I think this would still be FAILED_PRECONDITION. As per Status codes and their use in gRPC, INVALID_ARGUMENT is for when the arguments are incorrect regardless of the state of the system (e.g. some field is malformed or missing). In this case, the arguments could be correct if the entity with the given ID already existed. The fact that we don't allow user-specified IDs for creation is a separate matter.


Correct parsing of chains of < and <=

Parsing a chain of comparison operators, such as 1 <= x < 10 is a quite natural thing for humans to do. However, how to best represent this doesn't seem quite as clear cut to me. Which of the <= and < signs comes first? Or should we somehow encode that they're at the same level? Or..?
For the record, this is what the compute-engine currently does. It's a bit inconsistent.

That's a great question...
One option would be to parse this as ['And', ['LessEqual', 1, 2], ['Less', 2, 3'], ['LessEqual', 3, 4]]...

True, that would work. The only downside is that one ends up losing the information about the 2 being the same value in ['LessEqual', 1, 2], ['Less', 2, 3'].
I did ask someone who works a lot more with compilers than I do:

their response was the following
class BinaryOp : Node {
  lhs : Node
  rightHands : List<(Operator, Node)>
}

BinaryOp(Const(0), [(LessEq, Var("a")), (Less, Var("b")), (LessEq, Const(10))])

This isn't immediately applicable to MathJson, but I still wanted to mention it.

That could be ['Inequality', 0, ['LessEqual', a], ['Less', b], ['LessEqual', 10]]. It could work, but it introduces a completely new function, so it's something that needs to be handled. And it also uses somewhat weird single-operand inequalities. But then what does ['Less', b] mean on its own?
Another option, ['And', ['LessEqual', 0, a], ['Less', b], ['LessEqual', 10]]. But it would make And non-commutative, so that's a non-starter...

That could be ['Inequality', 0, ['LessEqual', a], ['Less', b], ['LessEqual', 10]]. It could work, but it introduces a completely new function, so it's something that needs to be handled. And it also uses somewhat weird single-operand inequalities. But then what does ['Less', b] mean on its own?
Another option, ['And', ['LessEqual', 0, a], ['Less', b], ['LessEqual', 10]]. But it would make And non-commutative, so that's a non-starter...

The upper could be justified by taking a page out of functional programming and going "partial functions are fineeee". As in, ['LessEqual', a] could literally be <= a. [1] It is most certainly odd for comparison operators.
With addition, multiplication and more it looks a bit less surprising in my opinion.
['Sum', 0, ['Add', 7], ['Subtract', 5]]
[1] Or it could be a <=, depending on the convention.

I realized that Mathematica has the same problem. So clearly, it would make sense to check what they're doing.
The following piece of code
SetAttributes[fullFormString, HoldAll];
fullFormString[expr_] := ToString[Unevaluated @ FullForm[expr]]
fullFormString[1<x<=k]

(Source: https://mathematica.stackexchange.com/a/152438 )
returns
Inequality[1, Less, x, LessEqual, k]

Which seems like a rather reasonable way of doing it in the compute engine. I guess functions would have to be wrapped in brackets or something, so that they can be distinguished from variables.
["Inequality", 1, ["Less"], "x", ["LessEqual"], "k"]

Yes, that could work as well.
BTW, ["Less"] is a valid MathJSON expression: it's the partial application of the Less function to no arguments (["Less", 0]  is the partial application of the Less function)

Hello, I found some inconsistencies in basic usage:

So far okay, great work.
Here it starts to get weird.

Latex formula shows some problem, but parsing still works.

And here it does not parse at all.
To be complete:

Another strange behaviour is here:

["LessEqual", ["LessEqual", 0, "b"], 3]
["LessEqual", 0, "b"] result of this should be boolean value so am I comparing True <= 3?

Right so I started from a place I got 'unexpected-argument'
https://github.com/cortex-js/compute-engine/blob/aa49d8b0099b2c47e4bd0a0d5dcaa75e74f40f6e/src/compute-engine/boxed-expression/validate.ts#L362
And I get here because here:
https://github.com/cortex-js/compute-engine/blob/aa49d8b0099b2c47e4bd0a0d5dcaa75e74f40f6e/src/compute-engine/boxed-expression/boxed-function.ts#L764
signature of the function does not have defined canonical.
So I went here where I can see that from the main comparison operators this one is the only one that does not have set 'canonical'.
https://github.com/cortex-js/compute-engine/blob/aa49d8b0099b2c47e4bd0a0d5dcaa75e74f40f6e/src/compute-engine/library/relational-operator.ts#L125
Like for example here canonical is
https://github.com/cortex-js/compute-engine/blob/aa49d8b0099b2c47e4bd0a0d5dcaa75e74f40f6e/src/compute-engine/library/relational-operator.ts#L153
So I guess fix would be to use canonical from GreaterEqual just not use reverse on args
canonical: (ce, args) => ce._fn('LessEqual', args),
@arnog
Hope it helps.

You're correct, there was a missing canonical handler. It has now been added. I have also fixed it so that chained relational operators get decomposed into boolean expressions, and so that they correctly compile to JavaScript.