text:
textFontColor token from text button is affecting active state of secondary button

When a color value is assigned to textFontColor token of the button, this same value is taken by the secondary button to use it in the font color of the active state.
In the default theme, this issues is not perceived since both modes are using the same color.
To reproduce this wrong behavior, just pick a noticeable color for the textFontColor token and click on a secondary button, you will see how this secondary font color is affected by the color picked for the textFontColor, which shouldn't be related.
Screenshot example

This bug is solved in release 1.2.1.

authors: aalbuerne marcialfps

repo: dxc-technology/halstack-react


text:
Problem with Chinese song title & please add support for NetEase Music

Description
When I'm trying to add support for the , I found this line in source code:
2481 [[ "$song" != *[a-z]* ]] && { unset -v song; return; }
So some song title that only contain Chinese characters won't show.
As the matter of the support for NetEase Music, it got MPRIS implementation, so you can just add netease-cloud-music in to the players list. Works fine.
Thank you for creating this masterpiece, and sorry for my bad english.

Does this work?
    [[ "$song" != *[[:alpha:]]* ]] && { unset -v song; return; }

That's not the only cause. Check the code starting from the 2381 line. You will see netease-cloud-music is not supported. You may write your own, but I am not sure if any one is still watching this repo since my pull request was opened nearly half a month ago and nobody even replied.
For the regex thing, we can work this around by saying [\u4e00-\u9fa5], but how about Japanese Arabic etc. I think it's better to know the intention of that line first, instead of directly building up more conditions.

@xudong-yang I just add netease-cloud-music to the player list,and comment out that line,and it's working.

Yeah man, I really don't know what is that line for.

I think it's better to know the intention of that line first

It was originally added as
[[ "$(trim "$song")" = "-" ]] && unset -v song

in 8e32dc78 to avoid printing a - when the song info (artist and title) was empty.
(Album was not supported at that time)
And changed to it's current form in 3ece779d.

I am not sure if any one is still watching this repo since my pull request was opened nearly half a month ago and nobody even replied

@xudong-yang have you seen https://github.com/dylanaraps/neofetch/pull/1118#issuecomment-447560872 ?

I am not sure if any one is still watching this repo since my pull request was opened nearly half a month ago and nobody even replied

@xudong-yang have you seen #1118 (comment) ?

errrrr... I didn't see that. I read that thread when I opened mine, and then I am not following it. That makes sense. I have edited my comment above. Thank you for pointing that out

source: gharchive/issue

authors: 4679 arisinfenix xudong-yang

repo: dylanaraps/neofetch

license: mit

license_type: permissive

license_source: bigquery


text:
Disable GPU Brand not working

Description
I expected that NVIDIA would be removed if I switched that setting to off, but it wasn't.
Neofetch version
2.0.1
Screenshot
gpu_brand="on"
GPU: NVIDIA GeForce GTX 750 Ti

gpu_brand="off"
GPU: NVIDIA GeForce GTX 750 Ti

Verbose log
gist/07bb652a6366e6acff98daeb828be886

I can reproduce this, working on a fix now.

Fixed.
It looks like I'm going to have to do another minor release tomorrow.

authors: Brottweiler dylanaraps


text:
Screen resolution broken on macOS

Description
Screen resolution is not displaying at all on macOS.
The system_profiler method does work, although it seems to slow down the entire script. The refresh rate isn't displaying, however (and it is definitely turned on in my config file).
"Mac OS X")
    # if type -p screenresolution >/dev/null; then
    #     resolution="$(screenresolution get | awk '/Display/ {printf $6 "Hz, "}')"
    #     resolution="${resolution//x??@/ @ }"
    #
    # else
        resolution="$(system_profiler SPDisplaysDataType | awk '/Resolution:/ {printf $2"x"$4" @ "$6"Hz, "}')"
    fi

    scale_factor="$(/usr/libexec/PlistBuddy -c "Print DisplayAnyUserSets:0:0:Resolution" /Library/Preferences/com.apple.windowserver.plist)"

    # If no refresh rate is empty.
    [[ "$resolution" == *"@ Hz"* ]] && \
        resolution="${resolution//@ Hz}"

    ((${scale_factor%.*} == 2)) && \
        resolution="${resolution// @/@2x @}"

    if [[ "$refresh_rate" == "off" ]]; then
        resolution="${resolution// @ [0-9][0-9]Hz}"
        resolution="${resolution// @ [0-9][0-9][0-9]Hz}"
    fi

    [[ "$resolution" == *"0Hz"* ]] && \
        resolution="${resolution// @ 0Hz}"
;;

We added screenresolution as a dependency on macOS because it's way faster than system_profiler and it shows refresh rates. (system_profiler doesn't iirc)
What's the output of this command?
screenresolution get

2017-02-25 17:31:46.140 screenresolution[5810:22510] starting screenresolution argv=screenresolution get
2017-02-25 17:31:46.154 screenresolution[5810:22510] Display 0: 1280x800x32@0

It looks to me like screenresolution is working, or am I wrong?
@iandrewt, can you take a look at this?

Yeah, I do have it installed, it's just not working with Neofetch for some reason.

Try this in the terminal:
screenresolution get | awk '/Display/ {printf $6 "Hz, "}'

Same output as above.
2017-02-25 17:36:45.162 screenresolution[7810:29735] starting screenresolution argv=screenresolution get
2017-02-25 17:36:45.168 screenresolution[7810:29735] Display 0: 1280x800x32@0

I've got no idea how to fix this and no macOS machine to test on so we'll have to wait for @iandrewt.

It seems that screenresolution is now writing the results to stderr instead of stdout, as the command expects.
So a simple fix would be changing the command to:
screenresolution get 2>&1 | awk '/Display/ {printf $6 "Hz, "}'

@eliezio That seems to be the problem. Care to make the PR?

It might be worth redirecting stderr to stdout so that the fix also works
with older versions of screenresolution
On Sun, 5 Mar 2017 at 9:22 am, Jorge Gonzalez notifications@github.com
wrote:

@eliezio https://github.com/eliezio That seems to be the problem. Care
to make the PR?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dylanaraps/neofetch/issues/662#issuecomment-284192323,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGfAa7wA4MlY5vUmt0JJn5G8HoOwFv5Mks5rifIagaJpZM4MMB1m
.

This issue should be fixed by now. Feel free to reopen if this issue somehow still exists.

