Fix incorrect behaviour on Windows related to stdio pipes being read-write

Unfortunately if we always always create the stdio pipes as R+W (instead of only R for stdin, and only W for stdout and stderr) child processes on windows start to behave incorrectly. For example, if you spawn the 'cat' program, write to it and then shutdown its stdin, the correct behaviour is for the child to receive EOF and exit. But if stdin is RW the child never exits on Windows, and you have to kill the process to force it to exit. Changing the stdin pipe to only UV_CREATE_PIPE|UV_READABLE_PIPE fixes the problem.
The current solution assumes only the standard stdio fd's (0-2) are used. A more flexible solution may be in order, but would require an API change.

We should probably use read/write for fds above 2 right?
Cool, that should cover all use cases... I'll send another commit shortly.

If everything is alright, do you mind uploading a new LuaRocks release? I'll need it to fix my AppVeyor. Thanks!

Thanks for fixing things on windows.  I really want luv to be stable and supported on windows, but I don't have the time or resources to do that properly.  Your help is greatly appreciated.  I'll publish a new rock shortly.

Published to github and luarocks.

https://github.com/luvit/luv/releases/tag/1.8.0-2
http://luarocks.org/modules/creationix/luv/1.8.0-2

Let me know if this works.

Thank you, everything is working now! I'm happy to help, thanks for being receptive :+1:
I know Windows is productivity-sucking black hole if you're used to developing on Linux/OSX. I'm on OSX but since so many people still use Windows (unfortunately), I'm willing to do the dirty work


Webcam upside down on AppleTV

My webcam image is only upside down on AppleTV. In OctoPod iPhone app, the image is fine. In the regular OctoPrint web interface, the image is fine.

Hi @mattadata ,
Thanks for reporting this issue. I did the following and it worked for me (though I found another bug)

Go to OctoPrint settings and flipped the camera
Camera looks ok in OctoPrint (as you said)
Camera initially looks incorrect in Apple TV
closed the Apple TV app and opened it again
Camera looks ok in Apple TV

Screenshot step 1:

Screenshot step 2:

Screenshot step 5:

I will see how I can fix step 3 since that is not working as desired.
Did you follow similar steps? If not, could you give this a try? Apple TV should respect whatever settings you have in OctoPrint. Currently you need to open the Apple TV app twice for the modification to take effect. After that it works fine

Hi @mattadata ,
Thanks for reporting this issue. I did the following and it worked for me (though I found another bug)

Go to OctoPrint settings and flipped the camera
Camera looks ok in OctoPrint (as you said)
Camera initially looks incorrect in Apple TV
closed the Apple TV app and opened it again
Camera looks ok in Apple TV

Screenshot step 1:

Screenshot step 2:

Screenshot step 5:

I will see how I can fix step 3 since that is not working as desired.
Did you follow similar steps? If not, could you give this a try? Apple TV should respect whatever settings you have in OctoPrint. Currently you need to open the Apple TV app twice for the modification to take effect. After that it works fine

Thanks. That solved it. I just had to open the AppleTV app a few times and then it showed the correct video.

Thanks. That solved it. I just had to open the AppleTV app a few times and then it showed the correct video.

Next release will just work without having to close the app. BTW, since I was working on this part of the app .... I added more improvements to make the experience more seamless. Will open new tickets for the improvements.


Different build environments.

Please provide a sample which has different values for different build variants.

I'm not sure I get what you mean. Please elaborate.

 productFlavors {
    dev {
        buildConfigField 'String', 'EXAMPLE_0', '"some value 000"'
        buildConfigField 'boolean', 'EXAMPLE_1', 'true'
    }
    prod {
        buildConfigField 'String', 'EXAMPLE_0', 'some value 111'
        buildConfigField 'boolean', 'EXAMPLE_1', '"false"'
    }

How can I replace above code by paperwork?
Different values of same variables for different productFlavors

Right. I'm not sure if it's even theoretically possible to do that automatically, as you define your flavors / buildtypes in the android block. Maybe there's a workaround to access the current one outside of that scope, and someone will correct me on this.
What you can do however, is you could have a plugin config like:
paperwork {
    set = [
        debugKey1: "debug value",
        prodKey1: "prod value",
    ]
}

And then at runtime access it:
paperwork.get(BuildConfig.BUILD_TYPE + "Key1");

The plugin config supports arbitrary embedded structures, so in theory you could group all your debug keys in another set on level deeper without resorting to string concatenation. On the other hand, the runtime component only supports accessing a flat structure as of the moment.

I tried putting:
paperwork {
  set = [
     someKey = "some value"
  ]
}

Inside the debug block and then again in the release block to have a switch based on build type. Unfortunately, doing it this way means you have to duplicate all the keys that you want for both build types, as each paperwork block overwrites the previous.
I cannot use the prefix approach due to having another build type for development environment and would also rather not use a prefix-based approach.
Would it be possible to make it so that you can have multiple different paperwork blocks and have all the variables be added to the JSON file?

@andrewlord1990 I think what you want to achieve has to do more with groovy than with paperwork, i.e. merging those arrays. Also, why not try the same key approach, but instead of literals, you could have function calls on the right side, then override those functions per environment. I haven't checked, but it would make sense if it worked.

Okay thanks, interesting idea. Will try that out when I get a chance.
On 29 Jan 2017 15:07, "Zsolt Kocsi"<EMAIL_ADDRESS>wrote:

@andrewlord1990 https://github.com/andrewlord1990 I think what you want
to achieve has to do more with groovy than with paperwork, i.e. merging
those arrays. Also, why not try the same key approach, but instead of
literals, you could have function calls on the right side, then override
those functions per environment. I haven't checked, but it would make sense
if it worked.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zsoltk/paperwork/issues/35#issuecomment-275919540,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKy1k_1JR3zMH8mmQioXXHL0hkr5Dfcrks5rXKswgaJpZM4HK1_g
.


Bug: Not responsive for smaller screen

Describe the bug
Fix the responsiveness of the web app for all screen views.
Use flex, stack row & column according to the screen size.
To Reproduce
Steps to reproduce the behavior:

Go to https://sql-editor-online.vercel.app/
Switch to mobile view.
See the components overlaying over each other and being unresponsive.

Expected behavior
Fix the responsiveness for each component for all screen views. (particularly mobile view)
Screenshots

@prash240303 idk how this issue occurred, earlier it was pixel-perfect responsive maybe the new merge/changes had this issue.

Can I pick this up?

Go ahead!


Typo

It should probably be "determine if"
https://github.com/paoloricciuti/bsky-svelte-feed/blob/3c00cec8618a2e0ee00ac8357d7b11341afc4694/src/ai.ts#L22

Uh thanks...will fix 😄


tweaks upgrade API

Coverage decreased (-0.2%) to 67.917% when pulling e8062c90aa201a2ff3ac762ee774bc61de9773b5 on upgrade into d8831523eeade6fa8b1501ffa9283af38a5bb77f on master.


Specification: OpenSSF Compliant Automated Vulnerability Fix Campaign

The following proposed specification is up for review:
https://docs.google.com/document/d/1_QwN7yQXWGM2tJaostIRNqyZIhVceVlIyXqCrSdC4E8

Have been working on an aligned RFC (still WIP) over here: https://github.com/ietf-scitt/use-cases/pull/18
Seems like transparency services will be where we log the end assessment of is vuln/is not vuln.


[Bug]: Desktop is misspelled as "desktp"

What version of Catnap are you running?
Not applicable, considering the typo is present in repo.
Describe the bug:
In config/config.toml, desktop is misspelled as "desktp".
Screenshots:
N/A
Device:

OS: NixOS
WM: KDE Plasma 6
TERMINAL: Alacritty

Additional context:
N/A

Thx :)


⚠ Bofrost.lu has degraded performance

In d84ec66, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1247 ms

Resolved: Bofrost.lu performance has improved in 99bb2e4 after 6 minutes.


Children not set inside connected callback

If you are trying to access the children of the current element inside the connected-Hook, the HTMLCollection will be empty.
    connected() {
        this._children = [ ...this.children ];
        console.log(this._children, this.children );
    }

But if we are requesting an animation frame it works and the array is not empty anymore
    connected() {
        requestAnimationFrame(() => {
            this._children = [ ...this.children ];
            console.log(this._children, this.children );
        });
    }

This occured due to early script execution time. It seems like the browser does not know the children of a custom element in the connectedCallback when the script is executed before the elements dom position.
`

`


Update Readme to reflect latest onboarding process

Even though the on-boarding process is much simpler these days, if new users don't know about the site, they're never going to use it. This update points them straight to it.
I would also recommend adding it to the "site" field for this repo.

Good call. Added

@neauoire btw, I accidentally had the wrong URL in the PR. So the URL in the github site field should actually be https://client-neauoire.hashbase.io/
My Bad 🙈


BUG Only allow the owner of a LoginSession to view/delete it

Fixes #57

Found an issue during manual testing, noticed that a non-admin user isn't able to revoke their own sessions.  When I attempt to revoke a session I see a red toast "Could not log out of session. Try again later"

I don't think it's a CanView/CanDelete problem. Checked out the 1 branch and got the same result.
The problem is probably that non-admin users are not allowed to interact with the LoginSessionController.

Have agreed to split of non-admin revoking as a separate issue https://github.com/silverstripe/silverstripe-session-manager/issues/67


Ide Helper Not Working like it was before

i Have a working app in laravel 4 with ide helper 4.*  and another one in laravel 5 stable version.
ide helper works good enough in laravel 4 and php storm 8 , but in laravel 5 its not working good , i mean all commands are not there ,
for example there is no auto complete for : User::where
or any model::where
I dont know if it helps but in laravel 4 with php storm , when i ctrl+click on a method for example on where
in User::where , phpstorm takes me to _ide_helper with that function , but now in l5 when i click on for example with in User::with , phpstorm takes me to \vendor\laravel\framework ... not  _ide_helper.php

Probably because you are extending the real Model class, not the Eloquent facade.

Thats Right , Somehow i remember a thing that its better to user model @taylorotwell , not Eloquent.
am right or there is absolutely no difference?

