[User Interface: Redesign]: Computational Tool Resources page update

Issue Name
Computational Tool Resources page update
Issue Description
The Computational Tool Resources page should be updated to reflect the improvements made to the Computational Tools cards
Issue Discussion
This issue was discussed at the biweekly meeting dated 2024.11.12
Mockup URL
No response
WCAG Compliance Check

[ ] The ui changes are not expected to significantly affect WCAG compliance (ex- wording changes)
[X] The ui changes have visual elements which have yet to be tested for WCAG compliance
[ ] The ui changes have visual elements which have been tested for WCAG compliance
[ ] The ui changes have passed all checks for WCAG compliance

Related WBS task

[X] Check here if the ui change is centered on the look and feel (https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/52)
[ ] Check here if the ui change includes new features (https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/53)
[ ] Check here if the ui change was suggested by the NIAID team (https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/2)

For internal use only. Assignee, please select the status of this issue

[ ] Not yet started
[x] In progress
[ ] Blocked
[ ] Will not address

Status Description
No response
UI change status check list

[ ] This ui change has yet to be discussed between NIAID, Scripps, Leidos
[X] This ui change has been discussed/reported between NIAID, Scripps, Leidos
[ ] This ui change has been mocked up
[ ] This ui change has been implemented on Dev
[ ] This ui change has been approved for Staging
[ ] This ui change has been implemented on Staging
[ ] This ui change has been approved for Production
[ ] This ui change has been implemented on Production

Hi @hartwickma, @rshabman, @lisa-mml, @sudvenk,
The ComputationalTool-related UI changes are now on Staging awaiting approval for Production. This includes updates for:

the cards
the resources page (this issue)
the landing page search options

The following updates cannot be applied to staging (due to the STRAPI pages already being published), so the updates will need to be approved in google docs before moving to production:

the documentation

The following changes are under investigation:

Facets and filter updates

ComputationalTool is now on production. I am marking this issue as pending close out


Referencing playlist player

There is a different ticket #20 to support a playlist all from a single feed, this is to also support that single feed having reference elements in the items to indicate that the items come from different rss feeds.
This will cause visual changes, such as displaying the source podcast for an episode and the image, as well as functional changes such as navigating to this referenced podcast (TBD)

Is this still something we want to add @kookster ? Or is mixed-RSS feed playlist generation more in RP land these days?

@gcampo88 https://github.com/PRX/play.prx.org/pull/119 Working on it :)

ah yes the 124 commit wonder! :) 👍 @chrisrhoden


Add Get/Set Method for model by field name

model.Get value by field name
model.Set value by field name

Done!


Please add dark mode.

please add dark mode. thanks!

something like this

Hi @0xearl
Thanks for your suggestion. Unfortunately, I don't have time to investigate adding dark mode at the moment.
Of course, I'd welcome a PR that would add this functionality.
Thanks again.
Best,
John

ill try to make it, should be easy enough for me

[dark mode]

Upgraded to VuePress 2.x which contains a default theme with dark mode options out-of-the-box.
https://github.com/Jhnbrn90/LaravelPackage.com/pull/109
I've provided a full explanation within the PR: https://github.com/Jhnbrn90/LaravelPackage.com/pull/108


ReverseDiff Error with Vector{Real} Input in Turing Model

Hi everyone!
We stumbled upon an issue when fitting a Turing model using ReverseDiff if the inputs are  Vector{Real}.
Minimal Working Example
using Turing, ReverseDiff, Distributions, LogExpFunctions

@model function some_model(x, y)

    parameter ~ Uniform(0, 30)

    for i in eachindex(y)
        probabilities = softmax(x[i] * parameter, dims=1)
        distribution = Categorical(probabilities)
        y[i] ~ distribution
    end
end

### This will work
log_probabilities = [
[-4.226834039860986, -1.10380534825695, -1.3485838864717796],
[-2.7411713024220434, -2.3756404263051873, -0.9992390187038857],
[-2.4084973027747805, -1.1944158586117868, -1.3887071333579988],
[-3.3499522854558443, -0.9086409330664779, -2.604388503142469],
[-2.3371073076367623, -1.3779453250505502, -1.0720136146812946]]

### This will crash
log_probabilities = [
Real[-4.226834039860986, -1.10380534825695, -1.3485838864717796],
Real[-2.7411713024220434, -2.3756404263051873, -0.9992390187038857],
Real[-2.4084973027747805, -1.1944158586117868, -1.3887071333579988],
Real[-3.3499522854558443, -0.9086409330664779, -2.604388503142469],
Real[-2.3371073076367623, -1.3779453250505502, -1.0720136146812946]]

outcomes = [2,3,2,2,3]

my_model = some_model(log_probabilities, outcomes)

results = sample(my_model, NUTS(-1, 0.65; adtype=AutoReverseDiff(true)), 100)

Error Message:
In the case where our log_probabilities are Vector{Real} this results in the following error:
ERROR: MethodError: no method matching increment_deriv!(::Float64, ::Float64)

Closest candidates are:
  increment_deriv!(::ReverseDiff.TrackedReal, ::Real)
   @ ReverseDiff .julia\packages\ReverseDiff\p1MzG\src\derivatives\propagation.jl:45
  increment_deriv!(::AbstractArray, ::Any)
   @ ReverseDiff .julia\packages\ReverseDiff\p1MzG\src\derivatives\propagation.jl:38
  increment_deriv!(::ReverseDiff.TrackedArray, ::Real, ::Any)
   @ ReverseDiff .julia\packages\ReverseDiff\p1MzG\src\derivatives\propagation.jl:34

Now, the obvious solution is to simply keep our inputs as Vector{Float64} .  However, this becomes an issue if we want to fit more complex models where we need to keep this as Vector{Real} .
As far as my understanding goes, the problem arises from ReverseDiff incorrectly tracking these inputs when it shouldn't, and consequently the wrong method for increment_deriv!() being called.
Feel free to move this issue to ReverseDiff if you think this is more ReverseDiff package specific.
Many thanks for your help!

Hello! This is an upstream bug, I'll report it there for you.


Simp should accept abstractions as theorems

example : ¬ true = true := by simp [(¬ ·)]  -- invalid 'simp', proposition expected

For generic operators, this also depends on #387

We might also want to lift the "parentheses around cdot" restriction for simp etc.


Update oss/enterprise versions to 'release-*' tags.

Update calico/enterprise versions
Update generated versions files

I'm sorry but I failed delete the branch after merging the pull request.


e2e tests: perform checkout

Add a checkout flow using asm customer emulation.

PR #4587

For local smoke test, use: yarn e2e:cy:cli --spec cypress/integration/smoke/asm.e2e-spec.ts
For pipeline assessment, see latest run:
https://jkmaster.test.c3po.b2c.ydev.hybris.com/job/spartacus/job/feature%252FGH-4527/
To find the result, search the console output for: Running: smoke/asm.e2e-spec.ts...

merged in GH-4589


Fix typo on EthereumAddressV2Field

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
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 93.566%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
8144

Relevant Lines:
8704

💛  - Coveralls


[Bug]  Getting Error on Create / Edit User

Bug report
What I did
Editing / Creating New User
What I expected to happen
User form Should Open
What happened
Getting Error (strpos(): Argument #1 ($haystack) must be of type string, array given)
What I've already tried to fix it
Checked Controller file & field
Is it a bug in the latest version of Backpack?
Yes
After I run composer update backpack/crud the bug... is it still there?
Yes
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
LARAVEL VERSION:
<IP_ADDRESS>
BACKPACK PACKAGE VERSIONS:
backpack/backupmanager: v4.0.2
backpack/basset: 0.15.0
backpack/crud: v6.x-dev
backpack/editable-columns: 2.1.4
backpack/filemanager: 2.0.1
backpack/generators: v6.x-dev
backpack/logmanager: v4.0.10
backpack/menucrud: v3.0.1
backpack/newscrud: 4.0.9
backpack/pagemanager: 3.0.12
backpack/permissionmanager: 6.0.16
backpack/pro: v6.x-dev
backpack/revise-operation: 1.0.12
backpack/settings: 3.0.16
backpack/theme-coreuiv2: dev-main
backpack/theme-coreuiv4: dev-main
backpack/theme-tabler: dev-main

Please find attached image

As I debug more, I found that error on "role / permission" field as that field name is ['roles', 'permissions'] which is NOT string in column name..

@munjaldevelopment I think it's because you are trying to use an array as the field name.
We removed arrayed names, so for example for the date_range, that previously was: name => [start_date,end_date] it now becomes name => start_date,end_date (a comma separated string).
Can you check if you are not using arrayed field names ?
Cheers

Thanks @pxpm, After change name to role,permission it works for me.
I have checked on permission manager package official file, it show array
https://github.com/Laravel-Backpack/PermissionManager/blob/main/src/app/Http/Controllers/UserCrudController.php

I guess it will be resolved on next composer update.
Anyway, Thanks for the help @pxpm  it's sorted now.

Also there is the v6 branch for permission manager: https://github.com/Laravel-Backpack/PermissionManager/pull/326 that has that change already.
To get it you probably need to add to your composer: "minimum-stability": "dev",
Cheers


SMS Alert Addon

Hello! It's a really nice app you have made. Can you please guide me how can i add an sms alert plugin so that whenever a user orders, he and the admin gets an sms alert of the order? I'd be glad if it works out.

A good place to start for now, is the 'cod' extension, you can look at the file structure and use that to start off a new extension.

Hi, can i add this code to my wordpress project is it possible?

Yep, it is opensource so u can use it
On 28 Apr 2017 4:55 p.m., "pradeep1995"<EMAIL_ADDRESS>wrote:

Hi, can i add this code to my wordpress project is it possible?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tastyigniter/TastyIgniter/issues/148#issuecomment-297971857,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWg7tlJVQb-q4KOuMOE-fMSJSheIsD15ks5r0ck8gaJpZM4K3Lz4
.


signed go compiler on macOS leads to errors

on macOS, when a go binary is SIP protected we patch it then it leads to the following error:
n/usr/local/go/src/unicode/utf8)
../../../go/pkg/mod/github.com/gin-gonic/gin@v1.9.0/internal/bytesconv/bytesconv.go:8:2: package unsafe is not in GOROOT (/var/folders/2h/fn_s1t8n0cqfc9x71yq845m40000gn/T/mirrord-bin/usr/local/go/src/unsafe)
exit status 1

