multimon smart-sizing correct, but in fullscreen shows display on primary monitor only

Hi
I'm experiencing the following issue: Multimon smart-sizing is correct but in fullscreen displays whole screen only on primary monitor
The whole screen 1920x1200+2560x1440 is in fullscreen forced to 1920x1200 (shrinks)
I have to mention that it did work earlier.
What can cause this issue?
BTW Client is Windows 8.1
[12:55:56:730] [19161:19162] [INFO][com.freerdp.client.common.cmdline] - loading channel cliprdr
 [12:55:56:751] [19161:19162] [ERROR][com.freerdp.core.gcc] - WARNING: true multi monitor support was not advertised by server!
 [12:55:56:751] [19161:19162] [ERROR][com.freerdp.core.gcc] - Sending multi monitor information anyway (may break connectivity!)

My config:
 xfreerdp --version
This is FreeRDP version 1.2.4-dev (git c8731ea)

 xfreerdp --monitor-list
      * [0] 1920x1200   +0+0
        [1] 2560x1440   +1920+0

/usr/local/bin/xfreerdp /f /rfx /cert-ignore /v:192.168.1.xxx /u:xxxxx /p:xxxxx /sec:rdp  +smart-sizing /multimon:force -sec-nla +clipboard +fonts

Distributor ID: Ubuntu
Description:    Ubuntu 14.04.1 LTS
Release:    14.04
Codename:   trusty

@b987123 you mean the server is windows 8.1?

@bmiklautz
Thanks, yes, the "server"  (client) with the rdp-server
I have now compiled FreeRDP version 1.1.0-beta1 (git 1.1.0-beta+2013071101-162-g770c67)
and there fullscreen span worked flawless.
I've tried FreeRDP version 1.2.3-dev and 1.2.4-dev (git c8731ea) but there is the problem as mentioned.

Hi.
I'm experiencing a similar issue on the Linux Client.
The /multimon parameter makes xfreerdp spawn a fullscreen window only on the primary monitor when using WM openbox 3.5 and 3.6.
Using metacity as WM, the fullscreen window is displayed on both monitors.
The regression was introduced on commit bad2f138c183b84c996ec16b4f2e0aaf77b54d7c, the issue is not present on the commits before.
Config:
$tmp/freerdp/bin/xfreerdp --version
This is FreeRDP version 1.2.4-dev (git d65cc5d)
$/tmp/freerdp/bin/xfreerdp /v:******* /u:******* /multimon
$/tmp/freerdp/bin/xfreerdp --monitor-list

[0] 1920x1080   +1920+0
[1] 1920x1080   +0+0

Any news to support Openbox in the future development? I experienced the same issues with the multimon setup

I have the same issue running from the latest source and have for several months I believe.

This is FreeRDP version 1.2.4-dev (git c12bc0e)

The same command line against the package for my system, version below, works without issue.  I too am running openbox as the WM (lxde desktop)

This is FreeRDP version 1.2.0-beta1 (git n/a)

I am experiencing this, too.
This is FreeRDP version 1.2.1-dev (git n/a) and Fluxbox 1.3.7

I'm having this same problem - only get video on the primary display.  If I compile eb14ab15f5bca5751d8a71965f31509d4c3b176b from April 14 fullscreen on dual monitors works, but when I add in bad2f138c183b84c996ec16b4f2e0aaf77b54d7c, it breaks.

I was able to rollback client/X11/xf_window.c to eb14ab15f5bca5751d8a71965f31509d4c3b176b and recompile to make FreeRDP start in fullscreen mode across all monitors again.  Not sure what all ramifications that might have - perhaps @nfedera could weigh in on this?

@cmsmith1977 please ...

output of xfreerdp --monitor-list
what window manager ?
full xfreerdp command line used

@giovannitarter and @cmsmith1977 - Here is what happened:
@bjcollins created the nice pull request #2426 (commit d4a9a2d) which provided many fullscreen and multimon enhancements. This commit removed the override_redirect approach (which worked with basically all window managers) and used the modern way using NET_WM_STATE_FULLSCREEN  and NET_WM_FULLSCREEN_MONITORS for multimon support.
This means that for fullscreen involving multiple monitors the window manager must support the NET_WM_FULLSCREEN_MONITORS property - which is not the case for many older wm like openbox, icewm, etc. @awakecoding obviously accepted to drop legacy wm support for /multimon  and merged this PR.
My commits bad2f13 and eb14ab1 were done many weeks later and brought some smart-sizing fixes. IMO it is impossible that /multimon worked with openbox on commit eb14ab1 because the override_redirect support was already removed at this time.
So if my point of view is correct I suggest to close this issue and to open a new feature-request issue for adding /multimon support for window managers that do not support  NET_WM_FULLSCREEN_MONITORS based on the old override_redirect approach.

@nfedera Your synopsis makes sense to me. Although my PR made improvements for WMs which support NET_WM_FULLSCREEN_MONITORS, it broke support on the WMs which do not support it. I did not take this into account and I do not know if @awakecoding was aware of the "regression" from the PR. I think handling this case should be relatively simple as I believe you can query whether NET_WM_FULLSCREEN_MONITORS is available and act accordingly. I will plan to look at this when I can carve out some time.

@bjcollins you are absolutely right. NET_WM_FULLSCREEN_MONITORS can be queried which means that we could autodetect the requirement for the override_redirect fallback.

<stupid comment>
@cmsmith1977 @nfedera sounds obvious that commit https://github.com/FreeRDP/FreeRDP/commit/bad2f138c183b84c996ec16b4f2e0aaf77b54d7c is bad :)
Ok I'm ===> [ ]
</stupid comment>

@nfedera - a little late on the response, sorry.

output of xfreerdp --monitor-list

user@host:~$ xfreerdp --monitor-list
      * [0] 1920x1080   +0+0
        [1] 1920x1080   +1920+0

what window manager ?
** LXDE 0.7.2 in lubuntu 15.04

full xfreerdp command line used

   xfreerdp /v:<IP_ADDRESS> /sec:tls /u:"" /p:"" /network:lan /sound:sys:alsa /cert-ignore +fonts +decorations +aero +menu-anims /f /multimon

exact remote server os
** Windows 2012 R2 Standard with ThinStuff XP/VS

and I want to re-iterate, that if I do the following, I am able to run in fullscreen across 2 monitors in LXDE.
git checkout eb14ab15f5bca5751d8a71965f31509d4c3b176b client/X11/xf_window.c

Update line 901 to this:
// void xf_SetWindowVisibilityRects(xfContext* xfc, xfAppWindow* appWindow, RECTANGLE_16* rects, int nrects)
void xf_SetWindowVisibilityRects(xfContext* xfc, xfAppWindow* appWindow, UINT32 rectsOffsetX, UINT32 rectsOffsetY, RECTANGLE_16* rects, int nrects)

