WIP: Change all uses of 'CInt' to 'Int32' in the SDK overlay.

What's in this pull request?
Ready to merge copy of https://github.com/apple/swift/pull/2091
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test and merge


Is zlib-ng fully compatible with zlib? Can zlib and zlib-ng decompress each other?

We have tests to confirm zlib can decompress files created by zlib-ng and vice versa. I can't still say zlib-ng is 100% compatible, but we fix issues as we find them.

Also see #905.


Docker deploy issues w/ RC1

I've had multiple issues when publishing from VS 2015 to a custom docker container after upgrading from Beta8 to RC1.
In the publish web dialog, the image name was empty - previously it defaulted to project name (in lowercase).  I had entered a name starting with uppercase which was rejected by docker, so validation is required on this field to use the same regex as docker does.
On publish, if the container already existed on docker the publish would fail.  Fixed that with:
<DockerRemoveConflictingContainers>True</DockerRemoveConflictingContainers>
After publishing the browser would not automatically start, do I fixed that with:
<LaunchSiteAfterPublish>True</LaunchSiteAfterPublish>
Both of the above were in Beta 8 template, not sure why they were removed in RC1.
The next issue was after starting, the web server was listening on port 5000 as below:

Hosting environment: Production
Now listening on: http://localhost:5000
Application started. Press Ctrl+C to shut down.

I specified Container port as 8080, so this port entry should be used instead.
However, there is interface binding issue raised in https://github.com/OmniSharp/generator-aspnet/issues/472, so I had to manually change the following:
"web": "Microsoft.AspNet.Server.Kestrel",
to
"web": "Microsoft.AspNet.Server.Kestrel --server.urls http://*:8080",
Finally, although this was raised in https://github.com/aspnet/EntityFramework/issues/3089, I got

EntryPointNotFoundException: sqlite3_close_v2 error.

Had to fix this by adding the following to the docker file.  I had done this in Beta 8 as well but I thought the packages would've been fixed for RC1.
RUN echo 'deb http://ftp.us.debian.org/debian jessie main' >> /etc/apt/sources.list && apt-get update && apt-get -y install libsqlite3-dev
I hope these issues can be looked at, but also to document these in case it helps others.

Just wanted to make a note here that I'm encountering this issue right now as well when running the current mono based container.

Hi folks, this seems like an issue with the Docker tooling and publishing experience. We contacted the team that owns that experience and let them know about this issue.

Is there a github issue for the "docker tooling and publishing experience" team that we can subscribe to?

@carolynvs not that I'm aware of, but when I contacted the team that works on that I asked them if there is such a place, or if they can update this issue with their finding. If I hear anything from them I will also update this issue.

Thanks everyone for the feedback. The fixes for the following problems will be included in the next release:

Publishing to a VM with an existing container passes. It's not longer failing as described above

Browser would automatically open the URL pointing to the newly deployed site

In the publishing UI if port number mapping is changed, the site's port number would change. No additional configuration will be required

Thanks

I encountered another issue when using MSDeploy to publish a website to a remote server.  As the build process copies the output to a new folder every time, MSDeploy copies all files as it uses file time stamps from source to determine changes against the target.
Therefore the only appropriate action for MSDeploy is to instead use CRC checksums for file comparisons.  Adding the line below to the pubxml file resolves this problem by copying only files that are changed, but really the -useChecksum should be set by default.
<MSDeployUseChecksum>true</MSDeployUseChecksum>

+1


ci: add a test to validate Zebra's config file and path

Motivation
We want to test that our Docker build scripts configure Zebra correctly:

check that $ZEBRA_CONF_PATH works
make sure the default Docker config works with the latest Zebra version

Fixes #5168
Solution

Add a Docker test for the default config
Add a Docker test for $ZEBRA_CONF_PATH

Review
Anyone can review this, validating the test is using the right configuration
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

Follow Up Work
Use a custom file instead of the existing one living inside common/configs

In the test Docker stage we use cargo test --locked --release --features lightwalletd-grpc-tests --workspace --no-run which doesn't have zebrad as a binary
This is different from the runtime stage as it uses cargo build --locked --release --features sentry --package zebrad --bin zebrad
How should we run zebrad from the test stage @teor2345 ?

I'm not sure I fully understand the question, but I'll try to say some helpful things:

In the test Docker stage we use cargo test --locked --release --features lightwalletd-grpc-tests --workspace --no-run which doesn't have zebrad as a binary

--no-run builds the binaries for the tests, without running any test binaries or the zebrad binary.

This is different from the runtime stage as it uses cargo build --locked --release --features sentry --package zebrad --bin zebrad

This builds the zebrad release binary.

How should we run zebrad from the test stage @teor2345 ?