reproduce:
RUST_LOG=mirrord=trace MIRRORD_PROGRESS_MODE=off /Users/aviramhassan/Code/mirrord/target/universal-apple-darwin/debug/mirrord exec -f mirrord.json dlv -- debug --headless -l <IP_ADDRESS>:14213 main.go

This seems to show few issues we have:

that Go accesses the file using ../ which doesn't work with our current temp dir strip.
We don't see any hook happening on open, it seems we lack opendir hook.
That Go uses cwd to set GOROOT - we need to patch cwd.

Seems that it doesn't use cwd.


Offset skidding value with -start/-end placements

CodeSandbox demo
https://codesandbox.io/s/popper-skidding-issue-iezrs
Steps to reproduce the problem

Open codesandbox demo
Try to comment/uncomment offset variables
Look at the preview

What is the expected behavior?
I expect that the skidding value of the offset will be negative for *-start placements and positive for *-end placements in this case.
What went wrong?
Popper shifts in the same direction with *-start and *-end placements.
Any other comments?
I can define something like this
const offset = ({ placement }) =>
  placement.endsWith("start")
    ? [-arrowPadding, arrowSize]
    : [arrowPadding, arrowSize];

and solve the problem, but maybe this behavior should be in the popper-core?

I'm split on whether this should be something Floating UI handles considering it's as low level as possible. You wouldn't be able to "undo" the logic if we changed it (even if you would almost? never want to do...)

I made an umbrella issue here to get these changes into v1: https://github.com/floating-ui/floating-ui/issues/1538


Add support for using a url to connect to PG

Solves #33

@robconery we are reviewing this today

This has been added to 2.x


6.2.1 fails with mktemp: Invalid argument

With ES_VERSION 6.2.1 docker run fails with:
sh: error setting limit: Operation not permitted
mktemp: Invalid argument
With ES_VERSION 6.1.3 works

@Quentin-M you've been quite active recently so maybe you could help me figure out this one?

@rkoc Hey, could you please provide us the command you are actually running to launch ElasticSearch? Do you use Docker userns remapping by any chance? What's your underlying OS/platform/user?

I have the same issue on both local (Linux 4.13.0-32-generic Ubuntu 17.10) and in k8s cluster (latest stable centos) based on this template with updated version.
Local run command:
docker run --rm -it --privileged quay.io/pires/docker-elasticsearch:6.2.1
mktemp: Invalid argument

According to my understanding of strace, elasticsearch tries to use mktemp -t <template>. However, Alpine includes the BusyBox version of mktemp, which expects
Issue correlates with the following PR: https://github.com/elastic/elasticsearch/pull/27659, introduced in the 6.2.0 release.
Busybox
mktemp --help
BusyBox v1.27.2 (2017-12-12 10:41:50 GMT) multi-call binary.

Usage: mktemp [-dt] [-p DIR] [TEMPLATE]

Create a temporary file with name based on TEMPLATE and print its name.
TEMPLATE must end with XXXXXX (e.g. [/dir/]nameXXXXXX).
Without TEMPLATE, -t tmp.XXXXXX is assumed.

	-d	Make directory, not file
	-q	Fail silently on errors
	-t	Prepend base directory name to TEMPLATE
	-p DIR	Use DIR as a base directory (implies -t)
	-u	Do not create anything; print a name

Base directory is: -p DIR, else $TMPDIR, else /tmp

