Fixing rendering issue - take 3

Content previously reviewed - trying again starting with last known good
set of changes

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/alternation?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/anchors?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/backreference?branch=pr-en-us-1047
Please see 27 more published files of this docset in report.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/basetypes/quickref.md). Referenced by file: docs/basetypes/alternation.md at line: 327...
Open Publishing Report.

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/alternation?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/anchors?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/backreference?branch=pr-en-us-1047
Please see 27 more published files of this docset in report.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/standard/basetypes/customnumeric.md)...
Open Publishing Report.

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/alternation?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/anchors?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/backreference?branch=pr-en-us-1047
Please see 27 more published files of this docset in report.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/standard/basetypes/customnumeric.md)...
Open Publishing Report.

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/alternation?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/anchors?branch=pr-en-us-1047
https://review.docs.microsoft.com/en-us/dotnet/articles/basetypes/backreference?branch=pr-en-us-1047
Please see 27 more published files of this docset in report.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/standard/basetypes/index.md)...
Open Publishing Report.

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
No file of this docset changes.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/standard/basetypes/quickref.md). Referenced by file: docs/standard/basetypes/alternation.md at line: 327...
Open Publishing Report.

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
No file of this docset changes.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/standard/basetypes/quickref.md). Referenced by file: docs/standard/basetypes/alternation.md at line: 327...
Open Publishing Report.

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
No file of this docset changes.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/standard/basetypes/quickref.md). Referenced by file: docs/standard/basetypes/alternation.md at line: 327...
Open Publishing Report.

Open Publishing Build Service: The pull request content has been published and here are some changed files links of this time:

Docset 1 - core-docs
No file of this docset changes.

Status: SucceededWithWarning. Message: Warning occurred: Invalid file link:(~/docs/standard/basetypes/quickref.md). Referenced by file: docs/standard/basetypes/alternation.md at line: 327...
Open Publishing Report.

Still failing after failed Win Samples CI build


writeFileSync only takes a string, Buffer, TypedArray, or DataView

over here: https://github.com/NullVoxPopuli/limber/runs/2602911954#step:6:21
I received a number

testing it out here: https://github.com/NullVoxPopuli/limber/actions/runs/851381576

This has been fairly stable

Fixed by #40


[Hetzner Cloud] Support creating private-network-only machines (without public IP)

Hetzner Cloud recently started supporting servers without a public ("primary" in their lingo) IP address, i.e. private-network-only servers.
It would be nice if it were possible to create these using machine-controller.

@sphr2k shouldn't this already be possible? If I understand it correctly then you just need to specify a private network here https://github.com/kubermatic/machine-controller/blob/main/examples/hetzner-machinedeployment.yaml#L54

@ahmedwaleedmalik @ahmedwaleedmalik Adding a private network under networks creates a VM with both a public and a private network interface.
In the past, every Hetzner VM needed a public IP, but that changed a few months ago, so it is now possible to create machines without a public interface.
However, I have just realised that this is probably not very useful for most use cases, since Hetzner does not provide a NAT gateway, so these VMs will only be able to serve incoming requests via a load balancer, but not pull any images, unless a private registry on the same subnet is used.

You need a NAT gateway if you will go this way.
Your apps need to be able to connect to outside, like maybe backends connecting to other 3rd party services.
If nodes are not started with a default gateway with internet connection, this will not work.
I think the AWS deployment has some tips on how to proceed with this, but on AWS is easy as they offer a manager nat gateway.
On hetzner it will bring another layer in this. Manually using kubeadm I did this kind of setup, works, but when u go this way, ensure that all you will deploy there it is good to have one single IP to communicate to outside.


v8/nodejs: ARM64 support unwinder?

curious if any work is being done here and what the roadblocks are
https://github.com/open-telemetry/opentelemetry-ebpf-profiler/blob/b755a7ced4bfd72dee64af5fc07c4c29a9971c00/tracer/types/parse.go#L141-L144

I believe this is not currently being worked on. I wrote the original nodejs unwinder. @athre0z worked on most of the arm64 unwinder ports, but is no longer working on those. I am not aware of any major technical road blockers, but it does require some low-level research regarding the stack frame layout and few other things so that this can be implemented. So I believe this is pending someone to just do (or sponsor for) the work to be done.


All shoes need noslip

Description

Slipping is cringe. Also only happens when you take your shoes off on cm13

Marines were made immune to slipping in https://github.com/CM-14/CM-14/commit/3be54a1809204a5a6bd4ac51d934c71b2a7566e8 already
Is there anything that should be able to slip them?

Oh I did not see that PR
Marines who take their shoes off can slip on the banana peel on LV :trollface: but it's not a used mechanic besides that
LGTM then


beta update

Beta Update

https://github.com/kodadot/nft-gallery/pull/10460
https://github.com/kodadot/nft-gallery/pull/10456
https://github.com/kodadot/nft-gallery/pull/10445
https://github.com/kodadot/nft-gallery/pull/10442
https://github.com/kodadot/nft-gallery/pull/10438
https://github.com/kodadot/nft-gallery/pull/10431
https://github.com/kodadot/nft-gallery/pull/10423
https://github.com/kodadot/nft-gallery/pull/10414
https://github.com/kodadot/nft-gallery/pull/10413
https://github.com/kodadot/nft-gallery/pull/10410
https://github.com/kodadot/nft-gallery/pull/10398
https://github.com/kodadot/nft-gallery/pull/10395
https://github.com/kodadot/nft-gallery/pull/10392
https://github.com/kodadot/nft-gallery/pull/10387
https://github.com/kodadot/nft-gallery/pull/10384
https://github.com/kodadot/nft-gallery/pull/10379
https://github.com/kodadot/nft-gallery/pull/10378
https://github.com/kodadot/nft-gallery/pull/10377
https://github.com/kodadot/nft-gallery/pull/10374
https://github.com/kodadot/nft-gallery/pull/10372
https://github.com/kodadot/nft-gallery/pull/10366
https://github.com/kodadot/nft-gallery/pull/10365
https://github.com/kodadot/nft-gallery/pull/10364
https://github.com/kodadot/nft-gallery/pull/10363
https://github.com/kodadot/nft-gallery/pull/10362
https://github.com/kodadot/nft-gallery/pull/10361
https://github.com/kodadot/nft-gallery/pull/10358
https://github.com/kodadot/nft-gallery/pull/10357
https://github.com/kodadot/nft-gallery/pull/10349
https://github.com/kodadot/nft-gallery/pull/10345

@kodadot/internal-dev
@prury
Plsease test if there are not critical bugs/ undefined behaviour. I want to merge this


Thinking in react

Current State
I am opening a PR with the progress I've made so far.
Completed

[x] Introduction
[x] Step 1
[x] Step 2
[x] Step 3
[x] Step 4
[x] Step 5
[x] Conclusion

Work in Progress

[x] Review

Note for Reviewers

Translation is complete, kept State and Props in English as it clearifies the content more.
Please Review 🚀

@shakib609, @nutboltu please review.

Thanks @JubayerJoy :rocket:


added version

Let's make this 1.5.1 and we can get this merged @gabrielflorit

Looks like I deleted the branch - I can't edit this file anymore. Go ahead and make the change @wilmoore , but thanks!

Looks like I deleted the branch - I can't edit this file anymore. Go ahead and make the change...

No worries. I think we will actually go another route with this since I'm not a fan of having to manually change the version number. I'll open a new issue for us to address this in a less manual way.
Thanks anyhow.


Rewrite test_fields.py to be pytest-style

Related to #1160.

Codecov Report

Merging #1205 into master will decrease coverage by 8.3%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1205      +/-   ##
==========================================
- Coverage     100%   91.69%   -8.31%
==========================================
  Files          21       21
  Lines        1975     1975
==========================================
- Hits         1975     1811     -164
- Misses          0      164     +164

Impacted Files
Coverage Δ

