date calculation for different note types needs clarification

I have changed to testing 1.0.0-beta and it seems the {{date}} calculation has changed a little bit. In 0.0.17 you could use {{date:YYYY}} on all note types and it would essentially put the year. In 1.0.0-beta, it seems that the optional YYYY parameter doesn't work and it fails to convert (leaves raw unconverted) - at least if trying to use in something like a quarterly note. Similarly, using {{date}} as is in a quarterly note converts it to 2022-Q3 for instance.
I think the action of using {{date}} output 2022-Q3 in a quarterly note can make sense, but I would expect to be able to use {{date:YYYY}} in quarterly note and have it generate the year based on the README, which states {{date}} is valid for all note types and accepts optional format parameter.
In the end, I think the current implementation requires users to use {{year}} in a yearly template, {{quarter:YYYY}} in a quarterly template, {{month:YYYY}} in a monthly template, and so on to represent the current year rather than having something consistent across all types. It can work, and maybe makes sense, but if this is the intent README is not very clear.

I agree, this confused me. There seems to be crossover between this and the behaviour described in https://github.com/liamcain/obsidian-periodic-notes/issues/128 (but #128 is about the wrong filename being created, while this issue is about the {{date}} token behaving inconsistently between template types.
As you say, these tokens operate as expected in the daily template. The documentation says that "supported template types" is "all" at https://github.com/liamcain/obsidian-periodic-notes#template-tags but the "optionally accepts a format" does not work consistently between the template types.
Quick visual demo below:

Using the same input in Daily and Weekly templates:
test1: {{date}}
test2: {{date:YYYY-MM-DD}}
test1: {{date:YYYY}}
day: {{date:YYYY-MM-DD}}
week: {{date:GGGG-[W]WW}}

The output in a Daily template is:
test1: 2022/10/16
test2: 2022-10-16
test1: 2022
day: 2022-10-16
week: 2022-W41

and in a Weekly template is:
test1: 2022/W43
test2: {{date:YYYY-MM-DD}}
test1: {{date:YYYY}}
day: {{date:YYYY-MM-DD}}
week: {{date:GGGG-[W]WW}}

I’m also seeing this issue. In my case, it breaks the automatic creation of a Dataview query to quickly reference the daily notes associated with that week:
# Daily Summary
```dataview
LIST
FROM "50 Resources/Daily Journal"
WHERE typeof(created) = "date" AND created >= date({{date:YYYY-MM-DD}}) AND created < date({{date:YYYY-MM-DD}})+dur(7 day)
SORT created ASC
```

The query is included into the template, but the {{date:YYYY-MM-DD}} instances are not correctly substituted. In my case, I’m also using a custom formatted date using “Wnn” for the weekly note so I can’t just pass plain {{date}} to Dataview.


[BUG]: yank highlight does not occur at the bottom half of larger files

Not 100% sure on the reproduction conditions, but as far as I can tell, the yank highlight fails when the file is large enough and you are (roughly) in the bottom half of the file.
example-file where that occurs

Looks like the cursor offset is not calculated properly when the viewport is scrolled down. Should be (famous last words 😆) an easy fix.
Thank you for reporting!

@chrisgrieser, this should be fixed in #1.0.7. Could you please verify and close this issue if everything is hunky-dory?

yup, can confirm that everything works now. Thanks for the quick fix!


mfgtools can't to work on i.MX6ULL + evk board

I get "fsl-yocto-L4.9.11_1.0.0.tar.gz" to my host PC.
And I compile the last mfgtools.
When I replace the "libMfgToolLib.so" and "mfgtoolcli" to fsl-yocto-L4.9.11_1.0.0 and run it.
The mfgtools fail run on linux version.
fail log:
ModuleID[2] LevelID[10]: new MxHidDevice[0x7f3d7c004dc0]
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is ./Profiles/Linux/OS Firmware/firmware/u-boot-imx6ull14x14evk_sd.imx
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is ./Profiles/Linux/OS Firmware/firmware/zImage, address is 0x80800000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is ./Profiles/Linux/OS Firmware/firmware/fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot, address is 0x83800000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is ./Profiles/Linux/OS Firmware/firmware/zImage-imx6ull-14x14-evk.dtb, address is 0x83000000
ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]
ModuleID[2] LevelID[10]: MxHidDevice[0x7f3d7c004dc0] Jump to Ramkernel successfully!*
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is ./Profiles/Linux/OS Firmware/firmware/u-boot-imx6ull14x14evk_sd.imx
ModuleID[2] LevelID[1]: RunPlugIn(): TransData(0x877FF400, 0x7EC00,0x74002380) failed.
ModuleID[2] LevelID[1]: PortMgrDlg(0)--MxHidDevice--Command Boot excute failed
I trace code, it will fail on "Jump".

i have same issue with you .please use the the commit 6b5ffe18fccdf80c79df5b3c6f223369fa098527,it's work ok.
it has  bug with last commit when work in linux platform .
the last windows version work ok.


A empty feature appears in roadmap.

As the screenshot shown below, a row with no feature description appears in roadmap table(2019 Q4 (October-December)).
Page URL: https://docs.microsoft.com/en-us/visualstudio/productinfo/vs-roadmap

@JacquelineWiddis Is this something that you can help with?


FR: Ask for target directory on first setup

AppImage installs, updates and downloads studd to user's "Documents" directory.
Sometimes user has another disk volume with appropiate space, or even faster for games.
And sometimes "Documents" directory is a network drive, inconvenient for software or rapid i/o.
AppImage should ask where to install files on first run.

It's not a rare practice to mount ~/Documents folder on a network resource.

But yes it's a rare practice to make an app installer to deploy its stuff at ~/Documents , which is intended for another use, fully controlled by user.

As I noted already, this was resolved, and launcher is now following the freedesktop XDG specification and not installing files in Documents.

About launcher creation and registration with an additional shell script, I believed BAR app was targeted to unexperienced users.

I've listed multiple options. Changing the installation directory, unlike on Windows, is uncommon for Linux software, and I consider it an advanced configuration option. BAR is not targeting any specific category of users, but we try to make it streamlined for all users. Changing directory is possible and I consider advanced configuration that doesn't have to be easy.

If somebody external will be willing to write some nice smooth prompts and GUI for picking up directory on the first run, handle properly different cases and it wouldn't add a lot of complexity to launcher, I would accept such PR. So, I will reopen this, but it needs external contributor to resolve.

Sorry, I didn't understand well the XDG implementation now implies to not install files in concrete ~/Documents
About uncommon selection of install directory on GNU/Linux, this is because GNU/Linux distributions have already defined FHS destinations for all software, and this structure is armonized with package managing (Dpkg, RPM, etc).
Any installation process out of package manager integration, and even more in unprivileged context (no root permissions), should ask user for things like program files directory and/or data files directory.

this is because GNU/Linux distributions have already defined FHS destinations for all software (...) Any installation process out of package manager integration, and even more in unprivileged context (no root permissions), should ask user for things like program files directory and/or data files directory.

No. Please read what XDG Specification is about.

XDG specifications are focused on GUI-specific behaviour, while FHS is focused on a wider scope: Unix-like including GNU/Linux.
And sure we are converging to same point, coming from each one's perspective.

XDG = X Desktop Group.
I mention this to compare with operating system FHS and supported package managers.
But yes, thread's focus is: Whatever setting where to save game data as configuration that needs to be offered on the first run


Patches replace operation when match is not specified

This is not the world's best patch, but I want to reduce the blast-radius of these changes for now.
Previously, providing the following valid JSON patch to a recipe:
{
    "op": "replace",
    "path": "@output/build/number",
    "value": "0",
}

would result in Recipe.patch() wiping out the entire block of build sub-keys.
I'm not entirely sure why that was happening, but I believe it had to do with defaulting the match variable to .* which caused the current algorithm to find every line under build and wipe it completely:
build:
  0
  0

Tested changes against perseverance-skills.
After having run into many issues using percy, IMO we need to:

Make patch operations "atomic" (i.e. .patch() should not render and save changes. To put another way, patching should maintain it's in-memory changes and the caller should be responsible for writing to disk. This is to save disk I/O operations when we start making lots of changes AND allows a program to ask a user if they would like the changes that have been made.
In general, make percy RFC 6902 compliant as much as we possibly can.

This will reduce confusion from anyone making calls to percy
Custom concepts like @object are not well documented and do not seem entirely necessary.

Add significant testing automation (primarily in the form of unit testing) to ensure reliability of the library AND to prevent regressions.
Reduce/eliminate the use of deepcopy() for performance and code clarity. Especially as it seems to be used heavily for logging purposes.
Reduce/eliminate the injection of custom information into the user-provided patch object in favor of using more variables. This correlates heavily with the previous point.

I can gladly raise these as GitHub issues, but I wanted them to be written down in some form. I do not likely have the time to implement all of these ideas before I get a first version of recipe-bootstrapper out, but I am concerned about the long-term stability of recipe-bootstrapper and percy if these points are not addressed.

This is not the world's best patch, but I want to reduce the blast-radius of these changes for now.
Previously, providing the following valid JSON patch to a recipe:
{
    "op": "replace",
    "path": "@output/build/number",
    "value": "0",
}

would result in Recipe.patch() wiping out the entire block of build sub-keys.
I'm not entirely sure why that was happening, but I believe it had to do with defaulting the match variable to .* which caused the current algorithm to find every line under build and wipe it completely:
build:
  0
  0

Tested changes against perseverance-skills.
After having run into many issues using percy, IMO we need to:

Make patch operations "atomic" (i.e. .patch() should not render and save changes. To put another way, patching should maintain it's in-memory changes and the caller should be responsible for writing to disk. This is to save disk I/O operations when we start making lots of changes AND allows a program to ask a user if they would like the changes that have been made.

In general, make percy RFC 6902 compliant as much as we possibly can.

This will reduce confusion from anyone making calls to percy
Custom concepts like @object are not well documented and do not seem entirely necessary.

Add significant testing automation (primarily in the form of unit testing) to ensure reliability of the library AND to prevent regressions.

Reduce/eliminate the use of deepcopy() for performance and code clarity. Especially as it seems to be used heavily for logging purposes.

Reduce/eliminate the injection of custom information into the user-provided patch object in favor of using more variables. This correlates heavily with the previous point.

I can gladly raise these as GitHub issues, but I wanted them to be written down in some form. I do not likely have the time to implement all of these ideas before I get a first version of recipe-bootstrapper out, but I am concerned about the long-term stability of recipe-bootstrapper and percy if these points are not addressed.

JC stumbled upon the same issue when working on another topic.
This PR should address it: https://github.com/anaconda-distribution/percy/pull/40
To address some of your comments:

patch atomic: good idea
patch as close as possible as rfc: I am not sure the rfc can support all our use cases
@output: This is useful to define generic patches while still being able to be specific when needed.

What I realize is that to use this patch implementation efficiently, one still need to be a regex master. At the match regex influence a lot the results.
Some additional information:

The patch method relies on the recipe to be rendered (this means at least one variant required).
Use cases:

remove an element matching a condition
add an element (duplicates allowed)
replace an element
replace or add an element
Things to take into consideration: whether to preserve selectors or not...

Example to append patches:
[
    {
        "op": "add",
        "path": "source/patches",
        "match": "(aa.patch)|(bb.patch)",
        "value": ["aa.patch", "bb.patch"]
    }
]

Examples to replace cython or cython 0.29.23 by cython 0.29 in any package of the recipe:
[
    {
        "op": "replace",
        "path": "@output/requirements/host",
        "match": "cython\\s+0.29.\\d+",
        "value": ["cython 0.29"]
    },
    {
        "op": "replace",
        "path": "@output/requirements/host",
        "match": "cython\\s*($|[^#])",
        "value": ["cython 0.29"]
    }
]

Example to update a build number:
[{"op": "replace", "path": "build/number", "value": "0"}, {"op": "replace", "path": "@output/build/number", "value": "0"}]

@cbouss I got pretty far with the parse-tree implementation late last week. For a day and a half of dev time, I think it's very promising. I can already go from YAML -> tree -> YAML losslessly on a simple example.
The work is here and I plan to continue to work through test cases this week: https://github.com/anaconda-distribution/percy/tree/schuy_recipe_parser
I'm going to start with the replace patch operation first as it addresses what I need in recipe-bootstrapper. I think I can match the RFC pretty closely and potentially expand upon it for our needs.
If you would like to discuss further about this, we can hop on a call, maybe with JC and Mark as well, but I think the parse tree method is going to be a very powerful tool. I think you saw my stats from last week, but I think we can cover about 90% of recipes with it and maybe fall back to a regex mechanism for the other 10%. And that last 10% is not likely to be automated anytime soon.

https://github.com/anaconda-distribution/percy/tree/schuy_recipe_parser

That's cool.
So what would be needed eventually is:

Ability to update yaml values
Ability to update jinja variables
Ability to update selectors variables

If you haven't looked at it, ruamel.yaml.jinja2 does handle some of the preserving part of jinja.
But it doesn't allow updating jinja itself. ruamel parser also has editing capabilities on comments (useful since selectors are comments)
A meeting with a few people would be useful. Perhaps we should define some use cases.

- Ability to update yaml values
- Ability to update jinja variables
- Ability to update selectors variables

I can confidently handle those first two points with that branch/already have plans to handle those cases.  The third one I have not addressed and the parse tree is storing those as "comments" per node in the tree. I don't need selectors for my current project needs, but I don't see an issue with parsing the "comment" into a more semantic form.
When I get a chance, I'll find time on the calendar to get a sync meeting between you, me, JC, and Mark.

Ah, I mostly needed 1 and 3 so far :)
To keep all links in one place, this is the conda recipe proposal change to address issues regarding manipulating recipes:
https://github.com/conda-incubator/ceps/pull/54

Ability to update yaml values
Ability to update jinja variables
Ability to update selectors variables

I would add to "Ability to update selectors variables" that we should be able to add, remove and update selectors without involving any kind of "environment" evaluation. For examplem when I ask to add a selector, I want it to be applied no matter what variants are currently available.


Update framework-components.mdx

add some explainations to named-slot

Description (required)

Related issues & labels (optional)

Closes #
Suggested label:

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Hello. Can you describe in more detail why you made this change?
If it is necessary to add additional instructions, I think we should add them first in the original English docs.
I thought maybe we could add a link to https://docs.astro.build/en/core-concepts/astro-components/#named-slots to achieve the same purpose?

Hey @leochenliu, welcome to Team Docs, thanks for your contribution!
To reiterate liruifengv's comment,  as this seems to be a content change, we need it to be proposed to the English version of the docs so that all translations can benefit from it afterwards.
Could you update this PR to change the English version instead with your proposed change?

Hi @leochenliu ! I translated the content addition, and if the translation is accurate, this is not something we would add to the English text. The note would be too large and seems to repeat information.
So, I am going to close this PR. But, it is possible that this is just how my browser translated and if you contribute content in English it will read differently! You can make a new English PR if you have content that is significantly different from what is already inside the note and we can look at that.


Latest ready inference service is showing the none working update

/kind bug
What steps did you take and what happened:
-Update a working existing model with a new inference revision (patch)
-The new inference revision crashes with an error such as ReconcileIngressFailed
-The inference service is incorrectly updated with having the nonworking revision as the latest Ready revision.
What did you expect to happen:
The latest Ready revision to be the one used per this graph:
https://github.com/kubeflow/kfserving/tree/master/docs/samples/v1beta1/rollout
https://github.com/kubeflow/kfserving/raw/master/docs/samples/v1beta1/rollout/canary.png

NAME                               URL                                                           LATESTCREATED                            LATESTREADY                              READY   REASON
test-model-088-predictor-default   http://test-model-088-predictor-default.default.example.com   test-model-088-predictor-default-00002   test-model-088-predictor-default-00002   True
test-model-092-predictor-default   http://test-model-092-predictor-default.default.example.com   test-model-092-predictor-default-00004   test-model-092-predictor-default-00004   False   ReconcileIngressFailed

Anything else you would like to add:
A excerpt from the knative logs;

{"severity":"ERROR","timestamp":"2021-03-19T11:51:37.607858036Z","logger":"istiocontroller.istio-ingress-controller.knative.dev-net-istio-pkg-reconciler-ingress.Reconciler","caller":"controller/controller.go:538","message":"Reconcile error","commit":"9f0302e","knative.dev/controller":"istio-ingress-controller","error":"failed to update VirtualService: Internal error occurred: failed calling webhook "validation.istio.io": Post https://istiod.istio-system.svc:443/validate?timeout=4s: context deadline exceeded","logging.googleapis.com/labels":{},"logging.googleapis.com/sourceLocation":{"file":"knative.dev/pkg@v0.0.0-20210107022335-51c72e24c179/controller/controller.go","line":"538","function":"knative.dev/pkg/controller.(*Impl).handleErr"},"stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\tknative.dev/pkg@v0.0.0-20210107022335-51c72e24c179/controller/controller.go:538\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\tknative.dev/pkg@v0.0.0-20210107022335-51c72e24c179/controller/controller.go:524\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\tknative.dev/pkg@v0.0.0-20210107022335-51c72e24c179/controller/controller.go:461"}

Environment:

Istio Version: 1.9
Knative Version: v0.20.1
KFServing Version: v0.5.1
Kubeflow version: none
Kubernetes version: (use kubectl version): v1.17.17-gke.1100

@PatrickGhosn What's the status of the inference service, the revision status is separate from the routing status. It seems like that the knative controller is not able to call the istiod webhook?

@yuzisun yes. I simulated a crash from the firewall by blocking the main node in a private gke cluster. I was trying to test out what would happen if a deployment update failed.
After some testing, the good news is that calls to the inference service was routing to the running revision correctly.
So it looks like only the issue is that the LatestReady was showing the none ready version when the Ready was false. Functionally this shouldn't affect anything. But I will verify more in a couple of days when I have some time.

@PatrickGhosn The revision status is correct, in this case if you check kubectl get revisions the revision status should be reported as true but kubectl get routes should show the status as false, knative service status aggregates the revision status and routing status so it shows false there.

/close


SDK fails to connect to Kinect sensor if same device was earlier plugged into another USB controller

Describe the bug
SDK fails to detect device if it was previously connected to a different controller on same computer
To Reproduce

On a clean system plug in device into motherboard (ASMedia USB host controller was used)
Unplug the device
Install supported USB controller card (Speed Dragon EU306A was used)
Connect the device to installed controller
Run Kinect Viewer

Expected behavior
Viewer starts and displays feed correctly
Logs
usb_cmd_create(USB_DEVICE_COLOR_IMU_PROCESSOR, NULL_INDEX, container_id, &colormcu->usb_cmd) returned failure
colormcu_create(container_id, &device->colormcu) returned failure in k4a_device_open()
find_libusb_device(). Unable to find Container ID {8358ea0b-ca8f-494c-6aa6-2ae38a7528a0}
Desktop (please complete the following information):

SDK Version:  1.4.1

Additional context
This was resolved by going into device manager, turning on hidden devices display and removing any Kinect related hidden device.

Try add "sudo" before your command. e.g. sudo ./k4aviewer
This works for me.

@czhaneva usually no sudo is needed. you just have to copy the "99-k4a.rules" files to your "/etc/udev/rules.d/" folder like described here:
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/develop/docs/usage.md#linux-device-setup


[feature] Add phpadmin

Would you like to integrate phpAdmin into the operator? I can contribute.

@cndoit18


KAFKA-14676: Include all SASL configs in login cache key to ensure clients in a JVM can use different OAuth configs

We currently cache login managers in static maps for both static JAAS config using system property and for JAAS config specified using Kafka config sasl.jaas.config. In addition to the JAAS config, the login manager callback handler is included in the key, but all other configs are ignored. This implementation is based on the assumption clients that require different logins (e.g. username/password) use different JAAS configs, because login properties are included in the JAAS config rather than as separate top-level configs. The OIDC support added in KIP-768 only allows configuration of token endpoint URL as a top-level config. This results in two clients in a JVM configured with different token endpoint URLs to incorrectly share a login.
This PR includes all SASL configs prefixed with sasl. to be included in the key so that logins are only shared if all the sasl configs are identical.
Two rejected approaches:

Only include sasl.oauthbearer.token.endpoint.url in the key. Rejected because there may be other configs in future for which we want different logins. It may also be useful to have a mechanism to force different logins when using custom configs, sasl. prefix would work in general.
Include all configs in the key. Kafka brokers create multiple inter-broker clients with different configs, e.g. client.id. We want brokers to create only one login, hence chose a subset based on the sasl. prefix.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@rajinisivaram - LGTM.
It took me a second to verify that the configs that was passed into the LoginMetadata  wasn't being used directly in the hashCode and equals methods.
Thanks for the fix!

@omkreddy @kirktrue Thanks for the reviews. Test failures not related, merging to trunk.

Also cherry-picked to 3.4 and 3.3 branches.


How about compile to css

Hi, I'm trying to host this lib on cdnjs.
But cdnjs cannot host scss files.
Could you provide css files?
Thanks.
https://github.com/cdnjs/cdnjs/pull/8652

Hey Guan,
Have you read my comment in #82 ?

...given family.scss has no actual output ...

There is no output and there will never be because it's a mixin library. Mixins do not generate any CSS output until they are @included in a Sass file. Even then, the output only makes sense in combination with actual site styles and is therefore very different to a standalone file like normalize.css or sanitize.css.

Hi, family isn't a css library per say, it's a mixin library. Therefore, if I compile it, there would be no CSS outputed.


Widget: Number Input

Description
This feature contains the widget for the number input

Related Issue(s)

Widget: Number Input
Checklist

Dashboard widget ✅
Tests  ✅
Docs of the widget (including tryout button) ✅
Interactive dashboard docs - Will be created and published once the widget published 🚀

[x] I have read the contribution guidelines
[x] Suitable unit/system level tests have been added and they pass
[x] Documentation has been updated

[ ] Upgrade instructions
[ ] Configuration details
[ ] Concepts

[ ] Changes flowforge.yml?

[ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
[ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

[ ] Includes a DB migration? -> add the area:migration label

Your 2 x E2E tests are failing, and have you 4 being skipped?

Your 2 x E2E tests are failing, and have you 4 being skipped?

This is my bad. I saw couple of time out issues so I thought it's because of the existing issue https://github.com/FlowFuse/node-red-dashboard/issues/882
I will update them

Checkout the other PR I've opened up for the E2E docs which will help get your local environment uo and running

Checkout the other PR I've opened up for the E2E docs which will help get your local environment uo and running

Thank you so much. I will check it for sure

Checkout the other PR I've opened up for the E2E docs which will help get your local environment uo and running

This is ready for to review

If I type a double-digit number into the widget, then a message is sent halfway through typing the number - this isn't desirable.
I'd expect the event to be sent when either the up/down arrows are selected, or after I've move focus out of the number input

If I type a double-digit number into the widget, then a message is sent halfway through typing the number - this isn't desirable.
I'd expect the event to be sent when either the up/down arrows are selected, or after I've move focus out of the number input, or set a 300ms timeout (or something similar) that waits to make sure no other input follows, before sending the message

@joepavitt Ihis is handled by setting the delay to 300ms by default, as this widget emits its value immediately after each update. Therefore, the user can change the delay as desired.

Updated the tests as well ✅

Be careful. when you're pushing, you force pushed and overrode changes I had previously committed to your branch

Be careful. when you're pushing, you force pushed and overrode changes I had previously committed to your branch

I apologize for that! I didn't realize I was overriding your changes. I'll be more cautious with force pushes in the future. Thanks for letting me know.

I'll be more cautious with force pushes in the future.

If git has prompted you to do a force push, then that means you're likely doing something wrong, e.g. changes on the remote branch you haven't pulled/merged. You shouldn't ever have to force push except in exceptional circumstances

@gayanSandamal you have many failing tests again, I checked locally and they're all failing there too - once again, please make sure your tests are passing locally before requesting review

@gayanSandamal you have many failing tests again, I checked locally and they're all failing there too - once again, please make sure your tests are passing locally before requesting review

I ran the tests locally before pushing them and all the tests got passed as below and in the github actions also as below.

Regarding the other test widget failures I thought it's because this random test failure reported https://github.com/FlowFuse/node-red-dashboard/issues/882

Make sure you're running npm run cy:run not just the tests in isolation, as there may be unintended consequences across other tests.
#882 normally causes one or two failures in the control.spec and sometimes one or two form failures, but nothing else.
Running tests locally, all the number-input tests fail.

@joepavitt I'm marking this as ready to review as the tests are passing locally

Still getting a failure in GH - can you remove any tests that rely on a timeout please, and just keep tests where click interaction trigger the payload being sent, e.g. click of up/down arrows

Still getting a failure in GH - can you remove any tests that rely on a timeout please, and just keep tests where click interaction trigger the payload being sent, e.g. click of up/down arrows
No point us having the tests in there if they're inconsistently reporting as it'll be a distraction on every PR we open

Removed the unstable tests of the number input as discussed. There's random test failure happens on other tests as well. I've tried by re-running the GH job


[opendp] Restore diamond_search_height_ to 400

diamond_search_height_ was originally 400 but has since been changed
to 100. On a design with large macros, the openroad version of opendp
fails but the standalone version works. Changing diamond_search_height_
back to 400 fixes it.
We should probably expose this option so it can be configured.

I'm also not sure why global placement is putting things in the middle of macros. I'm using openlane if it matters.

I'm also not sure why global placement is putting things in the middle of macros. I'm using openlane if it matters.

Please provide an test case showing the issue.

Changing the search height to 400 does not fix the underlying issue. It will just fail with a bigger macro. There has to be a testcase to understand why the cell ended up on top of the macro.

This tarball replace-opendp-issue.tar.gz should reproduce the issue. I see:
 _49364_
[WARNING DPL-0005] Overlap check failed (1).
 microwatt_0.soc0.processor.register_file_0 overlaps _49364_
[WARNING DPL-0006] Site check failed (1).
 _49364_

It looks like replace has placed quite a lot of stuff over the macros (especially the register file):

@jjcherry56 do you think replace should not place standard cells over macros? I had a quick look through the code and it seems to rely on opendp to fix things up. If it is relying on opendp then I'm not sure why opendp has a limit on the diamond search at all - it might have to move a cell a very long distance.

Apparently replace can place cells on top of macros. I don't think changing the displacement limit is the way to address this problem because it means the user has to know the max size of a macro in site dimensions and manually override whatever default there is. I am planning on simply moving the cells off of the macros (no search required) before legalization instead.

Apparently replace can place cells on top of macros. I don't think changing the displacement limit is the way to address this problem because it means the user has to know the max size of a macro in site dimensions and manually override whatever default there is. I am planning on simply moving the cells off of the macros (no search required) before legalization instead.

28b1ed74 Tue Jan 12 09:44:54 2021 -0700 opendp mv cells off blocks

28b1ed74 Tue Jan 12 09:44:54 2021 -0700 opendp mv cells off blocks


feat(QTREES-385): Page loading between pages

This PR ensures trees are loaded instantly via CSR and loading indication instead of SSR.

There is a small merge conflict, but that should be easy to resolve.

:tada: This PR is included in version 1.0.0-staging.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Hip134 update 2

Updates and clarifications based on the October 10th Mobile Working Group Meeting.

Is this ready to land, @jhella?

@abhay I need to confirm implementation details and coding commitments from madninja. I was planning to ping him in the hip channel on Monday during business hours. Thanks for checking.

@madninja I added some questions/comments in the HIP 134 discord channel.  Feel free to reply there at your convenience.

@zer0tweets That's a good clarification.  The intent was trailing, not 25 connections ever.  Will update to be more clear once I've collected other comments.

@abhay @waveform06 Please change the HIP and channel name to:
HIP 134: Reward MOBILE Carrier Offload Hotspots
I was informed by Madninja this program is technically no longer in beta so I'm updating the title as such.  With the title update and full approval of PR 1104 we're ready to go to vote as discussed in the MWG today.


Sample code to do layout modifications in Swagger UI generated by Swashbuckle

I want to make UI modifications on Swagger UI.
Could you please help me by providing some sample code for it.

On this topic, there should be enough information in the readme to get you started ...
https://github.com/domaindrivendev/Swashbuckle#customizing-the-swagger-ui


Added SK layout

Tested, it should work

Awesome! Thanks for your efforts 😃 mind sharing your testing script? Would safe me some time

LOCALE SK
DELAY 2000
STRING !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ\[]^_`abcdefghijklmnopqrstuvwxyz{|}~´ˇáéí´ĺ´ó´ŕúýčˇďľňšťžäô
ENTER

At the end ´ and ˇ must be pressed before these ´ĺ´ó´ŕˇď letters since these aren't on keyboard.

Awesome, works great! Thanks again.


Update aws-java-sdk-bundle to 1.12.486

About this PR
📦 Updates com.amazonaws:aws-java-sdk-bundle from 1.12.480 to 1.12.486
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-bundle" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #2725.


Better Rust error handling

Panics should raise an error to user code so it can deal with it
Console shouldn't get spammed with errors

@disambiguator Small bug (I think) that I came across in the current implementation: panics now seem to be completely silenced when they don't originate from the JS side. We just set wasmOnline to 0, but the error message in that case gets lost.
Should we still call print to the console during _throwError for now? Or maybe we can solve this when you add the JS callback for errors — by default that callback can print to the console but you can override it to do other things?

@janpaul123 Can you explain this comment a bit more? I don't really get what you mean by silenced. I added a panic! in a handle function, and I in fact do see it in the JS console.
For example: in the test suite handle function if I do...
        match event {
            Event::Signal(_) => {
                panic!("Ahhh!");
            }
            _ => {}
        }

and then press "Send signal from worker":
I see:
Uncaught RustPanic: panicked at 'Ahhh!', zaplib/test_suite/src/main.rs:41:17
    at _throwError ([module]:353:19)
    ...

@disambiguator Ahh thanks for checking! I think I got misled by the behavior in #30, which didn't in fact throw an error but just caused wasmOnline to be set to 0. All good then! 🎉


permit nullable response body

Guidelines
permit optionally nullable body like Result<Foo?>

[X] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

to solve https://github.com/skydoves/retrofit-adapters/issues/17

all test run correctly

pushed fix for spotlessKotlinCheck


Increase etcd instance sizes to conform with published CoreOS

recommendations (t2.large). Fixes #670.

Helm failed us:

[aws] fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["/opt/cnct/kubernetes/v1.6/bin/helm", "init"], "delta": "0:00:30.559221", "end": "2017-07-29 23:01:46.778717", "failed": true, "rc": 1, "start": "2017-07-29 23:01:16.219496", "stderr": "Error: error installing: Timeout: request did not complete within allowed duration", "stderr_lines": ["Error: error installing: Timeout: request did not complete within allowed duration"]

Restarting.

Actually, in view of k2/620, maybe we really should move to m4.16xlarge. Since that's too big for many typical clusters, I'm inclined to get this is in anyway. It's a more reliable baseline, and we can increase it again once we tackle the larger cluster scaling recommendations. Thoughts?

Combing etcd issues, network speed seems to be the biggest issue.  The smallest ec2 instance with enhanded networking is m4.large.
As I recall, all t2 instance types, no matter the size, have "burst" networking.  The "burst" anecdotally seems to contribute to the startup/discovery failure (but no conclusive data on that).
That being said, for dev work where we really only need quorum t2.large may be ok.   Otherwise, m4.large may be the better option.

I agree. The t2.large proposal was the smallest recommended size. Since the difference in cost between a t2.large and an m4.large is $0.006/per node hour, I will update this PR to use m4.medium.

ok, but m4.large is the first machine with enhanced networking (ie. faster networks).  m4.medium does not have that.

CI continues to timeout:

[aws] FAILED - RETRYING: Get all nodes (13 retries left).
[aws] Cancelling nested steps due to timeout
[aws] Sending interrupt signal to process
[aws] Terminated

Increasing the timeout as was done for k2/688.

After increasing the CI stage timeout, the kraken.readiness role is failing.
rodin:k2 dwat$ ks get po | grep Error
kube-scheduler-ip-10-0-73-31.ec2.internal              0/1       RunContainerError   0          119d
rodin:k2 dwat$

and
ks log kube-scheduler-ip-10-0-73-31.ec2.internal shows that there appears to be a leader election problem.
I0403 23:26:34.575600       1 leaderelection.go:247] lock is held by ip-10-0-57-226.ec2.internal and has not yet expired


add active class to heading to conditionally remove pb when active

should fix https://github.com/chec/dashboard/issues/274

Comparing the deploy preview and the current state:
https://deploy-preview-295--chec-ui.netlify.app/?path=/story/components-accordion--default-story
https://chec-ui.netlify.app/?path=/story/components-accordion--default-story
I feel like it looks a bit off now.

hmm yea im not sure why the ui component has a fixed height regardless of whether theres a subtitle or not. in implementation would look like this when accordion is inactive:

and when active:

Yeah okay I've had a brief look at this and something really weird is happening here. There's a helpful resource I found:
https://medium.com/fed-or-dead/margin-collapse-or-why-your-child-element-is-moving-the-parent-b199a0b60497

ok thanks will take a look at that!

Feel free to reopen when this is ready for review

Thanks, sorry haven't come back to this but will do so.


Create Hyperparameter Program Inputs

Create arbitrary specifications for hidden units and pooling layers
e.g. layers 9,5,3,3 -pools 2,2,2,2` for 4 layers with the respective hidden units and 2x2 poolings between them

Finished.
Doesn't allow for different types of layers (every layer is convolution --> maxPooling --> tanh).
Also, it doesn't allow for non square shaped pooling areas (assuming we will always use a square).


Update sched-ops vendor

Sched-ops now has new api for CreateNamespace, this PR adds vendor update for sched-ops

@ram-infrac thiago is already updating the sched-ops vendor as part of https://github.com/portworx/torpedo/pull/512
He is running our smoke job to ensure the vendor update doesn't break anything. Once his PR merges, we won't need this.

#512 is merged @harsh-px should we close this PR?

Yeah this is no longer needed.


No feedback when project import fails

Describe the bug
When importing a project via url failure does not give any feedback to the user. This appears to happen when a valid url is but the repo does not exist. I was able to reproduce this on both my local arcade and the live site.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://arcade.makecode.com/'
Click on 'import'
Paste a github url that looks valid => https://github.com/microsoft/pxt-arcade/fake

Expected behavior
This should give some feedback to the user similar to an invalid url instead of just failing and throwing an error in the console.
Screenshots

Console

Desktop (please complete the following information):

OS: OSX
Browser Chrome

Moving the error notification where the 404 userError is seems to solve the problem. The catch that should be displaying the notification doesn't seem to get hit.
https://github.com/microsoft/pxt/commit/adfb2429d7ee2c03b7d6a77f42cf7f1f8f32

Open a PR


private-ranges parameter support for 'az network firewall policy create' and 'az network firewall policy update'

Related command

az network firewall policy create, az network firewall policy update
Do we have a an option to specify private-ranges when creating new firewall policy or updating an existing one? This parameter is used for setting Perform SNAT options that are available in the portal shown on the below image.

Is your feature request related to a problem? Please describe.

Unable / don't know how to set Perform SNAT options in CLI. In PowerShell below command is used to specify the private ranges and based on the privates ranges provided the Perform SNAT is determined.
New-AzFirewallPolicy -Name myFp -ResourceGroupName myRg -Location westus2 -PrivateRange @("<IP_ADDRESS>/24", "<IP_ADDRESS>/8","<IP_ADDRESS>/20")
Describe the solution you'd like

Can we add private-ranges parameter to firewall policy create or update commands if we don't already have. If we already have, can you please provide usage and documentations?
Describe alternatives you've considered

Additional context

network feature

@Gizachew-Eshetie Does it meet your needs? https://learn.microsoft.com/en-us/cli/azure/network/firewall?view=azure-cli-latest#az-network-firewall-create (1st example)


Support question: Search images by creationDate

Hi
Thank you for this nice Python library! I wanted to use it to search for images that were created on specific days in the past. The idea is to create a script that gets the images of today's date for 1 to n years in the past. In the sense what Google and OneDrive do with their history notifications about images.
Could anybody give me a hint on the syntax of dk.images.select()? I see that these are instances of SQLAlchemy objects, but I don't get how to do the correct SQL join because creationDate is a property in table ImageInformation and not directly in Images.
Thank you
Thorsten

Hi Thorsten,
I'm not really a SQLAlchemy expert, so please take this with a grain of salt...
The classes Images, Albums etc. are wrappers for accessing the table (the general mechanism is in tables.py). The actual SQLAlchemy mapped classes can be accessed directly as Images.Class etc. The helper classes for images are available via dk.images.ImageInformation etc.
The mapped classes have a column prefix _ (the "official" properties without underscore can have format conversions or lack a setter to make them read-only) that needs to be added when extending queries manually. Relationships are defined with a _ prefix too (see images.py for mapping to the table names).
So I guess you can try something like
iinf = dk.images.ImageInformation
query = dk.images.select().join(dk.images.Class._information).where(iinf._creationDate > min_date).where(iinf._creationDate < max_date)

Even more complicated queries could be generated with the and_ and or_ functions of SQLAlchemy.
Regards,
Ralph

Hi Ralph,
thank you very much for this tip. It works as you suggested and I have created the following functions. Perhaps they will be of use to someone else.
def get_imageInfo(imgList):
    """Get image information for each image entry returned from query."""
    global VERBOSE, DEBUG, rootPath

    imgInfoList = []
    for img in imgList:
        image = {}
        id = img._id
        if dk.images[id]._album:
            album = dk.albums[dk.images[id]._album]
            path = album._relativePath
        else:
            path = '<Unknown>'
        fileName = dk.images[id]._name
        fileSize = dk.images[id]._fileSize
        creationDate = dk.images[id].information._creationDate
        modificationDate = dk.images[id]._modificationDate
        uniqueHash = dk.images[id]._uniqueHash
        if DEBUG:
            print(f"(I) {path}/{fileName} ({fileSize} bytes), Created: {creationDate}, Last Modified: {modificationDate}")
        image = {'path': f"{rootPath}/{path}/{fileName}", 'filesize': fileSize, 'creationDate': creationDate, 'modificationDate': modificationDate, 'uniqueHash': uniqueHash}
        if VERBOSE:
            print(f"(I) Adding image '{image['path']}' to list.")
        imgInfoList.append(image)
    return imgInfoList

def get_imageList(uniqueHash = ''):
    """Get list of images through Digikam DB query."""
    global VERBOSE, DEBUG, rootPath

    # Startzeit erfassen
    startTime = time.time()
    imgQuery = imgList = []

    # Heutiges Datum
    currentDate = datetime.today()

    # Find image by unique hash
    if uniqueHash:
        if VERBOSE:
            print(f"(I) Searching for image with unique hash '{uniqueHash}'.")
        imgQuery = dk.images.select(uniqueHash = uniqueHash)
        imgList.extend(get_imageInfo(imgQuery))
    else:
        for n in range(20):
            #pastDate = currentDate - relativedelta(years=n)
            #minDate = pastDate - relativedelta(days=1)
            #maxDate = pastDate + relativedelta(days=1)

            pastDate = currentDate - relativedelta(years=n)
            minDate = datetime.combine(pastDate, datetime.min.time())  # Datum mit Uhrzeit 00:00
            maxDate = datetime.combine(pastDate, datetime.max.time())  # Datum mit Uhrzeit 23:59

            if VERBOSE:
                print(f"(I) Searching for images created within range {minDate} - {maxDate}.")

            iinf = dk.images.ImageInformation
            imgQuery = dk.images.select().join(dk.images.Class._information).where(iinf._creationDate > minDate).where(iinf._creationDate < maxDate)
            imgList.extend(get_imageInfo(imgQuery))

    if DEBUG:
        pprint(imgList)

    # Endzeit erfassen
    endTime = time.time()
    num = len(imgList)
    if VERBOSE:
        print(f"(I) {num} entries found.")

    # Ausführungszeit berechnen
    executionTime = round(endTime - startTime, 2)
    if VERBOSE:
        print(f"(I) Query time is {executionTime} seconds.")

    return imgList

Kind regards
Thorsten


Fix b on long lines

Solves #773 and partially addresses #573.
Somehow a sequence of cursorMove commands is causing a bug in vscode. Removing them and directly setting the cursor location solves this issue. We don't need cursorMove vscode commands in this case anyways as less than one line move does not seem to get registered in jumplist.
Since the extension is getting highlights from redraw notifications, which is limited by window size, and neovim did not make the starting column of the current viewport in buffer available in the drawing notifications, the visual mode still displays incorrectly in vscode. However, it seems like the actual editing itself is working properly. There is no good fix to this other than implementing the display part of visual mode in the extension.

The deleted code sure looks attractive :)
Possible to write some sort of test? At least to exercise the codepath.
Rebasing will fix CI.

I've been using this for a while and it seems to work well. In addition, I think the codepath is already excersized by tests because it is a core part of the plugin. I think it also fixes a bug where lots of j/k up and down on the end of the line won't return to the same col after a bit.

Additionally, I think this fixes a problem where some jumps don't get registered in jumplist, because they come from a sequence of cursormove commands.


Upgrade Spring boot & framework

Currently OLS4 is using version Spring framework 2.4.5.RELEASE and Spring boot 1.3.8.RELEASE. These versions I think come from OLS3 and we may be forced to use it for backward compatibility of our REST API, but at least we should verify whether we can upgrade to a later version of Spring, if not the latest.
Latest versions available for comparison are  5.3.23 for framework and 2.7.5 for boot.

If there is a stumbling block it is likely to be HATEOAS. Currently we are using  version 0.19.0.RELEASE of org.springframework.hateoas with 2.0.0 being available. Here is the migration guide for reference: https://docs.spring.io/spring-hateoas/docs/current/reference/html/#migrate-to-1.0

We can also remove the thymeleaf dependency.


Update k9s docs

I needed to use k9s for the first time this week. I was unable to follow along the docs so I got help from the team. I've added all the additional info that helped me to access the pod logs via k9s.
Reference Issues or PRs

What does this implement/fix?
Put a x in the boxes that apply

[x] Documentation Update

Testing

[x] Did you test the pull request locally?

Documentation

Access-centered content checklist
Text styling

[x] The content is written with plain language (where relevant).
[x] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[x] All links describe where they link to (for example, check the Nebari website).
[x] This content adheres to the Nebari style guides.

Non-text content

[x] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[x] If there are emojis, there are not more than three in a row.
[x] Don't use flashing GIFs or videos.
[x] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

Thank you, @kcpevey!


feat: Standard Deviation metric for Numeric Field

Tell us about the problem you're trying to solve
As a user, I want to generate the stddev of the numeric column.
Describe the solution you’d like
Tasks:

[ ] Add Standard Deviation metric
[ ] Add docs for the metric

fixed with #108


Search only returns 10 results

Running the search an a model only returns 10 results. Is there any way to set the limit to return more?

10 is default size https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-from-size.html
There is two way to set new size

Using paginate

Book::search('zonga')->paginate(100);

Using search callback

$results = Book::search('zonga', function($client, $body) {
    $body->setSize(100);
    return $client->search(['index' => 'books', 'body' => $body->toArray()]);
})->get();

@matchish How paginations works?

How paginations works?

@ian-patel What do you mean?

and is it possible egger loading?

https://github.com/laravel/scout/pull/92#issuecomment-252427676
Also you can pass callback to query method.
Book::search('harry')->query(function($query) {
    return $query->with('author');
})->paginate(15);


How to chart the data

It may be useful to include links to @pietvandongen's brilliant charting tools in the README.
This PR hotlinks to Piet's example chart image in his batlog2csv repo, but it's also hosted on GitHub so I guess this is ok. Piet, let me know if you don't want your example image here or don't want it hotlinked and I'll change it.

It's fine by me, thanks :)


Revert "fix: Revert "chore: Refactoring multiple environments to use editorId instead of appId""

Reverts appsmithorg/appsmith#29942

Summary by CodeRabbit

Refactor

Streamlined the process for setting workspace and editor IDs across various components and actions.
Enhanced the route matching mechanism for improved navigation within the app.

Bug Fixes

Corrected typos and variable naming inconsistencies to ensure clarity and consistency in the codebase.

Style

Adjusted UI components for better accessibility, including the correct use of Aria attributes.

Chores

Removed unused imports and code to clean up the codebase and improve maintainability.

Documentation

Updated internal documentation to reflect changes in function signatures and payload structures.

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>


➕ Feature: Add a Dedicated Licensing Page Reflecting the "MIT Licence"

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
hey @VaibhavArora314 @akbatra567 and @Ultimateutkarsh11
To provide clear information about the licensing of the website's content and code, we need to add a dedicated "Licensing Page" that reflects the use of the MIT License.
What will I do :

Create Licensing Page 2. Content for Licensing Page
Include a brief introduction explaining the importance of licensing.

Provide the full text of the MIT License.

Will Style the page to Follow the  theme of the website.
Will Add "Licensing" in the Footer, To Navigate to this Separate Page in Legal section.

for ex like this :

please assign me this issue under gssoc'24
Use Case
.
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

There is no need to add a separate page for the MIT License since it is already present in GitHub repo. You can add a link to the License in repo in the footer and policy page.


Bug: add_chps does not add 2020 capacities correctly

The 2020-CHPs already exist as extendable generators in the prenetwork. In add_chps they are meant to be updated with Mastr-(and ppl) data. However, instead of adding them pypsa throws an error and does nothing.
Pypsa < 0.31:
ERROR:pypsa.io:Error, new components for Link are not unique
Pypsa >= 0.31:
WARNING:pypsa.io:Line:1142:The following links are already defined and will be skipped (use overwrite=True to overwrite): DE0 0 urban central gas CHP-2020, DE0 1 urban central gas CHP-2020, DE0 10 urban central gas CHP-2020, DE0 11 urban central gas CHP-2020, DE0 12 urban central gas CHP-2020, DE0 13 urban central gas CHP-2020, DE0 14 urban central gas CHP-2020, DE0 15 urban central gas CHP-2020, DE0 16 urban central gas CHP-2020, DE0 17 urban central gas CHP-2020, DE0 18 urban central gas CHP-2020, DE0 19 urban central gas CHP-2020, DE0 2 urban central gas CHP-2020, DE0 20 urban central gas CHP-2020, DE0 21 urban central gas CHP-2020, DE0 22 urban central gas CHP-2020, DE0 23 urban central gas CHP-2020, DE0 24 urban central gas CHP-2020, DE0 25 urban central gas CHP-2020, DE0 26 urban central gas CHP-2020, DE0 27 urban central gas CHP-2020, DE0 28 urban central gas CHP-2020, DE0 29 urban central gas CHP-2020, DE0 3 urban central gas CHP-2020, DE0 4 urban central gas CHP-2020, DE0 5 urban central gas CHP-2020, DE0 6 urban central gas CHP-2020, DE0 7 urban central gas CHP-2020, DE0 8 urban central gas CHP-2020, DE0 9 urban central gas CHP-2020

Simply setting overwrite=True in pypsa 0.31 correctly adds the existing capacities, however then the generators are no longer extendable. Therefore, the special case that the baseyear matches a grouping_year has to be handled separately. This could possibly be done similar to https://github.com/PyPSA/pypsa-eur/blob/7a4a7c703a972c8c1b703ec8503350c95076dd1b/scripts/add_existing_baseyear.py#L265-L269
A more streamlined treatment of existing capacities, requiring less nested ifs, might be desirable in the mid-term.

It seems that for Germany 2 GW of solid biomass CHP and 9 GW of gas CHP corresponding to 2020 are missing


Reminder to Lint, Docstring, and Reference Code

I thought it would be a good idea to put a reminder to Lint and Docstring our code, as well as include references. These are a not insignificant number of fairly easy points that we want to be sure to get. I do not know if this is the appropriate avenue for this kind of reminder, but it was the best option that I knew of.

Yes I think this seems like a good idea!


Questions about downstream transfer learning & fine-tuning performance.

Hi, @Quan-Sun , @Yuxin-CV and other authors of EVA.
Firstly, thanks for your excellent work and congrats for acceptance & highlight of CVPR'2023.
I am wondering how to use EVA as upstream foundation model to other tasks, such as remote sensing or medical image area. Currently my main idea is beyond "continue training" which means directly use your provided weights to train some specific tasks, I want to follow some methods proved in NLP and computer vision (like Adapter or Visual Prompt Tuing).
I would try to use Adapter mechanism like ViT-Adapter in EVA, do you think it can work? Because ViT-Adapter works in ViT and its performance in Swin Transformer is not as good as ViT (although I don't know why yet).
Also, I am new to foundation model area and my interest is on using foundation model (like EVA) for downstream fine-tuning tasks, do you have some recommended paper or github repositories?
Thanks in advance!
Mengzhang LI

Hello @MengzhangLI,
Thank you for your enthusiasm in our work.
We posit the optimal approach to transferring EVA or any other extensive representations is to end-to-end fine-tune all weights with a meticulous hyperparameter search. However, if resources are limited, we recommend the following two methods to adapt pre-trained EVA for downstream tasks:

Select the largest CLIP vision encoder (e.g. EVA-02-CLIP-E+), freeze all pretrained weights, and add & ft lightweight randomly initialized parameters (i.e. adapters).
Choose a moderately sized MIM pre-trained EVA (e.g. EVA-02-L), and end-to-end fine-tune all pretrained weights for your task of interest (with a meticulous hyperparameter search).

Hi @MengzhangLI. If you were interested in PEFT, I would like to recommend Towards a Unified View of Parameter-Efficient Transfer Learning.


Split postDeploymentRequest in meaningful functions file: deploy.go

Function to deploy resources and job spec is very long and has many different parts. It can split in smaller pieces.

this issue has been addressed and implemented in the main. closing this issue.


Poster abstract for ISB biocuration conference

Description of the issue
I'd like to prepare an abstract to present a poster at the ISB biocuration conference happening 5th-6th of May
Conference details: https://www.biocuration.org/1st-local-uk-biocuration-conference-may-2022/
Acceptance criteria

[ ] An abstract is written
[ ] The abstract is reviewed by @gabsie and any other member team that wants to review
[ ] The abstract is sent and the registration is formalised

The abstract is here https://docs.google.com/document/d/1PEuRu_8GvLFD9dvIaYRwagn-vFxRRF2d11YrRUrmhNA/edit


2023 Sandbox Project Review - Sealer

2023 Sandbox Review for Sealer
https://github.com/cncf/toc/pull/1041

@joshgav I can take this one

TOC has decided to change the way annual project reviews for sandbox projects are conducted and reviewed, and so this review is no longer needed. Thanks anyway @krumware! We'll close this issue now.

TOC has requested this review be completed. @krumware do you have enough information to complete? Would you like to finish this review?

@angellk I can pick this back up 👍 , will ping you on slack

Already finished/obsolete, so will close this.


train_on_inputs clarification

When you say train_on_inputs = False, I presume you mean to mask out the prompt, and train the loss only on the response that the model is supposed to produce.
This is made slightly confusing by the fact that the prompt itself has an "input" field. Signposting would seem to imply that you're only masking out the portion of the json with key "input". This should be changed for brevity.
I propose "train_on_inputs" should be renamed to "train_on_prompt"

Seems like it's masking out the instruction+input part of the tokenized prompt. So the label is correct, but confusing...
def generate_and_tokenize_prompt(data_point):
    full_prompt = prompter.generate_prompt(
        data_point["instruction"],
        data_point["input"],
        data_point["output"],
    )
    tokenized_full_prompt = tokenize(full_prompt)
    if not train_on_inputs:
        user_prompt = prompter.generate_prompt(
            data_point["instruction"], data_point["input"]
        )
        tokenized_user_prompt = tokenize(user_prompt, add_eos_token=False)
        user_prompt_len = len(tokenized_user_prompt["input_ids"])

        tokenized_full_prompt["labels"] = [
            -100
        ] * user_prompt_len + tokenized_full_prompt["labels"][
            user_prompt_len:
        ]  # could be sped up, probably
    return tokenized_full_prompt
    ```

This is still confusing. A simple example would be pleasing.


Upgrade to go control plane v0.10.1

This PR upgrades go-control-plane to v0.10.1 (changelog: v0.10.0, v0.10.1). The upgrade requires some changes in the code, most notably the switch from "github.com/golang/protobuf/proto" to "google.golang.org/protobuf/proto".
/kind feature
/priority important-soon
/assign
Closes #99

/ok-to-test

/lgtm

/approve


Create backup files instead of always overwriting.

Operating system: Linux (Arch, 64-bit)
Python version: 3.6.5
Black version: 18.5b0
Does also happen on master: yes
Black doesn't copy the input file(s) to a backup (eg, by appending ~ to the name), instead always overwrites in-place. This is kind of fine for files that are already managed by a VCS, but for ones outside of it, it will be nice to see what changes have happened and even the possibility to revert in case of bugs in Black itself that may produce invalid code.

If Black discovers it would produce invalid code, it will refuse to save the file. It checks the AST is the same before and after. The only unwanted changes might be in comments and whitespace. I don't want to litter users' directories with backup files.


changed two AOAI alerts to visible with the proper thresholds

Overview/Summary
Replace this with a brief description of what this Pull Request fixes, changes, etc.
This PR fixes/adds/changes/removes

added threshold and severity for both AzureOpenAITimeToResponse and AzureOpenAIProvisionedManagedUtilizationV2
Replace me
Replace me

Breaking Changes

Replace me
Replace me

As part of this Pull Request I have

[ ] Read the Contribution Guide and ensured this PR is compliant with the guide
[ ] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[ ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Ensured PR tests are passing
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

@cassiekays  - since this was verified by the PG, let's changed the verified flag to true


ERR_OSSL_EVP_UNSUPPORTED , Command PhaseScriptExecution failed with a nonzero exit code

Description
Hi I am using react<EMAIL_ADDRESS>it's an old project, but officially it's running

My node version is v18.17.0

And my openssl version : OpenSSL 3.0.10 1 Aug 2023 (Library: OpenSSL 3.0.10 1 Aug 2023)
And I am m1 MacBook Pro user.

and I am continuously getting this error.

 node /Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev false --reset-cache --bundle-output /Users/amitchakraborty/Library/Developer/Xcode/DerivedData/VulcanEleven-fauzipknssuyavfknzrdbgfdkwla/Build/Intermediates.noindex/ArchiveIntermediates/VulcanEleven/BuildProductsPath/ReleaseProduction-iphoneos/main.jsbundle --assets-dest /Users/amitchakraborty/Library/Developer/Xcode/DerivedData/VulcanEleven-fauzipknssuyavfknzrdbgfdkwla/Build/Intermediates.noindex/ArchiveIntermediates/VulcanEleven/BuildProductsPath/ReleaseProduction-iphoneos/VulcanEleven.app --minify false
warning: the transform cache was reset.
                    Welcome to Metro!
              Fast - Scalable - Integrated

watchman warning:  Recrawled this watch 39 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del '/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2' ; watchman watch-project '/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2'`

Recrawled this watch 39 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del '/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2' ; watchman watch-project '/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2'`

Failed to construct transformer:  Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:133:10)
    at stableHash (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro-cache/src/stableHash.js:19:8)
    at Object.getCacheKey (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro-transform-worker/src/index.js:593:7)
    at getTransformCacheKey (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler/getTransformCacheKey.js:24:19)
    at new Transformer (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler/Transformer.js:48:9)
    at /Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/Bundler.js:22:29
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
error Cannot read properties of undefined (reading 'transformFile').
TypeError: Cannot read properties of undefined (reading 'transformFile')
    at Bundler.transformFile (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/Bundler.js:48:30)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.transform (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/lib/transformHelpers.js:101:12)
    at async processModule (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler/traverseDependencies.js:137:18)
    at async traverseDependenciesForSingleFile (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler/traverseDependencies.js:131:3)
    at async Promise.all (index 0)
    at async initialTraverseDependencies (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler/traverseDependencies.js:114:3)
    at async DeltaCalculator._getChangedDependencies (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler/DeltaCalculator.js:164:25)
    at async DeltaCalculator.getDelta (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler/DeltaCalculator.js:94:16)
    at async DeltaBundler.buildGraph (/Users/amitchakraborty/Desktop/Office/React_Native/defi11-react-native-v2/node_modules/metro/src/DeltaBundler.js:50:5)
info Run CLI with --verbose flag for more details.
Command PhaseScriptExecution failed with a nonzero exit code ,

I have reinstalled project several times, cleared  node modes several time
I google tried to find solution although , there I found I have to add export NODE_OPTIONS=--openssl-legacy-provider in ~/.bashrc and ~/.zshrc, Which I did. It worked for react-native run-ios and react-native run-android
**but when I am trying to build from Xcode or I am trying to archive project for test flight I am getting previous error again **

Can you help me to resolve this issue?

Here is my package.json's dependencies

"dependencies": {
		"@biconomy/mexa": "2.0.35",
		"@coinbase/cbpay-js": "^1.6.0",
		"@craftzdog/react-native-buffer": "^6.0.5",
		"@ethereumjs/tx": "^3.3.2",
		"@gorhom/animated-tabbar": "2.1.1",
		"@gorhom/bottom-sheet": "^4",
		"@react-native-clipboard/clipboard": "^1.11.1",
		"@react-native-community/hooks": "^2.8.1",
		"@react-native-community/masked-view": "^0.1.11",
		"@react-native-community/netinfo": "^9.3.0",
		"@react-native-community/slider": "^4.4.2",
		"@react-native-firebase/analytics": "^12.9.3",
		"@react-native-firebase/app": "^12.9.3",
		"@react-native-firebase/dynamic-links": "^12.9.3",
		"@react-native-firebase/messaging": "^12.9.3",
		"@react-navigation/bottom-tabs": "^6.0.5",
		"@react-navigation/core": "^6.0.3",
		"@react-navigation/devtools": "^6.0.10",
		"@react-navigation/native": "^6.0.4",
		"@react-navigation/native-stack": "^6.6.1",
		"@react-navigation/stack": "^5.x",
		"@reduxjs/toolkit": "^1.8.5",

		"@shopify/flash-list": "^1.4.0",
		"@tanstack/react-query": "^4.13.0",
		"@tradle/react-native-http": "^2.0.1",
		"assert": "^1.5.0",
		"axios": "0.27.2",
		"base-64": "^1.0.0",
		"browserify-zlib": "^0.1.4",
		"buffer": "^4.9.2",
		"console-browserify": "^1.2.0",
		"constants-browserify": "^1.0.0",
		"crypto-js": "^4.1.1",
		"dns.js": "^1.0.1",
		"domain-browser": "^1.2.0",
		"ethers": "^5.5.2",
		"events": "^1.1.1",
		"https-browserify": "^0.0.1",
		"lodash.capitalize": "^4.2.1",
		"lodash.find": "^4.6.0",
		"lodash.isempty": "^4.4.0",
		"moti": "^0.20.0",
		"node-libs-browser": "^2.2.1",
		"path-browserify": "^0.0.0",
		"process": "^0.11.10",
		"prop-types": "^15.7.2",
		"punycode": "^1.4.1",
		"querystring-es3": "^0.2.1",
		"react": "17.0.2",
		"react-native": "0.67.5",
		"react-native-app-intro-slider": "^4.0.4",
		"react-native-bouncy-checkbox": "^3.0.2",
		"react-native-checkbox-reanimated": "^0.1.0",
		"react-native-code-push": "^7.0.4",
		"react-native-crypto": "^2.2.0",
		"react-native-device-info": "^10.0.2",
		"react-native-fast-image": "^8.5.11",
		"react-native-file-access": "^2.5.0",
		"react-native-flipper": "0.125.0",
		"react-native-gesture-handler": "2.9.0",
		"react-native-haptic-feedback": "^1.14.0",
		"react-native-inappbrowser-reborn": "^3.7.0",
		"react-native-keyboard-aware-scroll-view": "^0.9.5",
		"react-native-level-fs": "^3.0.1",
		"react-native-linear-gradient": "^2.6.2",
		"react-native-material-menu": "^2.0.0",
		"react-native-mmkv": "2.1.0",
		"react-native-modal": "^13.0.1",
		"react-native-os": "^1.2.6",
		"react-native-permissions": "^3.6.1",
		"react-native-popover-view": "^4.1.0",
		"react-native-quick-base64": "^2.0.5",
		"react-native-randombytes": "^3.6.1",
		"react-native-razorpay": "^2.3.0",
		"react-native-reanimated": "2.8.0",
		"react-native-rename": "^3.2.12",
		"react-native-responsive-fontsize": "^0.5.1",
		"react-native-safe-area-context": "^3.3.2",
		"react-native-screens": "3.9.0",
		"react-native-share": "^7.9.0",
		"react-native-snap-carousel": "^4.0.0-beta.6",
		"react-native-sound": "^0.11.2",
		"react-native-status-bar-height": "^2.6.0",
		"react-native-svg": "^12.1.1",
		"react-native-tcp-socket": "^6.0.2",
		"react-native-toast-message": "^2.1.5",
		"react-native-udp": "^4.1.7",
		"react-native-webview": "^11.26.0",
		"react-redux": "^8.0.2",
		"react-timer-hook": "^3.0.5",
		"readable-stream": "^1.0.33",
		"redux": "^4.2.0",
		"redux-flipper": "^2.0.0",
		"redux-persist": "^6.0.0",
		"stream-browserify": "^3.0.0",
		"string_decoder": "^0.10.31",
		"timers-browserify": "^1.4.2",
		"tty-browserify": "^0.0.0",
		"url": "^0.10.3",
		"util": "^0.10.4",
		"vm-browserify": "^0.0.4",
		"web3": "^1.6.1",
		"zustand": "^4.1.3"
	},
	"devDependencies": {
		"@babel/core": "^7.12.9",
		"@babel/plugin-transform-react-jsx": "^7.14.9",
		"@babel/runtime": "^7.15.4",
		"@react-native-community/eslint-config": "^2.0.0",
		"@types/crypto-js": "^4.1.1",
		"@types/fbemitter": "^2.0.32",
<EMAIL_ADDRESS>"^4.2.7",
<EMAIL_ADDRESS>"^4.6.7",
<EMAIL_ADDRESS>"^4.4.7",
		"@types/node": "^16.11.6",
		"@types/react": "17.0.18",
		"@types/react-native": "^0.66.11",
		"@types/react-native-razorpay": "^2.2.0",
		"@types/react-native-snap-carousel": "^3.8.5",
		"@types/react-redux": "^7.1.18",
		"@types/react-test-renderer": "^17.0.1",
		"babel-jest": "^26.6.3",
		"babel-plugin-module-resolver": "^4.0.0",
		"eslint": "^7.22.0",
		"eslint-config-prettier": "^8.3.0",
		"eslint-import-resolver-babel-module": "^5.1.2",
		"eslint-plugin-import": "^2.24.2",
		"eslint-plugin-jest": "^24.3.5",
		"eslint-plugin-prettier": "^4.0.0",
		"eslint-plugin-react": "^7.26.1",
		"eslint-plugin-simple-import-sort": "^7.0.0",
		"husky": "^7.0.0",
		"identity-obj-proxy": "^3.0.0",
		"jest": "^26.6.3",
		"lint-staged": ">=10",
		"metro-react-native-babel-preset": "^0.66.2",
		"patch-package": "^6.4.7",
		"prettier": "^2.4.1",
		"react-native-clean-project": "^4.0.1",
		"react-native-mmkv-flipper-plugin": "^1.0.0",
		"react-native-svg-transformer": "^1.0.0",
		"react-query-native-devtools": "^4.0.0",
		"react-test-renderer": "17.0.2",
		"rn-nodeify": "^10.3.0",
		"typescript": "^4.4.3"
	},

Here is the screen shot from xcode

I am facing this issue for several day's , but 3month earlier I was't getting this type of issue
React Native Version
0.67.5
Output of npx react-native info
System:
OS: macOS 13.4.1
CPU: (8) arm64 Apple M1 Pro
Memory: 85.23 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.17.0 - /opt/homebrew/opt/node@18/bin/node
Yarn: 3.6.1 - ~/node_modules/.bin/yarn
npm: 9.6.7 - /opt/homebrew/opt/node@18/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
Android SDK:
API Levels: 23, 29, 30, 31, 32, 33
Build Tools: 29.0.0, 29.0.1, 29.0.2, 29.0.3, 30.0.0, 30.0.1, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 32.1.0, 33.0.0
System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs ARM 64 v8a, android-29 | Google APIs Intel x86 Atom, android-30 | Intel x86 Atom_64, android-30 | Google APIs ARM 64 v8a, android-30 | Google APIs Intel x86 Atom, android-31 | Intel x86 Atom_64, android-32 | Google APIs ARM 64 v8a, android-32 | Google APIs Intel x86 Atom_64, android-32 | Google Play ARM 64 v8a, android-32 | Google Play Intel x86 Atom_64, android-33 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8139111
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
Languages:
Java: 11.0.20 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.5 => 0.67.5
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
react-native run-ios is working after I have added export NODE_OPTIONS=--openssl-legacy-provider in ~/.bashrc and ~/.zshrc.

But Xcode=>Product=>[Build / Archive / Analyze]
showing above error.

Snack, screenshot, or link to a repository

and it's private project can share more details..

any fix for this issue? same issue here @techamit95ch

You need to apply the same export NODE_OPTIONS=--openssl-legacy-provider that fixed react-native run-ios to the Xcode shell. You can add this to the "Bundle react native code and images" section under the Build Phases tab.

@patmisch  Thanks is not enough, you really saved my day, working like a charm


Add led / secondary component placement.

Also added minor feature to autodetect keyboard-layout.json in project folder.

Hi there, I've since changed a few things around with the plugin since, could you test and confirm that the led placement doesn't get screwed up by some of the calculation stuff that I did for the diode offset? (matters for rotated layouts) If you can test that it works as intended with non-rotated and rotated layouts (there are two cases: when the first key is rotated, and when it isnt), that should be good. Thanks.


Handling spatial indexes for NULLable POINT columns

👋 Hi there! As I was integrating this package with my application, I found out it's not possible to add a SPATIAL index on a POINT column if it supports NULL values. More info here and here.
Because only some rows in my table have location data associated, querying is slow without a spatial index. It seems as though the suggested way around this is to set a default POINT(0 0) value on all records without location data.
I can do this easily enough with an Eloquent model event:
public static function booted(): void
{
    // When a Model is being created, set its location field to a neutral Point(0 0) if not already set.
    static::creating(static function(Model $model) {
        foreach ($model->getLocationCastedAttributes() as $column) {
            if ($model->{$column} === null) {
                $model->{$column} = new Point();
            }
        }
    });
}

This now allows for spatial indexing to be used. However, the package's scopes become a lot harder to use practically. For example, calling Address::withinDistanceTo('location', new Point(25.45634, 35.54331), 10000000)->get() could incorrectly include records with POINT(0 0) set (or whatever default is used).
I appreciate the HasSpatial trait can be extended, and developers can override each method with an extra $query->whereRaw("ST_ASTEXT({$column}) = 'POINT(0 0)'") clause. Developers could also add their own scope method to their models, but would have to remember to call it every single time, which isn't ideal.
So it would be fantastic if support for this could be built-in natively somehow — especially if more scopes are likely to be added as the roadmap progresses in future.
Thanks for a really useful package! 🚀

Hi @JackWH
Thanks for the feedback. We released a new version which includes filtering 0,0 points in withinDistanceTo() method. Since v1.4.0 it is available.
Best.


Improve non-top-level import/export error, especially for JS

ES imports and exports can only be used at the top level of a module. This is illegal:
function container() {
  import 'fs'
  export { container }
  namespace N { }
}

The current errors for these three statements are vague and, for JS, contain irrelevant terms:
Actual:
(1) "An import declaration can only be used in a namespace or module."
(2) "An export declaration can only be used in a module."
(3) "A namespace declaration is only allowed in a namespace or module."
Expected:
(1) When the node is in a JS file, "An import declaration can only be used at the top level of a module."
Otherwise, "An import declaration can only be used at the top level of a namespace or module."
(2) When the node is in a JS file, "An export declaration can only be used at the top level of a module."
Otherwise, "An export declaration can only be used at the top level of a namespace or module."
(3) "A namespace declaration is only allowed at the top level of a module."
Implementation:
checkGrammarModuleElementContext issues these errors. I don't know whether it's better to make it smarter or just avoid calling it for case (1).

Isn’t export used inside namespaces too?  So (2) should probably be “An export declaration can only be used at the top level of module or namespace.”

Hey everyone, I'd like to take on this issue.

can I work on this issue?

@lokicodedaily sure, although you might want to co-ordinate with @vicente-s.

@fatcerberus Good point. I updated the Expected seciont.

@sandersn
I tried to fix it in #47076, but did I do something wrong in the PR procedure?
I would be grateful for any feedback.

@islandryu I'm backlogged on community PRs. I'll review it when I can.

Thank you @islandryu!


Transformations actions are broken

Create a simple mapping and add an Append transformation.

This is a backward compatibility issue, seems to be a problem with reading old field action format.

Creating a new field action transformation in a fresh mapping - no old files - still fails.

Right, once it reload. The mapping file at backend looks OK until reload. Now backend side deserialization is suspected.

backend side is working fine, but it converts to new @type: actionName style of action description when it serializes it into JSON. So UI had to support it.

There's also an issue with volume conversions with numberic actions.


eWallet: Create asset - UI

When on the initial page of the wallet, the plus button at the bottom takes you to a screen where you can add an asset.

[x] First select a payment provider
[x] Select the asset type (bank account / credit card / ...) depending on the payment provider

[x] Hide this step in case that there is only one option (e.g. GIG tokens)

[x] Select a currency

[x] Hide this step in case the asset type only has one currency option

[x] Additional data depending on the asset type

What's missing:

What to do after the asset was added, but additional actions are needed? Should this be added to the cordova plugin (open webpage and go through the 'create asset' flow on whatever webpage paycash returns)
Implementation of create asset in the cordova plugin & changes to add 'required_action' property to payment provider

You can add the same credit card multiple times in the paycash api

For rivine:

create key pair

name : random uuid
algorithm: ed25519

getAddress

name : random uuid from above
algorithm: ed25519
message: "please enter pin code to create address"
index: 0

Send to server

address: result from getAddress
id: guid


i18n(es): update deploy/cloudflare

Description (required)
updates deploy/cloudflare based on this commit fa387092c1090069c79d15d5caa400ccc736f69b

Related issues & labels (optional)

Closes # N/A
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

es
guides/deploy/cloudflare.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Dynamically convert to Struct？

Is there any plan to dynamically convert each row within excel into a struct-like data type
We can use reflect to scan and convert dynamically, and define the types that need to be converted through configuration.

This issue duplicate with #619. Users can easily make this wrapper and even create their own complex nested structure. I didn't suggest introducing this feature to make the library core and easy.

I will close this issue. If you have any questions, please let me know.


sharedpreferences does not exist after upgrading flutter and shared_preferences to version 2.2.2

Steps to reproduce
Update to latest Dart , Flutter versions and add dependency   shared_preferences: ^2.2.2. Implement a simple feature using it. Now the Compiler will throw the following error.
/Users/XX/XX/XXX/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:24: error: package io.flutter.plugins.sharedpreferences does not exist
flutterEngine.getPlugins().add(new io.flutter.plugins.sharedpreferences.SharedPreferencesPlugin());
Expected results
Implemented Method to work.
Actual results
Error as follows:
/Users/XX/XX/XXX/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:24: error: package io.flutter.plugins.sharedpreferences does not exist
flutterEngine.getPlugins().add(new io.flutter.plugins.sharedpreferences.SharedPreferencesPlugin());
Code sample
Code sample
import 'package:shared_preferences/shared_preferences.dart';

class PreferencesUtil {
  static late SharedPreferences _preferences;
  static const languageSelected = 'language_selected';

  static Future init() async {
    SharedPreferences _preferences = await SharedPreferences.getInstance();
  }

  static Future setLangOption(lang) async {
    _preferences.setString(languageSelected, lang);
    print("Saved to Preference");
  }

  static Future getLangOption(lang) async {
    _preferences.getString(languageSelected);
  }
}

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
Running Gradle task 'assembleDebug'...
/Users/XX/XX/XX/XX/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:24: error: package io.flutter.plugins.sharedpreferences does not exist
      flutterEngine.getPlugins().add(new io.flutter.plugins.sharedpreferences.SharedPreferencesPlugin());
                                                                             ^
1 error

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3s
Error: Gradle task assembleDebug failed with exit code 1

Flutter Doctor output
Doctor output
 flutter doctor -v
[✓] Flutter (Channel beta, 3.19.0-0.3.pre, on macOS 14.2.1 23C71 darwin-arm64, locale en-IN)
    • Flutter version 3.19.0-0.3.pre on channel beta at /Users/XX/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1b197762c5 (6 days ago), 2024-01-25 22:23:26 -0800
    • Engine revision 968e2945c7
    • Dart version 3.3.0 (build 3.3.0-279.2.beta)
    • DevTools version 2.31.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/XX/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] IntelliJ IDEA Community Edition (version 2023.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 77.0.1
    • Dart plugin version 233.13135.65

[✓] VS Code (version 1.85.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554             • android-arm64  • Android 14 (API 34) (emulator)
    • iPhone 12 (mobile)  • 00008101-000E35321E82001E • ios            • iOS 17.3 21D50
    • macOS (desktop)             • macos                     • darwin-arm64   • macOS 14.2.1 23C71 darwin-arm64
    • Chrome (web)                • chrome                    • web-javascript • Google Chrome 120.0.6099.234

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Duplicate of https://github.com/flutter/flutter/issues/141940


space

[ ] This patch includes any updated documentation of the proposed changes
[ ] This patch includes tests that verify the proposed changes work as expected

Codecov Report

Merging #1016 into master will decrease coverage by 1.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1016      +/-   ##
==========================================
- Coverage   78.23%   77.14%   -1.09%
==========================================
  Files          52       52
  Lines        5609     5609
==========================================
- Hits         4388     4327      -61
- Misses       1221     1282      +61

Impacted Files
Coverage Δ

vent/helpers/meta.py
73.73% <ø> (ø)
:arrow_up:

vent/menus/ntap.py
24% <0%> (-33.6%)
:arrow_down:

vent/core/network_tap/ncontrol/rest/nlist.py
66.66% <0%> (-33.34%)
:arrow_down:

vent/api/actions.py
76.33% <0%> (-1.91%)
:arrow_down:

vent/menus/main.py
77.89% <0%> (-0.53%)
:arrow_down:

vent/api/plugins.py
78.96% <0%> (+0.86%)
:arrow_up:

Continue to review full report at Codecov.

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


Implement/Update POSIX mutex APIs

Add

I will add more code to test case and mutex.c. Pushed early so that  I can fix review comment along with developing rest of code.

Codecov Report

Merging #7038 into master will decrease coverage by 0.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7038      +/-   ##
==========================================
- Coverage   58.58%   58.21%   -0.37%
==========================================
  Files         463      438      -25
  Lines       47389    46189    -1200
  Branches     8786     8594     -192
==========================================
- Hits        27762    26890     -872
+ Misses      15795    15578     -217
+ Partials     3832     3721     -111

Impacted Files
Coverage Δ

tests/posix/pthread_equal/src/pthread_equal.c

tests/posix/timer/src/posix_timer.c

lib/posix/pthread.c

include/posix/posix_sched.h

tests/posix/clock/src/posix_clock.c

lib/posix/pthread_barrier.c

tests/posix/semaphore/src/sem.c

lib/posix/mqueue.c

tests/posix/mqueue/src/mqueue_test.c

tests/posix/posix_checks/src/posix_checks.c

... and 12 more

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 c542c0e...fd71696. Read the comment docs.

@laperie Can you please review this ? If looks then we can merge this one.

@lpereira Can you please review this ? If looks then we can merge this one.

@lpereira I have updated changes. Can you please have a look ?

@andyross @lpereira
I think the reason for race condition here is that we are using irq_lock and k_sem_take togeather. From the current implementation, we are using k_sem_take for blocking the calling thread and using  irq_lock to protect the owner and lock_count variables, with this approach(irq_lock + sem) we cannot solve both race condition and deadlock scenarios.
I think it’s better to get rid of the semaphore and use irq_lock to protect the mutex data and use _pend_current_thread() to block the calling thread. With this approach, we can avoid race and deadlock conditions and the size of the mutex will be lesser than the original.
Punit will push the changes, Please have a look into the changes and let us know the feedback.

@andyross @lpereira I have updated as per Rama's suggestions. Thank for your time @ramakrishnapallala

I have removed usage of semaphore itself and reduced struct size of posix mutex. Hope it looks fine now. Thank a lot for review @andyross  @lpereira Let me know what do you think about new changes.

@andrewboie @nashif  Updated changes as suggested. Thank you for feedback guys


README: Small improvements

mention GitLab in first paragraph
Fix markdown syntax when describing env variable names
Add paragraph to document detect_credential() failure modes

The last one is most debatable: it's essentially API documentation but considering there
is only one method in the API, including it in the README here might be reasonable.
Fixes #125.

The last one is most debatable: it's essentially API documentation but considering there
is only one method in the API, including it in the README here might be reasonable.

Looks good to me -- we don't have any other public docs here, so putting this in the README seems appropriate 🙂

/gcbrun

/gcbrun


ISSUE-3: ROUGH DRAFT trigger monitorSubmissionResult() on ctrl + enter by hooking into network requests

PR is not merge ready. Just submitting as an idea.
fix https://github.com/HaolinZhong/PMCA/issues/3

Thanks for the PR, brilliant idea! I will try to merge it within next 2 versions.


docker_26: 26.0.0 -> 26.1.2

Description of changes
https://docs.docker.com/engine/release-notes/26.0/
https://docs.docker.com/engine/release-notes/26.1/
Versions taken from: https://github.com/moby/moby/tree/v26.1.2/hack/dockerfile/install
Fixes https://github.com/moby/moby/security/advisories/GHSA-x84c-p2g9-rqv9

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I only find a new feature in https://docs.docker.com/engine/release-notes/26.1/, no breaking changes from what I can tell.

Seeking feedback from @wegank & @Mic92 - what do you think? I'm open for feedback and switching this to 26.0.2 if desired.

@wegank and @LeSuisse You seem to have different point of view, what do we do here?

If that's approved by a RM it's fine by me.
I tend to be quite prudent with Docker upgrades, the high level changelog does not show everything and going through all the parts that are stitched together is quite annoying.


env vars

canonical url + redmine id need to be set as env

also the baseurl for the page gets momentarily set in metadata.config.ts, should be imported

this is working now, the vars had to be defined in interface & it was just a str


Retainer page lists items in a different order than the game

Currently when using the retainers page on the site & in the game they do not match


ziti-edge-tunnel updated to v1.0.3/c sdk v1.0.4 / tlsuv v0.29.5

closed by a different pr i just pusehd through


MetaMorpheus Add for maxThreads in MzLib change

#1290

Build eroor occurs in overload method from mzLib in the LoadFile method of MyFileManager.cs