Fix sidebar label dropdown divider

Follow #25312
Also fix the label dropdown on sidebar
Before:

After:

Can backport if https://github.com/go-gitea/gitea/pull/25312 also backports.

I was unable to create a backport for 1.20. @HesterG, please send one manually. :tea:
go run ./contrib/backport 25359
...  // fix git conflicts if any
go run ./contrib/backport --continue

@GiteaBot should try again now that https://github.com/go-gitea/gitea/pull/25372 is merged.


restructure DAG graph creation and fix some errors

This is a first attempt to update the DAG, so it can be used reliably to generate the list of packages to build.
The eventual goals are:

eliminate the manually-maintained list of packages in wolf-dev/os
use this DAG to build all of the packages in wolf-dev/os in order, automatically, without any caches and without any dependency failures

We will use the second step above to generate a regular CI test that builds them all from HEAD at least once a day
What this PR does

fixes a bug wherein the key to a provides actually is the filename, rather than the name of the provides (oops)
extracts a number of repetitive sections into functions
removes some methods that were on Graph and are about printing text, and moves them to a more appropriate place
removes some repetitiveness from some of the cli output methods (text, make, etc.)
handles (some of) multiple versions, whereas previously we would either lose information or have conflicts
separates parsing of the yamls in the directory and building configuration structs out of them, as well as reading all of their subpackages and provides, from constructing the actual graph
simplifies much of the building of subgraphs (from leaves and from roots) based on the separation of the previous step

The separation into Packages and Graph is particularly important. It makes it much easier to reason about what it is doing. It makes it possible to work with them separately, pulling from the appropriate location.
It also makes it clearer where we have redundancy. At a later stage, we may be able to remove some of this entirely, replacing it with other parts of this package or some of the features in apko.
What is left to do?
A number of things

add Packages and Graph unit tests - there were none before on Graph, but that doesn't mean we shouldn't add some. I don't think it should hold us up, but we should at least start.
handle versions in the graph - the graph right now is entirely based on package/subpkg/provide names. Period. That ignores the fact that there can be and are versions. Packages handles it, Graph does not. This also should not hold us up, as we do not handle versions now, and this does not lead to duplication. But we should get it right a bit later.
versioned requirements - we don't have many of these, just one for now. exim.yaml depends upon openssl-dev>3, which is treated as a straight-out package name. The logic for this already exists in apko, but is mostly not exported. We should leverage it. Again, this fails now, so this is not a regression. We should not hold up because of it.

I will try to get the above done, but if people feel this is ready, let's not hold it up. If this is a real improvement, let's accept it and iterate.

This is nice. It feels weird that we have DAG but still maintaining an ordered list in wolfi-dev/os :)

This is strange. It is failing in setting up the lint action itself?

Added tests for the Packages, moving on to Graph.

@luhring I saw you added some basic smoke test for NewGraph(). I disabled it temporarily in this PR, as it conflicts with some of my more contrived tests. But I will reenable it before we merge this in.

Please don't merge yet. Logic is not done.

Please don't merge yet. Logic is not done.

Shall we make this a draft PR for now? And you can ping us on Slack when it's ready for another look?

Yes, I will change it. It originally was draft, I thought we had it ready, now that we have reached the need for more work, I will change it back.

Those todos are done. This is ready to go in. It could use future iterations - like finer-grained options on what we report from the graph in various scenarios - but no reason for future improvements to hold us up.


More syntax for adding serial numbers

I will add the following two options to serial number-recognition:
<start>+ :add expected number of serials after <start>
<start>+<length> :add <length> numbers starting at <start>
I am thinking of also including a character for filling a pattern with all missing serials (to get the expected number of serial numbers).
What do you think @SchrodingersGat ?

I like it! Both suggestions I would support.

Sweet! Nice job!


Remove Compiled Files, ignore Files and add Compile-Check on PR

Pull Request
Another try a t resolving the "winutil.ps1 is included in a PR" once and for all and optimization to the Compilation / Merge process
!! IMPORTANT !!
This will most likely result in Merge Errors in the future. They can be resolved by manually deleting the winutil.ps1 and release.yaml from the PRs. This shouldn't be a problem for long. Just until the contributors pull the repo without winutil.ps1
Type of Change

[x] New feature

Description

