GPIO - query on HJSON/regression test

File:   hw/ip/gpio/dv/gpio_sim_cfg.hjson
// Default UVM test and seq class name.
  uvm_test: gpio_base_test
  uvm_test_seq: gpio_base_vseq

However, the base_vseq can not be run as-is and needs to be overriden (looks like) as we get error as below:
UVM_FATAL @    142306 ps: (cip_base_vseq.sv:75) uvm_test_top.env.virtual_sequencer [gpio_base_vseq] Need to override this when you extend from this class!
Why do I run that SEQ still? Well, in that HJSON file, further below we see:
    {
      name: gpio_csr_rw
      run_opts: ["+do_clear_all_interrupts=0"]
    }

So without uvm_test and uvm_test_seq - we will use the default isn't it? I am as of now parsing this hjson myself and hence this query. Not sure how it is handled elsewhere. Am I missing something here for the SEQ specification?
Thanks
Srini

@sriyerg @weicaiyang Please weigh in here.

@svenka3
In GPIO, no test directly uses the default seq - gpio_base_vseq.
since we import this hjson file. we have the basic setting for gpio_csr_rw and other csr seq (csr_hw_reset, csr_bit_bash, etc)
https://github.com/lowRISC/opentitan/blob/1143d7f7d457dfe64ed95d0d177923b2107e6577/hw/ip/gpio/dv/gpio_sim_cfg.hjson#L30
In csr_tests, it sets uvm_test_seq to {name}_common_vseq as it uses a common run_mode
  run_modes: [
    {
      name: csr_tests_mode
      uvm_test_seq: "{name}_common_vseq"
      run_opts: ["+en_scb=0"]
    }
  ]
...
    {
      name: "{name}_csr_rw"
      build_mode: "cover_reg_top"
      run_opts: ["+csr_rw"]
      en_run_modes: ["csr_tests_mode"]
    }

This part adds additional run opts to the test.
    {
      name: gpio_csr_rw
      run_opts: ["+do_clear_all_interrupts=0"]
    }

LMK if it's not clear. Thanks

@svenka3
In GPIO, no test directly uses the default seq - gpio_base_vseq.
since we import this hjson file. we have the basic setting for gpio_csr_rw and other csr seq (csr_hw_reset, csr_bit_bash, etc)
https://github.com/lowRISC/opentitan/blob/1143d7f7d457dfe64ed95d0d177923b2107e6577/hw/ip/gpio/dv/gpio_sim_cfg.hjson#L30
In csr_tests, it sets uvm_test_seq to {name}_common_vseq as it uses a common run_mode

LMK if it's not clear. Thanks

Great explanation on the flow, thanks. It surely helps :-)
Is this documented somewhere please?
And thanks @sriyerg for your explanation as well.
Regards
Srini

@svenka3
In GPIO, no test directly uses the default seq - gpio_base_vseq.
since we import this hjson file. we have the basic setting for gpio_csr_rw and other csr seq (csr_hw_reset, csr_bit_bash, etc)
https://github.com/lowRISC/opentitan/blob/1143d7f7d457dfe64ed95d0d177923b2107e6577/hw/ip/gpio/dv/gpio_sim_cfg.hjson#L30
In csr_tests, it sets uvm_test_seq to {name}_common_vseq as it uses a common run_mode
LMK if it's not clear. Thanks

Great explanation on the flow, thanks. It surely helps :-)
Is this documented somewhere please?
And thanks @sriyerg for your explanation as well.
Regards
Srini

Unfortunately, we are focusing on our DV efforts at this time. The regression tool does severely lack documentation, but we will address it on a lower priority.


How upload video to s3

Hello,I tried multipart request
    var stream = http.ByteStream(DelegatingStream.typed(file.openRead()));
    var length = await file.length();
    var uri = Uri.parse('http://hb.bizmrg.com');
    var req = http.MultipartRequest("PUT", uri);

    final multipartFile = http.MultipartFile('file', stream, length,
      filename: filename
    );

    req.headers['content-type'] = "video/mp4";
    req.files.add(multipartFile);
    req.fields['key'] = 'path/filename.mp4';
    req.fields['acl'] = 'public-read';
    req.fields['x-amz-date'] = date;

But receive
I/flutter ( 4040): <?xml version="1.0" encoding="utf-8"?>
I/flutter ( 4040): <Error>NotImplemented<RequestId>2WWqZhRvP</RequestId><Message>The requested method is not implemented</Message></Error>

This question is meant for Stack Overflow really. Can you close this hear and ask it on there instead?


fixed dfd buffer length

I ran into an issue trying to write a KTX file with more than 1 sample in the data format descriptor. It looks like the buffer length was hardcoded to 44 when it should be based on the number of samples.

Sorry I didn't meant to commit yarn.lock. Let me remove that.

Thank you!

You're very welcome 🙂


Having issue with Gemma model tokenizer

I'm having an issue with Gemma model. I used swift playground. Here is sample code to reproduce below error:
import UIKit
import Tokenizers

func testTokenizer() async throws -> Tokenizer {
    let tokenizer = try await AutoTokenizer.from(pretrained: "google/gemma-2b")
    let inputIds = tokenizer("Today she took a train to the West")
    return tokenizer
}

var greeting = "Hello, playground"

let t = try await testTokenizer()
t

error: Execution was interrupted, reason: .
The process has been left at the point where it was interrupted, use "thread return -x" to return to the state before expression evaluation.
Please advice me. Thank you so much!

@ivyas21 , Google gemma model is gated and you need authentication to access it.
refer these documentations:
https://huggingface.co/docs/hub/en/models-gated
https://huggingface.co/google/gemma-2b/discussions/28
You can do following steps to get this working:

Go to google/gemma-2b page and request access
Go to Hugging face access tokens page in settings. (https://huggingface.co/settings/tokens)
Generate new token if not already created and copy it
Modify your code to pass hfToken to HubApi

import UIKit
import Tokenizers

func testTokenizer() async throws -> Tokenizer {
    let tokenizer = try await AutoTokenizer.from(
        pretrained: "google/gemma-2b",
        hubApi: HubApi(hfToken: MY_ACCESS_TOKEN)
    )
    let inputIds = tokenizer("Today she took a train to the West")
    return tokenizer
}

var greeting = "Hello, playground"

let t = try await testTokenizer()
t


Added Binary Ninja script

Hey, super cool tool! I saw this tweet  and figured I would give it a shot :)
I don't have IDA, but I tried to match the functionality the best I could based off the documentation.
I am also totally new to Rust, so if you could provide some instructions on how to build the Python module so I could test the script, that would be appreciated.

Hi Matthew,
thanks for the pull request.
The Python integration isn't actually working right now (otherwise you could build it with cargo build --features "python")
I'll fix that next week and will give you heads up.

Hey Matthew,
sorry for the delay. cargo build --features "python" should now work.
Can you give it at try and see if your PR works as intended?

Binary ninja now has decompile to c support: https://github.com/Vector35/binaryninja-api/issues/1650


use {.base.} for base methods; baseless methods are deprecated

I started using NiGui.
However, the following warning appears when the compile command is executed.
C:\Users\nnahito\Desktop\NiGui-master\src\nigui.nim(466, 8) Warning: use {.base.} for base methods; baseless methods are deprecated [UseBase]
C:\Users\nnahito\Desktop\NiGui-master\src\nigui.nim(477, 8) Warning: use {.base.} for base methods; baseless methods are deprecated [UseBase]
C:\Users\nnahito\Desktop\NiGui-master\src\nigui.nim(497, 8) Warning: use {.base.} for base methods; baseless methods are deprecated [UseBase]
.....

Is this all right?

My environments:

Windows10 Home
Nim Compiler Version 1.0.0 [Windows: amd64]

The warnings are correct, the code needs to be adjusted, but it still works.
Leaving this open as reminder to fix the warnings.


Match failures in Covid19IndiaOrg source

/home/vmagent/app/lib/error_logger.py:30: UserWarning: [2020-07-30T13:18:55.2348][Covid19IndiaOrgDataSource] No key match found for:
Status
subregion1_code TT
date 2020-04-01
new_confirmed 424
Deceased 9
new_recovered 16
country_code IN
_vec TT
Name: 34, dtype: object
warnings.warn(f"{''.join((f'[{tag}]' for tag in tags))} {msg}")
/home/vmagent/app/lib/error_logger.py:30: UserWarning: [2020-07-30T13:18:55.2434][Covid19IndiaOrgDataSource] No key match found for:
Status
subregion1_code UN
date 2020-04-01
new_confirmed 0
Deceased 0
new_recovered 0
country_code IN
_vec UN
Name: 35, dtype: object
warnings.warn(f"{''.join((f'[{tag}]' for tag in tags))} {msg}")

@themonk911 was this addressed as part of your latest PR?

Yeah, this was addressed, closing.


Run server tests with multiple runtimes

Hello. Like as https://github.com/stripe-samples/accept-a-payment/pull/192,  made it run with multiple runtimes.
Here's the result of the CI run on my fork: https://github.com/hibariya/subscription-use-cases/actions/runs/1140971319

Thanks again @hibariya!


DevService: Start Temporal stack

Basically start a Dev Service stack using someting like that docker compose stack:
https://github.com/temporalio/docker-compose
This will give it a true Quarkus feel.

👍  could be nice !

@ggrebert any help would be appreciated!  Thank you so much for the GRPC fix!

with pleasure.
and thank you for Quakus Insight ❤
For the docker-compose, the default one seems to be too large (pg + elasticsearch + temporal)
What to you think about the MySQL one?

I am OK with whatever one works.  I didn't know if we would have to turn that Docker Compose into a single container on DockerHub to make it work with TestContainers?

We should:

create 2 containers:

temporalio/auto-setup
temporalio/ui

create a default config to use sqlite
add an option to allow the dev to replace the default config
create a proxy for ui (like mailpit)
take a beer !

I absolutely love this idea.


Add hybrid 30km-60km EnVar scenario with latest 60km covariance

Description

Add 30km-60km3dhybridSpecifiedEnsemble run

Update covariance stddev with 0.33 scaling from @byoung-joo

Adjust variational timings for 60km EnVar related to single-precision build

Issue closed
None
Tests completed
Since only modifies timings of full-scale experiments (more iterations than automated test scenario), the one affected test that uses a 60km ensemble B (3denvar_O30kmIE60km_WarmStart ) should still pass.  Therefore, testing is not needed.  I confirmed that the new 3dhybrid scenario finishes the first cycle in the allotted time and that 80 members in 60km EDA of single-mesh 3denvar finishes the first cycle, both with the single-precision bundle build.

I think you can remove the Issue closed section from the PR comment or modify it to Closes: None

Thank you @ibanos90 for the reminder!  @liujake, we could create a chain of issues for the year-end experiments we plan to conduct.  Then @ibanos90 and I can at least populate scenario YAMLs for the ones that are already possible.

