Disable / enable button after dialog is shown

With the standard AlertDialog.Builder I used to be able to disable the positive button after
dialog = builder.show();
by calling
dialog.getButton(AlertDialog.BUTTON_POSITIVE).setEnabled(false);
With MaterialDialogBuilder this doesn't work.

I am investigating on this. As a workaround you can use ((Button) dialog.findViewById(android.R.id.button3)).setEnabled(false); until this issue is solved.

Your workaround works. Thanks!

As far as I understand this issue, it is not solveable without reworking the library from scratch. The problem is, that the class AlertDialog references the buttons (and other views as well) by using IDs, which are not exposed publicly to the Android API. Therefore the library's MaterialDialogBuilder is forced to use different IDs when creating a dialog, which prevents the class AlertDialog from referencing these views. This issue is propably not only restricted to the getButton-method, but also to other methods, which require to reference views. The preferable solution for this is to not return instances of the class AlertDialog when creating a dialog, but implementing a custom dialog class, which implements methods like getButton on its own. I yield at implementing this in a future major release.

In version 3.0.0 the library has been completely reworked in order to make it independent from the class AlertDialog of the Android SDK. Dialogs, which are created using the library are now instances of the newly introduced class MaterialDialog. The class MaterialDialogBuilder has been removed. In order to create dialogs, the builder MaterialDialog.Builder has to be used now. The class MaterialDialog does provide methods, which allow to retrieve/modify attributes a dialog after it has been shown, including the getButton-method, which was the focus of this bug report.


WIP: Allow for options

Fixes #3
Keeping as Draft / proof-of-concept for now. If there's interest in supporting some kind of Options, I can clean this up (separate the new spago changes from the relevant changes here) and fill out the PR questions below. Documentation and examples would have to be updated too.
What does this pull request do?
Please describe the purpose of the pull request, including any background context and links to related issues. If this introduces a large change to the project, please describe what you have implemented.
Where should the reviewer start?
Help save the reviewer time by highlighting the most important sections of code. Please include test cases if you are implementing new code.
Other Notes:
Does the project documentation need to be updated? Should we introduce a new example, or update any existing examples? Does this PR require any other follow-up tasks?

I’m on board with supporting options, and using slugify as an example. Thanks for getting this started!
I’m a little hesitant to bring it in as a dev dependency; just one more thing to keep updated. Could we just use some example strings instead and parse/print them?

Opened #5 instead, with more minimal set of changes (keeps existing Nix setup)


feat: add support for granite architecture models (granite-3.0)

This PR does the following:

replace hard coded chat templates with imports from instructlab/training, which maintains chat templates for all natively supported models
For safetensor models that carry a tokenizer_config.json file, extract chat template and special tokens from there. Only fall-back to in-memory templates if unable to read from tokenizer config file
centralize system prompts in one place. Add a system prompt for granite-3.0 models. Add a default prompt for non-granite models. Use model architecture to pick the correct system prompt for a model
supply the correct system prompt to SDG based on the student model configured in the config file. Also supply extra parameter legacy_pretraining_format to sdg to dictate whether SDG should use granite-3.0 special tokens or existing granite-7b special tokens in the pretraining messages format
communicate usage of legacy special tokens to training via use_legacy_tmpl in the TrainingArgs API
update context handling to accommodate supporting multiple system prompts that need to be chosen based on model architecture
add --use-dolomite as an flag and additional_arg in train config for users to fall back to dolomite architecture if required  (default to False)
bump training version to >=0.6.0 to consume granite-3.0 related changes

NOTE:
detecting architecture for GGUF models is still a TODO, as a result right now all GGUF models get the default system prompt even if they are of granite or llama architecture. This will be fixed in a follow up PR
as for being able to serve and convert granite-3.0 GGUF models, that is currently blocked until we can upgrade llama-cpp to v0.3
Issue resolved by this Pull Request:
Resolves #2523 #2583

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Functional tests have been added, if necessary.
[ ] E2E Workflow tests have been added, if necessary.

I don't think we can update llama-cpp here - see the following:
Issue: https://github.com/instructlab/instructlab/issues/2516
PR: https://github.com/instructlab/instructlab/pull/2368

I don't think we can update llama-cpp here - see the following: Issue: #2516 PR: #2368

ah ack
thanks @nathan-weinberg , will remove that from here then

One larger question I have - if I am not mistaken, it seems 7b architecture is now being marked as "legacy" - I wonder, if that is indeed the case, we should just refer to it explicitly as 7b instead of "legacy"
My reasoning is: if we go on to support other granite archs (e.g. a 9b) we will find ourselves in a situation where we default to 9b but support 8b and 7b - in a case like that, it's better to use explicit terms than things like "legacy"

AFAIU, there is only the old architecture ("llama") and the new architecture ("granite") - any new granite models in the future should all just be using this granite architecture, so the arrival of a 9b model won't make 8b "legacy" in that sense - until there is a granite-2.0 architecture or something
so I'm assuming all future models will just be "granite" and we won't get another "legacy"

One larger question I have - if I am not mistaken, it seems 7b architecture is now being marked as "legacy" - I wonder, if that is indeed the case, we should just refer to it explicitly as 7b instead of "legacy"
My reasoning is: if we go on to support other granite archs (e.g. a 9b) we will find ourselves in a situation where we default to 9b but support 8b and 7b - in a case like that, it's better to use explicit terms than things like "legacy"

AFAIU, there is only the old architecture ("llama") and the new architecture ("granite") - any new granite models in the future should all just be using this granite architecture, so the arrival of a 9b model won't make 8b "legacy" in that sense - until there is a granite-2.0 architecture or something
so I'm assuming all future models will just be "granite" and we won't get another "legacy" architecture

Thanks for clarifying - should we just call "legacy" => "llama" then?

One larger question I have - if I am not mistaken, it seems 7b architecture is now being marked as "legacy" - I wonder, if that is indeed the case, we should just refer to it explicitly as 7b instead of "legacy"
My reasoning is: if we go on to support other granite archs (e.g. a 9b) we will find ourselves in a situation where we default to 9b but support 8b and 7b - in a case like that, it's better to use explicit terms than things like "legacy"

AFAIU, there is only the old architecture ("llama") and the new architecture ("granite") - any new granite models in the future should all just be using this granite architecture, so the arrival of a 9b model won't make 8b "legacy" in that sense - until there is a granite-2.0 architecture or something
so I'm assuming all future models will just be "granite" and we won't get another "legacy" architecture

Thanks for clarifying - should we just call "legacy" => "llama" then?

Sure, I have no strong feelings about that
Though both SDG and training have this parameter either already merged or in review - so I can't update those parameters at their boundaries with the CLI, but if there are any CLI-only places that use legacy I can replace them if we want to do that

One larger question I have - if I am not mistaken, it seems 7b architecture is now being marked as "legacy" - I wonder, if that is indeed the case, we should just refer to it explicitly as 7b instead of "legacy"
My reasoning is: if we go on to support other granite archs (e.g. a 9b) we will find ourselves in a situation where we default to 9b but support 8b and 7b - in a case like that, it's better to use explicit terms than things like "legacy"

AFAIU, there is only the old architecture ("llama") and the new architecture ("granite") - any new granite models in the future should all just be using this granite architecture, so the arrival of a 9b model won't make 8b "legacy" in that sense - until there is a granite-2.0 architecture or something
so I'm assuming all future models will just be "granite" and we won't get another "legacy" architecture

Thanks for clarifying - should we just call "legacy" => "llama" then?

Sure, I have no strong feelings about that Though both SDG and training have this parameter either already merged or in review - so I can't update those parameters at their boundaries with the CLI, but if there are any CLI-only places that use legacy I can replace them if we want to do that

Ah no worries then - let's leave it consistent for now, and we can revisit in the future need-be
Just to confirm - all existing supporting architectures will continue to work yes?

One larger question I have - if I am not mistaken, it seems 7b architecture is now being marked as "legacy" - I wonder, if that is indeed the case, we should just refer to it explicitly as 7b instead of "legacy"
My reasoning is: if we go on to support other granite archs (e.g. a 9b) we will find ourselves in a situation where we default to 9b but support 8b and 7b - in a case like that, it's better to use explicit terms than things like "legacy"

AFAIU, there is only the old architecture ("llama") and the new architecture ("granite") - any new granite models in the future should all just be using this granite architecture, so the arrival of a 9b model won't make 8b "legacy" in that sense - until there is a granite-2.0 architecture or something
so I'm assuming all future models will just be "granite" and we won't get another "legacy" architecture

Thanks for clarifying - should we just call "legacy" => "llama" then?

Sure, I have no strong feelings about that Though both SDG and training have this parameter either already merged or in review - so I can't update those parameters at their boundaries with the CLI, but if there are any CLI-only places that use legacy I can replace them if we want to do that

Ah no worries then - let's leave it consistent for now, and we can revisit in the future need-be
Just to confirm - all existing supporting architectures will continue to work yes?

yes, they should continue to work

Regarding reading the configs of gguf models, see https://huggingface.co/docs/transformers/en/gguf - it requires gguf >= 0.10.0, but we have an in-progress PR in SDG to do things like load a tokenizer out of a gguf model, using code like below where model_dir is the directly containing the gguf file and model_filename is the name of the gguf file itself:
tokenizer = AutoTokenizer.from_pretrained(model_dir, gguf_file=model_filename)