Currently Resolution: 1280x800@2x is what is being displayed for me. I have refresh_rate="on" in my config, but it's not displaying.
Also, would there be any benefit of using
{
    DisplayAnyUserSets =     (
                (
                        {
                Active = 1;
                Depth = 4;
                DisplayID = 69731840;
                DisplayProductID = 40984;
                DisplaySerialNumber = 0;
                DisplayVendorID = 1552;
                ForceDeepMode = 0;
                Height = 800;
                IODisplayLocation = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0";
                IOFlags = 33554439;
                LimitsHeight = 1600;
                LimitsOriginX = 0;
                LimitsOriginY = 0;
                LimitsWidth = 2560;
                MirrorID = 0;
                Mirrored = 0;
                Mode =                 {
                    BitsPerPixel = 32;
                    BitsPerSample = 8;
                    DepthFormat = 4;
                    Height = 800;
                    IODisplayModeID = "-2147479552";
                    IOFlags = 33554439;
                    Mode = 0;
                    PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                    RefreshRate = 0;
                    SamplesPerPixel = 3;
                    UsableForDesktopGUI = 1;
                    Width = 1280;
                    kCGDisplayBytesPerRow = 10240;
                    kCGDisplayHorizontalResolution = 227;
                    kCGDisplayModeIsInterlaced = 0;
                    kCGDisplayModeIsSafeForHardware = 1;
                    kCGDisplayModeIsStretched = 0;
                    kCGDisplayModeIsTelevisionOutput = 0;
                    kCGDisplayModeIsUnavailable = 0;
                    kCGDisplayModeSuitableForUI = 1;
                    kCGDisplayPixelsHigh = 1600;
                    kCGDisplayPixelsWide = 2560;
                    kCGDisplayResolution = 2;
                    kCGDisplayVerticalResolution = 227;
                };
                OriginX = 0;
                OriginY = 0;
                PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                Resolution = 2;
                Unit = 0;
                UnmirroredHeight = 800;
                UnmirroredLimitsHeight = 1600;
                UnmirroredLimitsOriginX = 0;
                UnmirroredLimitsOriginY = 0;
                UnmirroredLimitsWidth = 2560;
                UnmirroredMode =                 {
                    BitsPerPixel = 32;
                    BitsPerSample = 8;
                    DepthFormat = 4;
                    Height = 800;
                    IODisplayModeID = "-2147479552";
                    IOFlags = 33554439;
                    Mode = 0;
                    PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                    RefreshRate = 0;
                    SamplesPerPixel = 3;
                    UsableForDesktopGUI = 1;
                    Width = 1280;
                    kCGDisplayBytesPerRow = 10240;
                    kCGDisplayHorizontalResolution = 227;
                    kCGDisplayModeIsInterlaced = 0;
                    kCGDisplayModeIsSafeForHardware = 1;
                    kCGDisplayModeIsStretched = 0;
                    kCGDisplayModeIsTelevisionOutput = 0;
                    kCGDisplayModeIsUnavailable = 0;
                    kCGDisplayModeSuitableForUI = 1;
                    kCGDisplayPixelsHigh = 1600;
                    kCGDisplayPixelsWide = 2560;
                    kCGDisplayResolution = 2;
                    kCGDisplayVerticalResolution = 227;
                };
                UnmirroredOriginX = 0;
                UnmirroredOriginY = 0;
                UnmirroredResolution = 2;
                UnmirroredWidth = 1280;
                Width = 1280;
            }
        ),
                (
                        {
                Active = 1;
                Depth = 4;
                DisplayID = 69731840;
                DisplayProductID = 40984;
                DisplaySerialNumber = 0;
                DisplayVendorID = 1552;
                ForceDeepMode = 0;
                Height = 800;
                IODisplayLocation = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0";
                IOFlags = 33554439;
                LimitsHeight = 1600;
                LimitsOriginX = 0;
                LimitsOriginY = 0;
                LimitsWidth = 2560;
                MirrorID = 0;
                Mirrored = 0;
                Mode =                 {
                    BitsPerPixel = 32;
                    BitsPerSample = 8;
                    DepthFormat = 4;
                    Height = 800;
                    IODisplayModeID = "-2147471360";
                    IOFlags = 33554439;
                    Mode = 0;
                    PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                    RefreshRate = 0;
                    SamplesPerPixel = 3;
                    UsableForDesktopGUI = 1;
                    Width = 1280;
                    kCGDisplayBytesPerRow = 10240;
                    kCGDisplayHorizontalResolution = 227;
                    kCGDisplayModeIsInterlaced = 0;
                    kCGDisplayModeIsSafeForHardware = 1;
                    kCGDisplayModeIsStretched = 0;
                    kCGDisplayModeIsTelevisionOutput = 0;
                    kCGDisplayModeIsUnavailable = 0;
                    kCGDisplayModeSuitableForUI = 1;
                    kCGDisplayPixelsHigh = 1600;
                    kCGDisplayPixelsWide = 2560;
                    kCGDisplayResolution = 2;
                    kCGDisplayVerticalResolution = 227;
                };
                OriginX = 0;
                OriginY = 0;
                PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                Resolution = 2;
                Unit = 0;
                UnmirroredHeight = 800;
                UnmirroredLimitsHeight = 1600;
                UnmirroredLimitsOriginX = 0;
                UnmirroredLimitsOriginY = 0;
                UnmirroredLimitsWidth = 2560;
                UnmirroredMode =                 {
                    BitsPerPixel = 32;
                    BitsPerSample = 8;
                    DepthFormat = 4;
                    Height = 800;
                    IODisplayModeID = "-2147471360";
                    IOFlags = 33554439;
                    Mode = 0;
                    PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                    RefreshRate = 0;
                    SamplesPerPixel = 3;
                    UsableForDesktopGUI = 1;
                    Width = 1280;
                    kCGDisplayBytesPerRow = 10240;
                    kCGDisplayHorizontalResolution = 227;
                    kCGDisplayModeIsInterlaced = 0;
                    kCGDisplayModeIsSafeForHardware = 1;
                    kCGDisplayModeIsStretched = 0;
                    kCGDisplayModeIsTelevisionOutput = 0;
                    kCGDisplayModeIsUnavailable = 0;
                    kCGDisplayModeSuitableForUI = 1;
                    kCGDisplayPixelsHigh = 1600;
                    kCGDisplayPixelsWide = 2560;
                    kCGDisplayResolution = 2;
                    kCGDisplayVerticalResolution = 227;
                };
                UnmirroredOriginX = 0;
                UnmirroredOriginY = 0;
                UnmirroredResolution = 2;
                UnmirroredWidth = 1280;
                Width = 1280;
            },
                        {
                Active = 1;
                Depth = 4;
                DisplayID = 441053378;
                DisplayProductID = 10179;
                DisplaySerialNumber = 0;
                DisplayVendorID = 1129;
                ForceDeepMode = 0;
                Height = 1080;
                IODisplayLocation = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@2";
                IOFlags = 34603015;
                LimitsHeight = 1080;
                LimitsOriginX = 2560;
                LimitsOriginY = 0;
                LimitsWidth = 1920;
                MirrorID = 0;
                Mirrored = 0;
                Mode =                 {
                    BitsPerPixel = 32;
                    BitsPerSample = 8;
                    DepthFormat = 4;
                    Height = 1080;
                    IODisplayModeID = "-2147471360";
                    IOFlags = 34603015;
                    Mode = 0;
                    PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                    RefreshRate = 60;
                    SamplesPerPixel = 3;
                    UsableForDesktopGUI = 1;
                    Width = 1920;
                    kCGDisplayBytesPerRow = 7680;
                    kCGDisplayHorizontalResolution = 82;
                    kCGDisplayModeIsInterlaced = 0;
                    kCGDisplayModeIsSafeForHardware = 1;
                    kCGDisplayModeIsStretched = 0;
                    kCGDisplayModeIsTelevisionOutput = 1;
                    kCGDisplayModeIsUnavailable = 0;
                    kCGDisplayModeSuitableForUI = 1;
                    kCGDisplayPixelsHigh = 1080;
                    kCGDisplayPixelsWide = 1920;
                    kCGDisplayResolution = 1;
                    kCGDisplayVerticalResolution = 82;
                };
                OriginX = 1280;
                OriginY = 0;
                PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                "RefreshRate16.16" = 3932160;
                Resolution = 1;
                Unit = 2;
                UnmirroredHeight = 1080;
                UnmirroredLimitsHeight = 1080;
                UnmirroredLimitsOriginX = 2560;
                UnmirroredLimitsOriginY = 0;
                UnmirroredLimitsWidth = 1920;
                UnmirroredMode =                 {
                    BitsPerPixel = 32;
                    BitsPerSample = 8;
                    DepthFormat = 4;
                    Height = 1080;
                    IODisplayModeID = "-2147471360";
                    IOFlags = 34603015;
                    Mode = 0;
                    PixelEncoding = "--------RRRRRRRRGGGGGGGGBBBBBBBB";
                    RefreshRate = 60;
                    SamplesPerPixel = 3;
                    UsableForDesktopGUI = 1;
                    Width = 1920;
                    kCGDisplayBytesPerRow = 7680;
                    kCGDisplayHorizontalResolution = 82;
                    kCGDisplayModeIsInterlaced = 0;
                    kCGDisplayModeIsSafeForHardware = 1;
                    kCGDisplayModeIsStretched = 0;
                    kCGDisplayModeIsTelevisionOutput = 1;
                    kCGDisplayModeIsUnavailable = 0;
                    kCGDisplayModeSuitableForUI = 1;
                    kCGDisplayPixelsHigh = 1080;
                    kCGDisplayPixelsWide = 1920;
                    kCGDisplayResolution = 1;
                    kCGDisplayVerticalResolution = 82;
                };
                UnmirroredOriginX = 1280;
                UnmirroredOriginY = 0;
                UnmirroredResolution = 1;
                UnmirroredWidth = 1920;
                Width = 1920;
            }
        )
    );
    DisplayLayoutToRight = 1;
    DisplayMainOnInternal = 1;
    MTAccountBase = 309;
    MTAccountDelta = 220;
}

Neofetch hides the refresh rate if it's blank or appears as 0HZ in the screenresolution output.
What's the full output of:

screenresolution get
screenresolution get | awk '/Display/ {printf $6 "Hz, "}'

Also about that file, I think it'll be too difficult parse. I could be wrong though.

2017-03-20 17:56:09.860 screenresolution[17047:48227] starting screenresolution argv=screenresolution get
2017-03-20 17:56:09.866 screenresolution[17047:48227] Display 0: 1280x800x32@0

2017-03-20 17:56:30.138 screenresolution[17285:49209] starting screenresolution argv=screenresolution get
2017-03-20 17:56:30.144 screenresolution[17285:49209] Display 0: 1280x800x32@0

Yes you are correct, it's because it appears as @0.
Do ignore the file I pasted in my previous comment - I forgot to edit it!

authors: dylanaraps eliezio jorgegonzalez konimex


text:
Alacritty doesn't seem to be working with wal

I installed Void Linux today and finally managed to get pywal working (it only has py3.5 so I compiled 3.6.1 with pyenv) and since it doesn't have Termite (my go-to terminal) in it's repos I decided to try Alacritty (it's supposed to be fast). So turns out it's dash-fast, as in "lacks too many useful features" (probably because it's still in alpha). The printf "%b" "\033]11;#ff0000\007" does nothing so I guess you should add it to the list. I tried to make it work with wal by having a config.yml that contains non-color options and an auto-generated colors.yml that has colors (used termcolors to convert to Alacritty's format), what I did was add this function:
function fix_alacritty() {
	local dir="${HOME}/.config/alacritty"
	rm "${dir}/alacritty.yml"
	cat "${dir}/config.yml" "${dir}/colors.yml" >> "${dir}/alacritty.yml"
}

And call it in the script that gets executed after wal, turns out Alacritty needs everything to be in specific positions for the thing to work (it is possible with some mad regex-foo or yaml parsing, both of which I'm no good at and not going to try doing since the benefits aren't that good, not being able to change colors on the fly is a bummer)
So I guess it's not really an issue with wal but I'm just letting you know

Thanks for doing all of this testing!
We could try and open an issue on Alacritty's bug tracker, I did a quick search and couldn't find anything.

Issue opened on Alacritty's repo: https://github.com/jwilm/alacritty/issues/656

Alacritty is now supported! :D

So, how would I add wal to alacritty? It does work, but I need to re-run wal every-time I open a new alacritty instance.

You should be able to just add wal (and whatever parameters you pass to it) to your shell's rc file, for Bash it's ~/.bashrc.

So what you're telling me is that I should just add the wal command to my shell rc file?
(e.g. wal -i /path/to/wallpaper in .zshrc)

Something like that. Maybe only do it when running in a graphical session, I haven't used wal in a long time so I can't remember what I used to do.

It worked! Thanks.

[MacOS] I've recently installed alacritty, and pywal doesn't seem to be working! Am I missing something?
I've got the command (cat ~/.cache/wal/sequences &) in my .zshrc file
Whenever I try to wal -i /path/to/wallpaper it just does nothing.

I have no way of debugging macOS. Alacrity works just fine on my Linux install.
Are you using the latest version of Alacritty?

Just reinstalled Alacritty to make sure I have the latest version but the same problem still arises. Whenever I use wal -i it reads the wallpaper but the colors never change. Is there a log file or something alike that I can check to know more details about the problem?

What version of alacritty are you using?
On Sun, 11 Mar 2018 at 9:45 am, Francisco Santos notifications@github.com
wrote:

Just reinstalled Alacritty to make sure I have the latest version but the
same problem still arises. Whenever I use wal -i it reads the wallpaper
but the colors never change. Is there a log file or something alike that I
can check to know more details about the problem?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/dylanaraps/pywal/issues/37#issuecomment-372073242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGfAa7TafmYtGebnOH2uhpknoLqOFNJHks5tdFdzgaJpZM4ORbp9
.

I'm using the latest on their repo, can't really give you a number as I don't know any command the shows me the Alacritty version nor have they got any releases or tags on the repo.

This is still a problem with a fairly recent (march 01) version of Alacritty on macOS.
Oddly enough printf "%b" "\033]11;#ff0000\007" does change the background to red, but cat sequences does nothing. Running wal -i <file> changes the colors of iTerm2 windows but not Alacritty.

It might be worth opening a bug on their tracker. Alacritty works fine on Linux.

I just wrote a workaround that may help Mac users who want wal colors in Alacritty: https://github.com/egeesin/alacritty-color-export

@egeesin this is confirmed working for me on MacOS 10.15.2, alacritty 0.3.3

@dylanaraps if you don't mind, I'd like to add this to the Wiki as a section under the terminal customization, something like "Alacritty on MacOS".

Go ahead! :+1:

Done 😃

authors: Amar1729 Cakedy FranciscoJRSantos dylanaraps egeesin omrisim210 rugglcon

repo: dylanaraps/pywal


text:
please publish the latest version to npm

@dylanb thanks for accepting my contribution, Can you publish the latest changes to npm?

I will be able to publish on Sunday because I am travelling for work and do not have my personal laptop with me

done

authors: Jhorlin dylanb

repo: dylanb/gulp-coverage


text:
[Snyk] Security upgrade @backstage/theme from 0.0.0-use.local to 0.1.1

Snyk has created this PR to fix 4 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

plugins/todo/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860
  112

Cross-site Scripting SNYK-JS-EXPRESS-7926867
  80

Cross-site Scripting SNYK-JS-SEND-7926862
  80

Cross-site Scripting SNYK-JS-SERVESTATIC-7926865
  80

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)