Removes the winutil.ps1 from the Repo and the Git Tracking List
Adds a new Compile and Check action that Runs on every PR, and tries a Compilation and a Syntax Check using "Get-Command -Syntax" and  displays the Result accordingly
Modifies the Pre-Release Action to Compile the winutil.ps1 (because it doesn't exist in the Repo anymore)
Removes the Full Release Action (unnecessary if I understand your workflow correctly. 1. Create Pre-Release, 2. Manually Edit Pre-Release to a Full Release)

Testing
I tested this on my fork but (of course) you should test yourself because this is quite a process change.
Impact
Cleaner PRs. No more 10000+ lines changed if someone deletes the winutil.ps1
More stable PR Merging Process, because the sanity check of compiling and checking the syntax is already run before the PR gets merged (potentially it's also possible to restrict the Repo from merging a PR if the Check fails)
Checklist

[x] My code adheres to the coding and style guidelines of the project.
[x] I have performed a self-review of my own code
[ ] My changes generate no errors/warnings/merge conflicts. <- :*D Most definitely not because deleting files is always fun...

Do a PR to Contribute docs page stating how to remove the files.

@Marterich, as @Real-MullaC have pointed in his comment, these changes require updating some documentation before accepting, as some already existing Local Clones would still track WinUtil (so guiding devs on how to "refresh" their Git Cache, and why do it in first place).
And Contribute Guide heavily encourage devs to use GitHub Desktop, which GitHub Desktop by default doesn't install Git CLI, which's needed to update the cache (I believe so, maybe I'm wrong on this part), so we'll need to write an "Optional" step which'll guide devs on installing Git CLI, and how to update their local Git Cache.
Also also (this's last thing 😅), there's a step that isn't require anymore (as winutil.ps1 will not be tracked by Git anymore), see screenshot below for more info.

For the Commandline it's as simple as
git rm --cached .\winutil.ps1
git commit -am "remove ignored files"

If it's not too much of a hassle for one of you, I would really appreciate it if you could create a PR containing the DOC changes to my Branch :)
If not, I'll try to do my best later today or tomorrow...

Couldn't find a way to merge all these changes, so I manually did all these changes and made some minor modifications where needed.
The release script needed an env var for the code signing, but the rest was perfect!
Thank you @Marterich


Enable usage of Route Groups for client generation

When using controllers it is possible to use {controller} when setting stuff within the OpenApiProjectReference. We use that in our projects to set <ClassName>{controller}Client</ClassName>.
Since .NET 7 when using minimal apis we can now define so called route groups via app.MapGroup("GroupName") to group several endpoints together. When using this I would now like to have the possibility to define the ClassName in a similar fashion to what {controller} does. So e.g. a {routeGroup} which creates a client per route group.
By the way I'd gladly try to implement a first version if you think this would be a good and necessary addition.

FYI I just needed this as well, and figured out we can hijack the {controller} pattern for it.
You just have to create an IDocumentFilter implementation for your swagger generator, that constructs the operationId parameter for each operation, in the form controller_method. Obviously since you don't have an actual controller class, and methods with minimal apis, you need to sanitize the tags of the operation into a valid class name (the group will show up as a tag on the operation) and divine a method name for it from the info of the operation.
Has lots of possible ugly edge cases around so I can't give a complete example, as didn't have time for it yet, but that is the gist of it.


26 tailwind landing page

Changes

This PR closes #26
This PR also closes #15
Add TailwindCSS to landing page
Create header partial to render in layouts/application.html.erb
Refactor tests to match CSS on landing page

Type of Changes

[ ] new feature
[ ] setup
[ ] chore
[ ] bug fix
[ ] refactor
[x] other: styling

Checklist

[ ] Tests added for new functionality
[ ] All other tests are also passing (please note if not)

Current coverage %:

Number of reviewers

[x] 1
[ ] 2
[ ] 3

Emoji or GIF about how you feel rn (optional)
https://res.cloudinary.com/dukp6c7f7/image/upload/f_auto,fl_lossy,q_auto/s3-ghost//2019/09/CSS-Change.jpg

Awesome job!!! Super excited to see this deployed in action!


DrawingManager markerOptions icon object.

Can we not use custom icons in the Drawing Manager for drawing Markers???
With the following code, I get the default marker icon...
<drawing-manager
    drawing-control-options="{position: 'TOP_CENTER',drawingModes:['marker']}"
    drawingControl="true"
    drawingMode="MARKER"
    markerOptions="{
        draggable:true,
	    icon: {url:'./img/transparent-circle-marker.png',
            origin: [0,0],
            anchor: [12,12]}
	    }"
     on-overlaycomplete="onMapOverlayCompleted()"
>

But, if I change icon: to icon: {url: './img/transparent-circle-marker.png'} without the anchor property I get my custom marker image.... but it of course isn't anchored properly! >:(
Am I missing something? Or is this just not implemented?

It seems like anchorPoint, not anchor according to https://developers.google.com/maps/documentation/javascript/reference#MarkerOptions

I've yet to test it, but thanks for the reply. I didn't find this on my own lol. :+1:

Closing it.


iPhone Mirroring with macOS Sequoia

I'm testing out macOS Sequoia Beta 2, and I noticed that the scroll direction is reversed in the new iPhone Mirroring app.

Can you provide a bit more detail on this. Should it not reverse it? Since the purpose of Scroll Reverser is to reverse scrolling, a report that the app is reversing scrolling needs some extra context.

I have "Reverse Vertical" and "Reverse Mouse" enabled.
Using the trackpad, it scrolls as expected, the same way it would scroll when using the iPhone directly.  However, when using a mouse with a scroll wheel, it scrolls the opposite way.
For example, if I open Safari on macOS and scroll with the mouse wheel, it scrolls correctly based on how I have Scroll Reverser configured.  If I open Safari on iOS via iPhone Mirroring, it scrolls the opposite direction.

Yes. the reverse vertical functions not working in iPhone Mirroring.

Need update for iPhone Mirroring

Yes, iPhone Mirroring not working

+1，iPhone Mirroring not working

1+ scroll direction is wrong in the iPhone mirroring app.

iPhone Mirroring app takes gestures as its input, instead of scrolling signals.
Scroll Reverser can reverse scrolling signal but not gestures.
Therefore, unfortunately this is a can't fix.

I use logic master 3 and use Logi Options+ could work on IPhone Mirroring, i dont konw how logic options works.

I wonder if the Logi software uses a driver, perhaps. So as to work at a lower level.


K12 Update the Exit Reason picklist value to "No-Show" on Grade Enrollment

Critical Changes
Changes
We have updated the Grade Enrollment Exist Reason picklist value from "No Show" to "No-Show."
New customers will automatically get this updated value; we recommend that existing customers update the picklist label manually.
Issues Closed
Closes #173
New Metadata
Deleted Metadata
Testing Notes
Trial org:

Run cci org scratch trial
Run cci flow run trial_org
Ensure that "No-Show" is showing as the picklist value for Exist Reason on Grade Enrollment.

Non trial org:

Run cci org scratch dev
Run cci flow dev_org
Ensure that "No-Show" is showing as the picklist value for Exist Reason on Grade Enrollment.

Tested/Passes QE. Will merge after freeze has been lifted.


Add support for multiple identity providers

This is a rather crude hack around a bug in Cognito. Base64Url encode/decode the state variable to enable multiple identity providers.
Issue #, if available:
#21
Description of changes:
This is a rather primitive implementation of base64UrlEncode/Decode to get around the Cognito hosted UI error which is preventing this from being used with multiple identity providers. Instead of passing the state parameter as a string of JSON, this encodes the string it to base64, then replaces characters that would be encoded in the URL into characters that won't get modified in transit by Cognito.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

My thought is that by replacing the +/= characters, you would get a url-safe string that wouldn't get encoded/decoded incorrectly while in transit through Cognito. I haven't tested any other methods, but it's possible these additional replacements would be unnecessary with some smaller tweaks to the code.

Yeah that makes sense for sure. I'm just curious to see if if's needed in this particular case. I know replacing the / isn't needed, I see that Cognito button work fine with a slash in that state param.
Maybe you can test if + and = can remain in there too?

Also, I think it would be helpful to comment in the code on why we do the base64 encoding/decoding

Definitely agree on adding comments to the code regarding the bug. I'll test further and see what I find.

So after some testing, I found that I didn't need the replacements, encoding the state parameter as base64 was enough for me to login using SAML with multiple identity providers enabled.
Interestingly though, it looks like you're already doing the same base64 replacements that I was doing in checkAuth inside of the generatePkceVerifier function when creating the pkceHash: https://github.com/aws-samples/cloudfront-authorization-at-edge/blob/master/src/lambda-edge/check-auth/index.ts#L87
Is there a reason to do it to the pkceHash and not the state variable before placing them in the query string?

The OAuth standard mandates to do it for PKCE. https://tools.ietf.org/html/rfc7636
NOTE: The code verifier SHOULD have enough entropy to make it
   impractical to guess the value.  It is RECOMMENDED that the output of
   a suitable random number generator be used to create a 32-octet
   sequence.  The octet sequence is then base64url-encoded to produce a
   43-octet URL safe string to use as the code verifier.

So that's the reason it was there already for pkce.
Are you all done with the PR?

I think you are all done :)
Merging now

THANK YOU @ButkiewiczP  for your PR


Charts API

Spotify recently made an update to their Spotify Viral Charts, which used to be available here: http://charts.spotify.com/.
They are now available only via the web player itself: https://play.spotify.com/chart/6o9o1UphRtyv10VPuDT80D and I was wondering if there is a Spotipy solution to grab the songs from the Viral charts into Python.
As an example, here is the Global Viral 50 chart I would like to pull data on: spotify:app:chart:6o9o1UphRtyv10VPuDT80D
Any help would be greatly appreciated.

Long time since this was opened, but in case you're still interested - Spotify is working on a new Charts page that'll replace the existing charts.spotify.com page, but it's not available yet.

there's spotifycharts.com which offers a download option of current and historical chart position data as csv

@drs-m, can confirm that it's official. There are however no public API endpoints to retrieve the charts data yet.

Related to https://github.com/spotify/web-api/issues/33. (Spotify's repository for tracking feature requests and bug tickets for its Web API

Closing for now as it's still not implemented by the web API


DBZ-6937 MySql connector get NPE when snapshot.mode is set to never and signal data collection configured

closes: https://issues.redhat.com/browse/DBZ-6937

@mfvitale Applied, thanks


Upgrade seneca to allow finer handling of timeouts

change stopping service message destination
Add handlers for the queue workers to be stopped and not keep running after the parent has been killed

Looks good!


Filter samples to choose from by using the selected process

When the user goes to add a new process, if there is an existing process that has been selected, limit samples to choose from the samples in the selected process.
This helps limit the size of the samples list.

Added filter by search and by selected node. User can click a checkbox to see all available samples.


Need For Specifiying All The Binders During Build Time In Sping Native

Hello,
I have a spring application running using Spring Cloud Stream Function(Spring Native). I am consuming some data using cloud function.  I generated a native docker image with spring-boot-maven-plugin.
Additionally, I read spring cloud stream properties from config-server. This is exactly where my problem starts. Actually, I have no problem reading properties from config-server. However, for native (AOT), it seems like I have to specify spring cloud stream binders at build time. But I want to get the binder configurations from config server during application startup as I have been doing before native.
Case 1:
If I configure the application to connect to the config-server while building the project, the code runs without any problem.
Related application.yml
spring:
  application:
    name: person-service
  cloud:
    config:
      enabled: true
  config:
    import: optional:configserver:http://config-server

What I see in your code is that If I build as shown above (fetching from config server during build time), the following classes are generated for all binders correctly. Then, afterwards there is no problem in getting these classes from applicationContext in runtime and use them(DefaultBinderFactory - getBinderInstance- this.binderChildContextInitializers.get(configurationName).initialize(binderProducingContext)). But unfortunately, I don't have the chance to access config server in build time. I did this for testing purposes. I can't work like this in Production.
Case 2:
spring:
  application:
    name: person-service
  cloud:
    config:
      enabled: false

Another option is to disable property reading from the config server at build time.
In this case, I enable config-server from docker-compose.yml to fetch the properties from the config server at runtime.
If I do it this way, the relevant classes for the binders are not generated that are supposed to be generated in build time. Then I get an error because these binders cannot be found in the runtime.

Case 1 - Classes Generated After Code Build (Config.Enabled = True)

Case 2 - Classes Generated After Code Build (Config.Enabled = False)

I am getting the error here. Because the binderChildContextInitializers instance in DefaultBinderFactory was not initialized with the relevant binders at build time. It seems like this is a must to fill the binderChildContextInitializers in native build.
Error :
org.springframework.context.ApplicationContextException: Failed to start bean 'inputBindingLifecycle'
        at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:182) ~[spring-context-6.0.11.jar!/:6.0.11]
        at org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:357) ~[spring-context-6.0.11.jar!/:6.0.11]
        at java.base/java.lang.Iterable.forEach(Iterable.java:75) ~[na:na]
        at org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:156) ~[spring-context-6.0.11.jar!/:6.0.11]
        at org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:124) ~[spring-context-6.0.11.jar!/:6.0.11]
        at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:958) ~[spring-context-6.0.11.jar!/:6.0.11]
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:611) ~[spring-context-6.0.11.jar!/:6.0.11]
        at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[spring-boot-3.1.2.jar!/:3.1.2]
        at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:734) ~[spring-boot-3.1.2.jar!/:3.1.2]
        at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:436) ~[spring-boot-3.1.2.jar!/:3.1.2]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:312) ~[spring-boot-3.1.2.jar!/:3.1.2]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1306) ~[spring-boot-3.1.2.jar!/:3.1.2]
        at org.springframework.boot.SpringApplication.run(SpringApplication.java:1295) ~[spring-boot-3.1.2.jar!/:3.1.2]
        at org.cloud.framework.service.milestone.app.MilestoneServiceApplication.main(MilestoneServiceApplication.java:20) ~[classes!/:6.0.0-SNAPSHOT]
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[na:na]
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
        at java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[na:na]
        at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49) ~[milestone-service-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:95) ~[milestone-service-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:58) ~[milestone-service-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
        at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:65) ~[milestone-service-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
Caused by: java.lang.IllegalStateException: Requested binder 'commonBinder' did not match available binders: [kafka]
        at org.springframework.cloud.stream.binder.DefaultBinderFactory.doGetBinderAOT(DefaultBinderFactory.java:206) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.cloud.stream.binder.DefaultBinderFactory.doGetBinder(DefaultBinderFactory.java:178) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.cloud.stream.binder.DefaultBinderFactory.getBinder(DefaultBinderFactory.java:167) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.cloud.stream.binding.BindingService.getBinder(BindingService.java:411) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.cloud.stream.binding.BindingService.bindConsumer(BindingService.java:108) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.cloud.stream.binding.AbstractBindableProxyFactory.createAndBindInputs(AbstractBindableProxyFactory.java:98) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.cloud.stream.binding.InputBindingLifecycle.doStartWithBindable(InputBindingLifecycle.java:67) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at java.base/java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:647) ~[na:na]
        at org.springframework.cloud.stream.binding.AbstractBindingLifecycle.start(AbstractBindingLifecycle.java:57) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.cloud.stream.binding.InputBindingLifecycle.start(InputBindingLifecycle.java:38) ~[spring-cloud-stream-4.1.1-SNAPSHOT.jar!/:4.1.1-SNAPSHOT]
        at org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:179) ~[spring-context-6.0.11.jar!/:6.0.11]
        ... 21 common frames omitted