GNU
Usage: mktemp [OPTION]... [TEMPLATE]
Create a temporary file or directory, safely, and print its name.
TEMPLATE must contain at least 3 consecutive `X's in last component.
If TEMPLATE is not specified, use tmp.XXXXXXXXXX, and --tmpdir is implied.
Files are created u+rw, and directories u+rwx, minus umask restrictions.

  -d, --directory     create a directory, not a file
  -u, --dry-run       do not create anything; merely print a name (unsafe)
  -q, --quiet         suppress diagnostics about file/dir-creation failure
      --suffix=SUFF   append SUFF to TEMPLATE.  SUFF must not contain slash.
                        This option is implied if TEMPLATE does not end in X.
      --tmpdir[=DIR]  interpret TEMPLATE relative to DIR.  If DIR is not
                        specified, use $TMPDIR if set, else /tmp.  With
                        this option, TEMPLATE must not be an absolute name.
                        Unlike with -t, TEMPLATE may contain slashes, but
                        mktemp creates only the final component

  -p DIR              use DIR as a prefix; implies -t [deprecated]
  -t                  interpret TEMPLATE as a single file name component,
                        relative to a directory: $TMPDIR, if set; else the
                        directory specified via -p; else /tmp [deprecated]

      --help     display this help and exit
      --version  output version information and exit

Report mktemp bugs to<EMAIL_ADDRESS>GNU coreutils home page: <http://www.gnu.org/software/coreutils/>
General help using GNU software: <http://www.gnu.org/gethelp/>
Report mktemp translation bugs to <http://translationproject.org/team/>
For complete documentation, run: info coreutils 'mktemp invocation'

Solution is to create the temporary folder ourselves and set the ES_TMPDIR environment variable. I will make a PR in just a few, once I get to the office.

Thanks a ton!

Actual fix is in this MR, I think https://github.com/elastic/elasticsearch/pull/31003

@ademariag the issue you mentioned was closed won't fix, so I suppose folks (like us in zipkin) will have to make a one-off fix like others have.


[1.5.0] Refer to a Unique Update Version Tag for Evaluatory MySQL Deployment

Description:
Currently, the evaluatory MySQL deployment refers to 5.7 stable image tag of official MySQL Docker image tag.
It is ideal to refer to a specific, unique MySQL Docker image tag (e.g. 5.7.31) mapping to an update of MySQL. This provides us the knowledge of the exact MySQL update level up to which product Helm charts have been tested with.
Affected Product Version:
Kubernetes and Helm Resources for WSO2 Open Banking version <IP_ADDRESS> and above

Updating the title as it will be required to maintain a MySQL Helm chart for each PSD2 API specification supported (e.g. UK, Berlin).

Fixed.


added seo from open graph

created pull request for seo branch

added meta tags from the Open Graph protocol for SEO. Also added some og: metadata to things such as the title and content.


⚠ Bofrost.at has degraded performance

In 997c379, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1357 ms

Resolved: Bofrost.at performance has improved in 0847449 after 26 minutes.


Help server restart unreliable when installing packages

When I install a package, the number of help servers will increase after the installation. It looks like the way to restart the process implemented in #863 is not reliable or at least not working consistently as expected.

@ManuelHentschel When I install a package, e.g. install.packages("hms"), restart will be triggered when installation begins and finishes. It seems that this.cp will lose track of existing processes if the help server is triggered too quickly.

Can reproduce and found the (async) issue that causes this. I'll try to write a fix soon.

I guess we should make a release once this issue is fixed. Just imagine a user opens multiple R projects and install many packages.


Homepage webpackbin link is out of date

https://www.webpackbin.com/V1VNoINA- gives an error.

On styled-components.com I mean.

The styled-components boilerplate on webpackbin.com seems broken too 😢  (uses 2.0.0-7)
Uncaught TypeError: _styledComponents2.default.h1 is not a function
works with 2.0.0-6

It's working now with v2.0.0-10 but the URLs in the README needs to be updated.

@MMayla How did you get webpackbin to work with this version? I put it into the config, but then it threw this error: Uncaught TypeError: Super expression must either be null or a function, not undefined

Fixing now, sorry for the delay!

 I did just update to later version of webpack, which might be reason. But I am in loss of time due to work and family. Holidays coming up though, so will go through current issues.
Would be great if you could try to delete cookies though, just to see if that helps. That would confirm that it is the sandbox itself and not the bundles at least.
Sorry about it, but yeah... it is just very hard to test these changes.
It is working on my end btw. Though not sure if it is the bundle or the sandbox. A deletion of cookies will verify that :)

I've had the same problem and it's working for me after deleting cookies.

Damn, so it's the sandbox. Can we hotfix that from our side somehow so people don't get a horrible first experience of styled-components?

It is rather hard to track down why. The cookies expire rather quickly, it
might be related to that. Away with family this weekend, but I will find
some time later. Now we know it is related to the sandbox and likely the
expiration of your cookie... as it works fine with a fresh cookie :-)
On Sat, Apr 1, 2017, 12:16 Max Stoiber<EMAIL_ADDRESS>wrote:

Damn, so it's the sandbox. Can we hotfix that from our side somehow so
people don't get a horrible first experience of styled-components?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/580#issuecomment-290911029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADxgwYP-R_D-a-k5VSX_VGyIgqXJSUycks5rriP7gaJpZM4Mb_pX
.

Okay, I believe the issue is fixed now. It was related to the latest fix where it made it possible to import some-lib/whatever/index.js as some-lib/whatever... this is normal behaviour in Webpack, but due to using DLL bundles something awful happened there.
I kept the scope of this fix within the package itself, not its dependencies (which you would never require this way anyways), fixing the issue and keeping the functionality.
The reason this was not discovered (cause I always go through all boilerplates) is that I did not notice that the build failed on the EU instance on Heroku, so everything worked fine as I am using the instance.
Really sorry about this, I need to figure out a way to automate this testing :)

Everything works again! :tada:
Thank you so much for digging in @christianalfoni, much much appreciated :heart: Enjoy the time with your family!

@mxstbr They are not working with me.
I have this error with this:
Uncaught TypeError: Super expression must either be null or a function, not undefined

and this error with this:
Uncaught TypeError: _styledComponents2.default.input is not a function

Can confirm that the second one isn't working for me as well. Looks like updating the styled-components version will fix it.

@MMayla @k15a Hi guys... this seem very strange. Both of them are working fine on my end. The bundling of the DLL with the Bin happens the same way for everyone and there is no cache on that. So the first bin should instantly have worked for everyone. Could you please confirm that there is still an issue?
About the second error that seems related to a previous issue where a DLL bundling bug was introduced. Webpackbin is extremely vulnerable to these bugs due to its aggressive caching. But this has been resolved, but your browser might still have cached the DLL. Would be great if you could verify the cache is also cleared, or just update config to later version as that will produce a new DLL bundle  :)
I have to dig deeper if there is still an issue here, really appreciate you reporting and giving examples here!

Both are working for me in chromes incognito today so it should be related to something cached.

@k15a Thanks for confirming @k15a! :)

Working for me after cleaning cache. Thanks guys :)


AutoRest: Explore JDK 8 baseline

Lets assume that at some point in the future AutoRest will be generating JDK 8 baselined code. We should identify points in the generated output where we can offer a better developer experience. This issue should track the identification of possible areas of improvements, and then link to new issues created to improve both of these.
Areas identified so far:

Move to the new date / time APIs
Use the new java.util.function functional interfaces
Consider use of Optional
Consider use of Stream
Consider use of default / static methods on interfaces

@JonathanGiles please split this into smaller task in https://github.com/Azure/autorest.java, and link them here


discord-canary: 0.0.129 -> 0.0.130

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg eval

Result of nixpkgs-review pr 137879 run on x86_64-linux 1

1 package built:

discord-canary


When switching list data sources, there is a display problem

I created a git repository to reproduce this issue
https://github.com/issuebox/vue-virtual-drag-list-issue

The default status display is normal
Then click button1,  display normal, it show 2 items;
Then click button2,  I want to show 5 items, but it show 4items, ant the first item's place is blank.
Then click button3, same problem
Then click button1,  Then click button2 ...., Totally messed up

Apart from this problem, I think the vue3-virtual-drag-list  is great and I like it very much and thank you for providing such a great vue plugin.

@vaseala Thank you for your approval and use, I will review and fix this problem as soon as possible.

@vaseala Sorry for the late reply. Please update to the lasted version to solve the problem.

@vaseala Sorry for the late reply. Please update to the lasted version to solve the problem.

Just tested it with version 3.3.8, it works! Thanks very much!


add wps217 check

Summary

Test Plan

LGTM, can you link here what you used for reference?

Yes, sure
Violation description
Test cases in WPS project path:
tests/test_visitors/test_ast/test_complexity/test_function/test_awaits_count.py
Await counter logic in WPS project path(class _ComplexityCounter):
wemake_python_styleguide/visitors/ast/complexity/function.py


Bad shading in cube example

Thank you for providing rend3! I'm considering using it for a new non-game project where I want to combine my own custom graphics with standard models and nice looking shading, and it seems like rend3 perfectly fits my scope. However, I get a problem with the shading already in the simple cube example, running cargo run --bin cube (same problem in release mode). The problem is a bad and strange shading on the sides of the cube.

Here are my specs:
rend3 trunk pulled from github 2023-04-08 (release v0.3.0)
rust and cargo version 1.68.2
Windows 11 Home 10.0.22621
GeForce GTX 1650 (Display memory 3950 MB, Total Memory 12064 MB) Driver ver <IP_ADDRESS>41, 2023-03-16
Core i5-12400F, 16 GB RAM

I can confirm this happens to me also on Arch Linux using rustc/cargo 1.71.0-nightly on an integrated graphics card from an Intel Core i7-7500U


Drop compatibility for PHP 5

That is indeed a mistake. Thanks for reporting!
Addressed in https://github.com/apereo/phpCAS/pull/391.


Help

Challenge http://www.freecodecamp.com/challenges/waypoint-target-the-parent-of-an-element-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
I believe I have this correct.  Am I doing something incorrect in this code?
$("#left-well").parent().css("background-color", "red");
Your left-well element should have a red background.
There is a Large red X next to this section.

@MrAndrewPeterson thanks for posting this issue!
You can't pass the test because you are using an example from the description of the challenge and not the correct code. See here for more information. Also there is a merged PR https://github.com/FreeCodeCamp/FreeCodeCamp/pull/3050 which clarifies this situation. But in fact this type of issues are opened because campers don't actually read instructions entirely or they are not attentive.

Please review the Guidelines for Contributing, thank you!.


Native module cannot be null

Hi,
After I run rnpm install react-native-in-app-utils I got this error.

Log file:
: Native module cannot be null.
: Unhandled JS Exception: Native module cannot be null.
: Requiring module "191", which threw an exception.
: Unhandled JS Exception: Requiring module "191", which threw an exception.
: Module AppRegistry is not a registered callable module.
: Unhandled JS Exception: Module AppRegistry is not a registered callable module.
Any advice ?

Which version of react-native are you on?

React Native: 0.32
Xcode: 8.1

i haven't tried rnpm integration. See if it works when linking it manually.

Where a can see how to do the  the manually integration ?
Thanks

I had this problem but it went away after running Clean in XCode.

I am facing this issue in react native version 0.57.0


Updated Langs with English Placeholders

-Added English Placeholders to all lang files for translation

-Made all our custom blocks use getDefaultState instead of getBaseState
-The hope was this would add MoreWaterlogging compat, but it doesn't seem to
-Change still seems worthwhile as it should hopefully fix other errors we might get

-Whip sounds now always play as long as the whip was fully charged
-Whip sounds now work on server


Update whats-new-in-preview.md

Removed the broken link as the original document - https://docs.microsoft.com/Exchange/mail-flow-best-practices/mail-flow-insights/mfi-email-issues-for-priority-accounts has been modified.

@JohanFreelancer9 Please copy review.

@adefowler I have removed the link via the PR as the original link has been modified with new steps which do not contain details about email issues on priority account.

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3028

@adefowler Please merge this PR. Thanks.


Module not found: Error: Can't resolve 'react/lib/checkPropTypes' with react-native 0.47+

I am trying to upgrade to RN 0.47.2 and now I am facing this error when starting storybook (all my package are to latest version 3.2+
    "@storybook/addon-actions": "^3.2.6",
    "@storybook/addon-links": "^3.2.6",
    "@storybook/addon-storyshots": "^3.2.8",
    "@storybook/cli": "^3.2.9",
    "@storybook/react-native": "^3.2.8",
...
    "react": "16.0.0-alpha.12",
    "react-native": "0.47.2",

ERROR in ./node_modules/react-dom/lib/checkReactTypeSpec.js
Module not found: Error: Can't resolve 'react/lib/checkPropTypes' in '~/node_modules/react-dom/lib'
 @ ./node_modules/react-dom/lib/checkReactTypeSpec.js 13:21-56
 @ ./node_modules/react-dom/lib/ReactFiberContext.js
 @ ./node_modules/react-dom/lib/ReactFiberReconciler.js
 @ ./node_modules/react-dom/lib/ReactDOMFiber.js
 @ ./node_modules/react-dom/index.js
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS> @ multi ./storybook/addons.js<EMAIL_ADDRESS>

Did you try deleting node_modules and fresh install? Does your app work independent of storybook?

Will have a look later and will reopen if I still have the issue.


Cherry-pick abea229 from master to set-namespace/v0.3

@sdowell It seems there is an inconsistency between what the verify-docs expects and what we really want: https://github.com/GoogleContainerTools/kpt-functions-catalog/runs/6014038143?check_suite_focus=true

I'm going to merge this PR. We don't have to block this PR.


PublicSuffix::DomainNotAllowed when parse third-level domain

When I try to parse domain from data/list.txt I have error.
PublicSuffix.parse("vic.gov.au").domain

`vic.gov.au` is not allowed according to Registry policy (PublicSuffix::DomainNotAllowed)

I think this is misbehavior in PublicSuffix::Rule::Normal#decompose due regexp not matches three level domains
Tested on 6.0.1 version of gem

This is expected, because the name is in the list.
https://github.com/weppos/publicsuffix-ruby/blob/5297f28b40068510a2b4667d8dbd1e544a7ad03e/data/list.txt#L272


Implement all WWT settings

There are a number of WWT settings, most of them boolean or related to colors:
https://worldwidetelescope.gitbooks.io/worldwide-telescope-web-control-script-reference/content/webcontrolobjects.html#polyline-addpoint-method
At the moment the code just includes an example of how to implement showConstellationFigures in core.py
constellation_figures = Bool(False, help='Whether to show the constellations').tag(wwt='showConstellationFigures', sync=True)

Adding a setting just means adding a line here. For string settings we should use the Unicode traitlet class. We should use PEP8-friendly names for the Python side, and the wwt name indicates the WWT setting name.

Closing in favour of #39 which is more explicit about what needs to be done


Anyway to hook up platform detection to Android Studio's "Toggle Platform Mode"

Android Studio has a button in the Flutter Inspector to toggle the platform between Android and iOS in the same emulator. Just seems to trigger a page rebuild which changes the result of Theme.of(context).platform between TargetPlatform.android and TargetPlatform.iOS.
It seems like your platform.dart triggers off a lower level check against sky_engine/lib/io/platform.dart's Platform. Between isAndroid and isIOS.
I know you have nice methods changeToMaterialPlatform and changeToCupertinoPlatform, but is there any way to tie the auto detection into the Theme's platform so that when I toggled the platform in Android Studio it also toggled the widgets provided by this package?
Thanks.

My PR #76 fixes this.

The changes to PlatformProvider should allow for this now


[AMBARI-24681] Cannot deploy cluster without HDFS_CLIENT

What changes were proposed in this pull request?
Prior to AMBARI-24453 saving hadoop-env.sh and related logic was executed if the cluster had any NameNodes.  This change adds back the has_namenode condition to consider the cluster to have HDFS if it has any NameNodes (to preserve old behavior) or any HDFS Clients (to preserve the change from AMBARI-24453).
This fixes AMBARI-24681.
How was this patch tested?
Tested the following scenarios:

deploy cluster without HDFS_CLIENT via blueprint
add new host to host group without HDFS_CLIENT
add new host to host group with HDFS_CLIENT

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/4046/
Test PASSed.

@g-boros please review


rest api to display db schema

hint: use https://github.com/tjwebb/pg-json-schema-export

See https://github.com/FredericHeem/starhackit/pull/140


[GLUTEN-1632][CH]Daily Update Clickhouse Version (20231103)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

Gluten Perf Test Pass, GlutenWithCHStandard tpch-data-sf100 total time 137860

no siginicant performance chagne


After updating packages swagger not generating all routes

Please update your repository, since i updating packages to LTS swagger not more generating all routes in json

@azeemgujjar I have upgraded all the dependencies, and it is working fine. can you check again?


Spanish Translation

What problem does this feature solve?
Hello, I would like to collaborate with the Spanish translation, is it done?
What does the proposed API look like?
I would like to collaborate with the Spanish translation, is it done?

There's an WIP translation effort here. I don't know if it's active or not, but I'd suggest to get in touch. Anyway, the correct repo for discussing documentation, including translations, is vuejs/vuejs.org.

hi i want contribuite to spanish translation of the documentation, how i do this


Frequency, invalid edit (Chirp)

I apologize for the question which is perhaps trivial but I didn't understand what the problem is, which probably comes from Chirp.
It seems that using Chirp it is not possible to memorize the frequencies ranging, approximately (the range could be greater), from 77.00 to 79.00
In chirp I checked the box: Setting: Driver information: Limit disabled for modified firmware; but the window appears saying: Invalid edit: frequency [….] is of out of supported range….
Can this be resolved somehow?
Many thanks

It looks like there is already work being done on adding an appropriate memory map to Chirp
https://github.com/egzumer/uv-k5-firmware-custom/discussions/183
This might resolve any issues.


Theorem: distinct points + T2 implies not hyperconnected

Adding new theorem: distinct points + T2 implies not hyperconnected.
And deleting three traits files as they can be deduced from the theorem, and the deduction is more informative than the previous assertions:

https://topology.pi-base.org/spaces/S000067/properties/P000039
https://topology.pi-base.org/spaces/S000090/properties/P000039
https://topology.pi-base.org/spaces/S000122/properties/P000039

Note: https://topology.pi-base.org/spaces/S000052/properties/P000039 can also be deduced.  Should the trait be removed, or should we keep it?

I'll go ahead and approve this and I have no strong opinions about keeping P39 for S52 so I'll request @StevenClontz input on that. This is something I've been wondering in general; do we have a stated preference over keeping some properties for spaces despite the ability to leave them as simply deduced? Perhaps this depends on how informative the demonstration is compared to the deduction using established theorems.

Yeah, I definitely agree that I prefer to see automatic deductions rather than "Asserted in Counterexamples" entries. But if there is a more unique reference, I'd keep the redundancy.
Eventually we'll implement https://github.com/pi-base/viewer/issues/73 to easily confirm when a space/property pair is redundant with other properties/theorems.


How to get the app version by Lookup API for the app available only to specific businesses

As the Title, I had an app which is available only to specific businesses or organizations, how can we get the app version on the App store by the Lookup API for the APP?
I used the link for trying: (https://itunes.apple.com/lookup?bundleId=<my app bundle id>), but I got the below response:
{
 "resultCount":0,
 "results": []
}

Any suggestion?

Duplicate of https://github.com/apple/app-store-server-library-java/issues/38


Installation step 2: not a valid identifierline 89: export: `sha1