The test stage should create a zebrad binary for the acceptance tests. It should be in a similar place to the release binary:
https://github.com/ZcashFoundation/zebra/blob/7e5253e27f77399962dd496551119b16a91dc7f3/docker/Dockerfile#L132
(It won't be in the debug directory, because we build tests with --release.)
I think one of the goals of the ticket is automating this manual check from the Zebra release process:
https://github.com/ZcashFoundation/zebra/blob/7e5253e27f77399962dd496551119b16a91dc7f3/.github/PULL_REQUEST_TEMPLATE/release-checklist.md?plain=1#L155
Is it possible to run this test on the release Docker image instead?
If it's not, or it's a lot of effort, that's ok. The test will still cover most of what we need.

Actually, it's a lot easier to do it with the release image 😅
But if we're testing the actual PR, this will crash after we make the release, not before. But we can test it with the image from the main branch, which also uses the runtime stage

@teor2345 so, zebrad start is working as expected as it's generating output and reaching the regex, but using zebrad -c zebra/zebrad/tests/common/configs/v1.0.0-rc.2.toml start is not working, it just hangs and get killed.
I'm not completely sure if this is an issue with the zebrad CLI, but this is reproducible even if I create a new configuration with the same configuration being used in the Dockerfile.
I went to our actual instances and can confirm those are also not generating output

@teor2345 so, zebrad start is working as expected as it's generating output and reaching the regex, but using zebrad -c zebra/zebrad/tests/common/configs/v1.0.0-rc.2.toml start is not working, it just hangs and get killed.

How do you know that it is hanging? It looks to me like it finishes, but doesn't produce any output.

How do you know that it is hanging? It looks to me like it finishes, but doesn't produce any output:

@teor2345 I built and ran the commands locally, even inside the container, and the container exits with an error after it hangs for around a minute.

How do you know that it is hanging? It looks to me like it finishes, but doesn't produce any output:

@teor2345 I built and ran the commands locally, even inside the container, and the container exits with an error after it hangs for around a minute.

It looks like all the commands in the workflow and entrypoint are finishing:
+ exec zebrad -c zebra/zebrad/tests/common/configs/v1.0.0-rc.2.toml start
tee: 'standard output': Broken pipe
+ docker stop variable-conf-tests
variable-conf-tests

https://github.com/ZcashFoundation/zebra/actions/runs/3963283764/jobs/6791366909#step:3:154
But if zebrad was hanging, I think docker logs --follow would continue to run, and so docker stop would never run.
Can you show me the logs of zebrad hanging and getting killed?

If you run docker run zfnd/zebra does it generate output or starts syncing? (I'm in a Mac with M1 and it doesn't, and the ones deployed on GCP are not syncing either)

If you run docker run zfnd/zebra does it generate output or starts syncing? (I'm in a Mac with M1 and it doesn't, and the ones deployed on GCP are not syncing either)

Since this PR changes the entry point script, I'm not sure if running the main branch image will help us here.
Here is the output from Run tests using the $ZEBRA_CONF_PATH:
+ exec zebrad -c zebra/zebrad/tests/common/configs/v1.0.0-rc.2.toml start
error: Zebra could not parse the provided config file. This might mean you are using a deprecated format of the file. You can generate a valid config by running "zebrad generate", and diff it against yours to examine any format inconsistencies.
error: zebrad fatal error: config error: path error: zebra/zebrad/tests/common/configs/v1.0.0-rc.2.toml

https://github.com/ZcashFoundation/zebra/actions/runs/3963766811/jobs/6792068479#step:3:174
It looks like:

the config file isn't at the expected path - where is the Zebra git checkout in the Docker image?
tee isn't echoing the output before it exits - since tee works with longer "docker logs" output and with other tools, it could be a bug in "docker logs" where it doesn't send an end of file or flush its internal buffers before finishing. Printing all the logs at the end seems like enough for now.

Since this PR changes the entry point script, I'm not sure if running the main branch image will help us here.

The main branch does not build the Docker image with the entrypoint (is not included in the runtime stage), so this PR won't have an impact there, even after merged.

https://github.com/ZcashFoundation/zebra/actions/runs/3963766811/jobs/6792068479#step:3:174
It looks like the config file isn't at the expected path - where is the Zebra git checkout in the Docker image?

Right here https://github.com/ZcashFoundation/zebra/blob/feat-conf-test/docker/Dockerfile#L105
This are the result of a pwd and ls

We'll also need to update the patch workflows with the new jobs 🙂

@teor2345 sorry that I dismissed your review with this change

https://github.com/ZcashFoundation/zebra/pull/5968/commits/1beaebd875da34abf968cea6d24c271b7bf1fb3a

Please have a look at it, as this will ensure we test the Dockerfile on both stages: tests and runtime, as the build process is different and this ensures it works in both cases.

Manual deployment to test runtime stage https://github.com/ZcashFoundation/zebra/actions/runs/3982611624

I added these new jobs to the main branch protection rules:

Test Zebra default Docker config file
Test Zebra custom Docker config file


Unable to pass startupapicheck.podLabels within additional_set

additional_set = [
    {
      name = "global.leaderElection.namespace"
      value = module.cert_manager.namespace
    },
    {
      name = "startupapicheck.podLabels.sidecar\\.istio\\.io/inject"
      value = false
    }
  ]

Retruned error is:
Error: failed post-install: warning: Hook post-install cert-manager/templates/startupapicheck-job.yaml failed: Job in version "v1" cannot be handled as a Job: json: cannot unmarshal bool into Go struct field ObjectMeta.spec.template.metadata.labels of type string
I've tried multiple different escape sequences, none of them have worked.
I suppose it is related with escaping. And is related with following issue https://github.com/hashicorp/terraform-provider-helm/issues/64
Any advice how to proceed is welcome.

Thank you. Indeed that was where i have made an error.


Scrolling section menu in docs

The new looks of the docs miss the very handy scrolling (fixed position) section menu it had previously. I hope I'm not the only one missing that.

I'm not sure if we can easily reproduce that in the new setup. One thing I've done to mitigate that is to split things up a bit (hence why the programming guide is now several pages rather than one big document).


Setup JPA configuration.

Do not forget create DB in your PC (name of DB you can check in application.properties, in JDBC link).

It's better to use - "createDatabaseIfNotExist=true" in "spring.datasource.url"
E.g. spring.datasource.url=jdbc:mysql://localhost:3306/GreenCity?createDatabaseIfNotExist=true&useSSL=false&serverTimezone=UTC
So each user won't need to worry about creating a new database


Fix typo in all types parquet yml file (e2e test)

What this PR does / why we need it:
The typo in the e2e test feature set yaml cause the feature set to be registered incorrectly, which is the likely reason as to why the e2e test failed in https://github.com/gojek/feast/pull/676.

/lgtm

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-redis-cluster


Sync with upstream

Depends-On: https://github.com/opentelekomcloud-infra/otc-zuul-jobs/pull/17

recheck

recheck

recheck

recheck

recheck

recheck


Upgrade WSDL to Document/Literal

Currently, the WSDL's generated is using RPC binding style. This is not optimal, and should be changed.

Note, that the WSDL's are constantly checked against a validator.

Due to the complexity of this change, and as it is more of a wish than a requirement, it is pushed to a later release.

Closing this Issue for now - rather than trying to remove IAESTE from the core of this Project, a new one will instead be created.


[spark] Add 'Paimon' prefix for Call Procedure

Purpose

Linked issue: https://github.com/apache/incubator-paimon/issues/2449

Tests

API and Format

Documentation

This is just for call procedure. I will comb though the entire Spark subproject to make the package names and class names more reasonable.


TextExtractor not working at monitor1 on triple monitor

Microsoft PowerToys version
0.77
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
TextExtractor
Steps to reproduce
Not Enabled on Monitor1, Otherwise, Monitor2 and Monitor3 Working.
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

Hello @typedef-int-value this is a known issue and pops up sometimes in some configurations. Can you please attach a /bugreport

PowerToysReport_2024-01-26-15-07-27.zip


test: Fix Curl import test failures for AuditLog

Description

Fix curl import test failures for AuditLog due to missing workspaceId.

Type of change

Test Changes

How Has This Been Tested?

Locally

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=3ac8b70

/ok-to-test sha=c156071


Added link to JS for realtime

Closes #174.
I am a contributing developer of Folium and the developer of the Folium realtime plugin. Great work on streamlit-folium! I use Folium mainly from streamlit, so your package is really useful to me.
To fix the issue I added a link to the javascript file for realtime plugin to the component's public/index.html. I am curious though if streamlit-folium could not be changed to generate these links based on the Folium generated map. We are updating the Folium code base so that users can and and override javascript and css files at runtime. This would break the currently hardcoded list of javascript and css links.
The Folium generated code contains links to include the required javascript and css files. Is there some way these could be included in the generated code?

I am curious though if streamlit-folium could not be changed to generate these links based on the Folium generated map...

Can you split this off into its own issue? If it works, that does seem desirable, but I don't know that it does/the idea will get lost once this obvious fix is merged

LGTM, thanks!
re: using folium to specify the JS and CSS, I have thought about that before https://github.com/randyzwitch/streamlit-folium/issues/115, but haven't come up with a great way to do it. That would certainly help with issues like this where Folium gets updated and knows what new JS packages are to be included.

I am curious though if streamlit-folium could not be changed to generate these links based on the Folium generated map...

Can you split this off into its own issue? If it works, that does seem desirable, but I don't know that it does/the idea will get lost once this obvious fix is merged

Done.


Implement badges with stream history dates

Fixes #786
Fixes #787

@corylown thank you for reviewing!
I guess the reason for that is the following UI instruction from Gary:
If the stream is the current default, use the text Default since followed by the date/time it became the default stream.
So I didn't even consider adding those previous histories. Since I'm doing it already for the previous default/yellow badge, i should be able to fix this pretty easily. Thanks!


Pins on breadboard

Is it possible to have it hook on the breadboard view directly rather than require wires?

Yes, I noticed that the pins don't automatically connect when dropping the teensy onto the breadboard. I am fairly new to Fritzing and assumed this was default behaviour; It would be much better if the connections automatically wired correctly when dropping into the breadboard; I will have to look into this...

I think it is because the pins are not "male" pins. I might be inspired to fix this if this repository gets a star.


Wrong size of Pixi.Graphics() when using PIXI.Sprite() as container

See more: https://codepen.io/anon/pen/jjwero
Possibly related to #5707
Expected Behavior
Parent (PIXI.Sprite()) is 100x100
Child (Pixi.Graphics()) is 50x50
Current Behavior
Parent (PIXI.Sprite()) is 100x100
Child (Pixi.Graphics()) should be 50x50, but the yellow rectangle appears much bigger than it should

pixi.js version: 5.0.4
Browser & Version: Chrome 75
OS & Version: Mac OSX

target.width = 100;
target.height = 100;

And thus, you've changed the sprite scale, and it affects all children. Its the same behaviour as in Adobe Flash.
I've tried to  PR to add size to sprite one or two times but it wasnt approved.
Workaround: use extra container for it.

Working as intended.

https://github.com/pixijs/pixi.js/blob/v4.x/src/core/sprites/Sprite.js#L510

@ivanpopelyshev But the child isn't 100x100 pixels neither. It's much bigger than the parent.


feat: allow broader storage configuration

Fixes #12
Motivations
Discussed in #12
Modifications
This PR changes the structure of the server.storage block and is therefore a breaking change.
This takes the existing storage config (below for reference):
server:
  # Storage definitions related to the palworld-server
  #
  storage:
    external: false
    externalName: ""

    # Keeps helm from deleting the PVC, by default helm does not delete pvcs
    #
    preventDelete: false

    size: 12Gi
    storageClassName: ""

and modifies it to the following, basically moving it under main.
server:
  # Storage definitions related to the palworld-server
  #
  storage:
    main:
      external: false
      externalName: ""

      # Keeps helm from deleting the PVC, by default helm does not delete pvcs
      #
      preventDelete: false

      size: 12Gi
      storageClassName: ""

Then we have the backups key, which supports any Kubernetes Volume spec as it's body. The persistentVolumeClaim is a special case which matches the schema of server.storage.main rather than the Kubernetes Volume spec
server:
  storage:
    backups: {}
      # persistentVolumeClaim:
      #   external: false
      #   externalName: ""
      #   preventDelete: false
      #   size: 12Gi
      #   storageClassName: ""

      # nfs:
      #   server: your.server.ip
      #   path: /path/to/remote/dir

Finally, we have the extra array. This takes a list of objects where name and mountPath are required, along with a Kubernetes volume spec. In extra, the subPath and readOnly of the volume mounts on the deployment are configurable. If a persistentVolumeClaim is used, external can be set to not provision a new PVC, otherwise size, storageClassName, and preventDelete can be used to modify the provisioned PVC. The values.yaml shows several commented examples of this: https://github.com/Twinki14/palworld-server-chart/blob/5fae7415b4228c05a1ebc091e4e032342d65f9ea/charts/palworld/values.yaml#L45-L94

Deployed this HEAD to my cluster with
storage:
    main:
      size: 12Gi
      storageClassName: "longhorn-nvme"

    backups:
      nfs:
        server: my-ip-here
        path: /mnt/data/backups/palworld

and it's been backing up appropriately :)

Will take a deeper look into in the next few days


Android Only, Custom font Quicksand google not apply to Heading but apply well on Text.

Description
On Android (NOT ios), I am trying to custom font family on my react native project (with cli, not expo). Everything seem to work so far, but Heading is not apply font family at all, rare RN Text and gluestack Text seem fine. It's weird.
CodeSandbox/Snack link
No response
Steps to reproduce

Copy quick sand font to fonts folder
Run npx react-native-asset to link assets, check android folder and it copy to it.
Apply font on my custom theme heading, body, mono.
I even try to change fontfamily on props of Heading or custom in Heading component in theme config but it not work.
Update lib to newest, try follow issue on github issue => Not work
"@gluestack-style/react": "^1.0.30",
"@gluestack-ui/config": "^1.0.10",
"@gluestack-ui/themed": "^1.0.31",

gluestack-ui Version
1.0.10
Platform

[ ] Expo
[X] React Native CLI
[ ] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information

Just update:

I trying using FontResolver but it not work. Please check below my image.

hi @Viraj-10 , maybe you can help me with this issue too.
Thank a lot. I am trying my best to understand and using this lib like Native Base before.

I'm facing the same issue
Warning: Failed prop type: Invalid props.style key variantssupplied toText.

Having a similar issue but instead the app just crashes with the following error:
Error: You attempted to set the key fontWeightwith the value"$semibold" on an object that is meant to be immutable and has been frozen.
I am using expo google fonts and load correctly when using react-native Text component, i.e.
<Text style={{ fontFamily: 'NunitoSans_400Regular' }}>Hello</Text>.
But when using glustack's it throws the error.
I am also using the FontResolver with the following mapper:
const fontMapper = (style: any) => {
  let weight = "Regular";
  switch (style.fontWeight) {
    case "100":
      weight = style.fontFamily == "Nunito Sans" ? "ExtraLight" : "Thin";
      break;

    // All other font weight cases...
  }

  const fontFamily = `${style.fontFamily.replace(" ", "")}_${
    style.fontWeight
  }${weight}${style.fontStyle == "italic" ? "_Italic" : ""}`; // End result --> 'NunitoSans_100ExtraLight'

  style = { fontFamily };
  // Not sure if i'm supposed to return the style either..
};

bump! Need support. :(

Can someone from the GluestackUI team, tell us how to import fonts the proper way? I have this font installed in my React Native CLI project

and I'm integrating it into the theme only by doing

Atm the font is applied for my Text components but works only on Regular and Bold. I can't make the other variants work too. Any suggestions or help will be greatly appreciated.

I have the same problem. For now I chose to leave avoid the Heading component and just use the Text component
Then pass a fontFamily prop to the Text component that will make pick up your custom font.

I have the same problem. For now I chose to leave avoid the Heading component and just use the Text component
Then pass a fontFamily prop to the Text component that will make pick up your custom font.

Yep, I found that solution as well. I don't like it, but it is what it is.

I have the same problem. For now I chose to leave avoid the Heading component and just use the Text component
Then pass a fontFamily prop to the Text component that will make pick up your custom font.

Yep, I found that solution as well. I don't like it, but it is what it is.

When I drilled down, I realised this issue seems to be caused from @expo/html-elements instead. The Heading component just cascades all resolved styles to the H4 component of @expo/html-elements. Any way, not 100% certain but will dig deeper and see if I can raise a PR for it.
Best half measure is to abstract the Heading component in a custom shared wrapper so that whenever the issue gets resolved, you don't need to do a lot of refactoring to go the right path.

Facing same issue.

Hey @Digital-Human-BK, The fix will work for RN cli as well.  Can you share the github repo if it is possible? It will help me to debug the issue.

Hi @ankit-tailor, I have looked into you repo and used FontResolver in plugins but it seems not working.
Here is my config code:

Also, I have linked the Fonts in native projects.

Same issue.

Unable to change fontFamily for Heading on Android. Can't even change it to Arial.
Initial font is always Roboto.
No issues on iOS.

Versions:
"@gluestack-style/animation-resolver": "^1.0.3",
"@gluestack-style/react": "^1.0.43",
"@gluestack-ui/config": "^1.1.1",
"@gluestack-ui/themed": "^1.1.0",

Anyone able to use Heading as expected?

Title: Issue with Custom Fonts in React Native Project
Description:
I am facing the same issue - I can't get the font to work correctly in my React Native CLI project. I have local fonts installed using the method outlined in this guide: link to the guide. However, the fontResolver doesn't work for me on either Android or iOS. Without the fontResolver, it works on iOS, but only for the regular and bold fonts; the others are not functional.
Dependencies versions:

@gluestack-style/react: ^1.0.43
@gluestack-ui/config: ^1.1.1
@gluestack-ui/themed: ^1.1.0

Any help or guidance on resolving this font issue would be greatly appreciated!

Still doesn't work for me either. Can we have a reference for a working example? Also, can you add instructions in the docs on using fonts in React Native CLI projects?

Bumping for monitoring as I can am having the same problem where the Text component works correctly but other components aren't pulling it in (header, input placeholder)

For anyone interested in a solution, I've addressed this font issue. Check out the solution in my previous comment here. Feel free to test it, and if it works for you, I'm ready to create a pull request.
Thanks,
Moe

Duplicate of #788.


Contour: TF Function Editor not having any effect

The vertical bars of TF Function Editor of Contour Renderer are movable, but not having any effect.
To reproduce:

Open VAPOR, load Katrina.
Create a Contour Renderer, select MU variable.
Under the Appearance subtab, there are 7 vertical bars by default, and they are movable by mouse.
Weird thing is, moving these bars have no effect on the rendered contours.

I agree, the contour indicator lines should be immovable.


Poor error when calling sentry_sdk.init with too much *args

Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which SDK and version?
sentry_sdk for python version 1.3.1
Steps to Reproduce
>>> import sentry_sdk
>>> sentry_sdk.VERSION
'1.3.1'
>>> sentry_sdk.init(None, 1)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/emmanuel/projects/parsec-cloud/venv/lib/python3.8/site-packages/sentry_sdk/hub.py", line 105, in _init
    client = Client(*args, **kwargs)  # type: ignore
  File "/home/emmanuel/projects/parsec-cloud/venv/lib/python3.8/site-packages/sentry_sdk/client.py", line 84, in __init__
    self.options = get_options(*args, **kwargs)  # type: Dict[str, Any]
  File "/home/emmanuel/projects/parsec-cloud/venv/lib/python3.8/site-packages/sentry_sdk/client.py", line 51, in _get_options
    options = dict(*args, **kwargs)
TypeError: 'int' object is not iterable
>>> sentry_sdk.init(None, 1, 2)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/emmanuel/projects/parsec-cloud/venv/lib/python3.8/site-packages/sentry_sdk/hub.py", line 105, in _init
    client = Client(*args, **kwargs)  # type: ignore
  File "/home/emmanuel/projects/parsec-cloud/venv/lib/python3.8/site-packages/sentry_sdk/client.py", line 84, in __init__
    self.options = get_options(*args, **kwargs)  # type: Dict[str, Any]
  File "/home/emmanuel/projects/parsec-cloud/venv/lib/python3.8/site-packages/sentry_sdk/client.py", line 51, in _get_options
    options = dict(*args, **kwargs)
TypeError: dict expected at most 1 argument, got 2

Expected Result
Client.__init__ should raise an explicit TypeError exception about the fact it only accept one non-kwargs argument.
Actual Result
Currently the client crash due to an improper usage of dict:
https://github.com/getsentry/sentry-python/blob/832263bedca595be1e31a519d4f49f477bd77760/sentry_sdk/client.py#L51

Hey @touilleMan
Thanks for writing in. Yes, here the error message could be way better, I agree.
We will put in on our internal Backelog. (But our backlog right now is quite big, so please don't hold your breath on it! :-))

Added a PR https://github.com/getsentry/sentry-python/pull/1361


Where can I find the API?

The link has been there in docs/README.md

It's statically hosted here: https://patilshreyas.github.io/DummyFoodiumApi/api/posts/

Please use discussions for asking questions/doubts instead of raising an issue


Fix wrong link in docs

No functional changes here, just fixing a wrong link in docs.
jsonSchema was pointing to /api/model/static-properties.html#static-tablename, modified it to point to /api/model/static-properties.html#static-jsonschema

Coverage remained the same at 97.078% when pulling ba2b577a9b7c69887499c93d1943ac034a8c33fc on agarwalrounak:fix-link into 964ad4983d63cf8d238a86209c7643bf0bc7e175 on Vincit:master.

Thank you!


EnableException not showing errors

Backup-DbaDatabase -SqlInstance $sqlinstance -Databases $dbname -BackupDirectory $backupfolderlocation -EnableException:$true
Running the PS script with the above command in TFS (with Fail On Standard Error enabled)
##Expected behaviour
Throw an exception when an incorrect argument  (e.g. sqlinstance that doesn't exist) is passed
##Actual Behaviour
The task gives no error and the deploy is successful.
TFS logs:

TFS PowerShell Task settings:

Hi @potatoqualitee  , thanks for your reply. Due to some reason EnableException with -ErrorAction Stop also doesn't throw any error. However, if I use $WarningPreference = "Stop" with a try catch, then it works in the expected way and throws error.
Could there be any specific reason for this behavior?

It was a issue with the sleepygary version. EnableException shows the desired behaviour with v0.9.393

thanks for the info. ill do a new github release shortly. in general, if possible, I'd stick with syncing to the PowerShell Gallery. It's updated almost daily 👍 Sometimes multiple times per day.


Fix for Pullrequest #736: replacing all occurences of backslash with regex

For paths nested deeper in filesystem it should use the regex-version of replace to replace all occurences of the backslash.
I also updated the sample docs about vs-kubernetes.dotnet-source-file-map because it was pretty unclear to me that a string to the path is expected.
@mattjanson do you agree with the description?

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

@ltsbkuster Yes, I totally agree. I was on the Track the replace function does replace all occurances :(


time: Add timeZone option

Add option for time zone.
Resolves https://github.com/t184256/nix-on-droid-bootstrap/issues/25

force-pushed to solve a trivial conflict in the module list


Can't get 'installcredprovider.ps1' working with 'mcr.microsoft.com/dotnet/core/sdk:3.0'

Hi Guys,
I'm trying to get installcredprovider.ps1 working with mcr.microsoft.com/dotnet/core/sdk:3.0 - without a luck.
Docker file I'm using:
# escape=`

ARG PAT
ARG FEED

FROM mcr.microsoft.com/dotnet/core/sdk:3.0

SHELL ["pwsh", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]

RUN Invoke-WebRequest 'https://raw.githubusercontent.com/microsoft/artifacts-credprovider/master/helpers/installcredprovider.ps1' -OutFile installcredprovider.ps1; `
    .\installcredprovider.ps1 -Version "0.1.19" -Force `
    Remove-Item .\installcredprovider.ps1;

ENV DOTNET_SYSTEM_NET_HTTP_USESOCKETSHTTPHANDLER=0
ENV NUGET_CREDENTIALPROVIDER_SESSIONTOKENCACHE_ENABLED=true
ENV VSS_NUGET_EXTERNAL_FEED_ENDPOINTS='{"endpointCredentials": [{"endpoint":"$(FEED)", "username":"build", "password":"$(PAT)"}]}'

# dotnet copy, restore & build
...

When I don't specify Version I'm getting error that Unable to find the release version. Also blows up when I specify version = 0.1.20
When I specify the version installation is successful but dotnet restore fails with Response status code does not indicate success: 401 (Unauthorized).
Credentials are fine they work when I put them in the Nuget.config file.
Poking around:

script installs netcore plugin in c:\.nuget\plugins.
nothing is present in $env:USERPROFILE\.nuget\plugins folder.
no NUGET_PLUGIN_PATHS env variable defined
if I define NUGET_PLUGIN_PATHS and point toward C:\.nuget\plugins\netcore\CredentialProvider.Microsoft\CredentialProvider.Microsoft.dll - no exceptions thrown but dotnet restore still cannot authenticate.

Any ideas what is going wrong here?

Can you run dotnet restore --interactive --verbosity detailed and share the logs after the line "Using CredentialProvider.Microsoft.dll as a credential provider plugin." so we can investigate why authentication fails? Also, please make sure you're using dotnet SDK version 2.1.400 or later.
When it comes to the ps1 script installing the cred provider to the wrong location, it seems like for some reason your environment can't understand the line [System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::UserProfile. Have you tried the .sh script?

There was an issue with the latest release name, 0.1.20 specifically, which resulted in not being able to use the install script to install that version, but that issue has now been fixed.
Are you still experiencing issues auth with dotnet restore?

I just came across this issue myself.
I've used the .sh script a few times for Linux containers and it's worked like a charm. But now, due to project requirements, we have to run in Windows containers, and I'm having the same issue sakowiczm is with the ps1 file.
I'm not very familiar with Powershell, but I did notice the dotnet/core/sdk:3.0 Dockerfile is installing 7.0.0-preview.4. When I run the Get-Command command in docker the list is a lot smaller than when I run the Get-Command command on my PC outside of docker (Powershell version 5.1). Any chance PS version differences are causing the issue?

I just added some verbose logging to the script. Could you please use the latest script and running it with verbose logging.

Turn verbosity on: $VerbosePreference = "continue"
run installcredprovider.ps1
And then turn verbosity back off: $VerbosePreference = "silentlycontinue"

Maybe it gives some more info. @dasvacina does the script install the cred provider in the wrong location for you as well? If the script installs the cred provider to the wrong location, you could set the NUGET_PLUGIN_PATHS to the CredentialProvider.Microsoft.dll as a workaround. Does that work for you?

Setting the NUGET_PLUGIN_PATHS environment variable to the CredentialProvider.Microsoft.dll worked for me.
Thanks for the help.

There's been a code fix with a workaround in this thread. Please let us know if there's more blocking questions here.

The reason is Credential Provider is not install in C:\Users<currentuser>,
Because in docker image windows microsoft.com/dotnet/core/sdk:3.0 can't resolve [System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::UserProfile (emtpy string) (line 25 in installcredprovider.ps1)
Workaround: alter line 25, from:
$profilePath = [System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::UserProfile)
to
$profilePath = $env:USERPROFILE
You need to add local installcredprovider.ps1 to dockerfile instead of the one from github
Your dockerfile will look like:
FROM mcr.microsoft.com/dotnet/core/sdk:3.1-nanoserver-1903 AS build
WORKDIR /src
COPY ["abc/yourproject.csproj", "abc/"]
ENV VSS_NUGET_EXTERNAL_FEED_ENDPOINTS "{\"endpointCredentials\": [{\"endpoint\":\"https://pkgs.dev.azure.com/xxx/nuget/v3/index.json\"<EMAIL_ADDRESS>\"password\":\"xxxTokenSTRINGxxx\"}]}"

ADD installcredprovider.ps1 .
RUN pwsh -File ./installcredprovider.ps1
RUN dotnet nuget add source https://pkgs.dev.azure.com/xxx/nuget/v3/index.json -n PAB

RUN dotnet restore "abc/yourproject.csproj"


Reaching max timeout on inspecting specification.wiki

While small wiki files seem to work fine, larger ones like specification.wiki seem to take too long (over 1 second) to return a query. This seems odd given that once the file has been parsed I would expect querying the file to be quick.
I may have some bad logic somewhere slowing things down, either on the plugin or server side. First step is to see if there's anything to be done on the plugin.

Running a manual server and querying via graphql playground seems to be really snappy, so there may be something else going on. Need to support writing logs to file so I can monitor vim-launched version.

I don't see the server starting, but this is also the file where the vimwiki plugin encounters errors. Due to vim's nature, this may mean that autocmds are not getting run to launch the server and communicate with it.

Turns out the server works just fine. Seems like the vimwiki plugin errors are causing things to not load.


autoupdate conditionally broken with pwsh core 6

I am trying to switch to powershell core 6 and I have 2 packages in my bucket where one autoupdate check works and the other fails.  Both work under powershell desktop 5.
This package works under both:  https://github.com/matoro/bucket/blob/master/pcsx2-nightly.json
This package works under 5:  https://github.com/matoro/bucket/blob/master/nvidia-display-driver.json
But when run under 6 it spits out:
nvidia-display-driver: An exception occurred during a WebClient request.
URL https://www.nvidia.com/Download/processFind.aspx?psid=95&pfid=694&osid=19&lid=1&whql=&lang=en-us is not valid

Edit:  version tables:
Name                           Value
----                           -----
PSVersion                      6.2.2
PSEdition                      Core
GitCommitId                    6.2.2
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Name                           Value
----                           -----
PSVersion                      5.1.17763.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Cannot reproduce with powershell 5.1.18362.145, 6.2.3, 7.0.0-preview.5

Not even with 6.2.2

Thank you very much for checking.  Would this exception be issued if it were a transient network issue that dropped the request?

Try to mimic code used inside checkver interactively.
https://github.com/lukesampson/scoop/blob/6eb90c9c112c8c6c1790f1bd4e1c9cd67a6e70df/bin/checkver.ps1#L99-L104
https://github.com/lukesampson/scoop/blob/6eb90c9c112c8c6c1790f1bd4e1c9cd67a6e70df/bin/checkver.ps1#L160-L172
Theoritically you could see same result if you do simple (New-Object Net.WebClient).DownloadString('https://www.nvidia.com/Download/processFind.aspx?psid=95&pfid=694&osid=19&lid=1&whql=&lang=en-us') It is not async, but this quick test could give you some insight.

You're right, I can't reproduce it any more.  Guess that means it was just a one-off issue.  Thank you for taking the time to double-check; it's much appreciated.


Semantics fixes

Description
This patch should not be landed before https://github.com/flutter/flutter/pull/34368, and currently has those commits merged in (I'll merge again against master once that one lands).
The rects for a text span may be empty if the text span has been pushed out of view - for example, in a sized box with the height of one line and multiple text spans that span a few lines, where one of the ones out of view also has a gesture recognizer on it.  That triggers NPEs.
I also noticed issues here where we sometimes are passing in infinite values to the node, which we shouldn't be allowing (we never want to draw an infinite rect around something, or allow the a11y node report that it's physically larger by some user defined arbitrarily large/infinite amount).
Related Issues
Fixes https://github.com/flutter/flutter/issues/31949
Fixes https://github.com/flutter/flutter/issues/34433 (I think)
Tests
I added the following tests:
Test that overflows a secondary text span outside the constraints of a sized box.  Without this patch, that test crashes.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

@GaryQian I updated some rects here.  At first I thought it was better but I'm not sure now - it looks off to me.  Maybe we can take a look together tomorrow.

Regarding the ordering issue, it looks like the bug is in the describeSemanticsConfiguration (line 736) where visitChildren is hitting all the children in a row before adding the text itself.


Fix bug when using @SelfValidating with @BeanParam (#2334)

Problem:
When using the new @SelfValidating annotation on a class that is used as a @BeanParam, a 500 error is raised instead of 400/422.
This is described in more detail in #2334.
Solution:
Handle @SelfValidating violations like @ValidationMethod.

@manuel-hegner since you contributed this feature it would be great to get some feedback. Maybe constraint violations were intended to be handled differently and this is the wrong spot for it? Let me know.

I like it, seems sensible. I'll pause for a couple days to merge in case there are comments. Thank you very much for the excellent pull request.

I would agree that a 4XX is the expected behaviour. This is an excellent addition.


Update link to widget data source in data-view.md

Updates the link which should point to the page 'Listen to widget source' instead of 'Microflow source'

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


provide some overviews of models / gpus to run these as a "tricks and tips"?

Thanks for an amazing project!
One of the challenges when getting started with these llm lsps is getting a feeling for what is reasonable to run on different hardware.
Would it be within scope to have a dedicated documentation section with a few tables, recommending what model / config to use for different hardware? For example if I have on a CPU, what is a reasonable LLM to run? If I have a 4080 GPU, what is a good choice? I wonder if it feels a bit like a jungle otherwise for newcomers (at least it is my feeling now :) ).

This is a really good point. This project has an education problem. To use this project effectively you must not only have a decent understanding of LLMs, you must have a good understanding of the LSP.
This is something I have been thinking about and I have a few ideas. The main one being an auto configurator website where you are asked a series of questions and tick a series of boxes and are given a configuration.
Stay tuned.


Fix GetBranch response

I want to get a time of the last commit in branch. I read Github API: Get Branch docs and found the RepositoriesService.GetBranch method. I called it like so:
client.Repositories.GetBranch(orgName, repoName, branchName)

But get the following data (e.g. for this repo):
{
	github.Commit {
		SHA:"5c45bca952b96dedace6c307caff915483013003",
		Author:github.CommitAuthor{},
		Committer:github.CommitAuthor{},
		Parents:[
			github.Commit{
				SHA:"5c5ff1dadae3bb0b306004d480a88e7ddc1714ca",
				URL:"https://api.github.com/repos/google/go-github/commits/5c5ff1dadae3bb0b306004d480a88e7ddc1714ca"
			}
		],
		URL:"https://api.github.com/repos/google/go-github/commits/5c45bca952b96dedace6c307caff915483013003"
	}
}

As you see, the Author and Committer fields has no info. I tried to call the endpoint with curl:
curl -H 'Accept: application/vnd.github.v3+json' \
     -H "Authorization: token ${MY_GITHUB_TOKEN}" \
     "https://api.github.com/repos/google/go-github/branches/master"

And get data I expected:
{
  "name": "master",
  "commit": {
    "sha": "5c45bca952b96dedace6c307caff915483013003",
    "commit": {
      "author": {
        "name": "Ronak Jain",
        "email"<EMAIL_ADDRESS>        "date": "2016-12-09T18:12:45Z"
      },
      "committer": {
        "name": "Glenn Lewis",
        "email"<EMAIL_ADDRESS>        "date": "2016-12-09T18:58:51Z"
      },
      "message": "improve docs ...",
      "tree": {
        "sha": "de558bd3716b5304a7d40e90c4871a5173ac40a2",
        "url": "https://api.github.com/repos/google/go-github/git/trees/de558bd3716b5304a7d40e90c4871a5173ac40a2"
      },
      "url": "https://api.github.com/repos/google/go-github/git/commits/5c45bca952b96dedace6c307caff915483013003",
      "comment_count": 0
    },
    ...
  }
}

Looks like commit at the root of response is a RepositoryCommit.

I signed it!

You're absolutely right. It was surprising to me that we'd have such a glaring error, so I dug through git blame to see how it occurred (in order to make sure I'm not overlooking something).
It seems we've had the issue since its very initial implementation in 2014. From that commit, I have a pretty good of how it happened. ListBranches was implemented first, and Branch type was created for it.
If you look at https://developer.github.com/v3/repos/branches/#list-branches, you'll see the example that the list endpoint provides has only "sha" and "url" fields inside the "commit" object. A coincidence is that both Commit and RepositoryCommit have those fields, so it's easy to use one instead of the other.
GetBranch was added later and seemingly no one else ran into this until now (or reported it).
Thanks for the patch!

Thank you, @isqua and @shurcooL!
LGTM. Merging.

Included in https://github.com/google/go-github/commit/a77ccc9a588d217ea8c8b069620a3a070ed201c3.


[release-1.21] etcd member management controller

Backport of: https://github.com/k3s-io/k3s/issues/3973

Validated on release-1.21 branch commit 863512e0555662e4bc72c3722c13c04c62e92386

Performed the first 4 steps mentioned in https://github.com/k3s-io/k3s/pull/4001. Note the one difference is the annotation to watch for on the node has a cattle in it, so it is: etcd.k3s.cattle.io/removed-node-name
Observed when adding the annotation and it is removed from the etcd cluster, the node goes to a NotReady state and the k3s logs are correctly angry with:

Sep 14 23:26:58 ip-172-31-3-152 k3s[1393]: E0914 23:26:58.235065    1393 leaderelection.go:325] error retrieving resource lock kube-system/k3s: etcdserver: server stopped
Sep 14 23:26:58 ip-172-31-3-152 k3s[1393]: E0914 23:26:58.909675    1393 status.go:71] apiserver received an error that is not an metav1.Status: rpctypes.EtcdError{code:0xe, desc:"etcdserver: server stopped"}: etcdserver: server stopped
Sep 14 23:26:58 ip-172-31-3-152 k3s[1393]: E0914 23:26:58.910196    1393 leaderelection.go:325] error retrieving resource lock kube-system/kube-controller-manager: etcdserver: server stopped

Restarting the k3s service on this deleted node adds it back to the etcd cluster as is visible by etcd member list. It does correctly have a different Name there now. Furthermore, the added annotation etcd.k3s.cattle.io/remove is set to false, the programmatically added annotation of etcd.k3s.cattle.io/removed-node-name is no longer present, and the other related etcd annotation for its name has been properly updated to be the new etcd name value.
systemd did not try to restart the service itself, however upon rebooting the node, the service is correctly restarted and rejoins the cluster
Applying the value as a label instead of an annotation does not have any effect
Am able to remove the label on a node that has it set to false with no side effects
Applying the annotation to 2 nodes in a 3 server cluster does NOT cause a quorum loss as both nodes are simply removed from the etcd cluster.
Am able to apply the label, restart the service, apply the label again, and delete the node after it is removed from etcd.
Am able to apply the label and see proper handling after an upgrade, but opened #4023 for potentially related issue due to node deletion after an upgrade.


data viz updates

add bike <- read_csv(file = "http://jhudatascience.org/intro_to_r/data/Bike_Lanes.csv") to the lab for data viz for folks who can't get jhur
maybe rearrange the slides that have to do with theme() till later

[ ] Use ggplot2 package to make plot of average length of lanes (lane_avg_length; y-axis) for each year (dateInstalled; x-axis). You can use lines layer (+ geom_line()) or points layer (+ geom_point()), or both!

maybe show the other way of doing scale_x_continous - with to from by

[ ] maybe add back how to add equations and error bars? but don't walk through it just say that you can
[ ] maybe cut back on some of the theme stuff? idk seemed a tad long but I was tired :P

Noting that we talk about adding formulas in the stats lecture :)

[ ] DaSEH updates


Validate being called even when validateAfter is set to false in Write

We have set validateAfter to false in our models, but Validate is still being called. It appears to be due to the fact that PropertyChanged is being signed up for in the constructor. When that fires, validate is always being called and we have no way to override that.
Is there some way within the current code base to only have validate triggered manually? We can wait to set the Validator property and then remove it, but that seems like a hack.

Well It has been a long time man, but the Issue was on the ValidatetableModelBase constructor, I had edited Validate Method so we can have more control on validation so we can be able to triggered validate automatically or manually. Hopefully Jerry Nixon finds it good enough for usage.


Update version

This old jsonwebtoken version produce panic on M1 machine.

Thanks !

@yoshidan Could you please release a new version of google-cloud-auth with this updated dependency? We're seeing the same issue on our side. Thanks!

@alexkirsz Now we have released a new version.
google-cloud-auth = "0.13.1"


Blazor: ElementReference cannot be passed as a Parameter

Describe the bug
When trying to pass an ElementReference as a parameter to a component, the Id of the reference is not set.
Because the parameter is passed before rendering, but the ElementReference is not valid until after the render, the Id passed is null.
The ElementReference Id changing should cause the child component's Parameters to be set again.
To Reproduce
Index.razor
@page "/"

<input value="A" class="form-control" />
<input value="B" class="form-control" @ref=PageOneFocusControl />
<input value="C" class="form-control"/>
<AutoFocus Control=PageOneFocusControl @ref=MyAutoFocus/></br/>
Reference = @PageOneFocusControl.Id
<button type="button" @onclick=@SetTheReferenceManually>Set the reference manually</button>

@code {
	ElementReference PageOneFocusControl;
	AutoFocus MyAutoFocus;

	private void SetTheReferenceManually()
	{
		MyAutoFocus.SetControl(PageOneFocusControl);
	}
}

AutoFocus.razor
@inject IJSRuntime JSRuntime
@code {
	[Parameter]
	public ElementReference Control { get; set; }

	public void SetControl(ElementReference control)
	{
		Control = control;
	}

	protected override void OnParametersSet()
	{
		System.Diagnostics.Debug.WriteLine("=============OnParametersSet===========");
		if (string.IsNullOrEmpty(Control.Id))
			System.Diagnostics.Debug.WriteLine("Control.Id is NULL");
		else
			System.Diagnostics.Debug.WriteLine("Control.Id is SET CORRECTLY!!!");
	}
}

1: Run the app (Client-side blazor app)
2: Note the Id displayed on screen has no value
3: Note the output in the browser console says Control.Id is NULL
4: Click the button to set the parameter manually
5: The Id now displays correctly and the output in the browser console says Control.Id is SET CORRECTLY

@mrpmorris Thanks for contacting us.
I believe that's by design. ElementReference instances are only valid after the component in which they are defined has been rendered. If you pass them down to child component I believe there's no guarantee they'll work correctly, as in Blazor components render independently (A parent re-rendering doesn't mean a child re-renders) so you can't know from the child component whether the reference is correct or not.
To achieve your scenario, it would make more sense to simply perform a JS Interop call inside the OnAfterRenderAsync method of the parent component to set the focus to the desired form control.