I kind of get that these should be initialized during build time but how can we get over this situation (fetching binders during application startup)? Recently, I have been opening pull requests for problems caused by Spring Native.  If you direct me, I can make the development and open a pull request.

See this too: https://docs.spring.io/spring-cloud-config/docs/current/reference/html/#_aot_and_native_image_support_2

Thank you very much for your explanations @sobychacko . I try to contribute to your community as much as I can. I want to say some things. Actually, we can fetching configuration from config-server. Wouldn't it be more useful if we went for another solution instead of creating a class for each binder in your source code? Since I don't know the code as much as you do, I might be giving a ridiculous idea.
I will also try to spend more time review into your code.

Wouldn't it be more useful if we went for another solution instead of creating a class for each binder in your source code?
Not sure I follow. In Spring Cloud Stream, we create child contexts for the binders in order to support multi-binder-based applications. This is fundamental to the binder bootstrapping architecture and hard to change. Is this what you meant?

Yes. Let me try to explain to you what I tried.
There is no problem in fetching data from the Config server at runtime in a spring native project.
However, in a native spring project, spring cloud wants me to specify stream binders at build time.
This time, I will have to rebuild the code every time the binder configuration changes.
This is a very difficult development process for me. I'm wondering if the binder creation mechanism can be modified to find a solution to this.
Also, I didn't look too closely. Do I need to specify other configurations at build time?
For example; Do configurations under bindings need to be specified at build time?

All information that needs to be run in AOT and native mode must be provided at the build time so that the AOT engine can build the context. Please take a look at the docs I linked above for details. Any Spring context modifying operations are not permitted when running AOT mode as everything needed to run in AOT mode is already created at build time.

Thank you @sobychacko. I will do more research on native and read the resources you provided. Maybe I'll come back after I learn more.
😊

@sobychacko Would you like me to close the issue because I couldn't explain the problem clearly?

@omercelikceng If you want to close the issue, that is fine. I think you explained the problem really well. The thing is that because of the AOT limitations, it is very hard to achieve a solution in this case. If you want to close this issue and ponder on an alternative solution, that is fine with us. We can always link this issue if you send a PR related to this.

@sobychacko . I re-read all of our conversations today. I realized that I couldn't explain myself well. If it's okay for you, I'll try to open a pull request.
What I am trying to suggest is; we are using spring prototype beans for these cases. I know that for AOT runtime code generation is not possible. But instead of generating specific classes for each binder at the build time, if we use a generic prototype bean and create a different instance for each binder during runtime, it will be both suitable for AOT and JIT. By this way, may be the fundamental bootstrapping architecture will not be changed too much, and still we have different instances for binders at the runtime.

@omercelikceng the PRs are always welcomed. so you don't have to ask ;)
But based on my understanding of what you are proposing, it will be a fundamental change in the architecture of s-c-stream as @sobychacko pointed out earlier.
Regardless, going through this effort would probably help you as well to understand what we are dealing with.
That said, there are few things that the greater s-c-cloud team is working on, specifically to deal with AOT and Config server.
Feel free to close this issue if you want to

Got it @olegz. Thank you very much to both you and @sobychacko for your explanations. You know the project better than me and you have much better experience than me. I have infinite respect for you, @sobychacko and spring cloud stream team. I just wanted to talk about this issue because I think it's important. But I care about what you say and will take it into consideration. Instead of spending effort on this issue, I will try to solve other issues. Thank you very much again.


Update environment variables passed to harv-install script

Update the environment variables passed to the harv-install and cos-installer-shutdown script for elemental command. Do notice that elemental uses different names for several installation options, so we also need to adapt these new names in harv-install script.
We don't have to update the base-os version yet because elemental already exists in the current base-os: https://github.com/harvester/os2/releases/tag/20220407.
HarvesterConfig.Install fields and their corresponding environment variables

ForceEFI: ELEMENTAL_FORCE_EFI
Device: Positional arg or ELEMENTAL_TARGET
ConfigURL: ELEMENTAL_CLOUD_INIT
Silent: No env var. Must be specified by CLI arg --quiet
ISOURL: ELEMENTAL_ISO
PowerOff: ELEMENTAL_POWEROFF
NoFormat: ELEMENTAL_NO_FORMAT
Debug: No env var. Must be specified by CLI arg --debug
TTY: ELEMENTAL_TTY
ForceGPT: ELEMENTAL_FORCE_GPT

Not in HarvesterConfig.Install but still required

Custom partition layout file: ELEMENTAL_PARTITION_LAYOUT

Todos

[x] Test PXE installation
[x] Air-gapped installation
[x] Upgrade from older version of Harvester
[x] Use elemental command to upgrade OS: https://github.com/harvester/harvester/pull/2166

Rebrand error:

[x] Fix realpath: /run/netconfig/yp.conf: No such file or directory

elemental bug: https://github.com/rancher-sandbox/elemental/issues/164
Temporarily solved by add the symlink /var/run -> /run directly in harv-install script

[ ] (Will submit other PR) Move the environment variables adaptation code from harv-install to Go
[ ] (Will submit other PR) Develop some automated tests for base OS verification

Related issues

https://github.com/harvester/harvester/issues/2133

Hi. Could you provide a link to changelog or elsewhere you found those changes?

Hi. Could you provide a link to changelog or elsewhere you found those changes?

Names of those environment variables are automatically generated by viper and cobra. For example here and here. Currently, there is no document about this yet, so I manually tested all the environment variables.


fathest points

find fathest points in each cluster ?

See https://github.com/bdelespierre/php-kmeans/issues/2


Permissions error when saving CLOB content to a file (Windows 10)

When you try to save the content of a CLOB field to a file via right-click option, DBeaver raises a "Unable to write to temp folder" error.
This happens when DBeaver is executed normally. If DBeaver is launched as admimistrator, the CLOB content is successfully saved.
NB: I found this issue on a Sybase DB using a Windows 10 client machine, but I think this error is common to all DBs.

Can't reproduce.
In fact there is no such error "Unable to write to temp folder" in DBeaver, this seems to be an OS error.
Please post full stacktrace of that error (from Error Log).


Add discard support for ceph backends

Can one of the admins review this PR? @fpytloun is that you?


How are you using Legend?

Hi Legend community! We know that several organizations (banks and non-banks) are evaluating Legend, and we are looking to surface adoption of FINOS projects (see the FINOS FDC3 project as an example).
That being said, we currently aren't able to disclose the names of those organizations, feel free to comment on the issue below to let us know how you're using Legend

Closing this issue as stale. Please re-open if relevant.


DS-2579: Accepting string labels

