new nuxt install with windcss ui , yarn build back crash..

Versions

nuxt:  2.15.3
node: 14

Steps to reproduce
yarn create nuxt-app someone
add Wind CSS ui-framework
yarn build
What is Expected?
FATAL  Nuxt build error                                                                                17:41:41
at WebpackBundler.webpackCompile (node_modules/@nuxt/webpack/dist/webpack.js:2127:21)
at processTicksAndRejections (node:internal/process/task_queues:94:5)
at async WebpackBundler.build (node_modules/@nuxt/webpack/dist/webpack.js:2076:5)
at async Builder.build (node_modules/@nuxt/builder/dist/builder.js:327:5)
at async Object.run (node_modules/@nuxt/cli/dist/cli-build.js:110:7)
at async NuxtCommand.run (node_modules/@nuxt/cli/dist/cli-index.js:413:7)
╭─────────────────────────────╮
│                             │
│   ✖ Nuxt Fatal Error        │
│                             │
│   Error: Nuxt build error   │
│                             │
╰─────────────────────────────╯
What is actually happening?
after new install nuxt with wind css and when try yarn build we have crash...

It cause 0.4.5 nuxt-windicss-module. Please use 0.4.4

Hey, this one is a windi issue. You can close this issue here as it's sorted in that repo anyway.
See: https://github.com/windicss/nuxt-windicss-module/issues/28 https://github.com/windicss/nuxt-windicss-module/issues/29


k3s --disable-agent flag never starts kube-scheduler in newer k3s versions