I know it is by design, the important part of my report was
"The ElementReference Id changing should cause the child component's Parameters to be set again."

"The ElementReference Id changing should cause the child component's Parameters to be set again."

That is not how the Blazor rendering model works.
The component is responsible to tell Blazor when it needs to be rerendered. Blazor doesn't proactively look for changes in the component state/model to decide when a component needs to be re-rendered.

I realise that, that's why I said the child component's Parameters should be set again.
Whatever the solution is, passing element references as parameters currently does not work.
If it is chosen to not be supported, then perhaps a compiler warning should be raised when a [Parameter] ElementReference is declared.


RSConnect: speed up pin_search by allowing using guid behind the scenes

Currently, python pins with RSConnect needs to look up the user and content guid for actions like
fs.info("michael.chow/mtcars")

however, looking up the user guid requires iterating through all users. This is an expensive operation that R pins does as little as possible by using the guids whenver possible (through a local cache file).
Let's support something like
# similar protocol format to sqlalchemy uris
# may need to use "rsc://guid+<user_guid>
fs.info("rsc+guid://<user_guid>")                  # GET v1/users/{guid}
fs.info("rsc+guid://<user_guid>/<content_name>")   # GET v1/content?name=<content_name>?user_guid=<user_guid>

fs.info("rsc+guid://content/<content_guid>")       # GET v1/content/<content_guid>

