Don't close suggest widget when cycling with tab completion

I really like the "editor.tabCompletion": "on setting, but as soon as I insert a suggestion the suggest widget closes and I am no longer able to see the suggestions I am cycling through while pressing Tab.
I would expect the suggest widget to stay open, mainly because I consider the concept of tab completion as indifferent to the presence of the widget. When I turn tabCompletion on and from then on the widget disappears as soon I am choosing what to insert, this kind of feels like a surprising side effect.
I would prefer the widget to stay open as long as I am cycling through suggestions, close/refresh it with the next Non-tab keystroke and therefore have it open as long as I am using tab completion. This way I instantly see how often I have to press tab until I reach the suggestion I want to insert.
Therefore I suggest an additional option to keep the widget open when using tab completion.
Also I guess this is what #59828 was actually about, but I don't use Xcode, so I am not 100% sure.

I really like the "editor.tabCompletion": "on setting, but as soon as I insert a suggestion the suggest widget closes and I am no longer able to see the suggestions I am cycling through while pressing Tab.

That's what this feature is all about. Inserting suggestions without the suggest widget visible...

If you disagree, please explain what is expected and what is not in more detail.

I would not expect to have tab cycling coupled with the visibility of the suggestion widget. The disappearance of the widget is neither what I'd expect when turning "editor.tabCompletion" to "on", nor what I'd expect when I read the feature documentation: "Enables tab completions."
When I turn "editor.tabCompletion" to "on" I'd expect to be able to insert completion suggestions with tab. I would not expect "inserting suggestions without the suggest widget visible..."
If it is a design decision, not to have the possibility to swap out suggestions with the tab key and keep the suggestion widget open at the same time, I disagree with it.
My argument is the following: Logically separating the visibility of the suggestion widget and the ability to cycle the suggestions with the tab key increases the users degrees of freedom on customizing the editor.
In my case I would like to be able to have this:

Please correct me, if I'm wrong, but as far as I can see, this is currently not possible with VS Code.

Please correct me, if I'm wrong, but as far as I can see, this is currently not possible with VS Code.

You assign tab instead of arrow-up/down to cycle through the suggestion list which does some of what you want

Yes, I know. But I have to confirm every suggestion with Enter instead of just being able to type on.
I would be grateful if you could briefly confirm my understanding that by design there is and will be no option enabling what I want.

Unlocking since my request was marked as duplicate of this one: #74111

That's what this feature is all about. Inserting suggestions without the suggest widget visible...

I thought this feature is all about I can use tab rather than

using up/down which are at more awkward keyboard positions than tab
typing out the full suggestion

Currently if I'm using tab to select non-first item, then my subsequent tab are all guesses in the dark because I can't memorize all the list. This isn't really what I want...

https://github.com/microsoft/vscode/issues/70532


Missing baseline_15.1.1713.9

Describe the issue
The script reports me many .js files in directory "ClientAccess\Owa\prem\15.1.1713.9". I can not see a basefile for this version in the repository and there is no entry as valid version for E16 in the script. Seems for me to be a false positive. Creation Date of the files is the time and date when we installed Security Update For Exchange Server 2016 Cumulative Update 12 (KB4515832)
Expected behavior
Base files for all exchange version and fixes
or
if it makes sense just scan the current version

The same applies to "ClientAccess\Owa\prem\15.1.1713.6" (KB4487563), "ClientAccess\Owa\prem\15.1.1713.7" (KB4503027) and "ClientAccess\Owa\prem\15.1.1713.8" (KB4509409)

