Custom resource does not delete the resources created in another namespace - No ownerReferences set

Bug Report

What did you do?

step 1: I created a sample memcached-operator via the operator-sdk using ansible.
Used the below commands
mkdir memcached-operator
cd memcached-operator
operator-sdk init --plugins=ansible --domain=example.com
operator-sdk create api --group cache --version v1 --kind Memcached --generate-role
Basically I followed the steps listed in quickstart
step 2:
Just to simplify things, I gave cluster-admin ClusterRole to my operator in "ClusterRoleBinding" as shown below
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: manager-rolebinding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
kind: ServiceAccount
name: default
namespace: system
step3: I used the below tasks in my Ansible role (under tasks/main.yml)

name: create busybox namespace
community.kubernetes.k8s:
state: present
resource_definition: "{{ lookup('template', 'mywfns.yml') | from_yaml }}"
name: create busybox deployment
community.kubernetes.k8s:
state: present
resource_definition: "{{ lookup('template', 'mywfdeploy.yml') | from_yaml }}"
name: create service
community.kubernetes.k8s:
state: present
resource_definition: "{{ lookup('template', 'mywfservice.yml') | from_yaml }}"
debug:
msg: operatername {{ ansible_operator_meta.name }} operaternamespace {{ ansible_operator_meta.namespace }}

step4: I created the Custom Resource in a different name space than the resources created in "step3" above
My Custom Resource namespace is "mytest-ns" and all my Resources in the "step3" above are created in "sample3-ns" namespace
step5: I now delete the Custom Resource in namespace "mytest-ns", the resources in step3 are not cleaned up. I also do not see any "ownerReferences" section attached to any of my resources created in step3 - I am guessing that is why those are not getting deleted.
What did you expect to see?

I expect the resources created by my custom resource in a different namespace to be deleted as soon as I delete my custom resource which is in a different namespace.
What did you see instead? Under which circumstances?

The resources created by my custom resource  are not deleted. This works if these resources are created in the same namespace as the custom resource,
Environment
Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic
Operator type:

/language ansible

Kubernetes cluster type:

minikube version: v1.5.2
commit: 792dbf92a1de583fcee76f8791cff12e0c9440ad-dirty
$ operator-sdk version

operator-sdk version: "v1.2.0", commit: "215fc50b2d4acc7d92b36828f42d7d1ae212015c", kubernetes version: "v1.18.8", go version: "go1.15.3", GOOS: "linux", GOARCH: "amd64"
$ go version (if language is Go)

$ kubectl version

Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Possible Solution

Additional context

memcached-operator.zip

@jayeshnazre ownerReferences aren't actually supported across namespaces, if you want to clean up cluster-level, other-namespaced or otherwise external resources you need to do it manually using a finalizer.


reflective compilation has failed: '=' expected but eof found in 0.13.7-M3

It appears that defining multiple projects in a single line lazy val a, b = project is broken in 0.13.7-M3. It works fine in 0.13.6 (and I'm sure worked fine in 0.13.7-M3 today, but just out of the sudden stopped).
The messages are:
➜  jacoco4sbt-root-no-sources  xsbt
JAVA_HOME=/Library/Java/JavaVirtualMachines/java8/Contents/Home
SBT_OPTS= -Xms512M -Xmx1536M -Xss1M -XX:+CMSClassUnloadingEnabled -Dfile.encoding=UTF-8
[info] Loading global plugins from /Users/jacek/.sbt/0.13/plugins
[info] Updating {file:/Users/jacek/.sbt/0.13/plugins/}global-plugins...
[info] Resolving org.fusesource.jansi#jansi;1.4 ...
[info] Done updating.
[info] Loading project definition from /Users/jacek/sandbox/jacoco4sbt-root-no-sources/project
[info] Updating {file:/Users/jacek/sandbox/jacoco4sbt-root-no-sources/project/}jacoco4sbt-root-no-sources-build...
[info] Resolving org.fusesource.jansi#jansi;1.4 ...
[info] Done updating.
[error] [/Users/jacek/sandbox/jacoco4sbt-root-no-sources/build.sbt]:2: reflective compilation has failed:
[error]
[error] '=' expected but eof found.
Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore?

When I change project/build.properties to sbt.version=0.13.6 it works fine.

You broke this with no deprecation period from 0.13.6 to 0.13.7. If that's an option, why such gyrations for backward compatibility in other cases? If it isn't, then on what basis was it done?

@paulp Our effort in keeping the bincompat across 0.13.x I think is primarily for published plugins.
We do care about builds, and if possible we would've kept source-level backward compatibility of the builds. But I think we couldn't when we switched to using Scala compiler to parse build.sbt for whitespace. So the workaround was to fail the build from loading when we detect pattern on lhs.

I wonder how many thousands of man-years could have been saved (this is not hyperbole) by having working source positions in the compiler. Oh well, carry on.

@paulp I'd give my left elbow for working source positions.... but in this case, we did the damage to ourselves.   The reason we can't use the original source position is around refactoring of settings, and the reason we even care about "val x,y = ...." is because we haven't gone hole-hog into owning the parser ourselves, we're still in half-donkey, half-man land.  Sorry for the breakage.  We didn't make the decision lightly and we hope to never have changes like this.   In reality, it's always a balance of "never break things" and "improve things".   Hopefully the improvement outweighs (dramatically) the breakage.   Additionally, you can turn off the new parser to get the old behavior if needed.

The ability to omit blank lines would be worth it even if it came with ten new bugs injected into each project.


"az ml compute attach" fails with "*** unsupported compute type ***"

Trying to add an Azure-Arc connected EKS cluster. Extension already installed.
az ml compute attach --name K8S_CLU_NAME --resource-group RG_NAME --workspace-name AZUREML_WS_NAME --resource-id /subscriptions/SUBS_NAME/resourceGroups/AZUREML_RG_NAME/providers/Microsoft.Kubernetes/connectedClusters/K8S_CLU_NAME --type kubernetes --namespace azureml-default --identity-type SystemAssigned -o json
...
{
  "id": "/subscriptions/SUBS_NAME/resourceGroups/RG_NAME/providers/Microsoft.MachineLearningServices/workspaces/AZUREML_WS_NAME/computes/K8S_CLU_NAME",
  "location": "westeurope",
  "name": "K8S_CLU_NAME",
  "provisioning_state": "Succeeded",
  "resourceGroup": "RG_NAME",
  "resource_id": "/subscriptions/SUBS_NAME/resourceGroups/AZUREML_RG_NAME/providers/Microsoft.Kubernetes/connectedClusters/K8S_CLU_NAME",
  "type": "*** unsupported compute type ***"
}

Target cluster k8s is 1.21
$ az version
2.34.1  2.34.1  1.0.6

$ az extension list
False   whl     connectedk8s    /Users/USERNAME/.azure/cliextensions/connectedk8s False   1.2.7
False   whl     azure-iot       /Users/USERNAME/.azure/cliextensions/azure-iot    False   0.13.0
False   whl     k8s-extension   /Users/USERNAME/.azure/cliextensions/k8s-extension        False   1.0.4
False   whl     storage-preview /Users/USERNAME/.azure/cliextensions/storage-preview      True    0.8.1
False   whl     ml      /Users/USERNAME/.azure/cliextensions/ml   True    2.1.2
True    whl     account /Users/joaocc/.USERNAME/cliextensions/account      False   0.2.2

Also tried with az ml compute attach kubernetes ... (as per some of the the documentation) but CLI didn't recognize it.
Will try adding via WebUI, but would still like to be able to do everything by command line.

Update: strangely enough, compute cluster appears as correctly added in AzureML web UI.

@joaocc , the compute attach can work will from CLI. but the returned warning message is strange. If you attach from CLI, and go to portal to check, you can find the compute can attach successfully. We are working to fix that.

The the compute attach can work in both cli and UI.

Thanks. It is indeed working, despite the message. Cheers


[Integration logo AMD] - Logo is out of proportion

Description

Current state
Link: 260+ Built-In Integrations
Section under "260+ Built-In Integrations"
Currently, the AMD integration logo looks out of proportion.
Desired state

Adjust the proportions of the logo to accurately reflect the original design.
Note: It might be required that the shape the logo image is placed on remain as a square.
Screenshots
Before

After

Enviroment:

OS: Mac Linux Windows
Browser: Chrome Safari Firefox
Version:
Device: Desktop Mobile

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I would like to work on this .PLease assign it to me

@sandramsc  I've made some adjustments to the CSS and image is now centred vertically within the .card-front div and maintains its aspect ratio. Can you confirm if this the desired result? Can you assign me this issue, please?
Thanks!

You should be working once your assigned the issue.Its just really not appropriate

My intention was to offer a potential solution and demonstrate the desired outcome to facilitate a productive discussion around the task. I'm committed to contributing once assigned the issue. If there's anything specific you'd like me to address or if you have any concerns, please let me know.

@surajvast1 I have assigned this issue to you, as you were the first to comment requesting assignment.
Thank you, @Aseem22, for your well-intentioned approach in getting the issue assigned to you and for proposing a potential solution. This aligns with the guidelines outlined in the CONTRIBUTING.md - Working on an Issue (point 2. iii).

If the currently assigned contributor is willing to collaborate on implementing the solution, perhaps the two of you could work together?"


[UWP] return Warnings/Errors that ocurr during parsing/rendering

UWP renderer should return parse warnings/errors and rendering warnings/errors as part of the returned RenderedAdaptiveCard

Implemented in #950


⚠ SceneTime has degraded performance

In e6bf5b6, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1238 ms

Resolved: SceneTime performance has improved in 2e7bb56 after 9 minutes.


Setup CPack-based packaging for raygui

I'm not a fun of CMake, no plans to support CPack

no plans to support CPack
closed this as completed

Shouldn't it be closed this as not planned then?

not a fan of CMake

Noone is a fan of CMake, but it is currently the best build system available with own killer features.


Make gRPC communication between Posidon & Firmament secure.

We will revisit this issue at a later time. Closing this for now, will reopen it at a later time.


updated qlcolorcode (2.0.7)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Needs an appcast update

The appcast checkpoint was already updated in #20574, but without updating the version.


env file missing

Build stops because one of the files is missing
root@218497:/opt/apt-cacher-ng# docker compose up -d
open /opt/apt-cacher-ng/env: no such file or directory

File ls
root@server:/opt/apt-cacher-ng# ls -la *env*
ls: cannot access '*env*': No such file or directory
root@218497:/opt/apt-cacher-ng#

Git info
root@server:/opt/apt-cacher-ng# git log --name-status HEAD^..HEAD
commit 8b0b48d95d8314983990bf2e87e74678d343b88e (HEAD -> master, origin/master, origin/HEAD)
Author: Muhammad Hussein Fattahizadeh<EMAIL_ADDRESS>Date:   Sun Jul 17 11:44:58 2022 +0430

    feat: add bind address

you can simple add .env file for your application.
touch .env
# or
echo "ENVNAME=ValueForApp" > .env

then start the container.
It's best practice to git ignore .env file
 .env

This is not a problem for me. I just pointed out that the build is not possible because this file is not in the repository right now.
Maybe you should add an empty file so other users don't have problems with launching it right away? ;)

First, this repo automatically build using GitHub action so there is no build task. just pull and run the image.
In most cases .env file must not be part of git repo . https://stackoverflow.com/questions/43664565/why-do-people-put-the-env-into-gitignore
there is serveral way to handle this problem.

simply add .env file during docker-compose up as i describe before.
comment env_file directive in https://github.com/aasaam/apt-cacher-ng/blob/master/docker-compose.yml#L8
?

what's your suggestion?

I have known about .env best practice ;)
I would choose the second option and then anyone who uses your repository would have no problems at all and everything would start from 1 command ;)
Since it is not an error in the code / configuration - I think we can close this issue.


