[Doc Improvement][SEO title]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/bot-features.md
90
16
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/link-unfurling.md
90
15
link
:white_check_mark:

msteams-platform/toolkit/toolkit-v4/build-environments-vs.md
91
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/bot-features.md
90
16
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/link-unfurling.md
90
15
link
:white_check_mark:

msteams-platform/toolkit/toolkit-v4/build-environments-vs.md
91
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/bot-features.md
90
16
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/link-unfurling.md
90
15
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/bot-features.md
90
16
link
:white_check_mark:

msteams-platform/bots/how-to/conversations/workflow-bot-in-teams.md
89
20
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
90
8
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/link-unfurling.md
90
15
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
87
21
link
:white_check_mark:

msteams-platform/resources/moodleInstructions.md
88
32
link
:white_check_mark:

msteams-platform/resources/partner-apps-for-moodle.md
82
5
link
:white_check_mark:

msteams-platform/samples/virtual-assistant.md
87
31
link
:white_check_mark:

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Sequential-Workflows.md
87
5
link
:white_check_mark:

msteams-platform/toolkit/debug-overview.md
93
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/bot-features.md
90
16
link
:white_check_mark:

msteams-platform/bots/how-to/conversations/workflow-bot-in-teams.md
89
20
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
90
8
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/link-unfurling.md
90
15
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
87
21
link
:white_check_mark:

msteams-platform/resources/moodleInstructions.md
88
31
link
:white_check_mark:

msteams-platform/resources/partner-apps-for-moodle.md
82
5
link
:white_check_mark:

msteams-platform/samples/virtual-assistant.md
87
31
link
:white_check_mark:

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Sequential-Workflows.md
88
5
link
:white_check_mark:

msteams-platform/toolkit/debug-overview.md
93
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/bot-features.md
90
16
link
:white_check_mark:

msteams-platform/bots/how-to/conversations/workflow-bot-in-teams.md
89
20
link
:white_check_mark:

msteams-platform/concepts/build-and-test/share-to-teams-from-web-apps.md
90
8
link
:white_check_mark:

msteams-platform/messaging-extensions/how-to/link-unfurling.md
90
15
link
:white_check_mark:

msteams-platform/resources/bot-v3/bot-conversations/bots-conv-proactive.md
87
21
link
:white_check_mark:

msteams-platform/resources/moodleInstructions.md
88
31
link
:white_check_mark:

msteams-platform/resources/partner-apps-for-moodle.md
82
5
link
:white_check_mark:

msteams-platform/samples/virtual-assistant.md
87
31
link
:white_check_mark:

msteams-platform/task-modules-and-cards/cards/Universal-actions-for-adaptive-cards/Sequential-Workflows.md
88
5
link
:white_check_mark:

msteams-platform/toolkit/debug-overview.md
93
8
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


flow-cli 0.40.0 invalid default access check mode issue

Problem
Have seen some runtime issue after building out flow-cli 0.40.0 release.
Steps to Reproduce

grab the code archive, https://github.com/onflow/flow-cli/archive/refs/tags/v0.40.0.tar.gz

go build

run ./flow cadence hello.cdc

Then you would see
$ ./flow cadence hello.cdc
error: invalid default access check mode
--> hello.cdc

Acceptance Criteria
Passed ./flow cadence hello.cdc test
Context
relates to https://github.com/Homebrew/homebrew-core/pull/110886
This is similar to what I saw in cadence, https://github.com/onflow/cadence/issues/1912

Thank you for reporting, looking into this now.

Cadence 0.26.1 fixed this. https://github.com/onflow/cadence/releases/tag/v0.26.1

This should be fixed by the latest release

Yep, confirmed on my side, https://github.com/Homebrew/homebrew-core/pull/111813


Resource deletion stalls and is not propagated to Vault

Hi,
Using a Vault with kv-v2 enabled, creating a RandomSecret does properly create the entry into the Vault kv store.
However, removing the RandomSecret resource stalls after acknowledgment, and the Vault entry is not removed.
This is due to the fact that the finalizer key on the RandomSecret object is never removed - so Kubernetes awaits forever.
Manually removing the finalizer obviously unlocks the Kubernetes situation, but the Vault entry is left alone and still exists.
As far as I can tell, it does not look normal as the removal should be performed onto Vault as well.
By tracing calls to the RandomSecretReconciler controller, it turns out that the controller is not invoked upon the CR update on deletion: per https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/#how-finalizers-work, the deletion operation adds the deletionTimestamp (updating the CR object), then the Kube control plane awaits that the finalizer list is empty before actually removing the object.
Updating the RandomSecret CR is also entirely ignored - controller is not invoked, and no change is performed in Vault.
Note that this actually happens for any Custom Resource - removing an entire namespace containing multiple CRs from this operator hangs, Kubernetes reporting them as awaiting for finalizers.
This situation happens running a Kubernetes cluster 1.24.8 (GKE) with vault-config-operator version 0.8.10 deployed using Helm.
Is there anything I missed during deployment or configuration?
Thanks in advance,
Regards

there have been recent changes around that behavior. Let me test.

Sure. Let me know if you need some more details or want me to test sthg.

I looked into the code a bit more and think I found the root cause.
Problem 1: the predicate used in SetupWithManager ignores the deletion-with-a-finalizer code flow
The code at https://github.com/redhat-cop/vault-config-operator/blob/main/controllers/randomsecret_controller.go#L159 registers the controller with a predicate, so that it's invoked only when applicable, which makes sense.
However, as described in https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/#how-finalizers-work, the kube client object deletion is actually an event.UpdateEvent for the Custom Resource updated with the new field metadata.deletionTimestamp.
Because of the way the predicate is built, it actually discards the triggered event and the reconcile function is not invoked.
Problem 2: the reconciler function exits before checking if this is a deletion case
There is an early condition check which exits when the secret has already been created and no secret refresh is required at https://github.com/redhat-cop/vault-config-operator/blob/main/controllers/randomsecret_controller.go#L80
However, the code detecting and handling the deletion is performed a few line down at https://github.com/redhat-cop/vault-config-operator/blob/main/controllers/randomsecret_controller.go#L90 and never gets a chance to execute.
I can confirm that fixing those two issues does fix the problem: no more hanging, and the secret is deleted from Vault as expected.

do you want to send a PR?

Hi @raffaelespazzoli
Sorry I missed your question - I'll think about a PR next time.
Thanks for the fix, this is very close to what I did to confirm.


Update @askayastha/my-template as there is the newest 0.0.2 version

"Name of NPM package"
@askayastha/my-template

https://github.com/slitviachenko/aio-template-submission/issues/354 issue created to update @askayastha/my-template

There is the newest 0.0.2 version, the version in Template Registry is 0.0.1

See details in https://github.com/slitviachenko/aio-template-submission/issues/352


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL: https://tronscan.org/#/contract/TPoqTjgFU9wafGfHgntdisqe55Pb4Uq8Mm/code
JustList Name: ZexDex
Link to the official homepage of the JustList manager: https://tronscan.org/#/contract/TPoqTjgFU9wafGfHgntdisqe55Pb4Uq8Mm

Sorry, your issue will be closed as you did not submit your information in the correct format.


Project files permissions

Some confusing behavior. After docker-compose up -d command all files and folders became with owner 999 and group nobody.

I have the same issue.
Just starting up is normal, after a few hours it will be down due to permission issues.

I donno but somehow problem solved for me.
I've just created a new project and added nodedock as git module

@peakercope @17forever i was solve this issue, check my fork
cc @philtrep

currently my laptop os is arch llnux, but when i use macos i dont see this bugs. i think this bug just work in a few os. @peakercope @17forever


Clear session cookies before logging in a user

Trello: https://trello.com/c/PZyZdMtG/337-custom-dimension-to-capture-size-of-supplier
This will hopefully avoid Google Analytics linking separate users from different tests (and thus overwriting any custom dimensions they set and producing weird results in the GA dashboard).
I'm not sure if login_steps.rb is the best place for this - ideally we'd reset the session after every scenario rather than just before the login step. Where would we put a teardown equivalent?

Where would the best place for this be? hooks.rb?

Yeah I think that's the best place for it. Cucumber thinks of those things as 'hooks' from what I remember, so since we already have a file called that may as well use it :)


generate k8s gw apis

reference: https://github.com/solo-io/gloo-mesh-enterprise/issues/18646

no longer necessary as the clients are being generated directly in GME repo


added possibility to add customProps to customMarker

My customMarker is a React component and I needed to pass props to it. Hence, I added a new prop customProps to do it.

Have you tried to wrap your custom marker to pass props to it?
const CustomMarker = props => {
  const { markerStyle, pressed, pressedMarkerStyle, text } = props;
  return (
    <View style={[ markerStyle, pressed && pressedMarkerStyle ]}>
      {text && <Text>{text}</Text>}
    </View>
  );
}

// ...

<Slider values={[1]} min={0} max={10} customMarker={props =>
    <CustomMarker {...props} text="Custom Marker" />
  }
/>

It worked like a charm, thanks!


Add check for broken outbound links from the UI

Nothing's going to upset a user more than wanting to Learn more:

and not being able to

This new workflow scrapes the webui/src folder for any outbound links, builds the docs site, and then checks those links.
Here's a test run in which it successfully identifies a broken link

and here is a successful run

While I enjoyed reading the code, I think this one is a bit of an overkill. There aren't many links in the lakeFS UI, so I'm not sure it's worth the code complexity here.

While I enjoyed reading the code, I think this one is a bit of an overkill. There aren't many links in the lakeFS UI, so I'm not sure it's worth the code complexity here.