Environmental Info:
K3s Version:
k3s version v1.22.6+k3s1 (https://github.com/k3s-io/k3s/commit/3228d9cb9a4727d48f60de4f1ab472f7c50df904)
go version go1.16.10

Node(s) CPU architecture, OS, and Version:
Linux test-0 5.10.76-linuxkit #1 SMP Mon Nov 8 10:21:19 UTC 2021 x86_64 GNU/Linux

Cluster Configuration:
container k3s, single server, no agents

Describe the bug:
Hello! Thanks again a lot for the great project! This is a problem related to using --disable-agent with k3s.
The PR #4345 changed that the kube scheduler is only started if the nodeConfig in the embedded executer is set, which never happens, because the agent is never started, which in turn leads to kube-scheduler never starting.
You can see the problematic code at:
https://github.com/k3s-io/k3s/blob/feb6feeaeccc857a5744ef10efd82b18e8790e78/pkg/daemons/executor/embed.go#L113-L124
And the agent bootstrap that is skipped at:
https://github.com/k3s-io/k3s/blob/bb856c67dcd9063ca68691a3321a458f2663d71d/pkg/cli/server/server.go#L451-L455
I know --disable-agent its an unsupported flag, but since we are relying on it for correct functionality in vcluster, I hope you could consider fixing this as it has worked before and it would be in my opinion a minimal non-invasive change to k3s. If you decide to go forward with this change, I'm willing to submit a PR that fixes this as well.
Steps To Reproduce:
Specify the --disable-agent flag and notice kube-scheduler is never getting started
Expected behavior:
Kube scheduler starting up if --disable-agent is set to true.
Actual behavior:
Kube scheduler never starting up

@brandond thanks for the reply! Currently we use the scheduler of the underlying host cluster to decide where a pod should be scheduled on and then sync back the node into the virtual k3s cluster.
In an effort to allow users to taint and label nodes within the virtual cluster, we actually want to enable the scheduler inside the virtual k3s cluster, let it decide on which node a pod should be scheduled on and then create the pod in the underlying host cluster bound to the scheduled node already.
This works because we sync the nodes from the host cluster into the virtual one by creating the node objects in there without actually installing a separate kubelet or kube proxy on them, which is why we don't need the agent of k3s at all. Rather we only need the control plane part (kube api server, storage, controller manager and scheduler) which is virtualized completely in vcluster and works like in a normal Kubernetes cluster, while the workloads will then be executed on the host cluster nodes.

@brandond but this condition will never be true if you use --disable-agent will it as the agent is never started and this will never be non nil:
https://github.com/k3s-io/k3s/blob/feb6feeaeccc857a5744ef10efd82b18e8790e78/pkg/daemons/executor/embed.go#L113-L116

Ahh, I see. Sorry, I'd missed that part; I thought it was just waiting on a node to show up.

See if that PR fixes it for you?

@brandond thanks a lot for the quick PR! It works for me without running k3s in an unprivileged docker container, but if I run k3s inside a container I get the following errors:
INFO[0091] Waiting to retrieve agent configuration; server is not ready: "overlayfs" snapshotter cannot be enabled for "/data/agent/containerd", try using "fuse-overlayfs" or "native": failed to mount overlay: operation not permitted

Seems like the problem is this part here that is now executed to retrieve the agent node config:
https://github.com/k3s-io/k3s/blob/bb856c67dcd9063ca68691a3321a458f2663d71d/pkg/agent/config/config.go#L440-L459
I'm no expert here, but wouldn't it be much easier to use the kube scheduler kube config here instead of the agent config? Or is the node kube config strictly required?
I though about something like this:
func (e *Embedded) Scheduler(ctx context.Context, disableCCM bool, apiReady <-chan struct{}, args []string) error {
	command := sapp.NewSchedulerCommand()
	command.SetArgs(args)

	go func() {
		<-apiReady
		// If we're running the embedded cloud controller, wait for it to untaint at least one
		// node (usually, the local node) before starting the scheduler to ensure that it
		// finds a node that is ready to run pods during its initial scheduling loop.
		if !disableCCM {
			kubeconfig := ""
			for _, arg := range args {
				if strings.HasPrefix(arg, "--kubeconfig") {
					kubeconfig = arg[len("--kubeconfig"):]
					break
				}
			}
			if kubeconfig != "" {
				if err := waitForUntaintedNode(ctx, kubeconfig); err != nil {
					logrus.Fatalf("failed to wait for untained node: %v", err)
				}
			}
		}
		defer func() {
			if err := recover(); err != nil {
				logrus.Fatalf("scheduler panic: %v", err)
			}
		}()
		logrus.Fatalf("scheduler exited: %v", command.ExecuteContext(ctx))
	}()

	return nil
}

I was hoping to avoid having to pass that in explicitly since the nodeconfig already has all the various bits of information we need filled in properly, if we properly bootstrap the executor before using it.

Should be sorted now; I am able to run the server in an unprivileged container. Even rootless should work, if you give it a writable path:
docker run --rm -it --user 1000:1000 -e HOME=/tmp/k3s rancher/k3s server --disable-agent --token=token --rootless

Validated on  v1.23.5-rc1+k3s1
Installed node1 passing --disable-agent
$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE
kube-system   helm-install-traefik-crd-xjkjh            0/1     Pending   0          7m17s
kube-system   helm-install-traefik-4nrvz                0/1     Pending   0          7m17s
kube-system   local-path-provisioner-6c79684f77-c97zn   0/1     Pending   0          7m17s
kube-system   metrics-server-7cd5fcb6b7-gcjdr           0/1     Pending   0          7m17s
kube-system   coredns-d76bd69b-p86fc                    0/1     Pending   0          7m17s

Joined an agent node
$ kubectl get nodes
NAME               STATUS   ROLES    AGE     VERSION
ip-172-31-15-177   Ready    <none>   6m44s   v1.23.5-rc1+k3s1
$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS      RESTARTS   AGE
kube-system   coredns-d76bd69b-p86fc                    1/1     Running     0          12m
kube-system   local-path-provisioner-6c79684f77-c97zn   1/1     Running     0          12m
kube-system   helm-install-traefik-crd-xjkjh            0/1     Completed   0          12m
kube-system   helm-install-traefik-4nrvz                0/1     Completed   1          12m
kube-system   svclb-traefik-fxbth                       2/2     Running     0          4m13s
kube-system   metrics-server-7cd5fcb6b7-gcjdr           1/1     Running     0          12m
kube-system   traefik-58b759688b-zjx4j                  1/1     Running     0          4m13s

Metrics server fails to fetch metrics in the above setup as shared in the issue https://github.com/k3s-io/k3s/issues/5330


Merchant stall / product not showing up in search

Using LNbits I installed the Nostr Market plugin and follwed all the steps to make a merchant stall and product (socks).
How do I get it to populate in a search or have a link to it or have it show up in nostr?

How do I get it to populate in a search or have a link to it or have it show up in nostr?

the market client can be accessed as described here: https://github.com/lnbits/nostrmarket#diagon-alley-clients
then add the public key of your merchant:

How to add nostrclient?  I see it under the "installed" tab of "manage extensions" but not in my side bar. It doesn't show up in the "extensions" area

Installed means they are enabled for the users of your lnbits but not nessecarily activated for the superuser wallet yet. To activate them you need to go to extensions -> find nostr client -> set enable

nostr client isn't in the extensions

nostr client isn't in the extensions

It is under manage exstensions - installed. But on Legend its an admin-Exstension and you cannot use it to make relays there. Youll need your own lnbits. https://legend.lnbits.com/install?usr=840c08e56e5b48a99a502f52e02d2df4

@sirsatsalot I have updated the nostrmarket documentation. I hope it helps.

Prerequisites: https://github.com/lnbits/nostrmarket/blob/main/README.md#prerequisites

make sure nostrclient works as expected

Troubleshoot: https://github.com/lnbits/nostrmarket/blob/main/README.md#troubleshoot

trying to fix the connection with Nostr

Client: https://github.com/lnbits/nostrmarket/blob/main/README.md#diagon-alley-clients

make sure the merchant public key is correctly configured

@sirsatsalot can we close this issue? Are you still experiencing problems?


DRILL-6486: BitVector split and transfer does not work correctly for non byte-multiple transfer lengths

Fix for the bug in BitVector splitAndTransfer. The logic for handling copy of last-n bits was incorrect for none byte-multiple transfer lengths. This PR fixes this problem and adds new tests which simulate the failing condition and also exercise other changes in this PR.

@bitblender  Thank you for fixing the bug in this complex code. I have only few variable naming comments. LGTM.

Have we considered replacing BitVector with UINT1 vector? This swap was done in most places in Drill before 1.0, probably because BitVector was buggy and slow. Perhaps we should just remove it from the remaining places?
Or, if we get it to work, consider using it where it was originally intended, as the "bits vector" in Nullable types? If we do that, we have cross-version compatibility to worry about with old clients...

@paul-rogers  I have opened https://issues.apache.org/jira/browse/DRILL-6493 to follow up on your suggestion. Until that gets prioritized and completed, the changes in this PR will be necessary to make sure that BitVector splitAndTranfer() works correctly.

+1 LGTM Thanks for adding thorough unit tests.

@sohami I have fixed the last-byte issue. I removed the bounds check because some of the operators are hitting the IOB, most likely because they are not setting valueCount correctly. Those issues are best fixed in a different PR, so I am removing that check.

Yes.
On June 21, 2018 at 10:25:44 AM, Pritesh Maker (notifications<EMAIL_ADDRESS>wrote:
@bitblenderhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_bitblender&d=DwMCaQ&c=cskdkSMqhcnjZxdQVpwTXg&r=HlugibuI4IVjs-VMnFvNTcaBtEaDDqE4Ya96cugWqJ8&m=hlQMTw-fCidZaB1T0_96G3hUXi6jCqarmxAWz-qfT2M&s=sTmHTnIdq5BE9dp8wuPzCyuLG4B7r8-xKX4p4f8_LX4&e= would you be able to address the remaining review comments in time for the batch commit this week?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_drill_pull_1316-23issuecomment-2D399181499&d=DwMCaQ&c=cskdkSMqhcnjZxdQVpwTXg&r=HlugibuI4IVjs-VMnFvNTcaBtEaDDqE4Ya96cugWqJ8&m=hlQMTw-fCidZaB1T0_96G3hUXi6jCqarmxAWz-qfT2M&s=w5EwdGqBkcsdB82V-FqvQSzMI1lutQexIbn2o3Wzz3I&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AAaRheMUQN2UBlKgAmUXv-5FNL5bEKqCduks5t-2D9cMgaJpZM4UjZUK&d=DwMCaQ&c=cskdkSMqhcnjZxdQVpwTXg&r=HlugibuI4IVjs-VMnFvNTcaBtEaDDqE4Ya96cugWqJ8&m=hlQMTw-fCidZaB1T0_96G3hUXi6jCqarmxAWz-qfT2M&s=H9fTIsEBO8FfUfHLXSXC7a_zimEsw_LeVQIt3JHmZec&e=.

@sohami  Addressed all your review comments. Please take a look again.


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
The 1.21.x versions of the GoLang.Go package are missing the ARM64 installer and only have the x64 installer. This is a regression compared to the 1.20.x versions of the package.
The ARM64 versions are available upstream for 1.21.x, see e.g., https://go.dev/dl/go1.21.1.windows-arm64.msi.
Steps to reproduce
Install with winget install GoLang.Go on a Windows ARM64 device and observe that the x64 version is installed.
Actual behavior
Only the x64 version appears in the manifest and the x64 version is installed.
Expected behavior
The ARM64 version should also appear in the manifest and be installed on ARM64 devices.
Environment
C:\>winget --info
Windows Package Manager v1.5.2201
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22621.2134
System Architecture: Arm64
Package: Microsoft.DesktopAppInstaller v1.20.2201.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Screenshots and Logs
No response

Related to https://github.com/microsoft/winget-pkgs/issues/92688


States we're already in containers, when we're not

Changed the wording a little at the beginning that states that our tye app is already in containers. This isn't true, as the next step generates the images for the first time.
I'm not married to the new wording, feel free to suggest/edit if the voice is wrong.

Thanks


storage: Use the same flags that VDSM uses for converting image

Bug-Url: https://bugzilla.redhat.com/1828888
Signed-off-by: Asaf Rachmani<EMAIL_ADDRESS>

@nirs can you please review?


Request for the trained model

Hello there, author! Can you send me the segmentation model on brats2020 dataset? My email address is<EMAIL_ADDRESS>Thank you very much!

链接: https://pan.baidu.com/s/15X8N_7VdyoXzkjkORa4Skw?pwd=i4by 提取码: i4by
This model is trained on brats2020 dataset. I totally run 150epoches. You can try it. Thank you for your attention.

作者您好！您提供得百度网盘链接已失效，请问您是否能再次分享一下您的模型，谢谢！ @ge-xing

链接: https://pan.baidu.com/s/1zCdMeJKQ9KCVQVPoSaSZOQ?pwd=31pw 提取码: 31pw
--来自百度网盘超级会员v8的分享


Add section about recommend (and not) environments

In this comment, blueyed suggests that pytest-sugar is not recommended for use in production environments. This change makes that recommendation explicit so that downstream projects can reference this recommendation.

Codecov Report

Merging #164 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #164   +/-   ##
=======================================
  Coverage   87.44%   87.44%
=======================================
  Files           2        2
  Lines         478      478
  Branches       85       85
=======================================
  Hits          418      418
  Misses         35       35
  Partials       25       25

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 2764da4...06816c3. Read the comment docs.

I'm glad to hear that adding pytest-sugar to the CI isn't recommended against.

Just pin your dependencies.

I don't think that's as simple as those four words seem to imply. Pinning dependencies adds technical debt, and for someone like myself that maintains over a hundred packages (and that's just the open-source ones), the cost of maintaining pins is usually higher than the costs of dealing with emergent issues on a selective basis.
But I should acknowledge that I was unfair in my handling of this issue - I became frustrated when the fix was finally accepted but a release was not made (leaving the defect in the wild). I did not realize that an additional mention was what was needed to raise the attention of the maintainer. After that, a release was made promptly.
So I'll withdraw this PR. Thanks for the great package.


How to set gpu card for the demo project running

I  use  os.environ["CUDA_VISIBLE_DEVICES"] = "4" or env  to run demo.py, always default use 0, How can i use other gpu card, Is there any i can manully set it?

CUDA_VISIBLE_DEVICES=4 python demo_textmonkey.py -c model_path
Maybe you can add "CUDA_VISIBLE_DEVICES=4".

device_map="cuda:4"

input_ids=input_ids.to("cuda:4"),
attention_mask=attention_mask.to("cuda:4"),
Alternatively, you can modify the code here.

The first way not change too.
The second way  demo can no start ,rasie error

Is your GPU functioning properly? Can you run other models on "cuda:4"? I don't think this is an issue with our code.

It works, many thinks.


Fix the go.mod

Signed-off-by: Gary Brown<EMAIL_ADDRESS>

When building, it causes the go.mod file to be modified. Ideally we need a PR check that makes sure any changes to the go.mod file have been committed.


Add network connection button

To do:

Enable users to easily switch network between the buildnet and the mainnet.
When users change network, refresh the page and update the info.

in the code we know thanks to a env var that we are in buildnet or mainnet. So we can fetch the selected network in the wallet (station or bearby) via wallet provider and show to the user a warning if the network of the deployed version is not the same of the one of the connected wallet.


push nuget ibrary to "MaterialDesignThemes.MahApps"

This is a great library and now I'm using it.
However it seems only "MaterialDesignThemes.WPF" is pushed to Nuget library.
I'd like to also use "MaterialDesignThemes.MahApps" from nuget.

...yes...this will happen...i want to put something in it first...
Keep the faith :wink:

https://www.nuget.org/packages/MaterialDesignThemes.MahApps


MDC 31

This week on MDC, nice and easy!

Card: Add Primary action element
Chips: Leading and Trailing icons

Fixed with #151


Locking step fails with "Error: No available tap homebrew/core." if homebrew/core isn't tapped.

Bundling fails in lockfile generation when using brew 4 with homebrew/core untapped.
Steps:

brew update to 4.0 or later.
brew untap homebrew/core
brew bundle

Expected behavior: Homebrew completes the bundling process.
Actual behavior: Homebrew goes through the bundling process but fails in locking, reporting "Error: No available tap homebrew/core."
Notes:

It looks like Bundle::Locker#system_macos's interaction with CoreTap assumes homebrew/core is tapped.
Running brew bundle --no-lock succeeds.
Removing the "Homebrew/homebrew-core" => CoreTap.instance.git_head, line from Bundle::Locker#system_macos allows the bundle to proceed for this case, but presumably would do the wrong thing if homebrew/core is tapped.

I'm not able to reproduce this immediately.
I'm on HOMEBREW_VERSION: 4.0.1-58-g82a36d2 on Linux (Debian 11.6) and just today updated to 4.x and untapped homebrew/core. I'm able to run brew bundle with a variety of Brewfiles I have laying around.
Can you provide the output of:

brew config
brew doctor

I just caught that I have lockfiles disabled on this machine. I'm able to reproduce it now.
unset HOMEBREW_BUNDLE_NO_LOCK; brew bundle --file=Brewfile.all
Using colindean/personal
Using bash
Using bash-completion@2
Using bat
Using git-delta
Using coreutils
Using eoconv
Using fzf
Using zoxide
Error: No available tap homebrew/core.

The quick workaround is to use --no-lock or set export HOMEBREW_BUNDLE_NO_LOCK=1.


fix: allow globals in format strings

Description
Problem
Resolves #6372
Summary
Additional Context
Documentation
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I'm wondering... is there a reason not to support full expressions in format strings, like, say, in Ruby? I know full expressions aren't supported in format strings in Rust, but I never understood why.


refactor - move from macro to shapeless

The incentive is rather philosophical
1, macro should remain low-level and exists at the lower level libraries such as shapeless.
2, we should use each other's libraries more.

happy to help you write this! My talk at Scala eXchange last week should make this real easy. I predict you could do the whole thing in about 50 lines of code, and also support sealed traits.

That will be fantastic!  I bet you can write it much better than us.

well I didn't say I'd write it, but I'd be happy to show you how :smile: When my shapeless talk is out, I'll link you and then give you guidance on the example, then you can graduate to rewriting ficus. Ping me in a few weeks if I don't come back.

That's still very nice of you. Looking forward to your talk!

enjoy! https://twitter.com/fommil/status/678195060429705216

Thank you @fommil , I enjoyed your talk. The explanation of that several weird things shapeless has to do to overcome Scala compiler's defects can be immensely helpful for new comers to typelevel projects. I suggest shapeless have a section on these issues in documentation.

Travis Brown has done some recent work to support different cases in Circe. Since it uses Shapeless for derivation, it might be a good reference.

yup, but the shapeless for mortals talk is still probably a better learning experience. Travis was in the front row, btw :wink:

any movement on this?

@fommil I made some progress but not there yet. I am trying to build a library that can "read" any runtime structured data (Map[String, Any], Typesafe Config, Json AST, etc) into any case classes. I am still couple of days away from knowing if I can pull that one out yet.

@kailuowang I hope you've watched the talk ? Please don't make this library do any more than typesafe's config. There are already libraries to do the others.

Sam, I watched the talk. I am don't plan to make this library doing any
more than typesafe config. The thing I was talking about is a different
project.
On Wed, Jan 27, 2016 at 10:18 AM Sam Halliday<EMAIL_ADDRESS>wrote:

@kailuowang https://github.com/kailuowang I hope you've watched the
talk ? Please don't make this library do any more than typesafe's config.
There are already libraries to do the others.
—
Reply to this email directly or view it on GitHub
https://github.com/iheartradio/ficus/issues/5#issuecomment-175683885.

cool! Hope it helped :smile:

May be if it will interesting I did simple implementation on shapeless: https://github.com/andr83/scalaconfig

This library has a slightly wider scope than product/coproduct hierarchies. Trait, class, and enumeration support may have to be dropped or remain as is. Also, if compilation speed is affected, I don't see any immediate benefit for users.

I thought this issue discuss refactoring to shapeless and decide to share my implementation. Regarding this do not see any compilation speed trouble before start use case classes with hundreds of fields. Yes my solution do not support traits with apply factories and enumeration but classes and custom readers are supporting. If missing features important for someone I will implement it.

I didn't meant to target your comment. It simply brought the issue to my attention again, and I was voicing my opinion on the general topic.

@andr83 great! What license are you going to use?

@joprice sorry for my confusion - our comments were close by time after a big delay in this topic )
@fommil it's publishing by MIT license. You can see it on project github page. Any suggestions are welcome )

Apache 2.0 is better than MIT because it covers a lot of things MIT never considered but you almost certainly want if you want to go the permissive route. If you want the software to always be libre, then I recommend MPL or LGPL. I did a talk about this somewhere that you could find by googling my name and scalasphere

@fommil I'm agree with you on 100%. But exactly about this library I have no worries for any usage so MIT fit it well. Of course for other projects which I want to protect I will use more suitable license.

Still, Apache 2.0 is an upgrade on MIT and is the license preferred by shapeless :-)

please do not move to shapeless ... ficus is a great alternative to pureconfig (already based on shapeless) which is clashing with sparks old 2.0.0. version of shapeless for spark version of 2.1.0 https://stackoverflow.com/questions/47730585/shapeless-shading-in-spark-not-working-method-still-not-found


Added List Name and Find Commands

Close #99

Codecov Report

Merging #100 (d285a03) into master (05c8366) will decrease coverage by 3.81%.
The diff coverage is 90.90%.

@@             Coverage Diff              @@
##             master     #100      +/-   ##
============================================
- Coverage     67.94%   64.12%   -3.82%
- Complexity      524      571      +47
============================================
  Files            91      104      +13
  Lines          1641     1879     +238
  Branches        171      188      +17
============================================
+ Hits           1115     1205      +90
- Misses          474      616     +142
- Partials         52       58       +6

Impacted Files
Coverage Δ

...seedu/address/logic/commands/list/ListCommand.java
80.00% <ø> (ø)

src/main/java/seedu/address/ui/CommandBox.java
0.00% <0.00%> (ø)

...u/address/logic/commands/list/ListNameCommand.java
90.00% <90.00%> (ø)

...java/seedu/address/logic/commands/FindCommand.java
90.00% <100.00%> (-10.00%)
:arrow_down:

...ain/java/seedu/address/logic/parser/CliSyntax.java
91.66% <100.00%> (+0.75%)
:arrow_up:

.../seedu/address/logic/parser/FindCommandParser.java
100.00% <100.00%> (ø)

.../seedu/address/logic/parser/ListCommandParser.java
87.50% <100.00%> (+22.28%)
:arrow_up:

...du/address/logic/parser/ListNameCommandParser.java
100.00% <100.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
97.29% <100.00%> (+0.52%)
:arrow_up:

...model/task/NameOrTagContainsKeywordsPredicate.java
100.00% <100.00%> (ø)

... and 28 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


POC @ https://docs.microsoft.com/en-us/azure/azure-sql/database/ledger-overview

Out of scope, closing


Fix goroutine leaks

http.Client goroutines were kept idle after flow node's PEF endpoint discovery.
grpc.ClientConn not closed in the retry logic.

@tomasger tests failing?

@tomasger tests failing?

@cosmix indeed. Does not seem like an indication of an issue, just a nil dereference in a test of a different package when I added a method call to a struct that wasn't initialized on that test. I'll aim to solve, merge, and release today.

@tomasger great, thank you!


Documentation - Clean up the Reference > Pages sub-pages to be only about Page models

Pertinent section of the Wagtail docs

https://docs.wagtail.org/en/stable/reference/pages/index.html

Details

Within the Reference section of our documentation, we have a sub-page called Pages. This contains the 'Model reference' and 'Panel types' documentation, however, these are not specific to the Page models.
I have found it confusing but have kind of gotten used to it, but from a newcomer perspective it feels odd. Panels are now fully supported across Snippets and Pages, the Model reference page has all models (not just pages).
There are a few other changes that would make this 'Reference > Pages' section a bit more consistent and predictable.

Proposed changes

Move Panel types directly under Reference.
Move Model Reference directly under Reference.
Update the title of Model Reference to Model reference (lower case r, as this is the way most page titles are capitalised and Reference is not a proper noun.
Split the tagging section from Recipes out to a new page called Tags to directly under Advanced topics called Tags.
Fix the incorrect heading level nesting in Recipes for the 'adding endpoints with custom route methods, it should be the same level as 'overriding the serve method' not one under it.
Minor update to the text wagtail.models to use double backticks so that it appears highlighted as code. See https://github.com/wagtail/wagtail/blob/105338d0d63c5a8adf285d3c077a922f53a15d02/wagtail/models/init.py#L2 (we may also want to fix up the other backtick usage in that docstring to be double backticks)  * See https://github.com/wagtail/wagtail/blob/105338d0d63c5a8adf285d3c077a922f53a15d02/wagtail/models/init.py#L331C16-L331C31 for an example of the double backticks being used correctly to style as pre/code in the published docs.

Working on this

Feel free to cover items 1-3 as a stand-alone PR, it may make reviews easier.
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

Hi @lb-
Could you please review my PR and suggest me if any changes are required?

@Srishti-j18 there’s no need to @-mention reviewers, please wait for people to get to pull requests on their own schedule.

Thanks @Srishti-j18 I've added a review to one of them.

Hi @lb- - just saw (via #12438) that the "wagtail.models is split into submodules for maintainability..." text now appears on the model reference page. This is actually guidance for Wagtail developers working on the wagtail.models module, so isn't really appropriate to be surfaced on documentation about using the code. (In hindsight, it should probably have been a plain code comment rather than a docstring...)

Hmm good point, I will raise an issue about that - should we try to fix for 6.3? (it's there currently, but not sure how long it's been like that).
https://docs.wagtail.org/en/stable/reference/pages/model_reference.html

@gasman

It's been the case since 2.14 it seems...

https://docs.wagtail.org/en/v2.14.2/reference/pages/model_reference.html
https://docs.wagtail.org/en/v2.13.5/reference/pages/model_reference.html

I've added a redirect on the RTD dashboard for this. See:

https://docs.wagtail.org/en/latest/reference/pages/model_reference.html
Should redirect to https://docs.wagtail.org/en/latest/reference/models.html
Older version(s) should still be under the old URL: https://docs.wagtail.org/en/stable/reference/pages/model_reference.html

It's been the case since 2.14 it seems...

https://docs.wagtail.org/en/v2.14.2/reference/pages/model_reference.html
https://docs.wagtail.org/en/v2.13.5/reference/pages/model_reference.html

Ah, hadn't realised this was a long running issue! Definitely doesn't need to be fixed for 6.3 then.
(Thanks for sorting the redirects, @laymonage!)

@gasman  @laymonage  - PR up for the code modules reference text fix.
https://github.com/wagtail/wagtail/pull/12485


Getting error when trying to access office installed in Windows server core container via C# code

We are trying to dockerize the .NET core application which uses Microsoft Visio for generating diagrams. We are generating diagrams by using the interop library for Visio via C# code.
Our app works great if we are using a Windows client machine docker image, but when we try to use a Windows Server Core container image, we are getting the below error
Retrieving the COM class factory for component with CLSID {00021A20-0000-0000-C000-000000000046} failed due to the following error: 800706d9 There are no more endpoints available from the endpoint mapper. (0x800706D9)
May I know what could be the issue!? Do I need to enable any windows service to get it working!?

This is because the API surface on the Server Core and Nano Server images are smaller than the Windows or Server images. Most likely, the component your app is trying to use is not present on those images.
The other thing is that Microsoft Office components are not supported on Windows containers, although they might work.

Hi @vrapolinario , Thanks for the reply. I understand that the API surface on the server core image is limited compared to others.
Based on the above error, can we find the missing module and install it as part of the docker on top of the Windows server core image?
We really want to avoid using full-blown windows client machine as it's too big, that's why we are checking with windows server core image!

Any updates on this!?

it may be out of context but did you try using aks edge ?
https://learn.microsoft.com/en-US/azure/aks/hybrid/aks-edge-overview


TextField accented word writing problem using soft keyboard on some iPad

Steps to Reproduce

Create a project with the sample code attached below.
flutter run with iPad 12.9(ios 14.6)
Change keyboard and type below

keyboard
French
Spanish

Type
`a / ˆa
´a / ¨a

Expected results
à / â
á / ä

Actual results
`à / ˆâ
´á / ¨ä

video

Sample code
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Padding(
          padding: const EdgeInsets.all(32),
          child: Column(
            crossAxisAlignment: CrossAxisAlignment.center,
            mainAxisAlignment: MainAxisAlignment.center,
            children: [
              TextField(),
            ],
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel unknown, 2.2.2, on macOS 11.3.1 20E241 darwin-x64, locale ko-KR)
    • Flutter version 2.2.2 at /Users/nero/Project/FlutterContribution/flutter
    • Framework revision d79295af24 (7 weeks ago), 2021-06-11 08:56:01 -0700
    • Engine revision 91c9fc8fe0
    • Dart version 2.13.3

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/nero/Library/Android/sdk
    • Platform android-30, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.58.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.24.0

[✓] Connected device (3 available)
    • nero의 iPad (mobile) • 00008027-000A41CE0C0A402E                • ios            • iOS 14.6
    • Nero (mobile)       •<PHONE_NUMBER>6efd7b29d022582b18bb17ab9f9d92 • ios            • iOS 14.4.1
    • Chrome (web)        • chrome                                   • web-javascript • Google Chrome 92.0.4515.107

• No issues found!

List of devices that have identified problems

device
OS Version
Keyboard
issue

iPad Pro(12.9) 4th generation
iOS 14.6
soft keyboard
✅

iPad air 4th generation
iOS 14.5
inote x-key 38bt bluetooth keyboard
✅

Similar Issues

https://github.com/flutter/flutter/issues/59541

Hi @nero-angela
Thanks for fling the issue,
External keyboard issues like same as https://github.com/flutter/flutter/issues/59541
However I tried the soft keyboard, the result looks expected (PS, I am not too familiar with accented words)
Please this video, let me know if I missed something
https://user-images.githubusercontent.com/48603081/127508495-f5dbfe00-77bb-4fdb-a1c3-7cd185bc7820.mov

minimal code sample
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Padding(
          padding: const EdgeInsets.all(32),
          child: Column(
            crossAxisAlignment: CrossAxisAlignment.center,
            mainAxisAlignment: MainAxisAlignment.center,
            children: [
              TextField(

               style: TextStyle(
                 fontSize: 32,
               ),
              ),
            ],
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.3, on macOS 12.0 21A5294g darwin-x64, locale
    en-GB)
    • Flutter version 2.2.3 at /Users/tahatesser/Code/flutter_stable
    • Framework revision f4abaa0735 (4 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/tahatesser/Code/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/SDK
    • Java binary at: /Users/tahatesser/Code/openjdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (AdoptOpenJDK)(build
      1.8.0_292-b10)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode-beta.app/Contents/Developer
    • Xcode 13.0, Build version 13A5201i
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] VS Code (version 1.58.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.24.0

[✓] Connected device (3 available)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E • ios            • iOS
      15.0
    • macOS (desktop)      • macos                     • darwin-x64     • macOS
      12.0 21A5294g darwin-x64
    • Chrome (web)         • chrome                    • web-javascript • Google
      Chrome 92.0.4515.107

! Doctor found issues in 1 category.

Hi @TahaTesser
I tested the iPad Air 4th generation, and there was no problem as your video.
However, the iPad Pro 12.9 inch 4th generation has a different soft keyboard than the iPad Air, which causes a problem.
Added french soft keyboard screenshots for iPad Pro 12.9 inch 4th generation and iPad Air 4th generation.

iPad Pro 12.9 inch 4th generation
iPad Air 4th generation

Hi @nero-angela
Thanks for the confirmation!

Could this have something to do with the IME keyboard language selection in the settings menu? What happens if you select "Add New Keyboard" -> "French (France)" from the keyboard settings menu for instance?

Hi @chinmaygarde
The above test was conducted with a French (France) keyboard.

I'm facing the same problems in Spanish. Trying to add vocals with accents like é - á - ó etc... results in ´é - ´á - ´ó etc...


scrcpy.exe has stopped working

I try to run scrcpy on win 7 32
And scrcpy crash when i try to open..
adb is workig. (eg . adb shell)
how can I troubleshoot.

See https://github.com/Genymobile/scrcpy/issues/158.

how can I troubleshoot.

Try compiling it manually and debug it to get a stacktrace (but I have no idea how to debug on Windows).

I have the same issue. #257
It used to work fine, now I had no success to run scrcpy.

I running windows 7 on VMware and remote Desktop to that windows.
And I have no video drive to update to...
Is look is not working when you are using RemoteDesktop and scrcpy

Could you get a stacktrace when it crashes, please?
(sorry, I don't know Windows well, so I don't really know how to do that, but check https://stackoverflow.com/questions/24208767/get-stack-trace-of-a-crash-on-windows-without-installing-visual-studio-c)
Here is a debug version, to have all symbols (replace it in scrcpy directory): scrcpy.exe.
SHA-256: 8450851b06252761f723a825db308450a973ddb682b4b59b4d24008717fef0f3

Thank you for the logs.

DEBUG: Failed loading SHCORE.DLL: The specified module could not be found.

It seems this is not a problem: https://discourse.libsdl.org/t/sdl-image-2-0-1-tries-to-load-shcore-dll-in-windows-7/22796/2

That error message gets set by SDL2. The windows video driver checks for the DLL and loads some functions if it is present. The initialization does not fail if it is not.

The log CreateDevice() comes from SDL: SDL_render_d3d.c.
It does not explain why it make scrcpy crash though. When this happens, it returns NULL, and SDL_CreateRenderer() handles it correctly. In turn, scrcpy handle the error: screen.c.

If i start in RemoteDesktop is look like this,
But I start i VM host console is look normal..
Strange.

It seems there is a problem with your drivers.
What if you disable hardware acceleration (but it can be slow):
diff --git a/app/src/screen.c b/app/src/screen.c
index 5d7a400..6469b15 100644
--- a/app/src/screen.c
+++ b/app/src/screen.c
@@ -156,7 +156,7 @@ SDL_bool screen_init_rendering(struct screen *screen, const char *device_name, s
         return SDL_FALSE;
     }

-    screen->renderer = SDL_CreateRenderer(screen->window, -1, SDL_RENDERER_ACCELERATED);
+    screen->renderer = SDL_CreateRenderer(screen->window, -1, 0);
     if (!screen->renderer) {
         LOGC("Could not create renderer: %s", SDL_GetError());
         screen_destroy(screen);

I have problem to build the software.
Can you pleas build scrcpy with disable hardware acceleration..
Please..

Hi, @ostgardh
Here you are! scrcpy-win64-v1.3-13-g78d5a4d.zip.
The latest master branch with the patch of @rom1v .
Thanks.

I tested my phone in a HP computer with windows 10 and works fine. I had upgraded my windows 7 to windows 10 in a Dell laptop but the error still present.
Seems that is an issue with the USB connection. Is there a command to verify proper communication between PC and mobile? any idea to verify read/write or access permissions?
Note that when I write ADB devices my phone is properly detected.

@josuesoto1 If it crashes like this, it is probably related to your graphic driver.

Thanks, Is there a way to override this or bypass with lower resolution?

I don't know. I'm closing since there is probably nothing scrcpy can do if it's related to graphic drivers.

It seems like it might not be a graphic driver issue. In my case, Windows' Event Viewer reports the dgapi64.dll is liable for the crash.
Apparently,

This file is part of Verdasys Digital Guardian and is installed by many companies to protect corporate confidential data.
...
As an example it can block file all writes to removable media, or just block specific files according to preset criteria. It can block applications starting, either a particular application, or the other way around only allowing preset white listed applications to be run.

Source: https://www.file.net/process/dgapi.dll.html
Devs and testers in my company with company laptops have the same issue. It works on my personal laptop fine as it does not have the offending DLL under c:\windows\system32\.
Scrcpy probably uses some calls that our company policy deems insecure. It might be just our overprotective policy but it might be worth investigating a little bit more.


Discord bot

@KALLITAH, did you mean to open a blank issue? I'll close this in case it was opened by mistake, but feel free to reopen it with a description! Thanks!


Can we refer to our lab codes and the prof's lecture codes for the finals?

Also for the finals, can we use a software like Intellij to test our answers before submitting?

Yup we are able to refer to our lab codes and prof lecture notes. My TA told us using jshell should be fine but not sure about using Intellij tho

Yup we are able to refer to our lab codes and prof lecture notes. My TA told us using jshell should be fine but not sure about using Intellij tho

According to my TA, using IntelliJ is also fine!


MTLResource newBufferWithBytesNoCopy:length:options:deallocator: failed to create on mac os runner

Description
On Mac OS runner, newBufferWithBytesNoCopy:length:options:deallocator: create an instance with length zero and accesing elements causes a segmentation fault
    id<MTLBuffer> device_buffer = [device newBufferWithBytesNoCopy:ns_mutable_ptr
                                                            length:length
                                                           options:0
                                                       deallocator:nil
    ];
    printf("Device buffer created\n");
    int device_buffer_length = [device_buffer length];
    printf("Length: %d\n", device_buffer_length);

view full
Platforms affected

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

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[X] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[X] macOS 14
[X] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
macos-12
macos-14
https://github.com/mesozoic-egg/newbufferwithbytesnocopy/actions/runs/10977075322
Is it regression?
No
Expected behavior
The length should not be zero for the returned MTLBuffer instance
$ clang -framework CoreGraphics -framework Foundation -framework Metal newbufnocopy.m -o newbufnocopy && ./newbufnocopy
Malloc data[0] = 10
Malloc data[1] = 20
Malloc data[2] = 30
Malloc data[3] = 40
NSMutable data created
Length: 16
NSMutable data[0] = 10
NSMutable data[1] = 20
NSMutable data[2] = 30
NSMutable data[3] = 40
Device buffer created
Length: 16
Data pointer obtained
Device buffer[0] = 10
Device buffer[1] = 20
Device buffer[2] = 30
Device buffer[3] = 40

Actual behavior
The length being returned is 0 and accessing the elements cause a segmentation fault, happens on both arm (macos 14) and x86 (macos 12)
$ clang -framework CoreGraphics -framework Foundation -framework Metal newbufnocopy.m -o newbufnocopy
Malloc data[0] = 10
Malloc data[1] = 20
Malloc data[2] = 30
Malloc data[3] = 40
NSMutable data created
Length: 16
NSMutable data[0] = 10
NSMutable data[1] = 20
NSMutable data[2] = 30
NSMutable data[3] = 40
Device buffer created
Length: 0
Data pointer obtained
Device buffer length is 0 <----- THIS WOULD CAUSE SEG FAULT

Repro steps
reproducible example

Compile and run this script with clang -framework CoreGraphics -framework Foundation -framework Metal newbufnocopy.m -o newbufnocopy && ./newbufnocopy

Hi @mesozoic-egg, I will take a look into this issue and keep you posted updates.

When changing to use the vm_allocate, I saw that the mac 14 (arm) runner worked as expected, but not on mac 12 (x86) runner
https://github.com/mesozoic-egg/newbufferwithbytesnocopy/actions/runs/11055124079/job/30713571130
code: https://github.com/mesozoic-egg/newbufferwithbytesnocopy/blob/vm_alloc/newbufnocopy.m
    int length = 16;
    void *updateAddress;
    kern_return_t err = vm_allocate((vm_map_t)mach_task_self(),
                                            (vm_address_t*)&updateAddress,
                                            length,
                                            VM_FLAGS_ANYWHERE);
    for (int i = 0; i < 4; i++) {
        ((int*)updateAddress)[i] = i;
    }
    assert(err == KERN_SUCCESS);
    id<MTLBuffer> device_buffer = [device newBufferWithBytesNoCopy:updateAddress
                                                            length:length
                                                           options:0
                                                       deallocator:nil
    ];
    printf("Device buffer created\n");
    int device_buffer_length = [device_buffer length];
    printf("Length: %d\n", device_buffer_length);

Hi @mesozoic-egg,

Since we are deprecating macOS 12 by December and no longer generating new images for it, we recommend transitioning to macOS 14 or macOS 15, where the issue is not present.
As a workaround, you can use posix_memalign to ensure the allocated memory is aligned to 16 bytes, which is required by Metal. We've tested this across all macOS images, and it works as expected. Please use the following code and test it on macOS 12 and macOS 14 to confirm that the buffer length is correctly displayed as 16 bytes.

Please let us know if this works for you.
/*
 * clang -framework CoreGraphics -framework Foundation -framework Metal newbufnocopy.m -o newbufnocopy && ./newbufnocopy
 */

#import <Foundation/Foundation.h>
#import <Metal/Metal.h>
#import <CoreGraphics/CoreGraphics.h>
#include <stdlib.h>  // For posix_memalign

int main(int argc, char** argv)
{
    id<MTLDevice> device = MTLCreateSystemDefaultDevice();
    int length = 16;
    void *updateAddress;

    // Use posix_memalign to ensure memory alignment
    int alignment = 16;  // Metal usually requires at least 16-byte alignment
    int result = posix_memalign(&updateAddress, alignment, length);

    for (int i = 0; i < 4; i++) {
        ((int*)updateAddress)[i] = i;
    }

    // Create a Metal buffer with newBufferWithBytes
    id<MTLBuffer> device_buffer = [device newBufferWithBytes:updateAddress
                                                      length:length
                                                     options:0
    ];

    printf("Device buffer created\n");
    int device_buffer_length = (int)[device_buffer length];
    printf("Length: %d\n", device_buffer_length);

    int *data = (int*)[device_buffer contents];
    printf("Data pointer obtained\n");

    if (device_buffer_length == 0) {
        printf("Device buffer length is 0\n");
        free(updateAddress);
        return 0;
    }

    for (int i = 0; i < 4; i++) {
        printf("Device buffer[%d] = %d\n", i, data[i]);
    }

    free(updateAddress);
    return 0;
}

Hi @mesozoic-egg We believe that you will be able to generate  buffer length is correctly displayed as 16 bytes  on macOS 12 and macOS 14 images by using above mentioned code.There is no action item pending from our end hence we are closing the issue.

Thank you! @sureshe456


Add a guide about execution performance

This need after 0.2 performance increase release.
Need to add to documentation guide about how to use Neural Pipeline more effective.

Looks like this is an incredible tool: https://pytorch.org/docs/stable/bottleneck.html


Move test selectorsLabels

The tests passed. Only the publication of the report failed, It's not critical

One failed test is related to the issues with production connection on which the charts from test are based. The test is not related to changes in pr


[#254] Fix a bug where the helperClass isn't correctly applied

This is due to Element.classList.add not supporting multiple arguments in IE11, as noted in the browser compatibility table here: https://developer.mozilla.org/en-US/docs/Web/API/Element/classList
You should probably use classlist-polyfill.

This was fixed in a separate PR, see https://github.com/clauderic/react-sortable-hoc/blob/master/src/SortableContainer/index.js#L341


0.3.0 benchmarking

DO NOT Merge, testing only

0.3.0 analog of https://github.com/1c3t3a/rust-socketio/pull/71


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-09-27)
Features

pathfinder: script fisrt solution + add documentation adr (b693f80)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.1.0
:sunflower:


Skills

Description
Add person skills function
Proposed solution
No response
Alternatives considered
No response
Do you want to create a pull request?
No

@theryansmee do you want to take this?

Yeah sure assign it to me 😊

@theryansmee I've added you as a member of this project. You have write access now.

Thank you! That's really cool 😊


Remove block interface - worker side

What changes are proposed in this pull request?
This change removed the worker-side implementation of the Block API, i.e. how a file is managed in the unit of blocks and how the I/O and management go. Needless to mention, the corresponding UT and integration tests are removed with their functionalities.
Removed functionalities
Instead of listing the removed code classes one by one, corresponding functionalities will be listed here for future reference.

All Allocator & Evictor & Reviewer classes and implementations are removed. Those class specify how a block is allocated and evicted. Those include all code under worker/block/allocator/, worker/block/evictor/ and worker/block/reviewer/.
All tiered storage related code are removed, including the logic to sort the blocks between tiers and to move them between tiers. Those code typically reside in worker/block/annotator/ and worker/block/management/. Tiered store representations like StorageDir are also removed. Finally, TieredBlockStore is removed.
New BlockStore implementations like MonoBlockStore, UnderFileSystemBlockStore and LocalBlockStore are removed. Those implementations were added late in the 2.x line, to bring in Page API under the Block interface. PagedBlockStore is also removed. PagedBlockStore is an intermediate solution to convert Page to Block. That is no longer necessary because we now directly use Page. All code relevant to the page-block conversion, and the wrapped PagedBlockStore reader/writer are removed altogether, which typically belong to worker/page/. underfs/PagedUfsReader is removed too.
Metadata representations related to those feature are removed, together with their tests. Those logic are typically in worker/block/meta.
BlockReaderFactory/BlockWriterFactory and their children like TieredBlockReaderFactory are removed.
Block information view representations are removed. Some examples are BlockMetadataView and BlockMetadataManager.
Worker-side register and heartbeat logic is removed. This includes a normal register process like BlockMasterSync. This also includes special register logic like registering to all masters in HA. This includes reporting metrics and block updates in a heartbeat. One exception is some register logic are still used in PagedDoraWorker so will be kept around until a refactor purges the rest of those. PinList sync is removed too.
Worker-side block read and write handlers are removed. This includes client I/O handlers like BlockReadHandler, ShortCircuitBlockReadHandler, UfsFallbackBlockReadHandler in worker/grpc and worker/netty and worker/block/io.
Worker-side block reader and writers are removed. This part specifies how a worker read/write from a remote worker or UFS. Some examples are worker/block/RemoteBlockReader and worker/block/UnderFileSystemBlockReader.
Some request definitions and their RPC contexts are removed. For example, BlockWriteRequest and BlockWriteRequestContext.
Async caching logic is removed, together with the worker logic to handle async cache request.
Async block removal logic is removed.
Block locking lock management logic is removed.
Stress testing on worker register/heartbeat logic are removed.
General client block service handler BlockWorkerClientServiceHandler is removed.
REST service handler Alluxio AlluxioWorkerRestServiceHandler is removed. That means the worker is no longer serving REST requests. We need to implement new REST service definitions because that feature is still relevant.
DefaultBlockWorker is removed, together with its constructor class BlockWorkerFactory and BlockWorkerModule.
The old worker/block/FuseManager is removed.
Worker microbench tests are removed.

Exceptions
We try really hard NOT to modify existing code, because this PR is very hard to review and discuss on. Most of the switch changes are embedded in https://github.com/Alluxio/alluxio/pull/17638/commits/3febe93550792202420ef7bbb09fa359fc4421e6 If a change needs discussion, that will be postponed to a separate PR.
We had to keep some classes around because it is hard to remove it without incurring extra code changes. Generally speaking, a piece of code is not removed if:

It is not in the worker module. For example, the code is under alluxio-core-common or alluxio-server-common. The code is there because it is used by the master/client side. So it's hard to remove it now.
It requires extra code change to remove. We don't want extra code changes in this PR so we don't do it now. For example, PagedDoraWorker incorrectly reused some register code, so we keep those register code until the next refactor.

For many such cases, TODO are added explaining why a class is not removed, in https://github.com/Alluxio/alluxio/pull/17638/commits/8c20387556483b5ca2a10e751737519cc0240dd4. But note there may be a lot of overlooks.
Removed integration tests
Many integration tests are removed. They became irrelevant because they are mainly targeting the Block API. However, the functionality behind might still bear a little value, meaning the tests cases might be worth another look in the future. They are:
dora/tests/src/test/java/alluxio/server/tieredstore/CapacityUsageIntegrationTest.java
dora/tests/src/test/java/alluxio/server/tieredstore/SpecificTierWriteIntegrationTest.java
dora/tests/src/test/java/alluxio/server/tieredstore/TierPromoteIntegrationTest.java
dora/tests/src/test/java/alluxio/server/tieredstore/TieredStoreIntegrationTest.java
dora/core/server/worker/src/test/java/alluxio/worker/block/DefaultBlockWorkerExceptionTest.java
dora/core/server/worker/src/test/java/alluxio/worker/block/DefaultBlockWorkerTest.java
dora/core/server/worker/src/test/java/alluxio/worker/block/DefaultBlockWorkerTestBase.java
dora/core/server/worker/src/test/java/alluxio/worker/block/stream/BlockWorkerDataReaderTest.java
dora/tests/src/test/java/alluxio/client/fs/FreeAndDeleteIntegrationTest.java
dora/tests/src/test/java/alluxio/server/tieredstore/LostStorageIntegrationTest.java

Things we know are broken by this removal

FuseManager relies totally on Block API. With that removed, fuse on worker is broken.
The Rest service handlers are totally on Block API. With that removed, REST on worker is broken.

Why are the changes needed?
The Block API is obsolete. Keeping that around only makes it harder to develop new features.

Waiting on https://github.com/Alluxio/alluxio/pull/17612

alluxio-bot, merge this please


Create LICENSE.md

I added my name to the license, open for further adaptations if necessary by other contributors.

I would like my contributions to follow the license of this repository from this commit onwards


Dashboard still not embeddable

In the fix for issue #204 , a few dash files were moved from internal to pkg so that they could more readily called from another app (thanks for that!). But alas, it is still not quite there. in pkg/dash/dash.go, Run requires being passed a logger object that must implement an interface (Logger) that is in an internal package, so there is no way to call this externally.
internal/commands/dash.go also has to jump through some hoops to create this logger based on a zap logger with some extra functions wrapped around this. Perhaps this logger and a simple constructor can be exposed into pkg/dash ?

@GarySmith Ahh, ok, I think at a minimum we can move the log interface to pkg so that is can be implemented. I don't know if we want all of our logging code to move up in to pkg because then we will have people importing and depending on it and I think we want to keep the ability to be able to switch up and change our logging code on a whim.

Ok, that makes sense. Just need some ability to simply construct a logger and pass it along to Run, and keeping the details and implementation private is fine.

Circling back around to this after discussing plans with @dotNomad about how we're invoking octant.  Presently we are wrapping a command line style execution which, while @GarySmith was able to make it work, the end product presents a few issues that are less than ideal.  Out of curiosity has anything been done on improving the ability to embed octant since the last update of this issue?  Being able to embed octant without having to call command line redirects would most likely be a better solution for us long term.

After discussing this during the 26th Feb 2020 community meeting, we determined that making a public logging interface that could be implemented so that the Run function could be called directly from tools that wish to embed Octant as their front end was something we can/will do and that we'd welcome PRs for this.

I'll take a stab at this!

@dotNomad how are things going with this?

@wwitzel3 Really dove into this yesterday, and was struggling with some dependency caused import errors in airshipui. Working to solve that. I'll keep you updated with this as I continue.


Added C# example to create complex index

#24014
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Our executable samples have a few moving parts, so I prepared https://github.com/Azure/azure-sdk-for-net/pull/24654 if you want to take a look and see if that helps explain it better.

Thank you for the PR. Unfortunately, we do require that code shown in snippets gets extracted from buildable and even executed samples or tests, so more was needed as seen in PR #24654. Hopefully this resolves any confusion; however, if not, feel free to reopen this issue with clarification or submit another PR similar to #24654 e.g., that snippet code is added or updated in samples or tests and you run eng/scripts/Update-Snippets.ps1 search after.


Syntax error with Python 3.5 (Arch Linux, Python 3.5 default interpreter)

From what it looks like, someone attempted poorly to port Python 2.7 code to Python 3.
The below section includes a section of an error log when attempting to install with python3 as the default Python interpreter:
running install_lib
byte-compiling /usr/lib/python3.5/site-packages/fluxgui/fluxapp.py to fluxapp.cpython-35.pyc
  File "/usr/lib/python3.5/site-packages/fluxgui/fluxapp.py", line 28
    print e
          ^
SyntaxError: Missing parentheses in call to 'print'

byte-compiling /usr/lib/python3.5/site-packages/fluxgui/settings.py to settings.cpython-35.pyc
  File "/usr/lib/python3.5/site-packages/fluxgui/settings.py", line 102
    except DirectoryCreationError, e:
                                 ^
SyntaxError: invalid syntax

I have a similiar error when starting fluxgui:
File "/usr/lib/python3.5/site-packages/fluxgui/fluxapp.py", line 28
print e
^
SyntaxError: Missing parentheses in call to 'print'


Holding down the delete key on some input fields makes the cursor jump back to the beginning of the line

When using some input fields, the cursor will jump back to the beginning of the line. Here is an example of this behaviour in the email input field from the docs:

It doesn't seem to happen in all input fields and only seems to happen when there are spaces (i.e more than one word)
Example was taken from Chrome 51.0.2704.106 on OSX 10.11.5

This is happening because it's an email type and there is a reported bug in React repository about it. Closing since it's not actually related to the library.


Code transform task is very slow

The code transform task is very slow (appr. 22 seconds) for me with BartyCrouch 4.0.2
configuration file:
[update]
tasks = ["interfaces", "transform", "normalize"]
    [update.interfaces]
    path = "."
    defaultToBase = false
    ignoreEmptyStrings = false
    unstripped = false

    [update.code]
    codePath = "."
    localizablePath = "."
    defaultToKeys = false
    additive = true
    unstripped = false

    [update.transform]
    codePath = "iOS-App/."
    localizablePath = "."
    transformer = "swiftgenStructured"
    supportedLanguageEnumPath = "."
    typeName = "BartyCrouch"
    translateMethodName = "translate"

    [update.normalize]
    path = "."
    sourceLocale = "en"
    harmonizeWithSource = true
    sortByKeys = true

    [lint]
    path = "."
    duplicateKeys = true
    emptyValues = true

Xcode Version 10.3 (10G8)
macOS Version 10.14.5 (18F132)
BartyCrouch versions 4.0.2
Project with appr. 150 files and up to appr. 300 lines of code per file. Approximately 150 localized strings.

Thank you for reporting this. Did you already try providing more specific paths for all options including path as suggested in the README? For example for localizablePath and supportedLanguageEnumPath within the update.transform config. Also please note that you don't need to write iOS-App/., you can simply use iOS-App for the path.

Thank you for your quick reply. I added this line and the execution time decreased from 22 seconds to 0.8 seconds, thanks!
supportedLanguageEnumPath = "iOS-App/Supporting Files"

Glad I could help. 😃


How to calculate the computational complexity?

I saw that there is a Table 8:Comparison of computational complexity among different prompting methods in the paper.
I want to know how to calculate it and if there is any code in it.
Thank you!

Hi @EdmunddzzZ,
Thank you for your interest in MaPLe!
For the flops calculation, we evaluated all methods using a fvcore python library.
You can calculate the flops with simple commands such as follows. You might need to slightly change the parameters given to the  forward function of MaPLe, so it can use single input which is a requirement by fvcore package.
from fvcore.nn import FlopCountAnalysis
flops = FlopCountAnalysis(model, input) # input is the image
flops.total()  # running this line will print the flops

We calculated the flops using Caltech-101 datasets with 1 batch-size for the images.
Furthermore, the throughput was calculated by noting the imagenet inference time taken by each method on a single A100 GPU.
I hope this answers your issue, please let us know incase there are any further queries.
Thank you!

Thank you for your patient explanation！
I also want to know how to draw fig3 t-SNE plots , as I have been following your work and writing a paper recently.
Thank you!

Hi @EdmunddzzZ,
Please refer to this code which we used to generate the t-SNE plots. You would also need to first generate and store the CLIP vision-encoder image-embeddings. Afterwards, the t-SNE plot code will produce the require plots.
Thank you!

Can you provide your code about fig3 ?


Update dependencies

Coverage increased (+0.03%) to 90.919% when pulling 788cdaa926e7b19456a04483bdc3420a11dc829e on hsiliev:deps_shrinkwrap into 24f0c5b66e31be60dabc0acb4bb2d476e35198ce on cloudfoundry-incubator:master.


Pin<Box<dyn Future<Output = _>>> in Trait Object translate issue

Describe the bug
use std::{future::Future, pin::Pin};

#[flutter_rust_bridge::frb]
pub struct A();
impl TraitA for A {}

#[flutter_rust_bridge::frb]

pub trait TraitA {
    fn do_something(&self) -> Pin<Box<dyn Future<Output = ()> + 'static>> {
        Box::pin(async {})
    }
}

pub type TraitAObject = Box<dyn TraitA + Send + Sync>;

This minium code translation got 2 errors:

impl SseDecode
    for RustOpaqueMoi<
        flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
            Pin<Box<dyn Future<Output = ()> + 'static>>,
        >,
    >
{
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        let mut inner = <usize>::sse_decode(deserializer);
        return decode_rust_opaque_moi(inner);
    }
}

got error:
error[E0277]: `(dyn std::future::Future<Output = ()> + 'static)` cannot be shared between threads safely
    --> src\frb_generated.rs:183:16
     |
183  |         return decode_rust_opaque_moi(inner);
     |                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `(dyn std::future::Future<Output = ()> + 'static)` cannot be shared between threads safely
     |
     = help: the trait `std::marker::Sync` is not implemented for `(dyn std::future::Future<Output = ()> + 'static)`, which is required by `RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>: std::marker::Sync`
     = note: required for `Unique<(dyn std::future::Future<Output = ()> + 'static)>` to implement `std::marker::Sync`
note: required because it appears within the type `Box<(dyn std::future::Future<Output = ()> + 'static)>`
    --> C:\Users\canxin.LAPTOP\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\alloc\src\boxed.rs:196:12
     |
196  | pub struct Box<
     |            ^^^
note: required because it appears within the type `std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>`
    --> C:\Users\canxin.LAPTOP\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\core\src\pin.rs:1090:12
     |
1090 | pub struct Pin<Ptr> {
     |            ^^^
     = note: required for `flutter_rust_bridge::rust_async::RwLock<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>` to implement `std::marker::Sync`
note: required because it appears within the type `RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>`
    --> C:\Users\canxin.LAPTOP\.cargo\registry\src\index.crates.io-6f17d22bba15001f\flutter_rust_bridge-2.0.0\src\rust_auto_opaque\inner.rs:4:12
     |
4    | pub struct RustAutoOpaqueInner<T> {
     |            ^^^^^^^^^^^^^^^^^^^
note: required by a bound in `decode_rust_opaque_moi`
    --> src\frb_generated.rs:39:1
     |
39   | / flutter_rust_bridge::frb_generated_boilerplate!(
40   | |     default_stream_sink_codec = SseCodec,
41   | |     default_rust_opaque = RustOpaqueMoi,
42   | |     default_rust_auto_opaque = RustAutoOpaqueMoi,
43   | | );
     | |_^ required by this bound in `decode_rust_opaque_moi`
     = note: this error originates in the macro `$crate::frb_generated_rust_opaque_dart2rust` which comes from the expansion of the macro `flutter_rust_bridge::frb_generated_boilerplate` (in Nightly builds, run with -Z macro-backtrace for more info)

// Section: related_funcs

flutter_rust_bridge::frb_generated_moi_arc_impl_value!(
    flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
        Pin<Box<dyn Future<Output = ()> + 'static>>,
    >
);

got error:
error[E0277]: `(dyn std::future::Future<Output = ()> + 'static)` cannot be sent between threads safely
    --> src\frb_generated.rs:153:1
     |
153  | / flutter_rust_bridge::frb_generated_moi_arc_impl_value!(
154  | |     flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
155  | |         Pin<Box<dyn Future<Output = ()> + 'static>>,
156  | |     >
157  | | );
     | |_^ `(dyn std::future::Future<Output = ()> + 'static)` cannot be sent between threads safely
     |
     = help: the trait `std::marker::Send` is not implemented for `(dyn std::future::Future<Output = ()> + 'static)`, which is required by `std::sync::RwLock<MoiArcPoolInner<RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>>>: std::marker::Sync`
     = note: required for `Unique<(dyn std::future::Future<Output = ()> + 'static)>` to implement `std::marker::Send`
note: required because it appears within the type `Box<(dyn std::future::Future<Output = ()> + 'static)>`
    --> C:\Users\canxin.LAPTOP\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\alloc\src\boxed.rs:196:12
     |
196  | pub struct Box<
     |            ^^^
note: required because it appears within the type `std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>`
    --> C:\Users\canxin.LAPTOP\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\core\src\pin.rs:1090:12
     |
1090 | pub struct Pin<Ptr> {
     |            ^^^
     = note: required for `flutter_rust_bridge::rust_async::RwLock<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>` to implement `std::marker::Sync`
note: required because it appears within the type `RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>`
    --> C:\Users\canxin.LAPTOP\.cargo\registry\src\index.crates.io-6f17d22bba15001f\flutter_rust_bridge-2.0.0\src\rust_auto_opaque\inner.rs:4:12
     |
4    | pub struct RustAutoOpaqueInner<T> {
     |            ^^^^^^^^^^^^^^^^^^^
     = note: required for `Arc<RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>>` to implement `std::marker::Send`
note: required because it appears within the type `MoiArcPoolValue<RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>>`
    --> src\frb_generated.rs:39:1
     |
39   | / flutter_rust_bridge::frb_generated_boilerplate!(
40   | |     default_stream_sink_codec = SseCodec,
41   | |     default_rust_opaque = RustOpaqueMoi,
42   | |     default_rust_auto_opaque = RustAutoOpaqueMoi,
43   | | );
     | |_^
     = note: required because it appears within the type `(usize, MoiArcPoolValue<RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>>)`
     = note: required for `RawTable<(usize, MoiArcPoolValue<RustAutoOpaqueInner<Pin<Box<dyn Future<Output = ()>>>>>)>` to implement `std::marker::Send`
note: required because it appears within the type `HashMap<usize, MoiArcPoolValue<RustAutoOpaqueInner<Pin<Box<dyn Future<Output = ()>>>>>, RandomState>`
    --> /rust/deps\hashbrown-0.14.3\src\map.rs:190:12
note: required because it appears within the type `HashMap<usize, MoiArcPoolValue<RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>>>`
    --> C:\Users\canxin.LAPTOP\.rustup\toolchains\stable-x86_64-pc-windows-msvc\lib/rustlib/src/rust\library\std\src\collections\hash\map.rs:213:12
     |
213  | pub struct HashMap<K, V, S = RandomState> {
     |            ^^^^^^^
note: required because it appears within the type `MoiArcPoolInner<RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>>`
    --> src\frb_generated.rs:39:1
     |
39   | / flutter_rust_bridge::frb_generated_boilerplate!(
40   | |     default_stream_sink_codec = SseCodec,
41   | |     default_rust_opaque = RustOpaqueMoi,
42   | |     default_rust_auto_opaque = RustAutoOpaqueMoi,
43   | | );
     | |_^
     = note: required for `std::sync::RwLock<MoiArcPoolInner<RustAutoOpaqueInner<std::pin::Pin<Box<(dyn std::future::Future<Output = ()> + 'static)>>>>>` to implement `std::marker::Sync`
note: required by a bound in `lazy_static::lazy::Lazy`
    --> C:\Users\canxin.LAPTOP\.cargo\registry\src\index.crates.io-6f17d22bba15001f\lazy_static-1.4.0\src\inline_lazy.rs:19:20
     |
19   | pub struct Lazy<T: Sync>(Cell<Option<T>>, Once);
     |                    ^^^^ required by this bound in `Lazy`
     = note: the full name for the type has been written to 'C:\Users\canxin.LAPTOP\test_trait\rust\target\debug\deps\rust_lib_test_trait-82aa68d9a5eb476b.long-type-8598590409287766133.txt'
     = note: consider using `--verbose` to print the full type name to the console
     = note: the full name for the type has been written to 'C:\Users\canxin.LAPTOP\test_trait\rust\target\debug\deps\rust_lib_test_trait-82aa68d9a5eb476b.long-type-12697570336106566502.txt'
     = note: consider using `--verbose` to print the full type name to the console
     = note: this error originates in the macro `__lazy_static_create` which comes from the expansion of the macro `flutter_rust_bridge::frb_generated_boilerplate` (in Nightly builds, run with -Z macro-backtrace for more info)

Is there a way to translate the sync funcs in trait object that return Pin<Box<dyn Future<Output = _>>> to async funcs?
Steps to reproduce
Hint: A simple way to reproduce is to clone and modify the https://github.com/fzyzcjy/flutter_rust_bridge/tree/master/frb_example/dart_minimal example package according to your needs.

use the minium code to translate
got 2 error

Logs
The translate succeed without error or warn.

Expected behavior
    fn do_something(&self) -> Pin<Box<dyn Future<Output = ()> + 'static>> {
        Box::pin(async {})
    }

get the same translation as below async fn code
    fn async do_something(&self) -> () {
    }

Generated binding code
// This file is automatically generated, so please do not edit it.
// Generated by `flutter_rust_bridge`@ 2.0.0.

#![allow(
    non_camel_case_types,
    unused,
    non_snake_case,
    clippy::needless_return,
    clippy::redundant_closure_call,
    clippy::redundant_closure,
    clippy::useless_conversion,
    clippy::unit_arg,
    clippy::unused_unit,
    clippy::double_parens,
    clippy::let_and_return,
    clippy::too_many_arguments,
    clippy::match_single_binding,
    clippy::clone_on_copy,
    clippy::let_unit_value,
    clippy::deref_addrof,
    clippy::explicit_auto_deref,
    clippy::borrow_deref_ref,
    clippy::needless_borrow
)]

// Section: imports

use std::future::Future;
use std::pin::Pin;

use crate::api::TraitA;
use crate::api::*;
use flutter_rust_bridge::for_generated::byteorder::{NativeEndian, ReadBytesExt, WriteBytesExt};
use flutter_rust_bridge::for_generated::{transform_result_dco, Lifetimeable, Lockable};
use flutter_rust_bridge::{Handler, IntoIntoDart};

// Section: boilerplate

flutter_rust_bridge::frb_generated_boilerplate!(
    default_stream_sink_codec = SseCodec,
    default_rust_opaque = RustOpaqueMoi,
    default_rust_auto_opaque = RustAutoOpaqueMoi,
);
pub(crate) const FLUTTER_RUST_BRIDGE_CODEGEN_VERSION: &str = "2.0.0";
pub(crate) const FLUTTER_RUST_BRIDGE_CODEGEN_CONTENT_HASH: i32 = -444446631;

// Section: executor

flutter_rust_bridge::frb_generated_default_handler!();

// Section: wire_funcs

fn wire__crate__api__a_do_something_impl(
    port_: flutter_rust_bridge::for_generated::MessagePort,
    ptr_: flutter_rust_bridge::for_generated::PlatformGeneralizedUint8ListPtr,
    rust_vec_len_: i32,
    data_len_: i32,
) {
    FLUTTER_RUST_BRIDGE_HANDLER.wrap_normal::<flutter_rust_bridge::for_generated::SseCodec, _, _>(
        flutter_rust_bridge::for_generated::TaskInfo {
            debug_name: "a_do_something",
            port: Some(port_),
            mode: flutter_rust_bridge::for_generated::FfiCallMode::Normal,
        },
        move || {
            let message = unsafe {
                flutter_rust_bridge::for_generated::Dart2RustMessageSse::from_wire(
                    ptr_,
                    rust_vec_len_,
                    data_len_,
                )
            };
            let mut deserializer =
                flutter_rust_bridge::for_generated::SseDeserializer::new(message);
            let api_that = <crate::api::A>::sse_decode(&mut deserializer);
            deserializer.end();
            move |context| {
                transform_result_sse::<_, ()>((move || {
                    let output_ok = Result::<_, ()>::Ok(crate::api::A::do_something(&api_that))?;
                    Ok(output_ok)
                })())
            }
        },
    )
}
fn wire__crate__api__simple__greet_impl(
    ptr_: flutter_rust_bridge::for_generated::PlatformGeneralizedUint8ListPtr,
    rust_vec_len_: i32,
    data_len_: i32,
) -> flutter_rust_bridge::for_generated::WireSyncRust2DartSse {
    FLUTTER_RUST_BRIDGE_HANDLER.wrap_sync::<flutter_rust_bridge::for_generated::SseCodec, _>(
        flutter_rust_bridge::for_generated::TaskInfo {
            debug_name: "greet",
            port: None,
            mode: flutter_rust_bridge::for_generated::FfiCallMode::Sync,
        },
        move || {
            let message = unsafe {
                flutter_rust_bridge::for_generated::Dart2RustMessageSse::from_wire(
                    ptr_,
                    rust_vec_len_,
                    data_len_,
                )
            };
            let mut deserializer =
                flutter_rust_bridge::for_generated::SseDeserializer::new(message);
            let api_name = <String>::sse_decode(&mut deserializer);
            deserializer.end();
            transform_result_sse::<_, ()>((move || {
                let output_ok = Result::<_, ()>::Ok(crate::api::simple::greet(api_name))?;
                Ok(output_ok)
            })())
        },
    )
}
fn wire__crate__api__simple__init_app_impl(
    port_: flutter_rust_bridge::for_generated::MessagePort,
    ptr_: flutter_rust_bridge::for_generated::PlatformGeneralizedUint8ListPtr,
    rust_vec_len_: i32,
    data_len_: i32,
) {
    FLUTTER_RUST_BRIDGE_HANDLER.wrap_normal::<flutter_rust_bridge::for_generated::SseCodec, _, _>(
        flutter_rust_bridge::for_generated::TaskInfo {
            debug_name: "init_app",
            port: Some(port_),
            mode: flutter_rust_bridge::for_generated::FfiCallMode::Normal,
        },
        move || {
            let message = unsafe {
                flutter_rust_bridge::for_generated::Dart2RustMessageSse::from_wire(
                    ptr_,
                    rust_vec_len_,
                    data_len_,
                )
            };
            let mut deserializer =
                flutter_rust_bridge::for_generated::SseDeserializer::new(message);
            deserializer.end();
            move |context| {
                transform_result_sse::<_, ()>((move || {
                    let output_ok = Result::<_, ()>::Ok({
                        crate::api::simple::init_app();
                    })?;
                    Ok(output_ok)
                })())
            }
        },
    )
}

// Section: related_funcs

flutter_rust_bridge::frb_generated_moi_arc_impl_value!(
    flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
        Pin<Box<dyn Future<Output = ()> + 'static>>,
    >
);

// Section: dart2rust

impl SseDecode for Pin<Box<dyn Future<Output = ()> + 'static>> {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        let mut inner = <RustOpaqueMoi<
            flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
                Pin<Box<dyn Future<Output = ()> + 'static>>,
            >,
        >>::sse_decode(deserializer);
        return flutter_rust_bridge::for_generated::rust_auto_opaque_decode_owned(inner);
    }
}

impl SseDecode
    for RustOpaqueMoi<
        flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
            Pin<Box<dyn Future<Output = ()> + 'static>>,
        >,
    >
{
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        let mut inner = <usize>::sse_decode(deserializer);
        return decode_rust_opaque_moi(inner);
    }
}

impl SseDecode for String {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        let mut inner = <Vec<u8>>::sse_decode(deserializer);
        return String::from_utf8(inner).unwrap();
    }
}

impl SseDecode for crate::api::A {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        return crate::api::A();
    }
}

impl SseDecode for Vec<u8> {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        let mut len_ = <i32>::sse_decode(deserializer);
        let mut ans_ = vec![];
        for idx_ in 0..len_ {
            ans_.push(<u8>::sse_decode(deserializer));
        }
        return ans_;
    }
}

impl SseDecode for u8 {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        deserializer.cursor.read_u8().unwrap()
    }
}

impl SseDecode for () {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {}
}

impl SseDecode for usize {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        deserializer.cursor.read_u64::<NativeEndian>().unwrap() as _
    }
}