Note that we must meet these criteria...

Files are cached correctly (e.g. could use the guids for everything in the cache)
Users do not need to specify guid in pin_* methods
We could allow users to specify guid in pin_* methods if it's not a lot of work. Otherwise, could start by having pins use it as an internal fast path.

For now, let's inform people how many pins match the search, and that the search could take a while to return resutls.

Ideally I think we'd fix this upstream on the connect side.


DNS resolution of hosNetwork pods (e.g. Restric Backup Addon)

What happened:
As using kubeone as seed cluster provisioner (on vSphere), we applied the restrict addon with the target to use the in cluster minio service minio.minio.svc.cluster.local. Unfortunately this didn't worked, because the in cluster DNS name didn't get resolved.
backup job yaml
apiVersion: v1
kind: Secret
metadata:
  name: s3-credentials
  namespace: kube-system
type: Opaque
data:
  AWS_ACCESS_KEY_ID: xxxxxxxxxxxxxx
  AWS_SECRET_ACCESS_KEY: xxxxxxxxxxxxxxxxxxxxxx
---
apiVersion: v1
kind: Secret
metadata:
  name: restic-config
  namespace: kube-system
type: Opaque
data:
  password: xxxxxxxxxxxxxxxxxxxxxxxx
---
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: etcd-s3-backup
  namespace: kube-system