@jjguerrette I just made a test with this branch by ./test.csh. But I just see
liuz_3denvar_O30kmIE60km_WarmStart_TEST
liuz_3denvar_OIE120km_WarmStart_TEST
liuz_3dvar_O30kmIE60km_ColdStart_TEST
liuz_3dvar_OIE120km_ColdStart_TEST
liuz_3dvar_OIE120km_WarmStart_TEST
liuz_eda_OIE120km_WarmStart_TEST

but not the hybrid scenario output in scratch. Anything else I need to do to turn on hybrid test?

Hi @liujake.  You can execute the following from the command-line to start the experiment:
./run.csh 30km-60km3dhybridSpecifiedEnsemble

Since I already have this experiment completed (currently running extended forecasts), you may wish to modify finalCyclePoint in scenarios/3dhybrid_O30kmIE60km_SpecifiedEnsemble.yaml or kill the cylc suite after you confirm that it is running correctly.

Tests pass.


Automated cherry pick of #1599: fix max session login issue

Cherry pick of #1599 on release/2.10.0.
#1599: fix max session login issue

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@51e4dbb). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #1601   +/-   ##
================================================
  Coverage                  ?   7.72%
================================================
  Files                     ?     409
  Lines                     ?   62373
  Branches                  ?       0
================================================
  Hits                      ?    4818
  Misses                    ?   57147
  Partials                  ?     408

Flag
Coverage Δ

#aFlag
7.72% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/storagecachedimages.go
0.36% <0%> (ø)

Continue to review full report at Codecov.

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

/lgtm
/approve


[FEATURE] Update wash to use pre-built assets from releases

Once #874 is complete, we should update wash so that when running wash ui it will:

check for local assets and download if none exist
check for updated release and download if newer than local
set specific release with option like wash ui --version <washboard release>

@lachieh I propose we remove the second bullet point from the requirements here and file as a separate nice-to-have

Was just going to ask about that—agreed. Want to split it out into a new issue as a good-first-issue?

No, nevermind, let's add it to #848


Set plot label

UI version
1.0.56
Your idea
The Waveform widget displays plot labels: r, 0, 1, 2, 3, T.  It only displays units (not labels) for current, voltage, and power.
It would be great to be able to have labels for all signals with the ability to manually set the text to whatever you want.

The UI could add a context-menu action when you right-click on the plot y-axis to edit the text.
See forum.

Available in 1.0.59


"Face Corner" color attributes from Blender are not recognized

Godot version
3.5.1.stable, 4.0.rc1
System information
Windows 11, GLES3/Vulkan, NVIDIA GTX 1060
Issue description
In Blender 3.2+, the vertex paint tool works differently in the "Vertex" domain than it does in the "Face Corner" domain. In order to paint individual faces, I have to (afaik) create a color attribute set to use the "Face Corner" domain. However, Godot doesn't recognize this domain, and colors aren't recognized/rendered when exported from Blender and imported into Godot, even with a material applied.
For example, I have a cube model I made in Blender, with a color attribute using the "Face Corner" domain.  Importing this into Godot, either by saving the .blend file - or exporting a (for example) .glb file - to the project directory, I would expect to see the following:

However, this is not the case. Instead, the colors are simply not present, and there doesn't seem to be any way to get them to render.
This is a problem because it means I now have to revert to an older version of Blender just to be able to achieve this sort of effect and have it work in Godot.
As a side note, though I feel like this may need to be reported separately, vertex colors on models from .blend files imported directly are never visible, no matter the domain or data type of the color attribute.
Steps to reproduce
Download the attached MRP and unzip it. You'll find two folders, one with a project for 3.x, and another for 4.x. Open either one and try to create an inherited scene of any of the included .glb files. You'll notice that vertex colors only render for the models in the "vertex" folder (with the exception of the "old" folder, which includes a model made in an older Blender version).
To touch on the side note from earlier, the 4.x version contains the original .blend files, but in trying to create inherited scenes for any of those, you'll notice the vertex colors never show up, no matter the domain. Again, I'm not sure if that needs an issue of its own, or is due to the same problem causing the main issue at hand. I've tried adding a material to them, both in Blender and Godot, but that doesn't do anything.
Minimal reproduction project
Face Corner Color Issue MRP.zip

I think this is actually an issue with Blender's exporter. If you import the GLB file into Blender it looks the same as it does in Godot. In both cases the vertex colors are lost and the cube appears totally white

I think this is actually an issue with Blender's exporter. If you import the FaceCornerColor.glb file into Blender it looks the same as it does in Godot. In both cases the vertex colors are lost and the cube appears totally white

You're right. I should've thought to try that before opening the issue, my bad. In that case, should this be closed? I'm not sure there's anything that can be done on Godot's end to solve this.

@Zorochase

I'm not sure there's anything that can be done on Godot's end to solve this.

Unless there's some weird extra metadata that could be somehow hackishly parsed, no, but even then it wouldn't certainly be appropriate.
If the file's exported wrong, it's Blender's problem.
I've been thinking, though, does gltf even support face corner attributes? I fear that it might be some blenderism not supported by the format itself.

GLTF really just understands arrays of vertex info. So Blender should be baking the face corner attributes into the vertex data. Likely it needs to duplicate vertices per face corner so each can carry their own data. I'm not sure how complex that is as I am not familiar with Blender's face corner paradigm.

Reopening, as this should be documented in Importing 3D scenes.

Don't bother i reported the issue on blender.org and they have fixed it, it is already fixed on the 3.5+ version of blender.


Add St Richard Reynolds Catholic College

https://strichardreynolds.org.uk/sixth-form/welcome-to-the-sixth-form/
https://strichardreynolds.org.uk/wp-content/uploads/Sixth_form_booklet_2024_v5.pdf
.srrcc.org.uk email  domain

@OOP-on-top srrcc.txt I am sorry, I have to close the request without merging, because you made a mistake in a request and did not specify any filepath. Please ensure that you are familiar with this repository rules located at the bottom of this page and make a new correct request. Thank you for your understanding!


DBZ-712. ignore initsync offset during connector start.

Ignore the offset with initsync:true during connector start since that indicates the initial sync is not completed, see https://issues.jboss.org/browse/DBZ-712.

@echo-xu Nice! How it will behave when you complete the initial sync but no event from oplog has been processed yet? Will it restart the snapshot again?

@jpechane the BufferableRecorder will change the offset for the last record in the initial sync, that one will not have initsync:true and indicate the initial sync is complete.

@jpechane, on setting the "initsync" flag, it's as @echo-xu is saying. There'll always be a record buffered, so it can be written out to KC in a delayed fashion, with the right flag set once the snapshot has been completed. That's one of the things we should unify across connectors, as it's quite brittle... (or, ideally, KC allows us to commit that updated offset without sending another record as per that pending discussion in Kafka upstream).

Ok, let me double-check. Way too many if/else in this method for my taste :)

@gunnarmorling do you see any issue on this?

Hey, still on my list to double-check. Was side-tracked with other things
(time zones, agh...), but I should get back to this tomorrow.

Thank you for reviewing this @gunnarmorling !


Add starter files

Adds some starter files.

In a follow on could you also add a CONTRIBUTING.md, as I think we ask for that for repos in the Node.js org.


Use error info during integration testing

Describe the improvement you'd like to request
Our integration testing framework supports providing a "custom implementation" of the Cedar validator and authorizer to allow testing new implementations. If a custom implementation is provided, then we ignore the "errors" field of the integration tests, which records which policies are expected to error during an authorization request.
We'll eventually want to update this to enforce that error behavior is consistent between different implementations of Cedar.
Note: We can’t do this until we update the implementations in cedar-spec to return authorization error info.
Describe alternatives you've considered
No response
Additional context
No response
Is this something that you'd be interested in working on?

[ ] 👋 I may be able to implement this internal improvement
[ ] ⚠ This feature might incur a breaking change

Closing this issue, since it was addressed during the last round of integration test revisions. I believe this particular issue was addressed in #707.


Button color overrides do not seem to work in v8

Hello - upgrading to v8, I'm referring to https://github.com/basscss/addons/tree/master/modules/btn-primary, and setting my class like this:
<button type="submit" class="btn btn-primary bg-red rounded-right x-group-item">Subscribe</button>

... but the color override does not work.
I can set the default button color, using the variables:
  --button-color: var(--white);
  --button-background-color: var(--teal);

What can I look into to see why this might not be working?

It probably has to do with source order. You might want to import btn modules before other color modules.

And boom. That was it. I slavishly copied the order in bassplate and that produced this small glitch, I think. I'll mess with it some more to see what I can see. Thanks!


Hi, very nice work!!! Can u help me this bug?

it's not a bug, I just donlt know how to show it
build ‹master*› » ./hybridRenderer
Vendor:   NVIDIA Corporation
Renderer: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
Version:  4.6.0 NVIDIA 470.103.01

Beginning Scene load, checking scene description file:
Cannot access ../assets/scenes/Sponza.json
Cannot find scene descriptor file for Sponza
Could not load default sponza scene. No models succesfully loaded!
Failed to initialize scene manager.
HRE could not initialize successfully. Shutting down.
Closed input manager.
Closed renderer manager.
Closed scene manager.
Closed display manager.

Any help?
the json file just there...

The assets folder is not in the expected path. You can use my branch where this is fixed


Add test cases for #150

Closes #150

Thank you!

Is it possible to have a new release since the bug exists on the latest release ? :)

Done


How to use this for multi label?

Is is possible to use this in case of multiple labels present in the same document? If yes, please point out how.

yes, that's the main use case. Look at the example data, each document has more than one label assigned to it.

I saw a few .lab files in the data folder. All of there m had 1 label. Can you send me a link to the files that you are mentioning.

Well, there's thousands of files - I'm not going to browse through them looking for examples ;) You can write a script to find files that have more than one line if you need to see one. Or you can trust me that they exist :-)

No, that's not what I meant. Sorry if it sounded otherwise. My question was how to store the labels in the .lab file in case of multiple labels. From your earlier comment, I understood the way out to be placing them in separate lines. That is all that I needed.

That's exactly the case!


Implement compiler back end in Smalltalk to replace compiler implemented in C++

We already have a good Smalltalk parser in the image that is used for syntax and semantic analysis in the IDE, but are still reliant on a compiler written in C to compile methods into the system. It is really about time we implemented a compiler backend in Smalltalk that can generate Smalltalk bytecodes and methods from the ASTs created by the SmalltalkParser.

Pharo recently replaced their compiler.  Its MIT licensed so maybe it could be re-purposed for Dolphin.  Background reading... https://hal.inria.fr/hal-00862411/document


Scanner identity in pull log is not described in "Identify vulnerabilities in Azure Container Registry with Microsoft Defender for Cloud" document

The article/document FAQ states:

How does Defender for Containers scan an image?
Defender for Containers pulls the image from the registry and runs it in an isolated sandbox with the Qualys scanner. [...]

So it means, that the scanner does pull images from the registry. It does not specify, how we can distinguish such pulls in the registry activity log, from all the other image pulls. This may be important in log analysis, both when analysing the scanner behavior and/or impact, as well when those pulls caused by the scanner, are irrelevant in the analysis and should be removed from that analysis.

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

ID: 29434ef1-ac47-9226-c97a-b3ebd76438b1
Version Independent ID: d7ca7e00-09b4-819d-2e8b-f7699024a0e4
Content: Identify vulnerabilities in Azure Container Registry with Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/defender-for-containers-vulnerability-assessment-azure.md
Service: defender-for-cloud
GitHub Login: @bmansheim
Microsoft Alias: benmansheim

@hilari0n
Thanks for your feedback! We will investigate and update as appropriate.

#reassign:dcurwin

Thank you for your comment. We'll investigate and get back to you.

@hilari0n - Thanks for your question. We've updated the document with the answer here:
https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-containers-vulnerability-assessment-azure#how-can-i-identify-pull-events-performed-by-the-scanner

#please-close

Uhm... So the solution given is:

Search for pull events with the UserAgent of AzureContainerImageScanner.
Extract the identity associated with this event.
Use the extracted identity to identify pull events from the scanner.

Why can't you just specify the identity which will be there? It would suggest, that more than one identity can be used. In that case if I have multiple identities with that UserAgent, which one should I use in step 3? How can I be sure, I have found all the identities, which are and/or will be used by the scanner? When and why can it change?
What if someone else also used this same UserAgent for different purposes (e.g. to hide malicious activity)?

@hilari0n - I will look into your questions.

@hilari0n - This is the response I received from the product group:
There should only be one identity, but the identity is different per tenant, hence the reason we can't provide a specific identity.
If the customer is concerned about an internal user hiding their activity through this method, they should instead use Azure Active Directory (AAD) and search for an app with this identity: 918d0db8-4a38-4938-93c1-9313bdfe0272, and extract the object ID for the app, which is the ID that they are going to see in ACR activity log. I didn't want to include it as the first option, because not everyone have access to their AAD, and as a result may not be able to follow this method.

We haven't heard back from you, so we will now close this issue. If this remains an issue, please reply and we will gladly continue the discussion.

#please-close


Fix commit log and diffstat when creating MR

When the user creates an MR he's prompted with some basic information about what's going to be the MR content:

commit list
number of commits
commit diff statistics