Add an RSS feed

There can an RSS containing all posts.
(Can optimize the SEO)

I like this suggestion and already have a branch feature/feed build out with the necessary classes to accomplish this. There's one problem though:
Canvas doesn't "know" about how posts are routed from the frontend. The link value in each <entry> in the feed itself needs to be an absolute path to where the post can be publicly viewed.
So, the only viable solution I can see is passing some sort of config variable to serve as the path prefix.
That would make it so, for example:

Jim structures his frontend routes like www.athlead.com/posts/post-slug
Pam structures her frontend routes like www.theartinstitute.com/post-slug

However, Dwight wants his to look more personalized to himself:

He structures his routes like www.schrutefarms.com/dwight/post-slug
And his brother also blogs on his platform at www.schrutefarms.com/mose/post-slug

When it's a dynamic routing structure, even a config variable passed to Canvas won't do the job.
I'd really like to see this feature as a part of the package, but until I find a solution that will work for all these scenarios, and more, it's stuck where it is.

Maybe of interest to you  : https://www.tastethecode.com/adding-rss-to-any-laravel-site

Even I use Canvas with my Laravel Blog and I have written an whole article on it. You might find it very useful https://stackcoder.in/posts/how-to-generate-rss-feeds-in-php-larvel

@austintoddj I know it might be bit over asking from you.
Since many of them will have issues with generating RSS Feeds and Sitemap Can you please include my article links in the documentation.
Not only mine. But any other article/packages links which can help to grow the Canvas Community. I am damm sure many of them will surely find the articles/packages very useful

@austintoddj Я знаю, что это может быть немного больше, чем просить от вас.
Поскольку многие из них будут иметь проблемы с созданием RSS-каналов и карты сайта, пожалуйста, включите ссылки на мою статью в документацию.
И не только моя. Но любые другие статьи/пакеты ссылок, которые могут помочь расширить сообщество Canvas. Я чертовски уверен, что многие из них наверняка найдут статьи / пакеты очень полезными

This works with the link view domain.com/username/feed ?

@prodigital-design yea it does

Closing in lieu of #923.

Closing in lieu of #923.


Added capability of detecting the platform

Fixes #133 by implementing a way of detecting when we are running in OpenShift. If a "route" resource cannot be found, we assume we are running in Kubernetes.
When running in OpenShift, this is th expected output:
$ make run
customresourcedefinition.apiextensions.k8s.io/jaegers.io.jaegertracing created
INFO[0000] Go                                            arch=amd64 os=linux version=go1.11.1
INFO[0000] operator-sdk                                  version=v0.4.1
DEBU[0000] Attempting to auto-detect the platform
INFO[0000] Auto-detected the platform                    platform=openshift

And this is the expected output for Kubernetes:
$ make run
customresourcedefinition.apiextensions.k8s.io/jaegers.io.jaegertracing created
INFO[0000] Go                                            arch=amd64 os=linux version=go1.11.1
INFO[0000] operator-sdk                                  version=v0.4.1
DEBU[0000] Attempting to auto-detect the platform
INFO[0000] Auto-detected the platform                    platform=kubernetes

This PR also removes the content about --platform=openshift, which is still available to override the auto-detect routine.

This change is


Button onClick causes ember proxy socket hangup

Describe the bug
I have a login form that I'm using with ember-simple-auth and ember-simple-auth-token.  When I click the login button, ember-simple-auth-token sends a POST to the server to validate the user's credentials and the EmberJS proxy is crashing because of:
Error: socket hang up
    at createHangUpError (_http_client.js:335:17)
    at Socket.socketCloseListener (_http_client.js:376:25)
    at Socket.emit (events.js:201:15)
    at TCP.<anonymous> (net.js:586:12)

I think the underlying problem is related to ember-elements because I added a basic html button and  when I click the basic button, the POST works.  I also tried running without the Ember proxy and it still crashes - you just don't get the stack trace like you do when running with the proxy.
To Reproduce
Steps to reproduce the behavior:

Create a login form that uses ember-simple-auth and ember-simple-auth-token

<form class="login-form">
  <FormGroup @label="User Name">
    <InputGroup @placeholder="" @value={{this.userId}} @onChange={{action (mut this.userId)}}/>
  </FormGroup>

  <FormGroup @label="Password">
    <InputGroup @placeholder="" @type="password" @value={{this.password}} @onChange={{action (mut this.password)}}/>
  </FormGroup>

  <div class="login-button">
    {{!-- Using this button fails --}}
    <Button @intent="primary" @onClick={{action "login"}}>Login</Button>
    {{!-- Using this button works --}}
    <button {{action "login"}}>Login</button>
  </div>
</form>

Desktop (please complete the following information):

OS: macOS
Browser Chrome
Version 73.0.3683.103

Here is a bit more info ... I enabled breakpoints on caught exceptions in the debugger and it triggers in ember-fetch when using the elements button, but not when using the plain html button.  Here is where it triggers:

@BryanHunt what is the version of ember-cli and npm

I'm using ember-cli 3.9.0 and yarn 1.15.2.

@BryanHunt I have tested  ember-simple-auth and ember-simple-auth-token in new ember app with help of ember http-mock server . There is no problem with Button component. Please join our Slack group to talk to us

I think I need an invite to the slack group.

@BryanHunt  Please join our Slack group here.

Try this: https://github.com/BryanHunt/test-login
yarn install
ember s

If you click the plain html button, you should get a 404.  If you click the elements button, the page should reload.

For anyone else landing here ...
It turns out that doing:
<form>
  <Button @onClick={{action "login"}}>Login</Button>
</form>

is very bad.  The better way (and working way) is:
<form {{action="login" on="submit"}}>
  <Button @type="submit">Login</Button>
</form>


Fix various races

Fixes #139
@mattbostock

Thanks! Apologies I wasn't able to help review this due to lack of time this week.


Remove fixed dependency to xUnit in Development.Facts

Development.Facts should use the approach Development.Specs uses to select the correct xUnit version. Fail the build if more than one version is found

runner is included in development nuget package.


Whether to consider add the settings of evaluated symbol changes?

Current is { and }, but sometimes conflict with other libraries.

This is duplicate to #171. Closing this one. Thanks!

@rwu823: this is now fixed and will be released soon.


indexer: add method to lookup event from selector

Current dependencies on/for this PR:

main

PR #62   👈

This stack of pull requests is managed by Graphite.


GCM Message Failing in Push Example Failing to Reach the Service Worker

This sample: https://github.com/GoogleChrome/samples/tree/gh-pages/push-messaging-and-notifications
I've double-checked this.
I've added -v to the curl command and confirmed that GCM is returning 200 OK. I've put a break point in the first line of onpush and confirmed that it's never reached.

I just went through the full steps of registering an API key, configuring the local copy of the sample, etc. The curl step did trigger the notification for me, so I can't reproduce what you're seeing:

CC: @gauntface in any case, but it does look like the code can work given the proper configuration. Can you double-check your API key in config.json, API project number in the manifest.json, etc.?

@jpmedley How long did you wait from subscribing for push and receiving the push message?
Also what version of Chrome is this on?