That deviates a bit from the examples here of parsing config files directly, but I believe would let you get what you need out of the loaded tokenizer.

Regarding reading the configs of gguf models, see https://huggingface.co/docs/transformers/en/gguf - it requires gguf >= 0.10.0, but we have an in-progress PR in SDG to do things like load a tokenizer out of a gguf model, using code like below where model_dir is the directly containing the gguf file and model_filename is the name of the gguf file itself:
tokenizer = AutoTokenizer.from_pretrained(model_dir, gguf_file=model_filename)

That deviates a bit from the examples here of parsing config files directly, but I believe would let you get what you need out of the loaded tokenizer.

Thanks @bbrowning! The only problem is our version of transformers is not new enough to recognize granite architecture models - and I think we might be constrained to this version because of optimum for gaudi (based on the comment in the requirements.txt)

Just a general note that CI won't give us a great signal whether all this code works unless we kick off that larger CI job on this PR that uses non-gguf models - most of the chat template and such code is unimplemented for GGUF models still, which is what all of our smaller CI models use.

Removing my requested changes flag since the change in key from template to chat_template got in for reading tokenizer configs. I'd love to see a unit test get in for this as well, but also don't want to hold up the process since the bug itself looks fixed 😄

added a few!

added a few! sorry - i only pushed the fix earlier to be able to do some manual testing on a remote machine before adding unit tests

No need to apologize - and thank you for the quick turnaround! It looks like they may have also caught that SPECIAL_TOEKNS typo, which is even better! I pulled your latest changes and the new unit tests all passed for me locally :tada:

added a few! sorry - i only pushed the fix earlier to be able to do some manual testing on a remote machine before adding unit tests

No need to apologize - and thank you for the quick turnaround! It looks like they may have also caught that SPECIAL_TOEKNS typo, which is even better! I pulled your latest changes and the new unit tests all passed for me locally 🎉

yeah they did hahah
thanks for running this locally and confirming!


Failed to get count of items in a sap.m.Table

Hi Experts,
In my test, I tried to assert the count of items in a sap.m.Table.
Firstly I tried it like this:
const table = browser.asControl({
    selector: {
        id: "idDetailTable",
        viewName: "deleteDataSubjects.view.Detail"
    }
});
const items = table.getItems();
expect(items.length).toBe(1);

But I got the following error:

When I debug it, I could see that I successfully got the table object:

But it didn't generate the "getItems" method:

Then I tried this:
const table = browser.asControl({
    selector: {
        id: "idDetailTable",
        viewName: "deleteDataSubjects.view.Detail"
    }
});
const items = table.getAggregation("items");
expect(items.length).toBe(1);

I could successfully get the items as [] and the assertion failed:

I got the selector of the table from the test recorder:

Some other hint: the data resource of the table is OData, e.g. one cell of it is like:
{
        controlType: "sap.m.ObjectStatus",
        viewName: "deleteDataSubjects.view.Detail",
        bindingPath: {
            path: "/ResidenceExpiredDataSubjects(jobID='9223372036854775807',dataSubjectGuid='1641982475494')",
            propertyPath: "dataSubjectID",
            modelName: "mainODataModel"
        }
    }

Thank you and best regards,
Cong

Hi, can you please try interaction: „root“. Might be already the solution.
see: https://github.com/js-soft/wdi5/issues/61

code-wise example: https://github.com/js-soft/wdi5/blob/9ad347d07eb99e23678cc83def7c3006be77e8ff/wdio-ui5-service/test/ui5.test.js#L9

@dominikfeininger Thank you! It really works. Maybe it's better to document it in the readme or somewhere.


Request to include Power Platform and Dynamics 365

Can we please include Dynamics 365 and Power Platform in this KB as well?

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

ID: 3c9d1ff4-9e32-39fc-2d8d-46d3c07bca4d
Version Independent ID: 72b20547-e78b-f6d2-6e69-31c846965ad0
Content: Isolation in the Azure Public Cloud
Content Source: articles/security/fundamentals/isolation-choices.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @unifycloud
Microsoft Alias: TomSh

@sundium  Thank you for your feedback . We will investigate and update the thread.

@sundium Thanks for the feedback. We will engage the content development team for further investigation, they will verify and perform necessary changes in the document as needed.


[FEATURE]: Cockroach DB Support

Describe what you want
I know on the front README, drizzle states that cockroach is coming based on the emoji. I was curious if there was a better timeline estimate as to when cockroach will be officially supported?

Any update?

Bump

Im going to close this issue out. While I am no longer using CockroachDB, Drizzle supports it just fine with the postgres js driver.

Does this work with Cockroach db? I can't find any official mention in the docs...


Add a sound effect when receive funds

By default that sound has disabled, but user can enable on settings menu. I selected a fun sound from Super Mario just as an example.

+5


question: deploy deletes folder inside bucket

I'm trying to use the plugin to deploy my gatbsy project to my s3 bucket, my issue is that I also have another project on the same bucket but on a folder called /blog.
After deploying the main project, it deletes the folder; I've been looking through the plugin options and I'm not sure if there's a way to stop that from happening, thus I'm asking for help here.
My gatbsy-config.js is as basic as it gets:
    {
      resolve: `gatsby-plugin-s3`,
      options: {
        bucketName: bucketName,
        protocol: siteAddress.protocol.slice(0, -1),
        hostname: siteAddress.hostname,
      },
    },

Quick fix is to set removeNonexistentObjects to false in the config. But this means that stale objects will gather over time in your S3 bucket.
Longer term, we'd welcome a PR that adds functionality to selectively exempt objects from deletion via glob patterns.

Duplicate #33


dispatcher, agent: add way to stop worker remotely

There is new field Stop in SessionMessage.
Have no idea if it works.
ping @diogomonica @stevvooe @aaronlehmann

Current coverage is 54.65% (diff: 58.33%)

Merging #1269 into master will decrease coverage by 0.06%

@@             master      #1269   diff @@
==========================================
  Files            78         78
  Lines         12418      12427     +9
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6795       6792     -3
- Misses         4677       4685     +8
- Partials        946        950     +4

Powered by Codecov. Last update 069614f...fc56780

What does it mean to stop? Does this mean leave the cluster?

@stevvooe yes, I think that's what docker does on swarm leave.

Now that we addressed the concerns about repated close(), is this ready to go?

@aaronlehmann This will need to be rebased (even though it merges cleanly), and should use the new (*Agent).stop method.

With that said, should we also have a method on dispatcher that the agent can call to let it know it is shutting down?

@stevvooe maybe a different PR, but we need that for clean removal of nodes from raft (when they leave).

/cc @diogomonica


preview: makes wrong query to versions endpoint

Package version (if known): v6.0.0.dev1
Describe the bug
When clicking preview the page makes a query to the versions endpoint.
Steps to Reproduce

Go to uploads
Click on preview before saving
See the console

Screenshots (if applicable)

Additional context
Might be because if the record has not been published there are no versions available?

After some more thinking... I believe this is not a bug:

We want to display the versions
We gotta query
If not published before, there is no versions (response 404)
Does not throw an exception
UI doesn't fail

We could check if the record is published before doing the request maybe. But not sure if it's worth it, it behaves like any search query without results in the end.

Fixed by PRs related to https://github.com/inveniosoftware/invenio-rdm-records/issues/468

Not happening anymore.


Support for a hard coded hostname for a Marathon app

Feature.

What did you do?
Setup marathon in basic config so that tasks get the following hostname:
marathon-app-id.mycustomdomain.com

What did you expect to see?
I'd like to be able to configure the hostname dynamically or through some config file. I'm not sure if you can do this with the tmpl file, but couldn't find it documented anywhere.
So instead of
marathon-app-id.mycustomdomain.com
I can configure something like
my-custom-name.mycustomdomain.com is an alias for marathon-app-id.mycustomdomain.com
This is similar to the behavior in bamboo in which you can configure an haproxy rule.
What did you see instead?
hostnames are assigned the task id in marathon or if they are in subgroup, a combination of the task id with the subgroup name.
Output of traefik version: (What version of Traefik are you using?)