impl SseDecode for i32 {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        deserializer.cursor.read_i32::<NativeEndian>().unwrap()
    }
}

impl SseDecode for bool {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_decode(deserializer: &mut flutter_rust_bridge::for_generated::SseDeserializer) -> Self {
        deserializer.cursor.read_u8().unwrap() != 0
    }
}

fn pde_ffi_dispatcher_primary_impl(
    func_id: i32,
    port: flutter_rust_bridge::for_generated::MessagePort,
    ptr: flutter_rust_bridge::for_generated::PlatformGeneralizedUint8ListPtr,
    rust_vec_len: i32,
    data_len: i32,
) {
    // Codec=Pde (Serialization + dispatch), see doc to use other codecs
    match func_id {
        2 => wire__crate__api__a_do_something_impl(port, ptr, rust_vec_len, data_len),
        4 => wire__crate__api__simple__init_app_impl(port, ptr, rust_vec_len, data_len),
        _ => unreachable!(),
    }
}

fn pde_ffi_dispatcher_sync_impl(
    func_id: i32,
    ptr: flutter_rust_bridge::for_generated::PlatformGeneralizedUint8ListPtr,
    rust_vec_len: i32,
    data_len: i32,
) -> flutter_rust_bridge::for_generated::WireSyncRust2DartSse {
    // Codec=Pde (Serialization + dispatch), see doc to use other codecs
    match func_id {
        3 => wire__crate__api__simple__greet_impl(ptr, rust_vec_len, data_len),
        _ => unreachable!(),
    }
}