reason: allow octopod to take string labels as well as encoded labels. Basically the strategy is to use sklearn encoders to handle the incoming data in the dataset classes. The dataset classes then pass the label mappings to the dataloader class and when the learner is created it checks the train and val data loaders to make sure the label mappings are the same (a potential issue is that since the encoders are run on each dataset you might not have a certain class represented and so your train and val sets would have different label maps... which would be bad)
It looks long but is mostly tests... 4 for each of the image, text, and ensemble datasets. 2 for multi class and 2 for multi label. testing to make sure it loads with both string and ints and then checking to make sure it catches errors in loading if the label mappings are different between train and val datasets.
Note: I could just pass the class lists back and forth rather than the mappings I make. And I think they are ordered alphabetically by the encoder... But am passing the mapping bc I kinda like having it map to a node number so it could be used in the situation of a predict function where we wouldn't have to pass the sklearn label encoder around and save that places to use the inverse transform function in a preduct function.

Pull Request Checklist

[x] All tests in the tests folder pass with a local build
[x] Pull request includes a description of why we are doing this
[x] Init files import new capabilities to appropriate level of package (if applicable)
[x] CHANGELOG has been updated
[x] Version in _version.py has been updated
[x] README has been updated (if applicable)
[x] requirements.txt and requirements-dev.txt have been recompiled if requirements in setup.py or requirements-dev.in changed.

Also @sugi-chan can we make a ticket to update tutorial notebooks to use this new label encoder strategy?


Verify column and table name exists before SQL execution

keep the processing engine as lean and high performing as possible. will delegate this to the database and report the problem in detail in case of any db error.


feat(bench): Add callgrind benches for jolt-core

Adds benches for iai-callgrind in jolt-core as outlined in #291.
I had an issue importing the msm module so I created a separate benches folder in jolt-core, happy to refactor this or adjust the path.

Thank you! Just a quick cargo fmt and I'll merge this

@moodlezoup Done!


[fix] Updating parse_human_timedelta typing

CATEGORY
Choose one

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
This PR fixes a regression introduced in https://github.com/apache/incubator-superset/pull/8409 as per the typing for parse_human_timedelta I was led to believe that s needed to be a str yet it was being passed a type of Optional[str].  The logic I added in QueryObject turned out to be wrong as in fact s was of type Optional[str] per: https://github.com/apache/incubator-superset/blob/9fc37ea9f1ff032dea923012613d4e7189ada178/superset/utils/core.py#L303
TEST PLAN
Added additional unit test.
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
to: @etr2460 @graceguo-supercat @michellethomas @mistercrunch

Codecov Report

Merging #8436 into master will not change coverage.
The diff coverage is 50%.

@@           Coverage Diff           @@
##           master    #8436   +/-   ##
=======================================
  Coverage   67.61%   67.61%
=======================================
  Files         448      448
  Lines       22486    22486
  Branches     2364     2364
=======================================
  Hits        15204    15204
  Misses       7144     7144
  Partials      138      138

Impacted Files
Coverage Δ

superset/common/query_object.py
50% <0%> (ø)
:arrow_up:

superset/utils/core.py
88.55% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Command SwiftCompile Failed - Main Actor-Isolated Context Issues in Xcode 15

Bug Description, Steps to Reproduce, Crash Logs, Screenshots, etc.

Title: Command SwiftCompile Failed - Main Actor-Isolated Context Issues in Xcode 15
Description:
After installing the app dependencies, I am unable to build the project in Xcode 15. The build process fails with the following errors:

Command SwiftCompile failed with a nonzero exit code.

Multiple errors related to main actor-isolated calls in a synchronous nonisolated context, specifically:

Call to main actor-isolated static method 'window(for:)' in a synchronous nonisolated context.
Call to main actor-isolated static method 'togglePresented(for:)' in a synchronous nonisolated context.
Call to main actor-isolated static method 'setPresented(for:state:)' in a synchronous nonisolated context.

Steps to Reproduce:

Open the project in Xcode 15.
Attempt to build the project (Cmd + B).
The build fails with the errors listed above.

Expected Behavior:
The app should build successfully in Xcode 15.
Actual Behavior:
The build fails due to multiple errors involving calls to main actor-isolated methods from a synchronous nonisolated context.
Environment:

Xcode Version: 15
Swift Version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>)
macOS Version: 14.2.1

The compatibility updates for Swift 6 in release 1.2.0 may have bumped the Xcode version requirement as well. Let me check and see what needs adjusting.

I can see what's going on. In Xcode 15, SwiftUI's View and Scene are not implicitly @MainActor but in Xcode 16 they are.
I can push an update that resolves Xcode 15 builds soon.

Fixed in release 1.2.1.


Fan control working?

hey I do have a similar laptop vivobook 15 x515ja with ice lake
fan control working

My laptop fan is working fine

hey I do have a similar laptop vivobook 15 x515ja with ice lake
fan control working

My laptop fan is working fine

hey I do have a similar laptop vivobook 15 x515ja with ice lake
fan control working

My laptop is normal except for hdmi because it is not officially supported

Fan control??

Fan control??

The fan control is normal. When the temperature rises, the fan will rotate independently. When the temperature is normal, the speed will slow down.


Why port 587 not using self generated CA Certificate?

Before reporting a bug, please see our FAQ in FAQ.md!
Description
https://github.com/WhatsApp/proxy/blob/main/FAQ.md#5-does-the-proxy-support-https-or-socks
It is indicated here that this proxy is just passing TCP traffic around.
If that is the case, why need to generate a random CA Certificate?
https://github.com/WhatsApp/proxy/blob/2ea2f1fee80a065a4600ac43e3dec0f659e1c7df/proxy/src/generate-certs.sh#L25-L47
Since a random CA Certificate is generated for port 443, why doesn't port 587 use this same CA Certificate but chooses to use the official WhatsApp one?
This makes media fails in places that block WhatsApp.
Failed Step
The use of offical WhatsApp cert makes media fails in places that block WhatsApp.

Yes, that’s the problem

@Nicepaul do you know of a workaround?

@Nicepaul do you know of a workaround?

I'm not deploying a WhatsApp proxy on a VPS; I'm setting it up on my home OpenWRT router to bypass issues with media not working. However, the prerequisite is that the OpenWRT router must be able to successfully bypass the firewall restrictions.

Does the proxy behave differently on different hardware?
The proxy has to be located outside the restricted network.

Does the proxy behave differently on different hardware? The proxy has to be located outside the restricted network.

This is not hardware-related. I’ve installed Passwall or SSRPlus on OpenWRT to bypass the Great Firewall of China, essentially setting up a VPN. All internal network applications and data, including WhatsApp, are routed through this tunnel, so the data packets are transmitted within the VPN and won’t be intercepted by the firewall. I’ve then mapped WhatsApp’s port to the public IP of the OpenWRT router. This is essentially a workaround to bypass WhatsApp’s certificate issues

I'm a little confused, if your mobile's WhatsApp is connected to the router which has VPN, why does it still need a proxy?

I'm a little confused, if your mobile's WhatsApp is connected to the router which has VPN, why does it still need a proxy?

I want to use WhatsApp but prefer not to install a VPN app on my phone. Therefore, setting up a WhatsApp proxy on my home OpenWRT router seems like a good solution. Additionally, VPNs tend to drain battery and can significantly affect phone network performance, making it impractical to keep them always on. However, turning it off would disrupt WhatsApp communication.

ping @eozturk1


error upgrading connection: unable to upgrade connection: pod does not exist

Environmental Info:
K3s Version:
root@k8sopa1:/home/vagrant# k3s --version
k3s version v1.23.8+k3s2 (fe3cecc2)
go version go1.17.5

Helm Version
helm version
version.BuildInfo{Version:"v3.7.0", GitCommit:"eeac83883cb4014fe60267ec6373570374ce770b", GitTreeState:"clean", GoVersion:"go1.16.8"}

Node(s) CPU architecture, OS, and Version:
created below VM using oracle virtual box and vagrant
Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-122-generic x86_64)

Cluster Configuration:
NAME      STATUS     ROLES                  AGE   VERSION
k8sopa3   Ready   <none>                 27h   v1.23.8+k3s2
k8sopa2   Ready      <none>                 27h   v1.23.8+k3s2
k8sopa1   Ready      control-plane,master   27h   v1.23.8+k3s2

installation Link
**Master Node** :-curl -sfL https://get.k3s.io | sh -s - --docker
**worker Node** :- curl -sfL https://get.k3s.io | K3S_URL=https://MasterIP:6443 K3S_TOKEN=Nodetoaknfromaster sh -

Describe the bug:
getting error **error: error upgrading connection: unable to upgrade connection: pod does not exist**
while executing command **kubectl --namespace default port-forward firstapp-firstchart-fcd8676b9-kqcrq 8080:80**

Steps To Reproduce:
- Installed K3s: using link provided in installation steps
- Install helm using snap install helm --classic
- helm create firstchart
- helm install firstapp firstchart/
- kubectl get pods
- kubectl --namespace default port-forward Pod_name 8080:80

Expected behavior:
it should need to successfully forward port form 8080 to 80
like below
Forwarding from <IP_ADDRESS>:8080 -> 80
Forwarding from [::1]:8080 -> 80

Actual behavior:
it is giving error like although pod is exist :-
error: error upgrading connection: unable to upgrade connection: pod does not exist

