Increase GraphEdit node connection hot zone size

The graph editor in 4.0 has a too-small hot zone for connecting graph nodes, which can make snapping unintuitive. This PR simply adjusts the default theme's port_grab_distance_vertical property to increase the vertical height of the snapping zone.
For more information please see godotengine/godot-proposals#2790.

Apparently my doctool hook failed. Will fix it in a moment.

Before:

After:

This should probably be cherry-picked, correct?

Technically this breaks compat, because it changes a value in the default theme. This can be amended to change this property in the editor theme instead, then it can be safely cherry-picked.

Technically this breaks compat, because it changes a value in the default theme. This can be amended to change this property in the editor theme instead, then it can be safely cherry-picked.
In fact, this is what it should probably do anyway, as this PR seems to be mostly targeted for the visual editors.

I intentionally kept the value lower than I could have made it to maintain compatibility with user-created Grap Editors.
In theory, I could just remove the theme option entirely and take the height from the elements in the GraphNode. Added some more rects in green to my debug render to visualize what that would look like compared to the current hot zones:

I intentionally kept the value lower than I could have made it to maintain compatibility with user-created Grap Editors.

If you change the default value, you break compatibility. And since this is a theme property user can do the same on their end anyway. Just change it for the editor theme, or keep this PR as is and make a separate PR for 3.x that only changes editor theme, but keeps default theme values as is.


[BUG] there are remaining references to alibaba dubbo jar that should probably be changed to apache dubbo jar

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

https://github.com/apache/incubator-shenyu/blob/master/pom.xml#L96
https://github.com/apache/incubator-shenyu/blob/master/pom.xml#L263-277

Also appears in other pom files

https://github.com/advisories/GHSA-gw4j-4229-q4px - one CVE in alibaba dubbo
possibly other issues that might be fixed in apache version but not alibaba version

Expected Behavior
Use apache dubbo everywhere
Steps To Reproduce
No response
Environment
ShenYu version(s): dev

Debug logs
No response
Anything else?
No response

hi， we should support alibab duoob and apache dubbo。
BTW ，apache dubbo fully compatible with alibaba dubbo?

hi， we should support alibab duoob and apache dubbo。
BTW ，apache dubbo fully compatible with alibaba dubbo?

I have tested that using apache dubbo client to access alibaba dubbo service is normal, this is protocol compatible, but I have not fully tested.


Publishing config file not clear.

How can I publish the config file to set a default redirect for example?

Added this commit to the docs: https://github.com/lmsqueezy/laravel/commit/c0797502dbe48e575e7d8c89473bf4cb4f623197


docs(readme): add further instructions for building docs on Mac

Description:
Add instructions to install missing Ghostscript fonts on Mac.
Related issue (if exists):
Homebrew's ghostscript package does not install any fonts;
gm convert will fail without them.  Add instructions to install these
fonts manually.

Coverage remained the same at 97.041% when pulling 0c05e77724bfff50d0db3cd4468b3a41e3ce709a on boneskull:ghostscript-mac-fonts into 8ebee66e00156b3bc933370518526a2ecaa4f6c9 on ReactiveX:master.

LGTM


Initialize frontend rotary encoder state from the backend

This PR fixes #349 by making the frontend's rotary encoder reducer handle the case where its state is null (which is always how the frontend starts) and it receives a RotaryEncoder message from the backend. This is a very tiny hotfix and I've tested it on my Raspberry Pi setup; @raavilagoo once you test it and confirm that the frontend responds when you turn the rotary dial, I'll merge in this PR. For records-keeping:

This project is licensed under Apache License v2.0 for any software, and Solderpad Hardware License v2.1 for any hardware - do you agree that your contributions to this project will be under these licenses, too? Yes
Were any of these contributions also part of work you did for an employer or a client? No
Does this work include, or is it based on, any third-party work which you did not create? No

Rotary encoder test passed on this commit. Frontend responds to Rotary dial.


Add spec for multiple links

https://staging.example.com/foo/bar (Open in production, Development)
Some Other Link (staging) (Open in production, Development)

\o/ it works


How to run test with serverless and vandium

Hi,
I'm new to serverless tought and vandium seems to be a good tool for productivity. I was wondering how you can run tests with the vandium api part. Do you have any good exemple to show or use cases?

something like:
// handlers/hello.js
module.exports.handler = vandium.api()
        .GET( ( event ) => {

            return 'hello world';
        });

could be tested with:
// test/handlers/hello.test.js
const LambdaTester = require( 'lambda-tester' );

const expect = require( 'chai' ).expect;

it( 'normal operation', function() {

    const event = {

        resource: '/',
        path: '/',
        requestContext: {

            apiId: '0000000000'
        },
        httpMethod: 'GET'
    };

    let hello = require( '../../handlers/hello' );

    return LambdaTester( hello.handler )
        .event( event )
        .expectResult( ( result ) => {

            expect( result.statusCode ).to.equal( 200 );
            expect( result.headers ).to.eql({});
            expect( result.body ).to.equal( 'hello world' );
            expect( result.isBase64Encoded ).to.be.false;
        });
});


[stable/prometheus-cloudflare-exporter] Add chart

Description

Checklist

[x] Title of the PR starts with chart name (e.g. [stable/mychartname])
[x] Github actions are passing

You also need to include the options from here: https://github.com/wehkamp/docker-prometheus-cloudflare-exporter#try-it
For example, I would put AUTH_KEY in a secret, like here: https://github.com/deliveryhero/helm-charts/blob/master/stable/prometheus-soti-mobicontrol-exporter/templates/secret.yaml

You also need to include the options from here: https://github.com/wehkamp/docker-prometheus-cloudflare-exporter#try-it
For example, I would put AUTH_KEY in a secret, like here: https://github.com/deliveryhero/helm-charts/blob/master/stable/prometheus-soti-mobicontrol-exporter/templates/secret.yaml

I've wanted to just pass them as environment variable to deployment which could be more flexible

Nice!

Thanks for giving awesome suggestions


Provide policy that installs the official compliance operator

This policy doesn't use the upstream release, but instead gets the
official and supported release from the red hat catalog.

/assign @ycao56


Use the 'pull_base_image' plugin

Please do not merge until projectatomic/atomic-reactor#220 is merged and there was reasonable time to update buildroots to the new version.

I think it's ready for review/merge.

LGTM


Replace Exisiting screenshot for mediaports

Current screenshot is missleading as it does not comply with our best practice to have concurrent port for QOS. As we show QoS enabled we should display a supported configuration. I've therefore replace the current image with the configuration default.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LanaChin PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

Thanks @ericsche. There was a branch conflict in this commit so I spun up a separate branch and added your screenshot. The doc is now updated with the screenshot you provided.  Am closing this PR without merging.


Per the Florida's Wiretapping Law, our study and research may only be recorded only if there is consent of all parties.

The rule comes from the Florida Recording Law.
Link: https://www.dmlp.org/legal-guide/florida-recording-law#:~:text=Florida's wiretapping law is a,parties to the communication consent.

Title should be: Only record if consent
Issue description should be full rule with link integrated or placed after


streamlink: 3.2.0 -> 5.0.0; pythonPackages.versioningit: init at 2.0.1

Description of changes
This is #171179 plus updates to versioningit and Streamlink, reopened as new PR so all those force pushes don't make it hard to follow.
Changelogs:

https://github.com/streamlink/streamlink/releases/tag/4.0.0
https://github.com/streamlink/streamlink/releases/tag/4.0.1
https://github.com/streamlink/streamlink/releases/tag/4.1.0
https://github.com/streamlink/streamlink/releases/tag/4.2.0