spec:
  concurrencyPolicy: Forbid
  failedJobsHistoryLimit: 1
  schedule: '@every 30m'
  successfulJobsHistoryLimit: 0
  suspend: false
  jobTemplate:
    spec:
      template:
        spec:
          hostNetwork: true
          nodeSelector:
            node-role.kubernetes.io/master: ""
          tolerations:
          - key: node-role.kubernetes.io/master
            effect: NoSchedule
            operator: Exists
          restartPolicy: OnFailure
          volumes:
          - name: etcd-backup
            emptyDir: {}
          - name: host-pki
            hostPath:
              path: /etc/kubernetes/pki
          initContainers:
          - name: snapshoter
            image: {{ Registry "gcr.io" }}/etcd-development/etcd:v3.4.3
            imagePullPolicy: IfNotPresent
            command:
            - /bin/sh
            - -c
            - |-
              set -euf
              mkdir -p /backup/pki/kubernetes
              mkdir -p /backup/pki/etcd
              cp -a /etc/kubernetes/pki/etcd/ca.crt /backup/pki/etcd/
              cp -a /etc/kubernetes/pki/etcd/ca.key /backup/pki/etcd/
              cp -a /etc/kubernetes/pki/ca.crt /backup/pki/kubernetes
              cp -a /etc/kubernetes/pki/ca.key /backup/pki/kubernetes
              cp -a /etc/kubernetes/pki/front-proxy-ca.crt /backup/pki/kubernetes
              cp -a /etc/kubernetes/pki/front-proxy-ca.key /backup/pki/kubernetes
              cp -a /etc/kubernetes/pki/sa.key /backup/pki/kubernetes
              cp -a /etc/kubernetes/pki/sa.pub /backup/pki/kubernetes
              etcdctl snapshot save /backup/etcd-snapshot.db
            env:
            - name: ETCDCTL_API
              value: "3"
            - name: ETCDCTL_DIAL_TIMEOUT
              value: 3s
            - name: ETCDCTL_CACERT
              value: /etc/kubernetes/pki/etcd/ca.crt
            - name: ETCDCTL_CERT
              value: /etc/kubernetes/pki/etcd/healthcheck-client.crt
            - name: ETCDCTL_KEY
              value: /etc/kubernetes/pki/etcd/healthcheck-client.key
            - name: ETCD_HOSTNAME
              valueFrom:
                fieldRef:
                  fieldPath: spec.nodeName
            volumeMounts:
            - mountPath: /backup
              name: etcd-backup
            - mountPath: /etc/kubernetes/pki
              name: host-pki
              readOnly: true
          containers:
          - name: uploader
            image: {{ Registry "docker.io" }}/restic/restic:0.9.6
            imagePullPolicy: IfNotPresent
            command:
            - /bin/sh
            - -c
            - |-
              set -euf
              restic snapshots -q || restic init -q
              restic backup --tag=etcd --host=${ETCD_HOSTNAME} /backup
              restic forget --prune --keep-last 48
            env:
            - name: ETCD_HOSTNAME
              valueFrom:
                fieldRef:
                  fieldPath: spec.nodeName
            - name: RESTIC_REPOSITORY
              value: "s3:http://minio.minio.svc.cluster.local:9000/kubermatic-etcd-backups"
            - name: RESTIC_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: restic-config
                  key: password
            - name: AWS_DEFAULT_REGION
              value: "<<AWS_DEFAULT_REGION>>"
            - name: AWS_ACCESS_KEY_ID
              valueFrom:
                secretKeyRef:
                  key: AWS_ACCESS_KEY_ID
                  name: s3-credentials
            - name: AWS_SECRET_ACCESS_KEY
              valueFrom:
                secretKeyRef:
                  key: AWS_SECRET_ACCESS_KEY
                  name: s3-credentials
            volumeMounts:
            - mountPath: /backup
              name: etcd-backup