Can you include the kubectl get pods output showing that the pod in question actually exists? At this point it just looks like you've got a typo or something.

Hi, I had the same error today after starting a node and running the port-forward command. I tried again after a few minutes and the command could be executed successfully. In my case I guess not all istio components had finished starting. Maybe it helps.


Fix CI on windows

Running the compiled executable fails on windows. This should be fixed.

Windows unfortunately doesn't have an equivalent of rpath -> path need to be given to find the libs.
Fixed by 1217915


Guidance for improving time taken in video compression

Sharing some statistics that I observed using this library
2.32 MB -> 1.05 MB in 3 sec
4.5 MB -> 2.359 MB in 10 sec
38.2 MB -> 21 MB in 75 sec
KEY_BIT_RATE - 0.5 times of original bit rate
KEY_I_FRAME_INTERVAL - 5
KEY_FRAME_RATE - 30
I tried with keeping and modifying dimension as well.
Time taken for smaller videos is great but i have concern for larger videos.
Please guide how can I lessen the time required for compressing larger videos.

Thank you for reporting this!
LiTr relies on MediaCodec, which usually uses hardware codecs to provide maximum performance. We can try to dig in deeper to see what is going on on your device.
Couple of question, which might help to understand what is happening. By "larger" do you mean "longer" or "higher resolution" video? And can you check which encoder/decoder codecs are
being used for each of those videos? I wonder if device is switching to less performant codec.

By larger I mean size of the video. I installed 1 application to check codec, it showed codec as Advanced Video Codec for all videos.
The videos which are taking more time (>1 min) are having larger size (>40MB) but its resolution (width and height) is low. May be these videos are already compressed. I checked other larger sized videos ~50MB whose resolution is also high, they took lesser time ~15 SEC. Do we have a way to figure out that the video is already compressed and no more compression is required?

LiTr does not automatically skip transcoding, and that is done on purpose - we believe that this should be done by clients before calling LiTr, as such decisions are usually driven by client's business logic. On some occasions, clients might need to do an opposite and increase resolution/bitrate - for example, to upscale a video after editing it.
Is it possible to share those videos? We could investigate on our end.


Investigate if terraform service principal is being used

We need to double check if we're actually running the terraform as the terraform service principal instead of the current user. These variables in the generated terraform.tfvars are not used in the azurerm provider here. https://github.com/retaildevcrews/caf-terraform-landingzones-starter/blob/05181f1b864d96f603909af8b877929eaa3ce2c2/enterprise_scale/construction_sets/aks/main.tf#L42-L48
Docs on the azurerm provider. https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/service_principal_client_secret
Acceptance criteria:

Investigate use of terraform service principal
Create a bug if terraform is not configured to use service principal

refs: https://github.com/retaildevcrews/ngsa/issues/701

I think we need to define the scope and the meaning of having Terraform configured to use a service principal.

We are not currently using SP to run terraform,  besides as part of provisioning script stabilization issues #709, #704 and #705 removed  components such as Key-Vault and SP creation logic, since it was not working correclty.
Instead Azure logged in user must have enough permission to create all Azure resources.

A new task suggesting an approach for SP implementation was created, Issue #726


remove custom reset handling from nrf54h20/nrf9280 jlink scripts

Update the JLink scripts for nrf54h20dk/nrf9280pdk to work with the latest secure domain firmware v9.0.0

Do we have this new behavior documented somewhere? it seems like this change is quite substantial for there not to be a debugging guide somewhere, maybe even a migration guide entry

No good point, I don't think it is tracked yet and will try to add something for it

Do we have this new behavior documented somewhere? it seems like this change is quite substantial for there not to be a debugging guide somewhere, maybe even a migration guide entry

No good point, I don't think it is tracked yet and will try to add something for it

@bjarki-andreasen https://github.com/nrfconnect/sdk-nrf/pull/19608


Avoid using to/from_pandas in Categorify/GroupbyStatistics

Addresses Categorify bug related to int->float casting in to_pandas (by using pyarrow in lieu of pandas).  Implements this suggestion from the discussion in #354

rerun tests

rerun tests

rerun tests

rerun tests


Simplify CFString's Get MaximumSizeForEncoding so its program flow is clearer

CFString's Get MaximumSizeForEncoding method is not clear in that the else branch ALWAYS following the rest of the method due to early returns.
Because the two top branches always return, I removed the else statement, and put encoding & 0xFFF in the switch statement itself instead of modifying the encoding directly.

@swift-ci test

@swift-ci test

Thank you!


Update open-the-exchange-management-shell.md

The “All Apps” option is disabled by default after the build 14942 for Windows 10. As far as I know for the Windows Server 2016 there is no “All Apps” option.

OPS Build status updates of commit 0a4d0a7:
:clock10: Preparing: average preparing time is 1 min(s) 12 sec(s)

OPS Build status updates of commit 0a4d0a7:
:clock10: Incremental building: average incremental building time is 12 min(s) 23 sec(s)

OPS Build status updates of commit 0a4d0a7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/exchange-server/open-the-exchange-management-shell.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


cursor disappears on completion of execution

system: ubuntu 22.04
Whenever a graphrag.* module is executed, the terminal cursor is turned off.  Annoying.
### Tasks

I believe this is an artifact of how we’re displaying data frames and progress during the indexing/query process. Our goal is to display to users regular updates.
As an alternative approach, you can run the CLI commands and send them to a background process which would hide all stdout.
Closing this issue for now but we welcome all contributions.


[BUG] - Error on invalid injection

Describe the bug
If blocker.js isn't properly injected into the website, the extension will fail to send the toggle state message to it, as the listener will have never been created. This throws an error.
To Reproduce
Steps to reproduce the behavior:
(Only tested on Edge)
The easiest way to reproduce this is:

Open up the extensions page and add it through the developer mode.
Try running the extension, without letting blocker.js get injected.
Nothing will happen, but an error will be thrown.

Expected behavior
blocker.js should attempt to remove any ads on the page.
System/Browser info

OS: Windows 11
Browser Microsoft Edge (chromium)

Solved issue by checking for the error.


Pathological liar breaks zombie accent

i think i can fix it, but just want to specify the better way to do it

set ReplacementChance in ReplacementAccentPrototype to 1 in ZombieSystem.Transform.cs
https://github.com/space-wizards/space-station-14/blob/40802738ec84496cb55ad824bf0f94ed7a7916c6/Content.Server/Zombies/ZombieSystem.Transform.cs#L110-L113
make ReplacementChance applied only to wordReplacements, not FullReplacements
https://github.com/space-wizards/space-station-14/blob/40802738ec84496cb55ad824bf0f94ed7a7916c6/Content.Server/Speech/Components/ReplacementAccentComponent.cs
https://github.com/space-wizards/space-station-14/blob/40802738ec84496cb55ad824bf0f94ed7a7916c6/Content.Server/Speech/EntitySystems/ReplacementAccentSystem.cs#L25-L31

would like to hear any other proposals

Seems to me like ReplacementChance should be a field in ReplacementAccentPrototype, rather than ReplacementAccentComponent.


SendActivityAsync intermittently errors with No such host is known. (directline.botframework.com:443)