should be fixed with recent releases, please retry with latest script (https://github.com/microsoft/CSS-Exchange/releases/download/v<IP_ADDRESS>3/CompareExchangeHashes.ps1)
also, if the missing *js files are localized files (e.g. *Strings.localized.min.js), then it is caused by the fact that we did not collect baseline data for localized files, please follow #313 for baseline updates

#313

The baseline for 15.1.1713.6 still missing


I don't really know what to do here...

Describe your problem here.

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

make sure you add null checks

how would i do that-

if (insertvarhere != null)

also make sure you take coding lessons and learn how haxe works too while you're at it

i was just trying to play a fnf mod :(

well it's a problem with the mod, not the engine


No init build against musl libc

There's no build of rustup-init against musl libc, which means that rustup cannot be installed on Alpine Linux, for example, without building rustup yourself.

Building rustup-init for x86_64-unknown-linux-musl is not going to be enough because there is no rustc component for that triple. I'm not aware of anyone that has built a working rustc for that triple. I have tried and managed to built a rustc but it always crashed in the LLVM phase when I tried to compile anything. Probably, LLVM needed more patching (I applied some of Alpine Linux patches) to work correctly with musl but I didn't investigate further.

Alright then, my bad. This issue isn't really relevant to rustup then, so I'll close it.
Thanks anyway!

Using https://github.com/emk/rust-musl-builder I've just built what appears to be a perfectly good x86_64-unknown-linux-musl rustup-init (nothing fancy, just a cargo build --release). Is this problem now solvable or am I missing some other missing detail?

@palfrey, @japaric: Also wondering ...

It's still not possible to build a rustc that works on musl distros like Alpine. PR rust-lang/rust#40113 is one of the requirements to build such rustc.

It's still not possible to build a rustc that works on musl distros like Alpine.

That’s not entirely correct. It is possible (see APKBUILD), I did it in August 2016 (with your help), but it requires cross-compiling rustc against musl on GNU-based system and applying some hacks.
It’d like to also note that there’s no problem with musl itself, just in Rust build system. 😿

Oy, the cargo package on alpine:edge fails to access the cargo index, due to linking against a broken libgit2... Could someone fix the Alpine rust & cargo packages plz

Rust and Cargo in Alpine testing are currently broken. We’ve updated Rust to the latest version, with better patches that allow both dynamic and static linking on Alpine. Initially it seemed that everything is okay, but then we found many breakages. Still hard working on it, fixing Rust build system…

Now that https://github.com/rust-lang/rust/pull/40113 has closed can't this be reopened?

@japaric WDYT?

@fzgregor

@japaric WDYT?

The same thing as almost two years ago:

Building rustup-init for x86_64-unknown-linux-musl is not going to be enough because there is no rustc component for that triple.

Is rust-lang/rust producing rustc binaries for x86_64-unknown-linux-musl? I'm no longer involved with infrastructure stuff so I don't know. Producing rustc binaries is a rust-lang/rust issue that the infra team is in charge of so you should ask them.
P.S. Also, I'm not a rustup developer so I can't reopen issues in this repo.

Thanks I will ping them then. This is super important for things like building rocket services into a docker container

Is rust-lang/rust producing rustc binaries for x86_64-unknown-linux-musl?

No, they still do not. 😞 However, it is possible to build rustc on and for x86_64-unknown-linux-musl system with fully working both static and dynamic compilation, but it still requires some patches (see here). We in Alpine Linux do it since rust 1.17.0 (package rust). About half of the patches has been already upstreamed, somewhere between 1.19.0 and 1.21.0.

@raphaelcohn Your amazing! After only a little playing it looks like you don't even need the patches
FROM frolvlad/alpine-glibc

RUN apk add --no-cache curl bash

RUN curl https://sh.rustup.rs -o rustup-init
RUN chmod +x rustup-init
RUN ./rustup-init --verbose -y --no-modify-path --default-toolchain nightly --default-host x86_64-unknown-linux-gnu
RUN rm rustup-init

ENV PATH=/root/.cargo/bin:"$PATH"
RUN rustup target add x86_64-unknown-linux-musl
RUN rustup update
RUN rustc -Vv

ENTRYPOINT ["rustc"]

However it does appear that if I try to compile anything with a C/C++ dep then it implodes on jemalloc. I will have to look into other solutions there.

@raphaelcohn actually it looks like this may finally be coming anyway! https://github.com/rust-lang/rust/pull/55163


Support Jupyter notebook integration

Some users might want to use Neoscore inside Jupyter notebooks for interactive development and exploration. For many users, especially those coming from more academic backgrounds, as our users often do, Jupyter notebooks are a comfortable and familiar environment.
It seems to be pretty straightforward to build out such an integration. I suggest the following behavior:

Follow Matplotlib's pattern of magically detecting whether we're running inside a Jupyter session, then overriding the behavior of neoscore.render_image so that it renders to a Jupyter cell.

This necessarily makes the dest filepath argument redundant; the API should be updated to make that argument optional, then perform a runtime check. If running in Jupyter, the argument must not be provided (or should be ignored and log a warning if provided). If running outside Jupyter, the argument must be provided.

Make neoscore.show() raise an error if called inside Jupyter. Jupyter does support interactive cells, but I believe this would be much more complicated to integrate than it's worth, at least while we don't know how useful this would be for users.
The integration should not add any new dependencies to Neoscore. We can integrate with the IPython API only when available using the fallible import pattern; we already do this for our repl integration.

Released now in 0.1.16. Thanks @demithetechie !


Feature request: allow quotes strings containing commas in .fromSamplesheet() for .csv files

At this moment, it is not possible to create a channel from a .csv file with the .fromSamplesheet() function if the .csv file contains a quoted field that contains a comma.
id,path,description
sample1,reads.sample1.fq.gz,"no problems here"
sample2,reads.sample2.fq.gz,"oh no, I cause issues"

The line in row 2 will be split on the no, as well, which is not the desired behavior.
It should be easy to add this functionality by adding the appropriate parameter value  quote:true (https://www.nextflow.io/docs/latest/operator.html#splitcsv) to the following line:
https://github.com/nextflow-io/nf-validation/blob/b040ebbddf55163f61b8a0c22f49d5450146519b/plugins/nf-validation/src/main/nextflow/validation/SamplesheetConverter.groovy#L75
But perhaps it is even a good idea to allow all .splitCsv parameters to be passed through as well?

Hi @koenbossers thank you again for the great issue! Can you open up a PR to add this?


Chinese translation.

I had to change the font (again), but it looks to be working:
preview
Will now need to test all other languages with this font, to see if nothing else breaks.
If all goes well, I should be able to release this this weekend.


feat: Proposal for reconcile and Kafka version stored in Kafka Status

Proposal for reconciled version metadata to be included in the CRs recording which operator has finished reconciling
This allows better user story for confirming an upgrade has completed.

After going your review comments and a small slack discussion about this proposal, I have reworked it to be in the status now. I think this is now a lot simpler, and though we could propogate annotations through to the pods in the SPS's to track upgrade, i don't think this is necessary due to how the KafkaReconciler will wait on all pods to be ready post rolling update.

I have posted another update:

remove managedBy field
added a kafka version field to identify multi-reconcile upgrades
added potential extra fields for inter broker protocol version and log format version as these could be relevant (discussion to be had)
add clarity to examples and make clear why and how status fields wont be removed when set

@samuel-hawker Inter broker protocol version and log format version are basically deprecated as far as I understood. log.message.format.version is ignored is inter.broker.protocol.version is 3.0 or higher. inter.broker.protocol.version is not deprecated formally. But it is not used in KRaft mode. So it will be essentially removed in Kafka 4.0. So not sure I would include those given they cannot be easily removed later.

A great point. I will remove.

Thanks for the review comments.
I have removed the sections that just confused matters, and elaborated on the node pool case, proposing that we choose the minimum of all the node pool versions, but I suspect you may have thoughts as to whether this is a good solution or not.

I have removed the sections that just confused matters, and elaborated on the node pool case, proposing that we choose the minimum of all the node pool versions, but I suspect you may have thoughts as to whether this is a good solution or not.

TBH, I have only one idea with regard to the Kafka version and Node pools. We could make it list => today we can list there only one version. If we ever support multiple versions, we could list all used versions. Not sure it is good, but it would allow us to extend it to multiple versions if needed 🤷♂

A list is sensible - alternatively if we are quite convinced the scenario is unlikely, we can keep the field as a single string, and in the unlikely event multiple kafka versions are needed we just comma delimiter them i.le.
status:
  versions:
    kafka: "3.5.0,3.5.1"

this is probably not ideal, but if we genuinely think Strimzi supporting such configurations is unlikely it might be better, since I think it would be marginally easier for a user to verify a string field contains a version, rather than parsing a yaml/json array and checking for its presence as a element, but I could be persuaded either way here.

@samuel-hawker I guess that would work for me. Maybe you can add it to the proposal and add the proper list to the rejected alternatives and we will see what other reviewers think?

@samuel-hawker I should have add: "Thanks for the proposal"!

Thanks for the review @tombentley
To answer your questions:

No status.versions.zookeeper or distinguishing the version of the KRaft quorum? I know we wouldn't support people using a different kraft version than broker version, but there's a window during upgrade where they will differ.

I have not included zookeeper here as soon it will be removed, but additionally, from a user perspective I think a user would be more inclined to care about their kafka version, than their zookeeper version, since this is what they will be tracking during upgrade.
This proposal is solving the following problem: For the Kafka Custom Resource it is often unclear when an upgrade has truly finished, whether all the brokers have rolled and to which version of the operator a cluster has been reconciled with and which version of Kafka. and I am not personally of the opinion that the zookeeper version adds anything to this goal.

Should we also publish status.versions.cruiseControl too, similarly for other components? While I'm not advocating for or against that, I think we should be explicit why we are/are not doing that.

Similar justification to point 1, since a user will be tracking upgrade through the kafka and lastSuccessfulReconciliationBy fields, I feel like lastSuccessfulReconciliationBy specifically covers all components and the level of granular version checking is not required for all components, besides Kafka which is a special case due to its multi-roll situation.

3 Having the single status.versions mixes operator versions with component versions. To me those are quite distinct. Did you consider status.operatorLastSuccessfulVersion and status.kafkaVersion (or possibly status.componentVersions.kafka if we see a lot of value in the grouping)?

I did consider this, however I then decided that mixing all of these versions was reasonable as a user might want them all in one place (the versions.<x> fields, however I can definitely be persuaded to change it to: status.operatorLastSuccessfulVersion (or lastSuccessfulReconciliationVersionBy) and status.kafkaVersion
Given my answers to 1 and 2 though I am unsure about the status.componentVersions.kafka grouping as you suggested.
I hope this answers your questions!

@samuel-hawker thanks. Your answers to 1 and 2 make sense. For 3, I don't feel very strongly, but I think I prefer status.operatorLastSuccessfulVersion and status.kafkaVersion. I'm interested to hear what others think.

@samuel-hawker thanks. Your answers to 1 and 2 make sense. For 3, I don't feel very strongly, but I think I prefer status.operatorLastSuccessfulVersion and status.kafkaVersion. I'm interested to hear what others think.

I would not have a problem with having them in the .status directly.

@samuel-hawker thanks. Your answers to 1 and 2 make sense. For 3, I don't feel very strongly, but I think I prefer status.operatorLastSuccessfulVersion and status.kafkaVersion. I'm interested to hear what others think.

My preference is having status.versions but if the majority feels it's better having all versions directly under status I can live with it.

Given the pre-existing fields in the status do not already set a precedent for nesting, I think it makes sense for the versions fields to sit at the same level as clusterID, i.e. directly in the status field.
I will rename the fields to:
status.operatorLastSuccessfulVersion
status.kafkaVersion

FYI @scholzj @tombentley
@ppatierno does this sound reasonable to you? Happy to tweak the names, or leave with the versions field if any new conversations/reasoning come to light.

@PaulRMellor thank you so much for such a thorough review, addressed every comment.
Functionally no changes to proposal.
We have so many approvals now - are there any more thoughts or can we move this towards a merge?

@samuel-hawker I usually say something like If no new comments are received until tomorrow EOB, it will be merged and give one more day or so to everyone to have a look. Please do not forget to rename the file (52 is already taken) and add it to the index in README.md before merging it 😉.

Rebased branch + renamed file + added to index - thanks for the reminder Jakub!
If no new comments are received until tomorrow end of day, it will be merged
Thank you everyone for helping to refine this proposal!

Merged. Thanks again everyone.
Raised an issue: https://github.com/strimzi/strimzi-kafka-operator/issues/9002 and self-assigned


Crash with Texfix

Version 1.1.1-133 of VanillaFix crashes when loaded along with version 1.12-4.0 of TexFix.
Crash: https://paste.dimdev.org/uzovoqovur.mccrash

Disable TexFix. The newest version of VanillaFix makes it useless.


Update bitflags to v1 and publish v0.2

Breaking change, raises the minumum supported rust version to 1.20.

I'm all in favor of keeping deps up to date, but I'm not sure what the advantages / disadvantages of this move will be. Some people might want to compile with older Rust. Also, I don't think incrementing the minimum language version is considered breaking by Rust semver conventions.
I might scoop this in when making other actually breaking changes.

@raphlinus main reason is that version is "1.0" which means it won't be braking anymore (until 2.0)

Closing due to lack of CLA. Happy to accept a PR to upgrade bitflags. I don't think bumping to 0.2 is necessary, as upgrading bitflags shouldn't be considered a breaking change for semver purposes.


README.md: add a link to racket bindings

Signed-off-by: Maciej Barć<EMAIL_ADDRESS>Didn't knew where I should put that section. Right now I put it in such a place that link reference numbers don't have to be changed.

Looks good for now, thanks for your contribution and for creating those bindings.

Thanks for great library and cooperation.


Universal Package does not create new package if a similar name already exists

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Universal packages
Environment

Server - Azure Pipelines

If using Azure Pipelines, provide the account name, team project name, build definition name/build number: https://dev.azure.com/bosch-ciam/skid/_build/results?buildId=196263&view=logs&j=b3812022-0a90-52bf-5e32-d6630aef4c89&t=eb1f1b6f-37ca-50ff-46df-ab0b0d3cff20

Agent - Hosted

If using Hosted agent, provide agent queue name: 439

Issue Description
[Include task name(s), screenshots and any other relevant details]

The task is not able to upload a package to the given feed. As stated here the issue might be that a package with a similar name already exists: https://github.com/microsoft/azure-pipelines-tasks/issues/13983
Name of existing package: 1.0.0-ciamauthn-xxx
Name of package to be uploaded: 1.0.0
Task logs
Downloading: https://08wvsblobprodsu6weus73.vsblob.vsassets.io/artifacttool/artifacttool-linux-x64-Release_0.2.236.zip?sv=2019-07-07&sr=b&sig=Isa3jrUguKGKouWwDuoGndT87Lc7gXlbxp1%2FF1DjQ2g%3D&spr=https&se=2022-05-17T10%3A30%3A10Z&sp=r&P1=1652783110&P2=11&P3=2&P4=WcY9fEaKFdedgIVj7pz%2FOKnDkGm3xb61gNrxAMwMCDs%3D
Caching tool: ArtifactTool 0.2.236 x64
##[error]Error: Failed to get package versions
##[error]Packages failed to publish
Troubleshooting
log.txt
Error logs
Downloading: https://08wvsblobprodsu6weus73.vsblob.vsassets.io/artifacttool/artifacttool-linux-x64-Release_0.2.236.zip?sv=2019-07-07&sr=b&sig=Isa3jrUguKGKouWwDuoGndT87Lc7gXlbxp1%2FF1DjQ2g%3D&spr=https&se=2022-05-17T10%3A30%3A10Z&sp=r&P1=1652783110&P2=11&P3=2&P4=WcY9fEaKFdedgIVj7pz%2FOKnDkGm3xb61gNrxAMwMCDs%3D
Caching tool: ArtifactTool 0.2.236 x64
##[error]Error: Failed to get package versions
##[error]Packages failed to publish

This issue also exists in Found tool in cache: artifacttool 0.2.239 x64.

This issue is still there.

I just had the same issue.
There was a demo_config in the artifact feed. Then I tried to publish a new artifact called config and the error (Failed to get package versions) kept coming up until I changed the artifact name to main_config.
I was using ArtifactTool 0.2.266 x64.


Dota 2 update appears to have broken requestProfile

Since the Dota 2 client update earlier today I'm getting back an err 80 in the requestProfile callback which appears to indicate that the request is disabled according to the eresult enum. I'm wondering if maybe they updated the protobuf message signatures for this request since a few of the patch notes indicate potential changes to the internal API (Fixed dashboard performance impact of the friends list, enabled team matchmaking).
Tried on a couple diff steam accounts so I don't think it's that I'm rate limited or anything, plus I don't think I'd get a response back anyway if I was. I'm running a version a few commits back in the 1.0.0 branch so in the meantime I'll try a more recent commit and see if that fixes anything.

Looks like Valve is getting rid of the old player profiles and moving to profileCards?
@paralin might have a better idea of what's going on.
Sample response:
{"account_id":88367253,"background_def_index":0,"slots":[{"slot_id":0,"trophy":null,"stat":{"stat_id":5,"stat_score":2122},"item":null,"hero":null,"emoticon":null},{"slot_id":1,"trophy":null,"stat":{"stat_id":1,"stat_score":3911},"item":null,"hero":null,"emoticon":null},{"slot_id":2,"trophy":null,"stat":null,"item":null,"hero":{"hero_id":53,"hero_wins":156,"hero_losses":null},"emoticon":null},{"slot_id":3,"trophy":null,"stat":null,"item":null,"hero":{"hero_id":109,"hero_wins":129,"hero_losses":null},"emoticon":null},{"slot_id":4,"trophy":null,"stat":null,"item":null,"hero":{"hero_id":77,"hero_wins":91,"hero_losses":null},"emoticon":null}],"badge_points":4475,"event_points":null,"event_id":null}

For reference, stat_ids:
https://github.com/SteamDatabase/GameTracking/blob/c6903e73783d4affafdd619610a8e13b4db282e7/Protobufs/dota/dota_gcmessages_common.proto#L1619

Changes I have heard of:

Profile requests only work when friends
You MUST specify engine:1 in the request. See the PR I submitted before.

Other than that it should work.

Tried it with friend+engine, still was getting error: 80.
You could double-check

I'm trying with friends + engine as well, same thing.

Confirming error 80 now. The call has been disabled. Time to port to profile cards.

Ah cool, hadn't seen the discussion about profile cards until now. The implementation from @Crazy-Duck  is working well for me for the moment.
Does this mean we need to tell our friends to put their MMRs on their profile if we want to be able to track it now?

Yeah. You need to display it in the profile if you want to track it. Guessing @howardchung isn't getting much sleep right now.

lol, actually I already implemented it a couple hours ago (it only took about 30 minutes):
https://github.com/yasp-dota/yasp/commit/f2b662bcb6e799ee023830a438601ab65a2e2cd3
However, I did it on development branch and may not deploy for a couple weeks.  MMR tracking is pretty low priority.

I don't remember if this was fully actioned. Anyone remember?

I believe this was fixed with #138 ?

Response from profileRequest is error 80

Error 80 is "disabled". Are you using a non-limited account? Try it manually. This may also mean something else.

Isn't requestProfile discontinued by valve? It was replaced by the profileCard if I'm not mistaken..
On 25 Nov 2015 22:22, jimmydorry<EMAIL_ADDRESS>wrote:Error 80 is "disabled". Are you using a non-limited account? Try it manually. This may also mean something else.
—Reply to this email directly or view it on GitHub.

non-limited accout.. what does it mean? i'l just try fetch a mmr, from requestProfile. Now i can do it from profileCard if user select it

Replaced by profileCard. No longer an issue.


[QUESTION] Apparent poor performance in SKGLControl when overlaying bitmaps

Hello,
I'm new to SkiaSharp, am trying to use it with its OpenGL backend to pan, zoom and overlay large bitmaps, and I'm seeing poor performance I don't understand.   When I draw a single bitmap, drawing is very quick.  But when I overlay a second bitmap, performance drops precipitously.  I don't doubt that I'm using SkiaSharp incorrectly, but I don't see where.
I'm on windows 10 build 19043.1348, using the SkiaSharp, SkiaSharp.Views.Desktop.Common and SkiaSharp.Views.WindowsForms nuget packages, all v2.80.3.
Here is code that demonstrates the behavior.  This code creates an SKGLControl and a form containing it.  (My understanding is that the SKGLControl handles OpenGL, and I don't need to do anything further to get GPU acceleration.  Is this right?)
The code then loads three bitmaps, two from the same file.  It then proceeds to draw the bitmaps on the SKGLControl repeatedly, measuring the time between each iteration.  There's a configuration variable (run_case) that says what to draw, and the timings for each case are shown below.
[STAThread]
static void Main()
{
    var form = new Form { Size = new System.Drawing.Size(1400, 800) };
    var control = new SKGLControl { Dock = DockStyle.Fill }; form.Controls.Add(control);

    // All images Width=4992 Height=4096 AlpaType=Opaque ColorType=Bgra8888 isTextureBacked=false
    var image1 = SKImage.FromEncodedData(@"bitmap1.png");
    var image2 = SKImage.FromEncodedData(@"bitmap2.png");
    var image3 = SKImage.FromEncodedData(@"bitmap1.png");  // note, this is the same bitmap loaded as image1

    var draw_count = 0;
    var timer = System.Diagnostics.Stopwatch.StartNew();

    var run_case = 6;

    control.PaintSurface += (object sender, SKPaintGLSurfaceEventArgs e) =>
    {
        var opacity = 1f;
        var src_rect = new SKRect(0, 0, image1.Width, image1.Height);
        var dest_rect1 = SKRect.Create(0, 0, control.Width, control.Height);
        var dest_rect2 = SKRect.Create(0, 0, 0.8f * control.Width, 0.8f * control.Height);
        var paint = new SKPaint { FilterQuality = SKFilterQuality.None, Color = SKColors.White.WithAlpha((byte)(255f * opacity)) };
        var canvas = e.Surface.Canvas;

        switch(run_case)
        {
            case 1:
                canvas.DrawImage(image1, src_rect, dest_rect1, paint);
                break;
            case 2:
                canvas.DrawImage(image2, src_rect, dest_rect2, paint);
                break;
            case 3:
                canvas.DrawImage(image1, src_rect, dest_rect1, paint);
                canvas.DrawImage(image1, src_rect, dest_rect2, paint);
                break;
            case 4:
                canvas.DrawImage(image2, src_rect, dest_rect1, paint);
                canvas.DrawImage(image2, src_rect, dest_rect2, paint);
                break;
            case 5:
                canvas.DrawImage(image1, src_rect, dest_rect1, paint);
                canvas.DrawImage(image2, src_rect, dest_rect2, paint);
                break;
            case 6:
                canvas.DrawImage(image1, src_rect, dest_rect1, paint);
                canvas.DrawImage(image3, src_rect, dest_rect2, paint);
                break;
        }

        draw_count++;
        var msec_per_draw = timer.ElapsedMilliseconds / (double)draw_count;

        canvas.DrawText($"msec/draw = {msec_per_draw:F0}", new SKPoint(100, 100), new SKPaint { TextSize = 32, Color = SKColors.Blue });
        control.Invalidate();
    };

    Application.Run(form);
}

Here are the times printed by the DrawText call.  Because the Stopwatch is created on the main thread, then the form and SKGLControl are created and initialized before the draw loop starts on the graphics thread, I've let the program run a while to let this time settle down.
case 1: 18 msec <- draws bitmap1 once
case 2: 18 msec <- draws bitmap2 once
case 3: 18 msec <- draws bitmap1 twice
case 4: 18 msec <- draws bitmap2 twice
case 5: 510 msec <- draws bitmap1 then bitmap2
case 6: 403 msec <- draws bitmap1 then bitmap1 again as different image instance
Also, when running these cases in visual studio community 2019 with the debugger, it looks like one core is saturated in cases 5 and 6.
If I load the png files as SKBitmaps rather than SKImages, the case 5 & 6 times are somewhat less but still much greater than the other cases.  If I remove the assignment to the Color property of the SKPaint and let that default, the times don't change.
What is going on with these times, and what mental model should I have about what Skia is doing that explains them?  Do I need to initialize the SKGLControl differently?  I had thought that Skia would transfer the images as bitmaps to the GPU and render them onto the openGL context there, with very little work done by the CPU.  That doesn't seem to be the case when overlaying the second image.
My goal is to render multiple bitmaps overlayed with transparency and to pan and zoom them smoothly.  My machine's GPU should be capable of doing that, and I think Skia should be able to use the GPU do it.  These bitmaps are fairly large (4992x4096), and GDI+ is too slow.
Thank you,
Mark Shirley
p.s., If I switch from using SKImage to using SKBitmap explicitly and then create the bitmaps via new SKBitmap(4992, 4096, true) rather than reading them from files, the behavior is similar.  The speed of case 3 (draw image1 twice) is still 18 msec and the speed of drawing two different bitmaps (created the same way) is 241 msec. This is faster than the example with images with varying data in them but still much slower than drawing a single image either once or twice.
I've also calling SetImmutable() on each of the SKBitmap's, with no change to the behavior.

p.s., If I create the bitmaps via new SKBitmap(4992, 4096, true) rather than reading them from files, the speed of case 3 (draw image1 twice) is still 18 msec but the speed of drawing two different bitmaps (created the same way) is 241 msec, an order of magnitude slower.

This was due to a cache holding raster data on the GPU.  From an SKGLContext, this cache size can be set like this.  control is an instance of SKGLContect.
control.GRContext.SetResourceCacheLimit(number_of_bytes)
The default size of this cache in the version I'm using is 100,663,296 bytes, which turned out to be too small for my application.  control.GRContext will return null before the context has been initialized.  I'm not where it's best place is to set this cache size ... I'm doing it once, the first time the paint method has been called.  I also don't know whether it's reset of the graphics context is regenerated for some reason.


[Bug]: WriteToFiles(output_fn=...) is seemingly unused

What happened?
There's a ctor argument output_fn to WriteToFiles that isn't used other than setting a member variable that is never read:
https://github.com/apache/beam/blob/0d58d23f2d9c34ae5f068acddc622fa3ac6b0854/sdks/python/apache_beam/io/fileio.py#L542
Issue Priority
Priority: 3 (minor)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

agreed, appears to be never used. We could clean it up and force keyword-only arguments after it. It could be a breaking change for some users, so could also not touch it and add a note that it's unused and leftover for backward compatibiltiy.

.take-issue

@ima-attac-helikoptaaa are you still working on it?

agreed, appears to be never used. We could clean it up and force keyword-only arguments after it. It could be a breaking change for some users, so could also not touch it and add a note that it's unused and leftover for backward compatibiltiy.

To sum up we shouldn't change it ?

we can still make the clarification in the code that it is unused. Removing is fine too as long as we force keyword-only args.

agreed, appears to be never used. We could clean it up and force keyword-only arguments after it. It could be a breaking change for some users, so could also not touch it and add a note that it's unused and leftover for backward compatibiltiy.

should we add a note on the docstring so that it is visible for the caller

.take-issue


Service worker files do not get chunked

Describe the bug
Service workers do not get chunked like web workers.
In few words, sw file does not get chunked:
navigator.serviceWorker.register(new URL('sw.js', import.meta.url), {
  type: 'module',
  scope: '/',
});

but if used for a web-worker, it does:
let worker = new Worker(new URL('sw.js', import.meta.url));

Reproduction
https://stackblitz.com/edit/vitejs-vite-pw6vnq?file=main.js
Steps to reproduce

Run npm run build
Check dist/assets folder and you'll notice the chunk for sw.js is missing

System Info
System:
    OS: Linux 6.5 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 8.76 GB / 15.30 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash

npmPackages:
    @sveltejs/vite-plugin-svelte: ^3.1.0 => 3.1.0
    @testing-library/jest-dom: ^6.4.5 => 6.4.5
    @testing-library/svelte: ^5.1.0 => 5.1.0
    @vitest/coverage-v8: ^1.6.0 => 1.6.0
    eslint-plugin-svelte: ^2.35.1 => 2.35.1
    jsdom: ^24.0.0 => 24.0.0
    svelte: ^4.2.12 => 4.2.12
    svelte-preprocess: ^5.1.3 => 5.1.3
    svelte-spa-router: ^4.0.1 => 4.0.1
    svelte-tags-input: ^6.0.0 => 6.0.0
    vite: ^5.2.11 => 5.2.11
    vite-plugin-dynamic-import: ^1.5.0 => 1.5.0
    vitest: ^1.6.0 => 1.6.0

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Duplicate of #2248


a script on page load in a edit-view does not receive its context

Describe the bug
When I run this small  server side script below at the click of a button in an edit-view it works fine.
But if I switch this server side script to run on page load of thet same edit-view it gives an error. Even though the Builder says that the variable order is in scope.

Expected behavior
the scope variables should the there to use.
Screenshots
Error shown in the event log:

fixed in #2298

hi Tom
I can print the total received context/row/payload but I can not get the individual items from it. It looks like it's missing a parse.

hi Tom
I can save the total received context/row/payload to my help-Table  in my server-side script but I can not get the individual items from it. It looks like it's missing a parse?
BTW I tried fetchJSON() function on the context/payload/row as described in the help-text but it gives an error.


Fix feathersErrors.errors === undefined error

Summary
When disallowing a route through disallow('external'), this error occurs:
TypeError: Cannot read property 'MethodNotAllowed' of undefined
    at Object.context ([path]/feathers-hooks-common/lib/services/disallow.js:18:24)

That may be due to a possible change in @feathersjs/errors. In the current version, error functions like MethodNotAllowed reside on the feathersErrors object itself instead of feathersErrors.errors.
Other Information
All tests passed.

Thanks for this.


Use udp protocol to solve the p2p connection reliability

https://bitsharestalk.org/index.php?topic=12244.0

This would be great but unlikely to happen for the foreseeable future.


Add constraint to UnsupportedConstraint error in _check_constraints

This provides helpful information, in case you have larger
input files.
This improves https://github.com/nvie/pip-tools/commit/b53f79b1006f87ed213a8b46fdcdd144c073fd1b.

This is also included in #169.

@nvie
Was this closed intentionally?

This was fixed in ef0d1808609557dfbe04f98f2bd8668866a00512.


after flatpak was updated: bwrap: Can't mkdir /usr/lib/x86_64-linux-gnu/GL: Read-only file system

$ flatpak info fi.skyjake.Lagrange

Lagrange - A Beautiful Gemini Client

          ID: fi.skyjake.Lagrange
         Ref: app/fi.skyjake.Lagrange/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 1.11.1
     License: BSD-2-Clause
      Origin: flathub
  Collection: org.flathub.Stable
Installation: user
   Installed: 4.0 MB
     Runtime: org.freedesktop.Platform/x86_64/20.08
         Sdk: org.freedesktop.Sdk/x86_64/20.08

      Commit: 1a713cd1e1dd2c653e751860eb198f10fde680b53558482c0d253d5ab28909d1
      Parent: f4514db410563054e3d8ec4f25e6a168c28afac72996ce6f92da1c6ff7bb6c14
     Subject: Updated for v1.11.1 (8617093a)
        Date: 2022-03-02 13:07:42 +0000

$ flatpak --version
Flatpak 1.12.6

I recently updated flatpak (via apt-get, to the latest version on devuan), and that seems to have broken a number of things, lagrange among them. Mindustry was also affected, but they published an update that fixed it. When I try to run Lagrange, I get the following error message:
$ flatpak run --verbose  fi.skyjake.Lagrange
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path ~/.local/share/flatpak
F: Opening user flatpak installation at path ~/.local/share/flatpak
F: Skipping parental controls check for app/fi.skyjake.Lagrange/x86_64/stable since parental controls are disabled globally
F: Opening user flatpak installation at path ~/.local/share/flatpak
F: Regenerating ld.so.cache ~/.var/app/fi.skyjake.Lagrange/.ld.so/b576ce46e67ccbbfc6f24cda07198045d08f8f002fdce4899de02d2a1239c7ff
F: ~/.local/share/flatpak/runtime/org.freedesktop.Platform/x86_64/20.08/0e5f59c847f90b344208dc0f2b67bc27c9e4f3ab1a1a78fa56cdd0fb81c35274/files/lib32 does not exist
F: Running: 'bwrap --args 22 ldconfig -X -C /run/ld-so-cache-dir/b576ce46e67ccbbfc6f24cda07198045d08f8f002fdce4899de02d2a1239c7ff.iC7UHC'
bwrap: Can't mkdir /usr/lib/x86_64-linux-gnu/GL: Read-only file system
error: ldconfig failed, exit status 256

Unfortunately I have no idea what could be the problem here. If any Flatpak users know about this, I'm all ears...

Uninstalling, uninstalling unused dependencies, and then reinstalling everything seems to have worked.


[Issue] Error: Mismatch in TLS version for client and server when RegKey "Enabled" set to Value "0xffffffff"

Hello Team!
We get the following error from the HealthChecker Script regarding TLS Settings
================================================
Security Settings
LmCompatibilityLevel Settings: 5
	Description: Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM and NTLM authentication responses, but it accepts NTLMv2.
TLS 1.0
	Server Enabled: False
	Server Disabled By Default: False
	Client Enabled: False
	Client Disabled By Default: True
TLS 1.1
	Server Enabled: False
	Server Disabled By Default: False
	Client Enabled: False
	Client Disabled By Default: True
TLS 1.2
	Server Enabled: False
	Server Disabled By Default: False
	Client Enabled: True
	Client Disabled By Default: False
		Error: Mismatch in TLS version for client and server. Exchange can be both client and a server. This can cause issues within Exchange for communication.
SystemDefaultTlsVersions: True
SystemDefaultTlsVersions - Wow6432Node: True
SchUseStrongCrypto: False
SchUseStrongCrypto - Wow6432Node: False
SecurityProtocol: Tls12
	For More Information on how to properly set TLS follow these blog posts:
		Exchange Server TLS guidance Part 1: Getting Ready for TLS 1.2: https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Exchange-Server-TLS-guidance-part-1-Getting-Ready-for-TLS-1-2/ba-p/607649
		Exchange Server TLS guidance Part 2: Enabling TLS 1.2 and Identifying Clients Not Using It: https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Exchange-Server-TLS-guidance-Part-2-Enabling-TLS-1-2-and/ba-p/607761
		Exchange Server TLS guidance Part 3: Turning Off TLS 1.0/1.1: https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/Exchange-Server-TLS-guidance-Part-3-Turning-Off-TLS-1-0-1-1/ba-p/607898

================================================
TLS 1.2 is akticvated fpr Client and Server, but we use the Value of
Enabled=0xffffffff
inated of
Enabled=1
for the DWORD in
EXCHANGESERVER\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server\
But both values should have the same effect, right?

Hi @Sektorsync. The Health Checker project was moved to: https://aka.ms/ExchangeHealthChecker . Please use the latest version.
You should use 0 or 1 instead of 0xffffffff because this value can cause issues. Please see: https://github.com/dpaulson45/HealthChecker/issues/220


[WIP][Service Bus v1] Relaxing the scheme check

Can only be merged after releasing amqp-common v-1.0.0-preview.14 https://github.com/Azure/azure-sdk-for-js/pull/8402
TO DO

[x] Relax the scheme check in amqp-common - #8402
[x] Bump amqp-common version to preview.14
[x] Release amqp-common preview.14
[ ] Run the tests in this branch to make sure it works fine
[ ] Merge this for service-bus 1.1.7 release

/azp run js - servicebus tests

1 test failed with a timeout.(Seems to be just a transient error)

Triggering again.

/azp run js - servicebus - tests

@HarshaNalluru Shouldnt we be triggering tests after changing the base branch to 1.1.7?

/azp run js - servicebus - tests

Looks good, I believe all the check boxes are checked now. We can go ahead with the merge?

And remove the WIP from issue title?


VyjayantiN

I have submitted a c language code on linear search

I have also written a code for bubble sort


Add window to be visible in panel apps

I'm not sure why, but in others WMs, the window is listed as something and in Weema, don't

This needs EWMH support. Just set _NET_CLIENT_LIST atom property and manage this (not too simple for now)

Made in last changes. Partially EWMH compliant


Linked 2D views

🚀 Feature
It would be great if napari had the ability to show data as linked orthogonal views. e.g. Clicking or dragging across the current coronal plane causes the image in the sagittal and horizontal planes to update.
Motivation
Fiji and Icy both have an orthogonal views feature. At the SWC we wrote an orthogonal views Python-based viewer, Lasagna, for visualising registration to the Allen Atlas. It's a very convenient way to navigate the data. It overlays traced neurons Allen brain areas, etc, but becomes slow for datasets over about 5 GB. We would likely move to napari if it supported linked orthogonal views.

Thanks @raacampbell! This is definitely on our to-do list, but it appears we didn't have an issue for it!

Yes, we first need to add support multiple canvases each with their own cameras, and then need to set up various types of linking. Orthogonal views is one you mention (possibly with the full 3D view in the remaining corner). Another is linked 2D views in a grid mode for zooming into the same spot. This was requested in #565, where we quickly implemented a grid view with just one camera, but where we still need to implement the linked camera version

Also @raacampbell if you're interesting in contributing around this feature, or any of the others on our 0.2 and 0.3 milestones (or features that should be added to those milestones) let us know. We'd love to work with you. Lasagna is very impressive, and I'm sure you learnt a lot during that process that's very relevant here.
We're also planning to build a plugin ecosystem around napari where more domain specific analysis tools can live and be used from within the viewer - see #263 for some really early ideas around that - and would love your input there too

I would love to but right now I'm overwhelmed with coding and construction on some hardware projects. I'm hoping to slowly transition back to analysis, though, so contributing to napari is something I would like to do. I don't see the sense in developing multiple very similar solutions to the same problem and you have something much more mature and interesting than I do.


lint: update the check range

Signed-off-by: zhouhao<EMAIL_ADDRESS>

why do we need this?

Closed.


Standalone package tests failing to load unittest dependencies

The tests in tests/standalone/package construct their own packages directory, but still use the unittest package. Now that unittest has dependencies of its own, this is problematic.
Right now, it looks like the only test that's failing on the bots is the analyzer test for standalone/package/package_isolate_test. This seems to be because it's already marked as failing on the VM for some reason.

Unit test is not used


Tune the behavior of the Paratime Picker - Clicky version

Rationale coming at the next chance to talk.
See #479  for a no-click alternative.

After discussing this with @donouwens , we came to the conclusion that this is not (necessarily) what we want to do here.
Let's come back to this after I have created a new test version based on what we have discussed.

Updated as discussed


ci: add markdown link checker

Summary

This PR adds a new job called validate-markdown-links to our PR Lint workflow that scans only the modified markdown files in a PR for broken links.
We could configure this job to scan for all files and not just the modified files but that would make the check extremely slow. Let me know if this is something we need, though!

To-do

[ ] Find a fix for the 'dynamic' links in our docs site's content. Context
[ ] Create a script in our package.json that lets us run this check on all the files in the codebase locally if we want.

Closes #731

Does this validate external links as well?
Did you try running it against all files to see how long it takes?

We should try validating all .md files, if possible. The ones standalone (readme, contributing, etc.) and the ones from the Docs/Guide. This would guarantee we'd know when some external link breaks, not only manual mistakes made on modified files. A good example is the links to the Sway docs.

Needs to re-sync with master!

@arboleya

Yeah it does handle external links!
It was taking longer than 25 minutes (it failed at 25 mins because it found a broken link) :/

Let me see if I can do something to cut down the running time. One easy win I can see is ignoring the files inside of _guide because the same content is then sent to the auto-generated guide folder anyways.

Alright, that is way too slow. Your first approach is the best, indeed.

In the future, we could search for a similar tool that we can run locally and on-demand, to scan all files.

In the future, we could search for a similar tool that we can run locally and on-demand, to scan all files.

@arboleya I think we can use this command for that:
find . -name \*.md -print0 | xargs -0 -n1 markdown-link-check

We'll need to use this package called markdown-link-check. I think the Github action I added uses the same package under the hood.
I can add this as a script in our package.json.

@Dhaiwat10 Perfect!

Note CI (PR title validation) seems frozen; I tried renaming it but it didn't help. A new commit might do it.

Fixed the formatting! Having some issues with the command to run the checks locally, though. Figuring it out

I came across a bug: with the current setup this action won't be able to parse 'dynamic' links like this one in our docs site's content. Need to find a workaround for this, too.

@camsjams Would it make sense to run this validation against the guide directory instead?
Any drawbacks?

@camsjams that sounds fair, let me take a stab at this

This is how I'm thinking of going ahead with this one, please correct me if I'm wrong:

We will have a Github workflow that checks only the modified files for broken links (this is buggy rn, working on a fix)
We will have a local / npm script (eg. lint:docs) that, when ran, scans our entire codebase for broken links in markdown files. (right now it only scans the docs)

Have made some decent progress but still need to iron out some edge cases that keep popping up.

This is how I'm thinking of going ahead with this one, please correct me if I'm wrong:

We will have a Github workflow that checks only the modified files for broken links (this is buggy rn, working on a fix)
We will have a local / npm script (eg. lint:docs) that, when ran, scans our entire codebase for broken links in markdown files. (right now it only scans the docs)

Have made some decent progress but still need to iron out some edge cases that keep popping up.

Converting this to a draft until it's ready to be reviewed.

An update on this PR:

I think we should reduce the scope of this PR to only adding a Github action that checks the modified files in a PR for now. I propose creating a separate issue for a local npm script that runs the check on all the files in our codebase. There might be some additional work needed for that.

Re. checking links in our docs, the approach that Cam suggested won't work because even after running pnpm typedoc and generating the guide directory before running the check, the links in the markdown files still contain v{site.data.versions.sway etc. These 'phrases' are parsed and replaced only in the .html files inside of the _site folder.
tldr: to make sure there are no broken links inside of our docs, we should be checking the HTML files generated inside the _site folder and not the .md files inside of the guide folder.

To summarize:

We'll need to check the .html files inside of docs/_site to make sure there are no broken links in our docs.
We'll need to check the rest of our .md files for any broken links. (these would mostly be readme files)

Marking this as blocked for now

@Dhaiwat10 We might be able to resume this PR after #811 is merged.

cc @Torres-ssf

@Dhaiwat10 I feel we can resume this PR with the new docs, no?

cc @Torres-ssf

Oh yes, we can resume this one now. Will resume work on this 👍🏻  @camsjams @arboleya

Closing this in favor of #1010


Unit tests failing for versions of tinymce >= 4.3.13

INFO [Chrome 51.0.2704 (Mac OS X 10.11.4)]: Connected on socket JdQ1Ub4KOxbanMWXi3C0 with id 20342993
Chrome 51.0.2704 (Mac OS X 10.11.4): Executed 0 of 11 SUCCESS (0 secs / 0 secs)
Chrome 51.0.2704 (Mac OS X 10.11.4): Executed 1 of 11 SUCCESS (0 secs / 0.06 secs)
Chrome 51.0.2704 (Mac OS X 10.11.4): Executed 2 of 11 SUCCESS (0 secs / 0.072 secs)
Chrome 51.0.2704 (Mac OS X 10.11.4): Executed 3 of 11 SUCCESS (0 secs / 0.077 secs)
Chrome 51.0.2704 (Mac OS X 10.11.4) uiTinymce compiling this directive should execute the passed setup option FAILED
Expected spy setupFooBar to have been called.
at /Users/tunnicliffel/Projects/ui-tinymce/test/tinymce.spec.js:63:35
Chrome 51.0.2704 (Mac OS X 10.11.4): Executed 4 of 11 (1 FAILED) (0 secs / 0.275 secs)
It appears that the provided setup function is no longer being called.

@lee-tunnicliffe, I saw you opened a PR and then closed it. Was it not fixed with your changes?
Do you want to re-open it? I think there is an issue with the latest version of TinyMCE, I still need to look into. I hope to make some time to do that today.

I am going to close this for now. The tests are a mess, and I haven't had time to get to them yet.
I have commented out all broken tests, and the rest should be working at current time. If anyone wants to take a stab at cleaning up the tests, please feel free to open a PR.


[Request] Add support for react-native-windows

Embedding VLC in react-native-windows would be amazing.
I understand that this may too difficult, but can't hurt to ask.

I am a bit packed at the moment, yeh but we should certainly give a try. We do have the player window in here, maybe we can leverage on that and get it working. I will make you a contributor if you are happy to put some hours on to this. I will lend you a hand whenever I get a minute

+1 this would be really cool

+1 on this, it would be great to see this!


Show part of next and previous items

Is there any way to achieve something like this:

You can achieve this by making the lSSlideOuter and lSSlideWrapper classes to overflow: visible.
But make sure you have the parent wrap of the whole carousel set to overflow: hidden.
Then you can make all the li set to opacity: 0.2 except the li with .active class.

@melvindidit Thanks! Can you check this fiddle? Where did I make a mistake? https://jsfiddle.net/dim2k/g649anwe/1/


Rename methods to be more consistent and deprecate the old ones

Motivation:
Some of the methods used source_cid and destination_cid in the name while most others uses scid and dcid. Naming of methods should be consistent to make it easier to discover things.
Modifications:
Add new methods with consistent naming and deprecate the old ones
Result:
Cleanup of public API

@ghedo @LPardue let me know what you think .... I noticed this while working on exposing a few methods via ffi that I need ...

@ghedo up to you ... I only kept them to no introduce breaking changes . If you think we should remove these let me
Know and I will update the PR

+1 to just breaking things now rather than later :D


Add pointer related codes

Codecov Report

Merging #91 (944c870) into master (8764188) will decrease coverage by 0.31%.
The diff coverage is 44.44%.

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


how to hide vscode C# codelens view

Environment data
dotnet --info output:
VS Code version:
C# Extension version:
Steps to reproduce
how to hide vscode C# codelens view
i change the setting :
"csharp.testsCodeLens.enabled": false,
but it doesn't work.
Expected  behavior
close the code lens
Actual behavior

i found the answer in others issues. thank you guys.~


Azcopy is much slower compare to earlier version

azcopy_linux_amd64_10.23.0
Note: The version is visible when running AzCopy without any argument
Linux
time /abc/share/ms-azure/azcopy_linux_amd64_10.23.0/azcopy sync --recursive /abc/homebackup17feb24/shared-home "https://abc.file.core.windows.net/confqanfs/shared-home/$SASTOKEN"
Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.
The performance is prolonged and even the percentage information displays wrong. if you see the below provided info it copied 635158 files out of 905800  but still shows 51.3 %
INFO:
51.3 %, 635158 Done, 0 Failed, 270642 Pending, 905800 Total, 2-sec Throughput (Mb/s): 0
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution? No

Which AzCopy version are you comparing v10.23.0 with? v10.22.0
Is only sync operation compromised or all? I think only Sync

Thank you for your response @challaswamy097 ! As mentioned in https://github.com/Azure/azure-storage-azcopy/issues/2596, we are taking deeper look into performance and will update both threads.

@siminsavani-msft Can you help me to download the Azcopy of older version for Linux azcopy_linux_amd64_10.22.2

Absolutely @challaswamy097 ! Here you go: https://azcopyvnextrelease.blob.core.windows.net/releases/release-10.22.2-20240110/drop.zip


Implement "InstagramUploadPhotoRequest add possibility upload photo from web (using URL)".

For now, we do not need download required image on our machine to upload it.

That makes sense. Thanks @kolobych


Fix error behavior

I have fixed the error message behavior.
Because it may be empty.
And I have fixed warnings.

Thank you!


Issue with pandas dependency

Hi Matthew,
I tried installing MGEfinder on Stanford's sherlock through conda and it seemed to finish successfully. However, the help command mgefinder —help results in the following error:
ModuleNotFoundError: No module named ‘pandas.compat'
I also tried installing a more up-to-date version of pandas, but still produces the same error. I figured you might be able to help me, considering that you probably used sherlock to develop the tool. Do you know what might be going on?
Thanks!

Hi! I actually didn't use sherlock to develop the tool. If possible, I would use the singularity installation for batch computing. I don't really know how to help you otherwise.

In case anyone else runs into this issue, it's caused by a known anaconda issue where conda environment supersedes its own libraries with ones installed in .local instead. We were able to fix it by setting env var PYTHONNOUSERSITE.

Great! Thank you for explaining this.


Changed controls & did house keeping

I fixed up the controls so that they make use of the event keysym rather than the raw char. This allows for cross-platform key consistency. I tested the controls on both Windows and Linux and they work perfectly - and they should also work for Mac, too. I added in controls for the arrow keys and a quit key set to the escape key.
Also, I cleaned up the structuring of the code so that it's much more neat and tidy. Hope you don't mind...

Thank you!


Wardley Map: support maturity and visibility values in JSON model

Node and note coordinates are stored using x,y (Bloc values) like:
"x" : 0.25,
"y" : 0.75,

We want to support maturity and visibility values too:
"maturity" : 0.25,
"visibility" : 0.25,


[Tutorial] Transform Your Selfie into a Stunning AI Avatar with Stable Diffusion - Better than Lensa for Free

https://www.youtube.com/watch?v=mnCY8uM7E50

In this video, I will show you how to create your own Lensa app-like magic avatars without using any third-party apps. Our method ensures 100% privacy, unlike uploading your personal photos to external apps and platforms. I am sure you have seen many people sharing their magic avatars on social media. While these paid apps use free open-source AI models, they still require payment. Additionally, AI image generation apps may keep your private photos and use them as they please. Instead of paying and trusting the goodwill of these paid apps, we will use these open-source public AI models ourselves. I will provide step-by-step instructions, so even those with no technical expertise can follow along. We will be using Google's Colab, a free #AI platform that offers access to a powerful GPU at no cost. Therefore, this tutorial can even be completed on a mobile phone without a PC. All you need is a Gmail account. Once we train the open-source image generation model #StableDiffusion with #DreamBooth by using our own portrait images, the possibilities are endless. Unlike other applications, the method I will demonstrate does not impose any limitations on image generation. You will be able to freely compose any kind of image as many times as you desire. You can not only generate your own avatars, but also any other images you want, such as highly detailed car images or landscapes.

you can add this tutorial to the guide - readme section of the repository

Is it possible to achieve the same using DiffusionBee on your local Mac?

Is it possible to achieve the same using DiffusionBee on your local Mac?

I don't know mac but you can do on windows


What is the correspondence between the date of prediction and the dates during backtest?

Suppose that I use Alpha360 for the input features, which contains data from day (T-59) to day T and by default the label is given as Ref($close, -2) / Ref($close, -1) - 1, thus what the model predicts on day T should be traded on T+2. Where is this time difference addressed in the backtest? I don't see any date adjustments in the example code.
And also, if for example I use Ref($close, -1) / $close - 1 as the prediction target, (how) should I adjust the dates in the prediction dataframe?
Thanks!

https://qlib.readthedocs.io/en/latest/component/data.html#example
Can your question be answered by this doc?


"mySchema" variable is not defined in first example

I think "mySchema" needs to be "BookSchema" in the first example. "mySchema" is not defined in that example at all.

Fixed thanks.


MCR-empirical trace

First working version of the empirical trace construction.

@radicamc  you should assign at least one reviewer (I assume Geert Jan and maybe Loic?) to look over this - otherwise they may not see that you made a pull request.
You can do this on the right hand side at the top

Making some updates based on tests with mirage simulations at the ers-hackaton. Will reopen pull request when these are done.


Open Source Collective relations

Discuss with Open Source Collective how our future relation should look like.

Take-aways from meeting with OSC:

The 10 percent fee is independent of the budget and not negotiable.
If we want to work with a contractor for an undetermined period of time, they prefer to use a payroll company independent of the labor laws in the respective countries. This is a bit surprising to me because I expect them to take care of taxation issues.

In any case, I think OSC makes sense for MapLibre at the moment and if we should grow and become financially sustainable, we can always think of alternatives.


Update for RoomOS 11.9

Cisco has released documentation for a new on-premises endpoint software release.

RoomOS 11.9 API documentation PDF
Room Kit software downloads
RoomOS 11 release notes
Historical Room series API documentation
Online xAPI documentation

Superseded by #3.


Exception thrown in FileGraphLibrary is incorrect

Within _getProperties method if the exception is thrown it will get the Schema path and throw that within the exception.  This should be the properties path.  Line 127 of FileGraphLibrary.java.  Also addIds (line 101) gets Schema path, should be getGraphsPath

Merged into develop


The duck shouldn't only make a sound when hit but also give a visual signal

It may be turn more red for a while or later we can think of a more suitable animation for that like flapping its wings.

Looks like a duplicate of https://github.com/Quit975/DuckyGame/issues/18 :) closing this one


Swift 4

I can understand not wanting to merge this into master until Xcode 9 is out of beta – you may want to make a swift-4 branch that can become the base branch for this PR?

Hi, I created branch swift4. Can you please PR to that?

When can we expect the PR to be merged?

sorry for late applying


Run Go format: gofmt -s -w .

Run gofmt -s -w .
Commit and push the result

This is part of a slightly larger goal of getting ergo listed on the awesome-go repo.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

been reworked. not valid anymore


Zarr+CuPy+GDS+nvCOMP made easy

Introducing open_cupy_array(), which is a CUDA friendly version of zarr.open_array that reads and writes to CuPy arrays.

/merge


Update diablo.go

Fixed issue with Diablo Run where walkable character would not reach diablo after interacting with last seal (save and exit game).  Now compatible with both teleporting/walkable characters.
Update 2: Now skip (abort run) if kill diablo is unchecked after last seal

You are right i carried an unused function . I will correct this. However movement being call at the end of infector part is intended .  In v2 refactored version it could be outside of it but right now it wont work if i let it at the same place it was.

Obsolete with #422


Move GGD unit tests to separate file

Description

Moves GGD tests that do not need the network to a separate file.
The following unit tests were moved from aws_test_greengrass_discovery.c to aws_test_ggd_unit.c with no changes to the tests themselves, besides naming:

GetIPOnInterface
CheckForContentLengthString
Jsoneq
CheckMatch
GetCertificate
GetCore
IsIPvalid

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


Added notice of removal of Export-SPOQueryLogs

Added notice of removal as Export-SPOQueryLogs will not be supported beginning February 2022. It is replaced by the Microsoft Search download search history feature in https://myaccount.microsoft.com/settingsandprivacy/privacy.

Docs Build status updates of commit 260e528:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md
:x:Error

Details

sharepoint/sharepoint-ps/sharepoint-online/index.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOGeoAdministrator.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteGroup.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBuiltInSiteTemplateSettings.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserInfo.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPODeletedSite.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgNewsSite.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPublicCdnOrigins.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOUser.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHideDefaultThemes.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md

Line 0, Column 0: [Error: MAML2Yaml_LoadFileFailed]

Failed to load file: W:/hafb-s/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md:2:(0) '> [!NOTE]
> Beginning February 2022, we'll be rem...'
 Expect Heading, please try to use PlatyPS validate the content

sharepoint/sharepoint-ps/sharepoint-online/index.yml

Line 82, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Get-SPOTenantRenameStatus'.
Line 150, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Set-SPOBuiltInSiteTemplateSettings'.
Line 182, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Start-SPOTenantRename'.
Line 186, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Stop-SPOTenantRename'.

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOGeoAdministrator.yml

Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOGeoAdministrator.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteGroup.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOSiteGroup.yml'.
Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOSiteGroup.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBuiltInSiteTemplateSettings.yml

Line 7, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOBuiltInSiteTemplateSettings.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserInfo.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'New-SPOSiteGroup.yml'.
Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Get-SPOUser.yml'.
Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOUser.yml'.
Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOUser.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.yml

Line 11, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'set-SPOGeoStorageQuota.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPODeletedSite.yml

Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Restore-SPODeletedSite.yml'.
Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPODeletedSite.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgNewsSite.yml

Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOOrgNewsSite.yml'.
Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOOrgNewsSite.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOExternalUser.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPublicCdnOrigins.yml

Line 11, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'New-SPOPublicCdnOrigin.yml'.
Line 13, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOPublicCdnOrigin.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOUser.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'New-SPOSiteGroup.yml'.
Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Get-SPOUser.yml'.
Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOUser.yml'.
Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOUser.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHideDefaultThemes.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOHideDefaultThemes.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.yml

Line 15, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOGeoAdministrator.yml'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@dariomws  @get-itips

@dariomws

close > reopen

@traya1
Hi, Thomas,
Can you please help?
Thanks!

Hi @tiburd,
Given that the topics with warnings were not modified by the contributor, I created a replacement PR with the proposed change.
It looks like the original change was approved for merging and I will merge the replacement once all checks are cleared.
Lastly, I believe that a known bug affected this PR so I will apply the "Do not merge" and leave only myself as the assignee for troubleshooting at a later date.
Let me know if ya'll have any questions or concerns.
Thanks!

Docs Build status updates of commit e8d8eed:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md
:x:Error

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBuiltInSiteTemplateSettings.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteGroup.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/index.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOUser.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPODeletedSite.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHideDefaultThemes.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPublicCdnOrigins.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgNewsSite.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserInfo.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOGeoAdministrator.yml
:warning:Warning

Details

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md

Line 0, Column 0: [Error: MAML2Yaml_LoadFileFailed]

Failed to load file: W:/5x12-s/sharepoint/sharepoint-ps/sharepoint-online/Export-SPOQueryLogs.md:2:(0) '> [!NOTE]
> Beginning February 2022, we'll be rem...'
 Expect Heading, please try to use PlatyPS validate the content

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOBuiltInSiteTemplateSettings.yml

Line 7, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOBuiltInSiteTemplateSettings.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoStorageQuota.yml

Line 11, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'set-SPOGeoStorageQuota.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSiteGroup.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOSiteGroup.yml'.
Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOSiteGroup.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOGeoAdministrator.yml

Line 15, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOGeoAdministrator.yml'.

sharepoint/sharepoint-ps/sharepoint-online/index.yml

Line 82, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Get-SPOTenantRenameStatus'.
Line 150, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Set-SPOBuiltInSiteTemplateSettings'.
Line 182, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Start-SPOTenantRename'.
Line 186, Column 5: [Warning: xref-not-found] Cross reference not found: 'SharePointOnlinePowerShell.Stop-SPOTenantRename'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOExternalUser.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOUser.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'New-SPOSiteGroup.yml'.
Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Get-SPOUser.yml'.
Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOUser.yml'.
Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOUser.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPODeletedSite.yml

Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Restore-SPODeletedSite.yml'.
Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPODeletedSite.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHideDefaultThemes.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOHideDefaultThemes.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOPublicCdnOrigins.yml

Line 11, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'New-SPOPublicCdnOrigin.yml'.
Line 13, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOPublicCdnOrigin.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOOrgNewsSite.yml

Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOOrgNewsSite.yml'.
Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOOrgNewsSite.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Export-SPOUserInfo.yml

Line 10, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'New-SPOSiteGroup.yml'.
Line 12, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Get-SPOUser.yml'.
Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Set-SPOUser.yml'.
Line 16, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOUser.yml'.

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOGeoAdministrator.yml

Line 14, Column 9: [Warning: file-not-found - See documentation] Invalid file link: 'Remove-SPOGeoAdministrator.yml'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@traya1 please take next step and resolve this PR. thanks

@traya1

Docs Build status updates of commit 5c8f1ea:
:warning: Validation status: warnings
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


chore: release july 12 2024

External:

Showing "Skip this step" instead of "Nowhere" in create-app
Added exit instructions in create-app
No longer generating .dev.vars in create-app

Internal:

bun install lockfile in CI

:tada: This PR is included in version 1.32.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


modal show not working with v-b-modal or useModalController()

          When trying to show a modal window via useModalController() I get the same error

import {useModalController} from 'bootstrap-vue-next';

const {show} = useModalController();
show?.({
     component: FieldsSettingsModal,
});

Your focus-trap must have at least one container with at least one tabbable node in it at all times
"bootstrap-vue-next": "^0.26.6",
P.S. the same thing happens when using the v-b-modal directive
Originally posted by @acanthis in https://github.com/bootstrap-vue-next/bootstrap-vue-next/issues/2393#issuecomment-2506212092

tepsu from discord:

I think v-b-modal with lazy attribute is broken: https://stackblitz.com/edit/github-ydzoyh-juuuhb?file=package.json that's using 0.26.6, this one is using 0.25.15 (newst version it still worked with): https://stackblitz.com/edit/github-ydzoyh-y16ghw?file=src%2FApp.vue


No directory 'get_baseline_production' in src/

Hi Witold,
I'm following the vignette that walks through running the simulations and it references a directory named get_baseline_production that I don't see in the src directory. Was this directory removed or renamed?
Best regards,
Danny Toomey

I've updated the vignette so that it is consistent with the current pipeline (get_baseline_production is no longer used).


[BUG] Deserializing ManagedServiceIdentity in GetGenericResourcesAsync

Library name and version
Azure.ResourceManager v1.3.2
Describe the bug
Calling the function GetGenericResourcesAsync on Subscription,
the sdk deserializing ManagedServiceIdentity object and throws FormatException
When doing the call "await subscription.GetGenericResourcesAsync()" an exception is throwing with
Message:
System.Text.Json.JsonException : The JSON value could not be converted to Azure.ResourceManager.Models.ManagedServiceIdentity. Path: $ | LineNumber: 0 | BytePositionInLine: 46
Exception type:
System.FormatException
Failed method:
Azure.ResourceManager.Models.ManagedServiceIdentity.DeserializeManagedServiceIdentity
This happen as of now only in Microsoft.DevTestLab/labs generic resource with api-version 2018-10-15-preview
In the api-version 2018-09-15 of Microsoft.DevTestLab/labs the property identity is not returned at all.
Expected behavior
The call "await subscription.GetGenericResourcesAsync()" is not throwing FormatException
Actual behavior
The GetGenericResource method throws System.FormatException: The JSON value could not be converted to Azure.ResourceManager.Models.ManagedServiceIdentity.
Reproduction Steps
Unfortunately we cannot reproduce this behavior with new resources.
Environment
No response

Hi @int292, I'm trying to reproduce this issue and will investigating possible solutions once the reproduction is done. By the way, I will appreciate if you could provide the log of the call await subscription.GetGenericResourcesAsync().
Sample code about how to enable logging:
using Azure.Identity;
using Azure.ResourceManager;
using Azure.Core.Diagnostics;

using AzureEventSourceListener listener = AzureEventSourceListener.CreateConsoleLogger(EventLevel.Verbose);
ArmClientOptions options = new ArmClientOptions()
{
    Diagnostics =
    {
        IsLoggingContentEnabled = true
    }
};
ArmClient armClient = new ArmClient(new DefaultAzureCredential(), options);

Thank you for the reply! The logging is enabled. The body content is on this moment truncated. Sample part in end of response is: {"id":"/subscri
Do you have maybe (more) suggestions for logging?

Found that Resourcetype Microsoft.DevTestLab/labs returns this information as part of the json.
		"type": "Microsoft.DevTestLab/labs",
			"location": "westeurope",
			"identity": {
				"principalId": "",
				"tenantId": "",
				"type": "None"
			},

FYI, we have created this feature request for this kind of issue. Will discuss to finalize the solution.

@Yao725 This is indeed working for the armClient. Thank you for the support on this issue!


[FLINK-35109] Bump to Flink 1.19 and support Flink 1.20

Also

adds the migration support tests up to 1.20.
bumps Kafka-client to 3.6.2
various test cases that become flaky with the bumps

* What is the relation between the supported Flink versions and the connector version?

There is no relation and that was the intent of factoring it out. We currently encode the supported version in the name of the artifact, e.g.,  flink-kafka-connector-3.1.0-1.18. With Flink 2.0 and hopefully binary stable APIs, we would drop the name and just say that it's compatible with all Flink 2 releases (in some kind of version matrix). Hopefully, that works out.

* Do we only support the latest two Flink releases with one connector version (in this case can we remove the 1.18 compatibility)?

There is no strict guideline whatsoever. It's important that we maintain bugfixes for critical bugs for all maintained Flink bugfixes. I have outlined my proposal for the next 3 supported versions on the dev ML.

I forked out FLINK-36441 for the test fixes.


CNN add pad mod

the cnn's forward can support SAME_UPPER and SAME_LOWER now

Is this still a draft?

Is this still a draft?

still working on it, trying to fix the backward, now we need to add a column zeros at the end of the dy.
I am discussing with shicong.


Decompose Node

The Node class has gotten a bit unwieldy. I feel that the way I added storage, especially on top of two backends that are non-optimal (tinybase being incomplete, and h5io -- most of all -- not accommodating rercursive attributes) has resulted in some technical debt.
This became particularly evident in #240 when I tried to merge storage into Joerg's branch. I knew already that Node.iter didn't play well with the graph paradigm, but with storage present simply creating new copies of the same node with
So what I'd like to do is break apart Node into some different pieces to separate out the concerns and break responsibilities into smaller pieces. I had initially tried a purely component-based composition approach (e.g. Node.semantics.label instead of Node.label), but this proliferated trouble with h5io due to all the recursive relationships. So instead I'm opting for mutliple-inheritance mixin-compositions.
My current attack plan is:

[x] Semantics to handle labels, uniqueness, child/parent relationships, etc. (#244)
[x] Runnable (#246)

And later to handle interactions with remote queues

[x] HasIO to (#252)

[x] Use case: "single-value-ness" becomes a special case of HasIO where there is only one output data channel, so we can close #155 and reduce the number of user-facing classes (just Function and Macro, no more SingleValue) at the same time. (#255, #257)

[x] Finally, go back and revisit the existing abstraction of storage (#260)

Ok, I'm quite happy with this. I'm quite certain that there is room for improvement, and it's always possible that one goes too far decomposing things into too small of pieces, but overall this feels better. IMO the proof is in the pudding with how easy it was to now give all nodes "single value" power in #255. Critically, pyiron_workflow.node went from an unwieldy 1302 lines down to 729 -- a 46% reduction. There will be more to do in the future, but I feel this is a reasonable stopping point to go harvest some fruit from the improved infrastructure and get feature implementation done.


Update ember & ember-cli to version 2.8.x

Roll-up PR containing all dep updates and fixes required for Ember 2.8.0 compatibility.
TODO:

[x] blank screens (fixed by EPS beta version)

[x] broken search input styling with EPS beta

[x] Post title input does not allow spaces to be entered (caused by now-reverted ember-one-way-controls)
[x] remove deprecated use of Enumerable.contains
[x] fix private API change for viewRegistry used in active-link-wrapper
[x] fix error when using gh-image-upload-with-preview with no remove action passed in
[x] fix failing setup tests - appears to be an issue with tests continuing before promise chains have fully resolved, haven't been able to replicate the failures outside of testing. Fixed by modifying our ESA session serviceto use ourajax` service for it's network requests instead of dropping down to jQuery

FYI this needs a rebase now 😉


Enhance installation docs for improved user clarity

Users have reported difficulties in following the installation steps due to unclear documentation.
While all necessary information is present, the current format and wording negatively impact readability and comprehension.
Add clear headings, bullet points, and step-by-step instructions to guide users through the installation process more effectively.

/lgtm


[EXE] Ensemble and stacking methods

Learning Goals
[Learning goals, bulleted/numbered list is preferred]
Starting with randomforest, adaboost, etc up to popular LightGBM, XGBoost, expose learners to a variety of bagging/boosting/ensemble/stacking techniques.
This could be a series of 4-5 exercises.

Hey,
I was wondering if I could contribute to this issue. This would be my first OSS contribution. I have previously worked in algorithm development area. and presented a paper on a novel pipeline in IEEE CONECCT 2020. Kindly find attached a python file for the first exercise along with file structure (commented out) and sample code implementation. Let me know if I can contribute in any manner.
https://github.com/anandravishankar12/OSS_1

Hi @anandravishankar12 thanks for the interest and the help ! And yes, please contribute ! Please check out the contributing guide as well as a few of the projects to see what are the structures and format/convention. Otherwise, its all very informal and flexible. Feel free to create a PR once you created the codes and figured out how to do all the git stuff. Its ok to fumble and make mistakes as first contribution, we will help each other during the PR discussion.
Again, thanks !

Have submitted my first PR. Kindly review it and get back to me with the required changes. Thanks you.


Duplicate Paragraphs - Leveraging containers and orchestrators

This entire section on the page is also repeated twice.

https://docs.microsoft.com/en-us/dotnet/architecture/cloud-native/leverage-containers-orchestrators

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

ID: cde870f6-e7e3-f7e7-0044-df7bc7097516
Version Independent ID: fca65eda-a53e-a20b-26df-9bea6d8216c5
Content: Leveraging containers and orchestrators
Content Source: docs/architecture/cloud-native/leverage-containers-orchestrators.md
Product: dotnet-architecture
Technology: cloud-native
GitHub Login: @nishanil
Microsoft Alias: nanil

Thanks, @theterminalguy We have a PR that will fix it. https://github.com/dotnet/docs/pull/18720


Observers Doc refers to missing template

The section Template Rendering refers to sacred/examples/my_runs/template.html which no longer exists.

Yes, that's right. You can create a pull request if you like.
While looking at the code, I realized that there is a bug in the template rendering: If you provide a template file but mako is not installed, the code just runs through but doesn't create a rendered file. It also looks like the rendering code expects a pathlib.Path but the argument is never converted or checked.

I've also just run into this issue. It looks like in addition to the items noted by @thequilo there's also a problem with the mako template object when using pathlib.Path for the template filename. The mako.template.Template attempts a regex substitution on the filename and so expects a str not a pathlib.Path object. This looks fixable with a simple cast to str on the template object creation in the FileStorageObserver?

Hi @jamie-cunningham, yes, I guess that that's a quick fix for this issue. Would you create a PR and a test case for it?


v1.3   Time slot methods

Pull Request Test Coverage Report for Build 496

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.6%) to 82.475%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/model/group/Group.java
0
6
0.0%

Totals

Change from base Build 490:
0.6%

Covered Lines:
2386

Relevant Lines:
2893

💛  - Coveralls


Performance issue in snlds/examples/lorenz_attractor_trainer.py

Hello! Our static bug checker has found a performance issue in snlds/examples/lorenz_attractor_trainer.py:  Python type arguments  learning_rate, temperature and cross_entrophy_coef (here) are passed to tf.function decorated function train_step instead of tensors. As there is a while loop, every time the value changes, a new graph will be generated, and that can trigger tf.function retracing warning.
Here is the tensorflow document to support it.
Looking forward to your reply.

We are investigating this kind of issues, and your answer will be of great help to our work. Can you take a look? Thank you in advance! @jiawen @cghawthorne @jaingaurav @dfurrer


Add ability to abort submitted jobs

If the user interrupts the program with ctrl-c or similar (which creates a KeyboardInterrupt) when a job has been submitted to the server and the client is waiting for results, the submitted job is aborted.

(CI will fail until https://github.com/iqm-finland/iqm-client/pull/89 is merged)


[SPARK-36162][SQL] Support estimation of equal null safe join

What changes were proposed in this pull request?
Support estimation of equal null safe join
Why are the changes needed?
Support estimation of equal null safe join
Does this PR introduce any user-facing change?
User can estimate more accurate estimation result when using equal null safe join
How was this patch tested?
Added UT

Can one of the admins verify this patch?

Dose one of the admins have time to review this?


[WIP] Add "real" read_parquet logic

Updates ReadParquet to use metadata-parsing and IO logic from dask.dataframe.io.parquet.
Requires https://github.com/dask/dask/pull/9637 (only because my environment was using that PR when I put this together).

Looks clean to me.  I'm hitting the "Ready for review" button.  I had one final request, mostly to make sure that we cover the actual task graph code.


Handle statsd paths in different format

What does this PR do?
Add an environment variable to the internal stat field
Adjust the format if it contains unix://
Motivation
Make it easier to set the internal stats field.
Avoid breaking relenv

Yeah, this is a good idea. Thank you!

Thanks. CI was failing due to documentation updates. I think PR is now ready!