Version:      v1.5.4
Codename:     cancoillotte
Go version:   go1.9.4
Built:        2018-03-15_01:35:21PM
OS/Arch:      linux/amd64```

What is your environment & configuration (arguments, toml, provider, platform, ...)?
[entryPoints]
    [entryPoints.http]
       address = ":81"

    [entryPoints.dash]
       address = ":8081"

[api]
entrypoint = "dash"
dashboard = true

################################################################
# Mesos/Marathon configuration backend
################################################################

[marathon]
endpoint = "http://marathon.mydomain.com"
watch = true
domain = "mydomain.com"

If applicable, please paste the log output at DEBUG level (--logLevel=DEBUG switch)
(paste your output here)

Ah looks like traefik.frontend.rule=Host:test.traefik.io might be what I'm looking for.

Closing this as traefik.frontend.rule=Host:test.traefik.io works for me


How add more Switch

How can I add two, three or more Switch to the card?thanks.
I found that whatever I did was wrong

You can't. Slider card is only designed to handle one entity per card.
What are you trying to accomplish?


Huawei Game Services

You don't have to create a new pull request if you want to make further additions. If you push the changes to the same branch, they are automatically added to the PR.


Too many casts when if/cond used as a value.

For example, in ambient.gc in level-hint-displayed?
(the-as level-hint (if v1-0
                                   (the-as level-hint (-> v1-0 0 self))
                                   )

We could also revisit what the correct return type for if's without else in the decompiler

possibly related to (event cam-master-active) in https://github.com/water111/jak-project/pull/845


Add a protected shutdown RPC

The node doesn't currently have a "clean" way of getting shut down. This RPC endpoint provides us with one.

Note: once this PR is merged, the bootnodes that are updated to it should always be started with custom rpc-username and rpc-password params; we might also want to randomize at least the password, as suggested by an existing TODO in config.rs.

Are RPC calls made over insecure sockets in clear text?

It's currently simple HTTP authentication, but as long as we don't plan to expose RPC to the outside world, it's fine.

Should we wait for better security enforcements/protocols on RPC protected endpoints before merging this in? It seems to be a significant dos concern

We can postpone this PR for any amount of time we need, as it's small and self-contained. In the meantime, if we need this functionality for any ad-hoc test, we can just cherry-pick the only commit it contains, and I can rebase whenever necessary :+1:.


User Story

User Story
AS AN avid bicycle rider who travels regularly to cities for business
I WANT to be able to find community bike programs  and know the weather conditions in the city
SO THAT I can continue biking safely while traveling

Complete


Playback is clipping when using PipeWire ouput driver

Intervalic clipping during playback when using PipeWire backened. Issue not present when using PulseAudio or ALSA backened. Occurs across output devices (BT or wired headphones). Occurs across multiple encodings, bitrates, and bitdepths.
Musikcube version: 0.98.0 #6a440c69
OS: openSUSE Tumbleweed 5.19.8
pulseaudio: not installed
pulseaudio-utils: 16.1
pipewire/pipewire-pulseaudio: 0.3.58

Added some new settings in the 0.98.1 release to allow the user to adjust PipeWire buffer sizes. They are available in settings >configure plugins > PipeWire IOutput > enter


Ratebypass attribute ?

the link that is generated googlevideo.com/videoplayback?ratebypass comes..
What does it mean ? Like is there a max rate at which a video can be accessed and then it's streaming/downloading link wont come via cURL ?
Would appreciate more info on this
Thanks

Adding 'ratebypass=true' allows YouTube to send data at constant speed (usually is first 40 seconds at max speed, rest at watching speed).The parameter is present both at dash and non dash streams.


Settings app version footer

📲 What
Moves application version information from a settings cell to a footer.
🤔 Why
Design update
🛠 How

Simply adds a new footer view
Removes code debt

👀 See

Regular
Large
Extra extra extra large

♿ Accessibility

[ ] Footer resizes based on font size
[ ] VoiceOver reads the footer information as App version NUMBER (i.e. App version 3.12.0) without any traits

✅ Acceptance criteria

[ ] Tests pass
[ ] App version shows properly in the footer (based on design mocks)

 ⚙ Move 'App version' from a TableViewCell to footer information underneath the 'Rate us in the App Store' TableViewCell


Failed to ctr push with non latest tag

What is the problem you're trying to solve
I've tried to push/pull test for using ctr in my custom registry service.
Even though success to push/pull with latest tag, I failed to push with 'non-latest' tag
(I think ctr doesn't support docker's tag command)
Describe the solution you'd like
Can I change the tag name using 'ctr command' or push it to a 'non-latest' tag?
Additional context
Below are my logs
[root@~:/root] docker images | grep 5001
sds.redii.net/sdspaas/fluent-bit                                  1.2.2                               075001dca2c6        7 months ago        53.2MB
localhost:5001/httpd                                              alpine                              e930b133a978        11 months ago       128MB
localhost:5001/busybox                                            latest                              00950dad8965        2 years ago         12.3MB
[root@~:/root]
[root@~:/root] ctr images push localhost:5001/busybox
ctr: unable to resolve image to manifest: image "localhost:5001/busybox": not found
[root@~:/root] ctr images push localhost:5001/busybox:latest
manifest-sha256:06459888027d8d290b70759e69a46a5032779e78038d7b67b2f98db0d32b70d1: done           |++++++++++++++++++++++++++++++++++++++|
layer-sha256:e3debd4dac47035b84218f66a1792329bbe46a306ac19518712e955308d5aca5:    done           |++++++++++++++++++++++++++++++++++++++|
config-sha256:00950dad8965b32c9a0f4e6d369e848555e0434e2d9c804247b3a04f1e7507e5:   done           |++++++++++++++++++++++++++++++++++++++|
layer-sha256:6d987f6f42797d81a318c40d442369ba3dc124883a0964d40b0c8f4f7561d913:    done           |++++++++++++++++++++++++++++++++++++++|
layer-sha256:dbb0e1305741dc552e11e8a226195b68aeab0f1013c7f2e6e9268b04e6ed2327:    done           |++++++++++++++++++++++++++++++++++++++|
elapsed: 0.1 s                                                                    total:   0.0 B (0.0 B/s)
[root@~:/root]
[root@~:/root] ctr images push localhost:5001/httpd
ctr: unable to resolve image to manifest: image "localhost:5001/httpd": not found
[root@~:/root]
[root@~:/root] ctr images push localhost:5001/httpd:alpine
ctr: unable to resolve image to manifest: image "localhost:5001/httpd:alpine": not found
[root@~:/root]
[root@~:/root]
[root@~:/root]
[root@~:/root] docker push localhost:5001/httpd:alpine
The push refers to repository [localhost:5001/httpd]
e771280fc920: Pushed
1b02fd077f13: Pushed
fb6547044b4e: Pushed
641a07ed2436: Pushed
bcf2f368fe23: Pushed
alpine: digest: sha256:98bbe4bcfebbcf471cb0b32caf757def8f55b7cf4d515a168c90101f2e92d46f size: 1362
[root@~:/root]

thanks for reporting. could you mind to show the result ctr image ls | grep 5001 ? I am not sure that you pulled the image into your local ..... docker doesn't have used containerd to manage image store yet.

thanks for reporting. could you mind to show the result ctr image ls | grep 5001 ? I am not sure that you pulled the image into your local ..... docker doesn't have used containerd to manage image store yet.

Thanks a lot! I didn't know if containerd and docker use different local storage.
My containerd local storage didn't have that image, so it wasn't being pushed.
But I couldn't change the tag with ctr command, so I used the docker client.
Is there any way to change the ctr image tag?

Hi @bluefriday . I think you are using v1.2.x containerd version.

COMMANDS:
   check       check that an image has all content available locally
   export      export images
   import      import images
   list, ls    list images known to containerd
   pull        pull an image from a remote
   push        push an image to a remote
   remove, rm  remove one or more images by reference
   tag         tag an image <================================== here
   label       set and clear labels for an image

OPTIONS:
   --help, -h  show help

Great. Thanks for your reply for me.
I'll close this issue.


Move client declaration information to component

Before, conditional logic that determined which set of content was rendered for
a given application (i.e means-tested vs non-means-tested) resided in the view.
This made it difficult to test in isolation. While it is possible to write view
specs, their use is not widespread (and we have none in our test suite).
Currently we lean on integration tests (e.g request specs or cucumber features)
to assert that given content is rendered. This is useful, but they are
expensive —which prohibits unit style testing.
This introduces view_component as an explicit dependency (we use it implicitly
already through the govuk-components gem), and refactors the provider client
declaration confirmation page so that it renders a component.
This component encapsulates the logic for rendering means-tested and
non-means-tested specific content.
For now, i18n-tasks.yml excludes components files. I spent a couple of hours
trying to piece together a pattern mapper so that i18n-tasks didn't categorise
the keys as missing, but it was turning into a time-sink.
Given we have config.raise_on_missing_translations = true in development and
test, and the components are thoroughly unit-tested, I don't think this is a
major issue.

Closing because I haven't found time to compelling advocate that team members discuss the proposed change in the forum of this PR


API Name in second column should get trimmed based on column width and not be limited to 140 characters.

Is it possible to implement it using CSS only? I see the possibility to do it by JS.

@for-singer Any solution would do- js or css. Ideally the length of text shown should be dependent on browser size. So even if at runtime the browser size changes, it should adapt to the new size.
Let me know if you would like to take it up. I'll assign it to you.

Yes, please.

Assigned to @for-singer . Take the update before you start working.

@AnujaK I made solution using js in the browser's console. So now I need to get the right place to paste it to be handled by such events like render, element change size and "#tree" vertical scroll appears or disappears. I think that maybe it can be done in the 'tree-view.js' file. Could you explain me in details where can i paste it?

@for-singer  Logically speaking, yes it should be part of tree-view. Try adding it and test it thoroughly before you send a pull request.

Fixed with PR #346


subcommand hugo list aliases

It would be nice to have an overview of all aliases, which are generated by hugo.


[stable/openebs]: fix README image repository typo

Signed-off-by: prateekpandey14<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

NO
What this PR does / why we need it:
PR fixes READ me typo image.registry --> image.repository
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test


Fails when expected result should be a Float

We expect the area under the curve x^2 on [1,3] to be 27/3 - 1/3 = 26/3 ~= 8.667.
Performing this operation with metadelta, however, leads to an integer answer of 8.
metadelta.areaUnder('x^2', { start: 1, finish: 3})
8

This problem seems to be caused by the parsing of the lower limit as an integer rather than as a float on line 59 of calculus.js.
A similar problem occurs when we attempt to find non-integer zeroes of a curve. Given the function x^2-3, we expect the zeroes [-sqrt(3), sqrt(3)] ~= [-1.73, 1.73], but are instead returned with [3, -3]. This too appears to be because of integer parsing.
Is there a reason that strings are parsed as integers rather than floats, or can this be fixed?

Good catch! I'll get on this soon!


Fix broken link

Hello,
This simple PR Fixs the broken link #choosing-the-correct-credential-type-automatically.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #423   +/-   ##
=====================================
  Coverage      95%    95%
=====================================
  Files          15     15
  Lines         981    981
  Branches      217    217
=====================================
  Hits          932    932
  Misses         49     49

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 f105d3a...2aaccff. Read the comment docs.


[base-ui][slider] Slider is draggable beyond bounds (touch)

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://mui.com/joy-ui/react-slider/
Steps:

open example
scroll to first example
open dev tools with touch
drag ouside the bounds of root

Current behavior 😯
On touch devices the dragging of the slider works far beyond the root element.
Screenshot: the gaps either drag the upper or lower slider

If an interactive element is in the gap, the behavior is as expected

Screencast
https://github.com/mui/material-ui/assets/1148334/131104b7-b517-4da1-9536-b173e56b0a06
https://github.com/mui/material-ui/assets/1148334/d22467f1-6572-472f-a364-3b34f1f2a027
Expected behavior 🤔
I expect to be able do click on an area outside the slider bounds without triggering the slider itself, so that I can perform actions like scrolling.
Context 🔦
I have a page with several slider stacked in a box. I want to scroll the page on mobile, but it is impossible because each slider is somehow blocking me and triggering the slider instead of scrolling.
This breaks my UI/UX.
Your environment 🌎

npx @mui/envinfo

  System:
    OS: Windows 10 10.0.22621
  Binaries:
    Node: 18.5.0 - C:\Program Files\nodejs\node.EXE
    @emotion/styled: 11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.17
    @mui/core-downloads-tracker:  5.14.12
    @mui/icons-material: 5.14.11 => 5.14.11
    @mui/joy: 5.0.0-beta.9 => 5.0.0-beta.9
    @mui/material: ^5.14.11 => 5.14.11
    @mui/private-theming:  5.14.12
    @mui/styled-engine:  5.14.12
    @mui/system:  5.14.12
    @mui/types:  7.2.5
    @mui/utils:  5.14.12
    @types/react: ^18.2.23 => 18.2.23
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: ^5.2.2 => 5.2.2

It looks like the issue comes from useSlider via base-ui.
It can be reproduced here: https://mui.com/base-ui/react-slider/

I notice that the trigger area to capture dragging/touch expands to the box that encapsulates the slider.

Yes, the area to click is a bit larger than the track and thumb to make it easier to aim.
Perhaps we can make it a bit smaller, but that's up to Joy UI maintainers (cc @siriwatknp).

@michaldudak @siriwatknp we would like to pick this up.

Let's discuss the desired behavior with @siriwatknp first.

Here's another reason why this is currently a problem:
I have a colorpicker and when I close it, the slider get's triggered.  (tested in dev-tools, so I'm not sure if this even applies on a real mobile device)
https://github.com/mui/material-ui/assets/1148334/c7431b52-b8f8-4863-a635-567ef6bb9008

Have you tested the experience on a real mobile device to see if the scenario is same there as well?

Yeah! There is some touch target documentation out there, but to sum it up, for small area components such as a slider's thumb, I think between 42 and 48px is a healthy target.

Material Design's touch target docs
Android Accessibility touch target size docs
NN/g touch target docs

One thing that I think it'd be helpful there, though, is having the focus treatment (potentially on mobile only) fill the entire touch space; otherwise, it's indeed confusing to understand why the slider works if you're "apparently" not touching it. 🤔

Yeah! There is some touch target documentation out there, but to sum it up, for small area components such as a slider's thumb, I think between 42 and 48px is a healthy target.

Material Design's touch target docs
Android Accessibility touch target size docs
NN/g touch target docs

One thing that I think it'd be helpful there, though, is having the focus treatment (potentially on mobile only) fill the entire touch space; otherwise, it's indeed confusing to understand why the slider works if you're "apparently" not touching it. 🤔

The current touch area is 42px. I'd wait for @zanivan's comment. If we are agreed to go with 42px, I will close this issue.

I think Google/Lighhouse expects 48px based on the Android guidelines: https://support.google.com/accessibility/android/answer/7101858?hl=en
There was a very detailed discussion on this: https://github.com/GoogleChrome/lighthouse/issues/4358
This is also mentioned in the material-design specs: https://m2.material.io/design/usability/accessibility.html#assistive-technology

Have you tested the experience on a real mobile device to see if the scenario is same there as well?

I tested this and it is noticeable but not as crucial since iOS seems to block certain touches when a scroll happens. I haen't tested in on an Android though.

I did some further testing on iOS.
Go to the "track" section of the docs. There seems to be a difference in the slider being focused. There is definitely a certain annoyance and potential danger in making unwanted adjustments while scrolling.
Bit overall on a real device is seems a "a lot" better than on the dev tools or iOS simulator.


dubbo consumer cannot stop reconnect to the old provider after provider changed ip in docker

[√] I have searched the issues of this repository and believe that this is not a duplicate.
[√] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: <IP_ADDRESS>
Operating System version: docker alpine in k8s
Java version: 1.8
register: nacos 1.1.3

Steps to reproduce this issue

Start module A and module B， A depends on B, the register is nacos. Now A invoke B's dubbo interface correct.
Restart module B, because in k8s and module B’s IP address is changed.
Now A invoke B correct, but A begin reconnect to the old provider B and can not stop. The logs as below:

Pls. provide [GitHub address] to reproduce this issue.
What do you expected from the above steps？
stop reconnect to the old provider
What actually happens?
Actual Result is cannot stop reconnect to the old provider
If there is an exception, please attach the exception trace:
[ERROR] 2020-03-31 22:16:19.303 [] [] [dubbo-client-idleCheck-thread-1] ReconnectTimerTask.doTask[51]: [DUBBO] Fail to connect to HeaderExchangeClient [channel=org.apache.dubbo.remoting.transport.netty4.NettyClient [<IP_ADDRESS>:0 -> /<IP_ADDRESS>:20881]], dubbo version: <IP_ADDRESS>, current host: <IP_ADDRESS>
org.apache.dubbo.remoting.RemotingException: client(url: dubbo://<IP_ADDRESS>:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=mall-open&bind.ip=<IP_ADDRESS>&bind.port=20881&check=false&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&generic=true&group=mall-goods&heartbeat=60000&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=6&qos.enable=false&register.ip=<IP_ADDRESS>&release=<IP_ADDRESS>&remote.application=mall-goods&revision=2.2.0.RELEASE&side=consumer&sticky=false&timeout=30000&timestamp=1585642448627&version=1.0.0) failed to connect to server /<IP_ADDRESS>:20881 client-side timeout 3000ms (elapsed: 3000ms) from netty client <IP_ADDRESS> using dubbo version <IP_ADDRESS>
at org.apache.dubbo.remoting.transport.netty4.NettyClient.doConnect(NettyClient.java:166)
at org.apache.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:190)
at org.apache.dubbo.remoting.transport.AbstractClient.reconnect(AbstractClient.java:246)
at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeClient.reconnect(HeaderExchangeClient.java:155)
at org.apache.dubbo.remoting.exchange.support.header.ReconnectTimerTask.doTask(ReconnectTimerTask.java:49)
at org.apache.dubbo.remoting.exchange.support.header.AbstractTimerTask.run(AbstractTimerTask.java:87)
at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:648)
at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:727)
at org.apache.dubbo.common.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:449)
at java.lang.Thread.run(Thread.java:748)
[ERROR] 2020-03-31 22:17:23.303 [] [] [dubbo-client-idleCheck-thread-1] ReconnectTimerTask.doTask[51]: [DUBBO] Fail to connect to HeaderExchangeClient [channel=org.apache.dubbo.remoting.transport.netty4.NettyClient [<IP_ADDRESS>:0 -> /<IP_ADDRESS>:20881]], dubbo version: <IP_ADDRESS>, current host: <IP_ADDRESS>
org.apache.dubbo.remoting.RemotingException: client(url: dubbo://<IP_ADDRESS>:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=mall-open&bind.ip=<IP_ADDRESS>&bind.port=20881&check=false&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&generic=true&group=mall-goods&heartbeat=60000&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=6&qos.enable=false&register.ip=<IP_ADDRESS>&release=<IP_ADDRESS>&remote.application=mall-goods&revision=2.2.0.RELEASE&side=consumer&sticky=false&timeout=30000&timestamp=1585642448627&version=1.0.0) failed to connect to server /<IP_ADDRESS>:20881 client-side timeout 3000ms (elapsed: 3000ms) from netty client <IP_ADDRESS> using dubbo version <IP_ADDRESS>
at org.apache.dubbo.remoting.transport.netty4.NettyClient.doConnect(NettyClient.java:166)
at org.apache.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:190)
at org.apache.dubbo.remoting.transport.AbstractClient.reconnect(AbstractClient.java:246)
at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeClient.reconnect(HeaderExchangeClient.java:155)
at org.apache.dubbo.remoting.exchange.support.header.ReconnectTimerTask.doTask(ReconnectTimerTask.java:49)
at org.apache.dubbo.remoting.exchange.support.header.AbstractTimerTask.run(AbstractTimerTask.java:87)
at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:648)
at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:727)
at org.apache.dubbo.common.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:449)
at java.lang.Thread.run(Thread.java:748)
[ERROR] 2020-03-31 22:18:27.303 [] [] [dubbo-client-idleCheck-thread-1] ReconnectTimerTask.doTask[51]: [DUBBO] Fail to connect to HeaderExchangeClient [channel=org.apache.dubbo.remoting.transport.netty4.NettyClient [<IP_ADDRESS>:0 -> /<IP_ADDRESS>:20881]], dubbo version: <IP_ADDRESS>, current host: <IP_ADDRESS>
org.apache.dubbo.remoting.RemotingException: client(url: dubbo://<IP_ADDRESS>:20881/com.alibaba.cloud.dubbo.service.DubboMetadataService?anyhost=true&application=mall-open&bind.ip=<IP_ADDRESS>&bind.port=20881&check=false&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&generic=true&group=mall-goods&heartbeat=60000&interface=com.alibaba.cloud.dubbo.service.DubboMetadataService&lazy=false&methods=getAllServiceKeys,getServiceRestMetadata,getExportedURLs,getAllExportedURLs&pid=6&qos.enable=false&register.ip=<IP_ADDRESS>&release=<IP_ADDRESS>&remote.application=mall-goods&revision=2.2.0.RELEASE&side=consumer&sticky=false&timeout=30000&timestamp=1585642448627&version=1.0.0) failed to connect to server /<IP_ADDRESS>:20881 client-side timeout 3000ms (elapsed: 3000ms) from netty client <IP_ADDRESS> using dubbo version <IP_ADDRESS>
at org.apache.dubbo.remoting.transport.netty4.NettyClient.doConnect(NettyClient.java:166)
at org.apache.dubbo.remoting.transport.AbstractClient.connect(AbstractClient.java:190)
at org.apache.dubbo.remoting.transport.AbstractClient.reconnect(AbstractClient.java:246)
at org.apache.dubbo.remoting.exchange.support.header.HeaderExchangeClient.reconnect(HeaderExchangeClient.java:155)
at org.apache.dubbo.remoting.exchange.support.header.ReconnectTimerTask.doTask(ReconnectTimerTask.java:49)
at org.apache.dubbo.remoting.exchange.support.header.AbstractTimerTask.run(AbstractTimerTask.java:87)
at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:648)
at org.apache.dubbo.common.timer.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:727)
at org.apache.dubbo.common.timer.HashedWheelTimer$Worker.run(HashedWheelTimer.java:449)
at java.lang.Thread.run(Thread.java:748)

Perhaps you can check your nacos properties of live times. It seems as if the old version provider url is still in nacos.

After check my nacos client and server properties，I am using the default properties configuration， and the client as blow：

When the reconnect happens, I had tried to restart the nacos server, but the reconnect stills can not stop. So my dubbo consumer continues trying to reconnect the old provider ip for several hours, and the exception logs is continuing output.  Is it normally

What I said nacos properties is in you nacos server.
Can you reproduce this issue and check nacos on its web management (http://xxxxxx:8848/nacos/) ?
You can notice the Healthy Instance Count in ServiceManagement - Service List.

I had checked the nacos web pannel, the old provider was not show in the service list any more,  and the Healthy Instance Count is '1' which is the new provider

What about the Subscribers section is correct or not?

Just now I try to reproduce this issue in my computer, I found the module A will still try to reconnect the old version B before this new version's url notified by nacos and old version healthy checkout timeout. And this may takes about two minutes before stopping reconnecting to the old version provider. After that everything returns to normal.
@majjfootman Did module A still try to reconnect old provider B after serveral minutes ?

Moudule A still try to reconnect old provider B after serveral minutes, even after serveral  hours.
May be my config is not correct, or the nacos server version is not  compatibility? My nacos server version is 1.1.3, and I am using the spring-cloud-alibaba 2.2.0.RELEASE.
Can you share your module's version or configuration, Thank you very much

Dubbo version: <IP_ADDRESS>
Nacos version: 1.1.4
Nacos Server version: 1.1.4

I am just dirctly use dubbo without spring-cloud-alibaba.
        <!-- dubbo -->
        <dependency>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo-spring-boot-starter</artifactId>
            <version>${dubbo-version}</version>
        </dependency>

        <dependency>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo-registry-nacos</artifactId>
            <version>${dubbo-version}</version>
            <exclusions>
                <exclusion>
                    <artifactId>log4j</artifactId>
                    <groupId>log4j</groupId>
                </exclusion>
                <exclusion>
                    <artifactId>dubbo-common</artifactId>
                    <groupId>org.apache.dubbo</groupId>
                </exclusion>
            </exclusions>
        </dependency>

        <dependency>
            <groupId>com.alibaba.nacos</groupId>
            <artifactId>nacos-client</artifactId>
            <version>${nacos-version}</version>
        </dependency>

properties is below
dubbo:
  scan:
    base-packages: com.xxxxxx
  protocol:
    name: dubbo
    port: -1
  registry:
    address: nacos://<IP_ADDRESS>:8848
  application:
    name: xxxxxx
  consumer:
    check: false

Just now I notice your error message, the main error is client-side timeout. Perhaps this is the main reason because in general if a server shutdown the client reconnect it will come out Connection refused owing to closed port. But in k8s if a node is totally closed, the ip cannot be connect no longer and the result may changed while the request is loopback in the k8s network or even turned to outside network. This maybe the issue of doClient function in NettyClient.

Thank you for your help.
I run my application at my local environment and reproduce, the connection exception type changes but still continue reconnect. Then I use your dirctly  maven dependency instand of spring cloud alibaba, it was not reconnecting any more.  I will try this in k8s later.
May be the continues reconnection is the issue of spring cloud alibaba.

的确是重启provider会这样,我在consumer上调用几次，发现就在不停的连接，注册中心返回的数据查了下，没有原来的ip数据。我的docker用的是swarm网络，容器重启后ip会变，计算机名不变。


The total_memory_bytes of cn displayed in meta is not the cn config total_memory_bytes

Describe the bug
https://github.com/risingwavelabs/risingwave/blob/19f4254921c66bf83b9ceb2ba6f5a9d5f31c939a/src/rpc_client/src/meta_client.rs#L253
It uses the cn host memory limit
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response

Ping?

It's means to aim at getting the host resources. What will this information used for? Anyway we can tell users it's host resources instead of system config? cc @yezizp2012 @zwang28

It's means to aim at getting the host resources. What will this information used for?

system_memory_available_bytes() is the one related to OOM, while total_memory_bytes of cn can be set arbitrarily.


Login happy path

Use Case 1: Happy path login

Given As a signed up user
When I enter my user name and password
Then I will be signed into my account and on the dashboard page

Expected: That the user can log in and the dashboard is accessible

This ticket is done, marked closed with PR https://github.com/timeades/Phrasee_tech_test/pull/7


c4test frequently crashes with "malloc: Region cookie corrupted" when calling EVP_MD_CTX_new()

I'm exploring the suitability of using the hatrack portion of libcon4m for my own project(s). I'm running into some problems there, but before I go further into analyzing my own code, I want to report a crash I'm seeing in c4test.
When I run c4test it frequently—but not always—crashes in the sha_init() function when it calls EVP_MD_CTX_new(). Specifically, I'm referring to line 55 in
https://github.com/crashappsec/libcon4m/blob/9fdd12cccd636b8ec5a8c1a2110997832ddced4a/src/con4m/crypto/sha.c#L33-L59
I've built libcon4m on an arm64 Mac. Unfortunately (or not), macOS does not (seem to) come with a system -lcrypto. I'm using OpenSSL 3.2.1 from MacPorts. If you've built and run c4test on a Mac, which crypto library are you linking against and how did you install it? And are you able to run c4test repeatedly with no malloc errors?

Sorry, just saw this. I'm on an arm mac too, but linking to an OpenSSL I built. I can share the .a file directly if that's helpful?

It turns out I could not reproduce this problem in Apple's Terminal app.  I can reproduce it reliably in VSCode's terminal. Comparing environment variables, I found that VSCode's terminal's environment defines a suspicious-looking MallocNanoZone=0. I found that setting MallocNanoZone=0 in the Terminal app environment caused c4test to crash, just like it does in VSCode's terminal. Give it a try.
I could not find much information on the MallocNanoZone environment variable, but it seems to be used to help debug memory allocation errors. I wonder if this indicates some kind of malloc bug in OpenSSL? I'm tempted to file an issue with that project, or debug this problem myself. I don't suppose you might have any insight yourself?

Ah. That environment variable forcibly changes the system library's memory allocator. I don't know how it does it, but I would suspect it essentially does muck with redirecting function calls. That would be fine for using hatrack w/o con4m, but since con4m is basically adding a garbage collection layer, it's not too much of a surprise there'd be some conflict, depending on how openssl determines how to redirect malloc.
If it's an issue to disable nanomalloc, I can try to spend some time on it over the weekend, as I'm sure I could accomidate that but I don't see why one would need to use nanomalloc either :)

Hi @viega. The issue is just running c4test in the VSCode terminal. At this point it sounds like I won't be using the garbage collection facility, so I'll just close this issue now.
Thanks.


update ci-config to use os-climate quay repo

ssia

Repo created on quay:
https://quay.io/repository/os-climate/aicoe-osc-demo


[ios_platform_images] Provide a Swift example for plugin

Use case

I am trying to build a simple flutter app and a iOS widget. Between them, I want to use the some images. Since I am planning to use the images in Android as well, I put my images under flutter assets folder. When I try to use the images in iOS, I came cross this plugin, but I couldn't make it work in swift. I tried to write it like:
let image = UIImage.flutterImage(withName: "assets/foo.png")

But Xcode complains it doesn't have a flutterImage method.
Type "UIImage" has no member "flutterImage"

Could you help me with that? It's a noob questions, but I am blocked by this for many hours. Thanks in advance.
Proposal

@FelixLou
Does the package example help ?

Thank you so much for the quick response! The example is using iOS image in Flutter. I need the opposite(using Flutter images in Swift), as my images are in Flutter for sharing with Android.

Thanks for the update.
Keeping it open and labeling as documentation issue.

Thank you, do you have a timeline when are we able to get the example? Right now, I am duplicating these images as a temp solution(I know it's bad), which increasing the app size a lot...

I am making a demo for using Flutter in an existing iOS native App written in Swift. What I do is list below:

Run flutter build ios-framework in the flutter project directory.
Drag GeneratedPluginRegistrant.h & .m into the iOS project.
Add GeneratedPluginRegistrant.register(with: flutterEngine) where the flutterEngine is running.
Import ios_platform_images to where I need it.

let image = UIImage.flutterImage(withName: "assets/foo.png")

Then this line will work and return an image if existed.

Hi, I have the same problem.
How do you import the library in the Swift file?

@SilentJohn Thanks so much for the reply! I found my problem is actually I couldn't find the lib in my widget extension. I have no problems using the lib in the main app.
The podfile looks like this:
target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

Then I found if I put add the following lines in the podfile, the widget will also find this lib:
target 'widgetExtension' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

But then when I try to build the app, it will complain some lib are not available for extension.
    /Users/jiabin.lu/fun/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher_ios-6.0.13/ios/Classes/FLTURLLauncherPlugin.m:92:47: error: 'sharedApplication' is unavailable: not available on iOS (App Extension) - Use view controller based solutions where appropriate instead.
      UIApplication *application = [UIApplication sharedApplication];

Any suggestions on how to use flutter dependencies in iOS widget?

I'm facing the same issue
What is the correct way to import this ios_platform_images in swift ?
Thanks

@stuartmorgan could you help with the correct usage of this plugin?


[Issue]:  Any one has the code to visualize the graphrag. Other then using Plotly module?

Describe the issue
No response
Steps to reproduce
No response
GraphRAG Config Used
No response
Logs and screenshots
No response
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

A couple of suggestions:

When running your index, you can set GRAPHRAG_SNAPSHOT_GRAPHML=True to output graphml files that can be visualized in a desktop tool like Gephi.
We have config for node2vec and umap, which will embed the graph and then do dimensionality reduction so each node is assigned an x/y coordinate in the output. This is useful for plotting programs, and will locate the nodes near their community clusters.

Moving to viz discussion: https://github.com/microsoft/graphrag/discussions/697


The VS Code Speech extension should have a manual mode (disable end-of-speech detection)

The VS Code Speech end-of-speech detection is really frustrating for me, because it often assumes I'm done talking when I'm not.
Instead of being super fancy, can I just have the option to press a button when I'm done?
E.g. Command-u to start and Command-u again to stop?

you can set accessibility.voice.speechTimeout to 0 to disable that.


Find n'th Smallest and Largest Element in an Unsorted Array

Find the n’th  Smallest/Largest Element in an Unsorted Array. Given that all array elements are distinct.
Input: array[ ] = {7, 10, 4, 3, 20, 15}, n = 4
Output: 4th-smallest= 10
4th -largest  = 7

Anjali Thombare
I would like to work on this issue

I want to work on this issue.
Srushti Kage
UCE2022531
FY Comp

@Anjali2312-Thombare
@srushtikage   You have already been assigned one issue. You can work only on one issue at a time .


[BUG] Managed Identities are swapped between slots

Library name and version
Azure.Identity 1.12.0
Describe the bug
First, sorry if this isn't the correct place for this issue, but I didn't find a "general Azure repository" in the 2k+ repositories. The potential bug is however made visible using the dotnet sdk, but I hardly think that's where the actual potential bug is happening.
When swapping slots on an Azure WebSite AppService where both the production and staging slot are using Managed Identity, the actual identities are also swapped. Contrary to what the documentation says:

Settings that aren't swapped:
...

Managed identities and related settings

We deployed a simple API with just one endpoint /whoami that uses the Azure SDK to fetch the claims for the current identity and displays that along side a couple of settings I'll explain later. This is from the production slot prior to a swap:

The sub matches the Object (principal) id in the portal for the production slot:

The appDisplayName is fetched from the claim app_displayname returned with DefaultAzureCredential method GetTokenAsync(...).
However, if we perform a swap the production slot looks like this after the swap has completed:

...and the staging /whoamiendpoint shows the production identity as well.
The identity stays that way until we do a restart of the App Service, then it reverts back to using the correct managed identity again.
We also return value of "settings" and this is just trying to read a setting named foobar. On the screenshots above, it only exists in the appsettings.json file, but what we've found is that if we add an Environment Variable setting in the staging slot and mark it "Deployment slot setting", then the identities is NOT being swapped between the slots (as per the documentation).
I don't think it matters if we read the setting in our /whoami endpoint, I think it's enough to just have a dummy environment variable in the Environment Variable settings on any slot...
So to summarize:

When swapping slots without any Environment variables marked "Deployment slot setting" everything is swapped, including the Managed Identities.
When swapping slots with at least one Environment variables marked "Deployment slot setting" the Managed Identities are not swapped.

Expected behavior
Managed Identities should not be swapped between slots.
Actual behavior
Managed Identities are swapped between slots when no Environment Variable marked "Deployment slot setting" exists.
Reproduction Steps

Create a WebSite AppService in Azure.
Create a slot.
Add identities to both slots
Deploy a minimal API to the slots with one endpoint using the following code:

var credential = new DefaultAzureCredential();
var scopes = new List<string> { "https://graph.microsoft.com/.default" };
var token = await credential.GetTokenAsync(new Azure.Core.TokenRequestContext(scopes.ToArray()));
var handler = new JwtSecurityTokenHandler();
var jsonToken = handler.ReadToken(token.Token) as JwtSecurityToken;
var appid = jsonToken!.Claims.First(c => c.Type == "appid").Value;
var sub = jsonToken.Claims.First(c => c.Type == "sub").Value;
var value = configuration.GetValue<string>("foobar");

var appDisplayName = jsonToken.Claims.First(c => c.Type == "app_displayname").Value;

return Results.Ok(new { appid, sub, settings = value, appDisplayName, claims = jsonToken.Claims });

Check the appid, sub and other settings from the /whoami endpoints of both slots
Perform a swap

Environment
Azure AppService, .NET8

Thank you for your response. This has already been reported on the Microsoft Q&A site here for more than a month ago without any response what so ever. Unfortunately this is my experience with that forum, hence coming here first.
I guess I'll have to open an Azure support request as well, but that will hide the issue from everyone else that are/will be affected by this.


Rollback: How do I use the rollback

Hi! I want to rollback a helmreleases.  what shoud i do?
The YAML file I defined：
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: nginx-fluxcd
spec:
  interval: 5m
  chart:
    spec:
      chart: nginx
      version: '>=2.0.0 <5.0.0'
      sourceRef:
        kind: HelmRepository
        name: helmrepository-sample
      interval: 1m
  rollback:
    cleanupOnFail: true

And then I excute : kubectl apply  this yaml, but I don't see any change. my helmrelease don't rollback.
Please tell me next I need to do, thank you!

You need to configure the appropriate remediation strategies, as documented here: https://fluxcd.io/docs/components/helm/helmreleases/#configuring-failure-remediation.
However, because the release is in a failed state now, once you have made those configuration changes you need to manually roll it back one more time using helm rollback to kick off the new configurations.


updated images to current version

Rebase and remove conflicts.
New version of RancherOS is already included in Thorsten's PR. Please remove this change.


Add Bio feature on profile

Description
Currently, the profile only contain name, email and DP. I want to add a new feature of bio which user can display and edit anytime according to his/her need.
Screenshots
No response
Additional information
No response

Description
Currently, the profile only contain name, email and DP. I want to add a new feature of bio which user can display and edit anytime according to his/her need.
Screenshots
No response
Additional information
No response

Hi @Palakkgoyal this issue already exists, please either claim the original issue or wait for it to be inactive and close this as duplicate issue.
Thanks


Query parameters to static pages parsed incorrectly.

Before filing this issue, please ensure you're using the latest CLI by running swa --version and comparing to the latest version on npm.
Are you accessing the CLI from the default port :4280 ?

[ ] No, I am using a different port number (--port) and accessing the CLI from that port
[x] Yes, I am accessing the CLI from port :4280

Describe the bug
Using swa CLI 0.8.1, in local testing, query parameters in a static page request seem to get parsed incorrectly. A request for a page like http://localhost:4280/search/?query=foo is interpreted as a request for page /search/query=foo. Similarly, a request for /search?query=foo is interpreted as a request for page /searchquery=foo. (The page in question has javascript which accesses the query parameters.)
Rolling back to CLI version 0.8.0 restored correct behavior.
To Reproduce
Steps to reproduce the behavior:

Run any SWA app with static pages locally.
Visit a page in the browser.
Append any query parameters to the URL and try again.
Note the 404 error with text referencing an incorrect path.

Expected behavior
Adding query parameters should not affect the requested page path.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 20.04.3 (WSL)
Browser: Firefox on Windows host

Thank you for opening this issue. This should be fixed by PR #338.

FYI, this is also a duplicate of #346


Fixing gif related issues

Overview
For some odd reason the file name for gifs had the manim version at the end, which led to a
The file path\of\file.gif does not exist error because file_ops.py didn't know that that was done.
I have removed that addition of the version name , alternatively we could add the version name in to preview as well, that's a matter of preference I guess.
Addendum
Apparently brew install ffmpeg installs ffplay as well so we aren't adding anything additional anyway.
Ignore the part where I say that in the commit message for file_ops.py

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

So, the gif paths must have the version? 🤔

So, the gif paths must have the version? 🤔

No, they don't have to. That's how it was, and the CI just checks that it hasn't changed. I've always found it odd that gif files had a different naming convention as other output files, and think it makes sense to standardize the naming. You'd just have to modify the control data in the tests so that they pass.

Whoops, I just made changes to make the tests happy 😓
Should, I revert?

Something doesn't feel right in the logs.
AssertionError: gif file not found at
"/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pytest-of-runner/pytest-0/popen-gw1/test_gif_format_output0/videos/simple_scenes/480p15/SquareToCircle_ManimCE_v0.14.0.gif"
117
E       assert False
118
E        +  where False = <bound method Path.exists of PosixPath('/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pytest-of-runner/pytest-0/popen-gw1/test_gif_format_output0/videos/simple_scenes/480p15/SquareToCircle_ManimCE_v0.14.0.gif')>()
119
E        +    where <bound method Path.exists of PosixPath('/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pytest-of-runner/pytest-0/popen-gw1/test_gif_format_output0/videos/simple_scenes/480p15/SquareToCircle_ManimCE_v0.14.0.gif')> = PosixPath('/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pytest-of-runner/pytest-0/popen-gw1/test_gif_format_output0/videos/simple_scenes/480p15/SquareToCircle_ManimCE_v0.14.0.gif').exists

The paths are correct and they do have the extension so why does it say not found?

Right so you're saying that the version number should retain?

Right so you're saying that the version number should retain?

I think that would be at least consistent with the decision made in #984. We can ask in the community whether we should keep the names like that at all, but for this PR the file output behavior should be kept as-is. :-)

I don't know where things broke.
I will close this and open a new PR.
Sorry for the mess.


not compatible with pixi.js-legacy

Filters are not compatible with pixi.js-legacy when using in TypeScript.
Steps to Reproduce
install modules:
npm install typescript
npm install pixi.js-legacy
npm install @pixi/filter-glow

create Test.ts:
import * as PIXI from 'pixi.js-legacy';
import { GlowFilter } from '@pixi/filter-glow';

export class Test {
    constructor() {
        const app = new PIXI.Application();
        const glowFilter = new GlowFilter();
    }
}

Compile:
node_modules\.bin\tsc Test.ts
...
Found 41 errors.

The issue is caused by the GlowFilter referencing pixi.js typings here:
https://github.com/pixijs/pixi-filters/blob/master/filters/glow/types.d.ts#L1
Both pixi.js-legacy.d.ts and pixi.js.d.ts are loaded, resulting in duplicate identifier errors.

Workaround is to edit<EMAIL_ADDRESS>and change "pixi.js" to "pixi.js-legacy" but it will be undo-ed when updating the library.

You’re right! Good one.
There’s good news and bad news. Good news is that pixi is moving to typescript which will eliminate this issue by having low level imports of package types (eg, import {Filter} from ‘@pixi/core’) eliminating the type confusion/duplication. This will be ready in the next release.
The bad news is that, I’m not sure when that’ll be ready and we can fix this issue. Also, I don’t know if there’s a decent workaround that I can implement now. One idea is: Instead of using pixi.js-legacy, you could use http://pixijs.io/customize to create your own bundle plus add pixi.js. That should not create the type confusion. I’ll see if I can put an example together. Open to suggestions?

there are other issues with pixi.js + typescript such as:

pixi customize has issues with typescript: https://github.com/pixijs/customize/issues/8
@pixi packages don't have typings: https://github.com/pixijs/pixi.js/issues/6016
Maybe it is just better to wait the next release...

Agreed, thanks for reporting the issue. This hopefully should get squared soon

Any update to this one?

5.4.0 release of pixi will have package typings. We are just working out those bits now. Close!

Still an issue, will get resolved soon with next PixiJS release.

This should be fixed now with PixiJS v6 and Filters v4. We introduced package typings which means that we no longer reference types in pixi.js so this should be compatible with legacy.


[GIT PULL] man/io_uring_buf_ring_cq_advance.3: correct word spelling

Correct word spelling for io_uring_buf_ring_cq_advance.3 man page.

git request-pull output:
The following changes since commit 9e4190aed43f25b2986155a2f6019fc2fc89920f:

  man/io_uring_register_{buffers,files}: Kill trailing whitespaces (2023-03-07 13:54:54 -0700)

are available in the Git repository at:

  https://github.com/chimaoshu/liburing master

for you to fetch changes up to a3a8289665437e9ac741439155baf72f402692d5:

  [GIT PULL] man/io_uring_buf_ring_cq_advance.3: correct word spelling (2023-03-10 00:09:30 +0800)

----------------------------------------------------------------
chimaoshu (1):
      [GIT PULL] man/io_uring_buf_ring_cq_advance.3: correct word spelling

 man/io_uring_buf_ring_cq_advance.3 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Click to show/hide pull request guidelines
Pull Request Guidelines

To make everyone easily filter pull request from the email
notification, use [GIT PULL] as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

Follow the commit message format rules below.
Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

Commit message format rules:

The first line is title (don't be more than 72 chars if possible).
Then an empty line.
Then a description (may be omitted for truly trivial changes).
Then an empty line again (if it has a description).
Then a Signed-off-by tag with your real name and email. For example:

Signed-off-by: Foo Bar<EMAIL_ADDRESS>
The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).
Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes tag with the issue
URL.
Don't use GitHub anonymous email like this as the commit author:
<EMAIL_ADDRESS>
Use a real email address!
Commit message example:
src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the
syscall instead of by posting an internal timeout. This was done
to be both more efficient, but also to enable multi-threaded use
the wait side. If we touch the SQ state by flushing it, that isn't
safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402
Signed-off-by: Jens Axboe<EMAIL_ADDRESS>

By submitting this pull request, I acknowledge that:

I have followed the above pull request guidelines.
I have the rights to submit this work under the same license.
I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).

Looks like the spelling correction is on io_uring_cq_advance, not actually io_uring_buf_ring_cq_advance as mentioned. Not a huge deal though or worth respinning for.


_type mangling on record after #update_index

I am using Mongoid as my ODM.   I am also using single collection inheritance.  Tire wants to put all of my sub classes into the same elastic search type.
Example:
I have a class type of Foo,
When I have a sub class of Bar,  tire wants to put all 'bars'  in elastic search as 'foos'.
I noticed a method named .document_type, which will allow me to change what elastic search '_type'  I want.    In my 'Bar' model I do this:
document_type 'bar'

If I call '#update_index' on my bar model, it will set the actual _type field on my mongoid instance to 'bar'.  It should be 'Foo::Bar'.   If I save my model afterwards to the database, it will save the _type field as 'bar'.  Is this the intended behavior of '.document_type' ?

Hi, it's a known bug, there are several issues opened for that: #265, #201 related to that. It needs to be solved, definitely. And it needs to be solved with the multimodel search bug, #218 looks very promising in this regard.

I don't know that those issues directly solve the one I am experiencing. However they do address the root issue why I started playing around with the document_type settings.  I don't think update_index should be able to over write any model attributes.  At least not any that could potentially be persisted to the database after a manual index update.
Thank you for your huge contribution to the community with Tire.  I understand I am complaining without offering solutions. So I will take a stab at a solution when I have some time.
#218 does look like a good solution to the multi model issue. Is there something holding you back from pulling that fix into master?


Unexpected Application Error! Invalid regular expression!

Describe the bug
Unexpected Application Error! Invalid regular expression: invalid group
specifier name
RegExp@[native code]
module code@https://memos.xxx.com/assets/MemoResourceListView-8931b1bc.js:270:1182438
evaluate@[native code]
moduleEvaluation@[native code]
moduleEvaluation@[native code]
moduleEvaluation@[native code]
@[native code]
asyncFunctionResume@[native code]
@[native code]
promiseReactionJobWithoutPromise@[native code]
promiseReactionJob@[native code]
Error resolution(问题原因以及解决方法，开发者可参考)：
https://www.jianshu.com/p/0e6f0728df01

Steps to reproduce
打开就会重现，iOS系统无法使用。
Screenshots or additional context

Similar issue to: https://github.com/usememos/memos/issues/2639

@okhanyu this looks to be a duplicate issue from my comment above. Could you please close this and include these same details on the issue I linked? That way we have all this info in one place


CommandResponse not working  .Net Core 5

Hello.
I'm having problems with CommandResponse on Asp .Net Core with Asterisk 16. Always returns null.
CommandAction ca = new CommandAction("sip show users");
var responseUsers = manager.SendAction(ca) as CommandResponse;

I also noticed that the determineVersion() method in the ManagerConnection class cannot fetch the correct Asterisk version, due to this problem with the CommndResponse.
Has anyone else had this same problem?

This sounds similar issue  solved in #221.
Which version of AsterNET are you using?

I'm using a version 1.3.0.

I don't have a test setup that I can test this on anymore. So if someone else wants to try and fix this, go right ahead.

I can confirm that this is an issue in .NET 6 (which is also Core) for version 1.3.0.
I can also confirm that this issue is FIXED in master for .NET 6.
In case you run against this issue while using v1.3.0, using the following method also available on ManagerConnection works:
public int SendAction(ManagerAction action, IResponseHandler responseHandler)

You'll need to inherit from AsterNET's ResponseHandler or implement your own IResponseHandler but it it's a single method that accept the ManagerResponse so it's not difficult.

In case you run against this issue while using v1.3.0, using the following method also available on ManagerConnection works:

@stoyandimov  Can you give an explanation why this should work compared to the version with the timeout? Because the timeout version calls this method:
https://github.com/AsterNET/AsterNET/blob/c4df9d8ecb578460d6442f7cd673b9b11763fadd/Asterisk.2013/Asterisk.NET/Manager/ManagerConnection.cs#L1436

@stoyandimov Can you give an explanation why this should work compared to the version with the timeout?

The issue author mentions that this manager.SendAction(ca) always returns null. I did some tests on my own and mentioned that public int SendAction(ManagerAction action, IResponseHandler responseHandler) could work as a work around.
Haven't tested if the method with a timeout is also a working solution.

I think this has nothing to do with this, because this is broken with v1.3.0 but seems to work with latest master.
(btw. I compiled my "own" version from master and use this instead of 1.3.0 and it seems to work.


Document where this repo diverges from regular ReactJS

Hey, great project!
I'm just about to start reading through the source to figure out exactly what the tradeoffs are (beyond losing out on server-side rendering). This definitely looks like it  could be a sane alternative to the core library, especially for smaller projects, but it would be nice to know up front just what the differences are so people don't run into a wall down the road.
That is unless the only difference is the loss of renderToString/renderToStaticMarkup, which I find doubtful, but it'd be nice to know for sure straight from the documentation.
Thanks!

Good suggestion.
I have added react-lite vs react part in README
https://github.com/Lucifier129/react-lite#react-lite-vs-react

Good suggestion.
I have added react-lite vs react part in README
https://github.com/Lucifier129/react-lite#react-lite-vs-react

:+1: thank you very much!

:+1: thank you very much!


Weird crash on function call hover for function with default args

Not sure if this is an issue of the extesnion or clangd itself, but I have the following code:
  IRBuilder<> IRB(InsertBefore);
  if ( GlobalVariableForSymbol.find(symbol) == GlobalVariableForSymbol.end()) {
    GlobalVariableForSymbol[symbol] = IRB.CreateGlobalStringPtr(symbol);
  }

And the signature of CreateGlobalStringPtr is:
  Constant *CreateGlobalStringPtr(StringRef Str, const Twine &Name = "", unsigned AddressSpace = 0) { ... }

When i hover over the call to CreateGlobalStringPtr its working fine. Now if i provide a second or third argument (or both), e.g IRB.CreateGlobalStringPtr(symbol, "globalStr"), and then i hover over the call again, clangd crashes.
It works fine for other functions i tried, but somehow crashes for this one.
Logs
[Error - 12:58:40 PM] Request textDocument/hover failed.
  Message: Task was cancelled.
  Code: -32001
V[12:58:40.949] <<< {
  "id": 6,
  "jsonrpc": "2.0",
  "method": "textDocument/hover",
  "params": {
    "position": {
      "character": 52,
      "line": 355
    },
    "textDocument": {
      "uri": "file:///home/gkarlos/Projects/kerma/lib/Transforms/Instrumentation.cpp"
    }
  }
}

I[12:58:40.949] <-- textDocument/hover(6)
[Error - 12:58:41 PM] Connection to server got closed. Server will not be restarted.
[Error - 12:58:41 PM] Request textDocument/hover failed.
Error: Connection got disposed.
	at Object.dispose (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/connection.js:1009:27)
	at Object.dispose (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-languageclient/lib/common/client.js:71:35)
	at ClangdLanguageClient.handleConnectionClosed (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-languageclient/lib/common/client.js:2312:42)
	at ClangdLanguageClient.handleConnectionClosed (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-languageclient/lib/node/main.js:146:15)
	at closeHandler (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-languageclient/lib/common/client.js:2299:18)
	at CallbackList.invoke (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/events.js:54:39)
	at Emitter.fire (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/events.js:116:36)
	at closeHandler (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/connection.js:255:26)
	at CallbackList.invoke (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/events.js:54:39)
	at Emitter.fire (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/events.js:116:36)
	at StreamMessageWriter.fireClose (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/messageWriter.js:41:27)
	at Socket.<anonymous> (/home/gkarlos/.vscode/extensions/llvm-vs-code-extensions.vscode-clangd-0.1.7/node_modules/vscode-jsonrpc/lib/common/messageWriter.js:74:42)
	at Socket.emit (events.js:223:5)
	at Pipe.<anonymous> (net.js:664:12)

System information
Clangd version (from the log, or clangd --version): 10.0.0
clangd extension version: 0.17
Operating system: xubuntu 18.04 LTS

Moved to clangd repo as this is a server crash.
A couple of questions:

If you run clangd with --log=verbose (bya dding this to clangd.arguments in the vscode settings), do you get additional output that includes a backtrace for the crash?
Are you able to share a complete code file that triggers the crash?

Note that you're using clangd 10, we have plenty fixes after that, so this crash is likely fixed in trunk. I'd suggest you trying the upcoming release: https://prereleases.llvm.org/11.0.0/.

Moved to clangd repo as this is a server crash.

Thanks!

If you run clangd with --log=verbose (by adding this to clangd.arguments in the vscode settings), do you get additional output that includes a backtrace for the crash?

I think this output is with --log=verbose already. I can check again later to confirm.

Are you able to share a complete code file that triggers the crash?

If you are looking for an MWE that wouldn't help though anyway as there are multiple dependencies. Would the function that contains the triggering line help? Otherwise i can try craft an MWE that triggers the error.

Note that you're using clangd 10, we have plenty fixes after that, so this crash is likely fixed in trunk. I'd suggest you trying the upcoming release: https://prereleases.llvm.org/11.0.0/.

Thanks, i'll try it.


joker: 0.18.0 -> 1.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/candid82/joker/releases.
meta.description for joker is: "A small Clojure interpreter and linter written in Go"
meta.homepage for joker is: "https://github.com/candid82/joker"
meta.changelog for joker is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/a8670m20g9fchg4m0gn11ryagaj627h0-joker-1.0.0/bin/joker had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 1.0.0 with grep in /nix/store/a8670m20g9fchg4m0gn11ryagaj627h0-joker-1.0.0
found 1.0.0 in filename of file in /nix/store/a8670m20g9fchg4m0gn11ryagaj627h0-joker-1.0.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
joker

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a8670m20g9fchg4m0gn11ryagaj627h0-joker-1.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A joker https://github.com/r-ryantm/nixpkgs/archive/b0a6341bb7ba2205d1de1c4cd99ac3272b36a16d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a8670m20g9fchg4m0gn11ryagaj627h0-joker-1.0.0
ls -la /nix/store/a8670m20g9fchg4m0gn11ryagaj627h0-joker-1.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

joker

Maintainer pings
cc @andrestylianos @kalbasit for testing.

Change looks good to me, ping me for a revert if anything goes wrong.


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: istio-testing
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-presubmit

prow/istio-unit-tests.sh
2ff214956549c51c53ab3e3bf5ec540380a984ec
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


feat: port Analysis.Calculus.Deriv.Linear

[ ] depends on: #4434

This PR/issue depends on:

leanprover-community/mathlib4#4434
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#4434
By Dependent Issues (🤖). Happy coding!

bors merge

Avoiding merge conflicts on the queue:
bors r-

bors merge

bors merge


Fix print issue causing reviewdog to break

when this condition is reached a plaintext line is printed to the log that reviewdog later parses. Reviewdog then spits out the error "reviewdog: parse error: failed to unmarshal rdjson (DiagnosticResult): proto: syntax error (line 1:1): invalid value Did"

@tgorochowik I have mad the requested changes


How do I make a sticky footer in this theme

Sticky footers just got implemented in the last commit! 😄