Hi Team,
Following Step 2: Getting the esp-idf repository from github of the installation process on Windows 7 x64,  I got the following two messages regarding sha1 (at the end of the full log below):
$ git clone --recursive https://github.com/espressif/esp-idf.git
Cloning into 'esp-idf'...
remote: Counting objects: 3162, done.
remote: Total 3162 (delta 0), reused 0 (delta 0), pack-reused 3162
Receiving objects: 100% (3162/3162), 5.05 MiB | 1.03 MiB/s, done.
Resolving deltas: 100% (1695/1695), done.
Checking connectivity... done.
Submodule 'components/esp32/lib' (https://github.com/espressif/esp32-wifi-lib.git) registered for path 'components/esp32/lib'
Submodule 'components/esptool_py/esptool' (https://github.com/themadinventor/esptool.git) registered for path 'components/esptool_py/esptool'
Cloning into '/esp-idf/components/esp32/lib'...
Cloning into '/esp-idf/components/esptool_py/esptool'...
': not a valid identifierline 89: export: `sha1
': not a valid identifierline 89: export: `displaypath
Submodule path '': checked out '1303c92c1056b7f59b95360b58e70a21cb4a93e1'
': not a valid identifierline 89: export: `sha1
': not a valid identifierline 89: export: `displaypath
Submodule path '': checked out '7c84dd433512bac80e4c01c569e42b4fe76646a7'

I have tried this step twice with the same result.
The /esp-idf/components/esptool_py/esptool directory contains some files and sub directories.
I did not find any leads to this error on https://github.com/themadinventor/esptool repository.
Should I be concerned?

Hi @krzychb,
Until u got solution from esp32 team,try cloning git by desktop git app.I had some issue to but with desktop git app it worked.

Hi @krzychb,
Until u got solution from esp32 team,try cloning git by desktop git app.I had some issue too but with desktop git app it worked.

Seen this message on colleague's windows computer as well. It looked like everything was actually checked out correctly.
Here's a similar error mentioned in msys2 tracker: https://github.com/Alexpux/MSYS2-packages/issues/30. My guess that that's something with msys2 git, we'll check it...

Hi @krzychb,
Quick question, what directory were you in when you ran git clone? (ie what was the output of the pwd command?) Anything special about that drive (network mapped drive, removable drive, etc.)?
Also, what is the output of the command which git?
Thanks,
Angus

(Deleted previous comment because I can reproduce this without any special directories, etc.)
I can confirm @igrr's comment that despite this error everything seems to work fine and the git submodule checkout is 100% valid. So it's nothing you have to worry about for now, provided esp-idf works as expected.
I did notice this path is directly in the msys "root":
Cloning into '/esp-idf/components/esp32/lib'...

Did you mean to run the git checkout from the directory /? (this corresponds to c:\msys32 in Windows). It's OK if you did, just wanted to be sure this isn't unexpected behaviour.

@hardikharpal, @igrr, @projectgus - thank you guys for really quick replies and support.
@projectgus - indeed I did git checkout intentionally from '/'.
From deciding to set up the esp-idf to getting esp-idf-template compiled, took me maybe 45 minutes.  To get to this point with ESP8266 1.5 years ago has not been so easy for me and I was not sure what to expect now from ESP32 framework.  ESP32 Team made it it really accessible and easy to follow.
Congratulations :smile: :+1:

Thanks for the kind words, that's exactly the kind of result we are all aiming for!
I've added a note in our Windows documentation about the weird submodule messages, with a link to this issue. There may eventually be a solution, but at least it's not breaking any functionality.


Update create-retention-policies.md

When reviewing this as a mentoring opportunity, quickly realized that the Compliance center has been updated to include these options below Information Governance (and the retention policies will only be available under policies after creation). Hoping that you agree these changes help others along the way when configuring (and learning) how to get started with retention policies. Thanks in advance! CG

#sign-off   Yes, agree!


CB-18521 enforce default read timeout in rest client util to be 1 minutes instead of infinity

Retest this please!


feat(ls): first implementation of ls command

It acts much like a cat except that it returns json data containing object references and some information about them (like type and size).

:+1:


join feature for * zero_or_more

First of all, this project is great. I was working on my own parser generator and it turns out I was trying to implement PegJS.
I see a lot of head/tail conventions in programming language grammars, like examples/javascript.pegjs. I think there are more than a dozen of these cases in javascript.pegjs.
    head:AssignmentExpression tail:(__ "," __ Elision? __ AssignmentExpression)* {
      var result = [head];
      for (var i = 0; i < tail.length; i++) {
        result.push(tail[i][5]);
      }
    }

How about this instead?
    assignments:(AssignmentExpression)*{__ "," __ Elision?; 1, } {
      var result = assignments
    }

The proposed grammar is:
expression:primary star ("{" join:primary? (";" min:integer? ("," max:integer? )? )? "}")?

This would make the pegjs file easier to comprehend, IMO.
See my untested implementation here: https://github.com/jaekwon/pegjs/commit/4a979356546ee352d334df3d2dc483f69261817a
BTW, I had to make an edit to allow labels in optional nodes. That could be a separate issue.

Now it's tested and working. https://github.com/jaekwon/pegjs/tree/starjoin


libfprint-2-tod1-broadcom: init at <IP_ADDRESS>

Description of changes
This adds another driver for libfprint-2-tod1, which is supposed to be used as Touch OEM Drivers (TOD) package in the NixOS module services.fprintd.tod.driver. This enables fingerprint support for the Dell Latitude 7440 and some other notebook models.
I managed to get the driver running by supplying the needed statically linked libraries, but hit a road block when fprintd tries to load the driver's firmware:
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/etc/systemd/system/fprintd.service; linked; preset: enabled)
    Drop-In: /nix/store/if17mdl7z0j9q27m36z6b0gh4jiipvp2-system-units/fprintd.service.d
             └─overrides.conf
     Active: inactive (dead)
       Docs: man:fprintd(1)

Aug 01 07:49:28 nixos systemd[1]: Starting Fingerprint Authentication Daemon...
Aug 01 07:49:28 nixos fprintd[160929]: In cvif_IsUshThere(), cv_get_ush_ver() status: (0x0)
Aug 01 07:49:28 nixos fprintd[160929]: Control Vault getting chip type
Aug 01 07:49:28 nixos fprintd[160929]: Citadel A0 CID7 Chip Found....
 Check Firmware Files or CID used or Hardware etc. Error: 0x1c
Aug 01 07:49:28 nixos fprintd[160929]: Ignoring device due to initialization error: An unspecified error occurred!
Aug 01 07:49:28 nixos systemd[1]: Started Fingerprint Authentication Daemon.
Aug 01 07:50:15 nixos systemd[1]: fprintd.service: Deactivated successfully.

When the package is built, the firmware files are copied to the correct location, but it seems like fprintd cannot find them. Any help would be greatly appreciated!

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/need-some-help-getting-a-new-driver-working-for-fprintd/31157/1

@abbradar Could you provide some insight? I'm only asking since you are listed as the maintainer of libfprint


Does not support Steam code

Steam code that is supported in Yubico Authenticator desktop app won't work in the iOS app and displayed as six digits code.

This looks like an old version of the Authenticator application. Can you reproduce the error in the latest version?

This looks like an old version of the Authenticator application. Can you reproduce the error in the latest version?

The latest version of Yubico Authenticator desktop supported Steam code:

but the iOS version (latest from App Store) not:

Here is the discussion thread of the Steam code for Yubico Authenticator desktop: https://github.com/Yubico/yubioath-desktop/issues/72, probably bly also this thread: https://github.com/Yubico/yubioath-desktop/issues/703

Thanks for the rapid reply! I can't reproduce the bug. Maybe you've got some special character in your account name? Could you provide a step-by-step instruction on how to create an account that returns a non functioning steam code?

Thanks for the rapid reply! I can't reproduce the bug. Maybe you've got some special character in your account name? Could you provide a step-by-step instruction on how to create an account that returns a non functioning steam code?

Steps to reproduce:

Open Yubico Authenticator desktop, add account
Issuer: Steam; Account name: my account name; Secret key: secret key
Click add
Find the Steam account that just added, touch YubiKey
Observe that Yubico Authenticator desktop generates a correct Steam code
Open Yubico Authenticator iOS, pull down to initiate NFC
Observe that Yubico Authenticator iOS generates a TOTP code (6 digits) instead of Steam code

Thanks! I got it figured out. It only happens to accounts that requires touch and if you at the same time enable the "Bypass touch requirement" in the NFC Settings in the iOS app. We will fix this in the next release. While waiting for the release you could either add the Steam account without enabling the touch requirement or turn off the "Bypass touch requirement" setting in the app.


Fix mixed use of tabs and spaces

This generates an error in Godot 3.2.

@quendera It no longer generates an error in Godot 3.2, but it should still be a pretty simple cleanup to merge.


Add support for different font sizes

Adds support to change font size of texts.
Mapping of fontsizes supported by Tailwind to the selection available in the menu:
text-base -> Tiny
text-lg -> Small
text-xl" selected>Medium
text-2xl -> Large
text-3xl -> X-Large

Wonderful! Thank you for making this PR.


What is the purpose of these lines of code?

https://github.com/clovaai/EXTD_Pytorch/blob/e99af10f282d07054c1cf7c4b8c035084daaff78/mobileFacenet_64_PReLU.py#L190-L201
Hello, this conditional statement seems like making no sense. I am not sure that whether the author set it like this deliberately, or there is something wrong with these lines of code.

Ohh Thank you for the comment.
'If cnt >1 else ' statement is useless as you pointed out (same operations work).
We will revise this in the next upcoming large update.

thank you for your reply, I got it.


Not working with two containers in same pod

Not working with two containers in same pod.
I'm using docker for mac with kubernetes and i'm trying to work with ksync in local, because of performance of docker-for-mac with hostpath.
As explained in https://kubernetes.io/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume/ to communicate between to containers in same pod we have to use a volume with emtpyDir.
But when i'm trying to use it with ksync it doesnt works. Seems that it's working, but when i'm going to the directory inside the containers it continues empty. But if i go to one container and touch a file , i see it in the two containers.
Thank you.

@raulpuente ksync doesn't interact with volumes managed by Kubernetes directly (as in this case). It only values managed by Docker.

Thank you for the information tim.


Add API docs

we should include both querying by name to get the addressed and querying an address to see the associated name


Support SyncWAL

PTAL @zhangjinpeng1987  @BusyJay

 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.

What's the difference?

@BusyJay In our case, there is no difference. - -||


Problem releasing a previous websocket connection

I have found a bug in the WebSocket class.
The while loop doesn't stops until the it reaches the timeout event if the object has been released.
I have added this code after the if block:
                guard let _ = self else {
                    return
                }

This is how it looks like now the code:
 var out = timeout// wait X seconds before giving up
        FoundationStream.sharedWorkQueue.async { [weak self] in
            while !outStream.hasSpaceAvailable {
                usleep(1000) // wait until the socket is ready
                out -= 1000
                if out < 0 {
                    guard let s = self else {
                        return
                    }

                    let errCode = InternalErrorCode.writeTimeoutError.rawValue
                    completion(s.errorWithDetail("write wait timed out", code: errCode))
                    return
                } else if let error = outStream.streamError {
                    completion(error)
                    return // disconnectStream will be called.
                }

                guard let _ = self else {
                    return
                }
            }
            completion(nil) //success!
        }

Could you please add this change to the repo?
Best regards

Looks like this was fixed already: https://github.com/daltoniam/Starscream/commit/146368c71a00369d0a33bdc9713cd4666af48d23#diff-b298b191dc47bb2b59aedeaf62adb9d5R224
I think you just need to update your version of Starscream


Error at line 205 in selfbot.py

DeprecationWarning: There is no current event loop
loop = asyncio.get_event_loop()
Traceback (most recent call last):
File "C:\Users\*****\Desktop\Discord-SelfBot\selfbot.py", line 205, in
Astraa = discord.Client()
^^^^^^^^^^^^^^^^
TypeError: Client.init() missing 1 required keyword-only argument: 'intents'
Please fix

I am gonna try to look into it and try to fix it until I get more help

Fixed issue!
Replaced
#Initialization of the Bot parameters
Astraa = discord.Client()
Astraa = commands.Bot(description='ATIO Tool - SelfBot created by Astraa', command_prefix=prefix, self_bot=True)

with
#Initialization of the Bot parameters
intents = discord.Intents().all()
Astraa = discord.Client(intents=intents)
Astraa = commands.Bot(description='ATIO Tool - SelfBot created by Astraa', command_prefix=prefix, self_bot=True, intents=intents)

from line 204 in selfbot.py

Will close when fix does get added


Create a test case that declares an ORM persistent unit and a Reactive one

This use case is supported right now but we don't have a test for it.
Something not too complicated: an entity and a couple of unit tests persisting and reading it using JPA/Hibernate and Reactive persistence unit declared in the same persistence.xml.
In OGM we use a rule to isolate among different persistence.xml for tests, it might be helpful for us as well: https://github.com/hibernate/hibernate-ogm/blob/master/core/src/test/java/org/hibernate/ogm/test/jpa/JPAStandaloneNoOGMTest.java
We should test it for Mutiny and CompletionStage.
@blafond This could be a good first issue for you to get accustomed to the project and the way we work

Done!
Thanks


{keyvault}Add test for keyvault key get-policy-template

Description

Add test for keyvault key get-policy-template, below test will be affected:
test_keyvault_softdelete
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

keyvault


Retrofit Demo App

In this app we can show that how to use Retrofit for calling API and get data from API.

Hey @akshatbhuhagal one folk already sent PR on same issue, and not confirmed anything yet, so after confirmation, will assign this to you;
If you want to contribute, you can try here
send PR directly.


Configure test library

Description
Create the settings to have test on our application, have same discussion with pattern
Tasks

[ ] Install jest configs
[ ] Install testing-library
[ ] Set a file-structure pattern for the tests

The configuration was completed. The branch is updated with all the changes needed for the tests to be executed.
I made a change, not related to this issue, but to help improve the organization of the package.json. @types libs imported in the project aren't used when the application is built, so I moved them to devDependencies as they are only used in the dev environment.
I also needed to update the yarn.lock file because of these changes and the libs that were installed.


How to compile?

Sorry if that is obvious, but how do I compile a jar? My java knowledge is rusty, I'm used to javac and ant.

You should be able to build it using maven (you will need a version of maven installed on your system). I would strongly advise you to download either eclipse or netbeans though... import the pom... and just run it from the ide.
But if you just want to build it, run mvn compile.

Thank you for your quick help! I got it working with macports mvn and Netbeans!

Perfect... glad to hear it.


Usage is outdated

Usage doesn't apply to release 1.0.0

You're right. I forgot to update the README.md. A patch for 1.0.1 is in the works


Capability statement missing support for Patient $Everything

Describe the bug
Patient/$everything is now supported on cosmos DB but the capability statement doesn't state that it is supported.
FHIR Version?
Stu3/R4/R5
Data provider?
CosmosDB
To Reproduce
Steps to reproduce the behavior:

GET {FHIR SERVER URL}/metadata
Look at CapabilityStatement.rest.operation and patient-everything should be listed

Expected behavior
Capability Statement lists patient-everything as supported
Actual behavior
Patient-everything isn't listed

AB#82601


Fix html output of Webpacker::React::Component#render

Currently, calling the view helper multiple times will nest HTML output. The render method currently returns a self-closing div (
) element.  This PR changes the returned HTML to a div with an opening and closing tag (

).
view_component.html.erb
<%= react_component('Hello', key: '1', name: 'a component rendered from a view') %>
<%= react_component('Hello', key: '2', name: 'a component rendered from a view') %>
<%= react_component('Hello', key: '3', name: 'a component rendered from a view') %>

Before
Resulting HTML before call to React.DOM.render:
view_component.html

After
Resulting HTML before call to React.DOM.render:
view_component.html

This changes uses contet_tag instead of tag to generate HTML, similar to react-rails ComponentMount#react_component.
I'm using Chrome.  Maybe other browsers render self-closing tags appropriately, but hopefully this change does not affect support for other browsers.
Fixes #8

Thanks for your PR!
I merged #5 today that fixed the same bug. I just committed your test (and a new integration one) to ensure we correctly render 2 consecutive components.

Ah, I didn't realize it was already in the works.  Thanks for checking it out!


Error When Running Stable-Diffusion Example

I encountered an error while attempting to run the stable-diffusion example as instructed in the README.md. The specific command used was:
cargo run --example stable-diffusion --release --features=cuda,cudnn     -- --prompt "a cosmonaut on a horse (hd, realistic, high-def)" --cpu
The execution resulted in the following error:
Error: MatMulUnexpectedStriding { lhs_l: Layout { shape: [1, 1, 4096, 4096], stride: [16777216, 16777216, 4096, 1], start_offset: 0 }, rhs_l: Layout { shape: [1, 1, 4096, 512], stride: [2097152, 512, 512, 1], start_offset: 0 }, bmnk: (1, 4096, 512, 4096), msg: "non-contiguous rhs" }
After thoroughly reviewing the code and the recent changes, I suspect that the error might be related to the changes introduced in the following PR:(https://github.com/huggingface/candle/pull/1943/commits/c26dd7f54a44275b1a3803a95308bf8b37ed489c). The modifications in this pull request could potentially be causing the non-contiguous memory layout issue indicated by the error message.
I would like to suggest reconsidering the changes made in PR #1943 as a potential solution to this issue.

Thanks for reporting this, I've put a quick fix in #1993 , the longer term fix is to have this properly handled in the matmul but that's a bit more work.

Reverted the temporary fix in favor of a proper fix (that avoids the intermediate copy). It worked fine for me on both cpu and cuda + some tests have been added but let me know if this is still an issue on your side.

Closing as hopefully fixed, feel free to reopen if you run into further issues.


cleanup(rules): cleanup rules disabled by default

Signed-off-by: Melissa Kilby<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Be more consistent with explicitly tagging rules that are disabled by default with enabled: false, should give some perf boosts as well. Spotted 3 rules eligible for cleanup. Are there more rules eligible for cleanup?
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Depends on how end users customizes these rules. It should be communicated that tag enabled: false was added to some rules.

cleanup(rules): cleanup rules disabled by default

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: incertum
Once this PR has been reviewed and has the lgtm label, please assign mstemm for approval by writing /assign @mstemm in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: da90c0dde82e61d46ad7e17ddc45d028daa305e6

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add "Frame load interrupted" error handling for OAuth for RNCWKWebView

Adds the same code that is on RNCUIWebview https://github.com/react-native-community/react-native-webview/blob/master/ios/RNCUIWebView.m#L271 for the same purpose.
I came across this problem while implementing google SAML support with the RNCWKWebView.

Thanks for the PR @oNaiPs ! How would I go about testing this?

Thanks for the PR @oNaiPs ! How would I go about testing this?

@jamonholmgren not sure, I came across this error while developing with google SAML for an internal service.


protobuf lead to RuntimeError

This is my code.
from google.protobuf import descriptor as _descriptor  # protobuf==3.16.0
import ngtpy

ngtpy.create("index", 4, distance_type='Cosine')
index = ngtpy.Index('index')
index.insert([0, 1, 0, 1])

Traceback (most recent call last):
File "_debug_index.py", line 6, in
index.insert([0, 1, 0, 1])
RuntimeError: /work/NGT/release/NGT/lib/NGT/ObjectRepository.h:

Thank you for your brief code reproducing the issue. I have been investigating the issue.

I have released v1.14.3 that fixed this issue.


Error: (SystemJS) module is not defined on angular 4 project (without using angular cli)

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior

After creating an angular quick start project with this template (https://github.com/angular/quickstart), and installing all the npm pckgs as described in the documentation, angular application should start properly. I'm not using the angular CLI, but systemjs.
Actual behavior

I'm getting an Error like this:
Error: (SystemJS) module is not defined
	ReferenceError: module is not defined
	    at eval (http://localhost:3000/node_modules/clarity-angular/clarity-angular.umd.js:5964:31)
	    at Object.eval (http://localhost:3000/node_modules/clarity-angular/clarity-angular.umd.js:6005:2)
	    at Object.eval (http://localhost:3000/app/app.module.js:10:25)
	    at eval (http://localhost:3000/app/app.module.js:32:4)
	    at eval (http://localhost:3000/app/app.module.js:33:3)
	    at eval (<anonymous>)
	Evaluating http://localhost:3000/app/app.module.js
	Evaluating http://localhost:3000/main.js
	Error loading http://localhost:3000/main.js
	    at eval (http://localhost:3000/node_modules/clarity-angular/clarity-angular.umd.js:5964:31)
	    at Object.eval (http://localhost:3000/node_modules/clarity-angular/clarity-angular.umd.js:6005:2)
	    at Object.eval (http://localhost:3000/app/app.module.js:10:25)
	    at eval (http://localhost:3000/app/app.module.js:32:4)
	    at eval (http://localhost:3000/app/app.module.js:33:3)
	    at eval (<anonymous>)
	Evaluating http://localhost:3000/app/app.module.js
	Evaluating http://localhost:3000/main.js
	Error loading http://localhost:3000/main.js

Is basically complaining about this line of code:
WizardPage.decorators = [
        { type: _angular_core.Component, args: [{
                    moduleId: module.id, //source of the error

If I comment out the 5 times that this appears then everything looks fine, what am I missing?
Environment details

Angular version: 4.0.X

Clarity version: Latest

OS and version:  Windows 10

Browser: all

Me too...

Also getting the same error.

Also getting the same issue.

Also getting the same error.

Same happens with the plunker template (and all old plunks)
https://plnkr.co/edit/8TwwdL?p=preview

Some news?

@biapar , @Jinnie , @Thomas772 , @luis-cortina : This appears (at least from the plunkr) to be an issue with pulling in the 0.9.0-alpha.1 release. So if your npm packages are set to pull latest or anything greater than 0.8, I recommend changing your package.json to...

@biapar , @Jinnie , @Thomas772 , @luis-cortina : This should be fixed now with the 0.9.0-alpha.2 publish.
I do recommend not running your production apps off of alpha. But if you need to use alpha to work on the new wizard ( #156 ) then you should be able to do so now.

So, Is't possibile to use NG4?


Open the same sheet component from two different screens

i got specific bug on IOS when using true sheet - i want to open the same sheet from screen (home page) and from another sheet (that also on the home page) so i put my true sheet component to home page and to 'parent' sheet, on Android it works fine but IOS doesn't open any of them and return this - i found only one solutionput my sheet component to the parent screen (home) and when open it from another sheet close 'parent' sheet before open new one, but is there any other solution?
Attempt to present <TrueSheet.TrueSheetViewController: 0x125d9d000> on <UIViewController: 0x106216370> (from <RNSScreen: 0x108b7bc00>) which is already presenting <TrueSheet.TrueSheetViewController: 0x107abb800>.

@Luxlorys can you paste your code here?

// Home.tsx
export const Home = () => {
  <Box>
   <Map />
   <EventsBottomSheet />
  <EventDetailsBottomSheet />
 </Box>

// Map.tsx
export const Map = () => {
 const handleMarkerClick = (marker: MarkerT) => SheetService.open('EVENT_DETAILS_SHEET', 0);
return (
    <MapView
      ref={mapRef}
      showsCompass={false}
      provider={PROVIDER_GOOGLE}
      style={styles.flex1}
      initialCamera={{ center: initialCamera, pitch: 1, heading: 1, zoom: 13 }}>
      {markers.map((marker, index) => (
        <Marker
          key={marker.id}
          marker={marker}
          stopNumber={index + 1}
          onPress={handleMarkerClick}
        />
      ))}
    </MapView>
  );
}

// EventsBottomSheet.tsx
export const EventsBottomSheet = () => {
 const handleEventPress = () => SheetService.open('EVENT_DETAILS_SHEET', 0);

<TrueSheet
      ref={sheet}
      scrollRef={scrollRef}
      dimmed={false}
      cornerRadius={24}
      name={SHEET_NAMES.EVENTS_SHEET}
      sizes={[600]}>
// some code here for scrollview
   <TouchableOpacity onPress={}>
    <EventCard />
   </ TouchableOpacity >

 <EventDetailsBottomSheet />
</ TrueSheet>

Not all code but the logic is that i want to open  from home page by clicking on marker on the map or open that sheet by clicking on event card inside

hmmm looks okay.. Can you create a reproducible example? You can use the example project in this repo -- it's also using maps and child sheets

sorry i can't
the only solution i found is to put all my sheets to root screen (Home) and close parent sheet before open child one, but this solution isn't convenient for me

You need to close the presenting sheet first if it's not the parent of the sheet you're trying to present. That's how IOS works, unfortunately

that's the problem - i try to open new sheet which is child for sheet and it works fine, it opens above parent as i wanted to but at the same time i want to open this sheet (child) from Home screen which is parent for , also i have bottom sheet which i want to open from 3 different bottom sheet and i'm getting the same error
Attempt to present <TrueSheet.TrueSheetViewController: 0x125d9d000> on <UIViewController: 0x106216370> (from <RNSScreen: 0x108b7bc00>) which is already presenting <TrueSheet.TrueSheetViewController: 0x107abb800>.

Right. you can't open other sheet outside the parent. No way around that

i thought if i put this child sheet to Home screen so it becomes independent from parent sheet

oh, do you mean that when i try to open it globally it doesn't understand what sheet to open because that child sheet stay belong Home screen and parent sheet at the same time?

You can only open 1 sheet at a time UNLESS it's a child of a the currently opened sheet. I suggest you take a look at the example project. It has example of children sheets that you can reference.
Closing this.


Features/test anjo

List any issues that this PR fixes: fixes # , etc...

LoserAgent property functions now call appropriate agent functions instead of unit functions for minerals and vespene

This pull request proposes the following changes:

Adds template for 12 Spawning Pool Ravager All-in agent

Known issues/To do:

Implement build order

Looks good, thanks for fixing my bug!


error MT0180: This version of Microsoft.iOS requires the iOS 16.1 SDK (shipped with Xcode 14.1)

Description
I'm having major issues after the latest .Net Maui updates. My iOS app will no longer build.
Here is a link to the initial GitHub issue I created. https://github.com/microsoft/azure-pipelines-tasks/issues/17477
After forcing ASP.net to use 7.0.100 and Xamarin to use xamarin-sdk.sh 17_4_0_301, I'm still getting the error.
I even tried to force XCode to version 14.1 using the CmdLine@2 Task.
- task: CmdLine@2
  displayName: 'Set XCode Version'
  inputs:
    script: |
      sudo xcode-select -s /Applications/Xcode_14.1.app

Does anyone know where this error is coming from? Is this coming from the Maui install? If so, how do I fix this? As-is, I can no longer build my iOS app.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[X] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Current image version: '20221204.1'
Is it regression?
Current image version: '20221204.1'
Expected behavior
I would expect for the app to build.
Actual behavior
The app no longer builds.
Repro steps
Try to build a .Net Maui iOS app targeting iOS 16 with the Microsoft Visual Studio Enterprise 2022 (64-bit) - Current
Version 17.4.3 SDKs using the macos-12 image.

I think the problem lies with the latest version of .Net Maui.
I can see that the Maui install Task is installing this version of microsoft.net.sdk.ios.
Installing workload manifest microsoft.net.sdk.ios version 16.1.1481
This is the version used in my last successful build.
Installing workload manifest microsoft.net.sdk.ios version 16.0.1478

I'm facing the same issue.  Azure Dev Ops pipeline builds are failing that were working earlier this week.

Thank you @faceoffers28 , we will check it, can you provide minimal repro steps?

Hi @igorboskovic3
Since upgrading to latest version of visual studio any maui app launched as iOS we get an error

Launch Visual studio     (Microsoft Visual Studio Enterprise 2022 (64-bit) - Current Version 17.4.3)
Create a Maui App
Pair to a mac  (optional)
Build the app

@gabsamples6 I don't want to ask the obvious question, but you didn't say what XCode version you are using. Did you update to XCode 14.1?
Anyway, this issue is about building on an Azure DevOps hosted agent.

@igorboskovic3 the iOS build with the latest MAUI version doesn't work for us too.
This is how I select the correct XCode version:
  - task: Bash@3
    displayName: Select xcode version
    inputs:
      targetType: 'inline'
      script: |
        sudo xcode-select -s "/Applications/Xcode_14.1.app"

The build works fine, but when the "Optimizing assemblies" stuff starts, I get this warning:
ILLINK : warning MT0079: The recommended Xcode version for Microsoft.iOS 16.1.1481 is Xcode 14.1 or later. The current Xcode version (found in /Applications/Xcode_14.0.1.app/Contents/Developer) is 14.0.1. [/Users/runner/work/1/s/src/MyProj.csproj::TargetFramework=net7.0-ios]
After some time, it fails with this error:
xcodebuild: error: SDK "/Applications/Xcode_14.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk" cannot be located.
xcrun: error: sh -c '/Applications/Xcode_14.1.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode_14.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find dsymutil 2> /dev/null' failed with exit code 16384: (null) (errno=Invalid argument)
xcrun: error: unable to find utility "dsymutil", not a developer tool or in PATH

In the error message it looks like it's using XCode 14.1.

Starting with the version of VIsual Studio before this last release, I noticed that I couldn't select the version of iOS to use once I selected Asp.net 7.
You can see the problem here. It still hasn't been fixed. I assume VS can't determine what version of .Net Maui is installed therefore it can't suggest the correct version of iOS to use. It appears that Microsoft has made the initial release of .Net Maui dependent on iOS 16.0. It also appears that Microsoft has made latest release of .Net Maui dependent on iOS 16.1.

I can manually edit the csproj and set iOS to 16.1, as shown below. When I try to Build, using Visual Studio, I get all kinds of errors.
<TargetFrameworks>net7.0-ios16.1;net7.0-android33.0</TargetFrameworks>
Bottom line, this is really messed up! I'm going to try to work through the 15 errors that were just introduced when I tried to upgrade to  iOS 16.1.

I changed up my Pipeline to try and recreate the last .Net Maui Build that worked. I'm trying to recreate the initial Asp.net 7.0 .Net Maui environment in Azure DevOps.
- task: UseDotNet@2
  displayName: .NET Version
  inputs:
    packageType: 'sdk'
    version: '7.0.100'

- task: CmdLine@2
  displayName: 'Install Maui'
  inputs:
    script: 'dotnet workload install maui --from-rollback-file https://maui.blob.core.windows.net/metadata/rollbacks/7.0.1xx.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json --source https://api.nuget.org/v3/index.json'

Here is the error I'm getting.
==============================================================================
Task : .NET Core
Description : Build, test, package, or publish a dotnet application, or run a custom dotnet command
Version : 2.210.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli
==============================================================================
Info: .NET Core SDK/runtime 2.2 and 3.0 are now End of Life(EOL) and have been removed from all hosted agents. If you're using these SDK/runtimes on hosted agents, kindly upgrade to newer versions which are not EOL, or else use UseDotNet task to install the required version.
/Users/runner/hostedtoolcache/dotnet/dotnet publish /Users/runner/work/1/s/MyAppName.sln -f:net7.0-ios16.0 -c:Debug /p:ArchiveOnBuild=true /p:EnableAssemblyILStripping=false --runtime ios-arm64 --self-contained
MSBuild version 17.4.0+18d5aef85 for .NET
Determining projects to restore...
Restored /Users/runner/work/1/s/MyAppName.csproj (in 30.99 sec).
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): warning : MAUI0000 [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: System.IO.IOException: The process cannot access the file '/Users/runner/work/1/s/obj/Debug/net7.0-ios16.0/ios-arm64/resizetizer/r/Resources/success.png' because it is being used by another process. [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: at Microsoft.Win32.SafeHandles.SafeFileHandle.Init(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Int64& fileLength, UnixFileMode& filePermissions) [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, UnixFileMode openPermissions, Int64& fileLength, UnixFileMode& filePermissions, Func`4 createOpenException) [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: at System.IO.FileSystem.CopyFile(String sourceFullPath, String destFullPath, Boolean overwrite) [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: at Microsoft.Maui.Resizetizer.Resizer.CopyFile(DpiPath dpi, String inputsFile) in D:\a\_work\1\s\src\SingleProject\Resizetizer\src\Resizer.cs:line 51 [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: at Microsoft.Maui.Resizetizer.ResizetizeImages.ProcessImageCopy(ResizeImageInfo img, DpiPath originalScaleDpi, ConcurrentBag`1 resizedImages) in D:\a\_work\1\s\src\SingleProject\Resizetizer\src\ResizetizeImages.cs:line 201 [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: at Microsoft.Maui.Resizetizer.ResizetizeImages.<>c__DisplayClass26_0.<ExecuteAsync>b__0(ResizeImageInfo img) in D:\a\_work\1\s\src\SingleProject\Resizetizer\src\ResizetizeImages.cs:line 72 [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Maui.Resizetizer.Sdk/7.0.49/targets/Microsoft.Maui.Resizetizer.targets(531,9): error MAUI0000: at Microsoft.Maui.Resizetizer.AsyncTaskExtensions.<>c__DisplayClass0_0`1.<ParallelForEach>b__0(TSource s) in D:\a\_work\1\s\src\SingleProject\Resizetizer\src\AsyncTaskExtensions.cs:line 21 [/Users/runner/work/1/s/MyAppName.csproj::TargetFramework=net7.0-ios16.0]
Workload updates are available. Run `dotnet workload list` for more information.
##[error]Error: The process '/Users/runner/hostedtoolcache/dotnet/dotnet' failed with exit code 1
##[warning].NET 5 has some compatibility issues with older Nuget versions(<=5.7), so if you are using an older Nuget version(and not dotnet cli) to restore, then the dotnet cli commands (e.g. dotnet build) which rely on such restored packages might fail. To mitigate such error, you can either: (1) - Use dotnet cli to restore, (2) - Use Nuget version 5.8 to restore, (3) - Use global.json using an older sdk version(<=3) to build
Info: Azure Pipelines hosted agents have been updated and now contain .Net 5.x SDK/Runtime along with the older .Net Core version which are currently lts. Unless you have locked down a SDK version for your project(s), 5.x SDK might be picked up which might have breaking behavior as compared to previous versions. You can learn more about the breaking changes here: https://docs.microsoft.com/en-us/dotnet/core/tools/ and https://docs.microsoft.com/en-us/dotnet/core/compatibility/ . To learn about more such changes and troubleshoot, refer here: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshooting
##[error]Dotnet command failed with non-zero exit code on the following projects : /Users/runner/work/1/s/MyAppName.sln
Finishing: dotnet publish (Debug)

I was finally able to get my iOS app to Build using what I think is the configuration for the first .Net Maui release. This does not fix the current problem, but at least I can Build my app again.
Here is part of the script that I used.
- task: UseDotNet@2
  displayName: .NET Version
  inputs:
    packageType: 'sdk'
    version: '7.0.100'

- task: CmdLine@2
  displayName: 'Install Maui'
  inputs:
    script: 'dotnet workload install maui --from-rollback-file https://maui.blob.core.windows.net/metadata/rollbacks/7.0.1xx.json --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json --source https://api.nuget.org/v3/index.json'

- task: CmdLine@2
  displayName: 'Set Xamarin SDK'
  inputs:
    script: |
      /bin/bash -c "sudo $AGENT_HOMEDIRECTORY/scripts/select-xamarin-sdk.sh 17_4_0_301"

This worked. Thank you! @faceoffers28

I was able to get the latest working with the following:
    - name: Set XCode Version
      if: runner.os == 'macOS'
      shell: bash
      run: |
        sudo xcode-select -s "/Applications/Xcode_14.1.app"
        echo "MD_APPLE_SDK_ROOT=/Applications/Xcode_14.1.app" >> $GITHUB_ENV

The MD_APPLE_SDK_ROOT sets the Xcode path used by Xamarin.  I thought it was supposed to use the result of xcode-select -p, but apparently not.

Thank you @mattjohnsonpint, I can confirm that your solution works also with Azure Pipelines.
I can finally build our iOS app with the latest MAUI version. This is the Azure Pipelines task:
  - task: Bash@3
    displayName: Set XCode Version
    inputs:
      targetType: 'inline'
      script: |
        sudo xcode-select -s "/Applications/Xcode_14.1.app"
        echo "##vso[task.setvariable variable=MD_APPLE_SDK_ROOT;]/Applications/Xcode_14.1.app"

we check the following, in order:

The MD_APPLE_SDK_ROOT environment variable.
What's configured in ~/Library/Preferences/Xamarin/Settings.plist
xcode-select -p

That makes sense.  Just tested and the default currently on the macos-12 GHA runner image is MD_APPLE_SDK_ROOT not set, but both the ~/Library/Preferences/Xamarin/Settings.plist and xcode-select -p showing 14.0.1.
(On the macos-11 image, it's similar, but both are set to 13.2.1.)
Thus, using xcode-select -s alone is insufficient, one also needs to either set the environment variable or update the plist.

Hello! Given all the above I am going to close the issue. Unfortunately, unlike GH actions, AzDo does not have a nice way (a task) to switch between xcode versions :(, nothing can be done on our side.

The advice here worked for me. I use GitHub Actions to build a project based on .NET MAUI 7.x and has Windows and macOS builds to build all 4 main MAUI platforms (Windows, Android, iOS, macOS).
Here's what I ended up with in my YML file:
https://github.com/Eilon/HybridWebView/blob/4fcf89408bbfb38caa7edabf877f541cb8aaabcf/.github/workflows/_build.yml#L27-L41

@Eilon - Hi! 👋 I'm in a similar setup as you.
No need to go back to Xcode 14.1 at this point.  You can use 14.2, and only a minimal rollback file is needed.  See https://github.com/xamarin/xamarin-macios/issues/17561#issuecomment-1542559109
It's only Xcode 14.3 that we can't use in Github Actions yet (unless you want to try the macos-13 runner, currently in beta).
The only real problem today is that the latest iOS and MacCatalyst dotnet workloads require Xcode 14.3, so don't work on the macos-12 runner.  (It would be better if somehow we could have compatible workloads installed by default, without having to use rollback files.)


Add getCredential() to Scheduler/Filesystem

All arguments of the create() method have getters except the credential.

Blocking for https://github.com/NLeSC/xenon-grpc/issues/28

We use the credential only in the creation of the FileSystem / Scheduler, and subsequently forget it. Could remembering it be a potential security issue ? Not sure, since it was the user who provided it in the first place...

After further discussion we decided to add the getCredential, as many libraries store them anyway.


Add a common SNPs association too

Since we are already calling SNPs for the rare variants associations, we might as well look for common ones, which some people might find easier to look at
Still untested, and would require rewriting bits of the docs

I think all the necessary changes to include this new association analysis are there. I think after this we should drop the bits of the README that are a duplicate of the docs, because otherwise it's a pain to maintain


chore: release 2.4.1

Release-As: 2.4.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
266

Relevant Lines:
266

💛  - Coveralls


Documentation typo? Input and output types > Path()

Documentation link:
https://github.com/replicate/cog/blob/main/docs/python.md#path
Issue:
Should the command be "upscaled_image.save(output_path)" instead of "upscaled_image.save(output)" ?
I am a a bit confused by where does the "output" varaible comes from.
Thanks for clarifying.
Tutorial example code:

import tempfile
from cog import BasePredictor, Input, Path
class Predictor(BasePredictor):
def predict(self, image: Path = Input(description="Image to enlarge")) -> Path:
upscaled_image = do_some_processing(image)
      # To output `cog.Path` objects the file needs to exist, so create a temporary file first.
      # This file will automatically be deleted by Cog after it has been returned.
      output_path = Path(tempfile.mkdtemp()) / "upscaled.png"
      upscaled_image.save(output)
      return Path(output_path)

Hi @wongshumhei. The code in that example is pseudocode, but yes you're correct that it should be using output_path instead of output. I've opened a PR to correct that here: https://github.com/replicate/cog/pull/1464


Feature: XOR folding

As discussed in #32. This implementation adds an extra argument to the CLI, and also an extra argument to the API, permitting the user to specify the number of folds.

I've put the XOR folding in its own function, and changed the tests accordingly. I've also got a small test to check the integration of the XOR folding into existing code.
I would eventually like to include information such as the number of folds, as well as the number of hashes per field and the Bloom filter length, in the schema. It will make more sense to come up with a nice way to structure the hashing settings then. I've opened issue #45 for that.

XOR folding.

Can you bump the version to 0.9.0 and update the CHANGELOG.md please @nbgl

On it!


Error: timed out waiting for the condition kubeflow_components.secrets_manager

Hi,
I am working to deploy Kubeflow 1.6 on AWS EKS. I am following the documentation in:
https://awslabs.github.io/kubeflow-manifests/release-v1.6.1-aws-b1.0.0/docs/deployment/cognito-rds-s3/guide-terraform/
I have fulfilled the pre-requisites:
Create a Ubuntu environment
Clone the repository
Install the necessary tools
as detailed therein. I have also registered a domain with Route 53 as indicated, created a IAM user to use with the Minio client, exported and saved the environment variables. Everything is as indicated.
Everything runs smoothly, however, when the terraform process comes to this step:
  + resource "helm_release" "addon" {
      + atomic                     = false
      + chart                      = "../../../charts/common/aws-secrets-manager/rds-s3"
      + cleanup_on_fail            = false
      + create_namespace           = false
      + dependency_update          = false
      + disable_crd_hooks          = false
      + disable_openapi_validation = false
      + disable_webhooks           = false
      + force_update               = false
      + id                         = (known after apply)
      + lint                       = false
      + manifest                   = (known after apply)
      + max_history                = 0
      + metadata                   = (known after apply)
      + name                       = "secrets-manager"
      + namespace                  = "default"
      + pass_credentials           = false
      + recreate_pods              = false
      + render_subchart_notes      = true
      + replace                    = false
      + reset_values               = false
      + reuse_values               = false
      + skip_crds                  = false
      + status                     = "deployed"
      + timeout                    = 600
      + values                     = []
      + verify                     = false
      + version                    = "0.1.0"
      + wait                       = true
      + wait_for_jobs              = false

      + postrender {}

      + set {
          + name  = (known after apply)
          + type  = (known after apply)
          + value = (known after apply)
        }
    }

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

I am consistently (I have gotten this error after retrying the deployment 5 times) getting the following error:
module.kubeflow_components.module.secrets_manager[0].module.helm_addon.helm_release.addon[0]: Still creating... [9m40s elapsed]
module.kubeflow_components.module.secrets_manager[0].module.helm_addon.helm_release.addon[0]: Still creating... [9m50s elapsed]
module.kubeflow_components.module.secrets_manager[0].module.helm_addon.helm_release.addon[0]: Still creating... [10m0s elapsed]
╷
│ Warning: Resource targeting is in effect
│
│ You are creating a plan with the -target option, which means that the result of this plan may not represent all of the changes requested by the current configuration.
│
│ The -target option is not for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or when Terraform specifically suggests to use it as part of an error message.
╵
╷
│ Warning: Applied changes may be incomplete
│
│ The plan was created with the -target option in effect, so some changes requested in the configuration may have been ignored and the output values may not be fully updated. Run the following command to verify that no other changes are pending:
│     terraform plan
│
│ Note that the -target option is not suitable for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or when Terraform specifically suggests to use it as part of an error message.
╵
╷
│ Warning: Redundant empty provider block
│
│   on cognito-rds-s3-components/main.tf line 1:
│    1: provider "aws" {
│
│ Earlier versions of Terraform used empty provider blocks ("proxy provider configurations") for child modules to declare their need to be passed a provider configuration by their callers. That approach was ambiguous and is now deprecated.
│
│ If you control this module, you can migrate to the new declaration syntax by removing all of the empty provider "aws" blocks and then adding or updating an entry like the following to the required_providers block of module.kubeflow_components:
│     aws = {
│       source = "hashicorp/aws"
│       configuration_aliases = [
│         aws.aws,
│         aws.virginia,
│       ]
│     }
│
│ (and one more similar warning elsewhere)
╵
╷
│ Warning: Experimental feature "module_variable_optional_attrs" is active
│
│   on .terraform/modules/eks_blueprints_kubernetes_addons.ondat/locals.tf line 2, in terraform:
│    2:   experiments = [module_variable_optional_attrs]
│
│ Experimental features are subject to breaking changes in future minor or patch releases, based on feedback.
│
│ If you have feedback on the design of this feature, please open a GitHub issue to discuss it.
│
│ (and 7 more similar warnings elsewhere)
╵
╷
│ Warning: Helm release "secrets-manager" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then run Terraform again.
│
│   with module.kubeflow_components.module.secrets_manager[0].module.helm_addon.helm_release.addon[0],
│   on .terraform/modules/kubeflow_components.secrets_manager.helm_addon/modules/kubernetes-addons/helm-addon/main.tf line 1, in resource "helm_release" "addon":
│    1: resource "helm_release" "addon" {
│
╵
╷
│ Error: timed out waiting for the condition
│
│   with module.kubeflow_components.module.secrets_manager[0].module.helm_addon.helm_release.addon[0],
│   on .terraform/modules/kubeflow_components.secrets_manager.helm_addon/modules/kubernetes-addons/helm-addon/main.tf line 1, in resource "helm_release" "addon":
│    1: resource "helm_release" "addon" {
│
╵
Makefile:30: recipe for target 'deploy-kubeflow-components' failed
make: *** [deploy-kubeflow-components] Error 1

Any clue on how to fix this error?
Thanks a lot in advance!

I am able to deploy Kubeflow on AWS without any problem. This is no longer an issue and can be closed.

Great! As discussed on slack, checking the aws-secrets-sync pod and helm chart status might have helped resolving the issue

I'm getting the same issue:

NAME                            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                           APP VERSION
aws-authservice                 default         1               2022-11-18 22:36:55.416636 -0800 PST    deployed        aws-authservice-0.1.0           v0.1.0
cluster-local-gateway           default         1               2022-11-18 22:38:40.457996 -0800 PST    deployed        cluster-local-gateway-0.1.0     1.6.1
istio                           default         1               2022-11-18 21:30:17.454467 -0800 PST    deployed        istio-1-14-0.1.1                1.14.1
knative-eventing                default         1               2022-11-18 22:39:05.265905 -0800 PST    deployed        knative-eventing-0.1.0          1.2.5
knative-serving                 default         1               2022-11-18 22:37:24.486621 -0800 PST    deployed        knative-serving-0.1.0           1.2.5
kubeflow-issuer                 default         1               2022-11-18 21:29:57.706594 -0800 PST    deployed        kubeflow-issuer-0.1.0           v1.6.1
kubeflow-istio-resources        default         1               2022-11-18 22:40:21.590822 -0800 PST    deployed        kubeflow-istio-resources-0.1.0  1.6.1
kubeflow-roles                  default         1               2022-11-18 22:40:13.891175 -0800 PST    deployed        kubeflow-roles-0.1.0            v1.6.1
secrets-manager                 default         1               2022-11-18 23:21:35.45157 -0800 PST     pending-install aws-secrets-manager-0.1.0       v0.1.0

any hints on what to do?

I'm getting the same issue:
stuck on install secrets-manager and would timeout.
module.kubeflow_components.module.secrets_manager[0].module.helm_addon.helm_release.addon[0]: Still creating... [6m50s elapsed]

NAME                            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                           APP VERSION
aws-authservice                 default         1               2022-11-18 22:36:55.416636 -0800 PST    deployed        aws-authservice-0.1.0           v0.1.0
cluster-local-gateway           default         1               2022-11-18 22:38:40.457996 -0800 PST    deployed        cluster-local-gateway-0.1.0     1.6.1
istio                           default         1               2022-11-18 21:30:17.454467 -0800 PST    deployed        istio-1-14-0.1.1                1.14.1
knative-eventing                default         1               2022-11-18 22:39:05.265905 -0800 PST    deployed        knative-eventing-0.1.0          1.2.5
knative-serving                 default         1               2022-11-18 22:37:24.486621 -0800 PST    deployed        knative-serving-0.1.0           1.2.5
kubeflow-issuer                 default         1               2022-11-18 21:29:57.706594 -0800 PST    deployed        kubeflow-issuer-0.1.0           v1.6.1
kubeflow-istio-resources        default         1               2022-11-18 22:40:21.590822 -0800 PST    deployed        kubeflow-istio-resources-0.1.0  1.6.1
kubeflow-roles                  default         1               2022-11-18 22:40:13.891175 -0800 PST    deployed        kubeflow-roles-0.1.0            v1.6.1
secrets-manager                 default         1               2022-11-18 23:21:35.45157 -0800 PST     pending-install aws-secrets-manager-0.1.0       v0.1.0

any hints on what to do?

rerunning the make deploy and using a new terminal instances somehow went though.

@yongkangzhao thanks for the update, we will keep an eye for more such issues and try to reproduce it as well

Any solution around the same, I'm also running into same issue.