Due to some debugging I find out that the /etc/resolv.conf of the job pod didn't contain the search domains. After some research, it seams that using the hostNetwork: true could somehow cause that DNS resolution doesn't work. Maybe also the combination with flannel is a issue. Some ref. upstream issues:

https://github.com/kubernetes/kubernetes/issues/88986
https://github.com/coreos/flannel/issues/1243

backup pod, without searchdomain:
# cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search localdomain

normal POD
cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search default.svc.cluster.local svc.cluster.local cluster.local localdomain
options ndots:5

As I don't think this a normal behavior, we should may investigate the DNS Resolution issue.
What is the expected behavior:

The provided backup addon should work with in cluster svc
In cluster DNS names should get resolved also for hostnetwork=true

How to reproduce the issue:

Deploy kubeone cluster, with kubermatic minio + restric backup addon, introduced with PR #855
Cluster DNS resolution should wirk with hostNetwork=true

Anything else we need to know?
Issue happend in two different environments on vsphere. At my Lab setup (https://github.com/kubermatic-labs/kubermatic-demo/tree/master/vsphere) + customer
Information about the environment:
KubeOne version (kubeone version):
{
  "kubeone": {
    "major": "1",
    "minor": "1",
    "gitVersion": "v1.1.0",
    "gitCommit": "3e84d523a75cd178a7801a0fccf2b3195db3a376",
    "gitTreeState": "",
    "buildDate": "2020-11-17T23:13:15+01:00",
    "goVersion": "go1.15.2",
    "compiler": "gc",
    "platform": "linux/amd64"
  },
  "machine_controller": {
    "major": "1",
    "minor": "19",
    "gitVersion": "v1.19.0",
    "gitCommit": "",
    "gitTreeState": "",
    "buildDate": "",
    "goVersion": "",
    "compiler": "",
    "platform": "linux/amd64"
  }
}

Operating system: ubuntu
Provider you're deploying cluster on: vsphere
Operating system you're deploying on: ubuntu 18.04
workaround
For the backup location itself a the service IP of the minio svc could be used: kubectl get svc -n minio. Unfortunately this only as long stable as the service won't get redeployed

will try it and let you know

@xmudrii it seams to work:
k logs --all-containers test-backup-job-gdbp8 -f
{"level":"info","ts":1606845603.9692698,"caller":"snapshot/v3_snapshot.go:110","msg":"created temporary db file","path":"/backup/etcd-snapshot.db.part"}
{"level":"warn","ts":"2020-12-01T18:00:03.988Z","caller":"clientv3/retry_interceptor.go:116","msg":"retry stream intercept"}
{"level":"info","ts":1606845603.9892063,"caller":"snapshot/v3_snapshot.go:121","msg":"fetching snapshot","endpoint":"<IP_ADDRESS>:2379"}
{"level":"info","ts":1606845605.7280579,"caller":"snapshot/v3_snapshot.go:134","msg":"fetched snapshot","endpoint":"<IP_ADDRESS>:2379","took":1.758665093}
{"level":"info","ts":1606845605.7292426,"caller":"snapshot/v3_snapshot.go:143","msg":"saved","path":"/backup/etcd-snapshot.db"}
Snapshot saved at /backup/etcd-snapshot.db
Fatal: unable to open config file: Stat: The specified key does not exist.
Is there a repository at the following location?
s3:http://minio.minio.svc.cluster.local:9000/kubermatic-etcd-backups
created new cache in /root/.cache/restic

Files:           9 new,     0 changed,     0 unmodified
Dirs:            0 new,     0 changed,     0 unmodified
Added to the repo: 34.631 MiB

processed 9 files, 34.631 MiB in 0:03
snapshot af93cda6 saved
Applying Policy: keep the last 48 snapshots snapshots
keep 1 snapshots:
ID        Time                 Host                         Tags        Reasons        Paths
----------------------------------------------------------------------------------------------
af93cda6  2020-12-01 18:00:09  tobi-kubeone-vsphere-1-cp-1  etcd        last snapshot  /backup
----------------------------------------------------------------------------------------------
1 snapshots

I think we need a fix also for KKP backup container:
There we also specify: ClusterFirst, what I already see some issue:
kget-exp cronjob
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: etcd-backup-xxnxgh44nn
  namespace: kube-system
  ownerReferences:
    - apiVersion: kubermatic.k8s.io/v1
      blockOwnerDeletion: true
      controller: true
      kind: Cluster
      name: xxnxgh44nn
      uid: 6f9e0368-3139-4915-96ca-2b529247c738
spec:
  concurrencyPolicy: Forbid
  failedJobsHistoryLimit: 1
  jobTemplate:
    metadata:
      creationTimestamp: null
    spec:
      template:
        metadata:
          creationTimestamp: null
        spec:
          containers:
            - command:
                - /bin/sh
                - -c
                - |
                  set -euo pipefail

                  endpoint=minio.minio.svc.cluster.local:9000
                  bucket=kubermatic-etcd-backups

                  s3-storeuploader store --file /backup/snapshot.db --endpoint "$endpoint" --bucket "$bucket" --create-bucket --prefix $CLUSTER
                  s3-storeuploader delete-old-revisions --max-revisions 20 --endpoint "$endpoint" --bucket "$bucket" --prefix $CLUSTER
              env:
                - name: ACCESS_KEY_ID
                  valueFrom:
                    secretKeyRef:
                      key: ACCESS_KEY_ID
                      name: s3-credentials
                - name: SECRET_ACCESS_KEY
                  valueFrom:
                    secretKeyRef:
                      key: SECRET_ACCESS_KEY
                      name: s3-credentials
                - name: CLUSTER
                  value: xxnxgh44nn
              image: quay.io/kubermatic/s3-storer:v0.1.4
              imagePullPolicy: IfNotPresent
              name: store-container
              resources: {}
              terminationMessagePath: /dev/termination-log
              terminationMessagePolicy: File
              volumeMounts:
                - mountPath: /backup
                  name: etcd-backup
          dnsPolicy: ClusterFirst
          initContainers:
            - command:
                - /bin/sh
                - -c
                - |-
                  backupOrReportFailure() {
                    echo "Creating backup"
                    if ! eval $@; then
                      echo "Backup creation failed"
                      return 1
                    fi
                    echo "Successfully created backup, exiting"
                    exit 0
                  }
                  backupOrReportFailure etcdctl --endpoints https://etcd-0.etcd.cluster-xxnxgh44nn.svc.cluster.local.:2379 snapshot save /backup/snapshot.db
                  backupOrReportFailure etcdctl --endpoints https://etcd-1.etcd.cluster-xxnxgh44nn.svc.cluster.local.:2379 snapshot save /backup/snapshot.db
                  backupOrReportFailure etcdctl --endpoints https://etcd-2.etcd.cluster-xxnxgh44nn.svc.cluster.local.:2379 snapshot save /backup/snapshot.db
                  echo "Unable to create backup"
                  exit 1
              env:
                - name: ETCDCTL_API
                  value: "3"
                - name: ETCDCTL_DIAL_TIMEOUT
                  value: 3s
                - name: ETCDCTL_CACERT
                  value: /etc/etcd/client/ca.crt
                - name: ETCDCTL_CERT
                  value: /etc/etcd/client/backup-etcd-client.crt
                - name: ETCDCTL_KEY
                  value: /etc/etcd/client/backup-etcd-client.key
              image: gcr.io/etcd-development/etcd:v3.4.3
              imagePullPolicy: IfNotPresent
              name: backup-creator
              resources: {}
              terminationMessagePath: /dev/termination-log
              terminationMessagePolicy: File
              volumeMounts:
                - mountPath: /backup
                  name: etcd-backup
                - mountPath: /etc/etcd/client
                  name: cluster-xxnxgh44nn-etcd-client-certificate
          restartPolicy: OnFailure
          schedulerName: default-scheduler
          securityContext: {}
          terminationGracePeriodSeconds: 30
          volumes:
            - emptyDir: {}
              name: etcd-backup
            - name: cluster-xxnxgh44nn-etcd-client-certificate
              secret:
                defaultMode: 420
                secretName: cluster-xxnxgh44nn-etcd-client-certificate
  schedule: '@every 20m'
  successfulJobsHistoryLimit: 0
  suspend: false


Duplicate Content check can cause problems in specific languages

We currently have the problem that we have a translation for Country, like USA or Germany, and Country, the style or synonyme for Countryside. This causes problems with the duplicate check as it fails only in the english translations not i.e. the german as we have Land and Country there. As they mean something different by context and are spelled differently in german we cannot aggregate them to one key. This is probably not the only word and langauge where this can cause problems.
For now, which fixes this problem in our case, the filter logic for the key would be suffice so I've implemented it for yaml: #35
But in any other case this maybe would not be enough so I think we need to think about another possibility to fix this issue. My first idea would be to have a whitelist option for the duplicate content rule. Probably you also need to make it language specific as you want Country twice in english but only once in german.
Would that be a viable solution or are there any better ones? I'm happy to implement it but wanted your feedback first.

Hi
i think i dont really get it
duplicate check is only for the content, if Germany and Deutschland are different as values then its not duplicate?
do you have an example?
thank you

Following Example Translation Files:
admin.en.yaml
app:
    title:
        country: Country
    style:
        country: Country

admin.de.yaml
app:
    title:
        country: Land
    style:
        country: Country

This would result in a duplicate content for the admin.en.yaml but not admin.de.yaml. In other cases we would consolidate both translations into one so we have no duplicates. In this case this is not possible as in german those translations are written different and cannot be consolidated into one translation.
Therefore my proposal was to have a file/language specific filter option for that rule so we can exclude country for the english translation file.

Hi
implemented in the latest dev-master :)
thanks for this great idea