urllib3/util/selectors.py
49.38% <0%> (-50.62%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix crash in aws sdk

We have seen some crashes because of this issue in the aws-sdk.
I have been able to reliably reproduce this issue using this script in an EC2 server running ubuntu. I am not able to reproduce it locally on my Mac though.

IssueHunt Summary

Backers (Total: $300.00)

 supabase ($300.00)

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

This issue was caused by code reentrant in Node.js http parser, this PR (https://github.com/nodejs/node/pull/43369) is in progress to fix this issue.

Upstream node.js has fixed this issue in https://github.com/nodejs/node/pull/43369, should we follow it up?

Closed via #167.


Update nscplugin, sbt-scala-native, ... to 0.4.15 in main

About this PR
📦 Updates

org.scala-native:nscplugin
org.scala-native:sbt-scala-native
org.scala-native:scala3lib
org.scala-native:scalalib
org.scala-native:test-interface

from 0.4.12 to 0.4.15
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-native" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-native" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #86.


Azure OpenAI connection string not detected

I just upgraded https://github.com/aaronpowell/hanselminutesbot to using Preview 4 (4.24156.9 package versions) but when I run the application I get an error:
A connection string for 'AzureOpenAI' could not be retrieved
This app was working with Preview 3 on the same machine with no problems - I just flipped over the NuGet package versions.
Attempting to debug myself it seems that the ConnectionString property of AzureOpenAIResource is returning null.

I think the problem comes from this line change: https://github.com/dotnet/aspire/commit/bfd9376dc61c59971a2abad79ee7a546d3e93087#diff-7fd7862ce12369547085d74b5813ae529b1cdee8ab4024a4dbb23c2680539f3aR193
It removed the lookup to builder.ApplicationBuilder.Configuration.GetConnectionString if the resource failed to provide the connection string itself.

See https://github.com/dotnet/aspire/issues/2395. This is one of the big changes in preview 5 that we need to resolve in P5.

Docs here https://github.com/dotnet/docs-aspire/pull/485

Thanks, should have checked this before bugging @mitchdenny 🤣


Do not override explicitly specified values with the default from virtual variants

When building with a variant which is included into one of virtual variants, the value of the former is ignored:
↪  phpbrew -d install --dryrun 5.6.16 +default +openssl=/usr/local/opt/openssl
# ./configure --with-openssl=/usr

As far as virtual variants do not provide any values by definition, they shouldn't override explicitly specified values:
↪  phpbrew -d install --dryrun 5.6.16 +default +openssl=/usr/local/opt/openssl
# ./configure --with-openssl=/usr/local/opt/openssl

Thanks!


CASSANDRA-9494 was only committed on trunk

We need a @since for test_reading_with_ttl because CASSANDRA-9494 is only on trunk, at least for the time being.

Great, thank you. Merging.


Open-ended inputs via a link element

Hello @david-r-edgar! I hope you're well.
tl;dr – I'd like to add an input handler (across all domains) which looks for an element like this in the page head:
<link rel="map-view" href="geo:37.78918,-122.40335?z=12">

If such a link is found, it will work as an input for MapSwitcher.
I'm happy to code this up, if it sounds good to you!
Longer story –
I've been making my own mapping tools lately (Strava Atlas and Elevator, if you want to take a look). I've been missing getting to use MapSwitcher with them. But I don't think it would make any sense to add my peculiar niche tools to the MapSwitcher codebase! Rather, I thought it would be good if a website could advertise itself as offering a map view. Then MapSwitcher could read that off of any site, without needing a special input handler.
As far as I know, there is no existing convention for this. I picked the <link> style above by:

looking for a convention for map views (center + view), and finding the geo: uri scheme (or rather, Android's extension thereof),
figuring, since it's a URI, we might as well use a link tag.

I'm happy to revise this, especially if you know a standard I'm missing.
If MapSwitcher had this, it would be easy for hobby projects like mine to add a (possibly dynamically updated) <link> element and immediately work as MapSwitcher inputs. (Also, people could write extensions or userscripts which would add this <link> element to existing pages.)
Please let me know what you think. Thanks!
(Open-ended outputs are another story... an interesting one!)

An alternative to the <link> I proposed comes from this expired IETF draft from 2007. It proposes
<meta name="geo.position" content="37.78918;-122.40335">

(and some other less relevant keys).
Issues with this:

There's no provision for specifying zoom. If we wanted to use this notation, I might suggest augmenting it with:<meta name="geo.zoom" content="12">

More generally, this is a bit of an abuse of the standard. The meta tag is supposed to say "this page is about a location", but we're just using it to refer to where a map view is centered. So it's no surprise there's no "geo.zoom" already. (I don't mind this too much, if useful things can come of it.)
It doesn't seem like anyone actually uses this standard.

Maybe I'll ask around a bit.

This is a great idea.
Actually I had previously had the beginnings of thoughts along similar lines, but I didn't know of any existing standard or convention.
I'm not immediately sure which of your suggestions I'd prefer. As you mention, a zoom parameter is definitely desirable. (And if not that, then some other value that allows the scale to be determined.)
One thing to bear in mind is that I've done quite a lot of work on the tabs2 branch - I'm intending it to be the next major release; it just needs a bit more testing, hopefully over the coming days.
It refactors lots of the code quite significantly.
I imagine that it's best to set up a default extractor which will run against any non-recognised URL, and it can potentially search for whichever of these 'standard' formats matches.
If you would like to create a PR, you might prefer to base it on that tabs2 branch.

This is a great idea.
Actually I had previously had the beginnings of thoughts along similar lines, but I didn't know of any existing standard or convention.
I'm not immediately sure which of your suggestions I'd prefer. As you mention, a zoom parameter is definitely desirable. (And if not that, then some other value that allows the scale to be determined.)
One thing to bear in mind is that I've done quite a lot of work on the tabs2 branch - I'm intending it to be the next major release; it just needs a bit more testing, hopefully over the coming days.
It refactors lots of the code quite significantly.
I imagine that it's best to set up a default extractor which will run against any non-recognised URL, and it can potentially search for whichever of these 'standard' formats matches.
If you would like to create a PR, you might prefer to base it on that tabs2 branch.


The options argument is not passed to Spark reader properly.

The issue was reported at dev-list ('read_delta' with timestamp option).
df = ks.read_delta('/delta/OI_test', timestamp="2019-10-25")

retrieves only the most recent version of the table.
This is because the options argument is not passed to Spark reader properly.

I'll work on this.


HTTP2

Hi,
I've seen a few known issues for HTTP2 support but i haven't been able to find a solution anywhere. SDPY module seems to be working ok but some online comparisons show this to not be as fast.
I have tried and installed the modules http2 and express-http2 but still through the same errors alot of the same issues in previous issue submissions. Has there been a fix released or a workaround?
Thanks,
Perry

The author of the http2 module is asking for someone to submit a patch for this issue at https://github.com/molnarg/node-http2/issues/100#issuecomment-238672259
I have no idea what express-http2 is, and going to https://www.npmjs.com/package/express-http2 just shows it's a clone of this module, so the link goes to this repository and there is no information on what it is or does.


Update senders.md

Minor updates and deleted a hanging sentence.
Description of the change:
Reason for the change:
Link to original source:

Closes #

Hello @bcblackmer,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Metadata about supported Django versions is outdated

Hi there, thanks for the library.   Could you mention the supported Django versions on the github landing page and/or the docs?
It is still listing Django 1.8 classifier in the setup.cfg metadata, and on the PyPI landing page for release 6.0.1, even though I'm sure 1.8 is no longer supported.

Thanks @wimglenn I removed the classifiers. We generally only support the latest version + latest LTS.
Fix is released in 6.0.2


Save current outfit

@ErinDeveloping use discord for support. This is not an issue with the script, but rather a misconfiguration


Arguments

Is there a way to pass arguments when you start the app? I have tried setting them in AsyncStorage but the promise from AsyncStorage get stuck in firebase service. Thank you.

There were plans to pass args to the start function and then place them into a bundle which would be fed back to the main activity on launch. Mostly part of an update we haven't got around to yet.
Any suggestions as to how you'd like that? was thinking probably passing an array.
How are you trying to get the values?
Are you running promise based functions with firebase?
Might be able to use the finally promise method.

I'm gonna close this for now as you can store and retrieve values for use before the app starts and after the app starts depending on how you are handling your background task/service.
This might be something we handle in the future.
Please refer to the suggestions issue here if you'd like to see an implementation.


Don't use pragma once in .cpp file

Fix a compiler warning.

Thanks for your PR. Very much appreciated.


How to implement new rules

I have a few doubts:

How can I scan for different services under ec2 like ingress using rego
Where can I access the scan data or the AWS data related to ec2.

For a rego looking like this
deny[res] {
	policy := input.aws.ec2.policies[_]
	value = json.unmarshal(policy.document.value)
	statements = value.Statement
	# Need to write a logic to check for ingress port availability
	# Need to understand how the data looks like to implement a check
	res = result.new("EC2 Ingress Port 123456 ", policy.document)
}

I am not able to understand how the scan data is getting accessed or the raw data location or the location of the policy using which I can implement a check for ingress.

Hi @Chiranjeevignaidu ! I answered you here https://github.com/aquasecurity/defsec/discussions/1456.


Add FindCSV.cmake module

🎉 New feature
Summary
This patch adds a CMake module for libcsv-dev.
Test it

See https://github.com/gazebosim/gz-common/pull/402.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@scpeters how shall we go about Homebrew here?

@scpeters how shall we go about Homebrew here?

https://github.com/osrf/homebrew-simulation/pull/1976 should take care of it

This could technically be useful for some user, but we decided against introducing a dependency to libcsv because it's LGPL.


Anagram String Code

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
An anagram of a string is another string that contains the same characters, only the order of characters can be different.
For example, “abcd” and “dabc” are an anagram of each other.
Checklist

[X] I've read the contribution guidelines.
[X] I've checked the issue list before deciding what to submit.
[X] I've edited the README.md and link to my code.

Related Issues or Pull Requests
Fixed #1969 . I have linked my code in readme file and also made the changes required for pull request.
In my Previous pull request, the submodule were mistakenly added and when I try to remove it after @HarshCasper guide, I didn't find the submodule to remove it, So, I decided to create new PR for removing inconvenienced from previous one.

Hi @HarshCasper , I appreciate your endless support for guiding us.
Please review my PR and give your feedback if there is any changes required..
thanks in advance...

Please use a Java Code Formatter. Apart from the same, have these changes:

Use proper variable names. a, b, c doesn't suffice.

Hi @HarshCasper, please look into my new PR for same issue but after going through your review, I made the changes.
Please review #3259.
Thanks in advance...


Support portforward for kata and gVisor

We recently added portforward support for windows https://github.com/containerd/cri/blob/master/pkg/server/sandbox_portforward_windows.go. It exec into the pause container, and runs wincat.exe to do the bidirectional data redirection.
We can generalize the solution, and use it to support kata and gVisor, and even replace the current runc support to get rid of the dependency of socat on the host.
Option 1: Keep the socat implementation for runc, and support this for kata or gVisor.
We need to introduce 2 options PortforwardExecCmd and SandboxImage into runtime config https://github.com/containerd/cri/blob/master/pkg/config/config.go#L31.
And the CRI plugin will exec to run the PortforwardExecCmd instead of running socat if the 2 options above are configured for a runtime.
Option 2: Use this approach for everything.
This one requires changing the default sandbox image.
We are using k8s.gcr.io/pause:3.1 right now.
We need to:

Either maintain our own pause image;
Or work with Kubernetes upstream to add a socat implementation into the pause image.

Moving socat implementation into the pause image will get rid of the socat dependency for all Kubernetes users, and make it possible to support kata and gVisor, and windows is already doing that. I think it is worth doing.
NOTE that was previously discussed in https://docs.google.com/presentation/d/1x1B2_DFZ9VI2E_-pB2pzeYKtUxrK4XLXd7I0JWD1Z40/edit#slide=id.p.
One useful discussion there about this approach:
This makes the pause image larger, and increase the memory footprint when portforward runs.

However, pause image is only pulled once, and all pause containers share the same image, I don't see it introduce too much overhead.

As for memory footprint, if user doesn't use portforward, they won't be affected. If they are, the overall memory foot print is no difference with today, the extra memory usage is just moved into the pause container. The good thing is that the extra memory usage will be charged now; the bad thing is that this destabilize the pause container.

One option is that we keep pause process with original oom score, and set higher oom score adj for other utility exec processes.

@fvoznika @egernst @gnawux

draft implementation on kata side: https://github.com/kata-containers/kata-containers/pull/5979

Also some work was done here, but it's closed: https://github.com/containerd/containerd/pull/4814

is the issue actively being worked on?

is the issue actively being worked on?

Not to my knowledge on the containerd side. The last patch or POC was my PR https://github.com/containerd/containerd/pull/4814. This was rejected initially by the containerd team because they wanted it to be based on a better internal API or set of interfaces.
I think someone could work on it now that the Sandbox API is now done and this could be modeled after that as an extension to the shim API. Though, I'm not exactly sure how that landed.


Jax is_fully_replecated method issue

Description
Seems like the is_fully_replicated method is problematic. See colab: https://colab.corp.google.com/drive/1qIUvfu8OvdqbdEby8DdnzuNYb3dKOkBq?usp=sharing
The code we have there is :
_jax_arr= jnp.array([1,2,3])
jax_arr.is_fully_replicated # True
jax_arr = flax.jax_utils.replicate(jax_arr)
jax_arr.is_fully_replicated # False_
We would image it being the exact opposite outputs but both for a TPU and CPU runtimes we get that mysterious output.
What jax/jaxlib version are you using?
Latest
Which accelerator(s) are you using?
CPUt + TPU
Additional system info
Colab/Borg
NVIDIA GPU info
No response

It returns False because the data is not actually replicated. If you check the sharding, there is a UnStacked(8) in it which means that the value is not actually replicated but indeed sharded.
I'll figure out how to fix this.

Any updates on this? I am also affected.

I would suggest to move to shard_map. pmap is in maintenance mode and these problems are specific to pmap and PmapSharding.


handle issue about background thread in ios

Guessing we shouldn't be seeing this.
Using<EMAIL_ADDRESS>Xcode 14.3
iPhone 13
I see this warning in xcode console when I invoke:
BarcodeScanner.startScan()
⚡  TO JS undefined
⚡  To Native ->  BarcodeScanner startScan 65416664
Thread Performance Checker: -[AVCaptureSession startRunning] should be called from background thread. Calling it on the main thread can lead to UI unresponsiveness
PID: 3349, TID: 187904
Backtrace
=================================================================
3   CapacitorCommunityBarcodeScanner    0x0000000104ecb154 $s32CapacitorCommunityBarcodeScanner0cD0C4scan33_E9781981B91FA2D5C67BE1318BC971C3LLyyFyyScMYccfU1_ + 512
4   CapacitorCommunityBarcodeScanner    0x0000000104ec99f4 $sIeg_IeyB_TR + 48
5   libdispatch.dylib                   0x00000001052e4520 _dispatch_call_block_and_release + 32
6   libdispatch.dylib                   0x00000001052e6038 _dispatch_client_callout + 20
7   libdispatch.dylib                   0x00000001052f6798 _dispatch_main_queue_drain + 1196
8   libdispatch.dylib                   0x00000001052f62dc _dispatch_main_queue_callback_4CF + 44
9   CoreFoundation                      0x00000001c36fdd18 6A07CBE8-4F65-3DBC-B59D-C1A188A7B95D + 625944
10  CoreFoundation                      0x00000001c36df650 6A07CBE8-4F65-3DBC-B59D-C1A188A7B95D + 501328
11  CoreFoundation                      0x00000001c36e44dc CFRunLoopRunSpecific + 612
12  GraphicsServices                    0x00000001fe94435c GSEventRunModal + 164
13  UIKitCore                           0x00000001c5a7037c B0858D8E-7220-37BF-873F-ECC2B0A358C3 + 3789692
14  UIKitCore                           0x00000001c5a6ffe0 UIApplicationMain + 340
15  App                                 0x0000000104a5ffbc main + 64
16  dyld                                0x00000001e2b6cdec 41605DC7-F412-37D1-B51B-FEE1A26701E9 + 89580

We are aware of this "issue" and I am pretty sure it is fixed in the upcoming release, but I will have a look at it and double-check it :)

It is not an issue, it is a warning. The plugin works without any issues.
It is not ideal of course, but so far nobody had any issues because of this.

I seem to only get a black screen when launching the barcode scanner.  Here's what I'm using for Capacitor.  Let me know if you have any suggestions of things I can try to get it working or if I can provide any further information.  Thanks for your help.
  @capacitor/cli: 4.7.3
  @capacitor/core: 4.7.3
  @capacitor/android: 4.7.3
  @capacitor/ios: 4.7.3

So the black screen issue is with an iPad 5th generation running iOS 16.2.  I tested again on an iPhone 12 Pro running iOS 16.4.1 and it works as expected.  My black screen issue is seemingly separate from this issue.  Thanks for the help and feedback @thegnuu.  🍻

This is fixed in v5.0.0-beta.1 :)