Version:
Google Chrome	45.0.2454.99 (Official Build) (64-bit)
Revision<PHONE_NUMBER>a50e4f7e90fec49a3eb1796454618b-refs/branch-heads/2454@{#492}
OS	Mac OS X
Blink	537.36 (@202530)
JavaScript	V8 <IP_ADDRESS>
Flash	<IP_ADDRESS>
When I run curl, sometimes I get this back:

Unauthorized

Unauthorized
Error 401

Sometimes this:
{"multicast_id":7341722821521375837,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1443051876229708%2b9bbb26f9fd7ecd"}]}
In no case do I get message.
(Incidentally, If I'd gotten these two days ago, I would've suspected a GCM problem and never filed the ticket.)

@jeffposnic I triple-checked the key and number. I even generated a new key and triple-checked that.
@gauntface I'm not sure what you mean by 'how long did I wait'. Shouldn't it work immediately? It did when I used this demo last spring.

@jpmedley is this still an issue for you? If so, maybe we should debug things over a screen sharing session. I'm hopeful that it's not a widespread issue with the sample.

I've added retesting to my to-do list.
Joe Medley | Technical Writer, DevPlat |<EMAIL_ADDRESS>|<PHONE_NUMBER>
On Mon, Dec 7, 2015 at 8:24 AM, Jeffrey Posnick<EMAIL_ADDRESS>wrote:

@jpmedley https://github.com/jpmedley is this still an issue for you?
If so, maybe we should debug things over a screen sharing session. I'm
hopeful that it's not a widespread issue with the sample.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleChrome/samples/issues/211#issuecomment-162576213
.

After running though this with @jpmedley, we've come to the conclusion that it's something odd about his Chrome settings, rather than an issue with the code. He's able to use the code successfully when testing with a Chrome Canary instance, which has its own separate settings.


Fix: Vim crashes when passing non dict value to job-option 'env'

Repro steps
vim --clean
:call job_start('echo', {'env': 1})

Cause and Solution
https://github.com/vim/vim/blob/25a6e8a769aa1c0d308b5f871132961f37986d0a/src/channel.c#L4795-L4802
We have to check if the type of item is dict.

Codecov Report

Merging #2765 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2765      +/-   ##
==========================================
- Coverage    75.2%   75.19%   -0.01%
==========================================
  Files          92       92
  Lines      134307   134309       +2
==========================================
- Hits       101003   100996       -7
- Misses      33304    33313       +9

Impacted Files
Coverage Δ

src/channel.c
83.25% <100%> (+0.02%)
:arrow_up:

src/if_xcmdsrv.c
83.63% <0%> (-0.54%)
:arrow_down:

src/os_unix.c
55.06% <0%> (-0.18%)
:arrow_down:

src/term.c
60.47% <0%> (-0.06%)
:arrow_down:

src/gui.c
47.73% <0%> (-0.06%)
:arrow_down:

src/gui_gtk_x11.c
47.73% <0%> (-0.05%)
:arrow_down:

src/if_py_both.h
76.59% <0%> (-0.01%)
:arrow_down:

src/terminal.c
68.61% <0%> (+0.04%)
:arrow_up:

Continue to review full report at Codecov.

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


Practice mode 1: randomly blur words

At the click of a button, a certain number of words (say, 3) should randomly be selected to be blurred out. The user can click this button multiple times to blur additional sets of words.
Each blurred word is equal in length to the original word. This can best be done by simply underlining the word and changing font color to match background color.
Clicking (or perhaps hovering? For a second?) momentarily reveals the word. Clicking it a second time blurs it. Clicking a different blurred word reveals it and blurs the previously revealed word. If a word is revealed when clicking the "blur" button, it becomes blurred again in addition to the new set of blurred words.
A Reset button should always be visible, but secondary to the Blur button. Clicking it will reveal all the words again. This allows the user to restart, blurring a probably different set of words each time. When all words are blurred, the "blur" button is hidden/grayed out and the "reset" button becomes more visually significant to reflect that it is now the primary action.
Do not blur punctuation. Just alphanumeric characters. Punctuation is helfpul in memorization, and blurred punctuation could be mistaken for an additional letter at the end of a word ("hi, " should not become "___ " because that is much wider than the word "hi" that it represents).
Not actually required: visual blurring. "Blurred" words could be replaced with, say, underscores or a solid-colored span.

Implemented in aeb88e9.


Random prop/tree collections

Summary
Ability to create a collection of props or trees, and then be able to replace a prop or tree with that collection - one of the items would be chosen at random each replacement.
It's similar to replacement packs, but just defining a collection of replacements (rather than a specific mapping A -> B)
Example use case:
I want to customise the foilage along macwelshman's Rural Roads, of which there are several. By default these roads use deciduous trees, but those look out of place when the road is going through a huge pine tree (evergreen) forest.
So I want to replace the road's trees with various "scrub" trees from Pine Scrub Pack.
I could create a collection "Pine Scrub", add the trees from the scrub pack, set their probabilities, and then just use that collection as if it were a tree when defining replacemetns.
Note that it would be ideally be random per tree/prop, not per segment/building, otherwise repetition would be very obvious even within a single segment (based on my current testing). For example, see Klyte's "Prop Replacer" mod which allows "Fully Random" replacements as alternative to per-segment/building seed.
Another example is I could create a collection of map-themed trees to use in buildings, then not have to worry about choosing specific tree when replacing vanilla trees in my buildings. Same sort of thing with props, I could just bundle, for example, a load of residential garden props in to a collection and have low density residential buildings use those.
How it could work:

Create collection button - user specifies collection name and type (tree or prop)
Select which trees/props go in the collection
Save collection
Collections then appear in the replacements list alongside normal trees/props (as applicable)

Eg. if replacing a tree, the list in right panel would include collections ( maybe in different colour so they stand out )
Maybe even allow collections within collections (with recursion prevention)?

Eg. I could create small collections of trees, then bundle those in to a 'forest' collection

Could possibly make tree collections available for use in forest brush and vice versa?

Would need some way to edit collections (eg. if I want to add/remove trees to/from my pine scrub collection)

When collections are edited, refresh replacements using it city-wide

Note: Doesn't need to be called a "Collection", could be a "Asset Pack" or "Group" or whatever

Some notable benefits:

I can put assets from different authors / assets in to a collection
Saves time because I can now just say "replace with something from this collection"
Use in multiple assets (eg. there are about 12 rural roads where I want pine scrub)
I can edit the collection contents to propagate changes throughout my city wherever that collection is used
When replacing map trees, I could replace them with a collection - eg. if a map was filled with pine trees, I could create a collection with a mixture of deciduous trees and now I've got a much more interesting forest... and if I edit the collection, could potentially refresh my forest? (would need some way to remember original map trees which is likely painful tho?)

Oh, wait, the "Random Setup" button already does this? (I thought it just chose random replacements, rather than create a 'collection' style thing). Doh!

I just saw this and was about to mention the 'random replacements'!  UI can do with a bit more development, but yes, the functionality is there.
That being said, I'm going to keep this open for now, as I think what you've written above will go great in the documentation I'm starting to pull together - so thanks!

I just realised why I was struggling with the existing random prop/tree functionality.... If I already had the 'show random' checkbox selected, then I go in and create my first random group, and exit the random window, the list in the main window doesn't update so it looks like my random group doesn't exist.
Suggestion: Refresh the right-hand list in main UI after random groups are added/removed/renamed. Maybe also show random groups in the main list but prefixed with [r] and in different colour?
(BTW, now I've got it working, the random feature is really awesome! Already created several random tree groups for roads, buildings, etc., love it!)

Ah, that would make sense!  Yes, a refresh of random prefabs is needed.

Fixed in 79386ec07b660c2000609f05293c79c46e11ecd9


Expand/Collapse only when tap on button not on cell touch

hey @Augustyniak nice library but i don't want to expand/collapse on cell touch but i want to expand/collapse tap on button putted right side in cell.
Any help
Thank you.

@girishghoda you can achieve this by

Disabling selection of cells for RATreeView:
treeView.allowsSelection = false
and then manually expand/collapse cell on a button touch:

// Check current expand/collapse state of cell
let isExpanded = treeView.isCell(forItemExpanded: item)
// Expand or collapse cell
if isExpanded {
    treeView.collapseRow(forItem: item, collapseChildren: true, with: RATreeViewRowAnimationAutomatic)
} else {
    treeView.expandRow(forItem: item, expandChildren: false, with: RATreeViewRowAnimationAutomatic)
}

treeView.allowsSelection = false

will disable click into cell


force_torque_sensor_broadcaster values are not available

i tried to look into the force torque sensor simulation.
i couldn't find the ur_controller/force_torque_sensor_broadcaster as stated in the config.yaml
i downloaded the description and driver pkg from universal robots.
Is there a functional launch example where the force torque sensor broadcaster is utilized and actually publishes the values of the force_torque_sensor from ignition gazebo fortress to ros2 as a geometric wrench msg?
Thanks for any help with the error:
[ign-1] [ERROR] [1717421068.852962020] [controller_manager]: Can't activate controller 'ftsensor_broadcaster': State interface with key 'ft_sensor/force.x' does not exist
i am using the force_torque_sensor_broadcaster/ForceTorqueSensorBroadcaster and not the ur_controller/... as i didn't find it in the repos
controller_manager:
  ros_parameters:
  update_rate: 100
  publish_rate: 100
  use_sim_time: True
  ftsensor_broadcaster:
      type: force_torque_sensor_broadcaster/ForceTorqueSensorBroadcaster

/ftsensor_broadcaster:
  ros__parameters:
    interface_names:
      force:
        x: ft_sensor/force.x
        y: ft_sensor/force.y
        z: ft_sensor/force.z
      torque:
        x: ft_torque_sensor/torque.x
        y: ft_torque_sensor/torque.y
        z: ft_torque_sensor/torque.z

    frame_id: ft_sensor_link
    topic_name: ft_data

here is the part of the relevant urdf description:
    <joint name="ft_sensor_joint" type="fixed">
      <parent link="link_6_clean"/>
      <child link="ft_sensor_link"/>
      <origin xyz="0 0 0" rpy="0 0 0"/>
      <gazebo>
        <provideFeedback>true</provideFeedback>
      </gazebo>
    </joint>

    <ros2_control name="force_torque_sensor" type="sensor">
    <hardware>
      <plugin>force_torque_sensor_broadcaster/ForceTorqueSensorBroadcaster</plugin>
    </hardware>

    <sensor name="ft_sensor">
      <state_interface name="force.x"/>
      <state_interface name="force.y"/>
      <state_interface name="force.z"/>
      <state_interface name="torque.x"/>
      <state_interface name="torque.y"/>
      <state_interface name="torque.z"/>
      <param name="frame_id">sensor_frame</param>
    </sensor>
  </ros2_control>

Thanks for any hints or tips

Hi @jaronski,
to our current knowledge, gazebo ignition still doesn't provide that kind of information from the simulation. If you have any sources saying the opposite, then feel free to reopen.

@VinDP
thanks for your response. As far as i can tell there is a force torque sensor in the ignition fortress (gazebo) version. https://github.com/gazebosim/gz-sensors/issues/25. The "workaround" is to add the ftsensor inside of the "world.sdf" that i launch.
<!-- FT Plugin -->
    <plugin filename="ignition-gazebo-forcetorque-system" name="ignition::gazebo::systems::ForceTorque">
      <sensor name="tcp_fts_sensor"/>
    </plugin>

I am able to get values from the sensor inside ignition with ign topic -e -t /topic_name (in my case a very long name)
when launching ros_gz_bridge parameter_bridge i am also able to see the values in a ros2 topic.
so as i looked into your repos, i have seen that in your config.yaml you defined a ur_controller/force_torque_sensor_broadcaster which i couldn't find an implementation so this is why i asked here.
I also tried to setup my environment to work with gazebo classic ros2_control and ros2 humble and the "old" ft sensor but also no success.
I also tried to debug the force_torque_sensor_broadcaster but i couldn't find the part where the urdf is checked for the defined state_interfaces always resulting in the error:
[ign-1] [ERROR] [1717421068.852962020] [controller_manager]: Can't activate controller 'ftsensor_broadcaster': State interface with key 'ft_sensor/force.x' does not exist

@jaronski thanks for providing the insight. For this to work as the rest of this simulation it would have to be integrated into gz_ros2_control. As far as I can see, however, only IMU sensors are supported in gz_ros2_control.
Only then it would be possible to inject this into the ros2_control ecosystem with the ftsensor_broadcaster. See https://github.com/ros-controls/gz_ros2_control/issues/170 as the related upstream issue.

thanks @fmauch for your fast response. I didn't check the gz_ros2_control implementation :( i could have saved a lot of time
anyway thanks for providing the feedback


🔄 synced file(s) with worgarside/github-config-files

synced local file(s) with worgarside/github-config-files.

This PR was created automatically by the repo-file-sync-action workflow run #6148077849

This PR is empty, closing it. :no_good:


Gargoyle Hammer Toss Icon Fix

The Hammer throw for Gargoyles currently does not show an icon when the gargoyle is on 9 hp, which is the hp when you are able to throw the hammer to successfully kill the gargoyle

Needs rebase


Use kubectl create (without specifying namespace) for sock-shop app

Fix error while deploying sock-shop app (#3214)

This change is

Ok, I'll wait until Thursday for any additional responses before I merge.

We are fixing this in Sock Shop, as it was an unintended change (see https://github.com/microservices-demo/microservices-demo/pull/702), so please don't merge this.


Look into why "meltano ui" is not showing up in Events in Google Analytics

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/452
Originally created by @dmor on 2019-03-06 20:29:11

Expected to see "meltano ui" as a popular event
https://analytics.google.com/analytics/web/?utm_source=marketingplatform.google.com&utm_medium=et&utm_campaign=marketingplatform.google.com%2Fabout%2Fanalytics%2F#/report/content-event-overview/a132758957w192718180p188392047/_u.date00=20190201&_u.date01=20190306/
Need to make sure we are tracking correctly
Important to know how this being broken impacts other things

View 11 previous comments from the original issue on GitLab


cannot modify tags on Panorama example

Describe the bug
Install terraform 0.15.0
cd examples/panorama
cp example.tfvars terraform.tfvars
terraform init
terraform apply

Modify the tags in the azurerm_resource_group resource.
terraform apply

Expected behavior
RG modified accordingly, no resources destroyed/created.
Current behavior
Terraform will perform the following actions:

  # azurerm_resource_group.this will be updated in-place
  ~ resource "azurerm_resource_group" "this" {
        id       = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/jb36-rg"
        name     = "jb36-rg"
      ~ tags     = {
          + "environment" = "dev"
        }
        # (1 unchanged attribute hidden)
    }

  # module.nsg.data.azurerm_resource_group.nsg will be read during apply
  # (config refers to values not yet known)
 <= data "azurerm_resource_group" "nsg"  {
      ~ id       = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/jb36-rg" -> (known after apply)
      ~ location = "germanywestcentral" -> (known after apply)
        name     = "jb36-rg"
      ~ tags     = {} -> (known after apply)

      + timeouts {
          + read = (known after apply)
        }
    }

  # module.vnet.data.azurerm_resource_group.vnet will be read during apply
  # (config refers to values not yet known)
 <= data "azurerm_resource_group" "vnet"  {
      ~ id       = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/jb36-rg" -> (known after apply)
      ~ location = "germanywestcentral" -> (known after apply)
        name     = "jb36-rg"
      ~ tags     = {} -> (known after apply)

      + timeouts {
          + read = (known after apply)
        }
    }

  # module.vnet.azurerm_virtual_network.vnet must be replaced
-/+ resource "azurerm_virtual_network" "vnet" {
      ~ guid                  = "58f6dc8a-a296-4948-ba7a-eeed873d57dc" -> (known after apply)
      ~ id                    = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/jb36-rg/providers/Microsoft.Network/virtualNetworks/jb36-vnet" -> (known after apply)
      ~ location              = "germanywestcentral" -> (known after apply) # forces replacement
        name                  = "jb36-vnet"
      ~ subnet                = [
          - {
              - address_prefix = "<IP_ADDRESS>/24"
              - id             = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/jb36-rg/providers/Microsoft.Network/virtualNetworks/jb36-vnet/subnets/subnet1"
              - name           = "subnet1"
              - security_group = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/jb36-rg/providers/Microsoft.Network/networkSecurityGroups/nsg-panorama"
            },
        ] -> (known after apply)
        tags                  = {
            "environment" = "dev"
        }
        # (4 unchanged attributes hidden)
    }

Plan: 1 to add, 1 to change, 1 to destroy.

...

│ Error: deleting Virtual Network: (Name "jb36-vnet" / Resource Group "jb36-rg"): network.VirtualNetworksClient#Delete: Failure sending request: StatusCode=0 -- Original Error: Code="InUseSubnetCannotBeDeleted" Message="Subnet subnet1 is in use by /subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/jb36-rg/providers/Microsoft.Network/networkInterfaces/mgmt/ipConfigurations/mgmt and cannot be deleted. In order to delete the subnet, delete all the resources within the subnet. See aka.ms/deletesubnet." Details=[]

Possible solution
Avoid using this module at all:
module "nsg" {
  source = "Azure/network-security-group/azurerm"
}

Context
It looks like changing the tags on an RG would require Terraform to destroy the entire panorama. Panorama however contains policies and possibly vm-auth-keys. This would further require changing all impacted init-cfg.txt files. It seems a ton of manual work for such a small modification as tags.
Your Environment

Version used: 0.1.0
Terraform: 0.15.0
Operating System and version (desktop or mobile): Ubuntu 18.04 LTS

I've tried to re-create the issue with Terraform v0.15.0 but I couldn't even deploy the example - every single attempt ended up with an error claiming that a Service Account I wanted to use (despite I wanted to create a new one) is already in use.
When I've deployed the example with Terraform v1.0.0 and then tried to edit the tags, everything looked as expected - the resources would be updated in-place:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.nsg.azurerm_network_security_group.nsg will be updated in-place
  ~ resource "azurerm_network_security_group" "nsg" {
        id                  = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/damian-rg/providers/Microsoft.Network/networkSecurityGroups/nsg-panorama"
        name                = "nsg-panorama"
      ~ tags                = {
          ~ "environment" = "dev" -> "prod"
        }
        # (3 unchanged attributes hidden)
    }

  # module.panorama.azurerm_managed_disk.this["disk_name_1"] will be updated in-place
  ~ resource "azurerm_managed_disk" "this" {
        id                            = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/damian-rg/providers/Microsoft.Compute/disks/panorama-disk-disk_name_1"
        name                          = "panorama-disk-disk_name_1"
      ~ tags                          = {
          ~ "environment" = "dev" -> "prod"
        }
        # (14 unchanged attributes hidden)
    }

  # module.panorama.azurerm_managed_disk.this["disk_name_2"] will be updated in-place
  ~ resource "azurerm_managed_disk" "this" {
        id                            = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/damian-rg/providers/Microsoft.Compute/disks/panorama-disk-disk_name_2"
        name                          = "panorama-disk-disk_name_2"
      ~ tags                          = {
          ~ "environment" = "dev" -> "prod"
        }
        # (14 unchanged attributes hidden)
    }

  # module.panorama.azurerm_network_interface.this will be updated in-place
  ~ resource "azurerm_network_interface" "this" {
        id                            = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/damian-rg/providers/Microsoft.Network/networkInterfaces/mgmt"
        name                          = "mgmt"
      ~ tags                          = {
          ~ "environment" = "dev" -> "prod"
        }
        # (11 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # module.panorama.azurerm_public_ip.this[0] will be updated in-place
  ~ resource "azurerm_public_ip" "this" {
        id                      = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/damian-rg/providers/Microsoft.Network/publicIPAddresses/panorama"
        name                    = "panorama"
      ~ tags                    = {
          ~ "environment" = "dev" -> "prod"
        }
        # (11 unchanged attributes hidden)
    }

  # module.panorama.azurerm_virtual_machine.panorama will be updated in-place
  ~ resource "azurerm_virtual_machine" "panorama" {
        id                               = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/damian-rg/providers/Microsoft.Compute/virtualMachines/panorama"
        name                             = "panorama"
      ~ tags                             = {
          ~ "environment" = "dev" -> "prod"
        }
        # (8 unchanged attributes hidden)

        os_profile {
          # At least one attribute in this block is (or was) sensitive,
          # so its contents will not be displayed.
        }

        # (7 unchanged blocks hidden)
    }

  # module.vnet.azurerm_virtual_network.vnet will be updated in-place
  ~ resource "azurerm_virtual_network" "vnet" {
        id                      = "/subscriptions/d47f1af8-9795-4e86-bbce-da72cfd0f8ec/resourceGroups/damian-rg/providers/Microsoft.Network/virtualNetworks/damian-vnet"
        name                    = "damian-vnet"
      ~ tags                    = {
          ~ "environment" = "dev" -> "prod"
        }
        # (8 unchanged attributes hidden)
    }

Plan: 0 to add, 7 to change, 0 to destroy.

@migara what are the next steps you want me to conduct in terms of this issue?

Looks good, thanks!


Long titles in doc overflow sidebar (and look generally weird)

Describe the bug
In the sphinx docs, both the pointing and the eye module names overflow the sidebar bounds and are generally too long. They should probably be moved into their own section of the docs (e.g. Task and Agent Collections) anyways.
To Reproduce
Steps to reproduce the behavior:

Go to the docs
See the sidebar
Scroll down to 'Pointing Module. This module is used to model pointing tasks.' and 'Eye Module. This module is used to model eye movements of human observers.'
See error (overflow)

Expected behavior
You would expect the name to be separated into name and description or title and subtitle. Alternatively, you would perhaps expect these parts of the docs to be in another section like Task and Agent Collections entirely.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop:

OS: MacOS
Browser Safari
Version 15.1

After many changes to the doc, this seems to no longer be an issue


Question: On the GEOM Dataset availability

Would the referenced dataset located at https://dataverse.harvard.edu/api/access/datafile/4327252 also be available to access under a F/OSS-Compliant license? And is it accessible by any other means or mirrors?

I'm not sure. I suggest contacting Simon, the first author of the GEOM paper (saxelrod@mit.edu). He said he'd be willing to help answer your question!


Introduce build_lazy/2

Closes https://github.com/thoughtbot/ex_machina/issues/402, https://github.com/thoughtbot/ex_machina/issues/385, and https://github.com/thoughtbot/ex_machina/issues/373
The problem
Consider this scenario. People want a different email per account (especially if the email factory has a sequence), but they do this:
build_pair(:account, email: build(:email))

The problem is that build/2 is just function calling. So the above is equivalent to this:
email = build(:email)
build_pair(:account, email: email)

In other words, we get one email factory for all of the accounts.
The problem is worse when using it with Ecto. We can image the following scenario:
insert_pair(:account, user: build(:user))

If the user factory has a uniqueness constraint, insert_pair/2 will raise an error because we'll try to insert a user with the same value (even if using a sequence).
Solution
The solution is to delay evaluation of the factory. We do this by introducing a private struct %ExMachina.InstanceTemplate{} to hold the data necessary to build the instance of that factory.
Note that this struct is private and liable to change, so users of the library shouldn't depend on it.
The trick then lies in the build/2 function. We make it a terminal function in that it will evaluate any lazy factories recursively. To do that, we update the build/2 function to evaluate ExMachina.InstanceTemplate structs after building the build/2 factory.
In an early implementation of this feature, I evaluated the lazy factories when we first got the attributes in build/2 (i.e. attrs |> evaluate_lazy_factories() |> Enum.into(%{})). But then I opted for evaluating the lazy factories after the factory is created because that allows us to use build_lazy/2 from within factory definitions, and not just when combined with build/2 or build_* functions.

@WilHall that's an excellent question. I wrote a little bit about it in #402, but I should've mentioned it here.
The anonymous function seems simpler to me, and I like that people could even use anonymous functions to delay execution instead of using build_lazy/2. But I don't know if that would be a breaking change. If people have been using anonymous functions in their factories as an attribute like this:
def user_factory do
  %{
    name: "Some Name",
    creation_callback: fn -> User.user_created!() end}
  }
end

We would all of the sudden evaluate those anonymous functions when building a factory because the anonymous function is now the mechanism by which we delay execution. It's not something I have done in apps, and maybe others don't use ExMachina like that, but I also don't know all the cases for how ExMachina is used in the wild.
What do you think Wil? Is it safe enough to use the anonymous function approach? I really do like it.

@WilHall I've given more thought to what you said, and it made me realize that perhaps we really can introduce this feature without adding a new function like build_lazy/2. We can just take anonymous functions.
What I really like about the new approach is that we can also include passing the parent factory into the anonymous function so that we can get something like "derived" attributes.
In any case, I'm opening a different PR since it's fairly different.
Closing this in favor of https://github.com/thoughtbot/ex_machina/pull/408


Squash commit history prior to 5a84172919645d1b800335ad91c925342bd5f760

To ensure we have a clean repository with evidence of enforced branch protection we would like to squash the commit history prior to this commit: https://github.com/opentdf/platform/pull/93
Git commit: 5a84172919645d1b800335ad91c925342bd5f760

Was decided not something we are going to do.


Explore removing go.mod from subpackages

What is the problem you're trying to solve
go.mod in subpackages is causing issues with updating API and some headaches with the integration tests
Describe the solution you'd like
No go.mod
Additional context
No response

@dmcgowan We have removed the api package in https://github.com/containerd/containerd/pull/6439. Do you want to remove https://github.com/containerd/containerd/blob/main/integration/client/go.mod as well?

@kzys I can close this one. For now, I think it is best to keep it. It would be great to get rid of the extra vendoring step in CI if we can in the future. The only difference is the inclusion of the hcsshim test package, but that includes a shared object which we were trying to avoid vendoring.


Clean up functions in header vs source files

This cleans up the static declarations of functions that are used outside of their own source files by having the declaration in the .h file, and the definition in the .c file. In turn, this enables the ability to use WREN_IMPLEMENTATION in the amalgamated wren.h file.
Fixes #1030

I don't understand why moving all these functions are necessary. Isn't it possible to isolate "wren.h" at the top of the amalgation and isolate all the other files inside a giant #ifdef guard around all others files inclusions? There should be no good reasons to allow to access internal, so it should be simpler to do like this.

Would like to figure out how. The static inline functions were causing undefined references. I'm sure there is a way around it though.


Adds rpc repo url definitions

The change adds the rpc repo to the pip lockdown / container image installation process
variables. The change is in response to an upstream change which removes the upstream
repo dependencies as found here:

https://review.openstack.org/#/c/216181

needs to be resync'd with master

AFICS this isn't necessary any more :-1:


chore: add the WebXDAO community

👨💻 Changes proposed
-Add the WebXDAO community to the list of DAO communities.

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
None.

resource already added by https://github.com/FrancescoXX/free-Web3-resources/commit/edccd4d2c2e78757cd1bbdd27d7f0d16378a8bd1


Attempt to coerce the generated_at cookie to a Time object.

Time objects aren't properly coerced back when using the JSON cookie serialization,
so we need to do it ourselves.
To avoid any new JSON serialization issues, we now store the generated_at as
an String with the timestamp seconds + miliseconds in the cookie but still the
previous JSON encoded format.
Thanks to @boblail at https://github.com/plataformatec/devise/pull/3917 for the
initial patch.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:

:+1: Thanks, @lucasmazza!


Proposal: Add Support for Vulkan

Proposal For Vulkan Support In MaterialX
Shader Generation Ecosystem
The following shows how Vulkan code generation would fit into the current eco-system (at time of writing). Note that the intention is to reuse current GLSL code with customizations provided by a new Vulkan code generator classs which is derived from the base GLSL generator.

Code Generation / Rendering Support Timeline
The following is a possible timeline.

The next patch release (at time of writing is 1.38.4) which would be the target for creating a new generator along with appropriate source code validation.
Naturally rendering would come later with a possible target of a patch release or as part of the 1.39 release.
The initial goal is only to support code generation for a rasterizer and a simple sample renderer to use this code. One main reason is that the current GLSL code emits code which only works for rasterization. It is to be determined what the appropriate generation will be for a path tracer.
There will be no new source code implementations required. Instead a new code generator will emit the appropriate variation of GLSL required for Vulkan compliance. This is similar to how the existing ESSL generator is structured.
This means that there are no additional tooling dependencies such as SPIRV for code generation.
The tooling for code syntax validation will remain glslValidator. This is currently part of the the CI workflow and as desired will be an option for local unit test validation (unit test suite validation is currently too expensive to run on CI).
OCIO support in MaterialX is a related dependency, for which Vulkan support adds an additional requirement. This support will not be part of this proposal, except to note that the base colorspace transforms provided as part of the MaterialX core distribution should be supported.

Details:
Handling Vulkan GLSL

KHR_vulkan_glsl extension on OpenGL GLSL
Minor differences in functions, main changes in input and resource binding.
Default uniforms not allowed

e.g., uniform float base=1.0 is not allowed

Use layout identifier

e.g., layout (set=M, binding=N) uniform sampler2D variableName;

Use of sampler2D replaced by sampler and texture2D with separate binding points
Uniform Buffers to group uniforms by access and frequency of update
Advanced usage (for future exploration)
Storage Images (Image2d)

Push constants
Descriptor Sets
Storage buffers

Vulkan ShaderGen

Generate Vulkan compliant GLSL.
GLSL Shaders are compiled to SPIRV using Vulkan SDK tools.
Vulkan ShaderGen will not generate SPIRV.
A new Vulkan rasterization sample to demonstrate use of GLSL - SPRIV in a runtime environment.
Build framework to pull in the required Vulkan SDK.
Vulkan SDK is not a requirement to use MaterialX Vulkan ShaderGen.
Vulkan SDK is a requirement for validation, testing and samples.

What are the next steps? Are there any blockers?

From a rasterizer support point of view, code generation has been added. A sample renderer was started, but no active work is being done currently. Color management support I don't believe has been tested. No path tracer support has been started.

How would you recommend I implement MaterialX for Godot Engine which choosing either vulkan or an opengl renderer?

Is it possible to reuse any work from Metal to support vulkan?

I think this question is about generating shaders for Vulkan for use in Godot, more than it is about adding a Vulkan mode to the bundled MaterialX viewer.
I don't think the Metal code will be helpful in that case, but I do think the glsl code will be helpful.
I don't know what tooling Godot uses for shaders, but I think you can use the glsl shader gen from MaterialX for your purposes? Save out the shaders and run them through glslang to get SPIR-V?
I can imagine am ambition to emit SPIR-V directly, but without introducing an optimizer to the shader generator, that would be .... unoptimal.

Godot Engine has a glsl-like code that will be sent to possible targets like Dx12, Opengl and Vulkan.
That's probably a viable approach.

An interesting approach would be to see if you can specialize a Godot code generator from the glsl one then ~ recently some work was done by @kwokcb when the MSL generator was added that should make it easier to do things like that.

A customized code generator was "approach 1" I mentioned above and seems the better long term approach. This may or may not be a large undertaking so I was wondering as a first step whether "approach 2" works. That is just get something to show up by using an existing generator ?
The Metal work has helped to refactor / distill the existing code so there is a better "hardware" generator base logic. More work will be done there. A 3rd possibility is to enhance the Vulkan or base hw generators to support Godot requirements.


[BEAM-8343] Added nessesary methods to BeamSqlTable to enable support for predicate/project push-down

Added methods needed for predicate/project push-down to BeamSqlTable interface.
Create a sql.meta.BeamSqlTableFilter interface and a default implementation for it sql.meta.DefaultTableFilter.

Based on top of #9718
Design doc link.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @apilloud

Run JavaBeamZetaSQL PreCommit

R: @amaliujia

Run Java PreCommit


Error Invoke-PnPTenantTemplate : {"odata.error":{"code":"-2147024891,  System.UnauthorizedAccessException","message":{"lang":"de-DE","value":"Zugriff verweigert. Sie haben keine  Berechtigung, diesen Vorgang auszuf\u00fchren oder auf diese Ressource zuzugreifen."}}}

When invoking Invoke-PnPTenantTemplate -Path .\starterkit.pnp I am getting the following error. My user is term store administrator.
Does anyone experience a similar behaviour?

nStart der Windows PowerShell-Aufzeichnung
Startzeit:<PHONE_NUMBER>3124
Benutzername: SIMPL\E519371
RunAs-Benutzer: SIMPL\E519371
Konfigurationsname:
Computer: NBTRA081 (Microsoft Windows NT 10.0.18363.0)
Hostanwendung: C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe
Prozess-ID: 13832
PSVersion: 5.1.18362.1171
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.18362.1171
BuildVersion: 10.0.18362.1171
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: <IP_ADDRESS>

Die Aufzeichnung wurde gestartet. Die Ausgabedatei ist "C:\Users\E519371\OneDrive - login Berufsbildung AG\Documents\PowerShell_transcript.NBTRA081.7GEJFoYo.20210224073124.txt".
PS C:\Users\E519371\Developement\sp-starter-kit-master\provisioning> Invoke-PnPTenantTemplate -Path .\starterkit.pnp
Invoke-PnPTenantTemplate : {"odata.error":{"code":"-2147024891,
System.UnauthorizedAccessException","message":{"lang":"de-DE","value":"Zugriff verweigert. Sie haben keine
Berechtigung, diesen Vorgang auszuf\u00fchren oder auf diese Ressource zuzugreifen."}}}
In Zeile:1 Zeichen:1

Invoke-PnPTenantTemplate -Path .\starterkit.pnp

  + CategoryInfo          : WriteError: (:) [Invoke-PnPTenantTemplate], Exception
  + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.Provisioning.Tenant.InvokeTenantTemplate

Invoke-PnPTenantTemplate : {"odata.error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"de-DE","value":"Zugriff verweigert. Sie haben
keine Berechtigung, diesen Vorgang auszuf\u00fchren oder auf diese Ressource zuzugreifen."}}}
In Zeile:1 Zeichen:1

Invoke-PnPTenantTemplate -Path .\starterkit.pnp

  + CategoryInfo          : WriteError: (:) [Invoke-PnPTenantTemplate], Exception
  + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.Provisioning.Tenant.InvokeTenantTemplate

Thank you for reporting an issue. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.
(DELETE THIS PARAGRAPH AFTER READING)

Category

[x] Bug

Describe the bug
Expected or Desired Behavior

When reporting a bug, please describe the behavior you expected to occur when performing the action.
(DELETE THIS PARAGRAPH AFTER READING)

Observed Behavior

When reporting a bug, please describe the behavior you are observing when performing the action.
(DELETE THIS PARAGRAPH AFTER READING)

Steps to Reproduce

When reporting a bug please describe the steps to reproduce the bug in sufficient detail to allow testing. Only way to fix things properly, is to have sufficient details to reproduce it. If you are making a suggestion, you can delete this section.
(DELETE THIS PARAGRAPH AFTER READING)

Environment Details (Development & Target environment)

DELETE THIS LINE BEFORE SUBMITTING - Complete the following (if ignored you'll be prompted for it before we can address your issue... save the time and provide it in your initial submission).

Starter kit version: [e.g. v2 for current version, v1 for legacy solution]
OS: [e.g. Windows 10 | MacOS 10.15.x]
Target Environment:[SharePoint Server 2019 | SharePoint Online]
Framework: [Node.js v6/v8/v10/v12]
PnPPowerShell Version : [e.g 3.22.2006.2.]
Browser(s): [e.g. Chrome v79 | Safari v22 | FireFox v31 | IE v11 | Edge | Chromium Edge v79]
Additional details: The more context you can provide, the easier it is (and therefore quicker) to help.

Guidelines for issue creator (DELETE AFTER READING)

All bug reports are welcome, please let us know what's on your mind.
Remember that this repository is maintained by community members who volunteer their time to help. Be courteous and patient.
If you have technical questions about the framework, we’ll be monitoring #spfx, #spfx-webparts, and #spfx-tooling on (SharePoint StackExchange)> [http://sharepoint.stackexchange.com/]. You can also alternatively submit your question to (SharePoint Developer group)> [https://techcommunity.microsoft.com/t5/sharepoint-developer/bd-p/SharePointDev] in the Microsoft Tech Community.
Remember to include sufficient details and context.
If you have multiple suggestions or bugs please submit them in separate bugs so we can track resolution.
(DELETE THIS SECTION AFTER READING)

Thanks for your contribution! Sharing is caring.

Hi Thank you, can you confirm you are also a tenant admin?


Visual Studio add-in should only register with the IDE matching the installed version of BizTalk vs. all installed VS IDEs

Visual Studio add-in should only register with the IDE matching the installed version of BizTalk vs. all installed VS IDEs.  If BizTalk 2010 is installed, the addin should only register with VS 2010, etc.  Previously the add-in would register with all recognized VS IDE's installed, even if they weren't associated with BizTalk.
This work item was migrated from CodePlex
CodePlex work item ID: '7423'
Assigned to: 'tfabraham'
Vote count: '0'

[UnknownUser@10/25/2010]
Resolved with changeset 51207.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]


Vite proxying with https doesn't work

Describe the bug
We have an existing project with a  vue ( vue-cli ) front end that we are trying to migrate to vite, and a backend that only accepts secure https requests. We are using a wildcard certificate for *.companydomain.org and most developers have updated their etc/hots local redirect URL with local.companydomain.org. We do this because the backend only accepts strictly https requests.
Everything was working fine in the vue-cli project. However as we are attempting to migrate it to vite , the one and only thing we aren't able to get done is proxying to the backend server ( no API requests are proxied ).
Here is the old vue.config.js file.
// These values are used to configure the vue devServer.  They can be overriden using a .env file.
HOST = process.env.ENV_HOST || '<IP_ADDRESS>' // IP or hostname the vue dev server should be bound to (<IP_ADDRESS> uses 'localhost" and your external ip)
PORT = process.env.ENV_PORT || '8080' // port for the vue proxy server
HTTPS = process.env.ENV_HTTPS == 'true' ? true : false // enable or disable https for the vue proxy server
PFX = process.env.ENV_PFX || '' // PKCS12 ksystore for ssl certificate
PFX_PASSPHRASE = process.env.ENV_PFX_PASSPHRASE || '' // passphrase for ssl keystore
SERVER_URL = process.env.ENV_SERVER_URL || 'http://localhost:8447' // host where the spring boot server is running / target of the proxy server

// vue.config.js
module.exports = {
  // proxy all webpack dev-server requests starting with /api
  // to our Spring Boot backend (localhost:8088) using http-proxy-middleware
  // see https://cli.vuejs.org/config/#devserver-proxy
  devServer: {
    host: HOST,
    port: PORT,
    https: HTTPS,
    pfx: PFX,
    pfxPassphrase: PFX_PASSPHRASE,
    proxy: {
      '/': {
        target: SERVER_URL, // this configuration needs to correspond to the Spring Boot backends' application.properties server.port
        ws: true,
        changeOrigin: true
      }
    }
  },
  // Change build paths to make them Maven compatible
  // see https://cli.vuejs.org/config/
  outputDir: 'target/classes/public',
  assetsDir: 'static',
  publicPath: '/eventdirect/',
  configureWebpack: {
    devtool: 'source-map'
    // ,
    // externals: {
    //   dropzone: 'dropzone'
    // }
  }
}

As you can see we are proxying all "/" requests to the backend , and the vue.cli dev server was smart enough to only proxy the API requests. The javascript chunk requests were never proxied. This didn't work with vite dev server , so I attempted to add a baseUrl to axios in main.js
if (import.meta.env.DEV) {
  axios.defaults.baseURL = 'api'
}

And here is the corresponding vite.config.js
// These values are used to configure the vue devServer.  They can be overriden using a .env file.
import { defineConfig, loadEnv } from 'vite'
import { createVuePlugin } from 'vite-plugin-vue2'
import path from 'path'

export default ({ mode }) => {
  process.env = { ...process.env, ...loadEnv(mode, process.cwd(), 'VUE_') }

  HOST = process.env.VUE_ENV_HOST || '<IP_ADDRESS>' // IP or hostname the vue dev server should be bound to (<IP_ADDRESS> uses 'localhost" and your external ip)
  PORT = process.env.VUE_ENV_PORT || '8080' // port for the vue proxy server
  HTTPS = process.env.VUE_ENV_HTTPS == 'true' ? true : false // enable or disable https for the vue proxy server
  PFX = process.env.VUE_ENV_PFX || '' // PKCS12 ksystore for ssl certificate
  PFX_PASSPHRASE = process.env.VUE_ENV_PFX_PASSPHRASE || '' // passphrase for ssl keystore
  SERVER_URL = process.env.VUE_ENV_SERVER_URL || 'http://localhost:8447' // host where the spring boot server is running / target of the proxy server
  console.log(SERVER_URL)
  console.log(HOST)
  return defineConfig({
    envPrefix: 'VUE_',
    base: '/eventdirect/',
    plugins: [createVuePlugin()],
    server: {
      host: HOST,
      port: PORT,
      https: {
        pfx: PFX,
        passphrase: PFX_PASSPHRASE
      }
    },
    resolve: {
      alias: [
        {
          find: '@',
          replacement: path.resolve(__dirname, 'src')
        }
      ]
    },
    proxy: {
      '^/api/.*': {
        target: SERVER_URL,
        changeOrigin: true,
        secure: false,
        rewrite: path => path.replace(/^\/api/, ''),
        ssl: {
          pfx: PFX,
          passphrase: PFX_PASSPHRASE
        }
      }
    },
    build: {
      chunkSizeWarningLimit: 600,
      cssCodeSplit: false
    }
  })
}

We are trying to make as little change as possible , the only change in the above vite config file ( compared to vue config) is that , the environment variables are changed , they start with a prepend of VUE_ , and 2 , the proxying doesn't work.
There are multiple bugs reported earlier , and I am pretty sure this is a bug, that just hasn't been addressed yet.
Reproduction
Please see the vite config above , can't upload our certificates to reproduce it. As mentioned earlier , the same backend worked for vue-cli , and vue cli config is also uploaded.

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Here is a screenshot of 404 being returned for API requests.

@rachitpant did you ever find a workaround?

Nope.
On Fri, Dec 24, 2021 at 12:05 AM Joe Previte @.***>
wrote:

@rachitpant https://github.com/rachitpant did you ever find a
workaround?
—
Reply to this email directly, view it on GitHub
https://github.com/vitejs/vite/issues/6102#issuecomment-1000656439, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AALH6363VGEXIWQ7ZTCYK63USP5P5ANCNFSM5J7AESVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Vite experts any comments ??
At first I thought if there is something wrong in my proxy rewrite config.
 proxy: {
      '^/api/.*': {
        target: SERVER_URL,
        changeOrigin: true,
        secure: false,
        rewrite: path => path.replace(/^\/api/, ''),
        ssl: {
          pfx: PFX,
          passphrase: PFX_PASSPHRASE
        }
      }
    },

But as we can see if the logs above , the vite server is not even attempting to rewrite which is why the requests are not proxied.
vite:spa-fallback Not rewriting GET /api/getUserInfo because the client prefers JSON. +3ms

@patak-dev Please mark as bug

@import-brain thanks for the heads up! If you tested and confirmed that it is a bug, you can say so without tagging a particular maintainer, everyone that is watching the repo will get the notification and the closest one will label it :)

@import-brain thanks for the heads up! If you tested and confirmed that it is a bug, you can say so without tagging a particular maintainer, everyone that is watching the repo will get the notification and the closest one will label it :)

Ah, I didn't realize you guys had your notifications set up like that, thanks for the heads up!

My bad .. this is not a bug , I had to account for the baseUrl in addition white configuring proxy. Here is the working config. Also this should have been inside the server tag , but i am not sure why i put it outside. Corrected that as well and its working fine.
proxy: {
        '^/eventdirect/api/.*': {
          target: SERVER_URL,
          changeOrigin: true,
          rewrite: path => path.replace('/api', ''),
          ssl: {
            pfx: PFX,
            passphrase: PFX_PASSPHRASE
          }
        }
      }

My only suggestion would be that in the doesProxyContextMatchUrl function , we should probably check if request url starts with the base (already passed in the config ) , exclude that from testing the regex or string starts with.
Either that , or if that causes major changes , we can improve the server proxy config documentation to tell that the base url has to be explicitly prepended.. ( if there is any ).

My bad .. this is not a bug , I had to account for the baseUrl in addition white configuring proxy. Here is the working config. Also this should have been inside the server tag , but i am not sure why i put it outside. Corrected that as well and its working fine.
proxy: {
        '^/eventdirect/api/.*': {
          target: SERVER_URL,
          changeOrigin: true,
          rewrite: path => path.replace('/api', ''),
          ssl: {
            pfx: PFX,
            passphrase: PFX_PASSPHRASE
          }
        }
      }

My only suggestion would be that in the doesProxyContextMatchUrl function , we should probably check if request url starts with the base (already passed in the config ) , exclude that from testing the regex or string starts with.
Either that , or if we can't do that , we can improve the server proxy config documentation to tell that the base url has to be explicitly prepended.. ( if there is any ).

Wow, I can't believe I missed that too, we should probably include this in the docs.

if want to use all "/" requests to let it only proxy the API requests，we can use vite plugin api “configureServer”
JavaScript  {     name: 'serverProxy',     configureServer(server) {         const filter = function (pathname, req) {            return typeof req.headers['x-ajax'] != 'undefined'       }         server.middlewares.use(           ‘/’,            createProxyMiddleware(filter {             target: 'http://localhost:3000',             changeOrigin: true,             pathRewrite: path => path.replace(/^\/api/, '')           })         )     }   }

Hello Everyone !
I have the same issue with server proxy
The requests returns 404 when user navigate in a nested route
app.url/ => works fine
app.url/test/tests => doesn't work
Could you please help?


yolo config file

Hi,
I wonder how should i edit the config file.
What parameters should I make adjustment?

Feel free to edit solver parameter in config file, also you can modify ***_scale to change the weight of each loss.

Thank you. May I know what is the GPU parameter? is it the number of gpu or a pointer to which gpu i am going to use?

GPU = '' means using CPU and GPU = '0' means using the first GPU.

What if I would like to use two GPU? How should I change it?

You can try to set GPU = '0,1' or GPU = 'all'.

Thank you.


Adding firewall rule for certmanager webhook

This is an alternative solution to this PR  in Ingress module. Things to note are:

Since ingress module is a part of core modules, it make perfect sense to enable it along with SSH or GKE webhooks firewall rules.
We are slightly diverging from upstream cert-manager, since their preferred solution was to change the cert-manager webhook port to 10250.

LGTM!


Fix wrong escaping of "]"

Will fix #8 and provide a solution for https://github.com/tomav/docker-mailserver/issues/1630

@alinmear can this be merged? This would be very nice as we depend on this in tomav/docker-mailserver.

Thx for the contribution.


DG find

update DG for find feature implementation
handle some errors with assertion and logging
Fixes #136

LGTM


Chatdown: Add support for conversation update in .chat files

Conversation update activity is key for the bot to be able to deliver the default welcome message. As part of being able to mockup conersations using .chat files, we should add support for conversationupdate activity.

fixed in chatdown 1.0.10


[DO NOT MANUAL MERGE] Release Qualification

Trigger release qualification jobs
none

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

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-no_auth.sh
a65059c5a952be9fa8eff514e30611a869a304e9
link
/test daily-e2e-rbac-no_auth

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

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

Test name
Commit
Details
Rerun command

prow/daily-e2e-rbac-no_auth.sh
a65059c5a952be9fa8eff514e30611a869a304e9
link
/test daily-e2e-rbac-no_auth

prow/daily-e2e-rbac-no_auth-default.sh
a65059c5a952be9fa8eff514e30611a869a304e9
link
/test daily-e2e-rbac-no_auth-default

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


c/driver/postgresql: add basic benchmarks

Compare against? pgeon, psycopg, pandas.read_sql, DuckDB adapter
Will help guide the rest of the design

I want them too!
I want to use them for https://github.com/apache/arrow-flight-sql-postgresql too.

I put up a draft PR using asv to benchmark the Python driver against psycopg2 and duckdb (still need to add other clients, and expand the benchmarks). I still need to clean them up and make sure they're measuring the right thing (I expected DuckDB to win hands down; I may be setting something up wrong).


Downsample / concatenate?

Any explanation as to why this function is so involved? It's simply copying the input tensor and reshaping it. Why do we need four steps to do this?
https://github.com/epfml/attention-cnn/blob/21483bba7d8e3ff1dc104c1b311a44a84d5c9db4/models/transformer.py#L145

I think the reshaping is not just one line because vertical neighboring pixels are not next to each other in memory. So for example for a 2x2 concatenation, we first concatenate the channels of the horizontal neighbors. Then permute the dimensions and concatenate the vertical neighbors that are contiguous in memory. I was a bit crazy with the .contiguous(), some are maybe not necessary but they would lead to a no op so should not be a problem ;)
I am curious if you have a better/simpler solution that passes a test to match the output of my function.

It could be made simpler using unfold probably.


[SPARK-29438][SS] Failed to get state store when task number is not determinate

What changes were proposed in this pull request?
Add a new optimizer rule to add hint for join for those queries containing stream-stream-join.
Why are the changes needed?
This is a correctness bug.
Now, Spark use the TaskPartitionId to determine the StateStore path.
TaskPartitionId   \
StateStoreVersion  --> StoreProviderId -> StateStore
StateStoreName    /

In spark stages, the task partition id is determined by the number of tasks. As we said the StateStore file path depends on the task partition id. So if stream-stream join task partition id is changed against last batch, it will get wrong StateStore data or fail with non-exist StateStore data. In some corner cases, it happened. Following is a sample pseudocode:
val df3 = streamDf1.join(streamDf2)
val df5 = streamDf3.join(batchDf4)
val df = df3.union(df5)
df.writeStream...start()

A simplified DAG like this:
DataSourceV2Scan   Scan Relation     DataSourceV2Scan   DataSourceV2Scan
 (streamDf3)            |               (streamDf1)        (streamDf2)
     |                  |                   |                 |
  Exchange(200)      Exchange(200)       Exchange(200)     Exchange(200)
     |                  |                   |                 |
   Sort                Sort                 |                 |
     \                  /                   \                 /
      \                /                     \               /
        SortMergeJoin                    StreamingSymmetricHashJoin
                     \                 /
                       \             /
                         \         /
                            Union

Stream-Steam join task Id will start from 200 to 399 as they are in the same stage with SortMergeJoin. But when there is no new incoming data in streamDf3 in some batch, it will generate a empty LocalRelation, and then the SortMergeJoin will be replaced with a BroadcastHashJoin. In this case, Stream-Steam join task Id will start from 1 to 200. Finally, it will get wrong StateStore path through TaskPartitionId, and failed with error reading state store delta file.
LocalTableScan   Scan Relation     DataSourceV2Scan   DataSourceV2Scan
     |                  |                   |                 |
BroadcastExchange       |              Exchange(200)     Exchange(200)
     |                  |                   |                 |
     |                  |                   |                 |
      \                /                     \               /
       \             /                        \             /
      BroadcastHashJoin                 StreamingSymmetricHashJoin
                     \                 /
                       \             /
                         \         /
                            Union

Does this PR introduce any user-facing change?
No
How was this patch tested?
One new UT was added.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/17236/
Test PASSed.

Test build #112251 has started for PR 26156 at commit f25e4ac.

Test build #112251 has finished for PR 26156 at commit f25e4ac.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/112251/
Test FAILed.

retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/17243/
Test PASSed.

Test build #112261 has started for PR 26156 at commit f25e4ac.

Hi @uncleGen , sorry I didn't see what you meant for taskpartition in JIRA, now I got it.
Looks like I figured out the root cause - so submitted a patch to fix the root cause instead of taking workaround.
Could you please take a look at #26162 and see whether the patch will resolve SPARK-29438? Thanks in advance!

Test build #112261 has finished for PR 26156 at commit f25e4ac.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/112261/
Test PASSed.

@HeartSaVioR OK, let me close this pr and work on #26162

Thanks for understanding, and thanks again for your efforts to discover the issue and provide simple reproducer!


useElementSize does not detect resize of element, only resize of browser

https://github.com/juliencrn/usehooks-ts/blob/master/src/useElementSize/useElementSize.ts#L33
^^^^ I'm assuming without a 3rd arg, it binds to window? Why isn't the ref for the element passed in as the 3rd arg?

Can confirm. It seem to detect the sizes of the element only on the first try, then it's always 0.


Broken When No Blog Files

To support people setting up for the first time if they delete the template files then the application breaks. as there are hardcoded references to the first item in the posts array.
from memory its to access the date property on the first blog post. post[0].date
would be good to have a fallback render thats safe for the 0 length posts array.
anyway its a small thing, should be a easy PR for any of the people watching

Yes, sounds good. Happy to accept a PR on this

It's fine, I deleted the posts and it shows:

Hi, I really love the template. One thing: with the newest version (from May 4,2021, 0.3.0, commit 69a41932e7299b41558e489eb614d66000e4b3b0)  it still breaks when deleting posts. I got

when deleting the blog entry "the-time-machine.mdx".


merge main

Description
This PR add datastore cluster protocol in zone wizard for vmware.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

At the moment, I've no option to add a new zone in my test environment therefore i couldn't test this.

@DK101010 could you please update the title ?

@blueorangutan ui

@nvazquez a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5522 (SL-JID-706)


Password hash doesn't use salt

Proposoal
This gem should use salted passwords in order to prevent a rainbow table based attack.
I think the easiest way to do this is to have a required field (called "Salt") in the Identity model, which would be filled with a random value when a new record in the table is initialized. This salt should then be combined with the password which is entered, prior to creating the hash.
Benefits
The advantages of including salt are:

If two people have the same password, a person viewing the hashed password can't tell
Prevents attacks which utilize pre-computed dictionaries of common passwords

The password that is saved to database is encrypted using bcrypt ruby, it's password methods handle salting on their own, see https://github.com/codahale/bcrypt-ruby
It is the same mechanism used by rails 3.1, see this issue on same subject https://github.com/rails/rails/issues/2191
I think this issue can be closed

Ahh. I searched the source of omiauth-identity for the word "salt" and didn't find it; this explains why.
Thanks for the explanation.
For anyone interested in this topic in the future, the salting method in bcrypt is in this file (on line 59):
https://github.com/codahale/bcrypt-ruby/blob/master/lib/bcrypt.rb#L59
Closing this issue.


load two models report errors

I used a yolov3 trt engine  And a yolov5 trt engine, I tested  both of them  separately and everything is ok.
When put them togethor,Report the below error:

I did not change code in  the yolo_with_plugins.py ,
Only  flollow the https://github.com/jkjung-avt/tensorrt_demos/issues/203#issuecomment-680077788 ,change code in the yolov5_trt.py(this is my custom yolov5 file)
yolov5_trt.py file:
yolov5_trt.txt

Please try the code snippet here: https://github.com/jkjung-avt/tensorrt_demos/issues/219#issuecomment-695429092
If it works, then the problem is likely due to either: 1. the TensorRT yolov5 engine is not built correctly, or, 2. bug in your code.

I have no idea about "./build/libmyplugins.so".  I would have checked if there are name conflicts between the 2 so files...

sorry, I follow the  https://github.com/wang-xinyu/tensorrtx/tree/yolov5-v3.0/yolov5  to gender yolov5.trt file and  the  .so file .
I just copy the file to this project.

As stated earlier, you'll have to resolve naming conflicts between the 2 .so files by yourself.

I edit the two  yolo_layer.cu file,  one for yolov3,another for yolov5 ,
1.change the namespace  yolo3  and yolo5  ,
2. one change  YoloLayerPlugin to YoloLayerPlugin3 , another YoloLayerPlugin5
3. make success
4. test separately (success)
5. test together (fail)
error message:

Maybe can't init the nvinfer1 two times?
Pls give me some advice, Thank you.

The 2 plugins cannot register the same name and version.  After you modify plugin name of one of them, you need to re-build the TensorRT engine with the updated name.
https://github.com/jkjung-avt/tensorrt_demos/blob/bac5085d75e59369cc587cf9ec19f5120836cb3e/plugins/yolo_layer.cu#L337-L345


docs: update ICA auth module section about RegisterInterchainAccount

Description
Updates the documentation about RegisterInterchainAccounts with the addition of the version parameter and using the migration documentation written by @damiannolan.
closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Thanks @crodriguezvega! Apologies I missed this

All good, @damiannolan. Apologies that I also missed it during the review! :)


WIP: Enabling function-level XLA compilation

This is a WIP and needs some changes in TensorFlow as well as the CompilerRuntime.
Please take a look at xla.compile.swift to get a sense for the API to invoke xla compilation. The API is based on tracing.
This PR also has a version of batch norm that uses the API above. It is not working yet:  I have got it compiling, but I am encountering some runtime failures. (Including it in this PR, just as FYI.)

Talking with Gogul, this is now obsolete, so I'll close it out.


PR#18110

Will someone please advise on merging my pull request?  I was hoping I could get it to auto-merge, but it appears to need manual intervention.  Let me know if I can be of any assistance.  Thank you!

Thanks, keone.  I've followed the instructions and tried rebasing to my best understanding, let me know if it can be manually merged now.


Resizing text in Dark Circle tab

The text pulsing in the dark circle tab makes it really hard to read. An option to disable the pulsing text would be nice.

Ok, this will be added in the next major update, thanks for letting me know this was an issue.


rspack.SwcCssMinimizerRspackPlugin generated wrong css content

System Info
System:
    OS: Linux 6.2 Ubuntu 20.04.6 LTS (Focal Fossa)
    CPU: (2) x64 AMD EPYC 7763 64-Core Processor
    Memory: 5.20 GB / 7.74 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 20.10.0 - ~/nvm/current/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 10.2.3 - ~/nvm/current/bin/npm
    pnpm: 8.11.0 - ~/nvm/current/bin/pnpm
  npmPackages:
    @rspack/cli: latest => 0.4.5
    @rspack/core: latest => 0.4.5

Details
SwcCssMinimizerRspackPlugin changes -160deg to 200deg etc., which causes wrong behavior
input
.text {
    color: blue;
    background: conic-gradient(
        from -160deg at 50% 50%,
            #e92a67 0deg,
            #a853ba 120deg,
            #2a8af6 240deg,
            #e92a67 360deg
        );
}

wrong output(rspack+rspack.SwcCssMinimizerRspackPlugin)
.text{color:blue;background:conic-gradient(from 200deg at 50%50%,#e92a67 0deg,#a853ba 120deg,#2a8af6 240deg,#e92a67 0deg)}

output(webpack+CssMinimizerPlugin)
.text{background:conic-gradient(from -160deg at 50% 50%,#e92a67 0deg,#a853ba 120deg,#2a8af6 240deg,#e92a67 1turn);color:blue}head{--webpack-rspack-repro-src_render_js:\.\/src\/render\.css}

Reproduce link
https://github.com/guomio/rspack-issue-SwcCssMinimizerRspackPlugin
Reproduce Steps

git clone https://github.com/guomio/rspack-issue-SwcCssMinimizerRspackPlugin
npm i
npm run build
see the output

It probably caused by SWC CSS parser, can you try using other css minimizer

It probably caused by SWC CSS parser, can you try using other css minimizer

@JSerFeng Indeed, webpack with the following config resulted in the same output. Other minimizers looks ok
optimization: {
    minimize: true,
    minimizer: [
      isRunningWebpack
        ? new CssMinimizerPlugin({ minify: CssMinimizerPlugin.swcMinify })
        : new rspack.SwcCssMinimizerRspackPlugin()
    ]
  }

Fixed by https://github.com/swc-project/swc/pull/9072
And it is recommended to use LightningCssMinimizerRspackPlugin, Rspack will enable LightningCssMinimizerRspackPlugin by default in v1.0.0, see https://www.rspack.dev/plugins/rspack/lightning-css-minimizer-rspack-plugin


Fix finish task

What does this PR do?
This PR fixes the issue within release.finish task when calling add-prelude and add-dca-prelude methods. Both methods require string to be passed, while at the moment there is a custom type, which behaves likes string in many contexts, but not this one.
Motivation
Release process automation.

/merge


Creating a First Page for Wiki

Issue Description
A wiki first page is needed to describe the project. The page must include the title of the project, brief description, the aim and the contributors.
Final Actions
Review for the adequacy is required.
Deadline of the Issue
23.59 - 23.02.2023

Please do see the Home page in wiki.

Looks convenient for now. We will update it as we improve.


Apply deadzone and exponential on joystick inputs

Graph of the equations to double-check the maths is correct: https://www.desmos.com/calculator/hbadgc5z5h