Eloquent is just an alias to Illuminate\Database\Eloquent\Model, so it doesn't matter.
If you don't use the ide-helper, you should probably use the Model directly, because you get some autocompletion at least. If you do use the ide-helper, using the Facade can give you autocompletion for some magic methods also.

Thanks @barryvdh


Ensure the CloudWatch Log Group is encrypted by KMS/CMK

Create the possibility to encrypt the VCP Flow Logs Cloudwatch Log Group using KMS Customer Managed Keys (CMK)
Types of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING.md doc.
[X] I have added necessary documentation (if appropriate).
[ ] Any dependent changes have been merged and published in downstream modules.

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@alexandrealvao ready to be merged!


Tutorial skip button.

In accordance with issue #224

My android studio is not working properly, will make a new PR asap.

Will make a new PR.


Add a deprecation notice to the --blockEdit and --blockDelete options for spo list retentionlabel add

Add a deprecation notice to the --blockEdit and --blockDelete options for spo list retentionlabel add
Check this related issue that explains why these options should be removed and that this is a breaking change: https://github.com/pnp/cli-microsoft365/issues/4207

You sure can!

Hi @martinlingstuyl
We should add a deprecation notice to the spo list retentionlabel set command, instead spo list retentionlabel add ?
We do not have spo list retentionlabel add command.

No, to the Alias spo list label set

Sorry, you are correct. Typo by me

Wow @milanholemans, that was fast. I was still closing and addinglabels :-)

Thought you forgot it, sorry! 😂


Run pronto on GitHub Actions without any reporting

In #401 we discussed that there
currently is no 100% safe way to run pronto on pull_request_target
actions we can not send any reports to the GitHub pull request.
This simple action will show up as a failed check. The offences then
need to be viewed in the action output.

The test commit that included a rubocop offense failed the action as expected: https://github.com/prontolabs/pronto/runs/2041862031?check_suite_focus=true#step:4:228

I removed 2.4 from the test matrix because of this failures https://github.com/prontolabs/pronto/runs/2041832382?check_suite_focus=true#step:3:33

Makes sense about the GitHub CI check for now! For the Ruby 2.4 failure, can't we override the gem version for 2.4 like it's done here? We'll have to add support for Gemfile.local in Gemfile but I think that's fine.

We can, I simply wasn't aware of that trick 😄


[WEB] Quick install/download

Install and load plugins to the mc server by one click.

Also make IDs searchable in the plugins tab and maybe even add a section to download external links.
And maybe later you could add a command (providing the spigot ID, name and author or a static link to an external site) in the console, followed by an ingame command.

dropped


feature: cache the matched uri to ctx .

https://github.com/api7/lua-resty-radixtree/pull/38
it has been implemented at resty-radixtree, so we can close this PR now


Feature: add custom date format

This feature enable a  user to add a custom date format.
i.e yyy-MM-dd HH:mm:ss result to 2023-02-28 14:25:57.
dd/MM/YYY HH:mm:ss (O) results to 28/02/2023 14:25:57 (GMT +3),
This is based on the  date-fns format

Needs actually importing showErrorMessage and a lint pass.

I have imported the showErrorMessage from the @jupyterlab/apputils
I also include where the error is from in the title of the dialog box. This will help the user identify where the error is from when they refresh the browser.


Prototype of generic view trait

Use type system hackery to represent a generic bound over traits.
Note: this patch just makes the view itself generic, and doesn't address any of the supporting machinery (ViewSequence, AnyView, etc).