source: gharchive/pull-request

repo: dylansnyk/backstage

license_source: github-api


text:
Setup.py Fix

Bug fix for broken pip.req lib calls

:+1:

repo: dyninc/dyn-python


text:
-[UITableView setEmptyDataSetSource:]: unrecognized selector sent to instance

I am getting crash.
-[UITableView setEmptyDataSetSource:]: unrecognized selector sent to instance
Added by carthage.

Do you have solved this problems?

https://github.com/dzenbot/DZNEmptyDataSet/issues/325

repo: dzenbot/DZNEmptyDataSet


text:
Adaption off Learning Unit Endpoint to requirements from 25.09.23

1 Iteration done with Pull Request, will open new tickets for further changes

repo: e-Learning-by-SSE/nm-skill-service


text:
error after yarn dev

Hey guys,
first of all thank you for the work.
I´ve tried it out but i´m getting some errors after starting everything with yarn dev:
When i´m trying to login i´ll get the message: Failed to fetch
yarn run v1.22.19
$ npx concurrently -p none "next dev" "yarn start:api" "yarn start:playground"
$ cd api-service && QUART_APP=app:app PYTHONUNBUFFERED=1 poetry run quart --debug run --reload --port 49155
$ cd api-service/playground && yarn dev
$ concurrently "nodemon -q" "nodemon --config nodemon-tsoa.json "
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
info  - Loaded env from /home/debian-dev/e2b/e2b/.env
warn  - You have enabled experimental feature (swcPlugins) in next.config.js.
warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.

[1] [nodemon] 2.0.21
[1] [nodemon] to restart at any time, enter `rs`
[1] [nodemon] watching path(s): src/**/*Controller.ts
[1] [nodemon] watching extensions: ts
[1] [nodemon] starting `tsoa spec-and-routes`
Traceback (most recent call last):
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/bin/quart", line 8, in <module>
    sys.exit(main())
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/quart/cli.py", line 771, in main
    cli.main()
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/click/decorators.py", line 84, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/quart/cli.py", line 656, in run_command
    app = info.load_app()
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/quart/cli.py", line 245, in load_app
    app = locate_app(import_name, name)
  File "/root/.cache/pypoetry/virtualenvs/codegen-gAr6YSV0-py3.9/lib/python3.9/site-packages/quart/cli.py", line 175, in locate_app
    module = import_module(module_name)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/home/debian-dev/e2b/e2b/api-service/app.py", line 11, in <module>
    from codegen import Codegen
  File "/home/debian-dev/e2b/e2b/api-service/codegen/__init__.py", line 1, in <module>
    from .codegen import Codegen
  File "/home/debian-dev/e2b/e2b/api-service/codegen/codegen.py", line 19, in <module>
    from session.env import EnvVar
  File "/home/debian-dev/e2b/e2b/api-service/session/__init__.py", line 1, in <module>
    from .playground.nodejs import NodeJSPlayground
  File "/home/debian-dev/e2b/e2b/api-service/session/playground/__init__.py", line 1, in <module>
    from .base import Playground
  File "/home/debian-dev/e2b/e2b/api-service/session/playground/base.py", line 18, in <module>
    class Playground(Session):
  File "/home/debian-dev/e2b/e2b/api-service/session/playground/base.py", line 47, in Playground
    timeout: float | None = None,
TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn start:api exited with code 1
[0] Listening at http://localhost:49160
event - compiled client and server successfully in 5.1s (1189 modules)
[1] [nodemon] clean exit - waiting for changes before restart
wait  - compiling /_error (client and server)...
event - compiled client and server successfully in 993 ms (1190 modules)
warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
wait  - compiling /sign (client and server)...
event - compiled client and server successfully in 1443 ms (1199 modules)
warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
[0] Listening at http://localhost:49160
wait  - compiling /[projectID] (client and server)...
event - compiled client and server successfully in 2.4s (1765 modules)

Hi, thanks for opening an issue!
There seems to be an error when starting Python API - can you please check your Python version? I think you are not running python 3.10 and the error is described here https://github.com/tiangolo/typer/issues/371.
Also, if you are getting failed to fetch error during the login, there may be some problem with the local Supabase - was that started without problems?

thanks for your answer.
so my python version is Python 3.11.1
the Supabase startet without problems.
i´ve just updated python and restarted the Supabase but still the same error. Maybe reinstall everything?

one step further ;-)
soo it was the root/.cache folder i had to delete the files in there.
now i still get one error and still not able to login with admin@admin.com

I think that now you are missing the deleted deps :D (quart)
Somehow the Python virtualenv is creating env with Python 3.9

I tried it locally and the following steps should fix it:

Go to api-service/ and run poetry env use python3.10 command
Go to the top level directory and run yarn install:api-service
Try yarn dev again.

if i go to api-service and type poetry env use python3.11.1 (my installed version)  i´ll get No such file or directory
same with 3.10 of course ;-)
if i proceed with yarn install:api-service it installs everything based on my old python and i´ll get the same error as on post one. so i have to delete the root/.cache folder again and type yarn dev.
but the one quart error pops up again

You should be able to switch the poetry python env with the command specifying the full path to your Python:
poetry env use /full/path/to/python (poetry env use $(which python) could work if your python is accessible as python from terminal.)

yap perfect thank you. The only part i´m missing right now is the chatgpt input field like you´ve posted a few days ago...

Do you mean the input field for generating UIs?

No, this is actually our fault. The UI generation is not finished and accessible right now - but we will be adding it here soon :D
You can join the Discord (https://discord.gg/U7KEcGErtQ) - we will be announcing the release there too.

ok thanks! 👌

authors: BangerTech ValentaTomas


text:
SDSTOR-11619 Implement HeapChunkSelector

this is the initial version of HeapChunkSelector. it is mainly for review the logic and comments, and will be refactored or refined after deviceV2 branch of HomeStore is merged

Codecov Report
Patch and project coverage have no change.

Comparison is base (5b7a09a) 84.15% compared to head (8489142) 84.15%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #30   +/-   ##
=======================================
  Coverage   84.15%   84.15%
=======================================
  Files          14       14
  Lines         183      183
  Branches       21       21
=======================================
  Hits          154      154
  Misses         16       16
  Partials       13       13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

implemented in homestore

compiling error is caused by operator== and get_chunk_id() in VChunk.h , which will be added to homestore soon

compiling will fail until this PR in merged in homestore

Need code coverage: https://app.codecov.io/gh/eBay/HomeObject/tree/HeapChunkSelector/src%2Flib%2Fhomestore
Otherwise looks good!

@szmyd i do not link libhomeobject_homestore.a when writing UT for HeapChunkSelector, but the UT covers all the functions of HeapChunkselector, not sure if this will be captured by Codecov and update the code coverage.
let me explaint this in more detail. if we want to test the correctness of HeapChunkSelector, we need to check whether the returned chunk is the one we expected. but we know nothing detail of chunk and it is only known by homstore, we just only have a raw declaration in homeobject, and we can not derive or mock it.
so i write a chunk implementation in the test,  and if we link libhomeobject_homestore.a which will link libhomestore.a, there will be a conflict that two defination of homestore::chunk exist. this is why i do not link libhomeobject_homestore.a.

error mesage is
/home/runner/work/HomeObject/HomeObject/src/lib/homestore/homeobject.cpp:46:99: error: ‘homestore::hs_input_params’ has no non-static data member named ‘services’    46 |         hs_input_params{.devices = device_info, .app_mem_size = app_mem_size, .services = services},
seems the build error is not caused by my code, i build it successfully in my local environment.

error mesage is
/home/runner/work/HomeObject/HomeObject/src/lib/homestore/homeobject.cpp:46:99: error: ‘homestore::hs_input_params’ has no non-static data member named ‘services’ 46 | hs_input_params{.devices = device_info, .app_mem_size = app_mem_size, .services = services},
seems the build error is not caused by my code, i build it successfully in my local environment.

I think the error comes from the latest interface changes in HS, have you updated HS in your local env to the latest?

@zichanglai  the error is caused by the upate of Homestore.
if I update to the latest homestore , there will be a test failure cased by ShardManagerTest.
if i do not update, it will fail the building here.

so will try to address those problem

authors: JacksonYao287 codecov-commenter szmyd zichanglai

repo: eBay/HomeObject


text:
Performance improvements [6951]

Improve sending piggyback heartbeat:

[x] 1.9.x #887
[x] master #888

Improve sending GAP:

[x] 1.9.x #889
[x] master #890

Improve ReaderHistory sorting:

[x] 1.9.x #894
[x] master #895

Improve in consecutive calls to History::get_change:

[x] 1.9.x #896
[x] master #897

Created PR #905 with all the changes applied to 1.9.x

Changes have been applied to 1.9.x and master. Closing this meta-ticket.

authors: MiguelCompany richiware

repo: eProsima/Fast-RTPS


text:
Use correct headers for FreeRTOS

Fixes https://github.com/eProsima/Micro-XRCE-DDS-Client/issues/235

Build status:

Linux
Windows

@Acuadros95 related to your problem yesterday

authors: bjv-capra pablogs9 richiprosima

repo: eProsima/Micro-XRCE-DDS-Client


text:
Re-implement list_dir

Closes #321

FAILED tests/test_can_read_old.py::test_icechunk_can_read_old_repo - AssertionError: assert ['c', 'zarr.json'] == ['zarr.json']

  At index 0 diff: 'c' != 'zarr.json'
  Left contains one more item: 'zarr.json'

  Full diff:
    [
  +     'c',
        'zarr.json',
    ]

I don't understand this, there is a manifest but no chunks were ever written?

repo: earth-mover/icechunk


text:
See the Changes in the DCP/Archives after updating an existing project

As a wrangler I want to "Confirm and See the Changes in the DCP/Archives" so that I can correct mistakes with (meta)data or add (meta)data to an existing project that is in the DCP/Archives.

this is not a viable story and I think is misrepresented, so closing

authors: clairerye ofanobilbao

repo: ebi-ait/dcp-ingest-central


text:
Errors in structures of isonocardicin A compounds

Hi Gareth and Adnan,
I have realised that the structures for the isonocardicin A compounds (CHEBI:16483, CHEBI:57788 and CHEBI:77633) are wrong concerning the stereoconfiguration of C-9' and C-5. The correct structure can be found in pmid:15252031 . You can also compare with CHEBI:81022,  isonocardicin C.
I have attached the corrected structures.
Please also add a cross reference from CHEBI:57788 to MetaCyc ISONOCARDICIN-A

I just tried to attach the new structures, but I don't think it worked.
I will send them to you in a mail.
Cheers,
Kristian

Now done.
Best Regards,
Adnan

repo: ebi-chebi/ChEBI


text:
Add support for custom vendor.js paths

Adds support for custom vendor.js output paths specified in ember-cli-build.js (outputPaths). Fixes ebryn/ember-component-css#159

New beta version fixes this, my bad for not checking. Disregard!

repo: ebryn/ember-component-css


text:
🐛 Bug ➾ The compile and Originate commands are failing when invokded from command pallet

🆘 What happened?
The CLI has change the implementation of these commands to require the file name. Previously it was optional.
🪵 Relevant log output
No response
🐘 How impactful is this bug?
No response
⏱ Prevalance
No response
💻 Operating System
No response
🕸 System Architecture
No response
🌮 Taqueria Version
No response
🌿 Node.js Version
No response
☎ Contact Details
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Is this not resolved with your new PR @AlirezaHaghshenas ?

This should have been closed automatically

repo: ecadlabs/taqueria


text:
mini.indentscope: Add excluded_filetypes

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.indentscope
Description
An option to disable indentscope on certain filetypes where indentscope is not useful like lazy,mason,filetrees etc.

Hi!
This is a duplicate of #167, #85, #52, and somewhat #423.
At the moment I plan to support disabling only through {g,b}:mini*_disable. To make it easier for users, there is a section in documentation with common situations.

authors: echasnovski name-tar-xz

license: MIT


text:
zoom puts people in waiting room

Setting up the Server-to-Server Oauth was working about a week ago, now when the meeting is created, people are thrown in a waiting room and it won't start.
I have reached out to Zoom but haven't heard anything. My first assumption was something in the API changed?
We have default zoom waiting rooms off, and allow people to join meetings without the host.

I was able to reproduce this. I only have a user account, not a paid account, so I can't troubleshoot further. I was required to change these settings before I got it to work:

This could be because the zoom Api v1 seems to not support
 settings: {
          join_before_host: true,
          waiting_room: false,
        },

authors: LanceSandino echoboomer

repo: echoboomer/incident-bot


text:
Nullable Schema types

Hi, thanks for the awesome library!
I was testing structured outputs and found a limitation.
Because all fields must be required in the schema, OpenAI recommends making the type a nullable union if one wants an "optional" field.
{
    "name": "get_weather",
    "description": "Fetches the weather in the given location",
    "strict": true,
    "parameters": {
        "type": "object",
        "properties": {
            "location": {
                "type": "string",
                "description": "The location to get the weather for"
            },
            "unit": {
+               "type": ["string", "null"],
                "description": "The unit to return the temperature in",
                "enum": ["F", "C"]
            }
        },
        "additionalProperties": false,
        "required": [
            "location", "unit"
        ]
    }
}

As far as I understand, this is not possible with the current Schema objects, right? Would be nice if it could be added in the future. :)