Version 4.193
Describe the bug
When calling  SendActivityAsync  it intermittently  throws an exception System.Net.Http.HttpRequestException : No such host is known. (directline.botframework.com:443). This is causing issues for our customers.
To Reproduce
There are no defined steps to reproduce as it happens intermittently
Expected behavior
For SendActivityAsync  to send the message
Additional context
The channel the bot is using is webchat
Stack trace
System.Net.Http.HttpRequestException : No such host is known. (directline.botframework.com:443)
at System.Net.Http.HttpConnectionPool+d__97.MoveNext
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
at System.Net.Http.HttpConnectionPool+d__96.MoveNext
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
at System.Net.Http.HttpConnectionPool+d__98.MoveNext
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
at System.Net.Http.HttpConnectionPool+d__73.MoveNext
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
at System.Threading.Tasks.TaskCompletionSourceWithCancellation1+<WaitWithCancellationAsync>d__1.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at System.Net.Http.HttpConnectionPool+<GetHttp11ConnectionAsync>d__75.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at System.Net.Http.HttpConnectionPool+<SendWithVersionDetectionAndRetryAsync>d__83.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at System.Net.Http.DiagnosticsHandler+<SendAsyncCore>d__8.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at System.Net.Http.RedirectHandler+<SendAsync>d__4.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at System.Net.Http.HttpClient+<<SendAsync>g__Core|83_0>d.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Connector.Conversations+<SendToConversationWithHttpMessagesAsync>d__7.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Connector.ConversationsExtensions+<SendToConversationAsync>d__14.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.CloudAdapterBase+<SendActivitiesAsync>d__9.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.TurnContext+<>c__DisplayClass31_0+<<SendActivitiesAsync>g__SendActivitiesThroughAdapter|1>d.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.BotTranscriptLoggerMiddleware+<>c__DisplayClass2_0+<<OnTurnAsync>b__0>d.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.AnalyticsMiddleware+<>c__DisplayClass4_0+<<OnTurnAsync>b__0>d.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.TurnContext+<SendActivityAsync>d__30.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.Adaptive.Input.FlowAdaptiveCardRenderer+<RenderPrompt>d__28.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.Adaptive.Input.FlowAdaptiveCardRenderer+<BeginDialogAsync>d__25.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogContext+<BeginDialogAsync>d__32.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.Adaptive.Actions.ActionScope+<BeginActionAsync>d__17.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Flow.FlowActionDialogContainer+<BeginActionAsync>d__13.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.Adaptive.Actions.ActionScope+<BeginDialogAsync>d__6.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogContext+<BeginDialogAsync>d__32.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.Adaptive.Actions.ActionScope+<BeginActionAsync>d__17.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at Microsoft.Bot.Builder.Dialogs.DialogContext+<BeginDialogAsync>d__32.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.ComponentDialog+<BeginDialogAsync>d__7.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Flow.FlowAssistantDialogBase+<BeginDialogAsync>d__15.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogContext+<BeginDialogAsync>d__32.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.ComponentDialog+<BeginDialogAsync>d__7.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogContext+<BeginDialogAsync>d__32.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Main.MainDialog+<ProcessTurnAsync>d__11.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.ComponentDialog+<BeginDialogAsync>d__7.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogContext+<BeginDialogAsync>d__32.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogExtensions+<InnerRunAsync>d__2.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogExtensions+<InternalRunAsync>d__1.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at Microsoft.Bot.Builder.Dialogs.DialogExtensions+<InternalRunAsync>d__1.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.Dialogs.DialogExtensions+<RunAsync>d__0.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Main.DialogBot+<OnTurnAsync>d__6.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.SetLocaleMiddleware+<OnTurnAsync>d__2.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Debugger.BotDebugMiddleware+<OnTurnAsync>d__2.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.BotTranscriptLoggerMiddleware+<OnTurnAsync>d__2.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.AnalyticsMiddleware+<OnTurnAsync>d__4.MoveNext in    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.UserIdentifyingMiddleware+<OnTurnAsync>d__7.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.AssistantIdentifyingMiddleware+<OnTurnAsync>d__2.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at BottKitt.Bot.Middleware.CustomShowTypingMiddleware+<OnTurnAsync>d__3.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.RegisterClassMiddleware1+d__7.MoveNext
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
at Microsoft.Bot.Builder.RegisterClassMiddleware1+<OnTurnAsync>d__7.MoveNext    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification    at Microsoft.Bot.Builder.RegisterClassMiddleware1+d__7.MoveNext
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
at Microsoft.Bot.Builder.MiddlewareSet+d__3.MoveNext
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification
at Microsoft.Bot.Builder.BotAdapter+d__23.MoveNext
System.Net.Sockets.SocketException : No such host is known.

I see the same problem on something that I've been working on, its quite frustrating

I second the earlier comment, as I've come across this exception too: it is frustrating.

Version Microsoft.Bot.Builder 4.193
Webchat version 4.15.8
Yes using .net

@Rich-biomni, @JamesASinclair, @agentandy
I will attempt to reproduce the issue, though I am unsure how successful I might be given the intermittent nature of the issue. Are there any other details about the implementation that you can provide that might help?

@anishprasad01
Thanks for looking into this appreciate its a tricky one. Looking at the stack trace it looks like our code was calling TurnContext.SendActivity.
Googling the error HttpClient  System.Net.Sockets.SocketException : No such host is known.  You get hits about DNS issues and how usage's of HttpClient can impact that.
https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests?WT.mc_id=DT-MVP-5003978
https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/http/httpclient-guidelines
Is the BotFramework code 'new-ing' up HttpClients? or is it using IHttpClientFactory. Is there a HttpClient retry strategy in place like using Polly?

@Rich-biomni,
How are you hosting your Web Chat?

@anishprasad01  sorry not really what you mean?
The entire application is hosted in azure. The botframework is hosted in an App Service in .net C#, The web site is also an App Service. The web site is written in Vue  using an npm package "botframework-webchat": "^4.15.8" for the web chat component, though customers host their web chat component using the script from 'https://cdn.botframework.com/botframework-webchat/latest/webchat.js'

Is CloudAdapter or BotFrameworkHttpAdapter being used?
BotFrameworkHttpAdapter does not support use of IHttpClientFactory.  Rather, it supports a RetryPolicy and a custom HttpClient.  This is the original BotFrameworkAdapter provided.  If the bot was created some time ago, it's likely this would be in use.
CloudAdapter replaces that and supports IHttpClientFactory if enabled.  If not enabled (via the AddHttpClient call), it will perform as BotFrameworkAdapter does.
There are a few places, related to auth where a specific HttpClient is created outside IHttpClientFactory.  But for all the messaging around communicating with Azure Bot Service/SMBA, the factory would be used.

Thanks for the reply tracyboehrer. In my case, we'd an adapter that implemented CloudAdapter but was calling base using the CloudAdapter(BotFrameworkAuthentication, ILogger) constructor. We hadn't configured an IHttpClientFactory for that so I've updated it to use the DefaultHttpClientFactory and I'll see if it occurs again. Fingers crossed

Hi @JamesASinclair, @Rich-biomni Any status update on this issue?
Have you had a chance to extend the CloudAdapter class and use the IHttpClientFactory overloaded constructor in your derived adapter to see if that fixes this issue?

Hi @JamesASinclair, @Rich-biomni Any status update on this issue?
Have you had a chance to extend the CloudAdapter class and use the IHttpClientFactory overloaded constructor in your derived adapter to see if that fixes this issue?

The change we put in is making its way to production at the minute, but hasn't yet been deployed. Its been an intermittent problem so it will be a while before I'd be confident to say its resolved. Hope that answers the question.

Closing due to inactivity. Please reopen if further assistance is needed.


Can't not add code with "new" function

In my project, I need to change Tc and When I want to add code like "int *t = new int;" in thread_cache.h.Then Tc throws serious exceptions. Besides, the error message changes and is not always the same.
I guess that this issue happens because of some lock. But I don't get confirmation now.
Thanks for help!

I think I figure out the reason. "new" function has already been hooked.

Yes, calling operator new from inside operator new can't work.


Duplicate entries in visual studio code workspaces

Microsoft PowerToys version
0.45.0
Running as admin

[ ] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
Open PowerToys Run and search for VSCode workspaces
✔ Expected Behavior
No duplicates entries
❌ Actual Behavior
There duplicates of every VSCode workspace
Other Software
VSCode insiders

Sorry had user and system installed vscode :)

Same issue, how to fix it?

@Ahai-8 Please open a new issue and clarify your issue (A screenshot would be great). Thanks!


Missing index.html

After running 'node node_modules/jsdoc/jsdoc.js -c node_modules/angular-jsdoc/common/conf.json', we were able to properly produce our html jsdocs except for the index.html.
Any possible idea of what could be causing this issues?

Do you have README.md?

Yes

As you see here,
node_modules/jsdoc/jsdoc.js --configure common/test_conf.json --template angular-template --destination angular-template/docs --readme sample-codes/README.md --recurse sample-codes
This --readme has to be there to make index.html
 --readme sample-codes/README.md

Oh ok.  Thank for clarifying that.  I am a bit new to this stuff.

So i doubled checked and yes, the readme file actually was already there as I did do the changes as stated in the instructions....


model card misreports SDXL type

I downloaded the latest AnimagineXL from
https://civitai.com/models/122533?modelVersionId=133462
The autogenerated card says it is type "SDXL 0.9 Base"
But the writeup at civitai, very specifically says it is "SDXL 1.0 Base"

This is a mistake in that model, not swarm -- the model type is determined by either (A) ModelSpec metadata -- https://github.com/Stability-AI/ModelSpec - or (B) by autodetection from model content for legacy models.
ModelSpec is a mandatory component of "SDXL 1.0". Any model with the same tensor architecture layout, but lacking ModelSpec, is in fact an SDXL 0.9 model. If the model author used SDXL 1.0 but removed the ModelSpec metadata from their uploaded model, they broke spec and did therefore in fact upload what is technically an SDXL 0.9 model.
Swarm makes it easy to fix that though -- just click the hamburger menu next to the model, and click "Edit Metadata", and change the Architecture from 0-9 to 1: stable-diffusion-xl-v1-base. This will automatically add correct modelspec metadata to the model file.


Initialize Regex lazy in BasicHtmlWebResponseObject

PR Summary
Reorganize regex in BasicHtmlWebResponseObject.Common.cs

PR Context
DIscussed with @iSazonov in #19359
Used the same conventions found here:
https://github.com/dotnet/runtime/blob/673afec8a76cb4437eba318d7132140b7da9b111/src/libraries/Common/src/System/Data/Common/DbConnectionOptions.Common.cs#L50

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@CarloToso Please look CodeFactor issues.