In 4.0.0, Streamlink switched to the PEP 518 format (pyproject.toml), and additionally introduced a build-time dependency on versioningit (although the PyPI source distribution has the version number substituted in, so we don't need the full Git history).
versioningit does not build below Python 3.8 due to transitive dependencies in Nixpkgs not building below 3.8, so I'm constraining Streamlink likewise (and omitting a <3.8 dependency).
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.versioningit
python39Packages.versioningit
streamlink
streamlink-twitch-gui-bin

Updated to 4.3.0 with rebase on master.

Updated Streamlink to 5.0.0, versioningit init to 2.0.1 (was 2.0.0), with rebase on master.

Updated Streamlink to 5.0.1 with rebase on master

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1233


Microchip MEC1501 / mec15xxevb_assy6853 board support

Microchip MEC1501 pull request made up of 4 commits:

Add MEC1501 header to ext/hal/microchip/mec/mec1501
Add MEC1501 DTSI file to dts/arm/microchip/
Add MEC1501 SoC folder and files to soc/arm/microchip_mec/
Add mec15xxevb_assy6853 board folder to boards/arm

The PR looks ok, we are waiting for 1.14 to be release for this to go in. One main change that we need to address is the fact that the content in ext/ will need to go to a new and microchip related repo under the zephyr project GH org. I think we can merge this as is and do the split of ext/ components after the code is merged to avoid and conflicts or dependencies.

issues in https://github.com/zephyrproject-rtos/zephyr/pull/15101#issuecomment-478779066 needs to be addressed

Need to fix some issues with licenses:
ext/hal/microchip/mec/CMakeLists.txt missing license.
soc/arm/microchip_mec/mec1501/CMakeLists.txt missing license.

Also one checkpatch.pl error needs to be addressed.

-:142: ERROR:TRAILING_WHITESPACE: trailing whitespace
#142: FILE: boards/arm/mec15xxevb_assy6853/doc/index.rst:45:
+- `MEC1501 Reference Manual`_ $

Kconfig failing check needs to be addressed.

Path '/arch/arm/include/cortex_m/cmse/' not found, in CODEOWNERS

this is a spurious failure. let me see what I can do


Added support for SplFileInfo for Finder

@teohhanhui as promised here's the PR.

Added tests for the Finder component, resulted in some bugfix (removed the use of Doctrine Loader)
Added the support for SplFileInfo as requested in #64

Is there any reason to limit it to Symfony\Component\Finder\SplFileInfo instead of the base SplFileInfo?

None, good point.

@teohhanhui confirm me if it's good on your side.


removed profiles from popular whose stats are not visible

Fixes Issue #2581

Changes proposed
Have removed the profiles of those whose stats are not public, so when it's checking for stats it's checking if stats are visible than only show it

Check List (Check all the applicable boxes)

[ x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[] All new and existing tests passed.
[x ] This PR does not contain plagiarized content.
[ x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers
Do let me know if there are any changes needed ! Thank you !

Ooo my bad will check it out and make the changes


atlas upgrade

add subcortical!

here is citation:
https://www.nature.com/articles/s41593-020-00711-6
https://github.com/yetianmed/subcortex/tree/master/Group-Parcellation/3T/Cortex-Subcortex
Let's use these:
https://github.com/yetianmed/subcortex/blob/master/Group-Parcellation/3T/Cortex-Subcortex/Schaefer2018_400Parcels_17Networks_order_Tian_Subcortex_S1.dlabel.nii
https://github.com/yetianmed/subcortex/blob/master/Group-Parcellation/3T/Cortex-Subcortex/Schaefer2018_400Parcels_17Networks_order_Tian_Subcortex_S2.dlabel.nii
https://github.com/yetianmed/subcortex/blob/master/Group-Parcellation/3T/Cortex-Subcortex/Schaefer2018_400Parcels_17Networks_order_Tian_Subcortex_S3.dlabel.nii
https://github.com/yetianmed/subcortex/blob/master/Group-Parcellation/3T/Cortex-Subcortex/Schaefer2018_400Parcels_17Networks_order_Tian_Subcortex_S4.dlabel.nii

@sattertt ^^


New config options

Hi, this is an awesome component.
Can you add some options like: support to record video, maxVideoDuration (in video record and in video selection with duration predicate)?
Thanks

Sure, Are You need just one option? -> 'maxVideoDuration'

Yep. maxVideoDuration but this method should be affect video recording and filter videos from camera roll via predicate filter. It's possible?


Uncaught Exception: Object->__call(): the method 'getversionedstages' does not exist on 'CustomBlock'

I recently updated an old site to a new version of SilverStripe (currently 3.1.2, but looking into 3.2). I also updated silverstripe-blocks from 0.x to 1.x. I followed the migration guide, and all the blocks work nicely on my site, but when in admin UI I try to create blocks to a new page, I get this error
Uncaught Exception: Object->__call(): the method 'getversionedstages' does not exist on 'CustomBlock'
My CustomBlock class looks bascially like this (I omitted db fields and CMS fields since they don't seem to affect the issue);
class CustomBlock extends Block
{
    private static $singlar_name = 'Custom Block';
    private static $plurar_name = 'Custom Blocks';

    private static $db = array(
    );

    public function getCMSFields()
    {
        $fields = parent::getCMSFields();
        return $fields;
    }
}

I can fix it by adding
public function getVersionedStages() {
	return $this->stages;
}

to my CustomBlock class, but isn't this something Block should handle since it implements the versioning?

Never mind. I updated Silverstripe from 3.1.2 to 3.1.13 and it works. I didn't expect a minor version upgrade to make a big difference.


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1153 ms

Resolved: Bofrost.lu performance has improved in feb01ec after 7 minutes.


Error 0x80070003 after manually installing/uninstalling when launching bash.exe

Your Windows build number:

Microsoft Windows [version 10.0.17134.112]

What you're doing and what's happening:

Everything have been running on an elevated cmd/powershell.

I manually installed WSL without Windows Store with this answer on SO (it was a really bad idea).
bash.exe working well at the moment (created a user and apt-get update)
Tried to uninstall it with lxrun /uninstall /full.
Throw an error 0x80070003 for uninstall, as well when I start bash.exe.
Deleted all files related to Ubuntu/Canonical stuff.

After that, I tried to install it with lxrun in hope to get rid of the error:

lxrun /install /y: installation ok, didn't asked for the creation of a user.
bash.exe still broken but works fine when I start Bash on Ubuntu on Windows from Start Menu.

I think something messed up from the beginning when I tried to manually install WSL and now my installation is semi-broken.
I restarted my computer between some tasks and also tried to restart LxssManager service.

What's wrong / what should be happening instead:

bash.exe should run WSL properly and not give Error 0x80070003

use wslconfig /u <distro-name> to uninstall that distro. And delete this registry Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss.

I don't recommend manually deleting any registry state.

So, I have done what @Biswa96 said, now when I run bash I don't get the error anymore but instead ask me to download WSL. Seems to be OK.
However, when I run lxrun /uninstall /y or lxrun /uninstall /full /y I got an error 80070002.
Is this intended since I have uninstalled WSL Ubuntu? Or should I clean something else before installing WSL Ubuntu with lxrun?

@TotomInc OK, let me elaborate the problem. The error 0x80070003 may mean that the path where you've installed Ubuntu is not present/deleted/removed. There is a second answer in that SO question, written by me.
LxRun.exe /uninstall may only work with legacy installation i.e. LxRun.exe /install. So DON'T use it. Instead use the following procedure. Restart the LxssManager service if you want.
Download the Appx/ZIP file as you did it before. Delete the registry path (as I said before) IF AND ONLY IF there is no other distro installed. Extract Ubuntu.exe and install.tar.gz in a folder path, for example, C:\MyFiles\Ubuntu. Run this command as administrator:
icacls "C:\MyFiles\Ubuntu" /grant Everyone:(OI)(CI)(F)

Now run ubuntu.exe as administrator and it will be installed.

@TotomInc OK, let me elaborate the problem. The error 0x80070003 may mean that the path where you've installed Ubuntu is not present/deleted/removed. There is a second answer in that SO question, written by me.
LxRun.exe /uninstall may only work with legacy installation i.e. LxRun.exe /install. So DON'T use it. Instead use the following procedure. Restart the LxssManager service if you want.
Download the Appx/ZIP file as you did it before. Delete the registry path (as I said before) IF AND ONLY IF there is no other distro installed. Extract Ubuntu.exe and install.tar.gz in a folder path, for example, C:\MyFiles\Ubuntu. Run this command as administrator:
icacls "C:\MyFiles\Ubuntu" /grant Everyone:(OI)(CI)(F)

Now run ubuntu.exe as administrator and it will be installed. And use wslconfig.exe /u Ubuntu to uninstall it.

Thanks @Biswa96 it works well.

Hello
PS C:\Users\shahj\Downloads\Ubuntu-16.04> wslconfig.exe
Performs administrative operations on Windows Subsystem for Linux

Usage:
    /l, /list [/all] - Lists registered distributions.
        /all - Optionally list all distributions, including distributions that
               are currently being installed or uninstalled.
    /s, /setdefault <DistributionName> - Sets the specified distribution as the default.
    /u, /unregister <DistributionName> - Unregisters a distribution.

I first got a list of all the Windows Subsystems for Linux currently installed on the machine:
PS C:\Users\batman\Downloads\Ubuntu-16.04> wslconfig.exe /l
Windows Subsystem for Linux Distributions:
Ubuntu-18.04 (Default)
Ubuntu

I then deleted them both:
PS C:\Users\batman\Downloads\Ubuntu-16.04> wslconfig.exe /u Ubuntu
Unregistering...
PS C:\Users\batman\Downloads\Ubuntu-16.04> wslconfig.exe /l
Windows Subsystem for Linux Distributions:
Ubuntu-18.04 (Default)
PS C:\Users\batman\Downloads\Ubuntu-16.04> wslconfig.exe /u Ubuntu-18.04
Unregistering...

Ensured there were no existing subsystems:
PS C:\Users\batman\Downloads\Ubuntu-16.04> wslconfig.exe /l
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Windows Store:
https://aka.ms/wslstore
PS C:\Users\batman\Downloads\Ubuntu-16.04>

And I was up and running again!
Just re-installed the Windows Subsystem for Linux again.

Note: You may also get Error 0x80070003 if your domain has configured McAfee to block loading of WSL.  (You'd think there would be a nice, clear message, but you just get Error 0x80070003 and you have go dig through the event log to discover the policy.)
This is not a bug in WSL -- but it is a common explanation for Error 0x80070003 in the corporate environment.

Note: You may also get Error 0x80070003 if your domain has configured McAfee to block loading of WSL. (You'd think there would be a nice, clear message, but you just get Error 0x80070003 and you have go dig through the event log to discover the policy.)
This is not a bug in WSL -- but it is a common explanation for Error 0x80070003 in the corporate environment.

No, No McAfee only windows solution


Display helpful message when suggest returns no valid suggestions

The current Infoview displays "Try this:" without any subsequent content when there are no valid suggestions. With this PR, the Infoview displays the message "No valid suggestions." instead.
Before:

After:

Looks good, thank you!

I'm going to steal this if you don't mind :)  Maybe in the future, it would be great to move the code for displaying tactic suggestions to a separate package or directly to the upstream.


Finish adding grpc-gateway metadata to all endpoints

Right now only one endpoint has this:
https://github.com/spacemeshos/api/blob/8ce7510395f20fd4cb32f6a2285a97d04966f880/proto/spacemesh/v1/node.proto#L11-L16

@avive do we want to enable the gateway for every endpoint?


update class vs object

updated the class vs object as it is more understandable to tell someone about class vs object

Please check if this PR fulfills these

[x] The commit message is descriptive of changes
[x] You have tried at least one local test (this includes viewing the changes on your local fork)
[x] Docs have been added / updated as needed (for bug fixes / features)

What kind of change does this PR introduce?

[ ] Typo / Doc Update
[ ] Bug Fix
[x] Feature / New Item

What is the new behavior (if this is a feature change)?

[ ] Added Interview Technical Question
[ ] Added Interview Whiteboard Question
[x] Corrected existing items
[ ] Other

Other information:

This is great! I think a few code snippets or details added to the descriptions would help down the line, but I like it!


Fix issue: Use of Legacy String Ref API

Issue described here

Thanks for submitting this. Unfortunately you can't use jsx as we currently don't transpile source code.

Closing this due to changes required. Let me know if you have a time to fix it so I will reopen. Thanks!


Resolves #602: Detect ObjectLiteral for ES6 shorthand function

Resolves #602: Detect ObjectLiteral by checking surrounding context, to handle when ES6 shorthand function is first prop.
The tests include all currently handled scenarios of checking the surrounding context, such as:

x = {..}
return {..}
fn({..})
fn(x, {..})

Fantastic!


[Bug Report] Hopper "global" XML error

Describe the bug
When trying to run the Hopper-v4 environment, I receive the following error:
ValueError: XML Error: global coordinates no longer supported. To convert existing models, load and save them in MuJoCo 2.3.3 or older
Element 'compiler', line 2

As explained in https://github.com/deepmind/mujoco/issues/833, this is caused by an upstream change in the Mujoco library. For now, the best way to solve this is to pin Mujoco to version 2.3.3. I, however, wanted to open this issue to track the release of https://github.com/Farama-Foundation/Gymnasium/pull/589. Feel free to close this issue if you think this is unnecessary.
Code example

Install Mujoco v0.28.0.
Try to run the following code:

import gymnasium as gym

if __name__ == "__main__":
    env = gym.make('Hopper-v4', render_mode='human')

    env.reset()
    print("Testing Hopper-v4 environment.")
    for _ in range(1000):
        env.render()
        env.step(env.action_space.sample())

    env.close()
    print("Test finished.")

Be greeted by the error.

System info
Gymnasium install type: pip
Pip version: 23.1.2
Gymnasium version: 0.28.1
Mujoco version: 2.3.6
OS: Ubuntu 20.04
Python: 3.8.10
Additional context
Will be solved when https://github.com/Farama-Foundation/Gymnasium/pull/589  is released.
Checklist

[X] I have checked that there is no similar issue in the repo

Maybe this is already tracked in https://github.com/Farama-Foundation/Gymnasium/pull/572?

This has already been fixed in https://github.com/Farama-Foundation/Gymnasium/pull/589
We will hopefully have a release soon for everyone to use

This has already been fixed in #589 We will hopefully have a release soon for everyone to use

but how to use the file to fix the problem?

This has already been fixed in #589 We will hopefully have a release soon for everyone to use

but how to use the file to fix the problem?

You should just need to use gymnasium v0.29.0


Guided Diffusion lightning wrapper

This PR implements a lightning module for training Guided Diffusion Models based on the official implementation. Their code base has a custom Trainer, which I think is not necessary because lightning has all the functionalities plus more and I think this will make it easier to use. Additionally, Guided Diffusion is a base model for UQ-specific Diffusion models and therefore it would be handy for other models as well.

#105 OpenAI implementation is not maintained anymore, so support through denoising-diffusion-pytorch implementation


Don't hard-code future dates

Well, that didn't work out as well as you thought it would, did it now:
https://github.com/psu-stewardship/scholarsphere/commit/6b0a84465731e7cf03aecb39a972a1e514c68e55#diff-ae57f13690d6dca07faad047551cc550R33

Oh past self…always such a turkey

Coverage remained the same at 55.997% when pulling 8d88f7cd4afe8f5c44e2b29e168dec5ea82be953 on test-fixes into e8fa8c3055badb2108f88d204dd1931dc168f29c on develop.


Replacement for FastCsvReader from its author

Hello, I am the original author of FastCsvReader. It's been a long while since I wrote that library and I had a replacement which was on Codeplex that I recently put on github. Upon seeing your project, I thought it might interest you.
You can take a look at https://github.com/slorion/nlight for the library. The CSV reader is https://github.com/slorion/nlight/blob/master/src/NLight/IO/Text/DelimitedRecordReader.cs. You can go to https://github.com/slorion/nlight/tree/master/src/NLight.Tests.Unit/IO/Text to see it in action or https://github.com/slorion/nlight/tree/master/src/NLight.Tests.Benchmarks to benchmark it (including against my old reader).
I plan to release the library on nuget later this week, after adding some more unit tests.
p.s. My name is Sébastien Lorion, you misspelled it for "Sebastian Lorien" in a couple of places :)

Sébastien
Thanks for the information - I'll check it out and fix up your name :-)
I'd also suggest posting this information against the original CodeProject article as it still gets traffic

I agree and I just posted an edit to the article pointing to this repository as well as my new library. Thank you again for taking the time to setup this repo.


Create LocationView

Create LocationView according to the blueprint and the CA Lab code.

check this: https://github.com/CSC207-2024F-UofT/NoteApplication


BigInt not supported on Ledger Live app

We are currently working on Stacks integration on Ledger Live.
The library uses js native biting implementation to handle big numbers. Unfortunately, it is not supported on older react native versions. Ledger Live Mobile is planning to upgrade the react native version they use, but in the meanwhile, the BigInt support is done by using different libraries, like BigNumberJS. BigInt cannot be polyfilled globally, as it could affect other blockchain integrations.
Is it possible to handle big number with BigNumber.js? Or do you think is any other way to handle this situation.

@janniks Do you suspect BigInt could be removed as a requirement from the transactions package, or might @emmanuelm41 be better off forking and removing himself for this particular contextual usage?

Thanks for the input! The problem seems to be that we're dependent Ledger (the company) to update their JS runtime and we don't have a way to secure the update from them.
@emmanuelm41 Might you want to check a previous version and see if it works for our purposes?

@janniks thanks for your answer. I will test that specific version. We are not signing the tx internally actually, as the signing process is happening on the ledger HD. We are using the lib to generate the boilerplate tx object, fetching the nonce and fees, and not much more.
@markmhx let's try that version specifically. I will let you know!

@janniks I have fetched the v3.5.1 and it still uses BigInt for getNonce function for example. Is that possible?

1.3.5 doesn't use BigInt for getNonce. This might be the point in time that works. I will go over the changelog to see if there are important changes that are missed.
Otherwise we might need to think about creating a fork of the important things for ledger live. Do you have a list of features/methods which are required?

This is what we are using today:
import {
  txidFromData,
  getNonce,
  AnchorMode,
  UnsignedTokenTransferOptions,
  makeUnsignedSTXTokenTransfer,
  estimateTransfer,
  UnsignedTokenTransferOptions,
  createMessageSignature
} from "@stacks/transactions/dist";

We are using  @stacks/network too, but I don't see there is a 1.3.5 version for that package.

👍<EMAIL_ADDRESS>uses<EMAIL_ADDRESS>so those are compatible

Looking at getNonce and estimateTransfer is would also be possible to use the Stacks API directly (used by those methods already). And add some custom code.

@stacks/blockchain-api-client
Stacks API
Stacks API: /v2/fees/transfer
Stacks API: /v2/accounts/{address} pseudo-code: estimateTransfer() = feeRate * transaction.serialize.byteLength

Let me know where I can help

<EMAIL_ADDRESS>uses<EMAIL_ADDRESS>so those are compatible

@janniks I think it works with these two packages. Let me confirm it, but it seems to work well...

@janniks it works... but now we have another issue... this lib uses BigInt internally too
import { c32addressDecode } from "c32check";
I use it to check if an address is valid or not. Do we have another way to do it?

Have you tried 1.1.3 for c32check<EMAIL_ADDRESS>uses 1.1.1, but anything <2.0.0 would not use bigint (I believe)

Yes, you are right. It works now. Thanks!

Ok, everything works now. I think I can close this issue. The moment they add support to BigInt on React Native, we can update to newer libs.


feat(test): POC e2e tests

Summary

This PR contains a sample End-2-End test and a configuration for each tested service.
See related gist for details and instructions about how to run tests on each service.

Implementation:

https://github.com/algolia/instantsearch-e2e-tests
https://github.com/algolia/instantsearch.js/pull/4035


README enhancements

Move the introduction to Coroutines, LiveData and Kotlin DSL in the individual README file within the respective module.

Will try to do it.
If I am not wrong, coroutinespermission, dslpermission and livedatapermission are those respective modules. Right?

Yes. Let the top portion till Coroutines support be in top-level README.

Thanks for submitting PR. I will review once I am free.


Operation not permitted (Errno::EPERM) on using "--user" or "--group" parameter

Describe the bug
Fluentd crashes when it's started with either "--user" or "--group" parameter with the following error message:
/usr/lib64/ruby/gems/2.5.0/gems/serverengine-2.1.1/lib/serverengine/privilege.rb:50:in `groups=': Operation not permitted (Errno::EPERM)
To Reproduce
Start fluentd with "--user" or "--group" parameter.
Expected behavior
No crash.
Your Environment

Fluentd 1.5.2
Operating system:
NAME="openSUSE Leap"
VERSION="15.0"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.0"
PRETTY_NAME="openSUSE Leap 15.0"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.0"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"
Kernel version: 4.4.0-150-generic

Your Configuration
<match fluent.**>
  @type null
</match>

# Example:
# {"log":"[info:2016-02-16T16:04:05.930-08:00] Some log text here\n","stream":"stdout","time":"2016-02-17T00:04:05.931087621Z"}
<source>
  @type tail
  path /var/log/containers/*_fluentd_*.log
  pos_file /var/log/es-containers-fluentd-calico-peacock.log.pos
  tag kubernetes.*
  time_key time
  time_format '%Y-%m-%dT%H:%M:%S.%NZ'
  format json
  read_from_head true
</source>

<filter kubernetes.**>
  @type kubernetes_metadata
</filter>

<filter kubernetes.**>
  @type record_transformer
  enable_ruby
  <record>
    time_epoch ${time.to_f.to_s.gsub('.','').to_i}
    @timestamp ${time.strftime('%Y-%m-%dT%H:%M:%S.%NZ')}
    namespace ${record["kubernetes"]["namespace_name"]}
    host ${record["kubernetes"]["host"]}
    container ${record["kubernetes"]["container_name"]}
    pod ${record["kubernetes"]["pod_name"]}
  </record>
  remove_keys stream,docker,kubernetes
</filter>

<filter **>
  @type grep
  regexp1 "namespace ^fluentd$"
  exclude1 "container (fluentd|kibana|grafana|prometheus-kube-state-metrics|prometheus-alertmanager)"
</filter>

<match **>
   @type elasticsearch
   @log_level info
   include_tag_key true
   host elasticsearch
   port 9200
   logstash_format true
   time_key_format '%Y-%m-%dT%H:%M:%S.%NZ'
   # Set the chunk limit the same as for fluentd-gcp.
   buffer_chunk_limit 2M
   # Cap buffer memory usage to 2MiB/chunk * 32 chunks = 64 MiB
   buffer_queue_limit 32
   flush_interval 5s
   # Never wait longer than 5 minutes between retries.
   max_retry_wait 30
   # Disable the limit on the number of retries (retry forever).
   disable_retry_limit
   # Use multiple threads for processing.
   num_threads 8
</match>

Your Error Log
Traceback (most recent call last):
	10: from /usr/bin/fluentd:8:in `<main>'
	 9: from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:39:in `require'
	 8: from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
	 7: from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:135:in `require'
	 6: from /usr/lib64/ruby/gems/2.5.0/gems/fluentd-1.5.2/lib/fluent/command/fluentd.rb:310:in `<top (required)>'
	 5: from /usr/lib64/ruby/gems/2.5.0/gems/fluentd-1.5.2/lib/fluent/supervisor.rb:502:in `run_supervisor'
	 4: from /usr/lib64/ruby/gems/2.5.0/gems/fluentd-1.5.2/lib/fluent/supervisor.rb:597:in `supervise'
	 3: from /usr/lib64/ruby/gems/2.5.0/gems/fluentd-1.5.2/lib/fluent/supervisor.rb:577:in `dry_run'
	 2: from /usr/lib64/ruby/gems/2.5.0/gems/fluentd-1.5.2/lib/fluent/supervisor.rb:782:in `change_privilege'
	 1: from /usr/lib64/ruby/gems/2.5.0/gems/serverengine-2.1.1/lib/serverengine/privilege.rb:50:in `change'
/usr/lib64/ruby/gems/2.5.0/gems/serverengine-2.1.1/lib/serverengine/privilege.rb:50:in `groups=': Operation not permitted (Errno::EPERM)

Please see your log.

Operation not permitted

You don't have permission to the specified user.
Closing because you don't follow the contribution guide. https://github.com/fluent/fluentd/blob/master/CONTRIBUTING.md#got-a-question-or-problem

You don't have permission to the specified user.
@ganmacs Permission for what exactly? Isn't this exactly the purpose of providing "--user" and "--group": to run fluentd as this user of this group instead of almighty root?
Is it intended that fluentd crashes instead of exiting graciously with a well-understandable error message, e.g. which operation is not permitted and which permissions would be required?

I read the contribution guide but fluentd crashing directly when using documented parameters that don't mention any specific permissions being required felt more like a bug than a question..

You don't have permission to the specified user.

@ganmacs Permission for what exactly? Isn't this exactly the purpose of providing "--user" and "--group": to run fluentd as this user of this group instead of almighty root?
Is it intended that fluentd crashes instead of exiting graciously with a well-understandable error message, e.g. which operation is not permitted and which permissions would be required?
I read the contribution guide but fluentd crashing directly when using documented parameters that don't mention any specific permissions being required felt more like a bug than a question..

with a well-understandable error message, e.g. which operation is not permitted and which permissions would be required?

This point is right. Basically, setgroups needs root permission so adding it to log message is better.

Okay, so if I understand correctly, I'll need to start fluentd as root because setgroups needs root permission, but then the user and group set via the parameters will actually run it?

Is it intended that fluentd crashes instead of exiting graciously with a well-understandable error message, e.g. which operation is not permitted and which permissions would be required?

Right. Sorry. It's my bad. This issue looks like we need to discuss.

then the user and group set via the parameters will actually run it?

Yes. I confirmed.
$ cat Dockerfile
FROM ruby:2.6

RUN gem install fluentd
RUN groupadd -r fluent && useradd -r -g fluent fluent

ADD fluent.conf .

CMD ["fluentd", "--user", "fluent", "--group", "fluent", "-c", "fluent.conf"]
$ docker build -t test-user .
Sending build context to Docker daemon  3.072kB
Step 1/5 : FROM ruby:2.6
 ---> 682cc2f5b383
Step 2/5 : RUN gem install fluentd
 ---> Using cache
 ---> b1894b85a8f8
Step 3/5 : RUN groupadd -r fluent && useradd -r -g fluent fluent
 ---> Using cache
 ---> 13fe67ebcf99
Step 4/5 : ADD fluent.conf .
 ---> Using cache
 ---> 5c1a1389b0cb
Step 5/5 : CMD ["fluentd", "--user", "fluent", "--group", "fluent", "-c", "fluent.conf"]
 ---> Using cache
 ---> f001205fc76f
Successfully built f001205fc76f
Successfully tagged test-user:latest
$ docker run -it test-user
2019-08-01 02:37:43 +0000 [info]: parsing config file is succeeded path="fluent.conf"
2019-08-01 02:37:43 +0000 [warn]: both of Plugin @id and path for <storage> are not specified. Using on-memory store.
2019-08-01 02:37:43 +0000 [warn]: both of Plugin @id and path for <storage> are not specified. Using on-memory store.
2019-08-01 02:37:43 +0000 [info]: using configuration file: <ROOT>
  <source>
    @type dummy
    tag "dummy"
  </source>
  <match dummy>
    @type stdout
    <buffer>
      flush_interval 1s
    </buffer>
  </match>
</ROOT>
2019-08-01 02:37:43 +0000 [info]: starting fluentd-1.6.3 pid=1 ruby="2.6.3"
2019-08-01 02:37:43 +0000 [info]: spawn command to main:  cmdline=["/usr/local/bin/ruby", "-Eascii-8bit:ascii-8bit", "/usr/local/bundle/bin/fluentd", "--user", "fluent", "--group", "fluent", "-c", "fluent.conf", "--under-supervisor"]
2019-08-01 02:37:43 +0000 [info]: gem 'fluentd' version '1.6.3'
2019-08-01 02:37:43 +0000 [info]: adding match pattern="dummy" type="stdout"
2019-08-01 02:37:43 +0000 [info]: adding source type="dummy"
2019-08-01 02:37:43 +0000 [warn]: #0 both of Plugin @id and path for <storage> are not specified. Using on-memory store.
2019-08-01 02:37:43 +0000 [warn]: #0 both of Plugin @id and path for <storage> are not specified. Using on-memory store.
2019-08-01 02:37:43 +0000 [info]: #0 starting fluentd worker pid=8 ppid=1 worker=0
2019-08-01 02:37:43 +0000 [info]: #0 fluentd worker is now running worker=0
2019-08-01 02:37:44.063591900 +0000 dummy: {"message":"dummy"}
2019-08-01 02:37:45.079370200 +0000 dummy: {"message":"dummy"}
2019-08-01 02:37:46.094923300 +0000 dummy: {"message":"dummy"}
2019-08-01 02:37:47.016230800 +0000 dummy: {"message":"dummy"}

Yes. I confirmed.

@ganmacs Okay, thanks 🙂

Hello, I was working on fluentd upgrades recently, and I encounter this problem, too.
Describe the bug
Fluentd crashes when it's started with the command
fluentd --daemon <pid file> --user <user> --group <group> --config <conf_file> --log <log_file>
with the following error message:
/usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/privilege.rb:50:in `groups=': Operation not permitted
However,  fluentd works without the option 'daemon' of the above command.
To Reproduce
Start fluentd with fluentd --daemon <pid file> --user <user> --group <group> --config <conf_file> --log <log_file>
Expected behavior
No crash.
Your Environment
Operating system       CentOS 8.2.2004
ruby                   2.5.5p157
fluentd                1.11.2
fluent-plugin-sqlite3  1.0.2

Your Error Log
Starting fluentd: Traceback (most recent call last):
        16: from /usr/local/bin/fluentd:23:in `<main>'
        15: from /usr/local/bin/fluentd:23:in `load'
        14: from /usr/local/share/gems/gems/fluentd-1.11.2/bin/fluentd:8:in `<top (required)>'
        13: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:59:in `require'
        12: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:59:in `require'
        11: from /usr/local/share/gems/gems/fluentd-1.11.2/lib/fluent/command/fluentd.rb:341:in `<top (required)>'
        10: from /usr/local/share/gems/gems/fluentd-1.11.2/lib/fluent/supervisor.rb:562:in `run_supervisor'
         9: from /usr/local/share/gems/gems/fluentd-1.11.2/lib/fluent/supervisor.rb:712:in `supervise'
         8: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/daemon.rb:68:in `run'
         7: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/daemon.rb:107:in `main'
         6: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/daemon.rb:142:in `daemonize_with_double_fork'
         5: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/daemon.rb:142:in `fork'
         4: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/daemon.rb:150:in `block in daemonize_with_double_fork'
         3: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/daemon.rb:150:in `fork'
         2: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/daemon.rb:154:in `block (2 levels) in daemonize_with_double_fork'
         1: from /usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/privilege.rb:50:in `change'
/usr/local/share/gems/gems/serverengine-2.2.1/lib/serverengine/privilege.rb:50:in `groups=': Operation not permitted (Errno::EPERM)

same here, ubuntu 20

Same issue i am facing -
fluentd  -v --user 0  --group 0  -c fluent-test-tail.conf
2021-01-22 20:23:41 +0530 [info]: fluent/log.rb:329:info: parsing config file is succeeded path="fluent-test-tail.conf"
2021-01-22 20:23:41 +0530 [info]: fluent/log.rb:329:info: gem 'fluent-plugin-prometheus' version '1.8.5'
2021-01-22 20:23:41 +0530 [info]: fluent/log.rb:329:info: gem 'fluentd' version '1.12.0'
Traceback (most recent call last):
../.gem/ruby/gems/serverengine-2.2.2/lib/serverengine/privilege.rb:41:in `change_privilege': Operation not permitted (Errno::EPERM)

Same issue i am facing -
fluentd  -v --user 0  --group 0  -c fluent-test-tail.conf
2021-01-22 20:23:41 +0530 [info]: fluent/log.rb:329:info: parsing config file is succeeded path="fluent-test-tail.conf"
2021-01-22 20:23:41 +0530 [info]: fluent/log.rb:329:info: gem 'fluent-plugin-prometheus' version '1.8.5'
2021-01-22 20:23:41 +0530 [info]: fluent/log.rb:329:info: gem 'fluentd' version '1.12.0'
Traceback (most recent call last):
../.gem/ruby/gems/serverengine-2.2.2/lib/serverengine/privilege.rb:41:in `change_privilege': Operation not permitted (Errno::EPERM)

sudo fluentd .... also doesn't work. Can you help ?

sudo fluentd .... also doesn't work. Can you help ?


Overlay interacts with Modern Warfare in the background.

As above, when using the steam overlay to chat for example, it also interacts with the game.

This is an issue with the Steam overlay itself and how Steam handles hooking GPU accelerated launchers. I'm not aware of a workaround for this except to use GloSC.
I'm currently investigating adding a hook manager into a future version of OSOL or forking GloSC and adding OSOL's features to it (given that the GloSC project is now is maintenance-only mode).

I tested some possible workarounds just now and for some launchers you can get away with setting SkipLauncher=True and ReLaunch=False. This would have OSOL launch only the game (but still monitor the launcher once the game exits due to CloseLauncher=True being the default) and the game would usually launch its parent launcher if it isn't already running. The Steam overlay should still be able to hook the game in this situation but not always. Try it and see if it works for you.

Thanks mate, I'll give them a go later on and let you know how I go :)

No luck with those changes, this is what my .ini looks like when it's business as normal.
[Paths]
GamePath=X:\Games\Call of Duty Modern Warfare\ModernWarfare.exe
LauncherPath=C:\Programs\Battle.net\Battle.net.exe
LauncherArgs=--exec="launch ODIN"
LauncherURI=
GameArgs=
MonitorPath=
PreLaunchExecPath=
PreLaunchExecArgs=
PostGameExecPath=
PostGameExecArgs=
[Options]
ReLaunch=True
SkipLauncher=False
CloseLauncher=True
AutoGameLaunch=True
MinimizeLauncher=False
ElevateExternals=False
ForceKillExternals=False
PreGameLauncherWaitTime=5
PreGameWaitTime=5
PostGameWaitTime=5
ProcessAcquisitionTimeout=120
InterProcessAcquisitionTimeout=15
GameProcessAffinity=
GameProcessPriority=Normal
[Info]
ReleaseVersion=<IP_ADDRESS>


Container restarts every hour

Operating system
Ubuntu 24.04 LTS
Description
Every hour or so, the container restarts. Event Viewer shows Kernel-Boot entries every hour from whenever the container was last started. I should note that the LTSC evaluation period has expired.
To make sure it's every hour, I used this script to log every time the container shuts down:
while :
do
        docker compose up
        echo $(date) >> log.log
done

log.log:
Fri 9 Aug 15:14:02 IST 2024
Fri 9 Aug 16:14:17 IST 2024

I have docker running in Snap but as far as I can tell, no other container has this issue.
Docker compose
services:
windows:
image: dockurr/windows
container_name: windows
environment:
VERSION: "ltsc10"
REGION: "en-GB"
KEYBOARD: "en-GB"
DISK_SIZE: "100G"
RAM_SIZE: "6G"
CPU_CORES: "4"
volumes:
- ./storage:/storage
devices:
- /dev/kvm
cap_add:
- NET_ADMIN
networks:
vlan:
ipv4_address: <IP_ADDRESS>
ports:
- 8006:8006
- 27000-27020:27000-27020
- 28960-28970:28960-28970
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m
networks:
vlan:
external: true
Docker log
BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,E8DA8AB4-ABBF-4088-9C25-C982352E5640,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,E8DA8AB4-ABBF-4088-9C25-C982352E5640,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
Screenshots (optional)
No response

Issue was with LTSC evaluation period expiring. It shuts down every hour because of this.


Why I can only read the cards by DumpInfo sketch if there are at least 2 cards ?

Anyone can tell me why I can not read a single Mifare card? Can read the card only if having at least 2 cards side by side. For example: 2 cards could be included first one is a 13.56MHz  and another is whatever like 13.56Mhz or 125Mhz.
Please point out why that? Thanks

@saytinh I think it is a hardware issue.


Add UMD bundle to npm package

Since wzrd.in doesn't work (SSL certificate issue) it's impossible to import raf directly from CDN. It'd be nice to add UMD bundle to npm package, this way we can import lib from unpkg.com - example

It seems more expedient to get the ssl issue fixed rather than polluting thousands of packages with obsolete module formats, one at a time.

The certificate has been renewed.


Fix error in documentation about unary not

rgbasm.5 stated that ! (unary not operator) always returns 1.
This change reflects the actual behavior of the operator.

Merging, but I think the behavior should be changed to match the documentation instead. :^)


Defining evolving non homogenous Dirichlet boundary conditions in a NonlinearForm

Dear all,
I have defined a NonlinearForm on which I want to impose evolving non homogenous Dirichlet boundary conditions. By evolving, I mean that the NonlinearForm will be used for several time steps and I want to change the values of the imposed Dirichlet boundary conditions at each time step.
It seems that there is no example of using SetEssentialBC with a right hand side.
To make things clearer, here is a (non functional, of course) code snipset which tries to impose the boundary conditions on a unit cube. The faces of the cube are xy0 (normal along Oz), xy1, etc...
I came to the following code which I call at each time step:
    auto fixed_dirichlet_dofs = mfem::Array<int>{};
    auto fixed_dirichlet_values = std::vector<double>{};
    auto append_dof = [&fixed_dirichlet_dofs, &fixed_dirichlet_values, &mesh,
                       &fespace](const auto boundary, const auto normal,
                                 const auto value) {
      auto tmp = mfem::Array<int>{};
      auto ess_bdr = mfem::Array<int>(mesh->bdr_attributes.Max());
      ess_bdr = 0;
      ess_bdr[boundary] = 1;
      fespace->GetEssentialTrueDofs(ess_bdr, tmp, normal);
      fixed_dirichlet_dofs.Append(tmp);
      fixed_dirichlet_values.resize(fixed_dirichlet_values.size() + tmp.Size(),
                                    value);
    };
    append_dof(0, 1, 0.);     // xz0
    append_dof(1, 2, 0.);     // xy0
    append_dof(4, 0, 0.);     // yz0
    append_dof(2, 0, 1e-2 * (t + dt) / 10);  // yz1
    auto rhs = mfem::Vector{fixed_dirichlet_values.data(),
                            fixed_dirichlet_values.size()};
    p.SetEssentialBC(fixed_dirichlet_dofs, &rhs);

where p is my non linear form.
I don't know is this is the right way to do this. Indeed, there are many thing questionable here:

I call SetEssentialBC at each time step. I don't know if it is valid.
I shall probably precomputed fixed boundary conditions (i.e. boundary conditions whose values don't evolve)...

Currently, my residuals are 0, so probably no BC is applied and my code finishes with a memory fault (double free)...
Any help would be appreciated.

https://github.com/mfem/mfem/discussions/1948

Desipte @jandrej' help, I still don't find a suitable solution.
Here is a minimal example which shows the trouble.
I think that I initialize my initial value correctly, but in the AssembleElementVector all the values of the unknowns are zero. In my case, it leads to a zero residual.
The test has one element. Its output are:
u1 (initial guess):
0 1 0 1 0 1 0 1
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
AssembleElementVector:
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0

Any idea ?
test.tar.gz

Ok. The culprit has been found. I copy/pasted  code from ex19 where the iterative_mode was set to false as an option to the Newton solver. When this flag is set to true, it seems to works as expected....


Fix: Export 'project-name-ServerlessAliasReference' does not exist.

Fixes https://github.com/serverless-heaven/serverless-aws-alias/issues/181
adds support for serverless v2
drops support for serverless v1
updated dependencies

@HyperBrain could you merge / release?

What's the ETA for the fix to be merged?

Sorry
This bug is merged and release with new version?
Currently I'm using serverless-aws-alias and it's effected and occurs error in deploy.

can we get this released this week? This seems to be a fix much needed for people to use it with latest serverless versions

@HyperBrain Can you kindly review the PR please? It'll be great to use this plugin with the latest framework core version.
Much appreciated!

I get the error..
Serverless Error ---------------------------------------
Export 'project-name-ServerlessAliasReference' does not exist.
Get Support --------------------------------------------
Docs:          docs.serverless.com
Bugs:          github.com/serverless/serverless/issues
Issues:        forum.serverless.com
Your Environment Information ---------------------------
Operating System:          win32
Node Version:              12.18.2
Framework Version:         1.74.1
Plugin Version:            3.6.15
SDK Version:               2.3.1
Components Version:        2.31.12

How are people creating a new project with this plugin without this patch???
Every single time I create a new serverless project with it and I try to deploy I get this error

I don't think anyone is creating new projects with the latest serverless version. Most likely they are locking down the serverless version

Any news on this issue ? I'm also hitting this problem

I am evaluating this plugin for a client and am in a situation where they can't use serverless <=1.62.  Merging this fix would be very appreciated.

Hey, does anyone can approve this merge ?

Any chances of this PR to be approved?

@HyperBrain, could you please review/merge this one? Since it's really a bottleneck for projects of mine, we don't want to give up on using this plugin)

@HyperBrain Any updates?...

@Enase Would you consider releasing it as a separate package (serverless-aws-alias-hotfixed)? It has been almost a year and most of us would really appreciate a working version. Thank you in advance.

@Enase Would you consider releasing it as a separate package (serverless-aws-alias-hotfixed)? It has been almost a year and most of us would really appreciate a working version. Thank you in advance.

@Bielik20 Feel free to use serverless-aws-alias-fixed
Hope it helps everyone..

@Bielik20 Feel free to use serverless-aws-alias-fixed
Hope it helps everyone..

If this has been fixed, please merge. Would really appreciate it.

If this has been fixed, please merge. Would really appreciate it.

@Bielik20 Feel free to use serverless-aws-alias-fixed
Hope it helps everyone..

I have issue with serverless-aws-alias-fixed
TypeError: Cannot read property 'Properties' of undefined

@Bielik20 Feel free to use serverless-aws-alias-fixed
Hope it helps everyone..

I have issue with serverless-aws-alias-fixed
TypeError: Cannot read property 'Properties' of undefined

@ABRIO-PR Hello!
I didn't add or change any logic that somehow can affect 'Properties' property in this PR. Mb I can help with it, but a way you report the issue doesn't have something to do with software development.

@ABRIO-PR Hello!
I didn't add or change any logic that somehow can affect 'Properties' property in this PR. Mb I can help with it, but a way you report the issue doesn't have something to do with software development.

@Enase I set "role" at the provider and it working. But if set role at functions:
TypeError: Cannot read property 'Properties' of undefined
at AwsAlias.module.exports (/home/and/work/serverless/node_modules/serverless-aws-alias-fixed/lib/stackops/lambdaRole.js:38:11)
at AwsAlias.aliasHandleLambdaRole (/home/and/work/serverless/node_modules/serverless-aws-alias-fixed/lib/aliasRestructureStack.js:43:21)
at AwsAlias.tryCatcher (/home/and/work/serverless/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:544:35)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at PromiseArray._resolve (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
at PromiseArray._promiseFulfilled (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:145:14)
at PromiseArray._iterate (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:115:31)
at PromiseArray.init [as _init] (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:79:10)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:601:21)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:489:14)
at Promise._settlePromiseFromHandler (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at PromiseArray._resolve (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
at PromiseArray._promiseFulfilled (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:145:14)
at PromiseArray._iterate (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:115:31)
at PromiseArray.init [as _init] (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:79:10)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:601:21)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:489:14)
at Promise._settlePromiseFromHandler (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at PromiseArray._resolve (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
at PromiseArray._promiseFulfilled (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:145:14)
at PromiseArray._iterate (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:115:31)
at PromiseArray.init [as _init] (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:79:10)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:601:21)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at _drainQueueStep (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (internal/timers.js:456:21)
at process.topLevelDomainCallback (domain.js:137:15)

@Enase I set "role" at the provider and it working. But if set role at functions:
TypeError: Cannot read property 'Properties' of undefined
at AwsAlias.module.exports (/home/and/work/serverless/node_modules/serverless-aws-alias-fixed/lib/stackops/lambdaRole.js:38:11)
at AwsAlias.aliasHandleLambdaRole (/home/and/work/serverless/node_modules/serverless-aws-alias-fixed/lib/aliasRestructureStack.js:43:21)
at AwsAlias.tryCatcher (/home/and/work/serverless/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:544:35)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at PromiseArray._resolve (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
at PromiseArray._promiseFulfilled (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:145:14)
at PromiseArray._iterate (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:115:31)
at PromiseArray.init [as _init] (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:79:10)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:601:21)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:489:14)
at Promise._settlePromiseFromHandler (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at PromiseArray._resolve (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
at PromiseArray._promiseFulfilled (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:145:14)
at PromiseArray._iterate (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:115:31)
at PromiseArray.init [as _init] (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:79:10)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:601:21)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at Promise._resolveCallback (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:489:14)
at Promise._settlePromiseFromHandler (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:559:17)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at Promise._fulfill (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:673:18)
at PromiseArray._resolve (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:127:19)
at PromiseArray._promiseFulfilled (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:145:14)
at PromiseArray._iterate (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:115:31)
at PromiseArray.init [as _init] (/home/and/work/serverless/node_modules/bluebird/js/release/promise_array.js:79:10)
at Promise._settlePromise (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:601:21)
at Promise._settlePromise0 (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/home/and/work/serverless/node_modules/bluebird/js/release/promise.js:729:18)
at _drainQueueStep (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (/home/and/work/serverless/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (internal/timers.js:456:21)
at process.topLevelDomainCallback (domain.js:137:15)

@ABRIO-PR Could you provide serverless.yml sample?

@ABRIO-PR Could you provide serverless.yml sample?

@ABRIO-PR I'm not sure will it work or not, but you can try to apply this patch and let us know the result.
fix.patch

Index: lib/stackops/lambdaRole.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/lib/stackops/lambdaRole.js b/lib/stackops/lambdaRole.js
--- a/lib/stackops/lambdaRole.js	(revision eab5d8644d17d8b69ee7215bbbb2eb469bc39e57)
+++ b/lib/stackops/lambdaRole.js	(date<PHONE_NUMBER>900)
@@ -34,13 +34,15 @@
 	const roleLogicalId = `IamRoleLambdaExecution${normalizedAlias}`;
 	const role = stageStack.Resources.IamRoleLambdaExecution;

-	// Set role name
-	if (role.Properties.RoleName['Fn::Join']) {
-		_.last(role.Properties.RoleName['Fn::Join']).push(this._alias);
-	}
+	if (role) {
+		// Set role name
+		if (role.Properties.RoleName['Fn::Join']) {
+			_.last(role.Properties.RoleName['Fn::Join']).push(this._alias);
+		}

-	stageStack.Resources[roleLogicalId] = stageStack.Resources.IamRoleLambdaExecution;
-	delete stageStack.Resources.IamRoleLambdaExecution;
+		stageStack.Resources[roleLogicalId] = stageStack.Resources.IamRoleLambdaExecution;
+		delete stageStack.Resources.IamRoleLambdaExecution;
+	}

 	// Replace references
 	const functions = _.filter(stageStack.Resources, ['Type', 'AWS::Lambda::Function']);

@ABRIO-PR I'm not sure will it work or not, but you can try to apply this patch and let us know the result.
fix.patch

Index: lib/stackops/lambdaRole.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/lib/stackops/lambdaRole.js b/lib/stackops/lambdaRole.js
--- a/lib/stackops/lambdaRole.js	(revision eab5d8644d17d8b69ee7215bbbb2eb469bc39e57)
+++ b/lib/stackops/lambdaRole.js	(date<PHONE_NUMBER>900)
@@ -34,13 +34,15 @@
 	const roleLogicalId = `IamRoleLambdaExecution${normalizedAlias}`;
 	const role = stageStack.Resources.IamRoleLambdaExecution;

-	// Set role name
-	if (role.Properties.RoleName['Fn::Join']) {
-		_.last(role.Properties.RoleName['Fn::Join']).push(this._alias);
-	}
+	if (role) {
+		// Set role name
+		if (role.Properties.RoleName['Fn::Join']) {
+			_.last(role.Properties.RoleName['Fn::Join']).push(this._alias);
+		}

-	stageStack.Resources[roleLogicalId] = stageStack.Resources.IamRoleLambdaExecution;
-	delete stageStack.Resources.IamRoleLambdaExecution;
+		stageStack.Resources[roleLogicalId] = stageStack.Resources.IamRoleLambdaExecution;
+		delete stageStack.Resources.IamRoleLambdaExecution;
+	}

 	// Replace references
 	const functions = _.filter(stageStack.Resources, ['Type', 'AWS::Lambda::Function']);

Created a separate  PR for this with only needed change https://github.com/serverless-heaven/serverless-aws-alias/pull/201

@HyperBrain could this be merged? HyperBrain seems inactive in git over the last 2 years... Should we fork this plugin to a new repo?


Support external video buffer, Kickstart switching from keyboard

Moved config key to HELP
F1..F4 select kickstart roms with PB8, PB9
F9/F10 sets PB10 low/high for other uses (pal/ntsc, DF0/DF1 swap)
PB12 is used as an active high display enable to drive external buffer

Todo:

make display enable active low using slave select
Use the OSD to indicate kickstart and option pin state

Rom switching is nice but it will confuse users that system will likely crash since we are not switching during reset?

Okay my longer take on this is that it's a very good idea and should definitely be included. However, it would be nice if it's fully configurable. OSD names for hot keys, and configurable actions on GPIOB (some subset of: mask, set/clear, toggle, count, ...).
This is beyond what you'd want to configure with a few buttons on the OSD directly. It really needs at least easily-modifiable source code. Better would be a plain text config which gets cooked into the build by a Python script. Better still would be the above, but cooked into a pre-built Hex programming file by a Python script.
Then there's a story around upgrade: Download latest, cook in your previous config file (perhaps slightly changed for new options in the new firmware), then Flash it.
I can't see it getting much easier than that while allowing user (or at least downstream project maker/seller) configurability.
Right now I'm working on LCD/OLED + OSD simultaneous output in FlashFloppy. So this sits on the backburner til I've got that sorted. So I guess later this week, best case.

I’m basically re-implementing what I had done on an atmega328 on that keyboard adaptor photo.
On that board I also reset the Amiga when I change kickstarts.
I’ve decided to ditch my atmega design and respin it with STM32 and OSD instead.
I could also use the keyboard and OSD to configure kickstart display names.

Is your aim to produce and sell? Or do a full installation service? Or just a DIY project? I think it affects what the best config method might be. Doing these all via OSD could be a pita.

Sell if there’s some interest.
I won’t be doing an install service.
I’ll be bringing out the UART pins so there’s another config option.
OSD keyboard entry should be fine - we have a full keyboard to type on!

It's not a good story on upgrade though -- which currently losing config -- and not so good for slightly higher volume makers either -- eg. zaxon who wants the df0/df1 switch in every build, and he does scores or even hundreds.
I think for "pre configure" method right now, having a source file modifiable by confident users is okay though.
Yes having a key combo which toggles the keyboard into completely stolen mode makes sense given that presses can be hidden from the host. eg. CTRL-ALT-Del or C-A-Return or similar.

I plan to try a few hardware options over the weekend - all with the aim of safer stronger drive strength on all three channels for better contrast.
Have you finished your current work for now ?
Would you prefer separate PRs for kickstart and display output ?

Yes, I have a fix for rotary encoder on branch "pins" -- as I broke rot.enc. support and in fact it might even be hazardous to connect a rot.enc. at the moment as gpio_pins_connected() drives pins HIGH, while a rot.enc. drives them LOW. So I implemented a fix to be much more careful. :)
I also would like to robustify the I2C protocol a bit, in case of loss of sync.
Neither of the above really affect you: The core display code is now solid.
It probably makes sense to do Kickstart and Disp.Out. as separate PRs as they're totally unrelated. It doesn't matter too much as I will expect to refactor stuff a bit when you're done.

Re Kickstart switching: Is it worth considering one key to cycle between images, vs image per key? Obvs we have plenty of keys, then again will you always be able to remember which image is on which key anyway....
There's also the question of default state of pins relating to hot keys? Perhaps we default to them all LOW. Or we could make that configurable (again, just at build time for now, perhaps).

I think open drain is always the safest default for lines like this.
What’s the flash endurance like on the STM32 ?
I’m tempted to also auto save the kickstart after a period of inactivity.

It's rated for 10k erase cycles. You have to write 2 bytes at a time, but that gives you ~500k smallest-possible writes per 1kb of Flash.

I also would like to robustify the I2C protocol a bit, in case of loss of sync.
I wonder if that explains some weird hang on startup I’m seeing?
My wiring is a mess of dupont wires, so it could easily be me

Neither of the above really affect you: The core display code is now solid.
The connected pins test just screwed me !
It was seeing factory default jumpered cos the gotek has pull-ups

But the Gotek doesn't connect to pins A0-A2 and it's that range the pins-connected tests occur in.

Sorry - Brain fart on my part.
The jumper to enable FF magic mode on A0.A1 trips the factory default test (in the master branch)

I think this PR is dead now.


Library mode does not work with fragments (multi-root node components)

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[X] Read the docs.
[X] Use Vite >=2.0. (1.x is no longer supported)
[X] If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug
Building in library mode only works if components have one top-level tag.
The building of the files work, but when I try to consume then in another Vue project I receive a Invalid VNode type: Symbol(Fragment)
I don't know if this is intended or a bug, but if it is intended I could help by contributing to the guide explaining library mode.
Reproduction
The output from this template will work:
<template>

{{ msg }}

    <button @click="count++">count is: {{ count }}</button>

</template>

But not this one:
<template>

{{ msg }}

  <button @click="count++">count is: {{ count }}</button>
</template>

System Info

vite version: v2.0.0-beta.26
Operating System: Linux
Node version: v12.16.1
Package manager (npm/yarn/pnpm) and version:

Did you... externalize Vue when building in lib mode? It looks like you bundled Vue into your library.

Did you... externalize Vue when building in lib mode? It looks like you bundled Vue into your library.

see 7746674

see 7746674

Closing for now since there's no reproduction I assume this is the cause. let me know if this is not the actual reason.

Closing for now since there's no reproduction I assume this is the cause. let me know if this is not the actual reason.


Remove IFD in kernel build

Resolves #51

Thank you very much for figuring this out. Is it still technically doing IFD though if there are kernelPatches?

Is it still technically doing IFD though if there are kernelPatches?

It's not importing a Nix expr, so as far as I understand it it's more lile a "Read From Derivation", which shouldn't be problematic

I think it's still problematic because builds have to run before the evaluation can occur. I think the magnitude is much less than before but there is still IFD happening.

https://github.com/tpwrules/nixos-apple-silicon/pull/70/files#diff-6db5403c64ac81d76097a9d10fbf02809552a396970b1a594d422515de2f0140R37-R43

It's possible to get rid of the IFD by getting rid of writeFile here and concatenating the config with the patches in Nix code. Instead of readFile (writeFile foo), we just read foo, which isn't the output of a derivation.
I can PR this if needed.


Unexpected behaviour reducing an array of unknown

Bug Report
🔎 Search Terms
reduce, "unknown[]", list of unknown
🕗 Version & Regression Information

This is the behaviour in every version I tried, and I reviewed all FAQ for entries related.

⏯ Playground Link
Playground link with relevant code
💻 Code
// With array of strings, TS works as expected
const arrayOfString = [] as string[]

arrayOfString.reduce((acc, v) => {
    acc = acc + 1;
    return acc
}, 0)

// Bug
const arrayOfUnknown = [] as unknown[]

arrayOfUnknown.reduce((acc, v) => {
    acc = acc + 1; // BUG! Wrongly assumes that the accumulator has the same type as the value: "unknown"
    return acc
}, 0)

🙁 Actual behavior
The inferred type of acc is "unknown" instead of "number".
🙂 Expected behavior
To get the same inferred type when running on an array of string or an array of unknowns.

This is due to the ordering of the reduce overloads; this example "wants" to hit the third overload, but validly selects the second instead. It's not clear to me how we'd fix this without causing other breaks -- a homogeneous reduce call is clearly preferable, but creates a precision loss in this case. Maybe with negated types the second overload could specify not T as the acc value, but who knows what would break.
Please add to #36554 regardless.

This is due to the ordering of the reduce overloads; this example "wants" to hit the third overload, but validly selects the second instead. It's not clear to me how we'd fix this without causing other breaks -- a homogeneous reduce call is clearly preferable, but creates a precision loss in this case. Maybe with negated types the second overload could specify not T as the acc value, but who knows what would break.
Please add to #36554 regardless.

Isn't this wrong since, a single reduce can be used as a combination of filter and map when used together, the code runs faster,
and is easier to deal with and produces the result while using lower memory. I think so one should be able to have an accumulator of the choice one like. This kind of limits the usage of reduce function.

Inference is inference and has to make certain conservative assumptions. You can add a type argument to explicitly specify what you want to happen.

Still the typescript compiler complaints and seeing such errors over the project is a bit triggering.


feat: Upgrade to React 19

This cannot work until preact signals supports React 19 because the symbol name used for react elements has changed, see  https://github.com/preactjs/signals/issues/580#issuecomment-2196321246


x/pkgsite: missing urls for some licenses

What is the URL of the page with the issue?
https://pkg.go.dev/license-policy
What did you expect to see?
all of the license should point to url that describe the license.
What did you see instead?
but some of them don't

@julieqiu I was wondering if you accept CLs for this? If yes, do you have a preference for the remaining links, for example spdx.org/licenses? Thanks!


[milvus-4.1.18] Enhancement: Reset Default Max Limit on Users per Milvus Instance

Author - @Rachit-Chaudhary11
What this PR does / why we need it:
This update will allow for better scalability and flexibility in managing the users access to milvus instance. Presently this limit is set to 100 users per milvus instance and there is no way to increase / decrease the users limit to milvus instance.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [mychartname])
[ ] PR only contains changes for one chart

/assign @zwd1208
Please validate the pull request.

@Rachit-Chaudhary11  Please also sign-off this commit. And you may also need to rebase after the last PR is merged, and make sure the Chart Version is bumped.
same as I mentioned in https://github.com/zilliztech/milvus-helm/pull/61#issuecomment-1963385181

@haorenfsa please validate now.

/lgtm

@Rachit-Chaudhary11  We bump the chart version in every PR.
So please rebase master branch again, and bump the chart version to 4.1.21. Thank you very much.

@haorenfsa please check, I have bumped up the milvus chart version

/assign @zwd1208
@haorenfsa Please validate the pull request.


update /content/loaders & /content/plugins

update /content/loaders & /content/plugins

@Aladdin-ADD


fix: make JwtClaims.newBuilder() public

Fixes #349

since new API was added in JwtClaims this probably should be 0.18.0


MySQL Provider stopped working since v2.29.0

Using the following mysql provider config on any versions after v2.28.0 the endpoint value is either not set or set to <IP_ADDRESS>:3306. Not sure if the mysql provider will automatically use <IP_ADDRESS>:3306 if the value is empty.
provider "mysql" {
  endpoint = module.this.this_rds_cluster_endpoint
  username = module.this.this_rds_cluster_master_username
  password = module.this.this_rds_cluster_master_password
  proxy    = "socks5://<IP_ADDRESS>:8123"
  version  = "~> 1.9"
}

Error when using v2.29.0
Error: Could not connect to server: socks connect tcp <IP_ADDRESS>:8123-><IP_ADDRESS>:3306: EOF

Removing the provider and just checking the output it seems like the correct value is exported. So this is very strange.
terraform --version
Terraform v0.12.29
+ provider.aws v3.24.1
+ provider.mysql v1.9.0
+ provider.random v2.3.0
+ provider.sops v0.5.2

If more info is required please let me know.

hi @maartenschalekamp - unfortunately this module doesn't have anything to do with the MySQL provider. some things you might want to check are security group rules and any NACLs you might have in place on your network/resources

just strange that using module version v2.28.0 it works perfectly fine, but not since version v2.29.0. So cant think of any reason why SG and NACL's will be affected by that.

hi @maartenschalekamp - unfortunately this module doesn't have anything to do with the MySQL provider. some things you might want to check are security group rules and any NACLs you might have in place on your network/resources

just strange that using module version v2.28.0 it works perfectly fine, but not since version v2.29.0. So cant think of any reason why SG and NACL's will be affected by that.

@maartenschalekamp do you have a reproduction we could look at, test?


Use two modes to call/close affinder

Closes #1

Codecov Report

Merging #10 (01c0068) into master (bdd4bd6) will decrease coverage by 2.50%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master     #10      +/-   ##
=========================================
- Coverage    5.00%   2.50%   -2.50%
=========================================
  Files           3       2       -1
  Lines          80      80
=========================================
- Hits            4       2       -2
- Misses         76      78       +2

Impacted Files
Coverage Δ

affinder/affinder.py
0.00% <0.00%> (ø)

affinder/__init__.py

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 bdd4bd6...01c0068. Read the comment docs.

Codecov Report

Merging #10 (01c0068) into master (bdd4bd6) will decrease coverage by 2.50%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master     #10      +/-   ##
=========================================
- Coverage    5.00%   2.50%   -2.50%
=========================================
  Files           3       2       -1
  Lines          80      80
=========================================
- Hits            4       2       -2
- Misses         76      78       +2

Impacted Files
Coverage Δ

affinder/affinder.py
0.00% <0.00%> (ø)

affinder/__init__.py

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 bdd4bd6...01c0068. Read the comment docs.


Driverkit Features Requests: Enhanced auto-discovery, support concurrent builds for multiple headers and compiler versions

Motivation

Augment functionality for primary use case (compile one driver for one kernel build using recommended compiler version).
Add functionality to cover more use cases, for instance https://github.com/falcosecurity/libs/pull/524 or https://github.com/falcosecurity/libs/issues/531.

Feature
Primary Use Cases
[001] Builder Containers

Big +1 https://github.com/falcosecurity/driverkit/issues/194, need multiple builder images. How about covering clang-5.0 to latest and gcc-5 to latest. Could be 2-4 containers toggled within driverkit based on a knowledge base, see also https://github.com/falcosecurity/kernel-crawler/issues/36 responding to https://github.com/falcosecurity/driverkit/issues/194.

[002] Args

arg kernelurls can be misleading, how about introducing kernelheadersurls or headersurls instead?
new arg, option to automatically name driver artifact like kernelrelease $(uname -r).<extension>.
arg driverversion, more options

pass local dir
pass local file .tar.gz (extracts top level libs)
pass url .tar.gz (extracts top level libs)

Extended Use Cases
Extensions that deviate from the primary use case can be useful for dev, test, debug and research or CI integration of driver sanity tests.
[003] Concurrency support

Concurrently download and extract header packages for re-use when re-building many driver artifacts -> output is a directory with subdirectories like:

❯ tree -L 5 /tmp/headers
/tmp/headers
├── 5.15.59-051559-generic
│   ├── control.tar.zst
│   ├── data.tar.zst
│   ├── debian-binary
│   └── usr
...
│       └── src
│           └── linux-headers-5.15.59-051559
...
└── kernel-ml-devel-5.19.0-1.el7.elrepo.x86_64
    └── usr
        └── src
            └── kernels
                └── 5.19.0-1.el7.elrepo.x86_64

Concurrently compile driver for each kernel header passed (multiple kernelheadersurls, auto-select correct container)
Concurrently compile driver for each kernel header passed for each compiler version passed (multiple kernelheadersurls, multiple compilerversions - overwrites auto-selection , multiple drivertypes even)

├── clang-10
│   └── 5.19.0-1.el7.elrepo.x86_64.o
├── clang-14
│   ├── 5.15.59-051559-generic.o
│   └── 5.19.0-1.el7.elrepo.x86_64.o
├── clang-5.0
│   └── 5.19.0-1.el7.elrepo.x86_64.o
├── gcc-10
│   └── 5.19.0-1.el7.elrepo.x86_64.ko
└── gcc-5
    └── 5.19.0-1.el7.elrepo.x86_64.ko
...

Possible new args supporting various scenarios:

new arg kernelheadersdirs - local dir for one extracted kernel header
new arg kernelheaderssubdirs - local dir with subdirs - each subdir is one extracted kernel header
new arg kernelheadersfile as extension to kernelheadersurls,

file that contains one url per line (ubuntu really complicates things given 2 headers packages per kernel ... )

...

Can see that a balance between avoiding confusion and more functionality needs to be found.

arg kernelurls can be misleading, how about introducing kernelheadersurls or headersurls instead?

How about just headers, so we have convergence between this and kernel-crawler? The new proposed in kernel-crawler refers to kernel headers packages as just headers:

Yes just headers would be amazing! Re all other fields and naming, probably worth another round of discussion once everything gets refactored.
Additional note: Some end users may be less familiar with kernel development. Perhaps a small paragraph explaining essentials even in greater detail could help?

Be very clear to explain that end user should go to kernel crawler file and pass the packages from headers and @dwindsor good call which the renaming you suggested it will be an easy 1:1 mapping.
In addition something like ... to build the driver all you need is those headers packages ... bpf uses clang/llvm as compiler while kmod uses gcc ... if you wish to test this in a VM, kernel crawler now also exposes kernels which are the actual kernel package you install to then re-boot into the desired kernel. @dwindsor @FedeDP?

Hi @incertum !
Thanks for this feature request :)

Big +1 https://github.com/falcosecurity/driverkit/issues/194, need multiple builder images. How about covering clang-5.0 to latest and gcc-5 to latest. Could be 2-4 containers toggled within driverkit based on a knowledge base

I am not sure i understood everything well; btw IMO i think that we only need to cover GCC matrix; possibly we only need just one more builder image for newest kernels (with like gcc 10+); as far as i know, we are pretty stable building kernels <5.10. Here @EXONER4TED did some great tests for  #161, perhaps he has some inputs!
Instead, Clang has no such issues; we can build everything with current clang 12 and we should be fine!

arg kernelurls can be misleading, how about introducing kernelheadersurls or headersurls instead?

Mmh i am not sure i get it either :laughing: i mean, we only need kernel headers, therefore i chose the kernelurls naming. Do we need any other urls?

new arg, option to automatically name driver artifact like kernelrelease $(uname -r)..

I am not sure if this is really needed, i mean, what's its use case?

arg driverversion, more options

This is a little-effort feature that IMO can be easily implemented! Are you willing to work on this? :)

Concurrency support

Ugh i fear this! Driverkit was conceived as a simple project with a "single run -> single driver" logic.
I am not sure such a feature would help us, really. I only see the complexity it would bring on the table :/

Augment functionality for primary use case (compile one driver for one kernel build using recommended compiler version).

Driverkit 0.10.1 was just released and has the "multiple builders" feature which should address some points of your use case.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

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


Require file path to be passed to file-related exceptions

The user may not always know which file was the cause of the exception, so we force developers to be more explicit.

Nope, just add it as message


[riak] time to remove riak?

I can't tell what's up with Riak. Basho appeared to implode in ~2016-2017. The Riak client artifacts in Maven haven't updated since then. Every reference to their community mailing lists I can find are defunct so I can't tell when they last updated.
But the repositories for the various subprojects appear active and have had releases? I'm not sure where to ask. Maybe one of us could raise an issue on the RiakKV repo?

hey, I couldnt understand, whats the problem with Riak? I`m doing a research during my graduation, and I planned on using Riak...

The company that drove the majority of the activity on the Riak project does not appear to still be active AFAICT. The code base still has folks doing stuff, but I can not tell where I would even go to ask about e.g. where a person should get help if they have trouble getting a Riak server going.

Okay I added created an issue to gauge if we should update our binding rather than remove it. basho/riak-java-client#720

The riak project is maintained, and new releases are being added - https://github.com/basho/riak/blob/develop-3.0/RELEASE-NOTES.md.  There are still lots of large scale implementations out there, with organisations who are willing to fund work.  However, available resource to do that work is fairly limited and tends to be prioritised towards maintenance/efficiency work rather than enticing new features.
The mailing list is now defunct after a credit card mishap, so communication is poor.  The best place to get help is via github.  There's also a slack channel (https://postriak.slack.com/).  As mentioned on the java client issue, the actual clients are not being updated as part of releases - new functionality has to be exploited by the erlang clients are by calling the APIs directly.

thanks for the follow up! that's really helpful. I'll try to get us to the latest client and make a note of the above wrt riak server versions.


yubikey-neo-manager: drop

Motivation for this change
Get rid of Python 2: https://github.com/NixOS/nixpkgs/issues/101964.
Running neoman produces
Traceback (most recent call last):
  File "/nix/store/3viwpjs3i7w7f81pqf9haxxhyi2bbar2-python2.7-yubikey-neo-manager-1.4.0/bin/.neoman-wrapped", line 6, in <module>
    from neoman.__main__ import main
  File "/nix/store/3viwpjs3i7w7f81pqf9haxxhyi2bbar2-python2.7-yubikey-neo-manager-1.4.0/lib/python2.7/site-packages/neoman/__main__.py", line 31, in <module>
    import neoman.qt_resources
  File "/nix/store/3viwpjs3i7w7f81pqf9haxxhyi2bbar2-python2.7-yubikey-neo-manager-1.4.0/lib/python2.7/site-packages/neoman/qt_resources.py", line 10, in <module>
    from PySide import QtCore
ImportError: libpyside-python2.7.so.1.2: cannot open shared object file: No such file or directory

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

No real update since 2016 and broken which means it should be good to drop.


[SPARK-33029][CORE][WEBUI][3.0] Fix the UI executor page incorrectly marking the driver as blacklisted

This is a backport of #30954
What changes were proposed in this pull request?
Filter out the driver entity when updating the exclusion status of live executors(including the driver), so the driver won't be marked as blacklisted in the UI even if the node that hosts the driver has been marked as blacklisted.
Why are the changes needed?
Before this change, if we run spark with the standalone mode and with spark.blacklist.enabled=true. The driver will be marked as blacklisted when the host that hosts that driver has been marked as blacklisted. While it's incorrect because the exclude list feature will exclude executors only and the driver is still active.

After the fix, the driver won't be marked as blacklisted.

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual test. Reopen the UI and see the driver is no longer marked as blacklisted.

Cc @dongjoon-hyun

Cc @dongjoon-hyun

Test build #133710 has started for PR 31057 at commit c49ca50.

Test build #133710 has started for PR 31057 at commit c49ca50.

Thank you, @baohe-zhang .

Thank you, @baohe-zhang .

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38298/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38298/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38298/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38298/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38298/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38298/

Test build #133710 has finished for PR 31057 at commit c49ca50.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #133710 has finished for PR 31057 at commit c49ca50.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged to branch-3.0.

Merged to branch-3.0.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133710/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/133710/