I am closing this because I think a macro based approach (#61) is the way forward. In particular, a showstopper is that the trait cannot be made generic over both Send and !Send, and that is required to support both efficient (multithreaded) native and Web cases.


Brazil server routes are not optimized

I made a test with NextDNS routing trough Brazil and it seems the secondary DNS is much better than primary

I would run the diagnostic tool i found here https://help.nextdns.io/t/y4hmvcx/report-network-latency-issue
but i scanned it with virustotal and found 19 detections

As mentioned before, virus detectors are confused by all the IPs this program is measuring. The tool is open source, you can inspect its code and even compile it yourself if not sure.

Closing as this repository is not meant to post routing issues.


mixed tags

Hi there,
dexml does not seem to support mixed sub-tags. It ends generating lists (or dicts) at the first differing tag, for example:
import dexml

class Sub1(dexml.Model):
    arg = dexml.fields.String()

class Sub2(dexml.Model):
    arg = dexml.fields.String()

class Main(dexml.Model):
    sub1 = dexml.fields.List(Sub1)
    sub2 = dexml.fields.List(Sub2)

root = Main.parse("""
<Main>
    <Sub1 arg="a"></Sub1>
    <Sub1 arg="b"></Sub1>
    <Sub2 arg="c"></Sub2>
    <Sub1 arg="d"></Sub1>
</Main>
""")

assert(len(root.sub1) == 3)
assert(len(root.sub2) == 1)

I'd expect len(root.sub1) to be three, but it's two. The last Sub1 does not seem to be parsed. Is that a bug or a feature? Unfortunately i do not have control over the layout of the xml i'm trying to parse

Thanks for reaching out. Unfortunately I am no longer actively maintaining this project, so I'm going to move it into archive mode:
https://rfk.id.au/blog/entry/archiving-open-source-projects/


[WIP] ADR 8 - Reserving paths in Publishing API

I've flagged this as a work in progress as we've currently got 3 ADR's on the go so this one will slip onto on hold for time being.
👉 View rendered version 👈
This ADR is an attempt to try formulate a plan around a path reservation strategy. This ADR attempts to lay out both the goals we want to aim for and a proposed solution. In reviewing it'd be good to focus first on the goals rather than the solution as if we change the goals the solution proposal would need re-thinking.
Reasons to think about doing this:

We currently have the non-optimal requirement that asks a user to change a title if they try use a title that already exists
We've had a number of conflicts from Publishing API: https://sentry.io/govuk/app-content-publisher/issues/682788212/

Related stories/issues on trello: https://trello.com/c/snc4ihBE/575-delegate-unique-basepath-generation-to-the-publishing-api, https://trello.com/c/NPBZppvg/604-prevent-changes-to-the-basepath-after-its-been-published

This clearly isn't a work in progress anymore so I'm going to close it.


Chef Provisioning SSH incorrectly specifying machine name when used in Machine Batch.

Creating machines in chef-provisioning-ssh, I have the following
osi_list = [ "myvm01", "myothervm01", "vm03" ]
machine_batch "my-machine-batch" do
  osi_list.each do | osi |
    machine "my_machine" do
      name osi
      machine_options ({ ...  <add all transport options with host = osi } )
      action :converge
    end
  end

When this runs, it creates machines listed above, however, the machine name (node defined in Chef) (as defined in the corresponding machine json in /provisioning/ssh) does not correspond to the IP address or host entry added to the JSON object that is created, so machines are bootstrapped incorrectly.
Has anyone seen issues with Machine Batch in this scenario?

Looks like this is a bug. John Keiser and Taylor Ball looking at it.


[Tour of Beam][Frontend] Content Tree and SDK models (#23316)

Resolves https://github.com/apache/beam/issues/23316

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @damondouglas

Added a simple manual to README.
#23378 comes with Gradle tasks that make building and testing even simpler. When they are approved, we will make similar ones here. So not expanding on testing for now.

Friday's demo is my local WIP, it is not in this PR. So we will move the Run button there, not here.


Windows.old folder issue

Somehow after new installation by using the xml file generated by the website, there is an empty Windows.old folder under C partition.
Also, I put a registry key entry under "Scripts to run whenever a user logs on for the first time" section, but it seems not working for new (network) users' first login.

When performing an unattended installation e.g. of Windows 11 24H2 from the Windows11_InsiderPreview_Client_x64_en-us_26100.iso image, I also see an empty C:\Windows.old folder. However, this folder also appears when no autounattend.xml file is used at all, so this seems to be an oversight on Microsoft's part.
All custom scripts are stored in C:\Windows\Setup\Scripts. If you entered only one .reg file, its path will be C:\Windows\Setup\Scripts\unattend-01.reg. To analyze the problem, please login with the new account, then open the command prompt, type reg.exe import "C:\Windows\Setup\Scripts\unattend-01.reg" and verify the output is The operation completed successfully.

Just verified the issue is not from the configuration file, it was restricted by GP: ERROR: Registry editing has been disabled by your administrator.


"name" and "value" keys unnecessarily verbose?

Hi again!
Is there any particular reason why the "name" and "value" keys are used for labels, annotations, isolators, eventHandlers and environment variable lists? If those things were objects themselves, instead of lists, the ACI image schema would be much simpler and less verbose.
For instance, if you made the lists into objects for the above mentioned attributes of the image schema, you would go from this (from the examples):
{
    "acKind": "ImageManifest",
    "acVersion": "0.7.0",
    "name": "example.com/reduce-worker",
    "labels": [
        {
            "name": "version",
            "value": "1.0.0"
        },
        {
            "name": "arch",
            "value": "amd64"
        },
        {
            "name": "os",
            "value": "linux"
        }
    ],
    "app": {
        "exec": [
            "/usr/bin/reduce-worker",
            "--quiet"
        ],
        "user": "100",
        "group": "300",
        "supplementaryGids": [
                400,
                500
        ],
        "eventHandlers": [
            {
                "exec": [
                    "/usr/bin/data-downloader"
                ],
                "name": "pre-start"
            },
            {
                "exec": [
                    "/usr/bin/deregister-worker",
                    "--verbose"
                ],
                "name": "post-stop"
            }
        ],
        "workingDirectory": "/opt/work",
        "environment": [
            {
                "name": "REDUCE_WORKER_DEBUG",
                "value": "true"
            }
        ],
        "isolators": [
            {
                "name": "resource/cpu",
                "value": {
                    "request": "250m",
                    "limit": "500m"
                }
            },
            {
                "name": "resource/memory",
                "value": {
                    "request": "1G",
                    "limit": "2G"
                }
            },
            {
                "name": "os/linux/capabilities-retain-set",
                "value": {
                    "set": ["CAP_NET_BIND_SERVICE"]
                }
            }
        ],
        "mountPoints": [
            {
                "name": "work",
                "path": "/var/lib/work",
                "readOnly": false
            }
        ],
        "ports": [
            {
                "name": "health",
                "port": 4000,
                "protocol": "tcp",
                "socketActivated": true
            },
            {
                "name": "ftp-data",
                "port": 20000,
                "count": 1000,
                "protocol": "tcp"
            }
        ]
    },
    "dependencies": [
        {
            "imageName": "example.com/reduce-worker-base",
            "imageID": "sha512-...",
            "labels": [
                {
                    "name": "os",
                    "value": "linux"
                },
                {
                    "name": "env",
                    "value": "canary"
                }
            ],
            "size": 22017258
        }
    ],
    "pathWhitelist": [
        "/etc/ca/example.com/crt",
        "/usr/bin/map-reduce-worker",
        "/opt/libs/reduce-toolkit.so",
        "/etc/reduce-worker.conf",
        "/etc/systemd/system/"
    ],
    "annotations": [
        {
            "name": "authors",
            "value": "Carly Container<EMAIL_ADDRESS>Nat Network <[nat@example.com](mailto:nat@example.com)>"
        },
        {
            "name": "created",
            "value": "2014-10-27T19:32:27.67021798Z"
        },
        {
            "name": "documentation",
            "value": "https://example.com/docs"
        },
        {
            "name": "homepage",
            "value": "https://example.com"
        }
    ]
}

to this:
{
    "acKind": "ImageManifest",
    "acVersion": "0.7.0",
    "name": "example.com/reduce-worker",
    "labels": {
        "version": "1.0.0",
        "arch": "amd64",
        "os": "linux"
    },
    "app": {
        "exec": [
            "/usr/bin/reduce-worker",
            "--quiet"
        ],
        "user": "100",
        "group": "300",
        "supplementaryGids": [
                400,
                500
        ],
        "eventHandlers": {
            "pre-start": {
                "exec": [
                    "/usr/bin/data-downloader"
                ]
            },
            "post-stop": {
                "exec": [
                    "/usr/bin/deregister-worker",
                    "--verbose"
                ]
            }
        },
        "workingDirectory": "/opt/work",
        "environment": {
            "REDUCE_WORKER_DEBUG": "true"
        },
        "isolators": {
            "resource/cpu": {
                    "request": "250m",
                    "limit": "500m"
            },
            "resource/memory": {
                    "request": "1G",
                    "limit": "2G"
            },
            "os/linux/capabilities-retain-set": {
                "set": ["CAP_NET_BIND_SERVICE"]
            }
        },
        "mountPoints": {
            "work": {
                "path": "/var/lib/work",
                "readOnly": false
            }
        },
        "ports": {
            "health": {
                "port": 4000,
                "protocol": "tcp",
                "socketActivated": true
            },
            "ftp-data": {
                "port": 20000,
                "count": 1000,
                "protocol": "tcp"
            }
        }
    },
    "dependencies": [
        {
            "imageName": "example.com/reduce-worker-base",
            "imageID": "sha512-...",
            "labels": {
                "os": "linux",
                "env": "canary"
            },
            "size": 22017258
        }
    ],
    "pathWhitelist": [
        "/etc/ca/example.com/crt",
        "/usr/bin/map-reduce-worker",
        "/opt/libs/reduce-toolkit.so",
        "/etc/reduce-worker.conf",
        "/etc/systemd/system/"
    ],
    "annotations": {
        "authors": "Carly Container<EMAIL_ADDRESS>Nat Network <[nat@example.com](mailto:nat@example.com)>",
        "created": "2014-10-27T19:32:27.67021798Z",
        "documentation": "https://example.com/docs",
        "homepage": "https://example.com"
    }
}

The latter doesn't lose any information, and is significantly less verbose (and IMHO easier to read).
Thoughts?
Best,
-jay

Hmm, this has been discussed before in #58, #62, #64, and #84 and we landed on the more verbose format. To reiterate here:
It maintains that field names on the left are schema, values on the right are user values. Behavior during duplicate JSON object field names are not part of the JSON spec and may be handled differently based on the library being used...but generally an ill-formed manifest will have duplicate errors swallowed during JSON parsing. Some label names are not valid JSON object member names.

OK, that's good information, thank you. I guess I don't really see why AppC would use JSON as its file format and then allow "label names [to not be] valid JSON object member names." That doesn't make a whole lot of sense to me. Why bother using JSON at all, then, if you're just going to override what JSON means with the parser.go implementation? Or, put another way, what does not conforming to the JSON spec give AppC?

I guess I don't really see why AppC would use JSON as its file format and then allow "label names [to not be] valid JSON object member names." That doesn't make a whole lot of sense to me. Why bother using JSON at all, then, if you're just going to override what JSON means with the parser.go implementation? Or, put another way, what does not conforming to the JSON spec give AppC?

I'm a bit confused by @cdaylward's point here, as I don't know of cases where label names are invalid member names.
As justification for this schema I would lean more on his other points with respect to the field name/user value split.


Support arrow readers for strings with DELTA_BYTE_ARRAY encoding

Which issue does this PR close?
Closes #708 .
Rationale for this change
This allow to read parquet files that use the specified encoding.
What changes are included in this PR?
We wrap existing code to read the  into ValueDecoder.
Also added some machinery to write and read parquet files from memory. This seems generally useful, but happy to remove it from this PR if that makes sense.
Are there any user-facing changes?
No, it's a bugfix.

Codecov Report

Merging #709 (f578ef3) into master (8308615) will increase coverage by 0.01%.
The diff coverage is 93.44%.

:exclamation: Current head f578ef3 differs from pull request most recent head f438f72. Consider uploading reports for the commit f438f72 to get more accurate results

@@            Coverage Diff             @@
##           master     #709      +/-   ##
==========================================
+ Coverage   82.46%   82.47%   +0.01%
==========================================
  Files         168      168
  Lines       47419    47480      +61
==========================================
+ Hits        39104    39160      +56
- Misses       8315     8320       +5

Impacted Files
Coverage Δ

parquet/src/arrow/arrow_array_reader.rs
79.71% <93.44%> (+1.28%)
:arrow_up:

parquet/src/encodings/encoding.rs
94.48% <0.00%> (-0.20%)
:arrow_down:

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 8308615...f438f72. Read the comment docs.

Thanks for the quick response! Here's an updated version.


Please advise which Chrome version above supports pdf.js？thanks！

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:  android browser （chorme57.0）
Operating system and its version: android 6.0
PDF.js version:  2.6.347
Is a browser extension: No

Steps to reproduce the problem:

first，this true problem is some characters are missing in mobile browser rendering,
2.For details, I am using PDFJS-dist. In the same mobile phone, the WeChat browser is fine, but the characters are lost in the mobile browser. According to UA, the difference between the two browsers is that the former is Chorme 77, and the latter is Chrome57.So I think it might be a Chrome version problem, which Chrome version is not supported?Sincerely thank you

What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Attach (recommended) or Link to PDF file here:

Please note that in general, without this information the issue isn't actionable/valid.
Furthermore, the only compatibility information that we provide is found in the Wiki, where it explicitly states (emphasis mine):

The objective is to support all HTML5 compliant browsers, but since feature support varies per browser/version our support for all PDF features varies as well. In general, the support is below. If no version is indicated, then the latest desktop/mobile versions are intended.

[...] and the latter is Chrome57.

According to https://en.wikipedia.org/wiki/Google_Chrome_version_history, that version is four years old and browsers that old are unsafe and shouldn't be used by anyone.

OK, thank you, I have noticed in the Wiki and Q&A about the supported version,I would actually like to know the explicit version of Chrome that is not supported in order to prompt users to download the PDF,However, as you said, the version is too old and we will consider dropping it.

There is no explicit version that we don't support, but in general: the older the browser, the larger the chance that features could be unsupported. Always use the latest stable browser, currently Chrome 87 according to https://en.wikipedia.org/wiki/Google_Chrome_version_history.

By installing different versions of Chrome on my smartphone, I've found that it renders missing characters below Chrome70. Hope it helps


fix app selector crash

I can confirm that the fixes worked for me, with a jailbroken iOS 10.2 device. I still had some issues with  some idb functions, but the application did no longer crash on app selection.

same issue with ios 12.1.1 uncover jalibreak:
on linux
stack trace:
[INFO] 2019-04-25 18:55:13 :: idb ::  Locating application binary...
[DEBUG] 2019-04-25 18:55:21 :: idb ::  File not found: Net::SFTP::StatusException (2, "no such file")
[DEBUG] 2019-04-25 18:55:21 :: idb ::  File not found: Net::SFTP::StatusException (2, "no such file")
[DEBUG] 2019-04-25 18:55:21 :: idb ::  Executing blocking SSH command: /usr/bin/ldid -e '/private/var/containers/Bundle/Application/32695BFF-A624-404C-9FED-5F888EFC1910//Dream11.app/Dream11'
#Plist4r::Plist:0x0000555ccb44a250
[DEBUG] 2019-04-25 18:55:21 :: idb ::  Executing blocking SSH command: /usr/bin/ldid -e '/private/var/containers/Bundle/Application/32695BFF-A624-404C-9FED-5F888EFC1910//Dream11.app/Dream11'
#Plist4r::Plist:0x0000555cca849208
[DEBUG] 2019-04-25 18:55:21 :: idb ::  Executing blocking SSH command: /usr/bin/ldid -e '/private/var/containers/Bundle/Application/32695BFF-A624-404C-9FED-5F888EFC1910//Dream11.app/Dream11'
#Plist4r::Plist:0x0000555cccb4ed98
Traceback (most recent call last):
24: from /usr/local/bin/idb:23:in <main>' 	23: from /usr/local/bin/idb:23:in load'
22: from /var/lib/gems/2.5.0/gems/idb-2.10.3/bin/idb:4:in <top (required)>' 	21: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/idb.rb:278:in run'
20: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:479:in exec' 	19: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:479:in method_missing'
18: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:479:in qt_metacall' 	17: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:2470:in invoke'
16: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/global_app_details_group_box.rb:63:in block in initialize' 	15: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:917:in exec'
14: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:917:in method_missing' 	13: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:917:in qt_metacall'
12: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:2470:in invoke' 	11: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/app_list_dialog.rb:24:in block in initialize'
10: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/app_list_dialog.rb:24:in method_missing' 	 9: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/app_list_dialog.rb:24:in qt_metacall'
8: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:2470:in invoke' 	 7: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/global_app_details_group_box.rb:61:in block (2 levels) in initialize'
6: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/global_app_details_group_box.rb:61:in app_changed' 	 5: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/global_app_details_group_box.rb:61:in qt_metacall'
4: from /var/lib/gems/2.5.0/gems/qtbindings-<IP_ADDRESS>/lib/Qt/qtruby4.rb:2470:in invoke' 	 3: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/idb.rb:122:in block in init_ui'
2: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/main_tab_widget.rb:163:in app_changed' 	 1: from /var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/app_tab_widget.rb:48:in app_changed'
/var/lib/gems/2.5.0/gems/idb-2.10.3/lib/gui/app_details_group_box.rb:69:in app_changed': undefined method sub' for {"$class"=>nil, "snapshots"=>nil, "identifier"=>nil}:Hash (NoMethodError)
Did you mean?  sum
recv failed: Resource temporarily unavailable


'RebasedFeatureMap' is missing?

Hi, thanks to all your efforts for such a good repo.
I'm trying to build a model basing on RebasedLinearAttention, but encounter error:

ImportError: cannot import name 'RebasedFeatureMap' from 'fla.modules.feature_map' (.*/fla/modules/feature_map.py)

Should this feature under developing or use hazyResearch's implementation located in https://github.com/corl-team/rebased/blob/main/flash_linear_attention/fla/layers/rebased_fast.py?

@4IK1d Hi, fixed. Please check it out :-) https://github.com/sustcsonglin/flash-linear-attention/commit/8181db5d2e7ac5ddd78612db36bf7b3431f604e5

You guys are awesome!

https://github.com/sustcsonglin/flash-linear-attention/blob/646efa4cf12bf3b73993968931fe2f4b3597c285/fla/layers/rebased.py#L33C9-L33C32
Hi, seems you forget *arg and **kwargs, then we cannot passin something like layer_idx
(really trivial, :-P)

@4IK1d ah, thank you for the reminder~


python312Packages.pymsgbox: normalize pname

Description of changes
part of #245383
Things done

Built on platform(s)

[ ] 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
[ ] 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.

Result of nixpkgs-review pr 296736 run on x86_64-linux 1

16 packages built:

keepkey-agent (python311Packages.keepkey-agent)
keepkey-agent.dist (python311Packages.keepkey-agent.dist)
ledger-agent (python311Packages.ledger-agent)
ledger-agent.dist (python311Packages.ledger-agent.dist)
onlykey-agent
onlykey-agent.dist
python311Packages.libagent
python311Packages.libagent.dist
python311Packages.pyautogui
python311Packages.pyautogui.dist
python311Packages.pymsgbox
python311Packages.pymsgbox.dist
trezor-agent (python311Packages.trezor-agent)
trezor-agent.dist (python311Packages.trezor-agent.dist)
python312Packages.pymsgbox
python312Packages.pymsgbox.dist


Create mock DataManager functions

Create functions to retrieve & save for the models created in #30, which return mock data but are as close to the "real" function as possible

Functions are created and now in the dev branch. @myusome


Only fetch Google Analytics for present base paths

We have some content items with nil base paths. Trying to fetch
analytics data for these blank base paths results in a 400 Bad Request
when querying Google Analytics.
This change only fetches analytics data for those content items with a
base path.

 Fix BadRequest in Google Analytics integration

@pmanrubia done


Feature/batch integ tests

This PR is set on top of #89, and should NOT be merged until after #89 is complete -> draft PR for now

removed in favor of #83


JAMES-3499 Use a module chooser for LDAP users repository

Enables easy reuse for JPA & memory servers to provide
optional LDAP support out of the box.
Drops Cassanra-ldap and Distributed-ldap servers. The
regular version should be used instead. Docker images
are maintained as is for now, but we can consider dropping
them as well (separated PR). Maven projects are kept for now
but only hosts tests.
Ships the minimal LDAP dependency for everybody.

Reduction of server counts ease introducing new servers, for exemple
to let a grace period of one release to upgrade from ElasticSearch
version 6 to 7 (classpath clashes forces distinct maven projects;
the chooser trick can not be employed).
This is a drop-in, invisible replacement for people running ldap
docker images, as well for the CIs building these images.
If consensual:

[ ] We likely can get rid of the 2 testing LDAP projects...
[ ] We can discuss getting rid of the extra containers (will require changes to the soon to be deprecated linagora/james-jenkins CI)

This is :green_apple: on the CI

Merged


InheritFromTestCodunit typo

InheritFromTestCodunit should be InheritFromTestCodeunit

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

ID: 5e9a88b1-f7e9-e4cb-6b06-4d9e11ef4e35
Version Independent ID: c9b7c384-2643-75e6-c9cd-308d3b77042f
Content: TestPermissions Property - Business Central
Content Source: dev-itpro/developer/properties/devenv-testpermissions-property.md
Service: dynamics365-business-central
GitHub Login: @blrobl
Microsoft Alias: SusanneWindfeldPedersen

Thanks for catching this - will be fixed with the next doc refresh.


Update documentation for change.sh

Markdown link check failures seem to be unrelated to this PR

Markdown Link Check generates a lot of false positives. Maybe we should check if it is possible to migrate this check to Zuul and to improve it there.


Can't paste html code in chat gpt

I can't paste html code into the query field, the tags are cut off and only text is pasted. Although I can paste js, php. Where can I change the settings?

Hello @AndreySocium, Thank you for contacting us. Tell me, does this happen to you in Visual Studio Code or in the web platform? And if in Visual, can you verify the version you have?

Hello! It's in VS Code

any answer?

This was corrected in a recent version of VS.


fix: change config alteration process in withMiddleware to be immutable

Enable users to use shared config objects across useSWR, useSWRInfinite without the React rule of hooks error

closes #1555

Thank you for fixing it!

@shuding
Thanks for the feedback :) Thumbs up for the maintainers keeping this project running.
Been using SWR since start of 2021, a great library indeed. Glad to contribute!