Shareability of links to Playground and their parameters

Right now Playground is only checking for a manifest but longer term, it should support more search parameters e.g. text fragment to share more precisely into an OpenAccess publication for instance.
We will try listing and documenting all these params in this issue.

I think that in the case of mobile, shareability could also extend to support the share() method as an action: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/share

support the share() method as an action

I'm assuming this could also take different forms? E.g. action, entry in popover menu when highlighting text, buttons in a list of saved highlights, etc.?
So same logic, but the actual output is contextual (publication as a whole, text fragment in a resource, etc.).

That's right. Initially, we could implement this as an action where the user can include the current position as an option.
The nature of what is shared (URL, text, media…) has an impact on what the native share intent/screen displays to the user on Android and iOS.


Dynamic (native) module loading not supported

After trying to use these modules, it seems that they cannot load dynamic modules like bcrypt, for example.
I found this issue https://github.com/smebberson/docker-alpine/issues/52 which seems to highlight the --fully-static compilation flag as being responsible for this and noticed that it is indeed passed here.
Would it be possible to get these images to work in a way that supports dynamic module loading, but is still rather small?

@alanpearce I'm just curious: Are you using native modules that you had to write yourself, or is it something leftover from the dark ages of node before we had built-ins? I'm just wondering what in node (other than native desktop apps) still need native modules and why (because some of those problems I'm interested in tackling).

It seems to be the bcrypt module, although there could be others. We haven't written anything native ourselves.

A lot of npm modules uses native bindings.
bcrypt, node-sass, sqlite (IIRC), mysql [?].
@alanpearce How much is "rather small" for you?
I've done "rather small" images: https://hub.docker.com/r/dzek69/nodemin/tags
(Size listed on docker hub = transfer size (compressed), container size is 53.5MB) and these should work with dynamic modules
How these are built? I'm taking node alpine official image and simply removing everything that's not needed (npm and yarn for example). System tools are left untouched (so wget and all these are working, busybox, which provides these is 8MB big IIRC). After removal image is squashed into single layer.
See here for Dockerfile: https://github.com/dzek69/docker-node-minimal/blob/master/build/Dockerfile.node - and here: https://github.com/dzek69/docker-node-minimal for more information. Building images by yourself is far from perfect (I'm not good at bash scripts), but it works.
I'm using these on production without any issue.
Sorry for kind of advertisement. I made this project when I discovered scratch-node wasn't working for ARM even when building by myself (https://github.com/astefanutti/scratch-node/issues/1) and instead of waiting - I just did what it was possible to get as small images as possible without being "too raw".

@dzek69 Those images are pretty cool. We would like to avoid having any kind of tools in the image though. It looks as though there's a pending distroless/node PR which might work for us.
Thanks for the tips though

This should be fixed with 1da3813014732243c85799b646a38a221d292c39.
I've re-pushed the latest, 12.2.0, 12.2 and 12 tags so you can give it a try.
On my side, I've tested it successfully for amd64 and arm32v7.
Thanks for you patience!

Thanks for the new feature! Would it be possible to backport it to node 10? We'd like to stick to LTS versions on production. Node 12 will enter LTS at the end of October. I tried building the image locally and it seems to have worked

@alanpearce yes, all the documented images have been updated already, so 10, 10.16, 10.16.0 should have support for native modules.

Oh, great, thanks! I must've misunderstood the previous message. :ok_hand:


Add FEETECH BUS Servo library for Arduino and ESP32

Hi:)
Could you please add this library to the library manager?
https://github.com/ftservo/FTServo_Arduino
Thanks!

Hi @ftservo . We have a new system for submitting libraries. Please follow the instructions here:
https://github.com/arduino/library-registry#adding-a-library-to-library-manager
Let me know if you have any questions.
Regards, Per


May be an error in yolov3

This is my mistake, I found that I set trainable to False, Sorry!

Okay!
Close the issue!


how to disable to change matching brackets highlighter

VSCode Version: 1.7.2
OS Version: Win 7 (64-bit)

how to disable or change rectangular matching brackets highlighter. it's really very annoying specially when you have only empty pairs of brackets. is there any setting(s) to disable this or change it to something to look like as in sublime or notepad++.

Hi, I was able to make the necessary changes on my local repository but I'm unable to commit my changes for one of the files editorCommon.ts. I think I'm following all the necessary guidelines as per the Contributing guidelines (configuration shown in screenshot).

Can someone please help me with this so I can attempt a PR?


GCC EM3 doesn't seem to support paginated report deployment

No mention of it in the article, but this doesn't seem to apply to the GCC Tenants. We have an EM3 SKU but the options to deploy paginated reports isn't available to enable this functionality. Tried testing the deployment of paginated reports to a premium capacity and it failed.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0feb8663-445d-8536-37ae-068672c7a5b9
Version Independent ID: 4818af9e-c69b-0fbe-a106-0d1d711b9f0d
Content: Publish a paginated report to the Power BI service - Power BI
Content Source: powerbi-docs/paginated-reports/paginated-reports-save-to-power-bi-service.md
Service: powerbi
Sub-service: report-builder
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @marcbeacom -- whew, it took some tracking down, but I have the answer. If you have a Premium Gen1 capacity, then no, an EM3 SKU won't support paginated reports. You need a P1 - P3 SKU in Gen1.
If you have Premium Gen2, then EM1 - EM3 should also work, in GCC tenants and everywhere else. If you have Premium Gen2 EM3 and paginated reports aren't working, then the engineers ask that you please open a support request so they can investigate. https://powerbi.microsoft.com/en-us/support/
Hope that helps!
I'm updating several articles, including this one, as a result:

https://docs.microsoft.com/en-us/power-bi/admin/service-admin-premium-workloads
https://docs.microsoft.com/en-us/power-bi/paginated-reports/paginated-reports-faq#what-size-premium-capacity-do-i-need-for-paginated-reports-

So thanks!


Intel Wi-Fi

I thought I would post this here, as it might be worth implementing either kexts in the future:

https://github.com/AppleIntelWifi/adapter/
https://github.com/daliansky/XiaoMi-Pro-Hackintosh/issues/330

Some Intel cards are not yet fully compatible, although this is likely to change as development seems consistent.
Partially/Fully working (although not yet stable):
AC-3165, AC-7265, AC-8265
Source: https://www.tonymacx86.com/threads/success-working-intel-wifi-drivers-for-7265ac-on-catalina.292207/ (Nobody likes Tonymac, yet useful comments on there!)
Let me know your thoughts or whether you have tested either kexts.

You can refer to this zxystd/itlwm.

You should also refer to the bluetooth kext.
https://github.com/zxystd/IntelBluetoothFirmware

This would be amazing!

You should also refer to the bluetooth kext.
https://github.com/zxystd/IntelBluetoothFirmware

I also agree that it would be awesome if Osy86 could include an option for the HaC installer to include the IntelBluetooth Kext for those of us that don't need WiFi and just want BlueTooth with the stock intel chipsets.

Sure I can include any kext. Just let me know if there's any additional config that's needed (boot-args, etc).

Sure I can include any kext. Just let me know if there's any additional config that's needed (boot-args, etc).

Hi Osy!! Thank you for taking interest. There does not appear to be any special boot arguments needed. If I may suggest for the installer .pkg you made: if it can be either-or for the M.2 section: DW1820A support OR IntelBluetooth support.
For the .pkg description on that section:
Only the following Intel WiFi M.2 cards are supported for Bluetooth injection:

Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 3168
Intel Dual Band Wireless-AC 726x
Intel Dual Band Wireless-AC 8265
Intel Dual Band Wireless-AC 926x
Intel Dual Band Wireless-AC 9560
Intel Wi-Fi 6 AX200
Intel Wi-Fi 6 AX201

or just
3165, 3168, 726x, 8265, 926x, 9560, AX200, AX201

I can’t learn how to use git again. But I came up with some phrases might be useful for future development:
———on Update log
Added some Intel Wireless Network Card support (Not Stable, Use at your own risk)
添加了一些Intel无线网卡支持（不稳定，请酌情使用）
———Might be used in update log
Intel Wireless Network Card Support
Intel无线网卡支持
———wireless kext option title
Wireless Network and Bluetooth support
无线网卡及蓝牙支持
———wireless kext option explanation
Select this option to install specific kexts to support 3rd party network cards. If you are using Apple Airport Card, you don’t have to select this option.
选中此选项以获得对应的第三方无线网卡支持。如果你使用的是Apple Airport无线网卡，那么你不需要使用此选项。
———Intel option title
Intel
英特尔
———Intel option explanation
Add kext support for original Intel Dual Band Wireless-AC 8265. It also adds support for some other Intel wireless network cards including Intel WiFi 6 network card, checkout the HaC-Mini gitbook for more information.
添加对原机Intel Wireless AC 8265的无线网络支持。该选项还会提供对其他Intel无线网卡，包括Intel WiFi 6无线网卡的支持。前往HaC-Mini的Gitbook获取更多信息。
———Dell dw1820a option title
Dell Wireless DW1820A
戴尔DW1820A
———dell dw1820a option explaination
Add kext support for DW1820A network card.
添加对DW1820A的支持。