// Section: rust2dart

// Codec=Dco (DartCObject based), see doc to use other codecs
impl flutter_rust_bridge::IntoDart for FrbWrapper<Pin<Box<dyn Future<Output = ()> + 'static>>> {
    fn into_dart(self) -> flutter_rust_bridge::for_generated::DartAbi {
        flutter_rust_bridge::for_generated::rust_auto_opaque_encode::<_, MoiArc<_>>(self.0)
            .into_dart()
    }
}
impl flutter_rust_bridge::for_generated::IntoDartExceptPrimitive
    for FrbWrapper<Pin<Box<dyn Future<Output = ()> + 'static>>>
{
}

impl flutter_rust_bridge::IntoIntoDart<FrbWrapper<Pin<Box<dyn Future<Output = ()> + 'static>>>>
    for Pin<Box<dyn Future<Output = ()> + 'static>>
{
    fn into_into_dart(self) -> FrbWrapper<Pin<Box<dyn Future<Output = ()> + 'static>>> {
        self.into()
    }
}

// Codec=Dco (DartCObject based), see doc to use other codecs
impl flutter_rust_bridge::IntoDart for crate::api::A {
    fn into_dart(self) -> flutter_rust_bridge::for_generated::DartAbi {
        Vec::<u8>::new().into_dart()
    }
}
impl flutter_rust_bridge::for_generated::IntoDartExceptPrimitive for crate::api::A {}
impl flutter_rust_bridge::IntoIntoDart<crate::api::A> for crate::api::A {
    fn into_into_dart(self) -> crate::api::A {
        self
    }
}