Add libssl-dev to requirements(Ubuntu)

If Ubuntu installation has no libssl-dev(in requirements list for Ubuntu there is no libssl-dev) package then there is an error:
$ luarocks make

Missing dependencies for itorch:
luacrypto
uuid
lzmq >= 0.4.2

Using https://raw.githubusercontent.com/rocks-moonscript-org/moonrocks-mirror/master/luacrypto-0.3.2-1.src.rock... switching to 'build' mode

Error: Failed installing dependency: https://raw.githubusercontent.com/rocks-moonscript-org/moonrocks-mirror/master/luacrypto-0.3.2-1.src.rock - Could not find expected file openssl/evp.h, or openssl/evp.h for OPENSSL -- you may have to install OPENSSL in your system and/or pass OPENSSL_DIR or OPENSSL_INCDIR to the luarocks command. Example: luarocks install luacrypto OPENSSL_DIR=/usr/local

Thank you!

I've only tested this in anaconda environments, so might have missed some obvious things.


[IRGen] Adjust for LLVM r373054

setAlignment now takes a MaybeAlign, so construct one where needed.

CC @compnerd

The CI is still not completely working again, lets merge this to get things into a better state.


Cmake hip module restrict to cxx

Fix path issue in https://github.com/ROCm-Developer-Tools/HIP/pull/2190

Hi @tomsang, I created a reproducer for you under
https://github.com/ax3l/hip_cxxf_cmake
Simply build with:
CXX=$(which clang++) FC=$(which gfortran) cmake -S . -B build
cmake --build build

The error that you see is:
gfortran: error: unrecognized command line option ‘-mllvm’
clang-12: warning: argument unused during compilation: '-amdgpu-function-calls=false' [-Wunused-command-line-argument]
gfortran: error: unrecognized command line option ‘-amdgpu-early-inline-all=true’
gfortran: error: unrecognized command line option ‘-amdgpu-function-calls=false’
gfortran: error: unrecognized command line option ‘--offload-arch=gfx900’; did you mean ‘--offload-abi=ilp32’?
gfortran: error: unrecognized command line option ‘--offload-arch=gfx906’; did you mean ‘--offload-abi=ilp32’?
gfortran: error: unrecognized command line option ‘--offload-arch=gfx908’; did you mean ‘--offload-abi=ilp32’?

@yxsamliu    Do you know the issues @ax3l  reported ?
Looks like they are related to
INTERFACE_COMPILE_OPTIONS "$<$<COMPILE_LANGUAGE:CXX>:SHELL:-mllvm;-amdgpu-early-inline-all=true;-mllvm;-amdgpu-function-calls=false>"

I just went ahead, used an existing ROCm 4.1.0 install on Spack, copied and modified a local hip-config.cmake and tested with the reproducer repo I posted above.
https://github.com/ax3l/hip_cxxf_cmake/tree/test-hipconfig
This PR fixes the problem :tada:

INTERFACE_COMPILE_OPTIONS

Yes, this and the other changes in this PR need to be fixed.
It's missing CXX focus for flags and missing SHELL guarding for flags.

In the future, if HIP is recognized by cmake as a language, we just need to change COMPILE_LANGUAGE:CXX to COMPILE_LANGUAGE:HIP or add similar options for COMPILE_LANGUAGE:HIP.

No, this target is to use for CXX and switching it to COMPILE_LANGUAGE:HIP could break builds that do not have source files set to HIP language in cmake(such as .cpp files).
For the HIP language, there is a hip-lang-config cmake file and corresponding hip-lang::device target:
https://github.com/ROCm-Developer-Tools/HIP/pull/2230
CMake will use this hip-lang-config file and hip-lang::device when using the HIP language. The reason its seperate is not only because it needs to apply the flags to a different language but also some of the flags are actually different. CMake will pass the --offload-arch and -x hip for the hip language so we shouldn't add those flags.
So the hip::device target is meant for CXX, and the hip-lang::device is meant for HIP. Of course, we could look at unifying how we set the more common flags, so there is not so much repetition.

Hi @pfultz2 @yxsamliu, is this one ready to go in? :)

The patch has been merged internally.   Will be publicly released to github  in Rocm4.4 .