All these information were being created using a "union" approach of git: when the information being considered is the union of two different sets (branches) instead of the difference from one set to another (i.e. what's different from branch <source> to <target>).
The consequence of the union approach appears when the user wants to create an MR using a source branch that is behind of the target branch wrt commits: if the target is 4 commits ahead of the source branch, and the user doesn't rebase before opening the MR, the commits information (all three of them) will present the source branch's commits + 4 from target branch, which is, obviously wrong when compared to what the UI presents during MR creation.
All the information and related commands was took from Git's manpage.

Something strange is going on with the testing.
Will investigate.


Hint text semantics to be excluded in a11y read out if label text is not provided

Currently, hint text can either be used to (1) provide hint text for users, or (2) as a label for the text field.
E.g. to enter phone number, hint text can be either (1) 0000 - 0000 or (2) Phone number.
For a11y users, the hint text is always read regardless of use case (1) or (2) and this is problematic for use case (1).
E.g. when the text field is filled with 1234 - 5678, it reads both the text and hint text "1234 - 5678, 0000 - 0000"
Can we tweak the current feature to exclude the hint from a11y if the textfield is not empty AND a dedicated label text is given?

Internal bug for this is b/255727805
/cc @justinmc @chunhtai

Can we tweak the current feature to exclude the hint from a11y if the textfield is not empty AND a dedicated label text is given?

This sounds reasonable to me as long as the hint is included if there is no explicit label given because some app designs use the hint as a label in that case and we don't want to loose that information there.

This sounds reasonable we should exclude the hintext if there is text in the textfield.

This sounds reasonable we should exclude the hintext if there is text in the textfield.
Only if there is a separate label text, though. Otherwise, the hint is likely the label.

Should be a one line fix
https://github.com/flutter/flutter/blob/78dbe6661b3557c2355cad401287d0bce3479c06/packages/flutter/lib/src/material/input_decorator.dart#L2148
@hangyujin can you take a look at this?


Meeting project board

Create a GitHub project board to show meetings.

Board has now been created! All previous meetings have been added with a brief summary and references to mentioned issues.
The board will continually be updated, but its creation is now complete.


Duplicate put requests to registry trigger errors

Environment:

Jib version: Jib core 0.27.0
Build tool: maven 3.9.1
OS:  Ubuntu 22.04.4 LTS (in a container)

Description of the issue:
During our ci pipeline, we have an error occuring randomly. Jib triggers the same patch request which generates an error.
We know that the first patch takes a bit long to (1m12s) successfully process, but in the mean time Jib sends a second patch requests. This second request is the one that generates an error.
Expected behavior:
Should ends up fine.
Steps to reproduce:
Unable to reproduce surely the error.
Log output:
Mon, 01 Jul 2024 09:05:44 GMT Caused by: com.google.cloud.tools.jib.http.ResponseException: 404 Not Found
Mon, 01 Jul 2024 09:05:44 GMT PATCH https://.................../blobs/uploads/f7b334b6-be1f-4bfc-bd12-ca739c994a9b?_state=Z4RE2P18shUE5tW_Pk_XmXKYTOAtUlOoUA_G5isOd3l7Ik5hbWUiOiJwcm92b2x5L2RhdGEtdmlydCIsIlVVSUQiOiJmN2IzMzRiNi1iZTFmLTRiZmMtYmQxMi1jYTczOWM5OTRhOWIiLCJPZmZzZXQiOjAsIlN0YXJ0ZWRBdCI6IjIwMjQtMDctMDFUMDk6MDQ6MTUuMTQ1NTc4NzcxWiJ9
Mon, 01 Jul 2024 09:05:44 GMT {"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"blob upload invalid"}]}
Mon, 01 Jul 2024 09:05:44 GMT
Mon, 01 Jul 2024 09:05:44 GMT at com.google.cloud.tools.jib.http.FailoverHttpClient.call(FailoverHttpClient.java:355)
Mon, 01 Jul 2024 09:05:44 GMT at com.google.cloud.tools.jib.http.FailoverHttpClient.call(FailoverHttpClient.java:266)
Mon, 01 Jul 2024 09:05:44 GMT at com.google.cloud.tools.jib.registry.RegistryEndpointCaller.call(RegistryEndpointCaller.java:138)
Mon, 01 Jul 2024 09:05:44 GMT ... 48 more
Mon, 01 Jul 2024 09:05:44 GMT Caused by: com.google.api.client.http.HttpResponseException: 404 Not Found
Mon, 01 Jul 2024 09:05:44 GMT PATCH https://........................./blobs/uploads/f7b334b6-be1f-4bfc-bd12-ca739c994a9b?_state=Z4RE2P18shUE5tW_Pk_XmXKYTOAtUlOoUA_G5isOd3l7Ik5hbWUiOiJwcm92b2x5L2RhdGEtdmlydCIsIlVVSUQiOiJmN2IzMzRiNi1iZTFmLTRiZmMtYmQxMi1jYTczOWM5OTRhOWIiLCJPZmZzZXQiOjAsIlN0YXJ0ZWRBdCI6IjIwMjQtMDctMDFUMDk6MDQ6MTUuMTQ1NTc4NzcxWiJ9
Mon, 01 Jul 2024 09:05:44 GMT {"errors":[{"code":"BLOB_UPLOAD_INVALID","message":"blob upload invalid"}]}
Mon, 01 Jul 2024 09:05:44 GMT
Mon, 01 Jul 2024 09:05:44 GMT at com.google.api.client.http.HttpResponseException$Builder.build(HttpResponseException.java:293)
Mon, 01 Jul 2024 09:05:44 GMT at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1118)
Mon, 01 Jul 2024 09:05:44 GMT at com.google.cloud.tools.jib.http.FailoverHttpClient.call(FailoverHttpClient.java:349)
Mon, 01 Jul 2024 09:05:44 GMT ... 50 more

Additional Information:  The registry is a privately managed harbor

I don't think they are duplicate PATCH requests. It's just that Jib does concurrent blob uploads. I think for whatever reason, the harbor registry sometimes fails to handle concurrent uploads correctly. I guess retrying Jib in a loop or even disabling concurrency in Jib (slow, of course, particularly for initial uploads) would be a workaround.

I don't think they are duplicate PATCH requests. It's just that Jib does concurrent blob uploads. I think for whatever reason, the harbor registry sometimes fails to handle concurrent uploads correctly. I guess retrying Jib in a loop or even disabling concurrency in Jib (slow, of course, particularly for initial uploads) would be a workaround.

Hi @chanseokoh ... I think this looks like the problem we have too. I could not find howto "disable concurrency" in Jib.

@ddittmar set the system property jib.serialize, like -Djib.serialize=false on the command line. See this example. Note it's a system property only; no Maven or Gradle configuration for this Jib system property.

@ddittmar / @jtama does disabling concurrency solve this issue for you?

@ldetmer no ... the answer was a configuration of our Harbor registry ... our Harbor use an S3 compatible backend and we basically had to tell Harbor that it should wait until all the S3 nodes have written the data. Sorry I don't have more information because I don't configure our harbor. That's what I've heard from our administrators.

I can't say for sure, but we also have an managed harbor with S3 backend storage, so it could be that this is the exact same issue. Let me check please (If have enough rights)

So the answer is no, it did not, but as I said just before, it could be that the fault is not on jib side...


Opening a new ticker websocket kills the old one

It's likely quite normal to open multiple websockets for the ticker (and also the executions). i.e. I'm trying to run multiple bots, each of which will need its own ticker websocket. But when one connects, all other connections are closed, it seems.

Refactored websocket code, which seems to have fixed this issue.

I'm afraid this is still happening, although after a delay, i.e. 2 or more can run for a short time.
Also, I'm not sure the 2 clients are actually receiving the same data.

The clients should receive the same quotes now. The ticker chatter was probably due to the market makers constantly canceling tons of orders; they wait a bit now, which seems to have helped.
I'll see whats up with the sockets dropping. Maybe the sockets are timing out after 5 minutes, I'll try to keep them alive.

One thing: if possible, the ticker shouldn't care about account name at all. Although it's in the URL, official Stockfighter just ignores it, as far as I can tell.


RBAC broken in 7.2 if using ClusterRole

In the following file: https://github.com/appscode/voyager/blob/release-7.2/hack/deploy/rbac-list.yaml
There are 2 role definitions at the beginning:
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: voyager-operator
  namespace: ${VOYAGER_NAMESPACE}
  labels:
    app: voyager

and
apiVersion: rbac.authorization.k8s.io/v1
kind: ${VOYAGER_ROLE_TYPE}
metadata:
  name: voyager-operator
  namespace: ${VOYAGER_NAMESPACE}
  labels:
    app: voyager

If you use --restrict-to-namespace=false, for example, I'm only deploying it in kube-system, then the above mentioned parts will overwrite each other, because of this: https://github.com/appscode/voyager/blob/release-7.2/hack/deploy/voyager.sh#L99
Eventually it will render two ClusterRole objects, both at the same name of voyager-operator. So first it will apply one definition, then later overwrite it with the second one, therefore cancelling the definitions of the first file completely.
Because of this, all of the following permissions are missing:
- apiGroups:
  - apiextensions.k8s.io
  resources:
  - customresourcedefinitions
  verbs:
  - "*"
- apiGroups:
  - voyager.appscode.com
  resources: ["*"]
  verbs: ["list"]
- apiGroups: [""]
  resources:
  - nodes
  verbs: ["list", "watch", "get"]
- apiGroups: [""]
  resources:
  - namespaces
  verbs: ["get", "list", "watch"]

This causes Voyager to throw tons of API errors, because it cannot query nodes, namespaces, etc.

I used the kubectl auth reconcile command, which is supposed merge the 2 roles , not overwrite. https://github.com/appscode/voyager/blob/release-7.2/hack/deploy/voyager.sh#L400 .  This is what I see on a fresh minikube cluster.
$ kubectl version --short
Client Version: v1.10.2
Server Version: v1.10.0

$ curl -fsSL https://raw.githubusercontent.com/appscode/voyager/7.2.0/hack/deploy/voyager.sh \
                                  | bash -s -- --provider=minikube
checking kubeconfig context
minikube

checking whether extended apiserver feature is enabled

VOYAGER_CLOUD_CONFIG=
VOYAGER_CLOUD_PROVIDER=minikube
VOYAGER_DOCKER_REGISTRY=appscode
VOYAGER_ENABLE_ANALYTICS=true
VOYAGER_ENABLE_RBAC=true
VOYAGER_ENABLE_VALIDATING_WEBHOOK=true
VOYAGER_HAPROXY_IMAGE_TAG=1.8.9-7.2.0-alpine
VOYAGER_IMAGE_PULL_POLICY=IfNotPresent
VOYAGER_IMAGE_PULL_SECRET=
VOYAGER_IMAGE_TAG=7.2.0
VOYAGER_INGRESS_CLASS=
VOYAGER_NAMESPACE=kube-system
VOYAGER_PURGE=0
VOYAGER_RESTRICT_TO_NAMESPACE=false
VOYAGER_ROLE_TYPE=ClusterRole
VOYAGER_RUN_ON_MASTER=0
VOYAGER_SERVICE_ACCOUNT=voyager-operator
VOYAGER_TEMPLATE_CONFIGMAP=
VOYAGER_UNINSTALL=0

Wrote ca certificates in  /home/tamal/go/src/github.com/kubedb/postgres
Wrote server certificates in  /home/tamal/go/src/github.com/kubedb/postgres
deployment.apps "voyager-operator" created
secret "voyager-apiserver-cert" created
service "voyager-operator" created
serviceaccount "voyager-operator" created
clusterrole.rbac.authorization.k8s.io "voyager-operator" reconciled
clusterrole.rbac.authorization.k8s.io "voyager-operator" reconciled
clusterrolebinding.rbac.authorization.k8s.io "voyager-operator" reconciled
clusterrolebinding.rbac.authorization.k8s.io "voyager-operator" reconciled
rolebinding.rbac.authorization.k8s.io "voyager-apiserver-extension-server-authentication-reader" reconciled
clusterrolebinding.rbac.authorization.k8s.io "voyager-apiserver-auth-delegator" reconciled
clusterrole.rbac.authorization.k8s.io "appscode:voyager:edit" reconciled
clusterrole.rbac.authorization.k8s.io "appscode:voyager:view" reconciled
apiservice.apiregistration.k8s.io "v1beta1.admission.voyager.appscode.com" created
validatingwebhookconfiguration.admissionregistration.k8s.io "admission.voyager.appscode.com" created

waiting until voyager operator deployment is ready
waiting until voyager apiservice is available
waiting until voyager crds are ready

Successfully installed Voyager in kube-system namespace!

$ kubectl get clusterrole | grep voyager
appscode:voyager:edit                                                  43s
appscode:voyager:view                                                  42s
voyager-operator                                                       43s

$ kubectl get clusterrole voyager-operator -o yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  creationTimestamp: 2018-06-26T19:14:01Z
  labels:
    app: voyager
  name: voyager-operator
  resourceVersion: "537"
  selfLink: /apis/rbac.authorization.k8s.io/v1/clusterroles/voyager-operator
  uid: 157d77be-7975-11e8-8eea-080027deeada
rules:
- apiGroups:
  - apiextensions.k8s.io
  resources:
  - customresourcedefinitions
  verbs:
  - '*'
- apiGroups:
  - voyager.appscode.com
  resources:
  - '*'
  verbs:
  - list
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - list
  - watch
  - get
- apiGroups:
  - ""
  resources:
  - namespaces
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - voyager.appscode.com
  resources:
  - '*'
  verbs:
  - '*'
- apiGroups:
  - monitoring.coreos.com
  resources:
  - servicemonitors
  verbs:
  - '*'
- apiGroups:
  - apps
  resources:
  - deployments
  verbs:
  - '*'
- apiGroups:
  - extensions
  resources:
  - deployments
  verbs:
  - '*'
- apiGroups:
  - extensions
  resources:
  - daemonsets
  verbs:
  - '*'
- apiGroups:
  - extensions
  resources:
  - ingresses
  verbs:
  - '*'
- apiGroups:
  - ""
  resources:
  - replicationcontrollers
  verbs:
  - '*'
- apiGroups:
  - ""
  resources:
  - services
  verbs:
  - '*'
- apiGroups:
  - ""
  resources:
  - endpoints
  verbs:
  - '*'
- apiGroups:
  - ""
  resources:
  - configmaps
  verbs:
  - '*'
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - list
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - watch
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - create
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - update
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - patch
- apiGroups:
  - ""
  resources:
  - events
  verbs:
  - create
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - list
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - watch
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - delete
- apiGroups:
  - ""
  resources:
  - pods
  verbs:
  - deletecollection
- apiGroups:
  - ""
  resources:
  - serviceaccounts
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - serviceaccounts
  verbs:
  - create
- apiGroups:
  - ""
  resources:
  - serviceaccounts
  verbs:
  - delete
- apiGroups:
  - ""
  resources:
  - serviceaccounts
  verbs:
  - patch
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - rolebindings
  verbs:
  - get
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - rolebindings
  verbs:
  - create
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - rolebindings
  verbs:
  - delete
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - rolebindings
  verbs:
  - patch
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - roles
  verbs:
  - get
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - roles
  verbs:
  - create
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - roles
  verbs:
  - delete
- apiGroups:
  - rbac.authorization.k8s.io
  resources:
  - roles
  verbs:
  - patch

My bad! Yes indeed, I installed Voyager back in the early 5.0 times with some custom flags, so I couldn't use the shell script installer.
Now in order to upgrade to 7.2 and see the actual differences being done, I did the upgrade manually from the YAML files used in the automated script. I simply ran kubectl apply on the files, instead of reconcile. (Actually, didn't even know this exists! Thanks for pointing it out.)
I apologize for the false alarm.

Thanks for using Voyager !


Feature Request - Handle MongooseModel.method().cursor() streams

The .cursor() method on mongoose model methods returns a readable stream, not a promise. Given how stream-oriented node js, and how you can easilly .pipe your mongoose queries to your server response like so:
const Model = mongoose.model('model', mySchema);

// ...
Model.find().limit(10).cursor().pipe(res);

It would be nice to have a stub method that returned a readable stream like so
MyMock = sinon.stub(Model)
MyMock.expects('find')
      .chain('limit').withArgs(10)
      .chain('cursor')
      .streams([1,2,3])

For now, the only way I can do this is to create a custom readable stream that the mock returns like so.
const Readable = require('stream').readable,
      rs = new Readable({objectMode: true}),
      array = [1,2,3];
array.forEach(x => rs.push(x));
rs.push(null);

MyMock.expects('find')
      .chain('limit').withArgs(10)
      .chain('cursor')
      .returns(rs);

Hi @paynoattn, will take a look this week.
A PR for this would be great! 😃

Any news on this one?

Any news on this one?


Return Caitlyn's old default skin

How to return Caitlyn's old default skin?

Caitlyn's default skin has been changed by riot and the old model has been deleted from the game. This cheat cannot load a model that is not from the game.
Caitlyn Default Model: CaitlynBase

@Spanden I can actually revert since I do a lot of old champion restorations, however i'm kind of lazy, i'll probably do it next month or later with Old Ashe.

also need return old Miss Fortune Waterloo skin

also need return old Miss Fortune Waterloo skin
You can checkout killerskins. They have Old Miss Fortune mod there.


Adds flopoco to the floating point tests

Plays around with some gen framework stuff

Did this end up not working?


react(feat): implemented Navigation component

@justintemps , please review and comment. Thx

@wc-lei this looks great! I just added one line to make the Navigation SB story appear in full width. As soon as tests pass 🤞 I'll merge.


Exported Vars: Cannot clear item from array when hint is Array[Node]

Tested versions
v4.3.stable.official [77dcf97d8]
System information
Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+)
Issue description
When exporting a variable with the hint Array[Node] and adding an item to it, then on that item clicking the 3 dots then clicking Clear, this will show the following error:
 Attempted to set a variable of type 'NodePath' into a TypedArray of type 'Object'.
  core/variant/array.cpp:429 - Condition "!_p->typed.validate(value, "set")" is true.

Steps to reproduce

Create a new project (v4.3.stable is the only one I tested)
Add a node
Add a script
Write @export var test : Array[Node]
In the inspector, add an item to the array (select any node)
Now clear that item only using 3 Dots > Clear
The error above should display in Output

Minimal reproduction project (MRP)
N/A

CC @ajreckof


Format on save is not working on 4.2.1

If "Format on save" is enabled in the preferences, the code is not formatted on save and the following message "Format on save failed: due to engine bug. Please report an issue." is displayed in the output window.
Tested on Godot  4.2.1 standard version.
Note that the "Format on Save" plugin work well (no issue), and it can be used in replacement of the same feature of this plugin.

Are your using external editor?

VScode is configured as an external editor but I'm using the godot script editor in that case

Already do some change for this.
It will format anyway when saving a script. But it may not reload the code editor.
I am not sure that how to reproduce your issue, so please test and tell me the result.

The issue has gone with the latest version on this repo.
But still exists with the version on the AssetLib.
Thanks for your work


Create a wordlist for dirsearch users

Source?

It was crafted with bo0om.txt, dirsearch default wordlist and raft-medium-directories.txt (+ raft-medium-directories.txt with .%EXT% at the end)

Thank you!


Add command option to set package version

I needed to set a custom version for my deb packages but nothing seemed to go right.
The ---version-suffix command option sets the $(VersionSuffix) property in the project, however this property is not used anywhere, as opposed to $(Version) or $(PackageVersion).
I was only able to set custom version for my deb packages by invoking the package tools manually and setting /p:Version={version} property.
This pull request changes the command option from ---version-suffix to a simple -v | --version that sets the $(Version) property, the one actually used by Packaging.Targets.

@mikaelmello Thanks, looks reasonable to me. Do you think you could add a unit/integration test for this, to make sure we don't regress in the future?

@qmfrederik, I'm sorry but I don't know how to approach it.
I mean, should I just call dotnet deb/rpm/etc and use the same approach as ReadDebPackageTest?

@mikaelmello The CI scripts call dotnet rpm/dotnet deb/ dotnet zip & friends for you. What you could do is to add a new line which does dotnet rpm/deb/zip -v 9.99 and then makes sure that a .rpm/.deb/.zip file with 9.99 in the file name exists.
See https://github.com/qmfrederik/dotnet-packaging/blob/master/.travis.yml#L42 for the CI script.

I'll probably never get back to it :)
Sorry about that!

I'll probably never get back to it :)
Sorry about that!


The time-thermal map shows the problem

When I create a time heat map
The beginning of each month should be the first of the month
But this is the last day of last month
for example:

@mklzl can you give more info on how to repro this? I tested with master and it works as expected.

@mklzl can you give more info on how to repro this? I tested with master and it works as expected.

  Thank you for your reply !  We used docker to deploy the superset，and the version of Python is  2.7.5.
   when i create a heat map in my dashboard, and use a field of type timestamp as the time field.

Then i choose the Last year as the Time range , and  choose the month as the region the day as subregion, and count the number of  fields as queries . After i run this query , I saw the problem I was asking.
Does this have anything to do with superset`s version?

@mklzl do you know which version of Superset you're running? We dropped support for Python 2, so I'm assuming it's an earlier version. This seems to be working now, and we just released 0.35.

@mklzl do you know which version of Superset you're running? We dropped support for Python 2, so I'm assuming it's an earlier version. This seems to be working now, and we just released 0.35.
The version of Superset we're running is Superset 0.999.0dev ,and the version of Python we're running is Python 3.6.9 ,not Python 2.7.5

@mklzl do you know which version of Superset you're running? We dropped support for Python 2, so I'm assuming it's an earlier version. This seems to be working now, and we just released 0.35.

you can have a  look at this issue https://github.com/apache-superset/superset-ui-plugins/issues/52 . His problem was seem as mine, and someone offered a solution.


Command setting isn't in the UI anymore

The "Command" setting doesn't appear on the package's settings page as illustrated in the readme.

Status on this?

The "Command" GUI setting is back. 😃


Git: Fall back to Git CLI if the shallow fetch is failing using JGit

JGit handles unshallow server responses incorrectly 1. Add a fallback to the Git CLI if an unshallow fetch fails with JGit.

While this is not really desired with regard to https://github.com/oss-review-toolkit/ort/issues/3281, JGit causes unrecoverable issues when this bug is triggered.
Therefore, it would be great if we could add this fallback, as ORT is currently using the Git CLI along with JGit anyway.

Related commit which introduced the issue: d899156a73fb8cbe82f856c6b01e12f599487f57


Fix G keys mapping for Corsair K95 Platinum keyboard

Small fix in the json for K95 Platinum, some "G keys" at the left were no lighting up at all.

Thanks for the contribution!


[Fern's Documentation] Moving list of TODOs from Spring generator docs to an issue

The below is currently in the Fern docs page at https://docs.buildwithfern.com/server-boilerplate/server-boilerplate/spring and should be tracked as an issue instead.
I am submitting a PR to remove the text from the public facing page.
Demo Video
TODO
Spring Configurations
TODO https://github.com/fern-api/fern-java#spring-configuration
Relevant Screenshots

closing as these TODOs aren't populated. can move to Linear if needed!


Distribute Psst through Flathub

It would be great to have Psst build as Flatpak and distributed through Flathub (the most popular Flatpak store).
Flatpaks, and in particular Flathub as a package "store" are becoming more popular and adopted in many Linux distributions. Some distributions, like Fedora Silverblue, even use an immutable system, which means the recommended way of installing packages is via Flathub to avoid layering unnecessary packages on the system.

Ah, the thing I wrote yesterday didn't save, but I had a further look into this. It is still very much in the process of getting put into the flatpack store, and there are issues. It's not really being worked on anymore. When I have more time, I'll look into if I can help further.
Here are the relevant issues and PRs: #141 https://github.com/flathub/flathub/pull/4151
If you have a look there and you have ideas on how you could help, please feel free to add a message.


Roborock E4 support

Device model
roborock.vacuum.a01
Device name
Roborock E4
Does the device require a MiCloud connection?
Do not know
Anything special about the device?
Does it already work with the plugin with a limited scope (can be controlled using the auto created switch)?
no, it is not added with the plugin.

Will add support in the next update!

Support is now added in version 1.1.1


Enable backwards compatibility in the UI for different Pool versions

Artifacts, SDK, and appconfig packages are upgraded to the latest versions as usual.

UI should install aliased versions of sdk and appconfig packages for each version we need to support.

Add a useAppConfigs hook that returns an object keyed by chainid that maps to a list of appconfigs.

Add a version picker to the UI @jackburrus

Refactor existing useAppConfig to return the active appconfig

Refactor useReadHyperdrive and useReadWriteHyperdrive to grab the correct instance version from the sdk

Use best judgment and only split at the components where needed. If two hyperdrive versions have the same interface for a method, don't narrow or split the component. (Keep version specific components as few as possible!)

Diagram: https://app.excalidraw.com/s/6Cpa5unvDjf/9PJV8IEZN26

Related #1189


Telegram notification not working

I am not getting telegram notifications,actually i have reinstalled camera.ui as i had a problem with my mac and for that reason i had to restore my mac therefore everything was lost.
But now when i am entering everything ok , I don't for what reason it's not working for me.

closing in favor of #445 #458


Use mimalloc in attempt to reduce mem alloc perf. oddities

Problem
it's getting known that jemalloc is experiencing perf degradation under some certain work load.
Summary of Changes
Use mimalloc, in the hope of fixing it.
I'm intending to land this pr rather prematurely and see how our canaries like or not. Will revert without hesitation if it turned out that things aren't working well.
At least, this pr fixes https://github.com/solana-labs/solana/issues/27275 without this hack: https://github.com/anza-xyz/agave/pull/1364. However, I'm not sure mimalloc could fix all other known mem alloc issue around banking.
todo

[x] Remove jemalloc deps

Fixes https://github.com/solana-labs/solana/issues/27275

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.1%. Comparing base (206a87a) to head (a6644c4).
Report is 27 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1250   +/-   ##
=======================================
  Coverage    82.1%    82.1%
=======================================
  Files         886      886
  Lines      236435   236439    +4
=======================================
+ Hits       194221   194240   +19
+ Misses      42214    42199   -15

@Lichtso I seems you tried mimalloc before, right? did you find any potential blocker? as far as i can tell, it's better than jemalloc.

@alessandrod Note that I'm not opposed to reducing allocs. Obviously, it's better for perf.
I'm just getting tired of jemalloc. While it's well faster than the glibc allocator with less fragmentation, it has its own peculiar perf profile. So, I'm considering replacing it as a separate effort with bp-ing this to v1.17 & v1.18 in mind, parallel to the on-going alloc reduction efforts. I think you're opinionated around mem allocators in general. Is there any concern for using mimalloc? If any, I'd like to address with any additional investigation.
As for reliability (read: no leak & no fragmentation), I'm now running a devbox against mb, needs another day or two, before conclusion.
As a starter, I confirmed this fixes https://github.com/solana-labs/solana/issues/27275:
before:
# --block-verification-method=blockstore-processor
ledger processed in 31 seconds, 473 ms
ledger processed in 31 seconds, 164 ms
ledger processed in 31 seconds, 335 ms

# --block-verification-method=unified-scheduler
ledger processed in 16 seconds, 363 ms
ledger processed in 16 seconds, 601 ms
ledger processed in 16 seconds, 512 ms

after:
# --block-verification-method=blockstore-processor
ledger processed in 24 seconds, 665 ms
ledger processed in 24 seconds, 848 ms
ledger processed in 24 seconds, 623 ms

# --block-verification-method=unified-scheduler
ledger processed in 12 seconds, 165 ms
ledger processed in 12 seconds, 78 ms
ledger processed in 12 seconds, 117 ms

blockstore-processor is ~27% faster and unified scheduler is ~36% faster according to https://github.com/solana-labs/solana/pull/35286#user-content-steps. I think this alone is quite good perf gain by its own. :)
Also, I haven't confirmed but I'm moderately certain that this fixes the replay stall issue under system overload like rpmalloc fixed the stall (note that rpmalloc is out-of-question due to https://github.com/anza-xyz/agave/pull/1250#issuecomment-2103657904)

Yes I tried mimalloc a few months ago and no, nothing problematic stood out to me at the time.

@alessandrod Firstly, note that I'm not opposed to reducing allocs. Obviously, it's better for perf.
I'm just getting tired of jemalloc. While it's well faster than the glibc allocator with less fragmentation, it has its own peculiar perf profile. So, I'm considering replacing it as a separate effort with bp-ing this to v1.17 & v1.18 in mind, parallel to the on-going alloc reduction efforts. I think you're opinionated around mem allocators in general. Is there any concern for using mimalloc? If any, I'd like to address with any additional investigation.

Uh? Having spent a significant chunk of my time looking at profiles and reading the jemalloc source code my opinion is that it 😂 I'm more than open to replacing jemalloc, I just don't think that we should do it lightly. Changing allocator impacts every subsystem in the validator, personally I think it's a pretty scary change.

As for reliability (read: no leak & no unbounded fragmentation), I'm now running a devbox against mb, needs another day or two, before conclusion.

Hum imo you can't draw conclusions after running a devbox for a couple of days. Jemalloc sucks, and it's really struggling with the amount and pattern of allocations we do, especially since we do them from so many threads. But at least it isn't crashing 😅 Imagine we switch allocator, and then we find that in some configurations after a while it goes OOM - I don't think it's something we can establish in a couple of days based on a single machine configuration, with a single workload, etc. IMO it requires a lot of testing, especially on nodes with a lot of stake, which are the ones struggling the most with memory.

As a starter, I confirmed this fixes solana-labs#27275:
before:
# --block-verification-method=blockstore-processor
ledger processed in 31 seconds, 473 ms
ledger processed in 31 seconds, 164 ms
ledger processed in 31 seconds, 335 ms

# --block-verification-method=unified-scheduler
ledger processed in 16 seconds, 363 ms
ledger processed in 16 seconds, 601 ms
ledger processed in 16 seconds, 512 ms

after:
# --block-verification-method=blockstore-processor
ledger processed in 24 seconds, 665 ms
ledger processed in 24 seconds, 848 ms
ledger processed in 24 seconds, 623 ms

# --block-verification-method=unified-scheduler
ledger processed in 12 seconds, 165 ms
ledger processed in 12 seconds, 78 ms
ledger processed in 12 seconds, 117 ms

blockstore-processor is ~27% faster and unified scheduler is ~36% faster according to solana-labs#35286 (comment). I think this alone is quite good perf gain by its own. :)

This is amazing!

Also, I haven't confirmed yet but I'm moderately certain that this fixes the replay stall issue under system overload like rpmalloc fixed the stall (note that rpmalloc is out-of-question due to #1250 (comment))

There are at least two stalls that I'm aware of, here I'm assuming you're talking about the one caused by jemalloc's time based decay. Mimalloc almost certainly gets rid of that one, but how? How does it compact/release memory? When? And from what threads? Because getting rid of that stall is also possible by configuring jemalloc. Not saying that we should do it mind, and based on the replay speedups it looks like mimalloc might have better defaults for our workload, I just think that we should understand how mimalloc works and why it's better for us before we switch to it.

Mimalloc almost certainly gets rid of that one, but how?

It looks like mimalloc does time based purge like jemalloc

It looks like mimalloc does time based purge like jemalloc

I think I'm pretty mimalloc-pilled. I think that the key is that even if it does time based purge like jemalloc, since it has sharded freelists and works at a "mimalloc page" level, it never does gigantic (and contended) deallocations like jemalloc does, which means than even when purging after spikes, deallocation costs are amortized over a bunch of call sites and bounded in time, instead of having seconds long spikes like we do with jemalloc.
I personally would ship this to master and let it ride the trains, and see what happens. While it's in master it'll get tested on the master canaries, and we could ask Joe to test it on at least one big-stake node.

thanks for various thoughts and quick look into mimalloc so far! seems you have good first impression of it. lol
I'll spend some time to dig in further and write my own thoughts later.

Finally, it's time to share my thoughts after all the investigations.
As of now, I'm a bit neural to adapting mimalloc. Admittedly, I got hyped with the perf increase of replaying stage and mimalloc's promising design descriptions, originally.

As for reliability (read: no leak & no unbounded fragmentation), I'm now running a devbox against mb, needs another day or two, before conclusion.

Hum imo you can't draw conclusions after running a devbox for a couple of days. ... But at least it isn't crashing 😅 Imagine we switch allocator, and then we find that in some configurations after a while it goes OOM - I don't think it's something we can establish in a couple of days based on a single machine configuration ...

I agree. I just misused the word conclusion... Changing allocator is quite dangerous.
I wanted to see whether mimalloc would leak miserably, like rpmalloc did when used for agave-validator. After almost 10 days, i think mimalloc doesn't leak/crash at the very least (note that slight mem increase after 2-3 days is a known issue, which occurs even with jemalloc):

Also, I haven't confirmed yet but I'm moderately certain that this fixes the replay stall issue under system overload

i confirmed this is fixed.

blockstore-processor is ~27% faster and unified scheduler is ~36% faster according to solana-labs#35286 (comment). I think this alone is quite good perf gain by its own. :)

This is amazing!

here's a tone-down fact: the replay perf gain can be realized with jemalloc by working-around this particular alloc source in vm: https://github.com/anza-xyz/agave/pull/1364 Moreover, notice that jemalloc is slightly faster than mimalloc there. So, I don't think mimalloc is a clear win than jemalloc, as a general-purpose mem allocator, assuming the replay stage code-path should have exercised allocators with some varieties of alloc patterns.
Also, I've seen no general perf improvement over jemalloc as far as i've run a unstaked mainnet-beta node.

Mimalloc almost certainly gets rid of that one, but how? How does it compact/release memory? When? And from what threads? Because getting rid of that stall is also possible by configuring jemalloc. Not saying that we should do it mind, and based on the replay speedups it looks like mimalloc might have better defaults for our workload, I just think that we should understand how mimalloc works and why it's better for us before we switch to it.

As for this concern, I think you self-answered like below (and this aligns with my understanding):

It looks like mimalloc does time based purge like jemalloc

... I think that the key is that even if it does time based purge like jemalloc, since it has sharded freelists and works at a "mimalloc page" level, it never does gigantic (and contended) deallocations like jemalloc does, which means than even when purging after spikes, deallocation costs are amortized over a bunch of call sites and bounded in time, instead of having seconds long spikes like we do with jemalloc.

To add some colors from me, I stumbled on this paper, which is relevant for the time-decay stall: https://arxiv.org/abs/2401.11347:

algorithms ... that free objects in large batches circumvent a key optimization in JEmalloc. This optimization is intended to avoid the overhead of returning an object to a remote thread that allocated it (i.e., its owner), by instead placing the object in a local buffer that the local thread can subsequently allocate from. Every object allocated locally from this buffer is an object that does not need to be freed remotely, back to its owner. Freeing a large batch of objects can overflow this buffer, triggering an extremely high latency free call (on the order of tens of milliseconds or more) in which many objects are removed from this buffer and freed remotely to their respective owners, incurring extremely high lock contention in the process.
...
Further investigation using Linux Perftools led to the realization that poor performance in JEmalloc, such as when running on four sockets, is usually accompanied by a large fraction of the total cycle count being spent in function called je_tcache_bin_flush_small. Table 1  summarizes perf results to support the following discussion, and also quantifies how the total number of epochs changes as the thread count increases. These results confirm that the cost of freeing objects becomes prohibitive at high thread counts, preventing the data structure from scaling. According to the source code for this version (5.0.1-25) of JEmalloc, when a thread invokes free, it places the freed object in a thread local buffer, and then checks whether the buffer is filled beyond a given threshold. If so, it takes a large number of objects from that buffer (approximately 3/4 of the buffer), and for each object, does the following. First, it identifies which bin the object belongs to. If the object was originally allocated by a different thread, this bin might reside on a remote core, or even a remote socket. The thread locks the bin, then iterates over all objects in its buffer (while holding the lock), and for each object that belongs to this bin, it performs the necessary bookkeeping to free the object to that bin.
...
In summary, it is extremely expensive in JEmalloc for free to return objects to the remote threads that allocated them. To avoid this overhead, a thread frees to a local buffer, and subsequently allocates from that buffer. Every object allocated from that buffer is an object that does not need to be freed to a remote thread in future. Freeing a large batch overflows the buffer, forcing all objects to be freed remotely, causing extremely high lock contention.

on the other hand, as for mimalloc from the same paper:

MImalloc Sidesteps the Problem Altogether. MImalloc, on the other hand, is essentially immune to the problem we describe above by design. In MImalloc, a remote free synchronizes on a particular page’s free list. ... This makes it relatively inexpensive to immediately free an individual object to a remote thread in MImalloc, as doing so will cause contention only if another thread is simultaneously freeing another object that was allocated from the same page.
...
MImalloc is quite unique in its approach. To our knowledge, no other allocator maintains per-page free lists.

So, I think there's still some hope to mitigate the pathological perf degradation we're experiencing altogether with mimalloc.

It looks like mimalloc avoids the IPIs and TLB shootdowns jemalloc causes in calloc by... not implementing calloc. calloc in mimalloc is just malloc() + memset. I'm not sure how this scales with high number of txs, that's a lot of pagefaults.

to be clear, i don't have particular words on this as my knowledge is still limited... at least, system-wide minor pagefaults aren't particularly increased as compared to jemalloc
lastly, here's the remaining topic to cover: market share and product quality: my impression is that it's not ideal but acceptable for adaption.
market share:
seems it's used at microsoft internally. but, basically that's all. various high-profile projects (ClickHouse, rustc, Polkadot, Apache Arrow) tried it. however, none officially chose it, it seems. Admittedly, the market share growth is quite slow, considering it's been 5 years since released.
product quality:
as far as i read mimalloc's code, it's maintained, yet not in the highest coding standards. Also the technical report (https://www.microsoft.com/en-us/research/publication/mimalloc-free-list-sharding-in-action/)'s coverage is rather sparse with typos. as for rust-bindings, it's straight-forwardly written and updated to follow upstream releases: https://crates.io/crates/mimalloc

as a sample among our bench programs, I picked solana-banking-bench, because this is the closest bench I'd like to address the perf issue (banking stage flooded with mb txes):
glibc:

sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4                                                      [total_sent: 1152000, base_tx_count: 55296, txs_processed: 1195456, txs_landed: 1140160, total_us: 22874161, tx_total_us: 22138973]
{'name': 'banking_bench_total', 'median': '50362.50'}
{'name': 'banking_bench_tx_total', 'median': '52034.93'}
{'name': 'banking_bench_success_tx_total', 'median': '49844.89'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1200576, txs_landed: 1145280, total_us: 22701875, tx_total_us: 21960779]
{'name': 'banking_bench_total', 'median': '50744.71'}
{'name': 'banking_bench_tx_total', 'median': '52457.16'}
{'name': 'banking_bench_success_tx_total', 'median': '50448.70'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1202944, txs_landed: 1147648, total_us: 22738385, tx_total_us: 22000919]
{'name': 'banking_bench_total', 'median': '50663.23'}
{'name': 'banking_bench_tx_total', 'median': '52361.45'}
{'name': 'banking_bench_success_tx_total', 'median': '50471.83'}

rpmalloc:

sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1191360, txs_landed: 1136064, total_us: 19135997, tx_total_us: 18700941]
{'name': 'banking_bench_total', 'median': '60200.68'}
{'name': 'banking_bench_tx_total', 'median': '61601.18'}
{'name': 'banking_bench_success_tx_total', 'median': '59367.90'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1193472, txs_landed: 1138176, total_us: 18655284, tx_total_us: 18223262]
{'name': 'banking_bench_total', 'median': '61751.94'}
{'name': 'banking_bench_tx_total', 'median': '63215.91'}
{'name': 'banking_bench_success_tx_total', 'median': '61010.92'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1196736, txs_landed: 1141440, total_us: 19450234, tx_total_us: 19005383]
{'name': 'banking_bench_total', 'median': '59228.08'}
{'name': 'banking_bench_tx_total', 'median': '60614.41'}
{'name': 'banking_bench_success_tx_total', 'median': '58685.16'}

mimalloc:

sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1194609, txs_landed: 1139313, total_us: 18883418, tx_total_us: 18343669]
{'name': 'banking_bench_total', 'median': '61005.90'}
{'name': 'banking_bench_tx_total', 'median': '62800.96'}
{'name': 'banking_bench_success_tx_total', 'median': '60334.05'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1197824, txs_landed: 1142528, total_us: 18926181, tx_total_us: 18364487]
{'name': 'banking_bench_total', 'median': '60868.06'}
{'name': 'banking_bench_tx_total', 'median': '62729.77'}
{'name': 'banking_bench_success_tx_total', 'median': '60367.59'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1194560, txs_landed: 1139264, total_us: 18904023, tx_total_us: 18361670]
{'name': 'banking_bench_total', 'median': '60939.41'}
{'name': 'banking_bench_tx_total', 'median': '62739.39'}
{'name': 'banking_bench_success_tx_total', 'median': '60265.69'}

jemalloc:

sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1197440, txs_landed: 1142144, total_us: 18922589, tx_total_us: 18402904]
{'name': 'banking_bench_total', 'median': '60879.62'}
{'name': 'banking_bench_tx_total', 'median': '62598.82'}
{'name': 'banking_bench_success_tx_total', 'median': '60358.76'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1194432, txs_landed: 1139136, total_us: 18952931, tx_total_us: 18392036]
{'name': 'banking_bench_total', 'median': '60782.16'}
{'name': 'banking_bench_tx_total', 'median': '62635.81'}
{'name': 'banking_bench_success_tx_total', 'median': '60103.42'}
sol@dev-equinix-tokyo-5:~/work/solana-labs/final-unified-scheduler-branch$ target/x86_64-unknown-linux-gnu/release/solana-banking-bench |& tail -n 4
[total_sent: 1152000, base_tx_count: 55296, txs_processed: 1199104, txs_landed: 1143808, total_us: 18344841, tx_total_us: 17826278]
{'name': 'banking_bench_total', 'median': '62796.95'}
{'name': 'banking_bench_tx_total', 'median': '64623.70'}
{'name': 'banking_bench_success_tx_total', 'median': '62350.39'}

as a quick glance, it's so outstanding that glibc is slow. rpmalloc, jemalloc and mimalloc are similarly better than glibc by ~120%. One subtle takeaway is that mimalloc's perf variance is noticeably small, compared to rpmalloc and jemalloc. I think this is illustrating their 2 selling points, which is understandable:

bounded: it does not suffer from blowup [1], has bounded worst-case allocation times (wcat) (upto OS primitives)

and

... has no internal points of contention using only atomic operations

Lastly, glibc's low variance is kind of expected: its impl is way more naive in the light of multi-threaded age, than other newer kids (that's why it's slow...)

status update: almost stale. but i'm moving forward this very slowly. Recently, I've managed to repro the jemalloc-induced pathologically slow free()-ing via agave-ledger-tool simulate-block-production (#2733)
Also, I just found another encouraging paper about mimalloc: https://retis.sssup.it/~a.biondi/papers/RTAS24.pdf

there is another package: https://crates.io/crates/mimalloc-rust which indicate the main crate is not so optimized, but the underlying mimalloc version might be old, there is another one: https://crates.io/crates/mimalloc2-rust which is a fork but with a later version of mimalloc


[Feature]: MessageBar component

How to promote this component
Please give a thumbs up reaction to this post to promote this backlog item. You may also share your usage scenario in the comments.
Component description
A banner (MessageBar) displays errors, warnings, or important information about an open app or file. For example, if a file failed to upload an error message bar should appear.
The main difference between this control and the Notify() function is to provide option for Action buttons. Please only upvote if this additional functionality is actually needed.
Offer one to two action buttons to help people solve any errors they're receiving. Limit button text to fewer than 50 characters (including spaces) to leave room for translation. Action buttons can have any callback attached to them and should provide people with options to address the notification and dismiss the message bar.

Fluent UI Documentation

Would be really great, if these messages could stack and allow the user to respond to each item.  The problem with "Notify" is that when a user receives multiple notifications, they only ever see the last one as the prior ones are overwritten.  There is no way to show multiple notifications that might occur at the same time, for different reasons, to the user.

This would be awesome to have. We have many scenarios for this as well.


Can I using this crate with web framework like actix-web

I would like to use this crate to verify the operation of a REST API server implemented based on Rust, and I am wondering if it is possible.
So I would like to ask if it is possible to use this with crates like Actix-web.

You can see what of the top 1000 crates work out of the box on https://reports.risczero.com/crates-validation:

compile_error!("Socket2 doesn't support the compile target");

At this time it seems like there may be some issues using that crate in the guest - most likely there would be a way to work around this.
This kind of question is much better for our discord that has a dedicated dev-questions/support-forum channel : https://discord.com/invite/risczero
See you in there @sweatpotato13 :grinning:


Failing to detect SharePoint 2013 Foundation Install

SharePoint 2013 Foundation is not being detected as installed.
In the Function CheckConfigFiles([xml]$xmlinput please update
if ($pidKeyProjectServer -notlike "?????-?????-?????-?????-?????")
to
if ($pidKey -notlike "?????-?????-?????-?????-?????" -and $xmlinput.Configuration.Install.SKU -ne "Foundation" )
Also in the Function Get-SharePointInstall
if ((Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*) | Where-Object {$_.DisplayName -like "Microsoft SharePoint Server*"})
to
if ((Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*) | Where-Object {$_.DisplayName -like "Microsoft SharePoint Server*" -or $_.DisplayName -like "Microsoft SharePoint Foundation*"})

Same in Start-RemoteInstaller function (like in Get-SharePointInstall)

Same issue, I with this was pinned until it is (if ever) fixed.

Rick, If you look at my post it will give you the code to fix the issue. I just was never added to the official release.
…
-Paul
On Wed, Oct 9, 2019 at 3:13 PM Rick Toner @.***> wrote: Same issue, I with this was pinned until it is (if ever) fixed. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=ABI4MFJPFTFWQSZYHIR77J3QNY3NXA5CNFSM4EUEL2AKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAZFZ7Q#issuecomment-540171518>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABI4MFJZY6CBIYASPZTLCVDQNY3NXANCNFSM4EUEL2AA .

I did see that, I just wish it was added into the code, since 2013 Foundation is the last free version, some users will still try to use this.
The bad part is I had to find both of the errors, stepping through the code, before I found your solution.  That's why I was hoping they would add it to the code.

Rick, If you look at my post it will give you the code to fix the issue. I just was never added to the official release.
-Paul

I did see that, I just wish it was added into the code, since 2013 Foundation is the last free version, some users will still try to use this.
The bad part is I had to find both of the errors, stepping through the code, before I found your solution. That's why I was hoping they would add it to the code.


.env for Trino

The example-env file in still refers to presto:
#MODULES=presto,athena,prod,bq
MODULES=presto
MODULES_PRESTO_ENGINE=presto
MODULES_PRESTO_API=http://presto:8080/v1
MODULES_PRESTO_CATALOG=system
MODULES_PRESTO_SCHEMA=runtime
MODULES_PRESTO_SOURCE=quix
MODULES_PRESTO_DB_EMPTY_TIMEOUT=60000
MODULES_PRESTO_DB_REQUEST_TIMEOUT=10000
`MODULES_PRESTO_HTTP_HEADERS_PREFIX=X-PRESTO-
I have both Trino and Quix installed in docker containers and want to set up the connection. How can I update the code since Presto had been rebranded to Trino?

Change MODULES_PRESTO_* to MODULES_TRINO_*
Change MODULES=presto to MODULES=trino

This doesn't really change anything in terms of actual Trino setup, it's just how we manage module naming and configuration.


Flowmeter calibration Issue

When calibrating the flow meter I choose the correct tap (#9) and then check the Volume button and press “Do Config by Volume". In the older versions of firmware, on the next screen a 0 would populate right away in the Pulses box and when I got some flow going, the count would increase. In the Development firmware, a zero doesn’t immediately show up in the Pulses box and nothing happens when get some flow going. Pulses don’t increment, but the fact that it behaves different between v1.0.0 and devel makes me think it’s a firmware/coding problem and nothing on my end. It doesn’t matter whether I enter any ounces first or not, it doesn’t appear to count pulses. I’ve tried choosing different Tap numbers and that doesn’t make any difference either (didn’t expect it to though).

Working on this one now.

I added myself the ability to add pulses manually (by typing) so that I can debug this one.  A lot of work for that, but I don;t have any flowmeters at hand.

Closed (finally!) and in devel.  Beta release pending.

Updated Keg Cop Beta to 1.1.1-Beta.3


Fix process mode update when mode owner is set to Inherit

When the process mode owner is the root and is set to PROCESS_MODE_INHERIT, the mode needs to be considered as the default (PROCESS_MODE_PAUSABLE) instead of making the node disabled.
Fixes #49818

Ah right, the root node. I think for simplicity it should be set to PAUSABLE by default, and if changing the mode to INHERIT should error if is_inside_tree() && get_tree()->get_root() == this. We could probably do a consistency check with unlikely() and throw an error in the can_process function if the owner is set to inherit, as this would be a bug.

@reduz I've rebased and updated from your comment.

Thanks!


Dont show the web container

Describe the bug
When I Fork the tutorial Angular from  ready-made sample project in StackBlitz. (https://angular.io/generated/live-examples/getting-started-v0/stackblitz.html) only show the project but the preview is not charged
Link to the blitz that caused the error
https://stackblitz.com/edit/angular-25y8wu?file=src%2Fassets%2Fshipping.json
Steps to reproduce
1.-https://angular.io/generated/live-examples/getting-started-v0/stackblitz.html
2.-log into stack blitz
3.- Fork the project you generated.
Expected behavior

Screenshots

Platform
Browser name  = Chrome
Full version  = 95.0.4638.69
Major version = 95
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 94680331,
  "usedJSHeapSize": 85902127,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 320dd3b483ec8295ca1e4a3ccd95cf9e5165f9d0

Additional context
No response

same for me but on nodejs all the other platforms seem to work ;/

@firekoala Sorry I don't understand what you meant with "all the other platforms". Do you see any errors in the devtools console? Have you looked at #405?

I meant frameworks. It works with every framework but the blank nodejs.
All the others load the container properly.
On Wed, Nov 24, 2021, 4:20 PM Roberto Vidal @.***>
wrote:

@firekoala https://github.com/firekoala Sorry I don't understand what
you meant with "all the other platforms". Do you see any errors in the
devtools console? Have you looked at #405
https://github.com/stackblitz/webcontainer-core/issues/405?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stackblitz/webcontainer-core/issues/404#issuecomment-977976588,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADESN3QQUXVR6TTRCI4BH53UNT7E5ANCNFSM5IAOAW2A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

:wave: It seems this issue has been sitting for a while without new info. I'm closing this, but please feel free to open a new one if you still encounter this problem.


Add Support for User Relation

https://github.com/scrthq/PSGSuite/issues/129

Thanks for sending this over, @mattwoolnough!! Going to check it out ASAP, busy week this week!!

Merging this in, will get it deployed by this weekend once I add a few other pending items to the release! I'll comment on the original issue #129 once the additions are deployed to the PowerShell Gallery.
Thanks again, @mattwoolnough!!

@mattwoolnough gotcha! That's awesome! If you feel there's value in using a Global scoped variable, I'm all ears. Happy to help solve a problem if it means less workarounds needed on your, or anyone else's, end!

I don't think that my solution was the most elegant one, but it got me where I needed to be.
The issue is that there is no local file system from which to read the config file.

Interesting! How are you solving the lack of a file system? This would be a scenario I'd love to support, if possible!


Nested instances and immerable

Retracted

Created https://github.com/immerjs/immer/issues/1148 instead after new insights.


Re-factor/clean up lazyBlockReading use in HoodieCompactedLogScanner

Essentially, there are 2 ways to lazily read blocks :
Do a 2 pass over the log file (just like this implementation does) and merge at the end.
Do a first pass, find first group of blocks that need to be merged. Now the inputstream in the LogBlocks will rewind the disk pointer to the beginning from where it needs to read the block but the logblock does not know where to move the disk pointer for the last block ( which is at the end of the footer). So after this group of blocks is merged, the HoodieLogReader needs to reset the pointer to the end of the footer of this log block. This approach involves some extra context to be implemented in HoodieReader and/or in the logBlocks to move the pointer to the correct end position.

Moved to https://issues.apache.org/jira/browse/HUDI-48


TextVectorizationLayer supporting custom padding token

Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using): v2.2.0-rc2
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
When using the tf.keras.layers.experimental.preprocessing.TextVectorization we are not able to specify a padding token which should map to the value 0. When we have a sequence such as:
tf.constant(['<PAD> word1 word2 OOV <EOS>'], dtype=tf.string)

in which the <PAD> is the padding token. If the TextVectorization  output_sequence_length is bigger than the size of the previous sequence (5), for example 10, we would get:
vectorize_layer(tf.expand_dims(tf.constant(['<PAD> word1 word2 OOV <EOS>'], dtype=tf.string), axis=0))

`<tf.Tensor: shape=(1, 10), dtype=int64, numpy=array([[5,   2,   3, 1,  6,   0,   0,   0,   0,   0]])>`

(the oov token maps to 1, while the <PAD> token has a value different than 0 which is the default padding value by the layer). In my preprocessing I am generating sequences of the same size in each batch and the <PAD> token only appears at the beginning, so the model is oblivious to the 0 values and only sees the 5's as the padding token ID. However, it would be nice if we only had one token ID for the padding.
I overrided this behavior in tf v2.1.0 by doing the following:
vectorize_layer.adapt(tf.data.TextLineDataset('train.txt').batch(32))
pad_token_vocab = vectorize_layer._convert_to_ndarray(['<PAD>'])
pad_token_value = vectorize_layer._convert_to_ndarray([0])
vectorize_layer._insert_table_data(pad_token_vocab, pad_token_value)
vectorize_layer.set_vocabulary[('<EOS>'], append=True)

However, there were major changes from v2.1.0 to v.2.2-rc2 so this is no longer possible.
Will this change the current api? How? Adding an optional argument: padding_token.
Who will benefit with this feature? I believe it's a nice to have for everyone training language models.
Any Other info.

Hi @EduardoDixo!
We are checking to see whether you still need help in this issue . Have you tried latest version (TF 2.7) yet?


add config field in MLToolSpec for static parameters

Description
Add config field in MLToolSpec to support static parameters in tool execution.
An example from the issue 2918.
POST /_plugins/_ml/agents/_register
{
	"name": "Test Agent",
	"type": "conversational",
	"description": "test agent",
	"llm": {
		"model_id": "<model id>",
		"parameters": {
      "max_iteration": 5,
      "stop_when_no_tool_found": true,
      "response_filter": "$.completion"
    }
	},
	"memory": {
		"type": "conversation_index"
	},
	"app_type": "chat",
	"tools": [
		{
			"type": "SearchIndexTool",
			"description": "A tool to search opensearch index with natural language question.",
			"include_output_in_agent_response": true,
			"config": {
				"input": "{\"index\": \"sample-index\", \"query\": {\"query\": { \"match_all\": {}}} }"
			}
		}
	]
}

Related Issues
https://github.com/opensearch-project/ml-commons/issues/2836
https://github.com/opensearch-project/ml-commons/issues/2918
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] API changes companion pull request created.
[ ] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

The flow framework issue, https://github.com/opensearch-project/flow-framework/issues/878.

@reuschling Can you help review this PR?

@jngz-es Can you please provide an example on how to use tool config?

@jngz-es Can you please provide an example on how to use tool config?

Provided an example in the description section.

Pinging @reuschling to review the PR.

Pinging @reuschling to review the PR.

Thanks @yuye-aws for prompting review on this. Thanks @Zhangxunmt for approval. Thanks @dhrubo-os for your initial review.
Code freeze / 2.18 RC generation is next Tuesday Oct 22.  Downstream plugin PRs (https://github.com/opensearch-project/flow-framework/pull/899) are dependent on this one being merged and need to merge before code freeze.
Please do not wait until the last minute to get this merged; last-minute PR merges have occurred in at least 2 previous releases and this one's been open for a few weeks.


Multirun with filename globbing

Should be runnable from the node command-line, or from gradle/maven build script.

dup of #8


Fix some grammar in README.md

Tried to be more consistent with commas.
Fix capitalization.
Fix punctuation.

Additionally, I think the way “Winston” is written could be more
consistent (currently it is written “winston”, “Winston”, and
“winston” in different places. But I’m not one to say which the
correct way is.

Thank you for your contribution!


Regular Sync

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: wkcn:x: megvii-mgeYou have signed the CLA already but the status is still pending? Let us recheck it.


User & Role - Adding features and improving model

As the result of User Model unit testing in #61. We need to add more features and improve the User Model. Those items list below just for note, we will add more issues for them later.
Feature:

Disable user
Delete user
Change email

Improve:

Process of duplicate
More user states
Password expiration

User roles (Execute/View/Edit)
Change password


Check if PlayReady license message is wrapped in XML.

Resolves #814

Thank you very much for your contribution!

Looks good to me!  I'll run tests on the build bot.

This fix was just released in v2.1.2.


Add "Files" button on /ptal command

Why ?
Because it's more simple and fast to see files directly for review. At this moment, for an review, we need to click on the only available button "View on GitHub", wait for it to load, and click on Files.
Information
The emoji at line 222 is 📁 (a opened folder)
Preview

Small mistake in actually adding the component. I'm curious how you got the preview image as this code would duplicate the github link

For this question, I edited the HTML page for this preview. I haven't tested the robot, but I know about discord.js and builder modules. If ever, it's to be tested, but if the similar component above and below works without a hitch, then this one should work too. However, I tested it on one of my robots to integrate the folder emoji. It displays just as it does in the preview.

Small mistake in actually adding the component. I'm curious how you got the preview image as this code would duplicate the github link

For this question, I edited the HTML page for this preview. I haven't tested the robot, but I know about discord.js and builder modules. If ever, it's to be tested, but if the similar component above and below works without a hitch, then this one should work too. However, I tested it on one of my robots to integrate the folder emoji. It displays just as it does in the preview.

Makes sense. It looks like it should all work. I mostly want to test refreshing since that implementation is... not the most fault resilient

Just like I guessed. This behavior currently breaks reloading. I'm going to take a bit of time to rewrite the reloading logic and this should then be good to be merged on top of that

Just like I guessed. This behavior currently breaks reloading. I'm going to take a bit of time to rewrite the reloading logic and this should then be good to be merged on top of that

Good!

@thomasbnt could you please rebase onto main? I just merged #84 which should alleviate the reload issues, clearing this up to merge

@thomasbnt could you please rebase onto main? I just merged #84 which should alleviate the reload issues, clearing this up to merge

yeep just merged!

Great. I’ll just test it out quickly tomorrow to make sure reloading works now and then I’ll merge it

Everything works now

Awesome thanks!


(FACT-1078) Fix FQDN resolution where canonical name is node name.

From getaddrinfo's man page:

if the canonical name is not available, then ai_canonname shall refer
to the nodename argument or a string with the same contents.

This means that FQDN may resolve back to only the hostname when this
happens.  This fix treats a canonical name that matches the hostname to
be the same as if the hostname did not resolve, resulting in an empty
FQDN.  This causes the base resolver to fallback to using "hostname +
domain" as the FQDN.

I just wanted PR #1000.

CLA signed by all contributors.


Improved exceptions

Right now when some exception is thrown it gets logged in such form:
com.ocadotechnology.sttp.oauth2.common$OAuth2Exception: null

without any details or cause.
The reason is that Exception does not fill the Throwable fields like message or cause.
I've created some proposal, which I'm not 100% happy with though (especially fact how the cause is calculated with pattern matching), but will post is as a beginning for a wider discussion.

Some alternative idea would be making all Errors extending Throwable and leaving the responsibility to fill messages and causes on their part.

Some alternative idea would be making all Errors extending Throwable and leaving the responsibility to fill messages and causes on their part.

I like this idea a little more...

And I don't like it, because the idea was that Error should form a separate hierarchy from Throwable. Having a Throwable cause is something acceptable.

What's wrong with it being an ADT and a throwable?

That Throwable will be a supertype of that ADT, and it won't play nice in ZIO if you don't want Task or RIO.

I don't see why it wouldn't play nice, you don't have to use the fact it's a Throwable.

Yes, otherwise it'll likely infer to Product with Serializable, so Product with Serializable with Throwable isn't that bad in my opinion ;)

I think it will infer Object and you will have a warning that you are a lame programmer 😛
a type was inferred to be `Object`; this may indicate a programming error.

Since this library is an extension for sttp, in such situations i would look at how similar dilemmas were solved in sttp-core. In sttp there is ResponseException ADT with HttpError, DeserializationException as a possible implementations. They all are extending Exception.

Using ZIO we can still use IO[Error, Token] to be more precise than Task[Token]

also extending Exception instead of Throwable seems to be more reasonable, since Exceptions are recoverable in the matter of JVM (they are not java.lang.Error)

@bwiercinski this is interesting thought. I played with it a bit and this is a result:
https://github.com/ocadotechnology/sttp-oauth2/pull/145
I think I like it better, the only thing I don't 100% like is the fact Error is not something that will be thrown (OAuth2Exception would be), but they are still Exceptions. However the rest is quite clear, so this would be my preference.
@tplaskowski @kubukoz @bwiercinski @majk-p  what's your thoughts? I'd like to proceed with this soon.

I like #145 more ;)

Closing because of #145