Hello everybody,
I don't know if it could help, but I use the IntelBluetoothKext for one week now on my laptop thinkpad with Intel DW8265ac and it works very well, and it is stable. I just have to disable then enable bluetooth after sleep of the computer.
About he intel wifi driver, it works well for Internet but, when I want to download a file from my NAS, it is completely unstable and it stops working after 30s. Also, I must enter the SSID/pwd information into the info.plist file included in the kext package.
I don't need the WiFi on my NUC, but I need bluetooth, and it could be nice if you could include this kext into your intall. I just copied the kext package into my CLOVER/drivers/Other folder and it works. How can I do it with OC ?
Thank you for your work !

@zealucard
I suppose the intel BT & wifi kexts are still in experimental status, so maybe it's not the right time to include them in the installer.
For loading kexts in OpenCore, you should put the kexts in EFI\OC\Kexts, and then edit the EFI\OC\config.plist file to load the kext. You can take the existing kexts loading in Kernel->Add  as examples.

@goodbest
You're right, the wifi driver is clearly not stable for now, but the bluetooth driver is probably stable enough.
So, I downloaded the kext files from here IntelBluetoothFirmware, I copied the files into EFI\OC\Kexts folder, and I added this into config.plist file :
			<dict>
				<key>BundlePath</key>
				<string>IntelBluetoothFirmware.kext</string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/IntelBluetoothFirmware</string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>IntelBluetoothInjector.kext</string>
				<key>Enabled</key>
				<true/>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
Now, bluetooth is working very well, and I can use my wireless headset !
Thank you for the tips.

Please test https://github.com/osy86/HaC-Mini/suites/646220359/artifacts/5470857

I just tested this build. Re-installed the Intel chip that came with the Nuc and rebooted twice.

BT can be switched on for me.
Doesn't find any new devices till the BT device is very close to the machine.
Somehow managed to get my Airpods Pro to show up.
But connection drops every 2-3 seconds.

Maybe this is something to do with my machine or if I reinstalled the card and the antennas incorrectly.

Seems like you didn’t attach the antennas correctly. Make sure they clicked in place. It might take a little bit of pressure. Once they’re in it actually takes some force to remove it again.

Oh ok. Will do that today then.

Sorry it took me a week to get to this.
So, @osy86 was right.  Put it back and also put on some electrical tape to hold them in place and they work!
Tested with iPhone and Airpods Pro!


Successful in CPU mode but fail to use the GPU mode macecamera A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid ... (inference)

Before you open an issue, please make sure you have tried the following steps:

Make sure your environment is the same with (https://mace.readthedocs.io/en/latest/installation/env_requirement.html).
Have you ever read the document for your usage?
The form below must be filled.

System information
Docker-full

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
NDK version(e.g., 15c):
GCC version(if compiling for host, e.g., 5.4.0):
MACE version (Use the command: git describe --long --tags): master
Python version(2.7):
Bazel version (e.g., 0.13.0):

Describe the problem
This time I've made success in running the cpu mode, but failed to run the model in GPU mode.
Error information / logs
09-13 21:02:45.312 16466-16466/? I/art: Late-enabling -Xcheck:jni
09-13 21:02:45.324 16466-16466/? D/TidaProvider: TidaProvider()
09-13 21:02:45.334 16466-16466/? V/BoostFramework: mAcquireFunc method = public int com.qualcomm.qti.Performance.perfLockAcquire(int,int[])
mReleaseFunc method = public int com.qualcomm.qti.Performance.perfLockRelease()
mAcquireTouchFunc method = public int com.qualcomm.qti.Performance.perfLockAcquireTouch(android.view.MotionEvent,android.util.DisplayMetrics,int,int[])
mIOPStart method = public int com.qualcomm.qti.Performance.perfIOPrefetchStart(int,java.lang.String)
mIOPStop method = public int com.qualcomm.qti.Performance.perfIOPrefetchStop()
09-13 21:02:45.338 16466-16466/? V/BoostFramework: BoostFramework() : mPerf = com.qualcomm.qti.Performance@fb3814a
09-13 21:02:45.498 16466-16466/com.example.macecamera I/InstantRun: starting instant run server: is main process
09-13 21:02:45.566 16466-16498/com.example.macecamera W/linker: /data/app/com.example.zhoulei3.macecamera-2/lib/arm64/libmace_mobile_jni.so: unused DT entry: type 0xf arg 0x13634
09-13 21:02:45.574 16466-16498/com.example.macecamera I/APPModel: maceMobilenetCreateGPUContext result = 0
09-13 21:02:45.576 16466-16498/com.example.macecamera I/image_classify attrs: gpu perf: 3, priority: 3
device: 2
09-13 21:02:45.585 16466-16498/com.example.macecamera I/MACE: mace.cc:400 Creating MaceEngine, MACE version: unknown-20180913
09-13 21:02:45.621 16466-16498/com.example.macecamera I/MACE: mace.cc:421 Initializing MaceEngine
09-13 21:02:45.644 16466-16466/com.example.macecamera D/ActivityThreadInjector: clearCachedDrawables.
09-13 21:02:45.661 16466-16503/com.example.macecamera I/Adreno: QUALCOMM build                   : dd15ef5, Ic280a69317
Build Date                       : 05/09/17
OpenGL ES Shader Compiler Version: XE<IP_ADDRESS>
Local Branch                     :
Remote Branch                    : quic/gfx-adreno.lnx.1.0.r5-rel
Remote Branch                    : NONE
Reconstruct Branch               : NOTHING
09-13 21:02:46.633 16466-16501/com.example.macecamera A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 16501 (inference)

Please provide full messages as ISSUE_TEMPLATE.md

Sorry, I've carefully made a compilation for the mace libs and the model, this time it works fine for the GPU mode.


Add a Flatten layer on ResNet50(notop) and get an error

I am trying to add a Flatten layer, a Dense layer(relu) and a Dense layer(softmax) on ResNet50 for a multi-classification task using Keras 2.0.2 Theano 0.9.0 py2.7 on Win10.Here is my code:
def create_model():
base_model = ResNet50(include_top=False, weights=None,
input_tensor=None, input_shape=(3,224,224),
pooling=None)
base_model.load_weights(weight_path+'/resnet50_weights_th_dim_ordering_th_kernels_notop.h5')
x=base_model.output
x = Flatten()(x)
x=Dense(128,activation='relu',kernel_initializer='random_normal',
kernel_regularizer=regularizers.l2(0.1),
activity_regularizer=regularizers.l2(0.1))(x)
x=Dropout(0.3)(x)
y = Dense(8, activation='softmax')(x)
model = Model(base_model.input, y)
for layer in base_model.layers:
layer.trainable = False
model.compile(optimizer='adadelta',
loss='categorical_crossentropy')
return model
But I always get following error message:
The shape of the input to "Flatten" is not fully defined (got (2048, None, None). Make sure to pass a complete "input_shape" or "batch_input_shape" argument to the first layer in your model.
I have set image_dim_ordering:
from keras import backend as K
K.set_image_dim_ordering('th')
And here is my Keras.json file:
{
"backend": "theano",
"image_data_format": "channels_first",
"epsilon": 1e-07,
"floatx": "float32"
}

Here is a reproduction script (this is what you should have posted):
from keras.applications.resnet50 import ResNet50
from keras import backend as K
from keras.models import Model
from keras.layers import Flatten, Dense

K.set_image_data_format('channels_first')

base_model = ResNet50(include_top=False, weights=None,
                      input_shape=(3, 224, 224))
x = base_model.output
x = Flatten()(x)
y = Dense(8, activation='softmax')(x)
model = Model(base_model.input, y)

This completes as expected (with both backends).

However, if I add this line:
base_model.load_weights(weight_path+'/resnet50_weights_th_dim_ordering_th_kernels_notop.h5')
before
x = Flatten()(x)
I get this error:
The shape of the input to "Flatten" is not fully defined (got (2048, None, None). Make sure to pass a complete "input_shape" or "batch_input_shape" argument to the first layer in your model.
if I do not load_weights,everthing works fine.


From Martijn: improve network interface mocking

Thanks @martijnwalraven!

@martijnwalraven I started writing this last night but stopped. Its going to be SO helpful!


Use assert rather than warn for missing traits

We kinda discussed using assertions rather than warnings for missing traits in another PR. I decided to spike this out.
If this is merged it might be worth flagging this - maybe this change is bigger than a patch release. It's possible it will cause test failures for people where before they were seeing (but perhaps not noticing or acting on) warnings that were there all along.

was there another thing you were going to use assert for .. you want to do that one and then I put that out in next 2.10 release ?

Yeah was hoping to complete https://github.com/danielspaniel/ember-data-factory-guy/pull/264 alongside but it got a little involved... It'll probably be next week before I get back to it.