Research what ends up in stress shaded jar

The fluo pom defaults to hadoop 2.3.0. If I build stress jar with -Dhadoop.version=2.6.0 what version of hadoop ends up in shaded jar. Not sure if setting hadoop.version will affect dependant fluo poms. Also, can all of hadoop deps be excluded from stress shaded jar?

In #10, the stress tests stopped using a shaded jar and started using the fluo classpath command to include Hadoop dependencies.  Therefore, this issue can be closed.


Integration test does not serialise my request

I can't pinpoint why my integration test is not working; it seems somewhere the request object doesn't get serialised into my Endpoint method.
I hope you can give me some clues where to find the issue.
I am using a middleware just to see whether the json object is posted. That is the case.
But in the end the HandleAsync(Request req, CancellationToken ct) req object stays empty.
I am using XUNIT.
Using this class definition public class EndpointFixture : WebApplicationFactory<Program> to get my unit testing to work.
The unit test class itself
public class EndpointTests : IClassFixture<EndpointFixture>
	[Fact]
	public void LoginForUnknownUser()
	{
		var client = _fixture.GetAnonymousClient("en");
		var (_, result) = client
			.POSTAsync<Endpoint, Request, Response>(
				new Request
				{
					Email =<EMAIL_ADDRESS>				}).GetAwaiter().GetResult();

	// leaving out my assertions here
	}

the GetAnonymousClient is coming from the EndpointFixture class
public HttpClient GetAnonymousClient(string language)
	{
		var client = Server.CreateClient();
		client.DefaultRequestHeaders.Add("X-Request", "XXXXXXX");
		client.DefaultRequestHeaders.Add("X-Language", language);
		return client;
	}

As said, when I place break points, my Endpoint is called OK (so the client basically is working, and using my discovered endpoints)
By my request object - the properties of it - are all null while I know 100% sure (my debugging my Middleware) that I get the correct json with the Email field filled-in.
Can you point me in a direction / hook where I can see when the request object is filled so I can debug through it?
Debug print of the response body:

Same call, outside the unit test:

where my request is filled in.
public class Request
{
	public string Email { get; set; }
}

in bed right now so will have a look at this tomorrow morning. in the meantime if you reference the FastEndpoints source and add a breakpoint at the following location and then step through, you might be able to find out what's happening.
https://github.com/dj-nitehawk/FastEndpoints/blob/f5fdbe5beac4e4a897c080c23c8def6176317e9f/Src/Library/Endpoint/Endpoint.Static.cs#L12

OK; it's sure a serialisation issue.

even reading the body from within the handler, I see the correct json;
Will try to investigate further.

deserialization of the request dto only fails in the integration test right? works correctly from a browser or postman or something?

Yes correct. Only during test

FYI
I tried to debug, and came up with following issue:
    private static async Task<TRequest> BindToModel(HttpContext ctx, List<ValidationFailure> failures, JsonSerializerContext? serializerCtx, CancellationToken cancellation)
    {
        TRequest? req = default;

        if (ctx.Request.ContentLength > 0)

The ctx.Request.ContentLength is where it goes wrong. The ContentLength is 0 during the integration test; however, if I skip the if statement and move on to the next block
            if (isPlainTextRequest)
                req = await BindPlainTextBody(ctx.Request.Body).ConfigureAwait(false);
            else if (ctx.Request.HasJsonContentType())
                req = (TRequest?)await FastEndpoints.Config.ReqDeserializerFunc(ctx.Request, tRequest, serializerCtx, cancellation);

everything works fine; for some reason the ContentLength check is "different" when running from regular http client.

https://github.com/dotnet/aspnetcore/issues/18463
related?

interesting indeed. all the integration tests here are using the same approach with MSTest and the content length property is properly set automatically.
maybe its a issue with xunit + waf?
could you give it a shot with mstest?
ideally all clients should automatically set the content-length header if there is some content in the body.

Would love to keep using XUnit
What about this remark:
https://docs.microsoft.com/en-us/aspnet/core/test/middleware?view=aspnetcore-6.0#content-length-and-transfer-encoding-headers
TestServer does not set transport related request or response headers such as Content-Length or Transfer-Encoding. Applications should avoid depending on these headers because their usage varies by client, scenario, and protocol.

Temporary fix for me; in my (already) running middleware, I am setting the ContentLength myself if running from a unit-test. Then it works.
Still think you might reconsider that if (ctx.Request.ContentLength > 0) check.

As far as I can see, there is no need to have the check there; all calls behind it don't have an issue with the ContentLength property 0 but the underlying stream contains data.

yeah making the change now... will push out next beta in a few minutes!
this check was an old relic from some past code which is no longer necessary...

v3.11.0-beta3 released


Repositioning the plot toolwindow with drag & drop caused VS hang

It was stuck in the special transient UI that VS has for helping you re-arrange tool windows.
Happened on Shahrokh's machine. I put logs and dump here:
\pytools\r\Bugs\plotwindowstuckdragdrop

@huguesv - anything we need to take to 0.5 from here?

Not easy to repro, but possible.  I kept moving the toolwindow around, eventually it happened.  It looks like it's the drag & drop of plot themselves that interferes with the VS drag & drop of tool windows.
If I break into the debugger while it's stuck, I got:
 	[External Code]
>	Microsoft.R.Components.dll!Microsoft.R.Components.Plots.Implementation.View.RPlotDeviceControl.Image_MouseMove(object sender, System.Windows.Input.MouseEventArgs e) Line 130	C#
 	[External Code]

Stuck into this call:
DragDrop.DoDragDrop(this, obj, DragDropEffects.Copy | DragDropEffects.Move);

I'd switch off just my code, enabled native and point symbols to \\ddrps\symbols and \\symbols\symbols - it is probably stuck somewhere in thread transitions

I'm inclined to say we take the fix I have for 0.5, linked above.  Once you know how to repro, it's actually pretty easy:

Left click inside plot window.
Left click on the "R Plot" tool window label and start dragging up such that you'll send MouseMove events to plot window.
Plot window incorrectly thinks you started dragging a plot, and now you are multi tasking drag & drop :)