Awesome, I dig this! I'll get to it soon!

I think this works! Let's just call it nullable rather than isNullable."

I think this works! Let's just call it nullable rather than isNullable."

Awesome! I should have a PR up shortly.

authors: cosmastech sixlive studnitz

repo: echolabsdev/prism


text:
Still relevant

Is it still relevant now that FastImage is compatible with EAS build and managed ?
(even though fast image precache is not working well)

I think it's still relevant. It's pure react-native implementation and no platform specific code in it. Very simple, light weight, still offers flexibility for loading indicator and cache expiration etc... So, yes -- it still holds it's value :)

But feel free to share your thoughts.

Yeah, it's pure JS that is true and nice.
I ended up here reading your article about https://www.echowaves.com/post/expo-filesystem-cachedirectory-has-to-be-cleaned
And browsing this library give me some nice advice for such a use case. For now, I was using fast-images but I'm looking for the caching mechanism because i Also need to cache video assets and this looks great.

authors: ScreamZ dmitryame

repo: echowaves/expo-cached-image


text:
Persistent ParticipantStore

Feature Request
Support for persistent ParticipantStore
Which Areas Would Be Affected?
Registration Service
Why Is the Feature Desired?
Currently the Registration Service only supports an in memory version of ParticipantStore. As a consequence, whenever it is restarted, all stored Participants are lost.
Solution Proposal
As done for most stores in https://github.com/eclipse-dataspaceconnector/DataSpaceConnector, two extensions will be provided:

one for SQL databases,
one for CosmosDB.

Type of Issue
New feature
Checklist

[ ] assigned appropriate label?
[x] Do NOT select a milestone or an assignee!

@wolf4ood @jimmarino  can we close this one ?
as both SQL and Cosmos implementations have now been completed.

Closing the issue as both PostgreSQL and CosmosDB stores have been implemented.


text:
feat: removes StatusChecker

What this PR changes/adds
removes StatusChecker
Why it does that
Removed from EDC core component
Linked Issue(s)
Closes #95

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

Comparison is base (9b1a838) 73.19% compared to head (b1cbe59) 78.53%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #96      +/-   ##
==========================================
+ Coverage   73.19%   78.53%   +5.34%
==========================================
  Files          20       19       -1
  Lines         485      452      -33
  Branches       17       13       -4
==========================================
  Hits          355      355
+ Misses        129       96      -33
  Partials        1        1

Files
Coverage Δ

...nector/provision/aws/s3/AwsProvisionExtension.java
0.00% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

repo: eclipse-edc/Technology-Aws


text:
optional acl_set_fd in linux

Hi roudi fails to start in wsl due to missing acl_set_fd support I belive. -Would you consider making the shared memory access control optional somehow ? -That would facilitate testing under wsl.
iceoryx_hoofs/source/posix_wrapper/access_control.cpp:72 { bool iox::posix::AccessController::writePermissionsToFile(const int32_t) const -> acl_set_fd }  :::  [ 95 ]  Operation not supported
Error: Could not set file ACL.
2022-02-28 17:00:46.455 [ Error ]: ICEORYX error! MEPOO__SEGMENT_COULD_NOT_APPLY_POSIX_RIGHTS_TO_SHARED_MEMORY
(commit: da2d4725c6aa5d6527d8c59c43e1f9a7fc2883cb)

Hi, thanks for the input, can you point me which WSL version you are using? A recent test on a WSL 2 Ubuntu 20.04 image with latest iceoryx master did not show any error.
Do you maybe use some special filesystem that does not support ACL? Maybe this discussion give a hint.

@dkroenke it's WSL 1  (which don't have full linux call compatibility, or implementation rather, unfortunately)

@niclar I see what I can do but this may take some time.
To solve this problem locally yourself you could try to copy the file iceoryx_hoofs/platform/win/include/iceoryx_hoofs/platform/acl.hpp to iceoryx_hoofs/platform/linux/include/iceoryx_hoofs/platform/acl.hpp .
In Windows we do not support ACLs at all and replaced the libacl implementation with a stub implementation. When you copy the windows acl.hpp file to linux then linux would as well use the stub implementation of windows. It is like turning of ACLs.

I have the same problem with m1 max macos + docker + ros2 rolling image.

Great @elfenpiff.
-I can confirm, the workaround works.

-Can it be a runtime option instead ?

@niclar Looking at the tickets this is currently not planned, but you are invited to make a proposal Pull-Request for this.

Thanks, it really helps!

authors: Zard-C dkroenke elfenpiff niclar xixioba

repo: eclipse-iceoryx/iceoryx


text:
iox-#1103 Add discovery monitoring examples

Signed-off-by: Matthias Killat matthias.killat@apex.ai
Pre-Review Checklist for the PR Author