released in 1.17.0


OTT-248: Increase section title limit

Jira link
https://transformuk.atlassian.net/browse/OTT-248
What?
I have added/removed/altered:

[ ] Increase section title limit

Why?
I am doing this because:

We need to update a title that is more than 255 characters in length

Deployment risks (optional)

Includes destructive/migratory actions which may effect critical data

@jebw changes added to structure.sql. I'm skipping the nicer DSL change as I have already tested the raw version and the result would be the same so would like to save some time


bug: fix trivy scanning so that rbac roles are deleted

Trivy scanning was creating rbac roles that could not be deleted. Changing the Role Based Access Control on nodesig-agent-identity to be over the resource group and not the container means that the lock on the storage account wont affect the deletion of rbac roles

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.006%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2626

Relevant Lines:
3455

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.006%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2626

Relevant Lines:
3455

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 76.006%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2626

Relevant Lines:
3455

💛  - Coveralls


Walk auxiliary declarations when gathering stored properties

Make sure we walk auxiliary declarations when gathering stored properties. This ensures that we will get any stored properties introduced by peer macros.
Fixes rdar://108534298.

@swift-ci please test


To remove depreciated url patterns for Django 1.10

Django 1.10 is removing the depreciated urls patterns, so this update removes patterns where appropriate.

Thanks @tdsymonds . I'll push it to PyPi tonight.

@tdsymonds don't forget to star this repo :-)