piglit: opengl test suite

Because inquiring minds want to know if OpenGL really works in snaps.

The failure appears to be spurious... is there a way to turn down the verbosity of the cmake
build, or allow a longer build log?

Wow, this is an interesting build failure (https://s3.amazonaws.com/archive.travis-ci.org/jobs/166607459/log.txt):
The log length has exceeded the limit of 4 MB (this usually means that the test suite is raising the same exception over and over).

The job has been terminated

Confirming build locally.

Looking at dmesg while running shows I've missed a trick:
[82377.292349] audit: type=1400 audit(1476198649.841:408): apparmor="DENIED" operation="open" profile="snap.piglit.piglit" name="/dev/kmsg" pid=9898 comm="dmesg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[82377.311673] audit: type=1400 audit(1476198649.857:409): apparmor="DENIED" operation="open" profile="snap.piglit.piglit" name="/dev/kmsg" pid=9899 comm="dmesg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[82377.379139] audit: type=1400 audit(1476198649.925:410): apparmor="DENIED" operation="sendmsg" profile="snap.piglit.piglit" pid=9900 comm="shader_runner" family="unix" sock_type="dgram" protocol=0 requested_mask="send" denied_mask="send" addr=none peer_addr="@6E7669646961316138326630633100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" peer="unconfined"
[82377.704069] audit: type=1400 audit(1476198650.249:411): apparmor="DENIED" operation="open" profile="snap.piglit.piglit" name="/dev/kmsg" pid=9901 comm="dmesg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
I'll try to clean that up (once I figure out wtf :-) )

Does http://askubuntu.com/questions/783979/how-do-i-debug-snaps help?


Documentation about package-locks

Hi, I was just wondering why this site https://docs.npmjs.com/cli/v6/configuring-npm/package-locks is deprecated or redirects for newer versions of npm.
I was working around package-lock version conflicts and found out that https://www.npmjs.com/package/npm-merge-driver is also archived without any documentation of it being deprecated or not, so i was wondering if there are better approaches to this.
Best regards

npm automatically resolves conflicts in the package-lock internally now with https://github.com/npm/parse-conflict-json#readme
cf https://github.com/npm/cli/blob/68031f2ae1cd5d49b0fb263da1a7eae62712ff97/workspaces/arborist/lib/shrinkwrap.js#L52

That page was removed as part of the v7 updates https://github.com/npm/cli/pull/2475
Because there were other sites that linked to it, it was redirected to the v6 version so that it wouldn't 404 https://github.com/npm/documentation/issues/203

Oh I'm wondering because we had many merge conflicts when upgrading packages from branches and merging them into main.
Maybe I'm using something wrong then. Thank you


Securing the core function arguments to valid types

only standard library date and datetime types (or subtypes) are supported,
added a new dedicated exception,
added a paragraph in the documentation about this type support.

refs #294

[x] Tests with a significant number of years to be tested for your calendar.
[x] Changelog amended with a mention describing your changes.

/cc @yassineAlouini and @johnberroa
if you have any input on this PR, please do not hesitate.

LGTM to me. Well done. :tada:


[ADF-3748] add new license choose option

I have added a new subgenerator to allow the users to choose which license use

Nooooooo, not my liceeeenseee!
thanks @eromano


Make Crypto* streams thread safe

Now they are not, we need to wrap ciphers in Mutex.

I would like to take this one. Can you update a bit the context, especially around ciphers usage, role and why it should be threadsafe.


Is it possible to filter search with multiple parameters?

Can I filter with multiple parameters like:
activity?type=recreational&participants=3
Also, is the maximum number of participants 5?

Hi @amandalok10 ! It is possible to apply multiple filters, such as with type and participants. Using any of the min or max filters will override the normal filter though, so minparticipants overrides participants like in this example.
To answer your second question, technically there is no maximum number of participants, but the max right now is 8 seen here.
I hope this answers your questions!


Groundbreaking bug upon installing

As of the moment I cannot find a way to fix the issue. When you install this module you will get PrismaClient is not a constructor which will cause the developer tool not to show and causes some weird behavior with Nuxt.

@jamols09 I am not a massive fan of the nuxt-prisma package. The issue you've opened needs more information.
In the future, I encourage you to imagine yourself as the maintainer before opening an issue.
Could you share a reproduction repo or example?

Thanks @jamols09 for creating the issue.
@damisparks is right here, I need more information to reproduce this issue.

revert to these version till the issue is fixed    "@prisma/client": "^5.22.0",     "@prisma/nuxt": "^0.0.35",
it worked for me

@tinegaCollins were you also experiencing this issue? Could you provide a repo to help us debug this?

experiencing the same issue on a fresh install of nuxt v3.14.1592
Steps to reproduce:

create clean nuxt project npx nuxi@latest init <my-app>
install @prisma/nuxt npm install @prisma/nuxt
add @prisma/nuxt to nuxt.config.ts as module
start dev server npx run dev
select prisma console defaults
open browser `https://localhost:3000' and view DevTools console

Hi @jharrell , @ankur-arch
Here's a repository reproducing the issue : repo link
With prisma/client 5.22.0 & prisma/nuxt 0.0.35 no issues
With prisma/client 6.0.1 & prisma/nuxt 0.1.13 we get error messages within the browser console, also happens in storybook but w/e
I've migrated between the two versions so you can check the differences :
commits
In this large commit, you can see all the changes that been made to the generated prisma client between the two versions :
commit

Just for reference, on this repo :
No issues directly with npx prisma generate, but fails at npm run build / nuxt build
PS E:\GitHub\prisma-nuxt-failure> npx prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma

✔ Installed the @prisma/client and prisma packages in your project

✔ Generated Prisma Client (v6.0.1) to .\node_modules\@prisma\client in 40ms

Start by importing your Prisma Client (See: https://pris.ly/d/importing-client)

Tip: Want to react to database changes in your app as they happen? Discover how with Pulse: https://pris.ly/tip-1-pulse

PS E:\GitHub\prisma-nuxt-failure> npm run build

> build
> nuxt build

Nuxt 3.14.1592 with Nitro 2.10.4
✔ Prisma CLI is already installed.
✔ Prisma schema file exists.
✔ Database migrations folder exists.

Not migrating the database.
Generating Prisma client...

 ERROR  ✘ Failed to generate Prisma Client.

@jharrell this issue started when we update a repo packages

@jharrell  can I trust you with a private repo?

Yes, you can reach me at my Prisma email: Harrell (at) Prisma (dot) io

same issue here, using<EMAIL_ADDRESS>until this is resolved

Same issue.  As a temporary solution, I downgraded @prisma/client from 6.0.1 to 5.22.0
It work for me:
"@prisma/client": "5.22.0",
"@prisma/nuxt": "0.1.3",

Same issue. Sigh.

Hi @gsxdsm if you downgrade to Prisma Client 5.22.0 is the problem resolved?

Will try, but I'd like to be on 6.1. Not sure why nuxt-prisma is stuck on an older version of Prisma. Doesn't make sense.

Prisma 6 is only 3 weeks old, so I guess we need to be patient and give a break to opensource maintainers that already give a lot to the community.

sam issue, downgrade works fine

Thanks for the patience on this everyone 🙏 .
I can't reproduce the error with 0.0.0-experimental-b764aa7 and this PR should resolve this https://github.com/prisma/nuxt-prisma/pull/69.
Just be sure to use the required node versions required for Prisma 6 too.

Another data point: problem occurred with 6.1.0. I realised I had installed it using node 22.2.0, so I updated to node 22.12.0 and did a clean reinstall. Problem still occurred. Downgraded to Prisma 5.22.0 as described above and the problem disappeared.

@goldengecko 👋 , can you check if this is resolved in the pre-release version? 0.0.0-experimental-b764aa7.
The package wasn't published as there weren't significant changes 😕  from the PR above.

@ankur-arch Yes, I can confirm that it works with the following settings in node 22.12.0:
"@prisma/nuxt": "0.0.0-experimental-b764aa7",
"@prisma/client": "^6.1.0",
"prisma": "^6.1.0"

though I do get some errors about missing fonts in the Prisma Studio instance it boots up:
GET http://localhost:5555/inter-latin-400-normal.27ae72da.woff2 net::ERR_ABORTED 404 (Not Found)Understand this errorAI
index.css:1
GET http://localhost:5555/inter-all-400-normal.4c1f8a0d.woff 404 (Not Found)Understand this errorAI
index.js:1 Bootstrap Duration:<PHONE_NUMBER>34375 ms
index.css:1
GET http://localhost:5555/inter-latin-600-normal.87d718a2.woff2 net::ERR_ABORTED 404 (Not Found)Understand this errorAI
index.css:1
GET http://localhost:5555/jetbrains-mono-latin-400-normal.80a5dc9e.woff2 net::ERR_ABORTED 404 (Not Found)Understand this errorAI
index.css:1
GET http://localhost:5555/inter-all-600-normal.d0a7c8a9.woff net::ERR_ABORTED 404 (Not Found)Understand this errorAI
index.css:1
GET http://localhost:5555/jetbrains-mono-all-400-normal.f86807b7.woff net::ERR_ABORTED 404 (Not Found)
Thanks for getting this working


app crashed on android device of api level = 19 when load library "libtensorflow_inference.so"

System information

Os version 4.4.4
-sdk level 19

logcat:
07-26 15:01:59.429 6521-6521/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: al.omid.tfdroid, PID: 6521
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "rand" referenced by "libtensorflow_inference.so"...
at java.lang.Runtime.loadLibrary(Runtime.java:364)
at java.lang.System.loadLibrary(System.java:526)
at al.omid.tfdroid.MainActivity.(MainActivity.java:28)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1208)
at android.app.Instrumentation.newActivity(Instrumentation.java:1061)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2114)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2257)
at android.app.ActivityThread.access$800(ActivityThread.java:143)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1209)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5120)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:818)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:634)
at dalvik.system.NativeStart.main(Native Method)
07-26 15:02:01.179 6521-6521/al.omid.tfdroid W/System.err:     at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:94)
Describe the problem
Could  you pleas tell me how can I solve this ?  Is "libtensorflow_inference.so" usable for android devices of api level < 20 ?

Are you using only the library or are you trying to use the demo app? IIRC the demo app uses Camera2 so needs >21 but the actual library only requires >14.
Perhaps this comment chain from @andrewharp on #6763 will help you.

I only used the library. I guess it's because I used an old version library file.  It runs ok now when I use library of version r1.2. Thank you very much ~
BTW, I want to ask another question: I see some android example using tensorflow. For example, mnist and de demo app of tensorflow classifier,  They all need to write some c code and generate a new .so file containing both c code written by developer and tensorflow library so.
Is it necessary to write c code and generate a custom .so file when implement a complicate deep learning task ?
And how can I build my own c code together with tensorflow library .so file to generate a new one ?
Hope for your answer . Thank you so much ~

Ah that was going to be my next question because your issue appeared to be fixed in a later release! I've not got around to writing my own android libraries. That might not necessarily be required to create your own program. A lot of it can be done in android/java itself and you can use the inference library for when it's needed. I don't think it contains every op however so there might be some extra work to add in something which you need.
Perhaps you can find some more information here: https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/android
I'll let someone else answer your questions properly as I don't have the experience. Good luck!

@scucheri: @jubjamie is correct, you should be able to accomplish almost any inference task (i.e. non-training) using the Java API and TensorFlowInferenceInterface.java similarily to the examples in the Android demo. You can use the prebuilt Android TF binaries in almost all cases unless you need to add new custom ops.
For further support on non-bug/feature requests we suggest referring your questions to StackOverflow as there is a larger community there. Thanks!

Note that https://github.com/tensorflow/tensorflow/pull/10771, which adds camera 1 support, should enable the demo to run on devices < API 21.

Thank you ~
I had post this question here :

i run into the same issue last week , and it has been solved .
any question about cross compile tensor to mobile can contact me, i'm willing to help others cause google members and other guys always helps me.
here's my way for solving this issue:
target:
i'm using c++ interface and cross compile to ios \ android \ linux \ ...  , and let the app call the interface. android is using jni to call c++ interface.
steps:
1  for android 4.4, we need ndk r12b and api level 14 , my android colleague tells  me that 19 is also for android 4.4, well i didn't try it, i tested api level 14 and it works for android 4.4 \ 6.0 \ 7.0
2  modify the Makefile file in folder contrib/makefile:
modify:  --sysroot $(NDK_ROOT)/platforms/android-21/arch-arm
to :         --sysroot $(NDK_ROOT)/platforms/android-14/arch-arm \
3  modify the compile_android_protobuf.sh file in folder contrib/makefile:
modify:  android_api_version="${ANDROID_API_VERSION:-21}"
to :         android_api_version="${ANDROID_API_VERSION:-14}"
4 run build_all_android.sh to compile tensorflow and protobuf(which depended by tensorflow).
also see https://github.com/tensorflow/tensorflow/tree/master/tensorflow/contrib/makefile for detail
5 get the .h file and .so file .
in my circumstance, i packeted tensorflow lib to my own lib project , pls aware that my own lib set api level to 19, my own lib also can set to 14.  Theoretically libs in level 19 can call libs in level 14, and 14 cannot call 19.  And also aware that api level above 19 is not support android 4.4.

Hi @jakiechris , how about to build the aar by using docker? I'm trying to use lower NDK version but getting some error like
ERROR: /tmpfs/bazel_output/_bazel_root/43801f1e35f242fb634ebbc6079cf6c5/external/androidndk/BUILD.bazel:43:18: Traceback (most recent call last):
	File "/tmpfs/bazel_output/_bazel_root/43801f1e35f242fb634ebbc6079cf6c5/external/androidndk/BUILD.bazel", line 41
		cc_toolchain_suite(<2 more arguments>)
	File "/tmpfs/bazel_output/_bazel_root/43801f1e35f242fb634ebbc6079cf6c5/external/androidndk/BUILD.bazel", line 43, in cc_toolchain_suite
		{"arm64-v8a": ":aarch64-linux-android-4.9-gnu-libstdcpp", "arm64-v8a|gcc-4.9": ":aarch64-linux-android-4.9-gnu-libstdcpp", "arm64-v8a": ":aarch64-linux-android-clang3.8-gnu-libstdcpp", "arm64-v8a|clang3.8": ":aarch64-linux-android-clang3.8-gnu-libstdcpp", "armeabi": ":arm-linux-androideabi-4.9-gnu-libstdcpp", "armeabi|gcc-4.9": ":arm-linux-androideabi-4.9-gnu-libstdcpp", "armeabi-v7a": ":arm-linux-androideabi-4.9-v7a-gnu-libstdcpp", "armeabi-v7a|gcc-4.9": ":arm-linux-androideabi-4.9-v7a-gnu-libstdcpp", "armeabi": ":arm-linux-androideabi-clang3.8-gnu-libstdcpp", "armeabi|clang3.8": ":arm-linux-androideabi-clang3.8-gnu-libstdcpp", "armeabi-v7a": ":arm-linux-androideabi-clang3.8-v7a-gnu-libstdcpp", "armeabi-v7a|clang3.8": ":arm-linux-androideabi-clang3.8-v7a-gnu-libstdcpp", "mips64": ":mips64el-linux-android-4.9-gnu-libstdcpp", "mips64|gcc-4.9": ":mips64el-linux-android-4.9-gnu-libstdcpp", "mips64": ":mips64el-linux-android-clang3.8-gnu-libstdcpp", "mips64|clang3.8": ":mips64el-linux-android-clang3.8-gnu-libstdcpp", "mips": ":mipsel-linux-android-4.9-gnu-libstdcpp", "mips|gcc-4.9": ":mipsel-linux-android-4.9-gnu-libstdcpp", "mips": ":mipsel-linux-android-clang3.8-gnu-libstdcpp", "mips|clang3.8": ":mipsel-linux-android-clang3.8-gnu-libstdcpp", "x86": ":x86-4.9-gnu-libstdcpp", "x86|gcc-4.9": ":x86-4.9-gnu-libstdcpp", "x86": ":x86-clang3.8-gnu-libstdcpp", "x86|clang3.8": ":x86-clang3.8-gnu-libstdcpp", "x86_64": ":x86_64-4.9-gnu-libstdcpp", "x86_64|gcc-4.9": ":x86_64-4.9-gnu-libstdcpp", "x86_64": ":x86_64-clang3.8-gnu-libstdcpp", "x86_64|clang3.8": ":x86_64-clang3.8-gnu-libstdcpp"}
Duplicated key "arm64-v8a" when creating dictionary

Here is the configuration i used
ENV ANDROID_API_LEVEL 14
ENV ANDROID_NDK_API_LEVEL 12
ENV ANDROID_NDK_FILENAME android-ndk-r12b-linux-x86_64.zip

the rest is just the same as in here


bookmarklet language problem

When I tried to submit aseed using bookmarklet, I get a message saying "Please select a language before submitting" although I selected the language before submitting.
I was using the browser Chrome.

@theannielin think you could try to replicate and try to figure this out?

I tried to recreate the problem and found nothing. Could you elaborate a bit more? Any specific conditions?

@jcuanm @meeshmon
Javier, thank you for working on the issue.
I do not see the problem,either.  I used the bookmarklet using Safari, Firefox and Chrome.  I did not have any problem submitting items.  Let me close the issue right now.  When I see the problem again, I will ask you to look at the bookmarklet.

@meeshmon
Sure, no problem.


Update to 0.5.0

Also rerender while I'm here.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Reduce length of description

The description is too long and bleeding out our cards. It might be clipped in the future.

Thanks for pointing this out - it’s been cut!


Create Dockerfile

The google analytics query string is not needed. Also it's an RC release, wouldn't really merge into master

Merged the additions directories; closing the rest


<method-name_RVC> submission made across stereo benchmarks but not displayed on leaderboard.

Hi,
Following the instructions:

Our model does not appear on the leaderboard.
Thank you,
Best.

Hi, the crawler operates manually. We start it about 2-3 times per week. Please check the date/time displayed as "last updated" under the leaderboard  for more information. I think your submission now shows on the leaderboard?

Sorry I missed that piece of information below and did assume it was automatic. Its all good now. Thank you.


Implement Searching in AAS

Currently, the only option to find an object inside an AAS is to iterate.
It might make sense to implement some form of searching inside AASs, especially for the API.

As you mentioned, currently the only possible approach to search, filter, aggregate is to manually load the json, parse them, iterate through them and do some computation on them.
Just as an idea:

When RDF is implemented, with the help of RDFLib, it is possible to run SPARQL queries.
It would be a nice feature to also generate queries. So the search method offers a (SPARQL, MongoDB, CouchDB ,....) query generation functionality. This is quite complex, but it can be very rewarding.

Indeed, the ability to run SPARQL queries would be an extremely powerful tool. Thank you for your suggestion, we'll keep it in mind!


KAFKA-3189: Kafka server returns UnknownServerException for inherited…

… exceptions

@ijuma @becketqin Thoughts on this solution?

@becketqin Added a test for InvalidMessageException

@granthenke Thanks for adding the test. LGTM.
I went over all the Exception that might be thrown to user again. I found that UnknowCodecException and UnknownMagicByteException can be returned to clients but does not even have an error mapping. I think we should add them to error mapping. But we probably should create separate jira ticket for that.

@becketqin Thanks for creating KAFKA-3203. I will look into adding those exceptions.

A couple of minor comments, looks fine otherwise.

@ijuma Addressed your reviews. Thank you.

@ijuma Fixed.

LGTM

@ewencp @gwenshap Would you have time to review this?

LGTM


Gareth update Developer Guide for SortCommand

fixes #86
Create documentation for Sort Command

Codecov Report

Merging #87 (cb559c5) into master (ced2e60) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #87   +/-   ##
=========================================
  Coverage     57.37%   57.37%
  Complexity      553      553
=========================================
  Files            96       96
  Lines          2487     2487
  Branches        349      349
=========================================
  Hits           1427     1427
  Misses          832      832
  Partials        228      228

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Port notebooks to a gallery

[x] Closes #120
[x] I am familiar with the contributing guidelines
~[ ] Tests added~
[ ] Updates entries in docs/sphinx/source/reference for API changes.
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Pull request is nearly complete and ready for detailed review.
[ ] Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Addresses #120.
I've made a new sphinx gallery out of the content of the .ipynb notebooks.
View documentation front page for this PR
View tutorial gallery
Ported notebooks (checked ones can be reviewed)

[x] atmosphere.ipynb
[x] irradiance.ipynb
[x] pvsystem.ipynb
[x] solarposition.ipynb
[x] tmy.ipynb
[x] tmy_and_diffuse_irrad_models.ipynb
[x] tmy_to_power.ipynb
[x] tracking.ipynb

Checklist of reviewed by me

[x] hyperlinks
[ ] remove "notebook" references (PENDING FOR ALL)
[x] function links
[x] check I did not leave anything commented because it doesn't work (ehem ehem I need help)
[x] check bullet lists are correctly rendered

Various points:

I am proposing another gallery; maybe we don't want that and just a folder inside the current examples one (I can open a PR so you can compare the rendering)
Maybe we don't even want a gallery, alternatives just don't come to mind
Most of the tutorials were translated with:

jupyter nbconvert --to script tracking.ipynb
black --line-length 79 tracking.py

then used a list of regexes to find and replace things
Details

Remove In [*]:
Find: # In\[[0-9]+\]:\n\n
Replace: # %%

Hyperlink to sections:
F: \[(.*)\]\(.*\)
R: `$1`_

Convert MD math to rST inline
F: \$(.*?)\$
R: :math:`$1`

Subsections
F: # #{2} (.*)\n
R: # %%\n# $1\n# -------------------------------------

Subsubsections:
F: # #{3} (.*)\n
R: # %%\n# $1\n# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Find *possible* functions that need linking: ``

finally, visually inspected where text and code blocks should go so that related explanations are grouped all together and make sense
Expect to still find typos regarding that.
Feel free to point missed things and so on.

Can we have #1763 merged before this one? I've left some TODOs to remove redundant code.
Also, I've commented code at irradiance.py:614 (and at line 655 because of that) because it raises the following error:
Unexpected failing examples:
/home/docs/checkouts/readthedocs.org/user_builds/pvlib-python/checkouts/1818/docs/tutorials/irradiance.py failed leaving traceback:
Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/pvlib-python/checkouts/1818/docs/tutorials/irradiance.py", line 619, in <module>
    + F1c[ebin, 2] * z[ebin.index]
IndexError: index 8 is out of bounds for axis 0 with size 8

I expect the problem to be at the internal function called on line 617:
F1c, F2c = pvlib.irradiance._get_perez_coefficients(modelt)

View code.
@wholmgren can you have a look at it? TIA.

@echedey-ls thanks for taking the initiative! That issue is 7 years old and the pvlib documentation has changed a lot since then. I am not sure that 1:1 ports into a new Tutorial section are the right approach at this time. It's worth revisiting #329 especially @kandersolar comment https://github.com/pvlib/pvlib-python/issues/329#issuecomment-1277966321 before going too far here. Unfortunately I no longer have the vision or time to do documentation well and would defer to other maintainers and community members.

Thanks @wholmgren , I could figure out the issue with the broken tutorial, the error was on my side: just a commented out line.
I agree on the view about everything to be fair. However, I think it is worth to reuse the old tutorials (they still work well) and give them presence on the web page, so they are easier to spot for anyone so another source of knowledge for users that don't download the repo, and, what I think is the nicest point, they get tested with CI - better to integrate them today than in 7 years, luckily.
Btw I like taking the over-engineering path so we all see how another gallery could benefit us. Or if we prefer just a subsection in the examples gallery. Open to all alternatives, and desiring to improve current docs.
On the other hand, if we have a gallery or section of tutorials then that could ease the port of examples to tutorials (if they are more intended to do so) as stated in Kevin's comment in # 329, split long tutorials, or even make an effort and make new ones. Honestly, I believe this PR is on that path, or even if it wasn't, raising discussion for concrete next steps regarding old tutorials would be fine and I would be willing to help with that (if it is a reasonable amount of time, i.e. I can't create a whole new tutorial)

Unfortunately I no longer have the vision or time to do documentation well and would defer to other maintainers and community members.

Even if it was just a matter of willingness; we've got your back.

I am also hesitant to directly dump the tutorial notebooks into a new Tutorials docs section.  My concerns:

There is certainly good content in them, but some of the explanation needs to be expanded and/or updated for today's pvlib.  Some of the content might also not be within scope for pvlib's docs (looking mostly at the tracking notebook).  I think  a substantial cleanup would be necessary for the notebook contents to be satisfying additions to the sphinx docs.
I'm not sure that a new Tutorials section is the best home for this content.  It could be that a new section in the existing gallery would be better.  Or new User's Guide pages.  More thought is needed about the role that we want these notebooks to have in our docs, with #329 in mind.  The reason I think we should be deliberate here is that, even though semver doesn't apply to documentation, I think it is still desirable to minimize unnecessary "churn" in the documentation, especially in regards to changing the URLs of pages.  So just like we take care when choosing function names and what modules they live in so that we won't have to change them in the long run, I think we should be thinking ahead and trying to avoid setting ourselves up to have to move these pages somewhere else before long.

I think converting the ipynb files to rst is a useful start that will certainly be helpful when we start working on #329 in earnest.  For now I don't think we're quite ready to proceed with adding this content to the sphinx documentation.  I think first we need to do the documentation restructure, and then we can come back and add this content into the new structure.
For whenever we do go forward with this PR in some form, here are a few things I noticed:

this tutorial needs numba for the speed portion to be useful: https://pvlib-python--1818.org.readthedocs.build/en/1818/gallery_tutorials/solarposition.html
Math is using dollar signs instead of :math:: https://pvlib-python--1818.org.readthedocs.build/en/1818/gallery_tutorials/irradiance.html
Bad RST rendering: https://pvlib-python--1818.org.readthedocs.build/en/1818/gallery_tutorials/tracking.html
Bad math rendering: https://pvlib-python--1818.org.readthedocs.build/en/1818/gallery_tutorials/pvsystem.html

Considering the current state of pvlib, I think it's safe to assume this tutorials will be deleted at some point in the future, so I'm closing this PR as unnecessary.


Extern ref types

Closes #584
Adding types and showing the diff for hackatom contract.
It was just changing the function definitions, and then search replace in the test code: &mut deps -> deps.as_mut() and &deps -> deps.as_ref()

Update: After some nice conversations with an advanced Rust coder, I realized I could remove all the <S: Storage, A: Api, Q: Querier> generics in contract code if I just use eg. api: &dyn Api instead of api: &A. This definitely remove a lot of visual complexity from the contracts and makes them more approachable for Rust beginners.
This does involve some more changes to the contract code, but mainly removing complexity.
I would love some feedback when you can review. I think the newer contract code is much easier for devs starting with CosmWasm. And note that the vm code doesn't have to change at all, so this is backwards compatible with the wasm code generated from 0.11 (so we can stick with cosmwasm_version_4)

Haha, I see Mauro is stuggeling with this problem in a similar way I do. This concern is not about getting it compile, but this feeling that when things get super complicationd, you are probably doing something wrong. It feels like Rust is screeming don't try to code Java with me.
But looking at the facts, I think we can agree on the following:

A contract only needs a reference to a Storage and does not need to own it
For contract developers it is desireable to group Storage, Api and Queries into one thing.
There is no generics for mutability, such that handle and query need to receive different structs, one with a mutable and one with an immutable storage reference.

This at the end of the day make Ethan's solution the only one I see working. And I send a lot of time thinking about alternatives.
One change I'd like to propose (I can send a PR for the implementation) is to make the set of references the primary structure Deps: the "external dependencies" of a contract are a set of references. This gives us Deps/DepsMut as better names for the primariy structures (right now DepsRef is not a ref to Deps but something different). Owning dependencies is really a testing problem. In the production code we just have
fn _do_query<M, E>(/* … */) -> ContractResult<QueryResponse> {
    // ...
    let storage = ExternalStorage::new();
    let api = ExternalApi::new();
    let querier = ExternalQuerier::new();
    let deps = Deps {
        storage: &storage,
        api: &api,
        querier: &querier,
    };
    query_fn(deps, env, msg).into()
}

We then can have a cosmwasm_std::testing::OwnedDeps which is the result type of cosmwasm_std::testing::mock_dependencies.

Nice change using &dyn Storage instead of the generics.

Good analysis. I would like to challenge your point 3 above. There's a way to handle a reference with dynamically checked borrowing rules, and that's a RefCell.
Borrowing from your code above, what I'm proposing is something along:

fn _do_query<M, E>(/* … */) -> ContractResult<QueryResponse> {
    // ...
    let storage = ExternalStorage::new();
    let api = ExternalApi::new();
    let querier = ExternalQuerier::new();
    let deps = Deps {
        storage: RefCell::new(storage),
        api: &api,
        querier: &querier,
    };
    query_fn(&deps, env, msg).into()
}

So, basically, passing a reference to Deps in query_fn() (instead of passing Deps by value), and mutably (and dynamically) borrowing Storage when needed.
This still copies Storage in RefCell::new(), but if the only Deps around is that one, which is passed by reference everywhere, that's OK.
You can even do something like:
RefCell::new(ExternalStorage::new())
at initialization. Which is the logical thing to do, by the way.

Mauro, I explicitly only want to pass in the minimal ownership needed - not move in storage (or even &mut Storage) if I will only be using &Storage. A lot of the practical type wrangling came from https://github.com/CosmWasm/cosmwasm-plus/pull/130 which shows the issue with passing in owned values, and was my first draft on the DepsMut, DepsRef idea.
If I run recursive queries on a contract, that would be allowed in the Rust type system if they all have &Storage, but no more. I guess I could pass in &RefCell<Storage> and trust none of them try to get it mutable at runtime. But I also see &Storage as a much simpler API for contract developers than &RefCell<Storage>.
The point is this is not a normal struct, it really is just combining three args into one as they are commonly passed together. Simon did a spike to just pull them into 3 arguments and it made the API much messier. There has been quite some fiddling around to look for designs here, and supporting 2 different structs in the public API (Deps and DepsRef now) seems to be adding minimal complexity in order to save other issues.

But I also see &Storage as a much simpler API for contract developers than &RefCell<Storage>.

True. And, if the goal is precisley to make the API simpler, this is an important point.
Also, in terms of safety, what you say about restricting mutable access to static / compile time borrows makes sense.
I tend to forget we're dealing with an API here, and that it must not only work with the existing code base, but also be easy to use in future contracts / for future users.

The issue with RefCell<Storage> is that it represents ownership of the storage. The contract implementation is then free to destroy the storage and never give it back to the caller. It can even disallow the caller to have a read-only reference.


Invalid configuration, please set up your environment

Hi,
I am unable to configure this plugin;
I have these values in my .env file.
CLOUDINARY_URL=cloudinary://XXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXX@cloudname
CLOUDINARY_UPLOAD_PRESET=ml_default
CLOUDINARY_NOTIFICATION_URL=

"Unsigned uploading enabled" is also enabled in the Cloudinary upload preset section.
And in my controller, I have
$uploadedFileUrl = cloudinary()->uploadVideo($request->file('vidfile')->getRealPath())->getSecurePath();
Please let me know what am I missing.

@paramwork Did you publish your config file after installation of the package?

Hey, thanks for the reply.
I forgot to clear the cache that's why it was showing configuration error.  Now it is working correctly. Thanks

I have checked this answer. However I have already configured my .env and I published the configuration after installing the package but it still does not work in my development environment, in my local environment it does work


Finetuning scheduler

Before submitting

[X] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
Discussed as the appropriate implementation of #10197 and I have updated the FinetuningScheduler PR accordingly.
[X] Did you make sure to update the docs?
[X] Did you write any new necessary tests?

What does this PR do?
This PR adds a notebook-based tutorial introducing the FinetuningScheduler callback and demonstrating the use of FinetuningScheduler to finetune a small foundational model. As discussed with PL team lead(s), rather than adding the FinetuningScheduler callback directly to PL core, the preferred pattern moving forward will be to register callbacks via a forthcoming API. Until the new API is available, I've included a mock registry for the FinetuningScheduler callback and noted my callback fork of PL as a requirement below to facilitate evaluation of the new tutorial.
I'm scaling back my original FinetuningScheduler PR  to include only a couple minor changes that enable user-registered modules like the finetuning_scheduler to function.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
 :]

Thanks, done! I've annotated part of the fix for your review

@ethanwharris mind have look? :)

@ethanwharris mind have look? :)

@ethanwharris @Borda  Thanks so much again for your awesome work on the PyTorch Lightning ecosystem projects! I think this tutorial is almost there but wanted to let you know I'm planning to swap out the PL fork dependency for a regular package in pypi for a better user experience. I'm going to port it shortly and have discussed with @tchaton. I'll update this PR and you guys as soon as I'm done but I should be able to get to it in a few days and we might want to avoid merging it until then. Thanks again!

@tchaton @Borda @ethanwharris
Hey guys, just wanted to update you that the packaging of finetuning-scheduler (simplifying the lightning tutorial dependency to just the finetuning-scheduler[examples] extra) is ready,  I'm just holding off publishing the package to pypi for now due to a pypi limitation wrt direct dependencies in requirements.
As soon as the first 1.6 PL release is published to pypi, I'll add PL 1.6 as a minimum dependency for finetuning-scheduler, push it to pypi, update the notebook dependency here to finetuning-scheduler[examples] and the finetuning-scheduler lightning-tutorial should (finally) be ready! 😊🔥🎉
It looks like the team is making great progress towards the 1.6 milestone and I'll be keeping an eye on it to ensure this tutorial is ready to go as soon as it's released. If you guys are interested in the meantime, the finetuning-scheduler RTD documentation is ready to go and I've got the basic CI/CD going for the project (though I still need to get the azure pipelines workflow going since my GPUs have been unavailable for the last week due to my mobo shorting 🤣… finished THAT physical server rebuild last night though).
Thanks again for all your work and continued collaboration, can't wait to get this published and see what's next on the PL horizon!

@ethanwharris ^^ mind have a look :rabbit:

FYI, the transformers pre-release requirement is just required for the next couple days. I've already talked to the Hugging Face team and they indicated that transformers 4.18 will be released in the next few days. Also, as soon as PL 1.6 is officially released, I'll be able to push finetuning-scheduler to pypi and the only requirement will be finetuning-scheduler[examples] directly from pypi! :partying_face: :fireworks:

As transformers v4.18.0 has just been released today, I've just published finetuning-scheduler to pypi and this tutorial now only depends on finetuning-scheduler[examples]!
The only two current test failures I believe are related to outstanding issues unrelated to this tutorial (for the docs, an error in mnist hello world and for the tutorials test a horovod version mismatch error triggered on import of pl).
Thanks again for the tremendous work  (in quality and amount!) on PL itself and these tutorials everyone! I'll be in the woods and have limited availability until 4/12 but please lmk if there's anything else you need from me and I'll be sure to dive into addressing it starting then. Thanks again!

@rohitgr7 could you pls check/review this tutorial? :rabbit:


Update deploy-dynamics-365-finance-operations-solution.md

Updated content hub solution name to "Dynamics 365 Finance and Operations" instead of "Dynamics 365 F&O"

@limwainstein
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#reassign:cwatson-cat

#sign-off

#assign-reviewer:cwatson-cat

#sign-off


fix rbac permit for operator-admin

Description
Correct logic operation on permit for operator-admin RBAC
Issue reference
#6407
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

fyi @artursouza


1.0.2 branch fails to build on VC-32

Hi,
I'm getting a build failure on 1.0.2:
link /nologo /subsystem:console /opt:ref /debug /dll /out:out32dll\libeay32.dll /def:ms/LIBEAY32.def @C:\Users\Build\AppData\Local\Temp\nm432E.tmp
   Creating library out32dll\libeay32.lib and object out32dll\libeay32.exp
ec_asn1.obj : error LNK2019: unresolved external symbol _OSSL_NELEM referenced in function _EC_GROUP_get_basis_type
out32dll\libeay32.dll : fatal error LNK1120: 1 unresolved externals

Full Build Log and List of Changes.
Simon

See #2713 for the solution.  All that remains is having it merged into the 1.0.2 branch

fix merged, sorry for the inconvenience.


Handle CMs & Secrets connected to Pod via volume

Description
Changes proposed in this pull request:

Sooo Pod can be connected not only by pod.spec.containers[*].env, but also by pod.spec.volumes 🤦

Related issue(s)
Closes #1331

/retest

/retest

/retest


Characters should roll after role selection

We bikeshedded this during loadouts and it came up again with nukies.
tl;dr is that job selection should be entirely independent of character and rolled first (same with antags). Once this is done then you should be able to pick which character you want to play.

Completely agree, the good idea of an "antag only" character for what your regular character might be RP opposed to is inexecutable without this as you can't predict what you're going to get

will this give people the option to use clown/mime names? If so, then yes i agree!

will this give people the option to use clown/mime names? If so, then yes i agree! But if this allows players to have specific names for antag roll then i disagree

That just requires adding a field to the RoleLoadout entry for that role which is separate and much easier.

So the concern I have with this is it leading to metagaming and it leaning into "allowed metagaming"
Say I play Daniel Smithson, but Danny Smithson whenever I roll antagonist.
I could have my characters eyes be blood-red whenever I get antagonist.
While I can understand the character progression and interesting roleplay stance on this, I fear that the risks out way the benefits if I am reading the tldr correctly..


Error: (1364, "Field 'file' doesn't have a default value")

Summary
Every time I try to add a new File (as Plugin file from Django CMS) I get the error:
(1364, "Field 'file' doesn't have a default value")
Any suggestion?
Thank you.
Environment

Python version: 2.7.10
Django version: 1.9.12
django CMS version: 3.4.2

Hello @FabrizioA , please make sure to submit questions within the appropriate channels on either the User Mailing List, IRC (freenode#django-cms) or Stackoverflow.
If this is an issue with a third party package like https://github.com/divio/djangocms-file, please create a new ticket there.
You can find additional information on our support page.


Compilation error when running dartpad_ui: Error: The method 'withValues' isn't defined for the class 'Color'.

What happened?
Compilation error when running dartpad_ui: Error: The method 'withValues' isn't defined for the class 'Color'.

'Color' is from 'dart:ui'.

What is this method? I don't recognize it from flutter SDK, is it custom extension?

Steps to reproduce problem
Checkout the code from main, run dart pub get
Try running using flutter run -d chrome --web-browser-flag "--disable-web-security"
Additional info
[✓] Flutter (Channel stable, 3.24.3, on macOS 14.6.1 23G93 darwin-arm64, locale en-PL)
• Flutter version 3.24.3 on channel stable at /Users/bartoszkraszewski/Documents/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 2663184aa7 (11 days ago), 2024-09-11 16:27:48 -0500
• Engine revision 36335019a8
• Dart version 3.5.3
• DevTools version 2.37.3
Machine
Operating system:
OSX
Version:
Sonoma 14.6.1

This is likely due to https://github.com/dart-lang/dart-pad/pull/3056. I'm not sure when color.withValues was introduced; perhaps we now have a dep on a beta channel sdk.

yeah. dartpad_ui depends on sdk: ^3.6.0-0 instead of sdk: ^3.5.4 which is the latest released version of Dart according to the archive page.

well, crap. it looks like from https://github.com/dart-lang/dart-pad/pull/3065 that the beta build of 3.6 is required, so no fix for 3.5.4 would be valid.

I think we generally develop against beta, and would at least need the most recent stable. We do build + deploy the frontend using the main channel currently; I believe changed since we needed the latest latest in order to build w/ WASM.
https://github.com/dart-lang/dart-pad/blob/main/.cloud_build/dart_pad.yaml#L2
We should probably relax that to the beta channel once that's feasible.

I am facing same issue with flutter latest version 3.27.0, where I was getting warnings to update to withValues but after i build for ios it is showing completion error.

when i create new project from android studio it sees this error Error: The method 'withValues' isn't defined for the class 'Color'. - 'Color' is from 'dart:ui'. Try correcting the name to the name of an existing method, or defining a method named 'withValues'. borderPaint..color = Colors.grey.shade300.withValues(alpha: 0.5));

Yes. Changing withValues to withOpacity is working fine.
Note : withValues(alpha : 0.5) must be changed  to withOpacity(0.5)  --> Directly mention the parameter without alpha.


Add support for loginBehavior

Add support for setting the loginBehavior to any of the options specified in FBSDKLoginBehavior enum:

FBSDKLoginBehaviorWeb
FBSDKLoginBehaviorBrowser
FBSDKLoginBehaviorNative
FBSDKLoginBehaviorSystemAccount

by using the loginBehavior prop of FBLogin set to one of the values Web, Browser, Native, or SystemAccount from FBLogin.LoginBehaviors

vmagro could you explain the purpose of this flag in a bit more detail, and maybe provide some examples/update the README along with this change?
Thanks!

Also, is an int the best way to add this as a prop? Maybe we could have a set of string values instead, it'd make the eventual documentation a bit more clear as well.

Sure I can add something to the README or examples, but basically you can change what the button does when you click on it, for example by setting it to Web it'll open a webview for login.
I think an int is the best way to use this prop because it maps directly to the enum FBSDKLoginBehavior whereas if we use strings we would have to have some way to convert a string to an enum value.

Actually I'm not sure where you want this documentation to be, I was going to copy the descriptions of each enum value from https://github.com/facebook/facebook-ios-sdk/blob/master/FBSDKLoginKit/FBSDKLoginKit/FBSDKLoginManager.h#L76,L102
But I'm not sure where it should go

How about a section with examples under the usage
https://github.com/magus/react-native-facebook-login#usage

Any updates on this Vinnie?

Sorry I got super busy. I added some documentation around the change, let me know if you want me to change it

Solid! Thanks for the PR you bumped the minor version to 0.6.0!

Do we have loginBehaviour support in FBLoginManager?

Not at the moment, what do we think the API should be, another argument on login or a 'set' method to set the login behavior? Maybe we should just have set methods for both the behavior and permissions.

Feel free to file a new issue to track this @BasitAli and link this pull #28

Is this functionality available on Android? Searching the code for loginBehavior seems to point to being implemented in iOS only.


Add typescrript support to React Client

Client-side code is written in JS, and although react-script support TS by default, some changes are required.

Change the file extension
Add required types just to make the build successful.

Hi, @muke1908,
I have gone through the project. I can add typescript support to the client side code which is now written in vanilla js.
I want to work on this issue.

@suman313 Sure, go ahead.


Use User ID instead of email for identification

FEATURE REQUEST

Is there an open issue addressing this request? If it does, please add a "+1" reaction to the
existing issue, otherwise proceed to step 2.
No.

Describe the feature you are requesting, as well as the possible use case(s) for it.
As of #1245, User ID is in the response of Identify method. Since we switched to User ID as the main user identification attribute, we should use it whenever we can instead of User email, which we use now.

Indicate the importance of this feature to you (must-have, should-have, nice-to-have).
This is a must-have.

Originally posted by @dusanb94 in https://github.com/mainflux/mainflux/pull/1245#discussion_r512654502

Duplicated issue: https://github.com/mainflux/mainflux/issues/739
Closing this one


Why can't I get this to work in Microsoft Edge or on an iPhone?

Thank you.

This type of question may be better suited for StackOverflow.

It is part of a plugin for mantisbt. Won't work.
Sent from my iPhone
On 1 Mar 2017, at 22:36, Wes Cossick <notifications<EMAIL_ADDRESS>wrote:
This type of question may be better suited for StackOverflow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/NextStepWebs/simplemde-markdown-editor/issues/533#issuecomment-283493907, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHnYsxRHQMfGdwUu96ACJHyuE-71N2bXks5rhfLkgaJpZM4MOHPa.


Move Vega 3 extension

Should the Vega 3 extension move to JupyerLab? If so, how do we handle that Vega 2 and Vega 3 are installed at the same time?

@gnestor Have you had a chance to look into merging the two renderers fro Vega 2 and Vega 3? How soon do we need to get this in to include it in the final release?

I wasn't certain where to best bring this up, but I wonder what it would take to optionally plug vega-tooltips into the vega extensions?
it's a bit awkward, because the tooltip info is not included in the spec, and so there's not really any natural place within the mime repr to specify whether tooltips should be included, and there doesn't appear to be any way for the user to add tooltips to the representation generated within the extension.
Still, I anticipate tooltips will be a common request from users.
Can anyone think of a good way to add tooltips and make them configurable within this rendering?

@tongshuangwu and @neelmohapatra will work with me on building a single renderer that supports both Vega 2 and Vega 3. This can then replace the version we have here and the one in Jupyter Lab.

Dominik - is there a reason to merge the two into one renderer? I am not
opposed to it, but user's don't get anything different right. We would
still switch the rendering on the MIME type right?
On Fri, Feb 23, 2018 at 3:43 PM, Dominik Moritz<EMAIL_ADDRESS>wrote:

@tongshuangwu https://github.com/tongshuangwu and @NeelMohapatra
https://github.com/neelmohapatra will work with me on building a single
renderer that supports both Vega 2 and Vega 3. This can then replace the
version we have here and the one in Jupyter Lab.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterlab/jupyter-renderers/issues/82#issuecomment-368171467,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0JnC1y6yZL8b6CKmp5URgnr86Ljiks5tX00YgaJpZM4RP3A8
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

I thought that might make it easier to support what @gnestor suggested in https://github.com/jupyterlab/jupyter-renderers/issues/82#issuecomment-359889655. I'm going to think about this a bit more. Maybe it makes sense to keep the extension separate to be able to import Vega 2 and Vega-Lite 1 in the vega2 extension and Vega 3 and Vega-Lite 2 in the vega3 extension.
I was wondering what your thought on the supporting new versions in the future are. Do we build a new extension every time a new Version of Vega or Vega-Lite comes out?

You're right @ellisonbg it probably doesn't make sense to merge the extensions. I'm still curious about how future versions should be handled.

It all depends on if we want users to be able to install multiple versions
simultaneously. If we don't, we could just have a single package whose
version and vl/vg versions evolve naturally. I think this current
transition is a bit unique because it has taken us a while to get the
python bindings in place.
On Fri, Feb 23, 2018 at 11:19 PM, Dominik Moritz<EMAIL_ADDRESS>wrote:

You're right @ellisonbg https://github.com/ellisonbg it probably
doesn't make sense to merge the extensions. I'm still curious about how
future versions should be handled.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterlab/jupyter-renderers/issues/82#issuecomment-368207217,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABr0MhnRfe3PyHSjEoIil_Il8lHKIL3ks5tX7f3gaJpZM4RP3A8
.

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

It would be nice if folks don’t have to install anything. E.g., once Vega 4 is out, it would be great if one could still just open a notebook with a Vega 3 plot in jupyterlab without having to install anything new like a Vega3 extension.

@davidanthoff Working on it. That's definitely the goal.

Since rank does not support functions yet, I moved ahead and copied the extension over into jupterlab in https://github.com/jupyterlab/jupyterlab/pull/3377. Unfortunately, I encountered a blocking issue.

related: jupyterlab/jupyterlab#3702
Yes, I've encountered the same problem when I looked into it earlier today. If it were supported, I would expect the ranking function to look like this:
import schemaParser from 'vega-schema-url-parser';

const extension: IRenderMime.IExtension = {
  id: '@jupyterlab/vega3-extension:factory',
  rendererFactory,
  /**
   * A ranking function for auto generating the rendering.
   * Considered factors (prority high -> low):
   *  1. the schema inside the file
   *  2. user selected mode
   *  ?? Not sure how to get the file extension yet. (.vl.json)
   */
  rank: (model: IRenderMime.IMimeModel): number => {
    // file name???
    // user selected model
    const user_select_mode: Mode = this._mimeType === VEGA_MIME_TYPE ? 'vega' : 'vega-lite';
    // get the data
    const data = model.data[this._mimeType] as JSONObject;
    // parse the schema to get library and version
    // version is available if needed
    const schema_library = schemaParser(data['$schema'] as string).library;
    const schema_mode: Mode = schema_library === 'vega' || schema_library === 'vega-lite' ? schema_library : undefined;

    // prioritize.
    let schema: Mode;
    if (schema_mode) {
      schema = schema_mode;
    } else if (user_select_mode){
      schema = user_select_mode;
    } else {
      schema = 'vega';
    }
    return schema === 'vega' ? 0 : 1;
  },
 ...

https://github.com/jupyterlab/jupyterlab/pull/3377 works mostly but @tongshuangwu and I are super confused about the semantics of rank. We get very inconsistent behavior and would love some help from you. @gnestor @ellisonbg we're on slack

@domoritz When @blink1073 says:

This sounds like a good idea for tie-breaking.

I think he means that if 2 extensions both have rank 0, then the winner (default renderer for a mime type or file extension) is determined by the extension that is loaded last. I don't understand what determines extension loader order, but I'm sure there are edge cases where it produces unexpected behavior.

Hmm, if you look at https://github.com/jupyterlab/jupyterlab/pull/3377/files, you can see that the ranks are 50 and 60. Not sure what's going on there.

The rank is used for mime bundles only; it does not apply to documents.  For documents, we use file types and defaultFor to determine who should open a document.

@tongshuangwu I looked more into what it would take to enable a rank function for rendermime extensions: https://github.com/jupyterlab/jupyterlab/issues/3702#issuecomment-368704366

Ok, vega3-extension has been replaced with vega2-extension in  this repo. Now we're just waiting on https://github.com/jupyterlab/jupyterlab/pull/4107 to replace vega2-extension wit vega3-extension in jupyterlab.

🎉


Use ApplicationAwareTrait in all ApplicationAwareInterface classes

Let's avoid duplicated code...

Very nice, thank you!