[ ] Code follows the coding style of CONTRIBUTING.md
[ ] Tests follow the best practice for testing
[ ] Changelog updated in the unreleased section including API breaking changes
[ ] Branch follows the naming format (iox-#123-this-is-a-branch)
[ ] Commits messages are according to this guideline

[ ] Commit messages have the issue ID (iox-#123 commit text)
[ ] Commit messages are signed (git commit -s)
[ ] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[ ] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[ ] Relevant issues are linked
[ ] Add sensible notes for the reviewer
[ ] All checks have passed (except task-list-completed)
[ ] Assign PR to reviewer

Notes for Reviewer

Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior

[ ] Each unit test case has a unique UUID

[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes TBD

This is a proposal for a possible service discovery API usage with listener and waitset. The user can basically build her own discovery but there are certain limitations.
API comments and use case suggestions are welcome but it is too early for coding style remarks as it is WIP.

This example needs to be added to the Readme.

@elfenpiff Can be reviewed, readme will be written when the code is agreed upon.

Please check if we have to remove code examples for the removed findService method from the `iceoryx-v2-0-0.md as mentioned here.

@FerdinandSpitzschnueffler @dkroenke Ready for review


text:
[Model Update]: SingleLevelUsageAsBuilt 3.0.0

Update Reason
Based on continuous development of the Industry Core, the ability to run up the data chain for PartInstance twins was implemented so that the relationship described by the SingleLevelUsageAsPlanned model meets the requirements of the data chain template.
Relevant Standards
CX-0127 Industry Core: Part Instance
Example Data
{
  "catenaXId": "urn:uuid:055c1128-0375-47c8-98de-7cf802c3241d",
  "parentItems": [
    {
      "isOnlyPotentialParent": false,
      "parentCatenaXId": "urn:uuid:43364d8c-cf38-423c-b907-6e68e0f0fe2f",
      "quantity": {
        "itemUnit": "unit:piece",
        "quantityValue": 20
      },
      "createdOn": "2022-02-03T14:48:54.709Z",
      "businessPartner": "BPNL50096894aNXY",
      "lastModifiedOn": "2022-02-03T14:48:54.709Z"
    }
  ],
  "customers": [
    {
      "createdOn": "2022-02-03T14:48:54.709Z",
      "businessPartner": "BPNL50096894aNXY",
      "lastModifiedOn": "2022-02-03T14:48:54.709Z"
    }
  ]
}

MS1 Criteria

[ ] The model that should be updated exists
[ ] The referenced use case exists
[ ] The potential updates are discussed with all stakeholders
[ ] A decision on versioning was made in consensus with the affected parties according to the guidelines.
[ ] The potential update will be either

[ ] backward compatible or
[ ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

[ ] A modeling steward has been assigned

FYI @jacewski-bosch @BenediktMuellerIML

repo: eclipse-tractusx/sldt-semantic-models


text:
big error alerts are not fitting within the view port

currently when the error alert is too big, it is stretching outside the view port and adding scrollbar. The error message must be within the view port.

I'll take this.

repo: eclipse-xpanse/xpanse


text:
Remove method getMetricTypes

Method getMetricTypes returns the list of enum values. We do not need this.
We have the enum defined in the interface for this purpose and all clients must simply use it.

I'll do this.


text:
Allow pre preprocessing hooks to substitute for ops, adds onnx  global pooling averaging and max

What changes were proposed in this pull request?
Allow pre preprocessing hooks to substitute for ops, adds global pooling averaging and max
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
Quick checklist
The following checklist helps ensure your PR is complete:

[ X] Eclipse Contributor Agreement signed, and signed commits - see IP Requirements page for details
[ X] Reviewed the Contributing Guidelines and followed the steps within.
[ X] Created tests for any significant new code additions.
[ X] Relevant tests for your changes are passing.

@treo this one is also self contained, but depends on the changes here: https://github.com/eclipse/deeplearning4j/pull/9410


text:
Merge of Client and Observation registries

Because the observation lifecycle is tied to the client registration, it makes sense to have a common store.
This change is related to the race condition issues: #176 and #77

I'm working on it.
Very first stage available in the refactor_merge_store branch.

This is done (#210)

repo: eclipse/leshan


text:
Add a recovery test for the AfterLRA annotation

#164  added support for notifications that an LRA has finished. There are already two tests for this feature but these notifications should be guaranteed to be delivered in failure scenarios and we need a TCK test to verify that.

What do you mean by in failure scenarios, please? AfterLRA annotation JavaDoc says that implementation SHOULD retry if the response code is different from 200. @rdebusscher mentioned that we shouldn't be adding TCK for SHOULD statements.
However, I agree that we should test this and we should change the wording in every participant annotation to guarantee at least some minimal transactional guarantees. This is especially not good for @Compensate annotation because it's totally valid to write an implementation that will just log failures after the first call to @Compensate. So if any microservice enlisted in LRA is down, all LRAs will start failing until it's up again.

I mean any scenario where the listener does not respond with 200 to the AfterLRA notification.
It is not desirable to force implementations to retry forever. Saying something like "MUST retry at least 7 times" is arbitrary and therefore not useful.
So SHOULD allows the implementation to give up after a while. But to mitigate such a non-transactional outcome we do stipulate that if they do that then they MUST log a warning.

But can we then include TCK tests? I am asking because I want to do so for Compensate.

Maybe we can say it must retry once? I don't want the spec to be governed by the testing strategy but I think 1 is (maybe?) less arbitrary than 7?

@xstefank We already have tests for retrying compensate etc so I would +1 @tomjenkinson and go for "MUST retry at least once and log a warning if it gives up"

But if we could formalise the WARNING then we could continue to use SHOULD in preference to MUST which ideally I'd like to avoid.

I prefer "MUST retry at least once and log a warning if it gives up"

"retry at least once is still arbitrary", is there a way we can formalise the warning?

can't we say something like "MUST make reasonable effort to get a successful response"? I am aiming just on some minimal requirement (thus MUST) to write a TCK for this and Compensate.

can't we say something like "MUST make reasonable effort to get a successful response"? I am aiming just on some minimal requirement (thus MUST) to write a TCK for this and Compensate.

That won't help with a TCK test for Compensate.
PS Don't we already have a test that validates that Compenstate is repeatedly called in failure scenarios (I'd have to check but I am sure I wrote some)?

I think that "MUST make reasonable effort" is too vague and we couldn't code it in a TCK test?
I don't understand @mmusgrov 's comment about formalising the warning - please can you provide some wording to review?

I think that "MUST make reasonable effort" is too vague and we couldn't code it in a TCK test?
I don't understand @mmusgrov 's comment about formalising the warning - please can you provide some wording to review?

I was asking for input. Since the actual container used to execute our TCK will be different for each implementation we probably cannot access the container logs (which would contain the WARNING message).
We could require that each implementation makes the data available to the TCK (something that could be included with #175 )

However, I agree that we should test this and we should change the wording in every participant annotation to guarantee at least some minimal transactional guarantees. This is especially not good for @Compensate annotation because it's totally valid to write an implementation that will just log failures after the first call to @Compensate. So if any microservice enlisted in LRA is down, all LRAs will start failing until it's up again.

So are we ok with this as an acceptable implementation? We are developing distributed transactions in microservices so we must expect service and connection failures. Do we really want to not give any guarantees?

I don't think the discussion is about not retrying forever for compensate and complete? For AfterLRA I was all for making it non-durable like in JTA. I see no point in making any durability claims if we are just going to log a warning.

What about "MUST retry at least n times as defined by configuration parameter x.y.z"
So that we define a configuration parameter which defines how many times the implementation will retry and by setting this value to 1 in the TCK, we can effectively test it.

I like the concept from @rdebusscher  but I think something like "MUST retry until the LRA is requested to stop retrying" might be better. This could still be achieved by configuration but might be some other vendor specific API perhaps?
I think the client should be in control of the retry behaviour though (rather than the LRA vendor/host) because the client is going to expect the retry until the outcome is achieved and it is the client that would need to be notified if the AfterLRA could not be contacted - or maybe I am thinking about who the contract for the AfterLRA notification is with?

@tomjenkinson I agree, the client must be in control. But we need to standardize the way how this information is provided to the implementation for the TCK purposes.

The client could specify the retry policy using an annotation attribute of the LRA annotation.
The AfterLRA listener could do the same using an attribute of the AfterLRA annotation.

Would that cover also separate policies for Compensate, Complete, etc?

Please can someone clarify why the retry would be forever?

@tomjenkinson I don't understand. I think we are discussing including an attribute in the respective annotations that would define the number of retries. Let's say that we can add retry in the @LRA annotation that would define it for all participant methods and AfterLRA?

I meant fundamentally, I understand we are adding something because we don't want to retry forever but I lost the information about why we would ever retry forever anyway?

I think we can go with default no retries or some small reasonable number (1).

I think we should say "implementations MUST retry any callback API methods but vendors MAY provide further proprietary methods to resolve indoubt participant states and thereby prevent further retry calls"
PS I don't think we can mandate a logging methodology because certain implementations might not have a (for instance) file logging mechanism available

I like @tomjenkinson wording, we can go with this. But the configuration of max-retries and/or retry-interval is a separate question on top of that. We can take that in different issue if this one would be resolved with Tom's wording.

I like @tomjenkinson wording, we can go with this. But the configuration of max-retries and/or retry-interval is a separate question on top of that. We can take that in different issue if this one would be resolved with Tom's wording.

I think @tom_jenkinson_twitter 's sugestion (https://github.com/eclipse/microprofile-lra/issues/190#issuecomment-513796455) is that the TCK can rely on at least one retry.
Which would mean that our TCK participants would need to recover on the first retry
￼
BTW we only require this timeout behaviour to catch implementations that fail to finish an LRA. But we have the TCK property @ConfigProperty(name = "lra.tck.consistency.delay") for just this situation.
So is this a "non issue"?
￼
ie we go with Tom's text and make sure the TCK fails an implementation that does not recover on the first pass (which should be fine since we are in control of the participants).

ie we go with Tom's text and make sure the TCK fails an implementation that does not recover on the first pass (which should be fine since we are in control of the participants).

+1

@rdebusscher Do you (or someone else) want to raise a PR for this or do you want me to?

I have already something prepared for the Compensate case. I can put this preferably into one PR. Is there any other method that we want to test in TCK?

I have already something prepared for the Compensate case.
The AfterLRA case is for LRAs
The complete case is covered by the existing spec text:

Similarly if the resource cannot perform a completion activity immediately.
I can put this preferably into one PR.
One PR is prefererable
Is there any other method that we want to test in TCK?
Not that I am aware of

@mmusgrov thanks. The decision is then 2 TCK tests -- one for AfterLRA and one for Compensate with one participant failure.

@xstefank Have you started on this task yet. If not then I would like to create the two tests.
Remark: The test should also validate that it is possible to register for the notification both before and after the end phase is entered (we should probably be explicit in the spec that registering for notifications is allowed at any time that the implementation knows about the LRA - optionally even if the LRA has already ended).

yes, I have PoC already. I wanted to wait for triggerRecovery mechanism (which is now blocking development of these tests in Narayana). In case long delay solution is sufficient I can make a pr soon.

Okay no rush. So is that 2 tests for @AfterLRA and one for Compensate with one participant failure?

yes, for now, these two. We can add other scenarios later if needed.

authors: mmusgrov rdebusscher tomjenkinson xstefank

repo: eclipse/microprofile-lra


text:
SparqlBuilder to work with rdf4j model objects

Currently, the SparqlBuilder module has its own set of interfaces for RDF value objects: RdfResource, Iri, Prefix, etc. To facilitate better integration with the rest of the RDF4J framework we should make sure that the builder API (also) accepts RDF4J model objects, like org.eclipse.rdf4j.model.IRI etc.

Can this be done while maintaining the module's ability to be used independently?

Well it will need a maven dependency on rdf4j-model, but we can extend the API in such a way that you don't have to use rdf4j model objects if you don't want to, I think.

Well it will need a maven dependency on rdf4j-model, but we can extend the API in such a way that you don't have to use rdf4j model objects if you don't want to, I think.

Having to carry around a ValueFactory in RDF4J is quite a pain. The way the query builder code does it using static factory methods is much more convenient.

Having to carry around a ValueFactory in RDF4J is quite a pain. The way the query builder code does it using static factory methods is much more convenient.

This (a closed issue) isn't really the best place to be having a conversation about this, but if you have a specific use case in mind where some other pattern than a ValueFactory would be better, please open a feature request (or alternatively, send a message to the user forum). We are currently mapping out our plans for rdf4j 3.0, so this is an ideal time to come with proposals for improvements, even if they are not necessarily backward compatible.

@jeenbroekstra see #1325

authors: anqit jeenbroekstra reckart


text:
Add UI to change verification grid size

Add UI to change verification grid size
This pull request exposes a user interface to change the verification grid size after creation
Changes
Features

Adds a button to change the verification grid size

Bug Fixes

Fix a bug where increasing the grid size after initalization would not cause the new spectrograms to generate

Code Quality

Corrects typing of media controls changeNumberHandlerEvent callback to a HTMLInputElement Event instead of a SLMenuItem event

Remaining Bugs / Unresolved Problems
Because this PR exposes the verification grid size to the user #146, and #147 become much more prevelant because the user can input grid sizes that (obviously) won't fit on their screen and start scrolling.
Visual Changes

A new scrollbar + label that can be used to change the verification grid size
Related Issues
Fixes: #137
Additional Notes
N.A.
Final Checklist

[ ] All commits messages are semver compliant
[x] Added relevant unit tests for new functionality
[x] Updated existing unit tests to reflect changes
[x] Code style is consistent with the project guidelines
[ ] Documentation is updated to reflect the changes (if applicable)
[x] Link issues related to the PR
[x] Assign labels if you have permission
[x] Assign reviewers if you have permission
[x] Ensure that CI is passing
[x] Ensure that pnpm lint runs without any errors
[x] Ensure that pnpm test runs without any errors

Observations when playing with the demo:

Reducing the grid size has an error where size ends up as one

The page scrolls around confusingly and can push the control bar off screen (separate issue I suppose)

The control is not reactive

authors: atruskie hudson-newey

repo: ecoacoustics/web-components


text:
折线图tooltip丢失x轴项目名称, 自定义tooltip无法添加色盘提示

提问前应该做的事
请确保提问前做了以下事，将完成的项目的 [] 改为 [x]：

[x] 我已通读过 README
[x] 我已阅读过 FAQ

需提供的信息
将符合项的 [] 改为 [x]，并补充需要的信息：
简单描述问题：
折线图tooltip丢失x轴项目名称, 自定义tooltip无法添加色盘
预期效果：

实际效果：
缺少x轴名字

复现环境：

[x] 在微信开发工具（如有需要请提供截图）中存在该问题
[x] 在真机上存在该问题

补充配置代码
不支持dom 自定义tooltip的时候无法添加前面色盘
 formatter: (params) => {
        console.log(params)
        let time = ''
        let str = ''
        params.forEach((i) => {
          time = i.name + '\n'
          if (i.data === 'null' || i.data == null) {
            str += params[i].marker + i.seriesName + ' :  无数据' + '\n'
          } else {
            str += '<view style="display:inline-block;margin-right:5px;border-radius:10px;width:10px;height:10px;background-color:' + i.color + ';"></view>' + i.seriesName + ' : ' + i.data + '\n'
          }
        })
        return time + str
      }

@Ovilia请看下~

用 formatter，彩色的圆点用 '{marker0at0|}', {marker1at0|}, {marker2at0|}' 分别表示第 0、1、2 个系列，可能实现得不是很美，但是至少暂时可以这么用着。

用 formatter，彩色的圆点用 '{marker0at0|}', {marker1at0|}, {marker2at0|}' 分别表示第 0、1、2 个系列，可能实现得不是很美，但是至少暂时可以这么用着。
谢谢.实现了
不过感觉这个比较常用, 可以内置/默认吧

用 formatter，彩色的圆点用 '{marker0at0|}', {marker1at0|}, {marker2at0|}' 分别表示第 0、1、2 个系列，可能实现得不是很美，但是至少暂时可以这么用着。

不过这个感觉很常用,可以内置/默认吧
@Ovilia

这个其实应该算 ECharts 的项目了，这里先关了。

authors: Ovilia zhangruinian

repo: ecomfe/echarts-for-weixin


text:
对大规模散点图进行多次区域缩放和后退，出现错误

http://echarts.baidu.com/doc/example/scatter3.html
1、第一次缩放后，散点不是出现在整个坐标系内，而是只出现在大概1/4的区域内

2、从第二次缩放开始，显示的散点是错误的

缩放后四周空白较大的问题仍然存在

最新源码，还没release呢

是用最新源码build的, 问题2没有了, 问题1还有.

authors: kener xvacant

repo: ecomfe/echarts


text:
UC浏览器+搜狗高速浏览器+百度浏览器，横坐标的数值被遮挡

One-line summary [问题简述]
UC浏览器+搜狗高速浏览器+百度浏览器，横坐标的数值被遮挡。Safari、chrome、Firefox
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:3.7.0
Browser version [浏览器类型和版本]:百度浏览器，8.7.5000.4962
OS Version [操作系统类型和版本]:win7

Expected behaviour [期望结果]

ECharts option [ECharts配置项]

option = {
            title: {
                text: '用户趋势',
                left: 0,
                textStyle: {
                    fontSize: 14,
                    fontWeight: 'normal'
                }
            },
            color: ['#2695EB', '#3FDAAF'],
            tooltip: {
                trigger: 'axis',
                axisPointer : {
                    type : 'shadow'
                }
            },
            grid: {
                left: '55',
                top: '35',
                bottom: '20',
                right: '2%',
            },
            legend: {
                data: ['老用户', '新用户'],
                right: 0,
                textStyle: {
                    fontSize: 14
                },
                itemWidth:10,
                itemHeight:10
            },
            xAxis: [
                {
                    type: 'category',
                    data: u.map(chartData, function (item) {
                        if (self.state.trendTimeKey === 'yesterday' || self.state.trendTimeKey === 'today') {
                            return moment(item.timestamp).format('H') + '点';
                        }
                        return moment(item.timestamp).format('MM.DD');
                    }),
                    axisLine: {
                        show: true,
                        lineStyle: {
                            color: '#ccc',
                           fontSize: 14
                        }
                    },
                    axisTick: {
                        show: false
                    },
                    axisLabel: {
                        show: true,
                        textStyle: {
                           color: '#999',
                           fontSize: 14,
                        },
                        interval: function (index) {
                            if (self.state.trendTimeKey === 'lastSeven') {
                                return true;
                            }
                            else if (self.state.trendTimeKey === 'lastThirty') {
                                return (index % 3 === 0) || (index === chartData.length - 1);
                            }
                            else {
                                return (index % 2 !== 0);
                            }
                        }
                    }
                }
            ],
            yAxis: [
                {
                    type: 'value',
                    axisLine: {
                        show: true,
                        lineStyle: {
                            color: '#ccc'
                        }
                    },
                    axisTick: {
                        show: false
                    },
                    axisLabel: {
                        show: true,
                        textStyle: {
                           color: '#999',
                           fontSize: 14
                        },
                        padding: [0, 20, 0, 0]
                    },
                    splitLine: {
                        show: true,
                        lineStyle: {
                            color: '#EAEAEA'
                        }
                    }
                }
            ],
            series: [
                {
                    name: '老用户',
                    type: 'bar',
                    barWidth: '45%',
                    stack: '总量',
                    data: u.map(chartData, function (item) {
                        return item.oldUser;
                    })
                },
                {
                    name: '新用户',
                    type: 'bar',
                    stack: '总量',
                    barWidth: '45%',
                    data: u.map(chartData, function (item) {
                        return item.newUser;
                    })
                }
            ]

}

Other comments [其他信息]

问题已经解决，把gird.bottom的值调高一些能够解决改问题


text:
[SVG renderer] Wrong Axis Popover display when cursor over a chart

One-line summary [问题简述]
Wrong Axis Popover display when cursor over a chart
Version & Environment [版本及环境]

ECharts version [ECharts 版本]: 4.0.4
Browser version [浏览器类型和版本]: Chrome
OS Version [操作系统类型和版本]: Window 10

Expected behaviour [期望结果]
When cursor is hover over a Line chart, user should see popover box over x-axis and y-axis at the coordinate of the hover.
When renderer (used in initOpts) is set as "svg", the pop-up boxes should have the same style as that of "canvas".
ECharts option [ECharts配置项]

option = {
  // Chart is displayed perfectly fine with renderer as "canvas".
 // the issue occurs when I set renderer as "svg"
}

Other comments [其他信息]

https://i.imgur.com/aY5U77m.png

The same as #7947

Solved in #7947


text:
JURY - highlighted juror

We would like to highlight one of the jury - Arne Vogt Head of Jury. Business Development im E-Commerce @ ARTAVO
He is a head of jury and we cooperate with him.
page - JURY MEMBERS - highlight juror
Is it possible to put him right below the text: "The jury will evaluate the finalists and choose the winning companies." and above the other jurors? It would be perfect to put him in the middle of the section.

page - HOME - change the order
Is it possible to put him as a first person in the row? We are aware that there are two rows of jury only and it may be difficult to put him above the others.

@az I can't assign a person and add any label.

@klaudia2209 no it is not possible to do it this way but i can show 2 separate jury widgets

one will have only 1 member (via filtering function)
second one will have the rest (with one excluded via filtering function)
the con is that it will consume a lot of space.....decision?

@az I can't assign a person and add any label.

its good :) i am self-assigning issues only when i understand them (and they follow guidelines) and they will be processed :)

OK, I understand. I think that on the "JURY MEMBERS" page we can go with this option :)
What about this solution below on the homepage?
page - HOME - change the order
Is it possible to put him as a first person in the row? We are aware that there are two rows of jury only and it may be difficult to put him above the others.

assigning issues - ok, good! it's better for me ;)

@klaudia2209
"What about this solution below on the homepage?"
i will do some experiment with sorting options but i cannot guarantee the result now (maybe if we set "featured" =1 in the profile and set sort by featured descending (1,0,0,0) we will achieve this ...but i do not know now. i will create separate issue for this)

Ok, thank you so much.


text:
Modernization fixes for calc_euler_error_func

It looks like this method lacks tests and was never updated for changes in HARK.distribution. This commit fixes some notation so that the method works again.

[x] Update CHANGELOG.md with major/minor changes.

Arguably this PR should have a test added.

@akshayshanker This can also be reviewed and merged, once tests finish.

repo: econ-ark/HARK


text:
Added Windows capability to running cpp code

Add the ability to select the Visual Studio compiler for Windows using a radio button.
Add the ability to populate the python text block with either the "pi" or "python_hard" code

Hey @cloudllama! This is fantastic!
I'm wondering about including the path to VISUAL_STUDIO_2022_TOOLS like that.. like do we know it will always be in:
C:\Program Files\Microsoft Visual Studio\2022\Community\Common Tools\VsDevCmd.bat
And is that the most common C++ compiler on a PC? Once of the drawbacks of having 20,000 students on the course is that there's a lot of different variations and people get frustrated when it doesn't work on their system. Some students don't use the C drive, some have older versions of software, etc.
How bulletproof is this? Can anything be done to make it more generic, or at least to add comments to the student about what to check for and what to install or change on their PC?
Alternatively: you could put this in a community-contributions folder, in which case students know to use it "as is". But if it's in the main week4 folder, then we need to check it will work in most conditions..
Thanks so much!

@ed-donner Thanks for the fast response. Looking at the pull requests, I intuit that this is your full time job right now...I appreciate the sliver of attention. Of course, feel free to include or not; I simply offer any code as a service. (Insert here an ode to hands-on learning always being the most effective method to understanding.)
Visual Studio (Community Edition or Professional and not Visual Studio Code) are pretty much the most popular C/C++ compilers on Windows owing to their low, low price of free. I test for both the current version (2022) and previous version (2019). The path to the environment batch file (VISUAL_STUDIO...) can be considered static and immutable as Microsoft has no desire to move it around.
I've pulled the logic into a separate function that will detect the platform, test out the potential compilers, and return the compiler command that will work, or none if no compiler is found. Currently, the test includes:
Windows

Visual Studio 2022
Visual Studio 2019
gcc

Linux

gcc

clang

Mac

gcc

clang

I've run tests on Windows. I'm setting up an environment on Ubuntu to test the function under Linux. I don't have a Mac so I'll use your command line (for clang).
I expect I'll finish up tomorrow.

authors: cloudllama ed-donner


text:
support new configuration option moduleNamingMode

TL;DR
Prior to this change, schema files had to be flattened within modules; otherwise, this plugin would break. This update introduces a new option, moduleNamingMode, that allows for deeply nested schema files. The change is backward compatible with existing workflows.
Background
When parsing GraphQL schema files, the plugin identifies the "module name" for each schema file. It currently determines the module name by taking the parent directory of each schema file. This approach works well when the last folder denotes the module name, as seen in nested-domain-modules.
Problem
The current behavior causes issues when a project organizes schema files within additional subfolders inside a module. For example, our project structure looks like this:
codegen.ts
modules/
  user/
    schema/
      User.graphql
  profile/
    schema/
      Profile.graphql
      User.graphql

We configure codegen.ts to generate a resolvers/ directory in each module because we value separating implementation from API definitions. However, this setup breaks the plugin. In the example above, the module name for both profile/schema/User.graphql and user/schema/User.graphql is incorrectly identified as schema. This happens because the plugin takes the parent directory (schema) as the module name.
As a result, the definitions are merged under the same module name schema, and User resolvers are only generated for one of the modules—depending on the order in which the files are processed—leading to unpredictable behavior.
Solution
To address this issue, I've added a new option moduleNamingMode that allows clients to specify how the module name is determined:

last (default): The module name is the last folder in a file's path (existing behavior).
first: The module name is the first folder (within the working directory) in a file's path.

Using first means that if codegen is pointed to /path/to/modules, the module names will be the first layer of folders within /path/to/modules (e.g., user and profile). This allows for deeper nesting within modules without breaking the plugin.
Please refer to the e2e test included in this PR for an example of how this works in practice.

Love the idea @HunterLarco !
I wonder if this could be generalised further?
One option I'm thinking is letting the user chose the index of folder from base dir to schema file. The default is -1 which is the same as the last option. 0 would be the same as first option
For example, if ./modules is the base dir:

If the path is ./modules/user/schema.graphql, then the relative path array is ["user"], then -1 (or 0) both work
Some users may want to group modules based on the domain e.g. ./modules/user-domain/user/schema.graphql and ./modules/user-domain/profile/schema.graphql,

then the relative path array are ["user-domain", "user"], ["user-domain", "profile"] respectively
then -1 will pick user and profile respectively as the module names

Your use case of ./user/schema/schema.graphql should work as well with 0
For other nested use cases e.g. modules/foo/bar/baz/qux/User.graphql, 2 can be used to target baz

I think we might be able to do relativePathFromBaseToModule.at(theIndexConfig) here

If we did go with the index approach, do you have suggestion for the option name? 🙂

@eddeee888 that's a good question! I'm happy to expand the functionality here to be more flexible. Unfortunately I'm drawing a blank for naming. We could keep moduleNamingMode and simply explain the logic in the documentation. What do you think?

Yes, I think your suggestion works. I have plan to rename a few options for v1, so this rename can happen there if needed. Thank you!

@eddeee888 apologies for the delay. I hope you had a nice holiday season. I've updated the PR (and documentation) to reflect your suggestion. Now in addition to first and last, clients may use any number positive or negative to select the module name from the schema's path. Let me know if there's anything else I can do to help this land :)


text:
Archive empty room without entering

If a room is empty, can we have a feature to delete it (or archive it) without entering? [resumably as a third button in the RoomList]
We encourage students to create rooms during OH, but at the end of OH there are a lot of empty husks lying around that I wish to clean up quickly.
Even better: one button to clean up all empty rooms.

This is a good idea!  But I worry about either option making it a little too easy for students to (accidentally) archive empty rooms.  In my class, I want empty rooms to stick around until I want them to go (but when that is, I'd love this feature too).  So I'm afraid this has to block on #53.

@hanryhu It occurs to me that there's a way to hack this in the JavaScript console. If you paste the following into the console, you'll automatically archive all empty rooms (at least, based on my limited testing). Note that this will include any Main Room, so you might want to be in that room to prevent it from archiving (or tweak the code).
document.querySelectorAll('.RoomList .list-group-item[href]').forEach((r) => {
  if (!r.querySelector('.presence-count span') && !require('/lib/rooms.coffee').Rooms.findOne(r.dataset.room).archived) {
    console.log('Archiving', r.innerText, r.dataset.room);
    Meteor.call('roomEdit', {id:r.dataset.room, raised:false, archived: true, updator:require('/client/lib/presenceId.coffee').getCreator()})
}})

This is no longer blocked!  I propose that admins automatically get another button in the room dropdown to archive the room.  Also, I think everyone should get a button for archived rooms to make unarchiving easier.

The buttons in the RoomList on the left are now implemented, as described above.
For bulk actions, there's now an API that lets you do things like "archive all rooms". The operation would be something like this:
curl -g 'https://comingle/api/room/edit?meeting=xxx&secret=yyy&rooms={"meeting":"xxx","archived":false}&archived=true'

You can also add various filters to the rooms query.

authors: edemaine hanryhu

repo: edemaine/comingle


text:
Adress minor spelling issues

Thanks for the nice tutorial.

Thanks for your help :)

authors: TobiasRoeddiger jo-jstrm

repo: edge-ml/docs


text:
"Try parse" family of functions

Currently, both direct casting and the to_* family of functions throw an error if the value to be converted is not valid for the type being converted to. This makes a lot of sense given the highly typed nature of EdgeDB. However, sometimes it can be useful to try to cast from one type to another, or similarly, to try to parse a string to another type, and to fail gracefully if such a conversion is not possible. For example, one may have a type in one's schema with a string property, and may wish to have a computed property that tries to parse that string to another type, such as a datetime or float64, and if this is not successful, returns a null object instead. Example schema pseudocode:
type SomeType {
  required value: str;
  required numeric_value := try_to_float64(.value);
}

And what the returned results might look like:
[
  {
    "id": "79ae1d30-df9c-11ee-94a9-6b08d824cfdd",
    "value": "123.4",
    "numeric_value": 123.4
  },
  {
    "id": "8823c96e-df9c-11ee-94a9-3b2eaee6ce4e",
    "value": "abc",
    "numeric_value": {}
  }
]

Typically, other languages handle this by either not throwing an error when an invalid conversion is attempted (see javascript and typescript, where NaN is returned for invalid calls to parseInt and parseFloat), or by providing "TryParse" functions (see for example .NET).
It would be good to have a family of functions that handle this gracefully: either just returning {} if a conversion fails, or possibly allowing a user-specified fallback value: some_property := try_to_float64(.value, -1). This isn't limited to just floats, of course; I can see potential use cases with date strings, etc.

Discord thread (for completeness; there isn't any more info there than in this issue)

I'd suggest a wrapper to intercept exceptions. It would have more usages and not increase the API surface.
Naming can lean on std::assert(input, options):
Function name could be any of suppress, catch, throws ... I feel like suppress best describes the intention
result := std::suppress(
  to_float64(.str),
  catch := <float64>{}
)

I'm not sure its possible to default an empty set here based on the passed first args return type? If so the default should be an empty set of the inferred type.
The good thing is that this would allow having more logic if you know you have a mixed set where you need different handlers.
Ofc this could be achieved with regex matching and ifs too.
result := std::suppress(
  to_float64(.str),
  catch := (to_float64(str_split("foo#12", "#")[1]))
)

Another option would be to use if-then-else syntax with keywords, which tbh might be the most idiomatic.
result := try to_float64(.str) catch <float64>{}

authors: TreeOfLearning nervetattoo

repo: edgedb/edgedb


text:
feat(security): Set "no-new-privileges" on Svcs

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/developer-scripts/blob/master/.github/Contributing.md.
What is the current behavior?
UIDs within containers running in EdgeX can request and gain elevated privilege which creates a security risk to the processes running within the containers.
Issue Number:
#143
What is the new behavior?
All services, under the orchestration of docker-compose, are now prohibited from gaining elevated privilege through the Docker security option "no-new-privileges" set in the compose service defintions.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
N/A
Other information

Rebased to resolve the conflict behind the scenes...all good to go now.

LGTM. No explosions.

That's always a key component.

@cherrycl , the TAF smoke tests for Core Metadata tests are failing this another PRs. I am pretty sure this is unrelated to these PRs. Do these test fail in the regular TAF tests? THX!
https://github.com/edgexfoundry/developer-scripts/pull/367
https://github.com/edgexfoundry/developer-scripts/pull/368

@lenny-intel Yes, these tests also failed in functional-test. it has fixed by edgex-taf PR #249 at present.

Yes, these tests also failed in functional-test

Thanks you!

recheck

authors: beaufrusetta cherrycl lenny-intel

repo: edgexfoundry/developer-scripts


text:
HTTP request timeout when deleting numerous events from core-data by device name

🐞 Bug Report
Affected Services [REQUIRED]

 The issue is located in:
core-data
Is this a regression?

 Yes, the previous version in which this bug was not present was: not sure
Description and Minimal Reproduction [REQUIRED]
There are 2,973,356 readings came from a device named "ekuiper" to edgex message bus, and stored in edgex core-data.
I get a warning from  edgex-ekuiper:
level=warning msg="consumer chan full for request id rule1_EdgeXStream_0" file="edgex/edgex_wrapper.go:119"

so I try to clean the consumer edgex core-data by:
$ curl -X 'DELETE'   'http://localhost:59880/api/v2/event/device/name/ekuiper'
It didn't work, and returned the error:
HTTP request timeout

🔥 Exception or Error
$ curl -X 'DELETE'   'http://localhost:59880/api/v2/event/device/name/ekuiper'
HTTP request timeout
🌍  Your Environment
Deployment Environment: Ubuntu 20.04 LTS
EdgeX Version [REQUIRED]: latest/edge snap/(main branch)
Anything else relevant?
There is a workaround that deleting all events by age older than 1 day:
$ curl -X 'DELETE'   'http://localhost:59880/api/v2/event/age/86400000000000'

thanks, @MonicaisHer , it's really a bug.
the original design is to return 202 Accept response immediately and run the deletion in the background

fixed by #4063

repo: edgexfoundry/edgex-go


text:
Replace GenEvent with GenStage

GenEvent is deprecated etc etc

It was replaced by simply using gproc

repo: edgurgel/poxa


text:
Add support for Batch

https://docs.deps.dev/api/v3alpha/index.html#getversionbatch
https://docs.deps.dev/api/v3alpha/index.html#getprojectbatch

I've started to explore some possible implementation for the two batch methods.
You can have a look at https://github.com/zaibon/depsdev/tree/v3Alpha-batch to see if you would be interested in this kind of solution.

thanks @zaibon ! appreciated. waiting for a PR (remember to use devel branch) :)
I'm here for any question

authors: edoardottt zaibon

repo: edoardottt/depsdev


text:
Attempting to stream byte range for LCP encrypted audiobooks results in full book download

Hi - looking for some assistance here with my colleagues
We are attempting to download a byte range of an LCP'd audiobook. We've opened access to byte range streaming on our server. Our goals are:

to enable users to start listening to a partial download without waiting for the full book to complete
to give users a partial download to start,
to allow them to start and stop downloads,
and to preserve a partial download on their device and start listening if a user loses a connection mid download.

When we request the byte range with the API, we are getting the entire book download.
The documentation here suggests we should be able to do this:
https://github.com/readium/kotlin-toolkit/blob/develop/docs/guides/lcp.md
Platform: Kotlin / Android
LCP Server version: (I'll update, we should be on the latest)
Postman screen shot attached.

Indeed, this test HTTP Server may not be configured to accept byte range requests. We'll check that. The HTTP Server that serves the encrypted content is totally different from the HTTP Server which handles the REST API of the LCP Server.

@llemeurfr - we're using GCP object storage which does appear to support byte range requests. with this configuration, we still get the full file downloading.
is there more configuration required that we may have missed?

@mocuyeg, let's exchange real URLs on Slack then. We'll come back to Github with more info.

@llemeurfr @mutterback we were able to get byte range requests working end to end with GCP object storage. I'm not sure exactly what the issue was, but it seems to be working now.
I appreciate your willingness to help out

Thank you all. -closing this

authors: llemeurfr mocyeg mutterback

repo: edrlab/lcp-server


text:
Future plans?

Cool project!
What are further plans with this project?
In particular, I am wondering if there are any plans extend the API
(and maybe support nanovg https://github.com/memononen/nanovg).

I've no plans to support drawing vector graphics at this moment, this is way complex than it sounds. Regarding future plans I consider the project finished and it already fulfills its job.
Would be cool to have a vector graphics API on top Sokol like NanoVG, I could work on that someday, who knows, but not of free will because at this moment and I don't need such feature.


text:
Error: spawn EACCES

/usr/share/atom/resources/app.asar/src/buffered-process.js:260
Error: spawn EACCES
at exports._errnoException (util.js:734:11)
at ChildProcess.spawn (child_process.js:1145:11)
at Object.exports.spawn (child_process.js:977:9)
at BufferedProcess.module.exports.BufferedProcess.spawn (/usr/share/atom/resources/app.asar/src/buffered-process.js:188:44)
at new BufferedProcess (/usr/share/atom/resources/app.asar/src/buffered-process.js:52:14)
at /home/thers/.atom/packages/racer/lib/racer-client.coffee:41:23
at /usr/share/atom/resources/app.asar/node_modules/temp/lib/temp.js:252:7
at FSReqWrap.oncomplete (fs.js:77:15)
Config:
  racer:
    racerBinPath: "/home/thers/.local/share/racer/target/release"
    rustSrcPath: "/usr/local/src/rust/src"

Hello,
It doesn't say much but looks like a misconfiguration.
Look at the homepage and double check your configuration and that you setup things correctly.
Or post your config here.
Regards.

Sorry, it's all okay, was a bit confused about config, thought racer bin path is path to dir where bin sits :)

Glad it works now :)
Have a great day !

authors: RiderSx alkama

repo: edubkendo/atom-racer


text:
Finish migration of tutorial notebooks from emod-demo

emod_test (getting started) -> T1
naive_infection (plot_challenge) -> T2
naive_infection (multi-individual) -> T3
optuna_study (duration optimization) -> T4

... and add to includes in tutorials *.rst

T2 added in https://github.com/edwenger/emodlib/commit/fdb6f01a878f8e07ec188c6448ef34a108cf810b

repo: edwenger/emodlib


text:
Fix 'Filter by Subject' issue in 'Course Discovery'

Description
LEARNER-6736
Please refer to Jira story for more details.
Testing:

Tested all subjects filtering and match filter results on the server, all subjects getting filtered successfully.
Couple of subjects have ignorable filter result count difference on mobile as compared to server.

"Philanthropy" subject is cut from iOS but not from Android. Is this important? https://github.com/edx/edx-app-ios/commit/ae8069cd26024666fcc89222722e4e50284d4990
cc @saeedbashir @miankhalid @farhan

@jaimeohm it'll be removed in https://openedx.atlassian.net/browse/LEARNER-6842.

authors: farhan jaimeohm miankhalid

repo: edx/edx-app-android


text:
Refactor dependencies from bower to npm

Allows us to use npm for all project dependencies.
UITK-64
@andy-armstrong @cahrens

@dan-f This looks great. Is there a way to verify that the Bower package will still build correctly once this merges? If you're comfortable that this will work then :+1:

@andy-armstrong - I'm not too familiar with Bower package distribution, but I'll look into it!
Also - I upgraded all the libraries, including jQuery which is now at 2.2.0! :D

@andy-armstrong I was being silly by removing the dependencies key/value from the bower.json. I've put it back, which should ensure that our library installs correctly through bower.

:+1:

authors: andy-armstrong cahrens dan-f

repo: edx/edx-ui-toolkit


text:
Checking with django2.2

Upgrading to django2.2
Removing lower versions from tox and travis.

@jmbowman May I create a ticket to upgrade django ?

@jmbowman I will run code mod today.

repo: edx/openedxstats


text:
/bin/bash: xtensa-esp32-elf-gcc: command not found

Hey
Just tested pumbaa and followed: http://pumbaa.readthedocs.io/en/latest/getting-started.html#simba-simba-build-system
But it's complains about: /bin/bash: xtensa-esp32-elf-gcc: command not found
Full output:
"
jlindeberg@morgan:~/Work/pumbaa/pumbaa/examples/blink$ make -s BOARD=nano32 upload

app: blink, board: nano32 <<<

Generating build/nano32/genhdr/qstr.i.last
/bin/bash: xtensa-esp32-elf-gcc: command not found
/home/jlindeberg/Work/pumbaa/pumbaa/make/app.mk:92: recipe for target 'build/nano32/genhdr/qstr.i.last' failed
make[1]: *** [build/nano32/genhdr/qstr.i.last] Error 127
/home/jlindeberg/Work/pumbaa/pumbaa/simba/make/app.mk:114: recipe for target 'all' failed
make: *** [all] Error 2
"
I can read that i need xtensa-esp32-elf-gcc and i can link it my self, but just to say that getting started does not work.
Thanks

Ok, thanks for letting me know, I'll update the guide.

Dcoker image sounds good :-)
Anyway nice work, really enjoy the good documentation

Glad you like it! Doing my best to keep it clean and well structured. =)

authors: Kenzu eerimoq

repo: eerimoq/pumbaa


text:
Rule: keep-options-order

Story
For now, we can write sample/guard in any order:
sample({
  target: foo,
  fn: (bar) => Baz,
  source: bar,
  clock: clock
})

Would be nice to enforce a more convenient order
E.g. source->clock->fn->target (or clock first)
Extra stuff

We also need the same thing for @sergeysova patronum I guess

Also, it should autofix

@igorkamyshev Why not use the order of fn params?
What should be the order of guard options?

Linter should give your consistency, not options.
Linter can give options. You can use default ones for consistency. Or do you want to force your opinion without a choice?

I like the natural order of options: just like you read it.
sample({ source, clock, fn, target })
When clock is triggered, read data from source, pass it thru fn, and sent to target
As we see, order is clock, source, fn, target

The same for guard
guard({ clock, source, filter, target })
When clock is triggered, check filter for truthy, read data from source, send it to target.
Order is: clock, filter, source, target.

Yeah, I understand your point. It seems good as the default order. I could get used to that.
But you both ignore the fact that source data comes before clock data in the fn parameters. Many people are used to this alternative order. Why are you sure that the option is unacceptable here?

authors: Kelin2025 doasync sergeysova

repo: effector/eslint-plugin


text:
Archive Error IOS By For Unity 1.22

Unity 5.6.0f3 Effekseer1.22 で開発しています。
Unityの方でIOSbuildをかけてXcodeで読み込むと実機テストは問題なく出来るのですが、
Archive化をすると以下のリンクエラーが出てしまいます。
ld: bitcode bundle could not be generated because 'プロジェクトディレクトリまでのパス/Libraries/Plugins/iOS/libEffekseerUnity.a(EffekseerPluginCommon.o)' was built without full bitcode. All object files and libraries for bitcode must be generated from Xcode Archive or Install build for architecture arm64
libEffekseerUnity.aのほうにbitcode情報がついてないように見えます。
対応の方をよろしくお願いします。

了解しました。確認しますので少々お待ちください。

もしかしたら、1.3beta1では治っているかもしれないので、そちらも確認してみてください。

1.3beta1試してみましたが変わりませんでした。

問題確認しました。
とりあえず、リポジトリには修正版をあげました。
急ぎでなければ1.3beta2をお待ちください。

とりあえず、Win、Mac、iOS、Androidのみ対応の最新パッケージです。
おそらくこのバージョンで治っているはずです。
http://effekseer.sakura.ne.jp/Releases/EffekseerForUnity170618.zip

わざわざありがとうございます。Archiveも成功しました。

いえいえ。このissueは1.3をリリースした後に閉じます。
It's my pleasure. This issue closes after releasing 1.3.

repo: effekseer/Effekseer