impl SseEncode for Pin<Box<dyn Future<Output = ()> + 'static>> {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        <RustOpaqueMoi<
            flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
                Pin<Box<dyn Future<Output = ()> + 'static>>,
            >,
        >>::sse_encode(
            flutter_rust_bridge::for_generated::rust_auto_opaque_encode::<_, MoiArc<_>>(self),
            serializer,
        );
    }
}

impl SseEncode
    for RustOpaqueMoi<
        flutter_rust_bridge::for_generated::RustAutoOpaqueInner<
            Pin<Box<dyn Future<Output = ()> + 'static>>,
        >,
    >
{
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        let (ptr, size) = self.sse_encode_raw();
        <usize>::sse_encode(ptr, serializer);
        <i32>::sse_encode(size, serializer);
    }
}

impl SseEncode for String {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        <Vec<u8>>::sse_encode(self.into_bytes(), serializer);
    }
}

impl SseEncode for crate::api::A {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {}
}

impl SseEncode for Vec<u8> {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        <i32>::sse_encode(self.len() as _, serializer);
        for item in self {
            <u8>::sse_encode(item, serializer);
        }
    }
}

impl SseEncode for u8 {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        serializer.cursor.write_u8(self).unwrap();
    }
}

impl SseEncode for () {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {}
}