Thanks for the update, that's great!
Is the merge-window for this bugfix for ROCm 4.3 already closed?

Yes, the merge-window for this bugfix for ROCm 4.3 is already closed.

@ax3l    After that patch is merged internally, we experienced building failure in some math libs.
I have some questions:

What's the minimum cmake version   for that change?   To my knowledge, it's 3.18.0.
Is there any other dependent change ?

What's the minimum cmake version for that change? To my knowledge, it's 3.18.0.

I think its 3.13 because it relies on the SHELL: selector which I think was added in 3.13. We should not require such a newer version in hip-config.cmake, unless we plan to drop support for ubuntu 18.04 since it only has 3.10. Instead, we should conditionally use SHELL when its available. We could try setting a cmake variable:
set(_HIP_SHELL "SHELL:")
if(CMAKE_VERSION VERSION_LESS 3.13)
    set(_HIP_SHELL "")
endif()
set_property(TARGET hip::device APPEND PROPERTY
    INTERFACE_COMPILE_OPTIONS
    "$<$<COMPILE_LANGUAGE:CXX>:${_HIP_SHELL}-mllvm;-amdgpu-early-inline-all=true;-mllvm;-amdgpu-function-calls=false>"
)

I haven't tested this to know if this works. So we might need to only conditionally enabled the CXX restriction when using the newer cmake.

Hi,
the CXX restrictions and SHELL variable are two independent things.
The SHELL prefix makes sure that - independent of the restriction to the proper language targets - CMake does not deduplicate your -mllvm <something> and -mllvm <somethingElse> flags into -mllvm <something> <somethignElse>, which is an existing bug for all targets.
The :CXX if-s in the generator expressions make sure you don't propagate flags that only apply to HIP C++ targets to other CMake objects in languages like Fortran, Objective-C, etc.
CMake features in this PR by @robertmaynard (#2190), according to docs:

The CXX generator expressions for COMPILE_LANGUAGE are available since 3.3: https://cmake.org/cmake/help/v3.5/release/3.3.html?highlight=compile_language
SHELL: is available since 3.12: https://cmake.org/cmake/help/v3.18/release/3.12.html?highlight=shell
LINK_LANGUAGE is available since 3.18: https://cmake.org/cmake/help/v3.18/release/3.18.html?highlight=link_language

If you like to be backwards compatible, you can do the if(CMAKE_VERSION VERSION_LESS 3.13) switches that @pfultz2 suggests, but this essentially activates bugs unless you develop other work-arounds for them.
You could alternatively, like Intel oneAPI, ship a recent CMake package for with the ROCm packages. Or document to install a recent CMake for older Ubuntus from Kitware's apt repo: https://apt.kitware.com

Thus the minimum cmake version is 3.18.0 in terms of last comment .
rocBlas install.sh can automatically update cmake to 3.16.8 if the existing cmake version is lower(for example, cmake 3.10 on ubuntu 18.04).
See https://github.com/ROCmSoftwarePlatform/rocBLAS/blob/develop/install.sh#L581
rocBlas tester just confirmed 3.20.2 can work.
I'm asking the rocBlas owner whether it's acceptable to update cmake to 3.20.2 .

rocBlas tester just confirmed 3.20.2 can work. But I think it's too high.

3.20 is whats in ubuntu 20.04, so if we want to bump the version we should just require ubuntu 20.04.

I'm also asking the rocBlas owner whether it's acceptable to update cmake to 3.18.6 .

There is more than just rocblas. It would be best to fallback on the old way in older versions of cmake, and then use CXX, and SHELL: when the cmake version is greater than 3.18. This wont break any projects building with hip as most libraries just use whats in ubuntu.

I think that's do-able.
Note that personally, I would recommend to just bump your CMake requirement and document how to acquire CMake on older systems.
Besides the apt-repos, there are tons of resources to quickly get a pre-compiled CMake binary for legacy systems (apt/ppa, conda, pip, Spack, conan, ...) and the logic that you have to maintain across the ROCm eco-system will stay maintainable. I think moving fast(er) on bugs like this and adding features (like the upcoming HIP language feature) trumps the need to support old CMake versions - especially since it's trivial to upgrade for users to newer CMake releases (i.e. let's simply document how).

After updating cmake to  3.18.6 we still experience failures in a few mathlibs projects which cannot deal with something like  "$<LINK_LANGUAGE:CXX>" and  "SHELL:" .    I will have to rework patch to be backward compatible.

I've updated the PR to check cmake version for SHELL and LINK_LANGUAGE.
I ignore checking cmake 3.3 for COMPILE_LANGUAGE because nobody will use such a low version, as I know.
If he really uses 3.3, we can ask him to update cmake.

@ax3l   could you verify whether the new update can still work for your projects?

Thanks for the ping! I am a bit busy with deadlines right now, please feel free to test with the mini-reproducer here:
https://github.com/ROCm-Developer-Tools/HIP/pull/2280#issuecomment-850008375

@tomsang just to confirm. I used my example in https://github.com/ax3l/hip_cxxf_cmake, patched my local ROCm 4.2.0 install, and can confirm that with CMake 3.20.5 the demonstrator now compiles. (And it fails with e.g., CMake 3.16 as we patch out the fixes.)
Do you want to add the test I linked maybe to your integration tests, so we can be sure multi-language CMake projects will continue to build with HIP targets included?

LINK_LANGUAGE has issue on CMake 3.18 when complex lib dependence exists.  This PR failed building
some projects such as rocHPCG and rocHPL. Thus I have to make it jump to 3.20.2 that is known
to work well with LINK_LANGUAGE. The change will look like
if(CMAKE_VERSION VERSION_LESS 3.20.2)
set_property(TARGET hip::device APPEND PROPERTY
INTERFACE_LINK_LIBRARIES --hip-link
)
else()
set_property(TARGET hip::device APPEND PROPERTY
INTERFACE_LINK_LIBRARIES "$<$<LINK_LANGUAGE:CXX>:--hip-link>"
)
endif()

Close it as the  file was removed and another PR in a new project(hipamd) has been merged for the same purpose.

It looks to me that at least the missing SHELL: escapes are also in that project:
https://github.com/ROCm-Developer-Tools/hipamd/blob/d2d2cacfe210307ec10c77400e1dafdeafefbc0f/hip-config.cmake.in#L225
I see issues with that using ROCm 4.5.2, where CMake de-duplicates the flags away for CXX targets, I fear.
(Seen with Cray CC compiler wrappers on OLCF Crusher today.)


Drop support for Node <6

Unless using -n. This way we can get rid of the heavy babel deps.

According to the official Node LTS schedule, v4 is still LTS until October, when v6 will take over.
Could this be postponed? Or maybe let micro v4 support node v4, and micro v5 support node v6?

@millette Exactly! If people want to use an older version of node (not v6), they simply shouldn't update the package to v5...

I'm going to be prioritizing this

@rauchg 👌
I've also updated now-serve and micro-list to comply with this.

Might use async-to-gen as well instead of Babel for async/await? https://github.com/zeit/micro/issues/15

@onbjerg Great idea! But we probably won't be able to drop Babel completely, because the latest node still doesn't support ES2015 module syntax.

@leo 😓

Done


Update to use Ledger Bridge with chrome.hid

This isn't planned to be a long term solution since we can use native code for this, but we might decide to expose this API to other extensions.
The code to mock the navigator.hid in a way that works in extensions is here:
https://github.com/brave/eth-ledger-bridge-keyring/commit/6db82c15435f9ae47dadbc1fc19586552a7044eb
It basically moves the code from the gh-page and then adapts it to use the adapter HID bridge.
I didn't work on eth-ledger-bridge-keyring tests/linting since this is just temporary for us while the new wallet is being built. I did test things with my ledger device though and it worked.

Thanks!


Change high calorie threshold to 300

This change adjusts how data in the FDC data set is classified as high calorie. Now, any dish with over 300kcals per 100g of food is "high calorie." This better balances the classes in the data set, and is a more realistic number based on people eating 1.5-2kg of food per day.

Putting the new rough metrics in the PR here for posterity:
Data Set Class Balance

Low calorie: 25%
Average calorie: 30%
High calorie: 45%

ML Model Metrics

Categorical Accuracy: 83%
Precision 0.84
Recall: 0.81
F1 Score: 0.82
Per-Category F1 Scores

Low-Calorie: 0.83
Average-Calorie: 0.77
High-Calorie: 0.88

Confusion Matrix

Predicted Low-Calorie
Predicted Average-Calorie
Predicted High-Calorie

Actual Low-Calorie
11203
1712
591

Actual Average Calorie
1602
13103
2120

Actual High-Calorie
752
2472
20791


demo: make virtualbox more usable

Also disable upower on virtualbox
Fixes #36348.
Motivation for this change
This should give new users a better experience (no password entry for VirtualBox). It also fixes what I've described in #36348 where KDE tries to suspends and can't recover properly. All virtualbox images should be fine disabling powerManagement, leaving it to the host system.
If possible, it would be great to get these including in 18.03.

also in 02a0fb8e74468664d9af8b3cdbac82c044a4190d


Plan to fix all current CVEs

As of this statement in #7:

I haven't checked, but are the current CVEs resolved on the fork?
They are related to XSS flaws:

CVE-2019-11002(tooltip component)
CVE-2019-11003(autocomplete component)
CVE-2019-11004(toast component)