Can you expand on this? You don't think we should check for broken links, or you think we should but with code that's easier to read? thanks

@rmoff, I'm just not sure it justifies automation: we can manually check the links every once in a while. But I don't feel strongly about it so if I'm a minority here feel free to push this.

Thanks @N-o-Z - I've added a daily trigger too. I think it's important still to check on PR in case there's a new link/changed link as part of the PR that needs to be picked up in the checks.

Thanks @N-o-Z - I've added a daily trigger too. I think it's important still to check on PR in case there's a new link/changed link as part of the PR that needs to be picked up in the checks.

I agree - thanks!!


Make @smittyvb votes worth about (e^pi-pi)/40

Which is about 0.49997749948. Just for the lols.
Seriously, though, it's a joke. Although, it would be funny to be ~0.000022 away from the voting threshold.

@smittyvb would you upvote if I made it 1-(e^pi-pi)/40? That would make your voting power 0.50002250052, or about 0.00022 MORE than you currently have right now! Win-win, amirite?

                                                                                Yep.

There you go!

Unfair 😂


Automation example contains unsupported syntax

The automation example in the Readme.MD file contains unsupported syntax.
condition: [none]
Please remove this line to avoid issues loading the automation.

done


Not able to provision new hosts/create new containers when there are lot of services stuck in "activating" state.

Rancher server version -  v1.2.1-rc1:
Had a K8s env with 3 hosts.
Had few Service/RC/pods running.
Deleted all the hosts.
UI took ~20 secs to respond. But it loaded successfully after that.
Had a cattle env where there were 30 services that were stuck in "activation" state because of allocation failures.
Able to launch UI successfully.
Issues seen in this set up:
Adding new host is stuck in "provisioning" state.
Starting new container is stuck in "registering" state.

Processes have priority and stuff now.

Tested with Rancher server version - v1.4.0-rc3
Had a K8s env with 3 hosts.
Had few Service/RC/pods running.
Deleted all the hosts.
There is no retry to get infra service containers up anymore.
Had a cattle env where there were ~50 services with scale 3 that were stuck in "activation" state because of allocation failures.
When this was the state , I am able to to add new host successfully.
Starting new services also succeeds.


[Application Gateway] Avoid showing recommendations when every resource of that type is properly configured

Expected Behavior
I have an Application Gateway with SKU Standard V2 that is using Availability Zones. I don't expect any recommendation to show in the report if the resource is properly configured.
Actual Behavior

I got the following message after executing the tool:
_v2 SKU includes Zone Redundancy so an Application Gateway or WAF deployment can span multiple Availability Zones, removing the need to provision separate Application Gateway instances in each zone with a Traffic Manager.
Autoscaling and Zone-redundant Application Gateway v2 | Microsoft Docs_
Steps to Reproduce the Problem

Create an Application Gateway with SKU Standard V2 and configure Availability Zones for the resource. Then, run the tool and read the report.

Perhaps we should rename the section to something like: Best Practices and show it regardless of the results of the scan.
@Alvaromg45 thoughts?

It would be better than nothing, but I think it would be a lost opportunity if we cannot match information about the real resources (that we gather during the scan process) with actual recommendations that can help you to increase the quality of your Azure Solution.


Bridgy backfeed from Strava.com (new silo)