@cmsmith1977 this seems to be caused by openbox's special way of handling the size hints in combination with _NET_WM_STATE_FULLSCREEN.
If you comment line 492 and 495 in current master like this ...
--- a/client/X11/xf_window.c
+++ b/client/X11/xf_window.c
@@ -489,10 +489,10 @@ void xf_ResizeDesktopWindow(xfContext* xfc, xfWindow* window, int width, int hei
        XResizeWindow(xfc->display, window->handle, width, height);

 #ifdef WITH_XRENDER
-       if (!xfc->settings->SmartSizing)
+       //if (!xfc->settings->SmartSizing)
 #endif
        {
-               if (!xfc->fullscreen)
+       //      if (!xfc->fullscreen)
                {
                        size_hints->min_width = size_hints->max_width = width;
                        size_hints->min_height = size_hints->max_height = height;

... openbox will also work, but other legacy window managers still won't work.
So the correct way is still implementing @bjcollins' proposal for autodecting _NET_WM_FULLSCREEN_MONITORS support and using the override_redirect flag it it is not supported.

I am running Debian Stable (Jessie) which has KDE 4.14 and had the same problem.
I copied the steps from: cmsmith1977 comment on 21 Nov 2015 https://github.com/FreeRDP/FreeRDP/issues/2707#issuecomment-158584322 and multimon fullscreen now works again.
In addition: the reason I was running a newer version than the freerdp 1.1 in Debian stable, is because that version is even more broken under KDE 4.
Anyway back to freerdp 2.0.0 (git): I just thought it would be useful to know that this bug also affects KDE 4 (and Debian stable)

Just adding a note as this is still an issue as of current GIT and renders multi-monitor unusable in OpenBox (for anyone else that doesn't find this bug before spending hours trying to find out why it doesn't work).

Same issue in Fluxbox.

I think I have the same issue: the first screen is shown, but the second one isn't.
My command line:
xfreerdp /v:... /d:... /u:... /p:...  /multimon
I bisected it to commit 48be081. So for me current master (a0520f8) and reverting that commit fixes the issue. Both screens are used now.
I am using KDE and kwin 5.6.4 from Debian/unstable.

So when does this issue get fixed?

@akallabeth thanks for your answer. Since this bug is in there for a year the question is, when are we able to use multi-monitor-support again?

@RubenKelevra Well, simple (and probably unsatisfactory answer) as soon as someone finds time to address the issue. What I've seen it is a simple check missing to revert to old behavior, but I'm busy with other stuff :/

Sad. I found a workaround: turn the decorations off, set the resolution manually and the window will pop over everything (like fullscreen) but the window is presented to the rdp-server as one monitor, if the user expands one window this window is stretched over all monitors, which is not the expected behavior for the users.

@RubenKelevra from what I understand the other solution is to use a WM that correctly handles the fullscreen window case...

Well you can't use Openbox and you can't use Marco (see https://github.com/FreeRDP/FreeRDP/issues/3395) so which minimalist window manager can be used?

Here is a really messy workaround that seems to work for me in KDE Plasma.

Launch some lightweight X program of something you'll never use, like xclock:  xclock&
Go to the System Settings / Window Rules and create a new rule for xclock.  Set it under "Size & Position" to "Force" to your multiple monitor setup's full width and height, "w,h".  Under "Appearance & Fixes" set "No titlebar and frame" to "Force" "Yes".  Save and apply.
Get the parent ID of the xclock window on a terminal:  PARENTID=wmctrl -l -x | egrep 'xclock' | awk '{print $1}' | tail -1
Launch your normal xfreerdp command, but add this:  /parent-window:$PARENTID     Make sure that you are also using /multimon option.

Not the most elegant solution, but it will work for me until freerdp works again like it used to.

I also have this issue using the latest KWin/plasma setup on Arch Linux. I think "it's the WM's fault" is a pretty unsatisfactory answer. It seems like it shouldn't be too hard to just check the current WM against a blacklist and revert to the old behavior. Unfortunately I do not know enough about the codebase (or C) to do this intelligently...

Agreed.  The fact of the matter is that people use KDE plasma, and KDE plasma is doing things a certain way, rightly or wrongly.  I get that it makes for dirtier code, having to support multiple methods, but the code was already written.

If anyone is interested I tried to introduce (since we had a similar problem) a new command line parameter (currently named) +openbox to enable support for alternate window managers.
It just disables the function to set the fullscreen state if the parameter is set.
As a matter of fact it does work with openbox AND xfwm4. Without the parameter it still works with xfwm4.
https://github.com/RangeeGmbH/FreeRDP/commit/e8523d10dac86c468ce1e233934db923b6770203
Should not break the code since it is disabled by default and has to be explicitly set.

Is this still an issue?

On KDE Plasma, I still only get a single monitor.  This is the command I'm using:
/usr/bin/xfreerdp /u:username /p:************** /d:domain +fonts +window-drag /v:host.domain.com:3389 /bpp:32 /rfx +clipboard /multimon /cert-ignore

@Infinality which version did you test with? Fixes for fullscreen issues have only been merged to master which may not have landed in your distro packages yet.

@akallabeth I'm using the latest git.  I built it again on another system just to make sure and it still has the problem.

@Infinality just for confirmation, can you try to set /multimon:force ?

Just tried it with openbox, the issue seems to be that the XFreeRDP window for the second monitor is placed anywhere just not on the second monitor (The remote machine is correctly working in multimonitor mode)

@T3N4K4 When I use /multimon:force I get a black window on a single monitor (which never shows the login).

@akallabeth @Infinality The problem is still with "_NET_WM_STATE_FULLSCREEN" .. you cannot detect it automatically (at least I do not know a way) and some window manager seem not to be on good term with it (do not support it). Therefore I used the "+openbox" command-line in the rangeegmbh branch.
/* Set the fullscreen state */
		xf_SendClientEvent(xfc, window->handle, xfc->_NET_WM_STATE, 4,
		                   fullscreen ? _NET_WM_STATE_ADD : _NET_WM_STATE_REMOVE,
		                   xfc->_NET_WM_STATE_FULLSCREEN, 0, 0);

If I set +openbox this code above gets disabled ... and for me that worked in openbox..

Closing as marked as fixed in #4319

FreeRDP multiple monitors is broken for me on the latest master. Using arch linux and KDE Plasma. I have tried running plasma with xorg and wayland and get the same result. The issue must be with kwin.
FreeRDP works fine on the same system with Gnome using wayland as well as xfce using xorg.
One monitor sort of works. Even then the resolution is incorrect in full screen mode unless i specify resolution. Will take a look at the code to see if it is obvious. This is a completely new codebase though so may be like finding a needle in a haystack.

@matthewpapa07 did you compile with either xrandr or xinerama or is the xfreerdp /buildconfig using either of them ?
I think there were some changes in a xrandr / xinerama rework in client/X11/xf_monitor.c if I remember it correctly.
I noticed that if you have your monitors aligned wrong like you have to go left on your left monitor to get into the right one, xfreerdp opens on the left but still tries to go right (where nothing is).

Same issue here:
when I try to run xrdp with multiple monitor, the first monitor gets a RDP-full screen display, and the second monitor does not display the RDP-Screen. When you press ctrl-alt-enter (exiting Full-Screen), you get both monitors in one big window above both screens.
Environment:

Virtual Box with two monitors
Debian Testing (up to date)
KDE

I've just build freerdp from master (cmake -DCMAKE_INSTALL_PREFIX=/home/tibob/freerdp -DBUILD_SHARED_LIBS=OFF -DCMAKE_BUILD_TYPE=Debug -DWITH_SSE2=ON .; make; make install, as I just wanted to run in in my user folder).

tibob@paris:~/freerdp/bin$ ./xfreerdp /buildconfig
This is FreeRDP version 2.0.0-dev2 (14997f96e)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_JOURNALD_H=TRUE HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=OFF WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DIRECTFB=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FFMPEG=ON WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_GSTREAMER_0_10=OFF WITH_GSTREAMER_1_0=ON WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=ON WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PCSC=OFF WITH_PROFILER=OFF WITH_PULSE=OFF WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_LEAK=OFF WITH_SANITIZE_LEAK_AVAILABLE=1 WITH_SERVER=OFF WITH_SERVER_INTERFACE=ON WITH_SMARTCARD_INSPECT=OFF WITH_SSE2=ON WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=ON WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XV=ON WITH_ZLIB=ON
Build type:          Debug
CFLAGS:               -fPIC -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -g
Compiler:            GNU, 7.3.0
Target architecture: x64

Just tell me if you need me to test something for you.

@tibob Seems to be an issue with KDE only, tried it with fvwm, openbox, gnome, cinnamon and they work.
Only with KDE the fullscreen switching results in this strange behavior.

Filled a bug against KWIN: https://bugs.kde.org/show_bug.cgi?id=391778

KWIN sees the Bug in FreeRDP code, not in KWIN. I would have loved to help but I am not skilled enough for X11-Coding :-(

@akallabeth I just tried out your fix on the latest FreeRDP git master, and it solved the problem! Looking forward to this being merged in.

Thank you very much @akallabeth for fixing this! Works with the merged pull request.

THANK YOU so much @akallabeth
This works flawlessly now with master!!!!!!! Much appreciated.

It may help some people if I post this.
Using KDE, I had this behavior where the /multimon option spanned the session in all monitors as if it was one big screen.
xfreerdp /monitor-list
* [0] 1920x1080   +0+0
[1] 1920x1080   +1919+0
I noticed the coordinate of monitor [1]. Turns out there was a 1 pixel overlap with the monitors. I just fixed that in Display settings so monitor [1] is positionned at +1920.
Problem solved.

It may help some people if I post this.
Using KDE, I had this behavior where the /multimon option spanned the session in all monitors as if it was one big screen.
xfreerdp /monitor-list

[0] 1920x1080 +0+0
[1] 1920x1080 +1919+0

I noticed the coordinates of monitor [1] starting at +1919. Turns out there was a 1 pixel overlap with the monitors. I just moved the screen in Display settings so monitor [1] is positionned at +1920.
Problem solved.

I had a similar issue due to moving the application launcher panel to the top of the KDE Desktop (Kubuntu 20.04). This post tipped me off that it could be an issue in calculating/offsetting the usable size of the monitor.
As a workaround, I changed the application launcher panel to auto-hide, and then the /multimon flag worked fine.
I'll note that it seems like the /multimon flag (and the /span flag) were correctly using the second monitor, but the KDE Desktop on the second monitor appeared to flash and then cover the display of freerdp application on that monitor. So I am not certain if this issue is on the FreeRDP side or the KDE side.
Just posting this as an FYI of a workaround that did the trick for me. Not going to open a ticket.


Feature Request: Option to open feed link by system default

Right now, when you open a feed's link on iOS, it always open in a SafariViewController. I have a few site-specific apps (Tweetbot, Apollo) and extensions (Vinegar for YouTube) installed, and they don't open the URL or function from within the embedded view. Can an option be added to disable this behavior?

Duplicate of https://github.com/Ranchero-Software/NetNewsWire/issues/3029


added SVG animation to the research page

preview:

Fantastic work @Abhijay007. Keep it up!

Fantastic work @Abhijay007. Keep it up!

Thanks a lot, sir !!


Optional fields with default values are not considered as required if treatDefaultedOptionalAsRequired is set to true

Describe the bug
It appears that the current implementation of the treatDefaultedOptionalAsRequired option in src/parse (Line 70) does not align with the documented behavior.
To Reproduce
Steps to reproduce the behavior:
// for the schema
export const Schema = Joi.object({
  foo: Joi.number()
    .integer()
    .positive()
    .default(60000)
    .optional(),
});

// and configuration options
await convertFromDirectory({
      treatDefaultedOptionalAsRequired: true,
      ...
});

Expected behavior
The treatDefaultedOptionalAsRequired option should mark fields as required.
export interface Schema {
  foo: 60000 | number;
}

Actual behavior
Fields are still marked as optional.
export interface Schema {
  foo?: 60000 | number;
}

Additional context
The implementation can be updated:
if (
  presence === 'required' ||
  (settings.treatDefaultedOptionalAsRequired && presence === 'optional' && value !== undefined)
) {
  required = true;
}

Hi
If you are able to raise a PR im happy to merge it


include markers when skipping lock

Thank you for contributing to Pipenv!
The issue
What is the thing you want to fix? Is it associated with an issue on GitHub? Please mention it.
Always consider opening an issue first to describe your problem, so we can discuss what is the best way to amend it.  Note that if you do not describe the goal of this change or link to a related issue, the maintainers may close the PR without further review.
If your pull request makes a non-insignificant change to Pipenv, such as the user interface or intended functionality, please file a PEEP.
https://github.com/pypa/pipenv/blob/master/peeps/PEEP-000.md

The fix
How does this pull request fix your problem? Did you consider any alternatives? Why is this the best solution, in your opinion?
The checklist

[ ] Associated issue
[ ] A news fragment in the news/ directory to describe this fix with the extension .bugfix.rst, .feature.rst, .behavior.rst, .doc.rst. .vendor.rst. or .trivial.rst (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

Ignore the python 3.7 failures at this point -- we will drop it soon, and its too much work to pin everything down that has already dropped it.


Extra slick-active class applied when centerMode and slidesToShow even

When the number of slides to show is even and in center mode, an extra slick-active class is applied to the the next offscreen slide.
A quick fix I did for my project is here: https://github.com/weberml2/slick/commit/1b29b453388afa9ea2275d71ab5909dac4dc3c82

Would you please create a jsfiddle to demonstrate this with the newest release? it would help us close this much faster :)

This shows it succinctly: http://jsfiddle.net/5xnjxmqy/
After clicking "Calculate .slick-actives", I would expect the output to be:
#centerTwo: 2
#centerThree: 3
#centerFour: 4
#centerFive: 5

but instead it is:
#centerTwo: 3
#centerThree: 3
#centerFour: 5
#centerFive: 5

Applying this class correctly is important for my use case because it allows me to selectively hide content in the carousel depending on if it is on-screen, or on partially on-screen.

Hi @simeydotme, there are 84 pull requests at the moment, do you mind merging them? https://github.com/kenwheeler/slick/pulls?q=is%3Aopen+is%3Apr

@anteksiler ... u trollin' me, bro?
If you want to contribute, please find a more appropriate way to do it (such as joining Gitter chat, reddit or email) instead of writing on an unrelated issue. :)

@simeydotme Sorry about that, OP included a commit: https://github.com/weberml2/slick/commit/1b29b453388afa9ea2275d71ab5909dac4dc3c82

To elaborate for any spectators...
Merging even 1 pr is a bunch of work, and potentially dangerous to the core (as we can see with even my own PRs; who as the highest contributor has a pretty good grasp of the core; which are occasionally buggy).
We have to make sure each and every one is:

Aligned with Slick's vision.
Aligned with Slick's code style.
Fixing a real issue
Not bloating the plugin unnecessarily
Up to date and able to merge
Test the PR across hundreds of option combinations (which doesnt always get done)
Not breaking existing functionality, or creating regressions

I would put money on 90% of those PRs failing to satisfy points: 1, 3, 4, 5, 6 and/or 7. -- but I can't guarantee it as I cannot possibly review 84 pull requests on my own in any reasonable time frame. -- The vast vast majority of the one's I've looked at are "fixing" some tiny little environment issue which works for them and their website, but would break every other scenario on every other website.
To be honest, I think there should be a way for @kenwheeler to auto-decline PRs now, only accepting any merges from verified issues and people who are willing to really test and contribute in a sensible fashion.
have you really looked at 84 PRs and can tell me truthfully you think that they should all be merged?
Anyway, rant over, but please drop by Gitter (contributing.md) if you want to discuss anything :) -- I enjoy supporting this project, but it is overwhelming, and I cannot possibly keep up with the amount of PRs and Issues that are generated... over 60% of which are not even "a thing" :(
Si.

A quick fix I did for my project is here: weberml2@1b29b45

^^ this is exactly what I'm talking about, no offense @weberml2 surely means well, but this is something I cannot entertain without investing a lot of my own time to review/integrate it...

Yeah, don't merge my code. My code is a quick and dirty fix to make it work, definitely not up to standards of the project. This issue (specifically not a PR) is meant to bring the problem onto the radar of a more project-competent developer to investigate and fix in future release.

:bow: appreciated. -- and we are/will eventually get around to handling your issue. :)

Hi @simeydotme, all of the PRs from 2014 are either merged or denied, but remains Open for now. I would appreciate it if you could review them in your free time.

I have the following work-around:
$(".slick__slider").on("afterChange", testingThings);
$(".slick__slider").on("breakpoint", testingThings);
$(".slick__slider").on("init", testingThings);

function testingThings (event, slick) {
  var slidesToShow = slick.slickGetOption("slidesToShow");

  if (slidesToShow % 2 == 0) {
    // Even number of slides in Slick Carousel is incorrectly offset.
    // Adjust active slides.
    slick["$slides"][slick.slickCurrentSlide()].previousElementSibling.classList.add("slick-active")
    slick["$slides"][slick.slickCurrentSlide()].nextElementSibling.classList.remove("slick-active")
  }
}

I have the following work-around:
$(".slick__slider").on("afterChange", testingThings);
$(".slick__slider").on("breakpoint", testingThings);
$(".slick__slider").on("init", testingThings);

function testingThings (event, slick) {
  var slidesToShow = slick.slickGetOption("slidesToShow");

  if (slidesToShow % 2 == 0) {
    // Even number of slides in Slick Carousel is incorrectly offset.
    // Adjust active slides.
    slick["$slides"][slick.slickCurrentSlide()].previousElementSibling.classList.add("slick-active")
    slick["$slides"][slick.slickCurrentSlide()].nextElementSibling.classList.remove("slick-active")
  }
}

I have the following work-around:
$(".slick__slider").on("afterChange", testingThings);
$(".slick__slider").on("breakpoint", testingThings);
$(".slick__slider").on("init", testingThings);

function testingThings (event, slick) {
  var slidesToShow = slick.slickGetOption("slidesToShow");

  if (slidesToShow % 2 == 0) {
    // Even number of slides in Slick Carousel is incorrectly offset.
    // Adjust active slides.
    slick["$slides"][slick.slickCurrentSlide()].previousElementSibling.classList.add("slick-active")
    slick["$slides"][slick.slickCurrentSlide()].nextElementSibling.classList.remove("slick-active")
  }
}


HOSTEDCP-1323: Merge latest code into 4.14 branch

Updates 4.14 branch with latest from master
commit f0caebbab59ca8e8907f3eb8eb48f15c2a341228

/lgtm


ERM/ACQ - Add expense class to derived table "finance_invoice_transactions.sql"

In FOLIO it is possible to select a fund several times within the fund distribution in an invoice line if the expense class is different. In order for the derived table "finance_invoice_transactions.sql" to work properly, this functionality must be added to the SQL statement.

Requested updates to this derived table:
add expense class name and code as well as the external account number extension from the transactions table and the expense class table

Please note: This is the perspective of invoices on transactions. This is necessary if you want to see all invoices without depending on their workflow status. The transactions can be NULL. The fund distribution can be assigned correctly. However, as soon as expense classes are added, the relation between fund distribution and transaction is no longer 1:1. Therefore, the expense class must be built into the logic.


Upgrade kibana to version 5.1.1 and Alpine to 3.4

@kost The latest changes are successfully building
https://hub.docker.com/r/priceboard/docker-alpine/builds/


[µTVM] Remove need for -mcpu=native

Fixes x86 builds on OS X (I.e. as done by tests/python/unittest/test_crt.py). We may need to revisit this compiler auto-select logic at some point as well, since -mcpu may not always be the best way to specify a target ISA. However, I'd like to ideally defer that past Project-level API from the M2 roadmap.

@tom-gall @tmoreau89 @tqchen

@tom-gall @tmoreau89 @tqchen

@gromero

@gromero


zoom in augmentation

Hello, may I ask why zoom in cannot be used on streaming data?

Hi @Peterande
In principle, it would be possible (you would have to change the implementation). However, the issue with zoom in augmentation in streaming mode is that you might end up zooming into a window that contains very little or even no labels for the whole sequence (e.g. middle-top part of the FoV has very few labels and might be a bad spot to zoom in).
In the random sampling mode, we check that we have at least 1 full label in the sequence per batch sample to avoid this issue to some degree.

@magehrig Thank you for your reply. Have you verified that adding zoom-in will affect the performance?

Yes it's in the ablation study (table 7) in the paper. Removing zoom-in negatively affects performance

Allow me to correct my question. Have you verified that keeping zoom-in in streaming mode negatively affects performance?

No. I have never attempted to make it work in streaming mode.


Code completion does not work paths starting with /

I use zsh 5.2-3 on Debian and omz git tag=5464fe3.
Path completion does not work and completely hangs the console, when I try these completions (different commands not only ls of course):

I want to do completion a'la ls /*/.*<TAB>, e.g. ls /etc/i<TAB>
Completion a'la ls /home/myuser/*

I suspect that completion does not work when path starts with /.
What works:

ls <TAB>
ls ../<TAB>
in /etc/ ls -l init<TAB>

From zsh debug, the last lines:
...
+_path_files:243> [[ automenu-unambiguous == (*menu|[0-9]*) || -n '' || -n '' ]]
+_path_files:246> [[ -n '' ]]
+_path_files:250> Mopts=( -M 'r:|/=* r:|=*' )
+_path_files:255> [[ /etc/i == [^][*?#^\|\<\>\\]#(`[^`]#`|\$)*/* ]]
+_path_files:276> [[ / == \~ ]]
+_path_files:326> linepath=''
+_path_files:327> realpath=''
+_path_files:329> zstyle -s :completion::complete:ls:argument-rest: preserve-prefix tmp1
+_path_files:337> [[ / == / ]]
+_path_files:342> pre=etc/i
+_path_files:343> orig=etc/i
+_path_files:344> donepath=/
+_path_files:345> prepaths=( '' )
+_path_files:358> prepath=
+_path_files:364> skipped=''
+_path_files:365> cpre=''
+_path_files:367> [[ -n '' || -z 1 ]]
+_path_files:407> tpre=etc/i
+_path_files:408> tsuf=''
+_path_files:416> testpath=/
+_path_files:418> tmp2=''
+_path_files:419> tpre=etc/i
+_path_files:421> tmp1=( / )
+_path_files:424> ((  npathcheck = 0  ))
+_path_files:425> true
+_path_files:427> origtmp1=( / )
+_path_files:430> [[ etc/i == */* ]]
+_path_files:431> PREFIX=etc
+_path_files:432> SUFFIX=''
+_path_files:447> tmp2=( / )
+_path_files:449> [[ etc/i == (#b)*/(*) ]]
+_path_files:457> [[ -n i ]]
+_path_files:458> compfiles -P tmp1 accex '' 'm:{a-zA-Z}={A-Za-z} m:{a-zA-Z}={A-Za-z}' '' fake

_path_files is bundled by default within zsh. You can check if the case insensitive option of Oh My Zsh is the source of the problem, but I lean on the side of this being an issue with your installed zsh version.
If the above doesn't work, try changing you zshrc file for one that doesn't load Oh My Zsh but still enables completion with compinit -i ~/.zcompdump.

You are right. I downgraded to 5.2-2 and it works again. I will file Debian bug.

Nice! Feel free to reopen the issue if it's confirmed that Oh My Zsh has something to do with it.


fix(rbac): fix role list view permission policies column value

For RHIDP-2431
Screen recording
https://github.com/janus-idp/backstage-plugins/assets/26255262/b130e344-ed3a-4edb-be41-95cefdbc556a
Screenshot for error on fetching role conditions

@ciiay I don't see any issue here. The conditional policy is part of the original policy, functioning as an additional configuration rather than a separate condition. If the intention was to count a conditional policy separately, then we should not consider it as a new policy. In addition, we're going to improve this view to make it clearer which plugins are part of each role, so this column probably will be removed

@ciiay I don't see any issue here.

Hi @ShiranHi , do you mean the screen recording has no issue, or the description from RHIDP-2431 has no issue? I understand they should be considered as same policy from the user's view, but implementation-wise they are retrieved separately.
If there's no issue with the current behavior I could just close this PR.

Hey @ciiay ,It's a bit confusing, so let me clarify :)
In the Jira ticket, it appears that users see "0" in the main table list when they add a conditional policy. However, in the video attached to this PR, everything seems to be working fine. Was the screen recording added as a solution to the Jira ticket, or was it intended to showcase the problem that described in the ticket? If this is the solution - then great, it looks good

Thank you @ciiay for the explanation!

@ciiay CI is failing.

/lgtm

/cherry-pick 1.2.x


Uncaught TypeError thrown during an unsuccessful 2 way apprtc call

Browsers and versions affected
Win 10, M55 Canary 55.0.2872.0
Description
Uncaught TypeError: Cannot read property 'receiveSignalingMessage' of null
error thrown when a 2 way apprtc call couldn't connect successfully
Steps to reproduce

Start a 2 way apprtc call over a slow internet connection
Observe the JS console

Expected results
The apprtc call should connect successfully, albeit with some delay; No JS console errors should be seen
Actual results
"Uncaught TypeError: Cannot read property 'receiveSignalingMessage' of null" error thrown
Screenshot:

CC: @KaptenJansson

Github issue filed for similar error : https://github.com/webrtc/samples/issues/763

Intermittent issue but closing due to age.

@srnarayanan Did you solve this error? i am having the same error


fluentd: Added tail of kubespray default audit log location

What this PR does / why we need it:
Since we want to update the audit path to use kubespray default we need to make sure that both the old and the new way is supported.
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #
Public facing documentation PR (if applicable)

Special notes for reviewer:
Checklist:

[ ] Added relevant notes to WIP-CHANGELOG.md
[ ] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[ ] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

How about adding multiple paths in the current input tail plugin, fluentd-wc, fluentd-user, and fluentd-sc
path /var/log/kube-audit/kube-apiserver.log,/var/log/audit/kube-apiserver-audit.log

Just a note, fluentd-user shouldn't really need the kube-audit config as they are not run on master nodes.

How about adding multiple paths in the current input tail plugin, fluentd-wc, fluentd-user, and fluentd-sc
path /var/log/kube-audit/kube-apiserver.log,/var/log/audit/kube-apiserver-audit.log

Just a note, fluentd-user shouldn't really need the kube-audit config as they are not run on master nodes.

How about adding multiple paths in the current input tail plugin, e.g. fluentd-wc, fluentd-user, and fluentd-sc?
path /var/log/kube-audit/kube-apiserver.log,/var/log/audit/kube-apiserver-audit.log

Just a note, fluentd-user shouldn't really need the kube-audit config as they are not run on master nodes.

Aah missed that feature! Great!
Right, so that's probably a copy-paste miss I guess then

How about adding multiple paths in the current input tail plugin, e.g. fluentd-wc, fluentd-user, and fluentd-sc?
path /var/log/kube-audit/kube-apiserver.log,/var/log/audit/kube-apiserver-audit.log

Just a note, fluentd-user shouldn't really need the kube-audit config as they are not run on master nodes.

Aah missed that feature! Great!
Right, so that's probably a copy-paste miss I guess then

LGTM!
Do you need help testing it?

Yea, that would be great. I'm setting up a kubespray cluster to test this. So if you want to set up or have a "ck8s-cluster cluster" (or I guess a kubespray cluster with the old config) that would be much appreciated

LGTM!
Do you need help testing it?

Yea, that would be great. I'm setting up a kubespray cluster to test this. So if you want to set up or have a "ck8s-cluster cluster" (or I guess a kubespray cluster with the old config) that would be much appreciated

Maybe add a line or two in the wip-changelog about these two changes.

Maybe add a line or two in the wip-changelog about these two changes.

Maybe add a line or two in the wip-changelog about these two changes.

Yes I'll add it when I've tested it fully

Maybe add a line or two in the wip-changelog about these two changes.

Yes I'll add it when I've tested it fully


Allow for camel case model properties.

Added support for camel case model properties, as I had previously requested in #312.
There are some Laravel packages (such as Eloquence) that allow for accessing Eloquent model properties via camel case, instead of snake case.
This PR adds in an option (default disabled), to support these packages by saving all model properties as camel case, instead of snake case.
For example, normally you would see this:
 * @property \Carbon\Carbon $created_at
 * @property \Carbon\Carbon $updated_at

With this enabled, the properties will be this:
 * @property \Carbon\Carbon $createdAt
 * @property \Carbon\Carbon $updatedAt

It is currently an all-or-nothing option, as that was the simplest to implement and it suits my needs.

Thanks!

Slight helpful comment for who it concerns, you might need to run php artisan config:clear after copying vendor/barryvdh/laravel-ide-helper/config/ide-helper.php to ./config/ide-helper.php and editing 'model_camel_case_properties' to true.


/devspace/releases/assets/93304268: No such file or directory

What happened?
I keep getting the below error after upgrading devspace with devspace upgrade.

/usr/local/bin/devspace: line 1: url:https://api.github.com/repos/devspace-sh/devspace/releases/assets/93304268: No such file or directory

What did you expect to happen instead?
No issues
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
version: ...
...

Local Environment:

DevSpace Version: 6.2.5
Operating System: mac
ARCH of the OS: AMD64 | ARM64 | i386
Kubernetes Cluster:
Cloud Provider: aws
Kubernetes Version: v1.23.5

Anything else we need to know?

Thanks @cseas  for reporting! We will take a look.

exact same problem here

same problem after upgrading from 6.2.4 to 6.2.5 via self upgrade

Hi, this is because of a bug in the upgrade, where a json file is downloaded instead of the binary
This is in fact a duplicate of #2516, we will continue the debug there :+1:


style: dynamic css parts

Description

Right now CSS parts define the styles of all the components exposed with that CSS part. Make extra CSS parts to pinpoint the CSS with some identifier or maybe by some other better method.
Possible solution(s)

Additional context

just to get a little more context, are we talking about user defined css parts so users can target elements like they would with classes in css?

Maybe we can just add a customPart key so the package developers can specify that where they need to and have only as many parts as they can handle, and even group fields together if they want to. I think this will be more efficient unless what we're worried about is the accessibility of these parts for those that will be using the packages (excluding design)
In addition I was also considering some sort of depth based targeting for styling. It would still be considered general but it would let developers target fields based on their depth, this could also limit the number of custom parts they would need to specify. What do you think?


SSL Not working

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
<EMAIL_ADDRESS>Hello guys! Ur SSL is not working so my clients websites have destroyed styling. How long will it take to solve that?
Reduced test cases
SSL time expired
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
5.2.2

I see now it works but my websites are marked as unsecure

It seems to be related to this issue: https://github.com/jsdelivr/jsdelivr/issues/18565

Use this<EMAIL_ADDRESS>

Same here, I wonder when it will be fixed

Hello there,

Ur SSL is not working so my clients websites have destroyed styling. How long will it take to solve that?

jsdelivr is not maintained by Bootstrap team. As mentioned by @yeinahn, it seems to be related to https://github.com/jsdelivr/jsdelivr/issues/18565. You can enable the notifications to check whenever it'll be fixed on their side. On our side, I'm going to close this issue since there's nothing to do.
In the meantime, if technically possible for you, you could switch to alternative CDNs such as cdnjs or unpkg.
As mentioned by @Curo-Dev, it may be possible to switch to fastly.jsdelivr.net or gcore.jsdelivr.net too. Some folks in the jsdelivr thread seem to say that it's working.

Is there an official CDN version instead of jsdelivr ones?


Infinite scroll is not working with zoom out.

So, when you zoom out to certain point, depending on the amount of items displayed. The infinite scroll won't be triggered ever.

is also happens if the height of the window is too large and the initial data is not enoght to fill the window, then the data is never loaded, its only shows the loading... param

i came here with this issue.  if your first load doenst generate a scrollbar,  what do you do?

I have the same issue,
If you change in the example code from 20 div to 5, it will never load the data...
https://codesandbox.io/s/wandering-worker-6iyj0
https://codesandbox.io/s/ecstatic-dream-iy5sz

Has anyone figured out a reasonable solution to this?

Hi is there any solution for this


Auto argument

Is not documented the utility of using auto and the effect with other arguments as setting the bases

Does anyone know what is the purpose of it ?
Reading the source code I think that it raises a service for each item on the listen array, but I'm not sure of the advantage of this. In fact, all services try to start on the same port, so they fail. This has been a headache for me until I discovered.

It just automatically calls the listen function with the arguments provided. Otherwise you need to do it by yourself.
@danielo515 How are you configuring your listen? If you set the same port on all your services in dev environment it's going to fail, because (most probably) all are running on localhost. If you leave it empty though, mesh is going to run each in a random port.
https://github.com/senecajs/seneca-mesh/blob/master/mesh.js#L185
To make sure, that's how I configure my mesh listen:
    listen: [{
      pins: [ ......... ],
      port: process.env.PORT || 50000 + Math.floor((10000 * Math.random()))
    }]

Hello @otaviosoares ,
The configuration you posted is the fourth ? fifth ? configuration version that I saw that is not documented and works. Seems that any crazy combination except what it is documented works fine.
To be honest, I started using listen as documented, but that ended on a Die Count error as has been reported on other issue. Then I started to make all kind of crazy combinations:

Using just pins with an array of jsonic strings at the root of the mesh config
Using pin when it is a single string and pins when they are many at the root of the mesh config
Using a listen array of one single element where pin is a list of jsonic strings

The only option that does not work is providing a list property containing an array of objects with a single pin per object, and not specifying any port.
Just for the shake of trying I'll check it again, to see what happens.
Something very important that is not documented neither is that each listen element is directly passed to seneca.listen, so you can use any option that seneca listen accepts, that could be pretty handy.

Hello again,
I just tried again after reading the source code more carefully and I ended with a configuration that works. Here is an example of what I got:
 Mesh options: { listen:
    [ { pin: { role: 'profile', cmd: '*' } },
      { pin: { role: 'profile', cmd: 'probes.get' } },
      { pin: { role: 'profile', cmd: 'campaigns.get' } },
      { pin: { role: 'profile', cmd: 'universes.get' } },
      { pin: { role: 'profile', cmd: 'probes.del' } },
      { pin: { role: 'profile', cmd: 'campaigns.del' } },
      { pin: { role: 'profile', cmd: 'universes.del' } } ],
   auto: true,
   isbase: false,
   port: '0',
   bases: [ '<IP_ADDRESS>:39999', '<IP_ADDRESS>:39001' ],
   stop: false,
   balance_client: { debug: { client_updates: true } },
   jointime: 2000,
   sneeze:
    { silent: true,
      swim:
       { interval: 1111,
         joinTimeout: 2777,
         pingTimeout: 2444,
         pingReqTimeout: 2333 } },
   discover:
    { rediscover: true,
      custom: { active: true, find: [Function: dnsSeed] },
      multicast: { active: false },
      registry: { active: false } } }

However, with this new configuration the routing options has changed drastically. Before this is what I was getting:
IN  000010: { role: 'mesh', get: 'members' } # s1jz42gyxa22/uv32kn1gn5by get:members,role:mesh get_members_34 undefined
OUT 000010: { list:
   [ { pin: [ 'cmd:test,role:mesh' ],
       port: 59371,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: 'iws4znzlamoc/1529998816867/92301/3.6.0/base0' },
     { pin:
        [ 'cmd:*,role:profile',
          'cmd:probes.get,role:profile',
          'cmd:campaigns.get,role:profile',
          'cmd:universes.get,role:profile',
          'cmd:probes.del,role:profile',
          'cmd:campaigns.del,role:profile',
          'cmd:universes.del,role:profile' ],
       port: 56688,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '6tw2cbl9oece/1529999007058/92523/3.6.0/profiles' } ] }

But now each command is turned into a "host"
IN  000000: { role: 'mesh', get: 'members' } # 68b9m47zl66b/k9a3z18u8wn8 get:members,role:mesh get_members_38 undefined
IN  000001: { role: 'mesh', get: 'members' } # sogsu97hm7ol/k9a3z18u8wn8 get:members,role:mesh get_members_34 undefined
OUT 000001: { list:
   [ { pin: [ 'cmd:test,role:mesh' ],
       port: 58494,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: 'ug5j45ydwpid/1529999093005/92557/3.6.0/base:repl' },
     { pin: [ 'cmd:*,role:profile' ],
       port: 59306,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '9n5lbw9cfz1m/1529999092982/92556/3.6.0/profiles' },
     { pin: [ 'cmd:test,role:mesh' ],
       port: 57211,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: 'fx0iv8srpdtp/1529999092977/92555/3.6.0/base0' },
     { pin: [ 'cmd:probes.get,role:profile' ],
       port: 59648,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '9n5lbw9cfz1m/1529999092982/92556/3.6.0/profiles' },
     { pin: [ 'cmd:campaigns.get,role:profile' ],
       port: 57782,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '9n5lbw9cfz1m/1529999092982/92556/3.6.0/profiles' },
     { pin: [ 'cmd:universes.get,role:profile' ],
       port: 50790,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '9n5lbw9cfz1m/1529999092982/92556/3.6.0/profiles' },
     { pin: [ 'cmd:probes.del,role:profile' ],
       port: 57608,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '9n5lbw9cfz1m/1529999092982/92556/3.6.0/profiles' },
     { pin: [ 'cmd:campaigns.del,role:profile' ],
       port: 51346,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '9n5lbw9cfz1m/1529999092982/92556/3.6.0/profiles' },
     { pin: [ 'cmd:universes.del,role:profile' ],
       port: 50809,
       host: '<IP_ADDRESS>',
       type: 'web',
       model: 'consume',
       instance: '9n5lbw9cfz1m/1529999092982/92556/3.6.0/profiles' } ] }

I did not included it, but the answer is duplicated, seems that every base on the mesh is answering hence the duplicated response.
I don't know what is better in terms of routing, but I suppose that it is better to just have one port open per host.

@danielo515 Mesh with auto: true calls listen on each object of you listen array.
If you want to have just one port open then just make it
 Mesh options: { listen:
     [ { pins: { role: 'profile', cmd: '*' },
          { role: 'profile', cmd: 'probes.get' },
          { role: 'profile', cmd: 'campaigns.get' },
          { role: 'profile', cmd: 'universes.get' },
          { role: 'profile', cmd: 'probes.del' },
          { role: 'profile', cmd: 'campaigns.del' },
          { role: 'profile', cmd: 'universes.del' }],
   auto: true,
  ...
}

Instead of
 Mesh options: { listen:
    [ { pin: { role: 'profile', cmd: '*' } },
      { pin: { role: 'profile', cmd: 'probes.get' } },
      { pin: { role: 'profile', cmd: 'campaigns.get' } },
      { pin: { role: 'profile', cmd: 'universes.get' } },
      { pin: { role: 'profile', cmd: 'probes.del' } },
      { pin: { role: 'profile', cmd: 'campaigns.del' } },
      { pin: { role: 'profile', cmd: 'universes.del' } } ],
   auto: true,
  ...
}

Thank you very much @otaviosoares ,
I tried that previously and it resulted on a Die Count error, but maybe it was because any other problem.
Sorry for hijacking this thread, which is about documenting the auto param.

One more question,
If you want to specify different methods (observe, consume...) you need to specify different pines, which will be attached to different ports. There is no other way right ?


Click on Create Order to navigate to New Order Page

When user, clicks on Create Order button...

[x] Navigate to New Order Page

[x] New Order Page should contain the following fields...

[x] Dropdown for LaundryType (Wash, DryClean, Ironing, Wash + Ironing)
[x] Textbox with ClothType (Shirt, T-Shirt, Trouser, Dress, Sari, Other)
[x] Input field for quantity
[x] Input field for User Information (Customer Name)
[x] Input field for User Information (Customer Phone)
[x] Input field for User Information (Customer Address)

[x] After Order is Created, user should get the following information on the screen...

[x] Order Id
[x] Order Status [Pending, Confirmed, In Progress, Completed]

[x] By default, all new orders will be in Pending state

[x] Order Details
[x] Order Completion Date [TodaysDate + 3days]

Tech Specs

[x] Create View
[x] Create Order Controller
[x] Create Order Model
[x] Create Database


Vulnerability roundup 81: qemu-4.0.1: 1 advisory

search, files

[ ] CVE-2019-20175 CVSSv3=7.5 (nixos-19.09)

Scanned versions: nixos-19.09: eb65d1dae62. May contain false positives.

CVE is disputed


RDWebClientManagement now requires -AcceptLicense parameter to install

RDWebClientManagement now requires -AcceptLicense parameter to install

@jimitkg : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Linux Bug

If you are using the standalone 64 bit and try to move an ticket to a different column it wont work or show any reaction.
Linux Ubuntu Wine

Checked it with mono again and it works under deepin


1st commit: add Young to members

Add my name and picture to About page as members.
I am excited to be added to this group.

Hey @Hogusong
Great first PR!
At OpenForge we've been practicing a commit method called commitizen, which is super awesome for helping to format commit messages (that way everyone is consistent and having the same styles of commit messages).
Whenever we have work locally that we want to commit, we run the standard git add .. then execute npm run cz which will run through prompts within terminal. Once that is finished you can execute git push and it will push the commit message that you previously formed with the prompts!
If you need more information on this let me know. Feel free to check out the commits in this repository for examples for the future.
If you could please update the base branch (it is currently master) to develop then a developer will review, test, and see if we can get this merged in and closed out. You can edit the base branch by clicking the edit button on the right-hand side by the PR name up at the top of this view.
If you have questions at all feel free to message me on slack :)
Thanks!

Hey Paulina,
Thank you for your feedback.
My first day in OpenForge was great.
I updated the base branch to develop and I did a PR last night again. Would
you tell me what I did OK or wrong?
Have a great day.
Young
On Mon, Oct 15, 2018 at 4:47 PM Paulina Gallo<EMAIL_ADDRESS>wrote:

Hey @Hogusong https://github.com/Hogusong
Great first PR!
At OpenForge we've been practicing a commit method called commitizen
https://github.com/commitizen/cz-cli, which is super awesome for
helping to format commit messages (that way everyone is consistent and
having the same styles of commit messages).
Whenever we have work locally that we want to commit, we run the standard git
add .. then execute npm run cz which will run through prompts within
terminal. Once that is finished you can execute git push and it will push
the commit message that you previously formed with the prompts!
If you need more information on this let me know. Feel free to check out
the commits in this repository for examples for the future.
If you could please update the base branch (it is currently master) to
develop then a developer will review, test, and see if we can get this
merged in and closed out. You can edit the base branch by clicking the
edit button on the right-hand side by the PR name up at the top of this
view.
If you have questions at all feel free to message me on slack :)
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openforge/OPENFORGE.IO/pull/249#issuecomment-430007273,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AX82n9n7rhzG6ueoy3UHzESbyq6Zf7Ylks5ulPRcgaJpZM4XdCiy
.


[Plugin] CycloneDX SBOM

Suggesting a plugin to display a CycloneDX Software Bill of Materials (SBOM) Composition Report. CycloneDX is a commonly used standard across a number of tools that supports both JSON and XML schemas.
CycloneDX is the SBOM format created by the Open Web Application Security Project (OWASP) and was built with cybersecurity in mind. The largest benefit of CycloneDX is the ability to include vulnerability information in the SBOM or link to a separate Vulnerability Exploitability Exchange (VEX) which lets you indicate false positives alongside component vulnerability information. The schema also supports  a Package URL (PURL) which standardizes how software package metadata is represented so that packages can universally be located regardless of what vendor, project, or ecosystem the packages belongs to.

Thinking the plugin will work similar to the dependency-track plugin
metadata:   annotations:     backstage.io/sbom: enabled
A tab called SBOM to be shown at the component, system and even resource level with sub tabs with the SBOM provider name i.e Sonatype, syft or any tool that supports the Cyclone specification standard.

https://github.com/CycloneDX/cyclonedx-javascript-library/discussions/215
Unfortunately i don’t have time to contribute right now but wanted to throw the idea out there and get feedback from the community!

any one wants to take a stab at this?

any one wants to take a stab at this?

Hi @testn this is currently open for grabs, would you like to be assigned?
Unfortunately, I don't have the time at the moment, just wanted to throw the idea out there to see if there was any interest/feedback.
Docker now actually has a sbom plugin that generates a CycloneDX SBOM in JSON. Felt this plugin would come in handy to visualize the SBOM report at the component level.

Hi there.
I am the author of https://github.com/CycloneDX/cyclonedx-javascript-library
Feel free to reach out to me if you need something regarding the library, or just want to chat about CDX in general.
If you want to use custom properties in CycloneDX, then you might want to register your namespace here: https://github.com/CycloneDX/cyclonedx-property-taxonomy/

I did some work on a proof-of-concept CycloneDX plugin back in early 2022 before much tooling existed for CycloneDX, I'll see what I can contribute back and if it's still relevant but my approach/ideas on a plugin can be summarised below:
SBOMs are living documents that should be updated regularly, so they should be linked to rather than captured within a component yaml.
They could be stored within a repository such as https://github.com/CycloneDX/cyclonedx-bom-repo-server or potentially within VCS alongside the code, For my initial attempt I just got it working with harvesting from Git using the default URLReader and relying on the established auth mechanism.
I added a tab on each software component page to summarise some of the information contained within an SBOM, e.g. loop through the dependencies and list the number of each license within the SBOM etc, but with the CycloneDX library mentioned there could be a more informative/browsable UI.
Some inspiration for the UI could be taken from plugins like https://github.com/backstage/backstage/blob/master/plugins/fossa/README.md or https://github.com/snyk-tech-services/backstage-plugin-snyk/blob/main/README.md as similar information may be contained in the SBOM.

I did some work on a proof-of-concept CycloneDX plugin back in early 2022 before much tooling existed for CycloneDX, I'll see what I can contribute back and if it's still relevant but my approach/ideas on a plugin can be summarised below:
SBOMs are living documents that should be updated regularly, so they should be linked to rather than captured within a component yaml.
They could be stored within a repository such as https://github.com/CycloneDX/cyclonedx-bom-repo-server or potentially within VCS alongside the code, For my initial attempt I just got it working with harvesting from Git using the default URLReader and relying on the established auth mechanism.
I added a tab on each software component page to summarise some of the information contained within an SBOM, e.g. loop through the dependencies and list the number of each license within the SBOM etc, but with the CycloneDX library mentioned there could be a more informative/browsable UI.
Some inspiration for the UI could be taken from plugins like https://github.com/backstage/backstage/blob/master/plugins/fossa/README.md or https://github.com/snyk-tech-services/backstage-plugin-snyk/blob/main/README.md as similar information may be contained in the SBOM.

@DJDANNY123 Would love to see what you built so far, I agree that sboms are living/always changing documents and pulling from git is definitely a great start, given sboms are generated during build time, was thinking it would great to be able to post the sbom report similar how the code-coverage accepts a coverage report.

Had a meeting yesterday to progress getting permission from third party to open source this. Waiting for formal confirmation from them to release it.
That being said I think I would want to rewrite some of the work I did to use the library above to process the SBOM rather than manually decode it using the JSON schemas etc.
I was also returning the entire SBOM to the front-end which is probably not the approach I'd like to take, as it would be good to process that on the backend and then return the extracted information on the frontend, or get data from a report as well as a raw SBOM, do you have an example of any existing SBOM report data structures?

Agreed, here are some SBOM sample reports
The cyclonedx-javascript-library](https://github.com/CycloneDX/cyclonedx-javascript-library) also has a example of how to serialize a SBOM to JSON here
Let me know if you would like to be assigned to this one!

Ah maybe I misunderstood the terminology of 'report', I was viewing there would be a raw SBOM which is based on the CycloneDX standard, or a 'report' which contains a more minimal representation of the information contained within this, such as a list of licenses, vulnerabilities etc.
I was thinking the backend component would retrieve a full CycloneDX SBOM and process this in the backend to a more minimal JSON structure or 'Report' that provides information extracted from the SBOM (e.g. metadata, list of contained licenses, vulnerabilities etc.) to be displayed in Backstage in addition to a link to the raw SBOM.
I don't know if there are other services that produce/expose the processed information from an SBOM or a format around this which we could also use, but maybe thats beyond the scope of a CycloneDX plugin.

Agreed, here are some SBOM sample reports @jkowalleck would you happen to have any samples using the latest 1.4 spec?

There are more on the official documentation and website: https://cyclonedx.org/use-cases/
Examples might be nice, but you should study the spec - https://github.com/CycloneDX/specification/tree/master/schema

I don't know if there are other services that produce/expose the processed information from an SBOM [...]

You might connect with the CycloneDX community and check what others were already doing.
Or ask them for SBOMs they've created.

join the slack: https://cyclonedx.org/slack/invite
join the group: https://groups.io/g/CycloneDX

if it might help you, there is now a list of CycloneDX guides : https://cyclonedx.org/guides/

Maybe SPDX support is also important. If SPDX support is somehow easier to get, I'd be happy to have it first.

Regarding the storage location for the SBOM (in CycloneDX, SPDX or any other format), it could make more sense to store it as an OCI artifact alongside the container images (ORAS can be used to attach supply-chain artifacts to container images).
Indexing all SBOMS would also be great for searching.


refactoring code and design improvements

Signed-off-by: Sri Aspari<EMAIL_ADDRESS>

Sure. but what should i do?
Should I push the most recent commit or maybe there is another way to do this?
I've never experienced this. so, i don't know what to do.

@siarie Just write it and commit then force push

Merged, thanks @siarie.

What's wrong with my setup?
The live site doesn't show it correctly.
See: https://www.gnuweeb.org/

@ammarfaizi2 Refresh cache?

I did, how is the view from your device @irvanmalik48?

i don't know why. but it doesn't display it correctly in my browser too.

it doesn't show up properly for me either

@Sprtcrnbry same here

I am revoking cache from Cloudflare

It should be fine now, please proceed hard reload from your browser.

I put it under development mode. So it will temporarily bypass cloudflare cache and allowing us to see changes from origin server in realtime.


updates url to use url-template-tag.

I think this will do what you want.

Yes! Talk about not seeing the trees for the forest.


Patch 1

fix a few typos

Internal previews

📄 File
🔗 Preview link

docs/csharp/language-reference/operators/member-access-operators.md
Member access operators and expressions - the dot, indexer, and invocation operators.

docs/csharp/programming-guide/classes-and-structs/using-properties.md
"Using Properties - C# Programming Guide"

@microsoft-github-policy-service agree

closing and reopening to ping the CLA bot again.

@lemonez
For dotnet docs, it's a different CLA bot ID. It should be "dotnet-policy-service".
Sorry about that.

@microsoft-github-policy-service agree

@dotnet-policy-service agree


Fix invalid abstract service factory configuration

This fixes #129.
Registration of InputFilterAbstractServiceFactory is currently invalid in ConfigProvider. Instead of the abstract_factories key being nested under dependencies it should be nested under input_filters.
This pull request corrects the behaviour and allows using the service with no manual changes required when using the library in a Zend Expressive project.

[x] Are you fixing a bug?

[x] Detail how the bug is invoked currently.
[x] Detail the original, incorrect behavior.
[x] Detail the new, expected behavior.
[x] Base your feature on the master branch, and submit against that branch.
[ ] Add a regression test that demonstrates the bug, and proves the fix.
Is this really needed? I've included tests that validate the current (correct) behaviour.
[x] Add a CHANGELOG.md entry for the fix.

@webimpress Sorry, not sure what you meant. Is something wrong with the config?

@codeaid Documentation says that you have to add it manually in your configuration when you using zend-mvc v2. With v3 or expressive the configuration is slightly different and your change is not needed, imho.

Documenation says "when using the configuration manager [..] the functionality is enabled by default" - I registered ConfigProvider in my Expressive application (installed using the instructions on the project homepage) and I wasn't able to use the abstract factory. How does it get enabled by default then?

Ah, I thought I was going crazy for a moment! Glad I can be of help after all.
I force-pushed the updated link in the changelog to avoid duplicate commits. Everything should be alright now.
On a side note - would you want me to fix this issue in zend-form too  while I'm at it, @froschdesign?

Thanks, @codeaid!

Thanks, @weierophinney! Sorry, I haven't had time to fix this issue in zend-form. Been busy with things other than PHP.


Include source gene ID in drug, gene claim

It's currently provided (inconsistently) as an alias - if it's available, it might be important for the frontend in a few ways, and including it with the claim obviates the awkward regex/search through associated aliases

[ ] Also drugbank isn't pulling the gene ID (eg 'BE0000048') currently

I thought about this more and I don't think it's actually necessary, but we can revisit later


Sample missing

It would be great to see a sample PS script. Stuff like passing variables would be great!

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

ID: fb215324-b1a0-93b5-5022-4bcc7da93bb7
Version Independent ID: 9eb2977b-ac34-9d53-670e-04fa027bc8e4
Content: Azure PowerShell task - Azure Pipelines
Content Source: docs/pipelines/tasks/deploy/azure-powershell.md
Product: devops
GitHub Login: @steved0x
Microsoft Alias: dastahel

+1

Still no example?


feat(CHANGELOG): generate crate changelogs

Feature or Problem
This PR uses cargo-changelog to generate changelogs for our crates.
Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

@vados-cosmonic great question! Honestly I did it because it's the underlying tool under https://github.com/Byron/cargo-smart-release/pull/17#issuecomment-2079727056, (linked to PR where I'm adding something but the tool is cargo-smart-release) so I was hoping to keep the tools consistent since hopefully I'd be able to use that tool to release in the future! Definitely happy to consider alternatives too


Some print about eggs remaining distance

Hello,
Thank's for your work, the best one and using python (the best language for this kind of bot i think).
Could you add some prints allowing us to see the remaining distance of our eggs ?
I still don't know if we can see when we got the pokemon in and when the bot incubates an egg but just a simple detail of our eggs could be great (and kinda simple).
Thank's a lot.

[18:56:17]  Exchanging Zubat [CP 284] [Potential 0.53] for candy!
__[18:56:33]  [x] Next egg incubates in 0.25 km __
[18:56:43] Walking from (47.3729359, 8.5480928) to [47.3729359, 8.5462928] 0.14km
Bot actually does it.

Ooh great. Sorry. My bad.
Good to know :D

/close maybe?


Logically separate out parser to its own package for import of metric, event, and service check message parsing

What does this PR do?
Moves the parser logic into its own sub-dogstatsd package and makes the following functions exportable:

NextMessage(packet *[]byte) (message []byte)
ParseServiceCheckMessage(message []byte, defaultHostname string) (*metrics.ServiceCheck, error)
ParseEventMessage(message []byte, defaultHostname string) (*metrics.Event, error)
ParseMetricMessage(message []byte, namespace string, defaultHostname string) (*metrics.MetricSample, error)

...which are called by the dogstatsd server.
Motivation
Mainly, so we can call the parsing functions without having to pull in the server/listener weight. It can also be advantageous in the future should there be different implementations of the dogstatsd server: it'd be able to call the same underlying parsing funcs without duplicating code.
Also, the separation also seems cleaner/logical for hopefully improved maintainability.
Additional Notes
Please note, I did not update releasenotes (per contribution guidelines) as there is no change to the end-server, just code layout. In case I should, please let me know and I'll update the PR.
Go Test Results
server_test.go
[~/go/src/github.com/DataDog/datadog-agent/pkg/dogstatsd] $ go test
Error: Dogstatsd: error parsing metrics: invalid metric value for "daemon1:666:777|g"
Error: Dogstatsd: error parsing service check: invalid field number for "_sc|agen.down"
Error: Dogstatsd: error parsing event: Invalid event message format: empty 'title' or 'text' field
PASS
ok  	github.com/DataDog/datadog-agent/pkg/dogstatsd	0.365s

parser_test.go
[~/go/src/github.com/DataDog/datadog-agent/pkg/dogstatsd] $ cd parser/ && go test
PASS
ok  	github.com/DataDog/datadog-agent/pkg/dogstatsd/parser	0.008s

Hi @schahal, thanks for opening this PR, and sorry we failed to respond earlier.
I see the related issue on telegraf has been closed, so I don't know if your PR is still something you'd want to see merged. In addition, a few things were refactored/moved in the dogstatsd package since you opened your PR so I don't think it'll be easy to rebase and update. So I'll go ahead and close your PR, but if this something you're still interested in feel free to follow up here, thanks!


Circuit superoperator

Compatible with the protocol defined in #4545.
Follow-up: cirq.superoperator_to_kraus which will enable the computation of Kraus representation of small noisy circuits.

Extracted the nested functions and made them methods in Moment.
Considered the other einsum API, but it leads to more complicated code since it expects the index lists to be interspersed between arrays.


Add event logs deletion with filters

While the event log list allows you to delete events in a bulk fashion by filtering the list with a keyword, then selecting all the events and clicking on the "Delete selected" button, if the log includes more events responding to the query than the list can display, you need to repeat the action several times to delete all the events.
This PR provides a new button to display a pop-up window to the user, allowing him to enter a search term and date range to obtain the set of events matching the criteria, which will be deleted after confirmation.

@damsfx what do you think about instead adding date filters to the list itself and then making a PR to add support for a special "select all" mode that allows you to select all records that match the current query (like gmail has)?

Could even make the select all text even more useful by adding a count to it ("Select all records that match this search (402)")

@LukeTowers This would be a good improvement for the event manager and certainly the best UI/UX.
My tests in this direction are meeting several challenges:

The list search field is too generic and searches the different model properties.
The search field doesn't allow searching for special characters like %.

In addition, for the selection of items not displayed in the list, what do you think is the best solution for adding these capabilities to the controller?

Add them to BackendBehaviorsListController.
Create a new type of list controller
Add them only to Backend\Controllers\AccessLogs.

The search behaviour can be configured by setting searchable: false on columns that you don't want to be searched on.
I'd prefer the expanded selection logic to be added to the ListController behavior, it would be useful in pretty much every list.


KWin Windowrules

Hi
would it be in scope to implement a highlevel module for kwinrulesrc?
So that you can more easily generate those.

Thanks for the suggestion. I think implementing a module for this makes sense. I'll probably do it when I get some more time (the reason I haven't implemented it already is because I don't really use them personally)

Thanks for the suggestion. I think implementing a module for this makes sense. I'll probably do it when I get some more time (the reason I haven't implemented it already is because I don't really use them personally)

Then I will try to implement them my self an make an PR. This will probably take a bit of time.

I think #199 closes this?

Yeah you are right @ugur-a. I'll close now as it's implemented.


[Improvement]: Terminal improvements

Description
Note: The terminal is not added at the moment but will be soon: https://github.com/coollabsio/coolify/pull/2586
Minimal Reproduction (if possible, example repository)
Some improvement ideas for the terminal system could be:

[ ]  A full log of all the commands we have run in the terminal (with automatic log rotation and deletion) -> So we can keep track of what we have run on our system.
[ ]  A snippet store -> so we can store most used commands as snippets and easily execute them with one click (not have to retype them every time) -> For example docker system prune on the server
[ ]  Run commands on multiple containers at the same time -> could be achieved with the tags system --> But maybe not that smart for security?

Exception or Error
No response
Version

Oh I can see more clearly now about these ideas.
About number 3, If I understand correctly, this could be some kind of Cron system right? Like, setup some bash scripting or whatever, and run it periodically or by startup button

Oh I can see more clearly now about these ideas.
About number 3, If I understand correctly, this could be some kind of Cron system right? Like, setup some bash scripting or whatever, and run it periodically or by startup button

Yes. Also for 3, when you add tags, there is a way to re-deploy all containers with those tags, maybe the tags functionality can be leveraged for terminal as well.


Data Question

How can I learn from a tif file in Change detection? The directory configuration is the same, but it is a tif file, not a png file.

@chartgod I can't understand what you say, may be you can transform tif to png


(fix): Universal Frameworks target membership of OPTLYNSObject+Validation.

Summary
The current universal frameworks miss the symbols defined in OPTLYNSObject+Validation. This includes the category method on -[NSObject getValidString]. This PR fixes that issue.
Test plan
Follow the Manual Install instructions and attempt to track an event.

Coverage remained the same at 98.142% when pulling 5ae32f62cf41954cd8e02ef1b5b0a551f8751eec on yasir/fix-target-membership into 0e2f2bf563c58301bed0c3e675a5b4014c06e844 on master.

Coverage remained the same at 98.142% when pulling 5ae32f62cf41954cd8e02ef1b5b0a551f8751eec on yasir/fix-target-membership into 0e2f2bf563c58301bed0c3e675a5b4014c06e844 on master.


Response body is not closed after retries, and possibly after a 5xx error

For the client as well as the hystrix client, the response body is not closed before the next retry.
If the HTTP status code is >= 500, the client returns an error. This may lead developers to not close the response body on their end.

(1) is pretty straightforward to fix (close the body before the next retry)
For (2) we need to decide whether to send an error for 5xx http status codes. If we decide to omit the error, this would lead to a change in contract, and we would potentially have to bump the major version

@sohamkamani Thanks for the PR on this issue.
Have merged it.
For 2, can't we close the response body within the client, like if err is present so close it ?


Progress information?

As I complete levels, I see my count of stars go up, but I think it would help my sense of progress if there was a list of previously completed levels and I could view the solutions I did for each one

👋 @glenjamin !
That’s something I’ve been thinking for a while.
My initial idea for this game was to actually show the entire progress in the main screen, but from the initial feedback nobody was “that” interested, so I went for the current approach.
One think that was suggested on Hacker News is to create a new screen that shows the current progress, available by tapping on the score/star at the top right of the main menu. What do you think about idea?
Any other ideas?

@glenjamin just added a "Statistics" screen, see #16
It's not the best solution to the issue, but we can use it as a starting point :)


fix bug for YAML.load

Closing due to a lack of activity. If there is a problem, I think a bug should be opened so that we can discuss the best solution (eg, see my notes above).


Auto file mode for SFTPStream.createWriteStream?

I use createReadStream/createWriteStream to download/upload, I find that when remove mode option, download process will be smart auto: when overwrite, keep local file's mode, if no overwrite, use remote file's mode, but for upload process, this do not work like that, if no mode setting in options, it will always be 0o666.
Just wondering that could SFTPStream.createWriteStream be that smart? or I missed something?
  let option = {mode}
  let readSteam = type === 'download'
      ? sftp.createReadStream(remotePath, options)
      : fs.createReadStream(localPath, options)
    let writeSteam = type === 'download'
      ? fs.createWriteStream(localPath, options)
      : sftp.createWriteStream(remotePath, options)

sftp.createWriteStream() intentionally works the same way as fs.createWriteStream(), which is if you don't specify a mode option it will default to 0o666.
For the opposite (remote -> local), there is no way that node magically knows what the remote file mode was unless you explicitly provide it as they (sftp.createReadStream() and fs.createWriteStream()) are just streams of file data. The fact that it may be working as you expect without a mode set is just coincidence.

@mscdex Thank you!


Added type, data, and options getters from Chart.js Model

Q
A

Bug fix?
no

New feature?
yes

Tickets
Fix #34

License
MIT

Added getters for 'data', 'options', and 'type' for the Chart.js model
See #34

Thank you @bastien70.


Couldn't create candlesticks due to a database error

On first install this happens.
MongoError: Write batch sizes must be between 1 and 1000. Got 5176 operations
   at Function.MongoError.create (/Users/frankenmint/Desktop/sideprojects/BitBot/node_modules/mongodb-core/lib/error.js:31:11)
I could go into the mongodb-core dir but that doesnt seem right.
Googling around I find that this thread mentioned that mongo-db has a 1000 writes limitation (this makes me suspect that I could modify your files somewhere to account for the candlestick data to write in)

Pushed an updated that should store data in chunks of 1000.


Add Ripae pools on Avax

forgot addressbook

forgot addressbook

I will add them along the next PR on Avalanche, if that's ok :+1:

need them asap

need them asap

https://github.com/beefyfinance/beefy-api/pull/654


[REVIEW] krshkun

GitHub Profile Link
@krshkun

Reviewed on live stream https://www.youtube.com/watch?v=9pXcE3-WnkA


refactor: Clientbuilder accept backoffconfig

Describe your proposed changes here.
This changes will allow users to configure backoff/retry to their liking. This is also one of a 2 part changes (other still in progress) in an attempt to also allow a form of termination and not try forever especially without informing the user of the progress.

[x] I've read the contributing section of the project CONTRIBUTING.md.
[x] Signed CLA (if not already signed).

Thank you.


Document data_gen.py

Write documentation for the Data Generator data_gen.py

Hey, can you tell me what kind of documentation you specifically want for data_gen.py? Is it more so how the code itself works?

Hey @Donoven-Lam
Yeah Just add a small documentation which describes what the generator code does and
Instructions on how to capture images and save them

@Donoven-Lam Are you interested in working on this Issue?

Yes, @AnsahMohammad I'm still interested in working on this issue. I'll try to get it done by tonight/tomorrow. Apologies for the delay.


No streams.json file exist by default in the identity-anonymization-tool

Description:
streams.json file[1] doesn't exist by default in the identity-anonymization-tool.
[1] https://docs.wso2.com/display/SP4xx/Removing+Personally+Identifiable+Information+via+the+Forget-me+Tool#RemovingPersonallyIdentifiableInformationviatheForget-meTool-Step1:Configurethestreams.jsonfile
Affected Product Version:
wso2sp-4.0.0-update9

This section was updated as follows to mention that the file needs to be created by the user.
"In order to identify the streams and the stream attributes with PII, you need to create this file with definitions of the relevant streams and each attribute that contains PII (Personally Identifiable Information). This file must be placed in the <SP_HOME>/wso2/tools/identity-anonymization-tool-x.x.x/conf directory. "

For SP we don't have persisted streams therefore no need of streams.json. Updated the doc in this regards.

Verified with RC2


Subaru: use torque controller

[ ] CAR.ASCENT
[ ] CAR.IMPREZA
[ ] CAR.IMPREZA_2020
[ ] CAR.FORESTER

@michaelhonan Hey, do you have an Impreza to test?

@michaelhonan Hey, do you have an Impreza to test this?

Yep! Will do 👍

@michaelhonan Hey, do you have an Impreza to test this?

Works well. Much more stable than current upstreamed pid.
dc30ef2ad294a732|2022-08-02--12-20-29
Commit used:
https://github.com/michaelhonan/openpilot/commits/subaru-torque

Tested on a 2018 Crosstrek Limited: 6f35adacf2529520|2022-08-03--04-07-46--0
As Michael mentioned above, works well and definitely an improvement over the previous controller. However, I am still having issues turning on many freeway curves and hitting the max steer limit, which I believe is a known issue for 2017-2019 Impreza/Crosstrek models. Here's a sample: 6f35adacf2529520|2022-08-03--04-07-46--13

Holding off until we can really make the experience great with #25456


Optimize storing fill_value to Array

Would be nice if when storing a scalar or an array that contains only the fill_value of the Array, the chunk is merely deleted (if it exists) instead of writing out a chunk that contains only the fill_value for all elements. The Array should behave identically in either case. The only benefit is that storage is cutdown automatically in this case. A situation where this may come up is when copying one Array to another.

A rough attempt at solving this is in PR ( https://github.com/zarr-developers/zarr/pull/367 ).


Add a spec to be sure migrations will be run in order on upgrade

If two migrations are added which add columns on the same table, and only the later one gets into a release, migrations to the next release will have the columns in the reverse order when compared with newly created appliances or databases migrated from scratch.
This spec tests that no migrations which are not in the list of released migrations have a timestamp earlier than the latest released migration. If this happens, the developer has to regenerate the migration so that everything will run in the proper order.
This will help prevent us from getting into the situation which caused https://bugzilla.redhat.com/show_bug.cgi?id=1331114
@gtanzillo @Fryguy @bdunne @chessbyte

The output from a failure will look like:
Randomized with seed 28267
F

Failures:

  1) migration order is correct
     Failure/Error:
           expect(incorrect_migration_time_stamps).to be_empty, <<-EOS.gsub!(/^ +/, "")
             The following migration timestamps are too early to be included in the next release:

             #{incorrect_migration_time_stamps.join("\n")}

             These migrations must be regenerated so that they will run after the latest
             released migration, #{last_released_migration}.

             This is done to prevent schema differences between migrated databases and
             newly created ones where all the migrations are run in timestamp order.

       The following migration timestamps are too early to be included in the next release:

       12345
<PHONE_NUMBER>3456

       These migrations must be regenerated so that they will run after the latest
       released migration,<PHONE_NUMBER>4542.

       This is done to prevent schema differences between migrated databases and
       newly created ones where all the migrations are run in timestamp order.
     # ./spec/replication/util/migration_order_spec.rb:26:in `block (2 levels) in <top (required)>'

Finished in 0.50689 seconds (files took 5.96 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/replication/util/migration_order_spec.rb:20 # migration order is correct

Randomized with seed 28267

So it looks like those migrations are causing the following few to fail this test:
20160414123914_add_filters_to_entitlements.rb
20160414124134_move_filters_to_entitlements.rb
20160414132130_remove_filters_from_miq_groups.rb
Not sure how to handle this ...

@chrisarcand Can you check to make sure that moving these migrations doesn't cause any issues?

@carbonin Entitlement filters should not be included in the Darga release.

This PR won't backport them, it just changes the timestamp.  If the spec needs to be backported it will have to be an unclean cherry-pick to remove the edits to the migrations.

Ahhh I understand it all now. Yes, with these migrations just pushed to the end of the line (newest, unreleased) it should be fine. There should be no migrations dependent on the filters column(s) in the migrations since. 👍

Renaming migrations = :cry: for those of us who like our development databases and have already run those migrations.

This doesn't handle detecting the Rails 5 migration change of behavior (order in which references id and type columns are created).  Will there be another test for that?

@bdunne agreed, hopefully this spec will prevent us from having to make that type of change again :wink:
@bdunne , yes I'm working on that now.  That will involve saving a representation of the "expected" schema in a file. I figured that was too much for this one PR.

Nice @carbonin  ❤

Ugh, I didn't get a chance to review this yet...but conceptually I had spoken to @carbonin and was good with the idea.  I would prefer the file was not named darga, but something like "previous release"

Added a talk article about this change http://talk.manageiq.org/t/new-schema-specs-for-new-replication/1404


An unexpected error occurred

Details

Project URL: https://readthedocs.org/projects/diadocsdk-1c
Build URL (if applicable): https://readthedocs.org/projects/diadocsdk-1c/builds/5861108/
Read the Docs username (if applicable): diadocsdk

Expected Result
Documentation built
Actual Result
Almost immediately after start build failing with text "An unexpected error occurred". This happens for most of latest builds.

Looks similar to #2991

I addressed the issue in #3073. Triggering your build, it seems the hotfix resolved the issue.

It actually looks like there is another unicode bug with our branch handling:
Sep 15 19:52:47 build01 readthedocs/readthedocs.doc_builder.environments[20809]: ERROR (Build) [diadocsdk-1c:latest] 'ascii' codec can't decode byte 0xd0 in position 197: ordinal not in range(128) [readthedocs.doc_builder.environments:317]
Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/readthedocs/projects/tasks.py", line 145, in run_setup
    self.setup_vcs()
  File "/home/docs/checkouts/readthedocs.org/readthedocs/projects/tasks.py", line 280, in setup_vcs
    update_imported_docs(self.version.pk)
  File "/home/docs/local/lib/python2.7/site-packages/celery/app/trace.py", line 439, in __protected_call__
    return orig(self, *args, **kwargs)
  File "/home/docs/local/lib/python2.7/site-packages/newrelic/hooks/application_celery.py", line 80, in wrapper
    return wrapped(*args, **kwargs)
  File "/home/docs/local/lib/python2.7/site-packages/celery/app/task.py", line 420, in __call__
    return self.run(*args, **kwargs)
  File "/home/docs/checkouts/readthedocs.org/readthedocs/projects/tasks.py", line 530, in update_imported_docs
    } for v in version_repo.branches
  File "/home/docs/checkouts/readthedocs.org/readthedocs/vcs_support/backends/git.py", line 137, in branches
    return self.parse_branches(stdout)
  File "/home/docs/checkouts/readthedocs.org/readthedocs/vcs_support/backends/git.py", line 155, in parse_branches
    data = str(data)
  File "/home/docs/local/lib/python2.7/site-packages/future/types/newstr.py", line 102, in __new__
    return super(newstr, cls).__new__(cls, value)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 197: ordinal not in range(128)

@stsewd We should check that the rest of the workflow handles unicode branch names properly. We might fix one thing, just to have it break further down the line. Have you tested #4052 with a unicode branch name, and confirmed doc serving, etc. work?

@ericholscher #4052 is just for tags, unicode branches are still failing. Using py3 solves this also p:

I just tested this is in our Azure instance that it's running Python 3.6.5:

Imported this project https://gitlab.com/humitos/rtd-project-a
d- tag was created. All Unicode chars were removed completely. The tag name is úńìĉõdê
A branch called aúbranchńwithìweirdĉcharactersõanddê was enabled in Read the Docs. The name was converted to a slug: a-branch-with-weird-characters-andd-
Links to PDF download work properly
Links to "Edit on GitLab" works properly (I'm linked to https://gitlab.com/humitos/rtd-project-a/blob/aúbranchńwithìweirdĉcharactersõanddê/index.rst which is the correct branch name under GitLab)

So, we can say that "It works under Python 3.6" without #4433 merged.
Now, I have some questions,

do we want to remove these characters?
would we have a problem by allowing them in the slug? filesystem issues? URL issues?

do we want to remove these characters?

We could use what I suggested at https://github.com/rtfd/readthedocs.org/issues/1410#issuecomment-306091586 some time ago. Instead of removing the chars, it tries to use a "similar one".
>>> import unicodedata
>>> unicodedata.normalize('NFKD', u'aúbranchńwithìweirdĉcharactersõanddê').encode('ascii', 'ignore')
b'aubranchnwithiweirdccharactersoandde'

On the other hand, if there is not an "easy replacement" it just skip/ignore it:
>>> unicodedata.normalize('NFKD', u'Straße').encode('ascii', 'ignore')
b'Strae'


Nail Down Images and Links

We need to have 4 images and 4 links.
Links:

Link to sign up/in page (somewhere other than navbar)

Images:
I think some clip-art type stuff like on Global Privacy Control could be good
Maybe let's first put the images/links as comments to this issue so that we have them all in one place?

Image locations:

Behind the slogan
behind each point under "features"

We should make sure that these images are fine to use or if there are any copyright issues

Alright these four are copyright free


Update dependencies and release new version

context
proposed solution
This package depends on knex ^0.20.1
https://github.com/haltcase/trilogy/blob/6d73d7307456084c4e9c259105f87ebc01ce7727/package.json#L47
Meanwhile, knex itself has gone through 2 major version releases, with lots of changes and features. Among other things, it now supports better-sqlite3.
https://github.com/knex/knex/releases
It'd be lovely if that dependency were updated.
alternatives
Tricky, I'd love to use trilogy and avoid having to manually deal with all of this (installing sqlite, using an ORM, etc.)
additional info
When installing this package, one even gets warnings about old, deprecated dependencies. I suppose updating all dependencies might be in order?
$ npm i trilogy
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)

added 170 packages, and audited 726 packages in 9s

@stefnotch I'm with you all the way 😃 I started down this road with #114 and hit roadblocks I unfortunately don't have the time to investigate right now.
I'm more than happy to invite collaborators interested in helping maintain trilogy as well (I still have fancy static typing ambitions about v3).

I see, makes sense. I personally wouldn't have time to maintain this library, but hopefully someone else will step up to the task. :)
By the way, there is also another quite interesting library: https://github.com/koskimas/kysely
It definitely doesn't cover all the same use-cases, but I figured it'd be worth mentioning it anyways.


fix: disable cache in frontMatter to avoid mix duplicated contents

Description
Since both v2.5.0.md and v3.0.0-next-major-spec.4  are identical in terms of content, https://github.com/asyncapi/website/blob/master/scripts/build-post-list.js#L64 is returning the same exact file when processing the second, meaning it returns the same object as for v2.5.0.md. See cache logic in https://github.com/jonschlinkert/gray-matter/blob/8a22958e0afd4b2e09c705becec1c35e76c4f0ee/index.js#L37-L42.
Then, the issue is that any modification is being made to the same file in memory, ending up in v2.5.0.md being a mix of both files.
This PR uses a workaround to disable cache: to pass {} as second argument to frontMatter function, i.e. frontMatter(fileContent, {}).
Related issue(s)
Fixes https://github.com/asyncapi/website/issues/1057

@smoya I don't know but there is some error with the latest update on the workflows. Can you kindly check that on .github repo? I can't merge this PR until all the checks are passed.

/rtm


SL Review: Update language on introduction section

User Story
Update language to align with direction from Comms team (Reviews is plural, remove 'process')
Tasks
Form introduction:
•	First bullet, change to “Senior Leadership Reviews (SLR) are a commitment that will support the DMCPSR talent and executive priorities. They address input received from deputy minister talent conversations and respond to an increase in movement at the executive level”
•	Second bullet “The SLR supports…”
•	Third bullet “The SLR provides…”
•	Last bullet change to “Visit the MS Teams Senior Leadership Reviews site…”

Thank you, Andrew!

Looks perfect in TEST ready to deploy to PROD

perfect in PROD = closing