impl SseEncode for usize {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        serializer
            .cursor
            .write_u64::<NativeEndian>(self as _)
            .unwrap();
    }
}

impl SseEncode for i32 {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        serializer.cursor.write_i32::<NativeEndian>(self).unwrap();
    }
}

impl SseEncode for bool {
    // Codec=Sse (Serialization based), see doc to use other codecs
    fn sse_encode(self, serializer: &mut flutter_rust_bridge::for_generated::SseSerializer) {
        serializer.cursor.write_u8(self as _).unwrap();
    }
}

#[cfg(not(target_family = "wasm"))]
#[path = "frb_generated.io.rs"]
mod io;
#[cfg(not(target_family = "wasm"))]
pub use io::*;

/// cbindgen:ignore
#[cfg(target_family = "wasm")]
#[path = "frb_generated.web.rs"]
mod web;
#[cfg(target_family = "wasm")]
pub use web::*;

OS
Windows 10
Version of flutter_rust_bridge_codegen
=2.0.0
Flutter info
not related.

Version of clang++
not related
Additional context
no more

That complex type does not seem to be supported yet. However, frb does support normal Rust async fns. What about using https://blog.rust-lang.org/2023/12/21/async-fn-rpit-in-traits.html thus to write
pub trait TraitA {
    async fn do_something(&self) {
        //
    }
}