Just as it would be nice to POSSE to Strava (Issue #780 ) it would be great to be able to backfeed from those POSSE copies as well.
Backfeed on exercise posts would consist of kudos (likes), comments.
Backfeed on support.strava posts would consist of upvote (like), downvote, comments

More thoughts here: https://indieweb.org/Strava#backfeed

thanks again!


Make edit at line command work for sublime text

Currently, the edit command runs the following command:
$EDITOR +line file

As this notation might be a standard for some editors, this doesn't work for sublime text, where the syntax for opening a file is:
subl file:line

I propose an option that would change the default editor call syntax to the colon-notation. Like:
editor_line_syntax = 'option' # default, give the line as a command option.  $EDITOR +<line> <file>
                     'suffix'  # (give the file line as a suffix, as accepted by sublime text : $EDITOR <file>:<line>

As a workaround this problem for fish users, create a script that does the conversion:
#!/usr/bin/env fish
set line_arg $argv[1]
set file $argv[2]
set line (echo $line_arg | string match -r '\d+')
exec subl "$file:$line"

And then in ~/.pdbrc
import pdb
class Config(pdb.DefaultConfig):
    editor = '/path/to/your/script/open_to_fileline_subl_adapter.fish'

This does the job

I will add a new edit_cmd setting, where {lineno} and {filename} get replaced in every item (it should be a list of args, but a single command could be supported also).
E.g. edit_cmd = ["subl", "{filename}:{lineno}"].
Does that sound good?

Well, actually the editor setting could be kept, but we would try to format {lineno}/{filename}, or %d/%s in there.
I think optionally handling a list is also nice.

WIP: https://github.com/antocuni/pdb/pull/165

looks good!

Have you tried it yet?
Need to review/revisit it myself - it was done quite ad-hoc.

Does subl 'with space':12 work?
Or should it rather be subl 'with space:12'?

@antoine-gallix
gentle ping

Sorry I was away for a very long time. I´ll try that

Does subl 'with space':12 work?
Or should it rather be subl 'with space:12'?
both work

editor = "subl {filename}:{lineno}" in .pdbrc.py is working well!

PR for documentation there: https://github.com/antocuni/pdb/pull/227

and here is doc update for the config https://github.com/antocuni/pdb/pull/227


ImageDownloader to download to destination

Hello,
is there a way to download an image and save it to a destination using the ImageDownloader?
Something like this:
let destination = DownloadRequest.suggestedDownloadDestination(for: .documentDirectory) Alamofire.download("https://httpbin.org/image/png", to: destination)
With the Power of the ImageDownloader?
Thanks,
Urkman

What "powers" of ImageDownloader do you want to combine with simple image download?

Untested sample code:
let urlCache = ImageDownloader.defaultURLCache()
// maybe set your own path here
urlCache.diskPath = "org.alamofire.imagedownloader"

let configuration = ImageDownloader.defaultURLSessionConfiguration()
configuration.urlCache = urlCache

let imageDownloader = ImageDownloader(
  configuration: configuration,
  imageCache: AutoPurgingImageCache()
)

I am looking forward to this feature. I need to save images in the document directory.


graphics: Optimization: is it possible to embed color matrix info into vertices?

If this is possible, the number of draw calls would be much smaller.

https://github.com/hajimehoshi/ebiten/tree/colorm (Note that I might rebase this branch later)
On my MacBook Pro, I found some FPS drop from 55 FPS to 45 FPS with about 8000 sprites of examples/sprites. Let's wait for WebAssembly work (#528).

I think this is necessary for particle animations

Hmm, it is still slow on examples/sprites. (about 30 or more FPS on Chrome with 10000 sprites). Embedding all the color matrices data to vertices is too heavy.
Another idea is to pass multiple color matrices to the fragment shader as uniform variables, and make vertices have 'index' to one of the color matrices.

Yet another idea is to compress 20 float32 values into smaller array. It's ok even if it is lossy compression.

Only 8 float32 values for each vertex made vertices function slow... (40 FPS with 10000 sprites?)
Would it be feasible to replace vertices with asm.js or WebAssembly implementation?

I think adding 4 float32 values for each vertex would be allowed (I'm still not sure but let me do experiments later). If just scaling colors by ColorM is common enough, how about

fixing ColorM into scaling part and other part
embedding four scaling colors for vertex and
using them only when ColorM’s non-scale part is default

?
As for 2), if the ColorM doesn't have scaling part, we can skip embedding.
@seebs, what do you think? I was wondering if scaling is really common enough.

I started to think to simply add color values to vertices regardless of ColorM as @seebs suggested (probably), because I plan to add a new function to specify vertices directly to draw something on an image, and this would enable to change the color for each vertex, which is what @seebs wanted before as far as I remember.

I think scaling color is a particularly common application compared to translation or hue-rotation.
I would love a general vertex-specifying thing. I would also be super interested in a thing that would allow specifying the type of vertexes -- say, allowing triangle strips. (I'm not sure whether that's actually useful, but I think it would at least be nice to have something flexible enough that it became possible, because I'd like to benchmark triangle strips as an alternative way to render large polylines.)

I would also be super interested in a thing that would allow specifying the type of vertexes

Doesn't this require exposing shaders at the same time? I don't plan this though... (Mac/iOS tries to deprecate OpenGL and I plan to move to Metal, and shader languages are different).

I don't think it should require that, necessarily. You should be able to use the same shader with both triangle strips and regular triangles. I think you're doing quads, currently, and that's 4 vertexes per quad instead of 6 per two triangles, but I am not actually sure how much that differs in performance; I've seen claims that because triangles are the more common case, some hardware will do them enough faster that it's actually more efficient to just send triangles.

Let me confirm: what did you mean by types of vertices? I thought this meant something to decide whether vertices include color info or original info or not.

Hmm. That might not be insane; you couldn't do it fully generically, but you could handle with/without color data, perhaps, by having different prebuilt shaders for them.
But I was thinking quads vs. triangle strips, etcetera, so people who are writing their own vertices directly can write fewer of them for some use cases.

But I was thinking quads vs. triangle strips, etcetera, so people who are writing their own vertices directly can write fewer of them for some use cases.

Ah that makes sense. Now quads are drawn as triangles with 4 vertices and 6 indices as two triangles. Two vertices are shared and this is specified by the indices. The new function I am planning accepts not only vertices but also indices, so I think this is what you want.

https://github.com/hajimehoshi/ebiten/tree/issue-531-color
Perhaps I've succeeded to embed all the values of a color matrix... @seebs , could you test this branch when you're available? Thanks!

https://github.com/hajimehoshi/ebiten/tree/colorm-revert Experimental revert

Confirmed: on go-inovation, the FPS was
60 on colorm-revert
40+ on master
CC @wasedaigo

This is unfortunate, but the performance drop was inevitable. Let's revert this.


How to make it work with next.js ?

I am getting this error in next js:
Unhandled Runtime Error
Error: Hydration failed because the initial UI does not match what was rendered on the server.

See more info here: https://nextjs.org/docs/messages/react-hydration-error

I am using your example code
    const container = {
        width: 1280,
        height: 1000,
    };
                    <ProGallery
                        id="gallery"
                        isPrerenderMode={typeof window === 'undefined'}
                        items={items}
                        options={options}
                        container={container}
                    />

Hey, notice that prerender mode should include the hydrate stage.
In your example you make isPrerenderMode === isServerSideREndering which will create this exact issue.
isPrerenderMode was created to be true when the imformation that is used in the server/hydrate to create the gallery is still not whole.
As the most common example, if you use the gallery in a responsive manner (1vw) you will not know the window width in the server(window undefined) and before measuring it (hydrate).
If this is the case isPrerenderMode should be true (server) true (hydrate) and change to true only after setting the correct dimensions (render).


Fix badly converted links

There are some links that were not correctly migrated. You can find them by searching qualifyHint.
Not all of them will appear as an issue in the build report because the first part of the link was correctly migrated, so we just have garbage showing up, such as in:
https://docs.microsoft.com/en-us/dotnet/api/system.numerics.biginteger.op_greaterthan?view=netframework-4.7#System_Numerics_BigInteger_op_GreaterThan_System_Numerics_BigInteger_System_Numerics_BigInteger_

Yes, I couldn’t find any QualifyHint in my local repo so I thought it was finished. I was going to ask you for a sanity check earlier today. I now see I was in core only. Apologies! Thanks for reopening.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Maira Wenzel<EMAIL_ADDRESS>Sent: Tuesday, November 7, 2017 7:16:36 PM
To: dotnet/docs
Cc: John Alexander; Mention
Subject: Re: [dotnet/docs] Fix badly converted links (#2459)
@JRAlexanderhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjralexander&data=02|01|john.alexander%40microsoft.com|84447e2dfc47406badb808d526465bbf|72f988bf86f141af91ab2d7cd011db47|1|0|636457005986038191&sdata=uVCQAyHuOLpVDdAanTiwuz1TsWjkgshqNGMjTpw4jPY%3D&reserved=0 I still see qualifyHint in links in the migrated content:
https://github.com/dotnet/docs/search?utf8=✓&q=qualifyHint&type=https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fdocs%2Fsearch%3Futf8%3D%25E2%259C%2593%26q%3DqualifyHint%26type%3D&data=02|01|john.alexander%40microsoft.com|84447e2dfc47406badb808d526465bbf|72f988bf86f141af91ab2d7cd011db47|1|0|636457005986038191&sdata=53ndUFPxkd2huzNJkhl6Vvb6PDgV1xjWJXhgRETXtcU%3D&reserved=0
So I think this issue should remain open until that is fixed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fdocs%2Fissues%2F2459%23issuecomment-342677999&data=02|01|john.alexander%40microsoft.com|84447e2dfc47406badb808d526465bbf|72f988bf86f141af91ab2d7cd011db47|1|0|636457005986038191&sdata=e5EcCuKQvU5g2RKUm7gF%2FlIa4CUw1DChL8Zk%2FmqaPSk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAElQwUVIG_4tOx7qfYC1U-3y7SFoqdfxks5s0QD0gaJpZM4OAhXQ&data=02|01|john.alexander%40microsoft.com|84447e2dfc47406badb808d526465bbf|72f988bf86f141af91ab2d7cd011db47|1|0|636457005986038191&sdata=xyUjSBMBMhqTNQp8D83S4jn99PMXS5%2Bvnk%2BdTkRqt6I%3D&reserved=0.

I think we're close to get this one finished. There are only 3 more files showing up with that qualifyHint string!

Yup, working on it now!


Reduce warning strictness

What does this PR try to resolve?
This solves two use cases

When developing a feature, I might be experimenting with some sloppy, intermediate states and warnings shouldn't prevent me from running tests
A new dependency being released should not block people from running tests (also solved by the above) or cause CI (for PRs or Bors) to fail, blocking them on something unrelated to their work

How should we test and review this PR?
I didn't see any pertinent history for why cargo conditions deny(warnings) on cfg(test) while other parts of cargo use feature = "deny-warnings", so I just went forward with this consolidation.  It does mean some targets that we test without the feature might have warnings slip through though the risk is low.
I tested this against clap master which adds more deprecations.
Additional information
This does raise the risk of deprecations not being addressed but that is a question of contributor culture.  I know I would look into it if I saw deprecation warnings go by and I would hope others would too.

A bold idea: Having a bot to collect warnings and post a comment in the PR to raise the visibility. The bot categorises warnings by deprecations, clippy warnings, or other built-in lint rules.  So that either the PR author notices and fixes  them, or the reviewer takes it as a reference to request a change, or everyone is happy to ignore it.

A bold idea: Having a bot to collect warnings and post a comment in the PR to raise the visibility. The bot categorises warnings by deprecations, clippy warnings, or other built-in lint rules. So that either the PR author notices and fixes them, or the reviewer takes it as a reference to request a change, or everyone is happy to ignore it.

There is a clippy action that makes comments: https://github.com/giraffate/clippy-action
We could also use Serif which tracks alerts across commits and branches

https://www.reddit.com/r/rust/comments/yz7l2v/github_actions_for_clippy/ixpomjq/?context=3
https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning

These tools are really cool! I'll vote for allowing deprecations on CI with one of those GitHub Actions.

These tools are really cool! I'll vote allowing deprecations on CI with one of those GitHub Actions.

:umbrella: The latest upstream changes (presumably #11699) made this pull request unmergeable. Please resolve the merge conflicts.

Since https://github.com/rust-lang/cargo/pull/11699 got landed, is this pull request still useful? Looks like it is something we can close out.

With a Cargo.lock, the value of this is lessened.


Problem with signature, all dependencies are installed and working

Which apk used for backdooring?

spotify
Il giorno lun 8 mag 2023 alle ore 14:46 Sumit Ghosh <
@.***> ha scritto:

[image: Immagine 2023-05-08 133828]
https://user-images.githubusercontent.com/106509856/236814583-e7c3bc8c-44e4-491e-a0d6-d22f7196ac44.png
Which apk used for backdooring?
—
Reply to this email directly, view it on GitHub
https://github.com/HackWithSumit/AndroidBackdoor-EvilDroid/issues/1#issuecomment-1538301148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZMTMIHIQZ5EV5FML7QPJ7DXFDTKLANCNFSM6AAAAAAXZ2KXSM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please follow POC step by step.
Sent from Proton Mail mobile
-------- Original Message --------
On 8 May 2023, 8:15 pm, Oraclewhite < @.***> wrote:

spotify
Il giorno lun 8 mag 2023 alle ore 14:46 Sumit Ghosh <
<EMAIL_ADDRESS>ha scritto:

[image: Immagine 2023-05-08 133828]
https://user-images.githubusercontent.com/106509856/236814583-e7c3bc8c-44e4-491e-a0d6-d22f7196ac44.png
Which apk used for backdooring?
—
Reply to this email directly, view it on GitHub
https://github.com/HackWithSumit/AndroidBackdoor-EvilDroid/issues/1\#issuecomment-1538301148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZMTMIHIQZ5EV5FML7QPJ7DXFDTKLANCNFSM6AAAAAAXZ2KXSM
.
You are receiving this because you authored the thread.Message ID:
<EMAIL_ADDRESS>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


[MINOR][R][DOCS] Fix misplaced brackets in SparkR:::mapValues doc

What changes were proposed in this pull request?

Fixes usage @example for SparkR:::mapValues.
Why are the changes needed?

At the moment. example has invalid syntax and yields warnings when running additional checks on SparkR codebase.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Manual testing.

Test build #145510 has started for PR 34682 at commit f7079c9.

Test build #145510 has finished for PR 34682 at commit f7079c9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49982/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145510/

Merged to master.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49982/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49982/


[Bug] [website] Checkpoint-Storage description is incorrect.

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
https://seatunnel.incubator.apache.org/docs/2.3.3/seatunnel-engine/checkpoint-storage
Among the HDFS section, the kerberosKeytab configuration item is incorrect.
Among them, the seatunnel.hadoop.dfs.client.failover.proxy.provider.usdp-bing configuration item has an extra double quotation mark at the end.
SeaTunnel Version
2.3.3
SeaTunnel Config
not need

Running Command
not need

Error Exception
not need

Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Simple fix is here: https://github.com/apache/seatunnel/pull/5883


Missing deposit

I sent BTC to this wallet and it is not showing up ,
Transaction ID d8f469d96d1f3834becb54112dadf3ec1eef6919140a1043139a472096f7f48b
Wallet address bc1qsscjw6hu70t5x88yws4my0ke28v3ntnygn2wnz
Transaction listed as completed on Binance. Please advise.
Issue description

Your Environment

ASGARDEX desktop version:

Operating system and version:

Transaction hash(es):

Wallet address(es):

@julsay What's your ASGARDEX desktop version /  Operating system and version? Just in case: Pls try to use latest v0.3.3 of ASGARDEX desktop.

I downloaded the newer version and it worked, thanks.


Multilingual compatibility and batching for Code Evaluation

What does this PR do?
Adds support for C, C++ and JS and batching to Code Evaluation
What issue(s) does this change relate to?
Code Evaluation Deployment

Manual test

Sample datasets are in my PR to foundry


Cannot sign Permit2 to simulate Uniswap transactions

Just installed v0.0.73 and I'm failing to transact with Uniswap. Previously, in v0.0.72 I believe it was possible.

If you change here to experimental geth client, you should be able to sign it. But yeah, that should also Work. I'll look what's wrong with it

This is duplicate of https://github.com/DarkFlorist/TheInterceptor/issues/760
Unfortunately Uniswap decided to develop Uniswap V4 which makes their exchange to require centralized components so we are unable to simulate this kind of messages to make the swap to work :/


Creating new labels for virtual nodes is no longer possible

There used to be the possibility to add fields (key value pairs).

my bad, I refactored the modal. Angular 2 branch will have e2e tests so we can prevent these situations! :)

Since we're going to rebuild the UI from scratch I'm closing this issue.
If you still have any questions, don't hesitate to reach out on Gitter or open a new issue!


Make CollectionX operations lazy & more efficient

Operations such as map / flatMap etc can be made lazy and as a result we can perform a single iteration through the colleciton and short circuit where neccessary.

It's probably not possible to do this and leave the return type as CollectionX. The reason being that the intermediate Collection can be assigned to a variable / value and subsequently operated on in different ways. Meaning that all of the intermediate stages would need to be stored (expensive in terms of memory usage).
Alternatively the return type could simply be Traversable and we could return a Stream. This would make  the most common use case for Collection eXtensions redundant (that is cleaner code where users wish to perform a single action on a collection by requiring users to convert back to the collection type at hand.
For long chains (less efficient) the overhead of type llistX.stream().map(..).map(..).filter(..).map(..).toListX() is probably ok. Adding two additional methods to a long chain (compared with adding two additional methods when all you want to do is a single map operation.
Unlikely to get implemented.


Accessibility refs

Fixes #86
Preview

@Maroyafaied @mcharg edits look good to me, thanks for doing that. I will update it for the ONRResource copy.

I showed the updates to Sid and he's good with them.


500 if page param is lower than 1

I get 500 status code when in request page param is lower than 1. For example: /resource?page=0
I think that's client problem so status code should be 400. What are you think?
https://github.com/zfcampus/zf-hal/blob/master/src/Collection.php#L282

:+1:

+1

:+1:

:+1:

:+1:

I have find out that this issue is fixed in master. However I page_size param had same issue so I fix it. https://github.com/zfcampus/zf-rest/pull/94

Here is fix https://github.com/zfcampus/zf-rest/blob/master/src/RestController.php#L953

Page size should be allowed to be -1 (dectivate paginator).
Please take this into account in your solution.


For performance do not check the version on each run

Checking the version on each run slows down the linting unnecessary.
Sure we can try to cache this info but mypy is not stable software,
and we must expect users move to a new version a bit quicker.

I'm perfectly fine with this. This was only meant to be a temporary fix until people update to an updated version of mypy, given the performance implications. The old version that requires the change has been superceded about a year ago and I believe it is reasonable to assume that people have updated their version by now. If they report problems about column alignments of error reports, we'll know what to tell anyway.


Cow: Watch mfimedical.com

Cow requests the watch of the watch_keyword mfimedical\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

mfimedical\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Run as an administrator is not working as expected

I have selected Run as an administrator option and created an Application using shell script.After clicking on it instead of giving credentials if i select cancel application remains running. I need to forcequit before i launch my application. I need a solution for this ASAP.Please provide comments on this

This is a deficiency of Platypus. No mechanism to kill privileged processes.


SAK-44823 - Add title and aria tag to profile dropdown

Hey @adrianfish and @fostersdesign - I think we have got this finally - let me know if you want to look it over.


As VALIDATOR, I want to cross-check my study data against both the study define.xml and SENDIG for mismatching dataset variable labels so that I can stay compliant with SEND 6.

This check only applies to SEND.
This check needs CDISC Library.
This check is IG-version-agnostic.
This check is case sensitive.

SEND 6 in v4.0:

Rule: Metadata in Define-XML document should match both the SENDIG label and the label in the .xpt datasets.
Rule explanation: Metadata in Define-XML document should match both the SENDIG label and the label in the .xpt datasets.

The rules has been written and working. The rule has been split into 2 rules.


Add ITEM_PHARAOHS_SCEPTRE to convert untradeable item to tradeable counterpart

Fix issue where the Bank plugin does not register the GE value of the Pharaoh's Sceptre when it is charged.
Fixes https://github.com/runelite/runelite/issues/15588

You have PHARAOHS_SCEPTRE_13077 entered twice, remove the duplicate

fixed.

I ended up writing #15646 to solve the problem of these constantly-growing lists becoming hard to maintain.


Feature request: Auth inside firehose.js

Since last december the firehose.eosnation.io endpoint is not available anymore and we are now forced to use *.firehose.pinax.network or *.substreams.pinax.network .
Both of those endpoint are now requiring auth, i tried to modify myself firehose.js to include auth but without success
function metadataGenerator(params, callback) {
  const metadata = new grpc.Metadata();
  metadata.add("SUBSTREAMS_API_KEY", process.env.PINAX_KEY);
  metadata.add("SUBSTREAMS_API_TOKEN", process.env.PINAX_KEY);
  callback(null, metadata);
}

const getClient = useBootFirehose => {
  const channelCredentials = useBootFirehose ?
    process.env.BOOT_GRPC_INSECURE === 'true' ?
        grpc.credentials.createInsecure() :
        grpc.credentials.createSsl() :
    process.env.GRPC_INSECURE === 'true' ?
        grpc.credentials.createInsecure() :
        grpc.credentials.createSsl();

  const metadataCredentials = grpc.credentials.createFromMetadataGenerator(metadataGenerator);

  const credentials = grpc.credentials.combineChannelCredentials(channelCredentials, metadataCredentials);

  return new firehoseStream(
    useBootFirehose ? process.env.BOOT_GRPC_ADDRESS :  process.env.GRPC_ADDRESS,
    credentials,
    {"grpc.max_receive_message_length": 1024 * 1024 * 100, "grpc.max_send_message_length": 1024 * 1024 * 100 }
  );
}

Using v2 firehose service i get error "Error: 16 UNAUTHENTICATED: no authorization token found" and v1 "Error: 13 INTERNAL: Received RST_STREAM with code 0" so it looks like my code has no effect.
I would appreciate if someone familiar with @grpc/grpc-js can update firehose.js to support pinax auth key as firehose is mandatory on first boot to initialize the lightproof-db.

I have been told i should use X-Api-Key, doing this
function metadataGenerator(params, callback) {
  const metadata = new grpc.Metadata();
  metadata.add("X-Api-Key", process.env.PINAX_KEY);
  callback(null, metadata);
}

Solve the issue . I'm gonna push a PR later today.


#1075 Added new developers and moved retired developers to contributors.

Close #1075
Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[ ] Code is formatted according to the tidyverse style guide
[ ] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[ ] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[ ] Update to all relevant roxygen headers and examples
[ ] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[ ] Address any updates needed for vignettes and/or templates
[ ] Update NEWS.md
[ ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[ ] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[ ] Link the issue so that it closes after successful merging.
[ ] Address all merge conflicts and resolve appropriately
[ ] Pat yourself on the back for a job well done!  Much love to your accomplishment!

@pharmaverse/admiral
Hi all, I have added in new developers to our Description File.   The ordering is a bit arbitrary for authors and contributions to admiral, but folks who have made considerable contributions to admiral I pushed to the top.
Folks who have left admiral or have not contributed in this release cycle I moved to the bottom of the list and changed their role to contributors.
I looked at commit history, pull requests and meeting attendance to add in people.  If I missed someone, or you!!, please let me know.  The list is long! :)
Also need a reviewer.


Handling non-orthogonal key dimensions

Implicit in the idea of showing multiple sliders at once, say A,B,C is that for any setting of slider A (say)  you can choose any setting you want for B and C. In other words, this assumes the sliders can be independent and there are no constraints between the sliders e.g if the value of a particular slider is some function of the other slider positions.
This is true of many applications but is not the most general case. If you have data where this assumption doesn't hold, it is tricky to explore the full dataset as you have no guide to what particular slider positions have data available and which do not. Furthermore you can move the sliders and get 'stuck' without knowing which slider to change in order to explore the rest of the data.
One proposal we have is to detect this condition (keys that are not on a grid) and warn the user to use one of the widgets that serializes the data into a single slider (e.g scrubber). A different proposal that we have just discussed is to detect this condition and automatically show a single 'index' slider instead.
This is a fairly quick job but the idea can be extended. In future, you could have the index slider shown together with all the normal sliders per key dimension. Moving the index slider along (the serialization) would set the position of the other sliders to the appropriate values. Then you could still move the independent sliders around (useful if the keys are nearly on a grid). The index slider makes sure you always have a way to scrub through all the available data.
Moving the independent sliders would not move the index slider (unlike the converse). Note that this more advanced proposal would need to be implemented in JavaScript and would take more time whereas the simple proposal can be done entirely in Python relatively quickly.

I've been struggling with this problem myself, and I vote for doing the simple proposal right away, but also doing the more advanced proposal.  Part of the whole raison d'etre of HoloViews is to be able to explore large, multidimensional spaces, and the thing about such spaces is that they are often quite sparse, with meaningful things happening only in relatively local region of that space.  Providing good ways to explore sparsely (but potentially locally densely) populated spaces is very important.

Good summary of our discussion. One minor quibble:

Furthermore you can move the sliders and get 'stuck' without knowing which slider to change in order to explore the rest of the data.

This was true of our original prototype but isn't the case anymore. Doing it that way turned out to be completely useless for precisely the reason you mentioned.
I've got one more alternative proposal just to throw it all out there. Instead of providing one useless Index widget it would also be possible, to format each key (i.e. multiple dimension values) into a string and use that as the index instead. That would require a dropdown menu though, which is probably not as useful.
The basic index suggestion is what I can get working very quickly and would be feasible before the next release.

Why would the reformatted-key option require a dropdown menu?  Can't it be
a slider, with the value of the slider showing up as a string, but still
slidable (because whatever it is, it can be slid)?
On Tue, Nov 24, 2015 at 3:23 PM, Philipp Rudiger<EMAIL_ADDRESS>wrote:

Good summary of our discussion. One minor quibble:
Furthermore you can move the sliders and get 'stuck' without knowing which
slider to change in order to explore the rest of the data.
This was true of our original prototype but isn't the case anymore. Doing
it that way turned out to be completely useless for precisely the reason
you mentioned.
I've got one more alternative proposal just to throw it all out there.
Instead of providing one useless Index widget it would also be possible, to
format each key (i.e. multiple dimension values) into a string and use that
as the index instead. That would require a dropdown menu though, which is
probably not as useful.
The basic index suggestion is what I can get working very quickly and
would be feasible before the next release.
—
Reply to this email directly or view it on GitHub
https://github.com/ioam/holoviews/issues/301#issuecomment-159408863.

Sure, it could be but the slider text field is often too small to handle even a single float value, a long string of multiple would be mostly obscured.

It would also be possible to format each key (i.e. multiple dimension values) into a string and use that as the index instead.

Interesting suggestion although couldn't this end up being quite long (unless you use a tuple only) and be redundant with the title?  I think a dropdown would be unusable if you have lots of keys.
I was wondering if maybe you could hover over the slider and show a tooltip with the dimension values (which would be cool!) but I get the impression it isn't so easy. This seems the closest example I could find.
All in all, I think an index number isn't so bad as the dimensions are generally shown in the title.

Will the positions of the other sliders show the value of the index slider?

In the more complex proposal they would, but that's probably a days work, so for this release it would just be the index.

Sounds like it would make sense just to show the index in this release, and
then do the more complicated one.

Having had a very long discussion with Philipp, it is clear this issue is much thornier than we've made out in this issue so far!
Essentially, the cartesian is both a very special case (though people do use it a lot deliberately) and the only case when independent sliders make sense. If as soon as it isn't a cartesian product, you always switch to the index slider, then that will happen in almost every case a cartesian product hasn't been deliberately used (not helpful!).
We now think there are three cases:

Cartesian product (easy - an all-to-all relationship).

Contiguous subspaces: given the other values of the other sliders, there is a single small portion of the space that needs to be accessible. This is more general than hierarchical sliders which impose an ordering to say which values are more 'important' than others (so you select the subspace according to the more 'important' dimensions). Each level of the hierarchy has a one-to-many relationship with the level below it.

The general case: lots of disconnected 'islands' that are conditional on the state of all the other sliders. This is the many-to-many relationship (or some-to-some if it is sparse!) which is awkward to work with (and people prefer to avoid even if real data is often like this!).

We've come up with the following proposal:

We can automatically detect if the keys imply a hierarchical relationship, working in the declared order of the key dimensions. If this happens, we can use a contiguous subspace approach and also know the precedence of the sliders. One possible future idea is to allow the user to 'lock' sliders to decide precedence, allowing the more general contiguous subspace approach.

If it isn't hierarchical, we use independent sliders. Cartesian works nicely but if values are missing, we have a blank frame. In future, it would be nice to give a hint about valid and invalid spaces when dragging the slider. E.g the slider bar could go red when dragged over regions with no data. This is a completely general approach but only works well with the cartesian case because it gets hard to find any data at all if the dataset is sparse (the index slider is really just a way of handling sparsity).

The hope here is that the hierarchical/contiguous subspace case is common enough to help tackle sparse data in a useful way.

Okay after our discussion last night I've now implemented the hierarchical suggestion. The widget code now detects if a dimension has a one-to-many mapping to the following dimension and if that's the case then it updates the following slider/dropdown with just the values that are available in that subspace. This should solve all our current issues with the widgets but some of the other suggestions could definitely still be useful at a later stage.
Note the solution I've implemented isn't fully general, the hierarchical dimensions need to appear consecutively for this to work, i.e. if your key dimensions are Country and Continent (rather than Continent and Country) it will not detect the hierarchical relationship between them.

Here is a nice little example that will demonstrate this:
af_countries = ['Gambia', 'Uganda', 'Zimbabwe']
eu_countries = ['Germany', 'UK', 'Ireland']
countries = zip(['Africa']*3, af_countries)+zip(['Europe']*3, eu_countries)
years = range(1960, 1990)
hmap = hv.HoloMap({(cont, country, y): hv.Image(np.random.rand(10, 10))
                   for cont, country in countries for y in years}, kdims=['Continent', 'Country', 'Year'])
hmap

There should be something visual to indicate the relationship between the dimensions. While it's pretty obvious in the continents/countries example it might not be as clear in other cases. Not sure what best expresses the relationship though.
I also don't want to sink too much work into the current widgets, if we're eventually switching to PhosphorJS anyway.

Okay after our discussion last night I've now implemented the hierarchical suggestion.

Great! I am very happy we can improve the behavior substantially in an automatic way without introducing any new interface for the user to learn. We do need to document this feature though..something like "you can toggle hierarchical widgets (when applicable) by ordering the key dimensions according to their position in the hierarchy" (then follow up with a concrete example).

I also don't want to sink too much work into the current widgets, if we're eventually switching to PhosphorJS anyway.

I totally agree. As for showing the relationship visually, that would be nice but I can't think of any quick and trivial way  to do that. Maybe file an issue and we can address this at a later time, hopefully after we've integrated with Phosphor JS!

I'm ok with removing the current code for hierarchical dimension handling from HoloViews, at least for now while reimplementing widgets, but I still think that giving users ways to explore multidimensional spaces easily is very much a core function of HoloViews.  So we'll have to revisit it at some point, preferably automatically in HoloViews from a user's perspective, but in any case at least laying out clearly how a PyViz user would handle this (common) case with any available tool.

I had a discussion with Jean-Luc recently where I pointed out that since the Panel refactor the entire cross-product of the parameter space is now exported. This fixed various issues where sparse parameter spaces would not appropriately hide elements. Overall supporting non-orthogonal parameter spaces automatically is not really feasible and resulted in a lot of complexity, which was quite brittle and had many bugs. Since we now have parameter dependencies and Panel widgets non-orthogonal parameter spaces can now be expressed in various ways and we are no longer going to support them in HoloViews.


Feat/select

PR for: https://github.com/posva/pinia-colada/issues/111

See https://github.com/posva/pinia-colada/discussions/113

If you want to go forward with this, I think creating plugins for commonly used options would be the way! 👍


No code, no hype, no star, no fork

Hi, thanks for the attention. We have released the source code.


refactor: setup composition when starting an encounter (#402)

Review Checklist

Summary*

[ ] fix: Bug fix for Add the items tackled here as checklists
[x] feat: Completed task
[ ] chore: Incomplete task

[ ] test: Sub-task 1

Structure*

[ ] The Pull Request has a proper title that conforms to our MR title standards
[ ] The Pull Request has one commit, and if there are more than one, they should be squashed
[ ] The commit should have a proper title and a short description
[ ] The commit must be signed off
[ ] Unused imports are not present
[ ] Dead code is not present
[ ] Ensure dry running library to confirm changes

Tests

[ ] Proper and high quality unit, integration and acceptance(if applicable) tests have been written
[ ] The coverage threshold should not be lowered

Sign off*

[ ] All comments have been resolved by the reviewers
[ ] Approved by Czar {replace_with_czar_name}
[ ] Signed off by second reviewer {replace_with_name}
[ ] Ensure all checks are done before merging :warning:
[ ] All PRs needs to be signed before merging :warning:

N/B:

Add a checklist if more than one item is done.
Add screenshots and/or images where necessary
Indicate any breakages caused in the UI :exclamation:
Where necessary, indicate which issue the Pull Request solves (Closes #)
Any new files are updated in the folder structure in the README

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

118 of 125 (94.4%)  changed or added relevant lines in 3 files are covered.
61 unchanged lines in 3 files lost coverage.
Overall coverage remained the same at 81.964%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/clinical/usecases/clinical/composition.go
21
22
95.45%

pkg/clinical/usecases/clinical/composition_helpers.go
32
34
94.12%

pkg/clinical/usecases/clinical/encounter.go
65
69
94.2%

Files with Coverage Reduction
New Missed Lines
%

pkg/clinical/usecases/clinical/composition.go
3
98.35%

pkg/clinical/usecases/clinical/encounter.go
18
92.41%

pkg/clinical/application/dto/enums.go
40
17.69%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7262

Relevant Lines:
8860

💛  - Coveralls


SLING-6867, Repoinit ACL handler should take aggregate privilege into…

… account

With the upcoming migration to git this repository will be deleted. If the pull request contains data that should be re-submitted I suggest that you save the changes locally and resubmit them after the migration, which will likely happen on Monday the 9th of October.


Indihome OLT push configuration to enforce ODI running as router mode

Hi All,
Recently I got problem with Indihome on my ODI. Earlier, it worked fine in bridge mode and MikroTik dialed successfully for 3 years ago.
Now it seems Indihome did some changes on their OLT to enforce ODI running as router mode (as below image). OLT pushed PPPoE configuration and OID dialed directly on it.
I already tried with SFU and HGU firmware (M110_sfp_ODI_220304.tar, M114_sfp_ODI_Vlan_220414.tar, M114_sfp_ODI_hybrid_221209.tar) and got the same result.
Can someone let me know if I block ODI to dial directly or prevent OLT push configuration of PPPoE so that my MikroTik can dial PPPoE?
Thank you,

let's troubleshoot,
can you share the output:
omcicli mib get 84
omcicli mib get 131
omcicli mib get 171

Hi @Anime4000,
Below are output from my ODI. It is running firmware version V1.2.2-221209.

Hi @Anime4000,
You can see NOTE: This wan is created by the olt!, so that I can't delete this and create new one. Also can't modify current PPPoE account.

Let me try to switch image to M110_sfp_ODI_220304.tar and delete nas0_0. Last time I could delete.

I am running version M110_sfp_ODI_220304.tar and delete nas0_0 and nas0_1 and create new one as below.
So, theoretically, I will dial directly on sfp interface, no need create vlan then dial on that vlan, is it?

Yes, try Admin Status: Disable, don't let OLT manage your port

I tried yesterday evening and it did not work.

First case: delete all auto configuration from OLT, then create interface nas0_0 as bridge mode and tag VLAN 2483 on WAN interface of ODI.
Second case: delete all auto configuration from OLT on WAN interface, then create VLAN 2483 on MikroTik .

I notice the ME 171, Entity Id 0x4101 some kind of special, the Me Point to 0x4### id
let's try override to use 0x101 (LAN 1)
omcicli mib set 171 0x4101 AssociatedMePoint 0x101
omcicli mib set 84 0x4101 FwdOp 0x02
omcicli mib set 84 0x101 FwdOp 0x02


Refund-Manager not visible in Shopware 6.5

It seems like, that the Refund-Manager is not visible in Shopware 6.5. We are currently setting it up in the development environment and double checked, that the refund manager is enabled. Also the admin storefront has been rebuilt.
Are there any other settings which we could check?

Hi there :)
in 6.5 it should be in a card above it
do you see this?

I'll answer: I could swear that this was not visible when @azngeek created the issue :D
But nevertheless the Button is always disabled... I don't see no clear indication, why this is the case, what are possible reasons? :)

hi there
buttons are not hidden but only disabled, to at least have some better knowledge on what exists
there is a check if shipping is possible, according to mollie, so if items are still left to be shipped
but there is also a side effect when the SwagCommercialPlugin is installed, then its always disabled.
this will be fixed in 1-2 weeks with the upcoming relase

Ahh yep, the project has SwagCommercialPlugin installed. Fine, then we'll wait for the update, thanks :)
I think you can close this issue

ok super, then it makes sense
perfect, we'll try to be fast :)


Add support for HW-KEY-HASH

Add and test the support for HW-KEY-HASH.

hw-key-hash checking support has been implemented as a variable, HWKH, and managed by the edk2 driver.


Dashboard banner should size to columns

Dev Home version
0.5
Windows build number
No response
Other software
No response
Steps to reproduce the bug
Have a horizontally filled dashboard with the banner visible
Expected result
No response
Actual result
Banner should snap to the column grid sizes

Included System Information
No response
Included Extensions Information
No response

This would be new feature work


Authorize users create subnet

What
Uses cancancan to authorise a user and only allow Subnet creation if they are an editor
Why
Building support for editor / viewer permissions so that we have granular control over what a user can do
Screenshots
Notes

Nice!


MWPW-133205 Update CSP

Codecov Report

Merging #273 (93a7129) into stage (c9fe140) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            stage     #273      +/-   ##
==========================================
+ Coverage   99.41%   99.50%   +0.09%
==========================================
  Files          26       26
  Lines        2224     2230       +6
==========================================
+ Hits         2211     2219       +8
+ Misses         13       11       -2

Impacted Files
Coverage Δ

acrobat/scripts/contentSecurityPolicy/dev.js
100.00% <100.00%> (ø)

acrobat/scripts/contentSecurityPolicy/prod.js
100.00% <100.00%> (ø)

acrobat/scripts/contentSecurityPolicy/stage.js
100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


issues with ывам-толд-2-0

Hi
Think you have some wrong characters on this layout.
You have mdash but not underscore.
You have the two hard signs instead of the soft signs. I am not Russian so don't know the correct terms. The other layouts have the soft signs.
What is English name for ывам-толд ?
Thanks, Ian

Think I am confused.
I modified my layout checker to handle Russian.
At the moment it says:
checking filename diktor.ru.ansi.json
checking diktor.ru.ansi
Error with diktor.ru.ansi.json : diktor.ru.ansi, characters not on keyboard: ₽
UNconventional
Not zxcv
Checking filename jcuken-typewriter.ru.ansi.json
checking jcuken-typewriter.ru.ansi
Unusual character '|' (ord 124) found on keyboard.
Error with jcuken-typewriter.ru.ansi.json : jcuken-typewriter.ru.ansi, characters not on keyboard: *₽
conventional
Not zxcv
checking filename jcuken–narrow.ru.ansi.json
checking jcuken–narrow.ru.ansi
Error with jcuken–narrow.ru.ansi.json : jcuken–narrow.ru.ansi, characters not on keyboard: ₽
UNconventional
Not zxcv
checking filename zubachev.ru.ansi.json
checking zubachev.ru.ansi
Error with zubachev.ru.ansi.json : zubachev.ru.ansi, characters not on keyboard: ₽
UNconventional
Not zxcv
checking filename ывам-толд-2-0.ru.ansi.json
checking ывам-толд-2-0.ru.ansi
Unusual character '`' (ord 96) found on keyboard.
Error with ывам-толд-2-0.ru.ansi.json : ывам-толд-2-0.ru.ansi, characters not on keyboard: ЪЬ₽
UNconventional
Not zxcv
For some reason in the last one it is picking up ЪЬ as missing, but they are there ... let me try some debug prints to see what is happening.
Will revert.

Ok so looks like it is missing the capital versions of the soft and hard signs. Are these redundant?

Ok so looks like it is missing the capital versions of the soft and hard signs. Are these redundant?

Hi iandoug! Sorry for the long silence (: ывам-толд-2-0 has soft and hard signs in lowercase only, because these letters are not used at the beginning of Russian words, but are used only in CAPITALS. With this layout, you can type uppercase soft and hard signs in Caps Lock mode.

The underscore sign in Russian can be considered obsolete, since it is used either on typewriters (actually for underlining) or in writing formal code. In the latter case, the Latin alphabet is the primary one.

characters not on keyboard: ₽

The ₽ sign is not standard, at least it is not present in the Russian Windows layout. I might suggest you replace the error message with a warning.


calling activate() hangs

Assuming the gripper is reset (all registers are 0). The following code hangs:
using Gripper = RobotiqSModelControlClient;
    ....
std::shared_ptr<Gripper> gripper(new Gripper());
      ....
ROS_INFO_STREAM("Activating the Gripper...");
gripper->activate();
gripper->setGraspingMode(Gripper::GM_pinch);
ros::Duration(5).sleep();
while(!gripper->activationCompleted() && ros::ok()) ros::spinOnce();
ROS_INFO_STREAM("...activated!");

Oddly when debugging the code in gdb the gripper begins its activation sequence after the gripper->activate() call.

After a bit more debugging I'm confused as to what the ros::Duration(...).sleep() is for in your example. That is should not while(!gripper->activationCompleted() && ros::ok()) ros::spinOnce(); this wait until the gripper is activated (or replacing !gripper->activationCompleted() with !gripper->stoppedAtRequestedPosition() should make it wait until it's done moving)?

Can't really remember, wrote this code a long while ago and it may be even incompatible with newer versions of the robotiq package. I would check by echoing the "/SModelRobotInput" topic and seeing if gIMC==3 after the activate() function has been called


feat: add queue limit and timeout for connection pool

Codecov Report
Attention: Patch coverage is 76.47059% with 16 lines in your changes missing coverage. Please review.

Project coverage is 69.92%. Comparing base (8dae5ae) to head (9e086ba).

Files with missing lines
Patch %
Lines

tools/connectpool/pool.go
75.00%
9 Missing and 3 partials :warning:

db/commonpool/pool.go
66.66%
2 Missing and 2 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              3.1     #340      +/-   ##
==========================================
+ Coverage   69.65%   69.92%   +0.26%
==========================================
  Files          87       86       -1
  Lines       10127    10163      +36
==========================================
+ Hits         7054     7106      +52
+ Misses       2377     2366      -11
+ Partials      696      691       -5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


docker-compose exec for searchguard initialized

docker-compose exec makes more sense to initialize searchguard, as all the commands using docker-compose.

Fair point, you can also remove the docker command in that case.


Exclude GetStackTraceALotWhenPinned test on zLinux

https://github.com/eclipse-openj9/openj9/issues/18908

@pshipton can you please take a look

It failed on xmac as well, now that we have xmac machines working again. Pls exclude it there as well.

Updated


Fixing issue 899

Fixes https://github.com/marmelab/ng-admin/issues/899
Added watcher to value.
After the change should be applied via $apply or better via triggerHandler('change').

Super-seeded by #1196


NO-JIRA Adding CompareUpgradeTest to fast-tests

first commit will fail, as I'm only adding it to fast tests (to test the test is actually picked up and failing since it's supposed to fail)

I will add the fix after the failure.

I will merge this for now. If anyone has a better solution please follow up with a new commit.

@gemmellr / @brusdev the OCD is strong on this one, I will have to fix it properly.. sending a fix by the end of the day :)
I will do the proper upgrade and parsing in jolokia-acces.xml

@clebertsuconic  I didnt see this comment until I came here to reference a commit...and I'm not sure youve seen my comment elsewhere, lol.
I've already pushed a change to address it in the way I was suggesting yesterday: https://github.com/apache/activemq-artemis/commit/1f3745c87d77252d81fa22486d4cc2a06420d66b


callback_phase issues with callback_url

Hi,
I've recently been trying to use your gem for a project i'm working on and I can't seem to get it working.
During the callback when the token is requested. The azure AD instance is throwing the following error:
AADSTS70002: Error validating credentials. AADSTS50011: The reply address does not match.
At first I thought I had a typo inside my app setup in azure but that wasn't the case.
Azure seems to complain about the fact that the underlying auth2 implementation of callback_url  appends the code parameter on the end of the redirect_uri and therefore it doesn't match what is is expecting.
Just wondering if you have run into this scenario?
Thanks

hi @andrew-whitmore , thanks for the note. I haven't seen this, but haven't been using this gem actively (project back burnered). It worked when we prototyped it, but I imagine something could have changed on the azure size. However, for authorization code grant type, the code needs to be sent back to the redirect uri.

Hi @marknadig - Thanks for your response. Just to let you know i got to the bottom of this in the end. Basically versions 1.3.1 of omniauth-oauth2 used to override the callback_uri in its strategy to the following:
def callback_url
        full_host + script_name + callback_path
      end

It looks like they thought this was a bad idea and removed it recently. What happens now is the callback_url method falls back the the oauth2 implementation which also includes request parameters. so on the second auth pass when going to the oauth2/token url azure complains because the redirect_url has the code parameter appended on the end so it throws the error hightlighted in my previous comment. I have just simply overridden callback_url in your strategy and it works fine.
Hope this makes sense.
Thanks Again
Andy

:+1: thanks for tracking this down.

Is there going to be an update to this gem? I'd like to see it working again.

@abezulski , I didn't have time to test Andrew's fix. I see it in his branch, but never submitted a PR. Sorry, time constraints :/    Curious, I see LightspeedSystems fork with a lot of recent activity, but they don't mention any of the issue Andrew mentioned.

@marknadig Thanks for reply. What would be the quickes way of getting it fixed in my code without building entire gem?

@abezulski quickest way would be just to ref abezulki's fork directly in your gemfile https://github.com/andrew-whitmore/omniauth-azure-oauth2/
http://bundler.io/git.html

I had the same issue and checked when omniauth-oauth2 changed the callback_url mentioned above. It appears to have been around 1.1.1 so for my gem I just set s.add_dependency 'omniauth-oauth2', '~> 1.1.1' which current resolves to 1.1.2 and solves the problem.

@thomas-siimpl can you open a Pull Request for that? :)

I needed a much newer version of omniauth (for compatibility with Rack 2.0), so I've built a version of this gem which brings omniauth up to 1.4.0 and sets callback_url without the query component:
https://github.com/nickcampbell18/omniauth-azure-oauth2
Looks like the omniauth-oauth2 team re-added the query component here. Seems like they can't decide which way to go on this.

@nickcampbell18 can you push your version as a PR on the official branch? :D

Brilliant @nickcampbell18.  Thank you so much for your fork, that fixed the callback query parameters issue for me with omniauth-1.3.1.
Can we get a PR?  Do we need some tests?


Idea : Stream playlist of another user in spotify ?

Sometimes, spotify's user shares link of playlist in this form : http://open.spotify.com/user/nameofuser/playlist/XXXXXXXXX. But i can't find how to open it in pimusicbox. I try to enter the URL directly in the "stream menu" and select spotify but it only add the XXXXXXXX in the queue and nothing happened.

You need to convert that into a Spotify URI by replacing http://open.spotify.com with spotify:// and replacing all / characters with : characters i.e. spotify://user:nameofuser:playlist:XXXXXXXXX
I think there is a future plan for it to understand the http://open.spotify.com links but we are not there yet.

Ok thanks man for the tip :)

The way ahead looks like this:

pyspotify 2 already understands open.spotify.com and play.spotify.com links.
Mopidy-Spotify 2 which use pyspotify 2 is soon to be released.
Mopidy issue #696 will hopefully be implemented in v0.20, making it possible for Mopidy-Spotify to claim ownership of open.spotify.com and play.spotify.com URIs.

When this is done, Pi Musicbox must upgrade to the new Mopidy-Spotify and Mopidy versions.


Failing with dbt

Hi,
I'm trying this out with https://github.com/fivetran/dbt-language-server but I'm getting the following error. If I disable emacs-lsp-booster things work fine. Let me know what info I can provide. Thanks!
[2024-05-24T22:40:24Z INFO  emacs_lsp_booster::app] Running server "dbt-language-server" "--stdio"
[2024-05-24T22:40:24Z INFO  emacs_lsp_booster::app] Will convert server json to bytecode! bytecode options: BytecodeOptions { object_type: Plist, null_value: Nil, false_value: Nil }
thread '<unnamed>' panicked at /github/workspace/src/app.rs:145:18:
called `Result::unwrap()` on an `Err` value: Server->client read thread failed

Caused by:
    Invalid header format

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: emacs_lsp_booster::rpcio::rpc_read
   2: emacs_lsp_booster::app::process_server_reader
   3: std::sys_common::backtrace::__rust_begin_short_backtrace
   4: core::ops::function::FnOnce::call_once{{vtable.shim}}
   5: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/boxed.rs:2007:9
   6: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/boxed.rs:2007:9
   7: std::sys::unix::thread::Thread::new::thread_start
             at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys/unix/thread.rs:108:17
stack backtrace:
   0:     0x77cfe055b8ec - std::backtrace_rs::backtrace::libunwind::trace::h370587616c149a45
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:     0x77cfe055b8ec - std::backtrace_rs::backtrace::trace_unsynchronized::h4cc55038e4a874cd
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x77cfe055b8ec - std::sys_common::backtrace::_print_fmt::hc26cc3c2eddc21d7
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:67:5
   3:     0x77cfe055b8ec - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hb67f6e94152691e9
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:44:22
   4:     0x77cfe059a0fc - core::fmt::rt::Argument::fmt::h1fd35fc4c88687b8
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/fmt/rt.rs:138:9
   5:     0x77cfe059a0fc - core::fmt::write::h738793984be7f52c
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/fmt/mod.rs:1094:21
   6:     0x77cfe055910e - std::io::Write::write_fmt::h84056616c47209ca
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/io/mod.rs:1714:15
   7:     0x77cfe055b6d4 - std::sys_common::backtrace::_print::h20a11f09f8216cd4
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:47:5
   8:     0x77cfe055b6d4 - std::sys_common::backtrace::print::h7b70e260a2475fa3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:34:9
   9:     0x77cfe055d173 - std::panicking::default_hook::{{closure}}::h81c979645f368377
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:270:22
  10:     0x77cfe055ce8c - std::panicking::default_hook::h157ab9bf73bc8932
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:290:9
  11:     0x77cfe04b60fe - emacs_lsp_booster::main::{{closure}}::hb2b0baf668103ab3
  12:     0x77cfe055d86e - <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call::hd2597171485cc473
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/boxed.rs:2021:9
  13:     0x77cfe055d86e - std::panicking::rust_panic_with_hook::hec9e488e5d9ea17f
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:711:13
  14:     0x77cfe055d5f7 - std::panicking::begin_panic_handler::{{closure}}::h83232311f2354a3d
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:599:13
  15:     0x77cfe055be16 - std::sys_common::backtrace::__rust_end_short_backtrace::h8a82556d18c9cf5a
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys_common/backtrace.rs:170:18
  16:     0x77cfe055d342 - rust_begin_unwind
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/panicking.rs:595:5
  17:     0x77cfe04a05d3 - core::panicking::panic_fmt::h9fb1cf80aef8bb8a
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/panicking.rs:67:14
  18:     0x77cfe04a099a - core::result::unwrap_failed::hdeffda1fd287c7d3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/result.rs:1652:5
  19:     0x77cfe04a717e - std::sys_common::backtrace::__rust_begin_short_backtrace::h056dc2d0ff09f963
  20:     0x77cfe04c8767 - core::ops::function::FnOnce::call_once{{vtable.shim}}::hd6158818be7a5cb0
  21:     0x77cfe0561af5 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::hc4b69460ab0b58b3
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/boxed.rs:2007:9
  22:     0x77cfe0561af5 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::hff9ab78020349a37
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/alloc/src/boxed.rs:2007:9
  23:     0x77cfe0561af5 - std::sys::unix::thread::Thread::new::thread_start::h7fa77081a8285658
                               at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/std/src/sys/unix/thread.rs:108:17

Process dbtls stderr finished

Hi,
Thanks for your report. Based on the error message, it seems that it received unexpected data from dbt-language-server (cannot parse as json-rpc header).
It would help a lot if you can post the output of the language server here. You may do it in this way:

Add a new dbt-language-server-wrapper.sh script in your $PATH (and remember to make it executable), with the following content:

#!/bin/bash
exec dbt-language-server "$@" < <(tee -a /tmp/dbt.stdin.txt) > >(tee -a /tmp/dbt.stdout.txt)

Change your emacs config to use dbt-language-server-wrapper.sh instead of dbt-language-server
Reproduce the issue with emacs-lsp-booster. Then you should find the input and output data to/from the language server in /tmp/dbt.stdin.txt and /tmp/dbt.stdout.txt respectively.

(I tried to reproduce this locally but unfortunately cannot get dbt-language-server working (constantly getting an "invalid_type" type error...).. )

Thanks @blahgeek ! Here is my emacs setup for dbt:
https://github.com/fivetran/dbt-language-server/issues/1426#issuecomment-2130470832
I can send you those files, but they contain some semi-private information. Can I email you? My email is on my profile.

I can now successfully run dbt-language-server based on your configuration, without any issues you mentioned :)

So I think I need your input/output contents to debug. I sent you an email.

Hi @egh ,
At the end of your dbt.output.txt there are the following lines:
{"jsonrpc":"2.0","id":3,"result":[]}Running server on localhost:40109...
Server listening on localhost:40109

These "Running server on ..." lines are the ones that causes the issue. The dbt language server should not output these contents to stdout according to lsp spec (it should only contains "Content-Length: xxx" followed by json objects).
So I think maybe you should report to dbt-language-server project about this bug. (Though as I said, I personally cannot reproduce this, so I'm not sure why or when it happens)
On the other hand, emacs-lsp-booster could try to tolerate this kind of error and try to recover. I think that's how lsp-mode itself does, which explains why you don't have this issue without emacs-lsp-booster enabled.  I will do this later.

Hi @blahgeek ,
Thank you so much for looking into this! I will file an upstream bug.


Louis: add chatbot to SICP textbook

Description
This is a follow up based on #2714
It depends on this change in the backend https://github.com/source-academy/backend/pull/1063
Implemented an embedded ChatGPT dialogue box for SICP. Students have the ability to inquire with GPT about the content they are currently exploring within a passage.
Need to add openai to dependency
Implementation:

As students navigate through a specific subsection(e.g. 1.2.3), the system records the current subsection and utilizes useRef to mark all divs containing text within that subsection.

When a student poses a question to the bot, useRef is employed to identify all paragraphs currently visible on the screen, and their text is extracted.

The system retrieves the summary of the current subsection from SICPNotes which contains short summary for subsections. Then the summary is incorporated into the prompt along with the text of the current paragraph, transmiting it to GPT as the "system," .

Student queries are sent to GPT, and the responses are received.

Code snippets in the replies are extracted and highlighted. A reminder is included at the end of the answer, specifying that the response is from GPT.

The responses are displayed on the screen for the students.

Concerns raised:

The GPT key is stored in the .env.local file of the project, and there's uncertainty about how to utilize it in the official version.

Creating useRef using a loop is not feasible. The manual creation and addition of useRef instances to an array are deemed cumbersome.

There's a lack of comprehension regarding Chapters 4 and 5 of SICP, leading to insufficient confidence in summarizing the content or evaluating the accuracy of GPT-generated summaries for these chapters.

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

-75 of 156 (51.92%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 37.274%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/pages/sicp/subcomponents/chatbot/Chatbot.tsx
7
13
53.85%

src/pages/sicp/Sicp.tsx
1
10
10.0%

src/pages/sicp/subcomponents/chatbot/ChatBox.tsx
1
61
1.64%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
5893

Relevant Lines:
14849

💛  - Coveralls


i18n(pl): Add new aliases.mdx translation

What kind of changes does this PR include?
Translated content
Description
Added Polish translation for the aliases page

LGTM


A very specific but irritating problem with SCM

In the company where I work the project structure is as follows: .../PROJ_NR/software/<.git folder>+
In Source Control Repositories only the parent folder is displayed, which results in displaying only 'software' names. Is it possible for SCR to recognize identical folder names and add one more parent folder when it recognizes two identical names? I am adding a picture of how it looks like in practice at the moment.

@RTS007, would it help if there would be an option to display the path of each repository in the repositories view?

@RTS007, would it help if there would be an option to display the path of each repository in the repositories view?

Yes, any information to distinguish between repositories would be helpful.


Merging and publishing an improved project fork

Hello,
I've been looking to use this solution as part of my projects but found it having poor SSL support capabilities. I saw there is an ssl-improvements branch already created but I believe there isn't any real work going on it since it's been quite a while since any new commits happened on it and the work is unfinished. Fortunately, I found a fork of this project  https://github.com/gekiss/serilog-sinks-rabbitmq which already has implemented these features and has some other improvements too.
Would you possibly consider merging in the fork features and releasing a new version of the nuget? I'm sure it would be beneficial for everyone. In my case particularly, it would avoid me maintaining the forked and locally build assets.
Thanks!

Related - #124

@sarunasil Working on it.


Reflect error on StandardMaterial serde

Bevy version
Current main (dev for 0.12)
What you did
Trying to serde a StandardMaterial through reflection
What went wrong
brings an error: Custom("no variant found at index 4128768 on enum bevy_pbr::alpha::AlphaMode")
Additional information
Test in branch: https://github.com/raffaeleragni/bevy_sync/blob/bevy_0_12/src/proto_serde.rs#L148

Created https://github.com/bevyengine/bevy/pull/10167 to reproduce it through tests directly in bey.


feat: Allow DataFrame.join for self-join on Null index

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Thanks Trevor!
Should we add an e2e test for the .fit(X, y) table with null index / unordered mode, too?

Good idea. This revealed that ml modules were caching pre-join, which is invalidated by row-identity join. Instead, I made it cache post-join.


Erro to install

Hi, i'm running marathon install johnsundell/testdrive command, but return this error:
   Updating packages...
💥  Failed to update packages
👉  Make sure you have write permissions to the folder '/Users/raisiqueira/.marathon/Packages/'

Hi @raisiqueira 👋
I'm guessing you're running Xcode 9.1 and that you installed Marathon through Homebrew? If that's the case, then you'll either need to wait for Marathon 2.0.0 to become available on Homebrew, or simply re-install Marathon through Make, which will give you 2.0.0 which includes a fix for Xcode 9.1.
Hope the above solves your problem - let me know 👍


Update setup.py for PyPI publish

Codecov Report

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

@@          Coverage Diff          @@
##           master     #1   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines         251    251
  Branches       46     44    -2
=====================================
  Hits          251    251

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 c1e1329...5a3f59e. Read the comment docs.


Change Date Format

Is there anyway to change the date format from YYYY-MM-DD to MM-DD-YYYY?

I know this is old but for posterity:
options="locale: { format: 'MM-DD-YYYY' }"

Thanks!


A new Zero-Knowledge cheatsheet and related section name "make-up"

Hi everybody
After the previous cheatsheets the intention was to write the next one about Bulletproof (the "to be continued..." of the third infographic). However very soon it has been clear that Zero Knowledge Proofs theory is mandatory to have a comprehensive understanding about how BP works (apart from being a very interesting field by itself, laying foundations for many cool techs): so I have authored and I'm PRing this new cheatsheet, as a step of an ongoing documentation effort.
I have tried to not miss the basic core concepts despite the simplified approach and topics selection, stressing ideas more than formalism: the merit of this cheatsheet, if any, is trying to represent an at-hand, concise, first bridge between theoretical foundations and applications developers approaching this world (not necessarily cryptography professionals). Of course this kind of resource cannot be a rigorous reference, but authoritative sources that I have consulted are listed, to let the interested reader dig deeper: definitely not an easy task, but worth the study these books require.
I have taken occasion for a small "rebranding" of cheatsheets section: as said I consider them as an ongoing documentation thread, in which boxes colours have a semantic meaning (even if weak) but also a unifying function as a recurring theme... and they really remind me salmons colours, from raw to cooked 😉  I hope the name I'm proposing is not too shallow, but if it is I'll not complain reverting to the current published one.
See ya

Hi everybody
any news? I link the deploy preview to make more comfortable to take a look at the cheatsheet :)
https://deploy-preview-1986--barolo-time-757cf9.netlify.app/library/ZKbasicsCheatsheet20220621.pdf

you are right @SamsungGalaxyPlayer , it wasn't my intention to mortgage the space :) ...just unconsciously beginning to think I was the only one with a cheatsheets' "fetish" lol
I think "X cheatsheet by Salmon" could wrongly suggest "Salmon" is a nick of mines, so I guess a better option would be to rollback the section name as you suggest and to list my cheatsheets (with unchanged names/descriptions) as a bullet list in a group named "The Salmon Series". What do you think about it?
I'm going to wait a few days before re-commmiting and squashing, to gather any further opinions

I have made the changes stemmed from the talk with @SamsungGalaxyPlayer and squashed to make the merge clean:
https://deploy-preview-1986--barolo-time-757cf9.netlify.app/library/

Hi @erciccione
nice to see you back here! 👍
I got your point about html tags location.. it has been my doubt as well, but I followed Z2M and MM sections as tie-breakers (they both have links and bullet list in en.yml) because confining html tags to index.md would have implied a bunch of variables (instead of only two) interleaved with tags/links.  I'm just saying this because it seems relevant to me , anyway no problem to follow your suggestion if you confirm your preference :-)

@erciccione ok I got it... now that I understand the reason (thanks for the explanation!) perhaps I can get what you are looking for without reverting to the previous structure (I like the section style stemmed from talk with samsunggalaxyplayer)... please gimme a few days to try refactoring it before final decision

Here it is, I think I have fully decoupled localize-able strings from html tags :)


Lea County, NM

Contact:
http://www.leacounty.net/p/Departments/Community-Development/271
http://www.leacounty.net/p/Elected-Officials/195

Closing as stale - Feel free to open a new issue if someone is actively going after these.


Update scopes according to internal meeting

It was one of the roadmap plans to change the current scope of each Meilisearch developer.
This PR applies the changes we discussed in an internal meeting today on May 17.

Well done team! 🎉