We know the CVEs are not fixed yet on Materialize, and there are already discussions in the original repository (Dogfalo/materialize#6331 and Dogfalo/materialize#6286) about this subject.
Current situation
Since the current CVEs are related to XSS that can be triggered when Materialize is used in a bad manner, this is the developer's responsibility to sanitize their data before using the three aforementioned components.
However, since the warnings will still display, and since Materialize can be "considered harmful" because of these (even though the discussions on the original repo suggest that it's not Materialize's problem, but rather how devs are using it), we should still find solutions to fix the warnings in an easy and backwards-compatible manner.
This is important for some CI that don't accept dependencies with warnings, or for clients that are worried about warnings they might not understand, especially when it's written "XSS" in them (which is a well-known flaw on the web in general)
Proposal
I suggest that for all the three involved components we add a boolean sanitizeInput option.
When this option is true, the input data will be sanitized with an equivalent of htmlspecialchars() in PHP. There are plenty examples about this on the internet, the best one I found is this one here:
function escapeHtml(text) {
  var map = {'&': '&', '<': '<', '>': '>', '"': '"', "'": '''};

  return text.replace(/[&<>"']/g, function(m) { return map[m]; });
}

Suggestions on other sanitizing methods are encouraged, since this has never been a "standard" process in the web industry 😄 .
Behavior on Materialize 1.x
This option will by default be null. To keep backwards compatibility, null will be equivalent to false.
However, if we detect null, we display a warning in the console, as a reminder to the developer that the native behavior of not-sanitizing is deprecated, and default value will change in 2.x to true.
To remove the warning, we suggest the user to specify the value themselves, even if it's false.
An explicit false will not trigger the warning, since this means that the developer knows what they are doing, and in such case, Materialize cannot guarantee input data safety.
Behavior on the future Materialize 2.x branch
Here, default value is true, and any falsy value will be interpreted as false. We could add type checks to force the user to specify a boolean, but I think this might be overkill. Suggestions appreciated 😉

Feel free to discuss all the different points, and even provide PRs if necessary.

I would suggest DOMPurify which is also used by others and Bootstrap mentions it at https://getbootstrap.com/docs/4.3/getting-started/javascript/.
I would not write our own sanitizer / reinvent the wheel as this could also lead to other issues like bypasses due to problems in the logic.
https://github.com/cure53/DOMPurify

As long as it doesn't introduce too much overhead/bloat on the dependencies, I feel like it's okay to introduce a new dependency for this 👍

You only need sanitizers if you want to allow HTML. Currently autocomplete does not work and is not indended to work with HTML data. So autocomplete wouldn't need sanitizer, it would simply need to use textContent equivalent instead of innerHTML.

When this option is true, the input data will be sanitized with an equivalent of htmlspecialchars() in PHP.

I just want to emphasise that this does not fix the vulnerability with autocomplete, as demonstrated here. If you don't sanitize, typethis will trigger XSS, if you sanitize, still not safe will trigger it.
Root of the problem is Autocomplete._highlight first calling $el.text() effectively unescaping the provided data and then later setting the results with $el.html.

@Pierstoval I've been reading through the other discussions on this, including the response from Snyk, and I like the suggestion from @lirantal for Toast. It would be easy (I assume) and non-breaking to add a properly sanitized text property and update the documentation. Make the examples use text by default and document that the html property is unsafe and should only be used with trusted/properly sanitized data. The response from @lirantal says that it's not obvious that Tooltip accepts HTML, but the options are similar to Toast and include an html property. I think that Toast and Tooltip can be fixed with the same non-breaking method. In fact, maybe we add both text and unsafeHTML properties and mark the existing html property as deprecated - to be removed completely in a later release. That would eventually make it completely obvious that passing HTML to a Toast or Tooltip is not safe.
@DanielRuf I think this is worth a slightly breaking change on Autocomplete for the first release of materializecss/materialize for the following reasons:

This shouldn't affect anyone currently using the old npm repository at materialize-css, only people who are adding the  new @materializecss/materialize repository. That means anyone "upgrading" from materialize-css to @materializecss/materialize will have the opportunity to see a message in the README.md about the breaking change.
It seems the behavior was never intended to include HTML output. Anyone doing that already is essentially exploiting a bug, not using a documented feature. Breaking someone's code by fixing a bug they were exploiting may make them angry, but I don't think we have any responsibility to feel bad about that. Especially when the bug can cause vulnerabilities in code written by inexperienced devs.
It would be really nice if the first release from this team didn't have any publicly visible vulnerabilities, regardless of whether we believe it should be the developer's or the library's responsibility to sanitize inputs. It's just good public relations and I think that's important for adoption of the new fork.
The breaking change would force upgrading users injecting HTML in their Autocomplete to review their code and either stop injecting HTML or use a new property or option to allow unsafe HTML.

Thoughts?
I think the change can be minimally breaking by adding a default property to the Autocomplete options like allowUnsafeHTML: false. Then all a developer needs to do to make their existing code work is add allowUnsafeHTML: true to their initialization options. The other path I had thought of would be harder to upgrade, but potentially better. I'm already working on making Autocomplete accept Chips data as well as the standard URL/null. There may be a good way to implement an unsafeHTML property on that data object. Not sure though.

Yes thats awesome! It would also be very cool to add IDs to the Autocomplete Data.

Root of the problem is Autocomplete._highlight first calling $el.text() effectively unescaping the provided data and then later setting the results with $el.html.

In't the code at https://github.com/materializecss/materialize/blob/a8a30a321753b3c637a2e177e71c0e09d0b59746/js/autocomplete.js#L382 also a problem? The image URL could potentially be a user-supplied avatar URL. Is the escaping done by
img = document.createElement('img');
document.body.appendChild(img);
img.src="x\" onerror=\"alert(\'XSS Attack\')\"";

sufficient?


Trigger batch solutions based on volume

Currently, we only batch solutions on-chain based on a schedule. Solutions should be batched on-chain if a certain volume threshold is met.

Low priority.

Moved to low priority. If it were to be done then needs better defined AC


promises instead of callbacks?

It looks like in bot.reply, callbacks are used instead of promises.  It seems like promises would be better in this situation?

You can easily promisify it.

On this breath the internals of botkit would be helped a lot (at least to understand) if there was less reference to implicit state using this (maybe it is just my unfamiliarity with OOP) as well as maps and reduce functions instead of nesting for loops.


Restore Data and HDFS Nodes upon Relaunch of Framework

If the framework is killed and relaunched, the HDFS Nodes should be restored with data intact if possible. For example, the same host and data files should be used for a Name Node that was previously running.

@elingg Can this be closed after the latest round of failure-handling changes and testing? I.e. #31

Indeed!


feasibility of providing as a couple of simple tensorflow models

I am curious about whether this could be provided as a simple tensorflow model. I.e. something where one could just:
lyra_encoder = keras.models.load_model('path_to_lyra_encoder_model')
lyra_decoder = keras.models.load_model('path_to_lyra_decoder_model')

and from there one would be able to simply
encoded_sound_frame = lyra_encoder.predict(sound_frame)
decode_sound_frame = lyra_decoder.predict(encoded_frame)

Releasing lyra in such a way would make it so much easier to use on a wide range of environments, from microcontrollers to gpus.
Is there any fundamental reason for such a way to release to not work, or "is it just not how it is done as of today"?

Today only the generative model at the decoder is trained in TensorFlow, so it would be quite a bit of work to port the rest over.
I can see the value of having TF models like that, but at least for some use-cases it is preferred to have a C++ API to integrate with.

Temsoflow has a C++ API too though :) . Actually, this would be one of the use I would like to try - using this on a moder Cortex MCU, through the tensorflow lite C++ API.

That is a great point. But that would require a large effort, since big parts of our system aren't implemented in TensorFlow today.

 Or is there anything unusual about these?

are the training data open with pipelines available to generate these? If yes, training anew with the same network in Keras and same data would be easy. If not, maybe some other voice dataset could be used, at least first?

If not these points are easy to implement, wonder if it would be possible to train a Keras model to match the present encoder decoder pair, simply by generating large amounts of synthetic data using Lyra and using these as training data for the Keras version.

Those are definitely all great points.
Regarding re-implementing in Keras, it would definitely be some work. But on top of that, we are currently working on Lyra v2, which will have many improvements and changes. We are planning on releasing it here as soon as it is ready, so I would wait before putting in the effort.
And regarding the training data, we are not planning on releasing that. So if someone would want to re-train the system, it would need to be using some other available dataset.
I don't think there is much value to train on samples generated synthetically by Lyra, since it would only introduce additional artifacts.

Ok, thanks!

I agree training on synthetic data would just introduce artifacts, but as a first quick fix it would be better than no tensorflow model :)

Sounds exciting with Lyra V2; if it can be available as a tensorflow model that would be awesome :) .

I still think it would be better to train on clean (and noisy) recordings without having gone through Lyra. The current feature extraction is traditional, not learned, so it could be written out with no training.
And just for transparency sake, there is no plan to provide an encoder and decoder TensorFlow models at the moment.

Thanks for making this open source, really appreciate your contributions @aluebs.
Definitely a +1 on the enc/dec w/ TF :)
Excited for the release of v2, approximately when can we expect it?

There is no set date for the Lyra v2 release, but it should happen very soon (within the next month or two).
It will still have the same C++ API, but, because it is trained end-to-end, many components are migrated to TFLite.

Yes, one advantage of migrating to TFLite is the portability.
There will still be fair amount of C++ logic and glue, so full tensorflow implementation might require some porting work.

It's great to know that Lyra v2 is coming out! Will you provide a training pipeline (so that we can train and tweak the model using our own data), or just a pretrained model?

At this time we'll only open-source a pretrained model for inference.

Since it was mentioned in this discussion, Lyra 1.2.0 has been release, together with its TFLite models.

So this is effectively done, right? :) Feel free to close.

The TFLite models are still divided in encoder, quantizer and decoder and I am not sure how simple it would be to implement something along the lines of the initial suggestion. So I am not sure that it is done, but at least it is a step in the right direction. I'd love to know if someone implements python wrappers like that.


Fixed for 0 sided dices (4d0)

4d0 gives 4 and not 0

Not sure why anyone would do "4d0", but good catch nontheless :+1:

I integrated this library in an IRC chat bot and the first thing they tried was "4d0" ^^


Update gromopo monster in "About"

Use the new purple monster instead of copyrighted one.

closed with #68


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 16:57:29 on 2023.04.13
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 2, errors out: 0
Original problem ID: 16164
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=16164

Problem has been resolved in 9m 0s at 17:06:29 on 2023.04.13
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 16164


Allow failures in FirebaseMessaging

#4053 introduced a travis failure for Messaging.  The issue is suspected to be test only.
This PR allows the failure to continue while being investigated (#4236) while allowing the overall build to go green.

cc: @chliangGoogle


Log dryRun flag to deleteMetadataJob

이거 안찍으니까 사용자가 식겁할거 같더군요.

I thought the user would be surprised if I didn't film this.

Codecov Report

Merging #21 (ae50384) into main (922e2d4) will increase coverage by 0.39%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
+ Coverage   98.29%   98.69%   +0.39%
==========================================
  Files          33       33
  Lines         763      764       +1
  Branches       36       36
==========================================
+ Hits          750      754       +4
+ Misses         12       10       -2
+ Partials        1        0       -1

Impacted Files
Coverage Δ

...batch/plus/job/metadata/DeleteMetadataTasklet.java
100.00% <100.00%> (+7.89%)
:arrow_up:

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


Lmda, pre review

Codecov Report

Merging #4 (d400bc6) into master (0d4f70f) will decrease coverage by 1.07%.
The diff coverage is 0.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
- Coverage   83.80%   82.73%   -1.07%
==========================================
  Files          63       64       +1
  Lines        4821     4883      +62
==========================================
  Hits         4040     4040
- Misses        781      843      +62


Descriptive entity_ids for their respective devices

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
It's hard to find the sensor for a particular device you're writing an automation for because the entity_id's are currently named without any context of the parent device name. For example:
For my Foyer doorbell (named Foyer):

binary_sensor.motion_detected_6
binary_sensor.person_detected_6
[... other sensors]

Describe the solution you'd like
It'd be great if the entity_id's were prefixed with their device name. For example, based on the above:

binary_sensor.foyer_foyer_motion_detected
binary_sensor.foyer_foyer_person_detected

Somewhat related but different: it'd be great if the friendly name also followed this pattern.
Describe alternatives you've considered
I could rename each individually, but this will likely break during updates and is pretty tedious going through many devices.
Additional context
For whatever reason, it seems like the camera.* entities are following this pattern and not the sensors.

Good news and bad news:
Good news is that v1.1.0 will resolve this for new entities going forward, as well as fix the name of any existing entities that haven't already been overwritten.
There is no danger of you changing something manually as every entity is tracked by a unique identifier - actually without this Home Assistant doesn't even allow the dialog to change the entities.
Bad news is that this won't fix entity keys you already have (names should update). For that I think you'll have to delete entities and reload the integration, or delete the integration entirely.


Make current_dir and current_path in FileDialog useable.

Fixes #45822
Replace dir->get_text() with dir_access->get_current_dir() in FileDialog::get_current_path and FileDialog::get_current_dir.
The current implementation just returns the raw text value in the directory LineEdit, which ignores the driver so the path is not usable, especially considering that the driver itself is not exposed.

Instead, this PR returns the value dir_access->get_current_dir() mentioned in the workaround in #45822 which is also used in many places in the source.
Example:
FileDialogDebug.zip
Select any file to get the output :
Before:
path: D:/gd_ws/GodotAreaMovementMono/icon.png.import current_dir: /gd_ws/GodotAreaMovementMono current_file: icon.png.import current_path: /gd_ws/GodotAreaMovementMono/icon.png.import

After:
path: D:/gd_ws/GodotAreaMovementMono/icon.png.import current_dir: D:/gd_ws/GodotAreaMovementMono current_file: icon.png.import current_path: D:/gd_ws/GodotAreaMovementMono/icon.png.import

Oh, the absolute path case is not handled properly. I would amend it soon.

The methods you modified are getters for a property. Doing set_current_file(set_current_file()) should result in setting the same text, which I think might be not true after your changes. If anything, your behavior could be implemented in separate methods. Or just one method - get_full_path(), you can then use get_base_dir() to get the directory.


Allow for use of  event publication registry outside of Spring Modulith

For spring boot projects which want to make use of the outbox pattern which the event publication registry provides would it be possible to extract the relevant bits into their own starter?

It would, indeed. We just would like to avoid creating a gazillion of starters for different usage flavors because that adds cognitive load for people approaching Spring Modulith (which starter would I use under which circumstances). Starters are an expression of preferred usage scenarios. While perfectly possible, using the registry outside of Spring Modulith currently is not one.

I realise this is now marked as not planned but there is precedent in Spring for creating separate projects like this e.g. spring-rety.
I still think it is worth separating this out as its own project given how the "transactional outbox" is such a great pattern.

For one, rest assured that we constantly observe this space and would reconsider the project arrangement in case we see the picture significantly changing. Spring Retry is not the best analogy here, as it's basically and advice and a bit of configuration to repeat method invocations. That's by no means comparable to a piece of infrastructure that deeply integrations with Spring's event multicasting and also integrates with many different third-party technologies like message brokers and databases.
I still don't quite understand what's wrong with the existing starters (spring-modulith-events-jpa et al.) because they're exactly built for what you're asking.


Path bbox calucalation should scale stroke width

Consider a path like
<path id="1" fill="none" stroke="#ffffff" stroke-width="4" transform="matrix(0.1 0 0 0.1 0 0)" d="M 0 0 L 0 20 L 20 20 L 20 0 Z"/>

A correct bbox for such a path would be something like -2 -2 24 24
scaled down to -0.2 -0.2 2.4 2.4
However, PathData::calc_bbox_with_transform uses original stroke width
added to a transformed path bbox and produces a wrong result of -2 -2 6 6
Scaling stroke width by \sqrt{|ad - bc|} helps.

Yes, makes sense.  But is this a correct formulae? We have usvg::Transform::get_scale and it looks like this:
let x_scale = (self.a * self.a + self.c * self.c).sqrt();
let y_scale = (self.b * self.b + self.d * self.d).sqrt();

Well, determinant of a 2d transformation matrix gives an area scaling factor, so sqrt(det(M)) results in a "visual zoom factor" for a stroke width when you'd prefer to keep the shape of the stroke itself unchanged, which is often the desired result when scaling a figure (I found a good visual example here)
I think though that the exact formula should match the way resvg scales stroke while producing bitmap. If resvg transforms strokes' shapes, the bounding box calculation should reflect that.
For my purpose (a one-off tool coverting a bunch of svg icons into pgf) either way would fit.
Do I get it right that the correct way would be
    // TODO: find a better way
    // It's an approximation, but it's better than nothing.
    if let Some(stroke) = stroke {
        let w = stroke.width.value();
        let (x_scale, y_scale) = ts.get_scale();
        minx -= w * x_scale;
        miny -= w * y_scale;
        maxx += w * x_scale;
        maxy += w * y_scale;
    }

?

I just thought that it would be better to use the same logic as tiny-skia uses during rendering. And it seems like it does the same as your code: https://github.com/RazrFalcon/tiny-skia/blob/3b5ec3c8de1ea16fadaf94f1099d01eeda172ea1/src/stroker.rs#L279 So it's fine.
tiny-skia is actually strokes the original path and then scales it. So there is not "stroke scaling" happening, afaiu.
Anyway, it should be fine.


Use the uguid crate to replace the Guid struct and guid! macro

The uguid crate is something I open sourced at work. It can hopefully serve as a useful bit of shared vocabulary in the ecosystem for crates that need Windows-style GUIDs.
This should be mostly transparent for the end user except that the from_values method has been removed. Usually the guid! macro is a more convenient choice anyway, but new or from_bytes can also be used if needed.
This allows us to delete a bit of code and some tests, as well as slightly reducing our dependency on proc macros as the uguid::guid! macro is a declarative macro.

Checklist

[ ] Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
[ ] Update the changelog (if necessary)

Nice, I like it. I can use this to use the same code for my UEFI and non-uefi code. Like ESRT parsing.


Top align card title

Card titles should be aligned to flex-start instead of center by default according to MD.
However, this far after release due to cards being so flexible, who knows what has been implemented/planned that relies upon the title's being centered. So, seems best to wait until the next major to bring this into alignment.

Closing; superseded by #4472


185782620 Bound New Sparrows To Document

This PR ensures that the text boxes of new sparrows do not get placed outside the bounds of the document.

@tealefristoe, are you trying to get this merged before 4.5.0 is frozen? I see it is tagged with the same story which already had code merged to master so that already merged code will be part of 4.5.0.

@tealefristoe Because some bugs were found, there might be time. Do you think we need approval from Kirk and/or Boris before merging?


Add trigger for deployment updates where an image changes

On Slack, @mitin20 asked for the ability to trigger an action when a deployment is updated and the pod's image changes
We might be able to implement this the same way as https://github.com/robusta-dev/robusta/issues/405

@alikhanxgrid , May I know if you have any plans to implement this?

@alikhanxgrid , May I know if you have any plans to implement this?

Not at this moment.
Had worked on it but couldn't complete it.

@aantn this was added on 0.11.0
change filters


fix: get actual protocol for windows instead of protocol + drive

On windows current regexp from this url gets incorrect protocol:
file:///C:/path

Incorrect: file:///C
Correct: file

This PR fixes it making {2,} ungreedy, so it will end after the first :. (You can test it in https://regex101.com/)
Related: https://github.com/vitest-dev/vitest/issues/379

Can you add some tests?

Can you add some tests?

Your test setup doesn't allow me to import that function to properly test it.
isValidNodeImport checks on the running machine, but tests run only on ubuntu and even then it's hard to replicate without Windows.


fix Node.js package vulnerabilities

If the current master branch is checked out, then npm audit reports almost 16,000 vulnerabilities in the package dependencies. This pull request fixes those vulnerabilities (commit 68e73e6). Additionally, it updates the package versions (commit 106a448).

Just a quick question since there has been no reaction here for almost a month: Did you by any chance just fail to notice this pull request? Or is there some other reason why there has been no reaction so far? Please let me know if there is anything missing in this pull request or if there is anything I can do on my side to speed things up.
Thanks.

@garmeeh Let me ask you a question, can you view this pull-request from @striezel and merge it if you are pleased with it?
It would be damn nice if the current ~15000 vulnerabilities were fixed. :)
npm audit: found 15273 vulnerabilities (2 moderate, 15270 high, 1 critical)

🤦


refactor(LinearAlgebra/Basic): R-linear equivalence between spaces of R₁-linear maps

Loosens the hypothesis of LinearEquiv.arrowCongr to get an R-linear equivalence between spaces of R₁-linear maps.
This is needed for #9334.

!bench

@eric-wieser do you have a moment to review this please? Thanks.

Closing this PR as it doesn't seem to be of interest.


'#29000000' is not a valid value for property 'BorderBrush'.

I am trying to convert an application that previously used the metro interface library to a WPFUI, I removed a lot of styles that relied on metro and prioritized making the application work.
After confirming the removal of metro and making it work, I inserted the code " <ui:Resources Theme="Light" />" into the App.xaml to run it with the error "'#29000000' is not a valid value for property 'BorderBrush'." .
Then I checked the source code of WPFUI, deleted line 27 of ComboBox.xaml, and the program worked fine.
Then I reverted all the code and added " <ui:Resources Theme="Light" />" directly without removing the metro, and it still prompts this error.
The above problem occurs in this project:
https://github.com/aiqinxuancai/WkyFast
Screenshots

Desktop (please complete the following information):

OS: [e.g. Windows 10] 19043.1766
.NET: [e.g. net6.0-windows]
Version: [nuget last]

Hey @aiqinxuancai. The error is due to an invalid Color to Brush assignment for the ComboBox control. This bug will be corrected in version 2.1.0.

Release 2.0.1 has fixed this problem.


Replace "deno" with "demo" in two places

I assume this was a typo, since the libraries in question were "demo" repos and have nothing to do with Deno, correct? 👍

This was actually correct as Deno :)
We adapted the Deno Postgres and MySQL drivers.
Thank you for the PR though!

Haha, very good, keep up the good work!


"supabase migration up" fails on local projects

Describe the bug
I'm using supabase for local dev and I don't have a linked project set up.
As of version 1.95.0, when I run supabase migration up it fails with the following error:
Cannot find project ref.

I had a look and it seems like recently the way that the cli flags were parsed/defined was changed, and the relevant ones are here I think.
https://github.com/supabase/cli/blob/b7c58ad9dc937a01a40591a5a8b8a66746010637/cmd/migration.go#L127-L128
These flags' default values, on my machine at least, cause the cli to think it should run in linked mode, and it ends up going down this code path:
https://github.com/supabase/cli/blob/b7c58ad9dc937a01a40591a5a8b8a66746010637/internal/utils/flags/db_url.go#L63-L72
which causes the failure mentioned above.
To Reproduce
run supabase migration up in a non-linked context
Expected behavior
it applies the migrations, or tells me that my local db is up to date
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: macOS
Version of CLI: 1.99.1 but the bug was introduced in 1.95.0 as far as I can tell

Additional context
This doesn't seem to happen for other members of my team, so I may have some special messed up state on my machine. I tried nuking all the dotfiles in the supabase directory of my project, I tried resetting the db, I tried stopping and starting. Let me know if I can provide any other useful context.

Thanks for raising this issue. I managed to reproduce and release a fix in the latest version.


[FR] Improve overall error handling and fault tolerance

Is your feature request related to a problem?
Under most circumstances, the docusaurus-plugin-openapi-docs plugin successfully reads, parses and generates MDX for a given OpenAPI specification. Still, there are times when processing errors occur, due to gaps or incompatibilities, which can lead to exceptions. These errors can occur for a number of reasons at a number of points during processing, including:

Conversion of OAS to postman collection
Creation of API items (especially when creating sample request payloads/schemas)

Describe the solution you'd like

Better, more informative errors/traces, i.e. include function, spec path, etc.
Better fault tolerance, i.e. continue processing other specs after failure
Pre-flight validation checks before proceeding with deeper processing

Describe alternatives you've considered
Focusing more on validating the OAS outside of the plugin using various linters, extensions, tools, etc.
Additional context
Improvements in this area would greatly enhance the usability of the plugin while also decreasing the time needed to diagnose failures and deliver fixes.
TODO

[ ] Document process flow (diagram?) and where failures could occur
[ ] Implement pre-flight validation to help fail faster
[ ] Add appropriate exception handling to functions prone to failure
[ ] Pass/add appropriate context to improve error messages
[ ] Support continue on failure/error
[ ] Improve logging, i.e. provide more logging to understand where we are in the process

Smaller Fixes

[x] PAN-OS REST API [ERROR] TypeError: Cannot read properties of undefined (reading 'default')

After some internal discussion, we determined it would be better to focus on improving our testbed. Archiving this issue for now.


Move install command from base to plugin

Fixes:
https://github.com/grails/grails-core/issues/10108

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


Seed Parameter Not Respected in Image Generation

Hello,
I am experiencing an issue with the seed parameter when using the Replicate API for image generation. It seems that the seed parameter is not being respected, as the images generated with the same seed value do not match.
Details:
Model Used: black-forest-labs/flux-schnell
API Call Example:
output = replicate.run(
"black-forest-labs/flux-schnell",
input={
"seed": 123456,
"prompt": "black forest gateau cake spelling out the words "FLUX SCHNELL", tasty, food photography, dynamic shot",
"num_outputs": 1,
"aspect_ratio": "1:1",
"output_format": "jpg",
"output_quality": 100
}
)
print(output)
Issue Observed:
Generating multiple images with the same seed value results in different images.
Even with a single image generation request, the output varies despite using the same seed.
Expected Behavior:
The images generated with the same seed value should be identical to ensure reproducibility.
Actual Behavior:
The generated images are different even when the seed value is the same.
Additional Information:
I have verified the issue with different seed values and different prompts to ensure it is not related to other parameters.
The issue persists across multiple requests.
Could you please investigate this issue and provide guidance on how to ensure the seed parameter is respected in image generation?
Thank you for your assistance.
Best regards,
Danilo Maia
From Brazil - Fortaleza - CE

solved

Hi @danilomaiaweb. I'm sorry that was causing you problems. This seems to be an issue with the model rather than the Python client or API. It looks like this issue has since been resolved in the model, so please try again and let us know if you're still having this problem.


Value of pulldown resistors

Hi,
Could you let me know the value of the pulldown resistors?
Can I use 10KOhm resistors?
Thanks!

Yes, you should be able to use 10kΩ resistors.
A typical value for a pull-down resistor for a 5V signal from a battery-powered device ranges between 10kΩ and 100kΩ.
Higher value resistors (e.g., 100kΩ) minimize current draw from the battery but may result in slower response times for the signal to change states.
Lower value resistors (e.g., 10kΩ) ensure a stronger pull-down effect and quicker signal stabilization, but they will draw more current, which might be a concern for battery life.
It really doesn't matter that much -- I don't think you can harm the device -- you will just either use a little more battery or you will have an unstable signal that won't work.


OrderEmailNotifier::sendCancelNotification doesn't have a separate template

sendCancelNotification doesn't have a separate email template and simply uses Order::class's template, which is a bad design and hard to customise in projects.
TODO:
set template in sendCancelNotification, include Order etc. in that template.
FIXES:
in custom projects, this template can be adjusted in the project theme.

fixed by #801


Add missing dependencies between fusesoc cores

The i2c and alert cores were missing dependencies on packages, which could lead to a wrong include order of these files, failing compilation. See the individual commit messages for the exact error message and steps taken to resolve that.

Can we standardize on this and mandate each comportable IP has a "package" core and a "main" core with the rest of the RTL files? This introduces some overhead in terms of core files, but if would allow for clean separation of DV and RTL in the sense that definitions from RTL packages can be imported without having to import functional RTL code into DV environments. @sriyerg would that work for you guys?

Btwy, in order to unblock other PRs from Philipp and me, can we move forward with this one and clean up the package core files on our end after this? That is going to tough several core files...

Btwy, in order to unblock other PRs from Philipp and me, can we move forward with this one and clean up the package core files on our end after this? That is going to tough several core files...

Okay to merge this in as-is - a better fix would be to add standalone core files for the packages that contain data structures that are safe for reuse in DV than adding dependency on the entire RTL code into an internal DV component.

I have split this out as issue #1779. I'll go ahead and approve this PR such that you can merge and move on with #1679, @imphil .

Thanks for the reviews.
What's going on here is this:

The bug: some RTL files in the DV tree relied on packages, but didn't declare a dependency on them in the core file. This worked before due to an implementation detail of FuseSoC, but was always wrong (TM).
Why it worked before: in current versions of FuseSoC, dependency orderings are retained as an implementation detail. That means, if you had a core with depends: [ core1, core2 ], FuseSoC would first include files from core1, and then from core2. That behavior effectively created an "invisible" dependency between core2 and core1.
What changed now: with the work on dynamic primitives in #1679 the implementation of the dependency resolution process changed, and the "invisible" dependency isn't present any more.
What didn't change: fusesoc still guarantees that all dependencies (and their dependencies) are evaluated before files, and files are included in the order they are specified.

I agree that depending on the full RTL implementation in DV isn't nice, and that the proper fix is to split out packages ("headers" in C lingo) into a separate core file. Until that's done, this patch should do the trick.


Better documentation and dev UX for snapshot testing

Talk about snapshot testing in CONTRIBUTING.md:

how it works
when to use it
how to use

Add a update-snapshots command to package.json so that it's easy to update the snapshots when necessary.

A link to how it works and how to use was added in #1146.

@ylemkimon Lots of npm scripts are mentioned in CONTRIBUTING.md, but the screenshot ones aren't.  (Though the steps seem reasonably documented.)  Could you add a few explicit npm run ... lines?  (Ideally all npm scripts would be mentioned here...)

@edemaine They're in the dockers/Screenshotter/README.md, but it'll be nice to have a centralized place.


Client DPI does not load any data

Hi, I just installed your unifi-poller (influxdb) and the rest of the charts work fine, except for the Client-DPI (#10419).
Am i missing anything here?
Nothing loads and it just says No data to show.
Let me know what other information you require :)

You must enable DPI on the controller and in the poller config. Two spots.

Hi David
Thanks for the response.
DPI has all along been enabled on the controller though.
When you mentioned poller config, where exactly is this setting at?
On 26 May 2020, 1:25 AM +0800, David Newhall II<EMAIL_ADDRESS>wrote:

You must enable DPI on the controller and in the poller config. Two spots.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Show me your current config.

Hi David
Thanks. Realised I didn’t add the environments for DPI. It’s now working. Just want to let you know that this dashboard of yours is truly amazing! Keep up the fantastic work!
On 26 May 2020, 2:09 AM +0800, David Newhall II<EMAIL_ADDRESS>wrote:

Show me your current config.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Sweet!