That complex type does not seem to be supported yet. However, frb does support normal Rust async fns. What about using https://blog.rust-lang.org/2023/12/21/async-fn-rpit-in-traits.html thus to write
pub trait TraitA {
    async fn do_something(&self) {
        //
    }
}

error[E0038]: the trait `TraitA` cannot be made into an object
  --> src\api\mod.rs:17:10
   |
17 | struct B(TraitAObject);
   |          ^^^^^^^^^^^^ `TraitA` cannot be made into an object
   |
note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>
  --> src\api\mod.rs:11:14
   |
10 | pub trait TraitA {
   |           ------ this trait cannot be made into an object...
11 |     async fn do_something(&self) -> () {}
   |              ^^^^^^^^^^^^ ...because method `do_something` is `async`
   = help: consider moving `do_something` to another trait
   = help: only type `api::A` is seen to implement the trait in this crate, consider using it directly instead
   = note: `TraitA` can be implemented in other crates; if you want to support your users passing their own types here, you can't refer to a specific type

There is a crate about it async-trait
This crate's macro translate async fn to fn -> Pin<Box<dyn Future<Output = _>>>

Hmm I see. Then maybe we can fix it like: Whenever we see Pin<Box<dyn Future<Output = WhateverType>>>, we internally treat it as async fn f() -> WhateverType. What do you think?
And btw, is there a full list what types needs to be treated like this pined boxed future?

Hmm I see. Then maybe we can fix it like: Whenever we see Pin<Box<dyn Future<Output = WhateverType>>>, we internally treat it as async fn f() -> WhateverType. What do you think?
And btw, is there a full list what types needs to be treated like this pined boxed future?

I'm not sure about other types.
And I currently use a wrapper like below. And it works well.
use std::{future::Future, pin::Pin};

use flutter_rust_bridge::frb;

pub mod simple;

#[frb(ignore)]
struct A();
impl TraitA for A {}
#[frb(ignore)]
pub trait TraitA {
    #[frb(ignore)]
    fn do_something(&self) -> Pin<Box<dyn Future<Output = ()> + 'static>> {
        Box::pin(async {})
    }
}

#[frb(ignore)]
type TraitAObject = Box<dyn TraitA + Send + Sync>;

#[frb]
pub struct TraitAObjectWrapper(TraitAObject);
#[frb(opaque)]
pub struct TraitAObjectWrapperRef<'a>(&'a TraitAObject);

impl TraitAObjectWrapper {
    async fn do_something(&self) {
        self.0.do_something().await;
    }
}

That looks great!
Feel free to PR for the type translation, alternatively I will work on it in the next batch.

I'm afraid I've been busy lately and haven't had time to read the flutter_rust_bridge code to figure out how to implement it.

No worries