Chrome 79 white screen

I've been running Chrome using @jessfraz's recipe for a while now (thanks) and a couple of days ago found Chrome had broken. It still launches but I just have a completely white screen. I can switch tabs but nothing is drawn. If I revert to my last Chrome 78 image it works again...
Anyone else running into the same issue with Chrome 79?

I am also having this issue. On the latest chrome, the window is completely white other than the title bar

I noticed that I can still interact with the browser - I can move the mouse around and it changes from a pointer to a text cursor over the spot where the omnibar probably is. If i enter a new website there and press enter, the titlebar changes to indicate the new site is loading.
Looking at the debug output, I have this message
[55:55:1217/201123.332202:WARNING:x11_util.cc(1415)] X error received: serial 205, error_code 10 (BadAccess), request_code 130, minor_code 1 (Unknown)
[55:55:1217/201123.332393:WARNING:x11_util.cc(1415)] X error received: serial 206, error_code 10 (BadAccess), request_code 130, minor_code 1 (Unknown)
[55:55:1217/201123.332564:WARNING:x11_util.cc(1415)] X error received: serial 207, error_code 128 (BadShmSeg), request_code 130, minor_code 3 (Unknown)

There was a big change to Drawing to Shared Memory in Sept https://chromium-review.googlesource.com/c/chromium/src/+/1789444 but disabling shared memory doesn't seem to make any difference, which makes me think it's something else.

@cradcore I was able to fix it by adding the runtime flag --use-gl=swiftshader as per https://support.google.com/chrome/thread/23098754?hl=en

@xlfe Did you add this to the last line of the Dockerfile (the CMD line?)

yep it's a Chrome command line flag.

Works for me after wiping my config folder, thanks @xlfe!

I had similar problem with Ubuntu 18.04 based Docker Image with mesa driver compiled for CPU rendering.
I could make the window content to appear providing --ignore-gpu-blacklist switch on launch
See: https://bugs.chromium.org/p/chromium/issues/detail?id=1048186#c5

After some more investigation found that adding --ipc=host on Docker container run (Allowing shared memory to avoid RAM access failures and rendering glitches due to X extension MIT-SHM) fixed the problem (without needing to provide --ignore-gpu-blacklist switch).
Looks like this is related to this change: https://chromium-review.googlesource.com/c/chromium/src/+/1789444

What if I’m running NVIDIA GPU? Do I add: —runtime=nvidia?
On Tue, Feb 18, 2020 at 1:58 AM Ruben Suarez Alvarez <
<EMAIL_ADDRESS>wrote:

After some more investigation found that adding --ipc=host on Docker
container run (Allowing shared memory to avoid RAM access failures and
rendering glitches due to X extension MIT-SHM) fixed the problem (without
needing to provide --ignore-gpu-blacklist switch).
Looks like this is related to this change:
https://chromium-review.googlesource.com/c/chromium/src/+/1789444
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jessfraz/dockerfiles/issues/515?email_source=notifications&email_token=ABHVQHACB2X7CMGDSR6SW7TRDOIK3A5CNFSM4J26EDYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMA63DY#issuecomment-587328911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHVQHFWNMCZKV7TPMURILLRDOIK3ANCNFSM4J26EDYA
.

What if I’m running NVIDIA GPU? Do I add: —runtime=nvidia?
…
On Tue, Feb 18, 2020 at 1:58 AM Ruben Suarez Alvarez < @.***> wrote: After some more investigation found that adding --ipc=host on Docker container run (Allowing shared memory to avoid RAM access failures and rendering glitches due to X extension MIT-SHM) fixed the problem (without needing to provide --ignore-gpu-blacklist switch). Looks like this is related to this change: https://chromium-review.googlesource.com/c/chromium/src/+/1789444 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#515?email_source=notifications&email_token=ABHVQHACB2X7CMGDSR6SW7TRDOIK3A5CNFSM4J26EDYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMA63DY#issuecomment-587328911>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHVQHFWNMCZKV7TPMURILLRDOIK3ANCNFSM4J26EDYA .

Yes, if you have nvidia-docker installed (but also needs the --ipc=host parameter to avoid the rendering glitches).
NOTE: I have not tried that cause I do not use nvidia-docker.  I've tested with vanilla docker ci sharing host graphic resources and installing the host nvidia driver version in the container.

--ipc=host fixed this for me, but the blacklist gpu doesn't do anything (or it might be that it makes chrome to work slightly better)

On 18. Feb 2020, at 16.15, Ruben Suarez Alvarez<EMAIL_ADDRESS>wrote:

What if I’m running NVIDIA GPU? Do I add: —runtime=nvidia?
…
On Tue, Feb 18, 2020 at 1:58 AM Ruben Suarez Alvarez < @.***> wrote: After some more investigation found that adding --ipc=host on Docker container run (Allowing shared memory to avoid RAM access failures and rendering glitches due to X extension MIT-SHM) fixed the problem (without needing to provide --ignore-gpu-blacklist switch). Looks like this is related to this change: https://chromium-review.googlesource.com/c/chromium/src/+/1789444 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#515?email_source=notifications&email_token=ABHVQHACB2X7CMGDSR6SW7TRDOIK3A5CNFSM4J26EDYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMA63DY#issuecomment-587328911>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHVQHFWNMCZKV7TPMURILLRDOIK3ANCNFSM4J26EDYA .
Yes, if you have nvidia-docker installed (but also needs the --ipc=host parameter to avoid the rendering glitches).
NOTE: I have not tried that cause I do not use nvidia-docker. I've tested with vanilla docker ci sharing host graphic resources and installing the host nvidia driver version in the container.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

--ipc=host fixed this for me, but the blacklist gpu doesn't do anything (or it might be that it makes chrome to work slightly better)
…
On 18. Feb 2020, at 16.15, Ruben Suarez Alvarez @.> wrote:  What if I’m running NVIDIA GPU? Do I add: —runtime=nvidia? … On Tue, Feb 18, 2020 at 1:58 AM Ruben Suarez Alvarez < @.> wrote: After some more investigation found that adding --ipc=host on Docker container run (Allowing shared memory to avoid RAM access failures and rendering glitches due to X extension MIT-SHM) fixed the problem (without needing to provide --ignore-gpu-blacklist switch). Looks like this is related to this change: https://chromium-review.googlesource.com/c/chromium/src/+/1789444 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#515?email_source=notifications&email_token=ABHVQHACB2X7CMGDSR6SW7TRDOIK3A5CNFSM4J26EDYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMA63DY#issuecomment-587328911>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHVQHFWNMCZKV7TPMURILLRDOIK3ANCNFSM4J26EDYA . Yes, if you have nvidia-docker installed (but also needs the --ipc=host parameter to avoid the rendering glitches). NOTE: I have not tried that cause I do not use nvidia-docker. I've tested with vanilla docker ci sharing host graphic resources and installing the host nvidia driver version in the container. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

Yes, I discovered it after my first comment.
As I tell in my second comment, the key is using --ipc=host and not using --ignore-gpu-blacklist
With --ignore-gpu-blacklist I get it working with the mesa driver compiled for CPU rendering but the --ipc=host works also with "real" GPU acceleration.


Added xplor.one

@tyler201 lib/domains/one/xplor: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@tyler201 Regrettably, this request has signs of fraud. I have to close it without merging.
It does not mean that something is wrong with the school. The issue is related to a combination of suspicious factors related to the request, the domain, and incomplete school name.
Please feel free to apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
Thank you for your understanding!


Live Indicator

I looked through all documentations (and Github issues) and couldn't find an answer. So here it is: Is there anyway to add a "live indicator" to Fluidplayer's controlbar when source is a live stream, showing to users that it is in fact a live video and they are on tolerance edge and if they are behind the stream by clicking on it the would jump the the very end?
Something like the attached screenshot.
Best Regards.

@kaambiz This is not a feature currently with Fluid Player, we have had some tickets mentioning this #394 and #328.
To implement this you need to use callbacks from both hls.js and dash.js, we have a module to deal with streaming stuff streaming.js, but the layout and configuration itself is handled with fluidplayer.js.
I'll create an internal ticket for a Feature Request so we can track this.


Sidebar looks wrong when compiled with Xcode 12

This isn't an issue on the 6.0 branch, so I'm going to go ahead and close it.


EKF2 does not detect if no mag is fused

We had an incident where the mag data published in sensor_combined was not updating properly. The timestamps sensor_combined_0.magnetometer_timestamp_relative showed that the data was old and EKF2 did not do any fusion.
However, it still claimed that there are no faults / that the position solution was good.
Position controlled flight performed poorly (significant toilet-bowling).
In my opinion, EKF2 should mark the position solution as bad if no heading fusion was done within some timeout.
Here is a log file: https://logs.px4.io/plot_app?log=8f1505e6-f998-47e4-9693-58c3c0424774
@dagar as per our discussion.
@priseborough what do you think?

This is firmware side, but I'm also wondering about tightening the commander check.
https://github.com/PX4/Firmware/blob/master/src/modules/commander/commander.cpp#L1794-L1820

8f1505e6-f998-47e4-9693-58c3c0424774.ulg.pdf

I can re-create the situation in SITL on current master with the following change in PX4/Firmware:
https://github.com/ndepal/Firmware/commit/172815f621be649d094fdc38fb4aaef978eb4577
This will cause EKF2 to stop fusing mag measurements after 2000 published mag measurements. This causes heading drift in simulation and subsequent control instability* (having done commander takeoff before the above triggered).
PX4 remains in position hold mode (and allows taking off) in this situation, despite having detected a mag timeout:
ERROR [sensors] Mag #0 fail:  TIMEOUT!
ERROR [sensors] Sensor Mag #0 failed. Reconfiguring sensor priorities.
WARN  [sensors] Remaining sensors after failover event 0: Mag #0 priority: 1

I have tried to make EKF2 detect the heading fusion timeout with the following change in PX4/ecl:
https://github.com/ndepal/ecl/commit/a15bce935167b0ba3a8a4967bc12d6f124d1293a
EKF2 does detect the timeout, sets _fault_status.flags.bad_mag_hdg to true, and estimator_status.solution_status_flags goes to 192 (i.e. neither True if the horizontal position (relative) estimate is good nor True if the horizontal position (absolute) estimate is good).
However, PX4 still does not go into a failsafe mode.
* Since the heading drift depends on the random gyro noise/drift, the timing and magnitude of the control instability varies between simulation runs.

@priseborough I would really appreciate your input on this.

I will have a look at it this week

In the scenario posted, the velocity and position errors are not large enough to fail innovation consistency checks. position and velocity errors are therefore within limits and the ekf has no reason to declare the local_position data invalid.

The toilet bowling is a predominantly due to a coupling between estimator yaw error that cause transient velocity errors and the velocity controller responses in body frame. Normally when yaw errors build up to the point where toilet bowling starts, the motion makes the yaw observable and the motion subsides or stabilises.
I do not believe this behaviour is something that we should handle with addtional EKF checks that declare local_position invalid because the sensitivity to yaw errors is vehicle type specific. Additional vehicle and controller type specific checking should be done in the commander.

Thanks for having a look at this, Paul.

Normally when yaw errors build up to the point where toilet bowling starts, the motion makes the yaw observable and the motion subsides or stabilises.

This does not match my SITL tests described above, where the vehicle reproducibly crashes into the ground after some time.
If I understand correctly, you are suggesting that mag failures should be detected by the increase in position/velocity innovations caused by the heading estimation error.
I find this problematic because:

It requires that the vehicle does some toilet-bowling to make the heading error observable. Depending on the environment this can be dangerous. In my SITL tests, the vehicle did not stop circling until it (inadvertently) hit the ground.
Tightening the position innovation gate may have other negative side effects, especially in environments with potentially jumpy GPS measurements, where a wider gate may be necessary.
It does not allow detecting mag failures on the ground before flight.

During work on a recent commercial multi-rotor project I was involved with, the behaviour of the EKF and position controller for varying levels of takeoff yaw error was extensively flight tested and in that application, the yaw and toilet bowling was found to be self correcting.
I was recommending that declaring local_position invalid on the basis of mag fusion timeout  should not be done by the EKF. For example a FW plane or copter doing regular speed and/or course changes can fly without mag fusion.
I do not have a problem with strengthening the preflight checks in the commander to include a check for mag timeout. Adding it to in-flight failsafes does need to be application/vehicle type specific. Making a FW vehicle failsafe due to a mag timeout is more risky than allowing it to continue.

During work on a recent commercial multi-rotor project I was involved with, the behaviour of the EKF and position controller for varying levels of takeoff yaw error was extensively flight tested and in that application, the yaw and toilet bowling was found to be self correcting.

Unfortunately I have not had the same experience.

For example a FW plane or copter doing regular speed and/or course changes can fly without mag fusion.

Understood. So you're proposing that the preflight check applies to all vehicles and in-flight failures depend on vehicle type or some parameter?
I think a fundamental problem is that the "failover" that happens when only one mag is present effectively does nothing at all because it fails over to the sensor that just failed.
Perhaps the behavior in general when there are no more sensors to fail over to needs to be defined. Just like we can configure e.g. no action on telemetry loss, we could add an option on what to do on total mag failure.


Mobile wallet, Send via Slatepack "SAVE SLATEPACK" button is not working.

Description:
In Mobile wallet, Send via Slatepack "SAVE SLATEPACK" button is not working.

Verified with the latest build but able to reproduce the issue.
Hence re-opening this ticket.

As per the last discussion, the "SAVE SLATEPACK" button needs to be removed from the Mobile wallet.


Distributed tracing with Unirest HTTP library

I use Unirest HTTP library in my Java lambda to call backend APIs. In order to trace the calls end to end, it would be great, if Unirest is supported by this library. Thank you.

@sujee81 We are still working on bringing dd-trace-java support to the lambda runtime. However looking at our compatibility support, we don't have a Unirest integration yet. It might be a better idea to post that feature request on the dd-trace-java repo.

Sure. Thanks @DarcyRaynerDD


Edit files in SSHFS

Issue Type: Performance Issue
When working on a file in a drive connected with sshfs, if sshfs is closed before the script is closed in the VSCODE editor, it just hangs !
VS Code version: Code 1.35.1 (c7d83e57cd18f18026a8162d042843bda1bcf21f, 2019-06-12T14:29:22.216Z)
OS version: Darwin x64 18.6.0

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to the code. As such, I will go ahead and close it. If you can identify the component that is causing the issue, please report it upstream:

for UI, OS integration: https://github.com/electron/electron
for Rendering: https://bugs.chromium.org/p/chromium/issues/list
for file IO: https://github.com/nodejs/node

Thanks for understanding.


An extra slash is added to template url from tsv reader

@serverfire
This is not disturbing on a regular server, but is disturbing on S3.
The url called is [reader server]/assets/tsvreader_modules/covers//covers.tmpl, which prevents tsv reader to work properly on the S3.
You can test using http://reader.librelio.com/tsvreader.html?wapublisher=developer&waapp=wind&waurl=/Magazines.tsv&wamodule=covers

@serverfire Can this be fixed urgently?

@serverfire We fixed this


Building Godot for a custom platform yields compilation errors

Tested versions

Reproducible with Godot 3.5.2 stable
Reproducible with Godot 3.5.3 stable

System information
Windows 11 - Docker - PS2SDK - Godot 3.5.3
Issue description
I am trying to compile Godot for the PlayStation 2 using the PS2SDK homebrew project.
I am running into compilation errors and I am not sure how to resolve them. I have a repository created so that people can try to reproduce the issue locally.
The error I am receiving is:
In file included from ./core/method_bind.h:383,
                 from ./core/class_db.h:34,
                 from ./core/reference.h:34,
                 from modules/csg/csg.h:43,
                 from modules/csg/csg_shape.h:36,
                 from modules/csg/csg_shape.cpp:31:
./core/method_bind.gen.inc: In instantiation of 'PropertyInfo MethodBind0RC<R>::_gen_argument_type_info(int) const [with R = int]':
./core/method_bind.gen.inc:548:23:   required from here
./core/method_bind.gen.inc:549:74: error: incomplete type 'GetTypeInfo<int, void>' used in nested name specifier
  549 |                 if (p_argument==-1) return GetTypeInfo<R>::get_class_info();
      |                                            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
./core/method_bind.gen.inc: In instantiation of 'GodotTypeInfo::Metadata MethodBind0RC<R>::get_argument_meta(int) const [with R = int]':
./core/method_bind.gen.inc:535:34:   required from here
./core/method_bind.gen.inc:536:55: error: incomplete type 'GetTypeInfo<int, void>' used in nested name specifier
  536 |                 if (p_arg==-1) return GetTypeInfo<R>::METADATA;
      |                                                       ^~~~~~~~
./core/method_bind.gen.inc: In instantiation of 'void MethodBind0RC<R>::ptrcall(Object*, const void**, void*) [with R = int]':
./core/method_bind.gen.inc:586:15:   required from here
./core/method_bind.gen.inc:588:36: error: 'encode' is not a member of 'PtrToArg<int>'
  588 |                 PtrToArg<R>::encode(  (instance->*method)() ,r_ret)  ;
      |                 ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Most probably, I am missing some flags for the compile, but I am unsure which.
Steps to reproduce
This is my detect.py file:
import os
import platform
import sys
import os.path

def is_active():
    return True

def get_name():
    return "Playstation 2"

def can_build():
     # Check the minimal dependencies
    if "PS2SDK" not in os.environ:
        print("PS2SDK not defined in environment.. Playstation 2 disabled.")
        return False

    if "PS2DEV" not in os.environ:
        print("PS2DEV not defined in environment.. Playstation 2 disabled.")
        return False

    return True

def get_opts():
    return []

def get_flags():
    return [
        ("tools", False),
        ("builtin_bullet", True),
        ("builtin_enet", True),
        ("builtin_freetype", True),
        ("builtin_libogg", True),
        ("builtin_libpng", False),
        ("builtin_libtheora", True),
        ("builtin_libvorbis", True),
        ("builtin_libvpx", True),
        ("builtin_libwebp", True),
        ("builtin_wslay", True),
        ("builtin_mbedtls", True),
        ("builtin_miniupnpc", True),
        ("builtin_opus", True),
        ("builtin_pcre2", True),
        ("builtin_squish", True),
        ("builtin_zlib", True),
        ("builtin_zstd", True),
    ]

def configure(env):
    env["CC"] = "mips64r5900el-ps2-elf-gcc"
    env["CXX"] = "mips64r5900el-ps2-elf-g++"
    env["AR"] = "mips64r5900el-ps2-elf-ar"
    env["AS"] = "mips64r5900el-ps2-elf-as"
    env["LD"] = "mips64r5900el-ps2-elf-ld"
    env["OBJCOPY"] = "mips64r5900el-ps2-elf-objcopy"
    env["STRIP"] = "mips64r5900el-ps2-elf-strip"
    env["ADDR2LINE"] = "mips64r5900el-ps2-elf-addr2line"
    env["RANLIB"] = "mips64r5900el-ps2-elf-ranlib"
    env["BIN2S"] = os.environ.get("PS2SDK") + "/bin/bin2s"
    env["VCL"] = "vcl"
    env["VCLPP"] = "vclpp"
    env["DVP"] = "dvp-as"

    PS2DEV = os.environ.get("PS2DEV")

    env.Prepend(CPPPATH=["{}/ps2sdk/ee/include".format(PS2DEV)])
    env.Prepend(CPPPATH=["{}/ps2sdk/common/include".format(PS2DEV)])
    env.Prepend(CPPPATH=["{}/ps2sdk/ports/include".format(PS2DEV)])
    env.Append(CCFLAGS='-D_EE -Wall -O3 -DPOSH_COMPILER_GCC -DPOSH_OS_VITA -DPOSH_OS_STRING=\\"ps2\\" -D__PS2__ -DPS2_ENABLED')
    env.Append(LIBS=["stdc++", "dma", "packet2", "graph", "draw", "math3d", "png", "debug", "z", "pad", "audsrv", "patches", "cdvd"])
    env.Append(LINKFLAGS="-O3 -Wl,-zmax-page-size=128")
    env.Append(ASFLAGS="-O3")

    env["bits"] = "32"

    env.Append(CPPDEFINES=['NEED_LONG_INT'])

    env.Prepend(CPPPATH=["#platform/ps2"])

Minimal reproduction project (MRP)
https://github.com/ivandortulov/godot-ps2

This sounds like your code is incorrectly configured, but this isn't the place to ask for support in developing your own plugins unless you've find a specific issue in the engine that's causing this

@AThousandShips Thanks, I was unsure where to post my question.


Use errorMsgFilter to check for plaintext errors coming back from API.

The remote API has a bad habit of returning status 200 with a plaintext error message when errors occur. Angular $resource turns these responses into something like this:
{
  0: "E",
  1: "R",
  2: "R",
  3: "O",
  4: "R"
  ...
}

Passing these through errorMsgFilter converts it into a usable error message string, but it's only used in the startContainer and pullImage controllers. As a result actions sometimes appear to succeed and the user never sees the error message.

Solved globally by f353dc2c419664bc8aa5523bad6d9af7025106ee


introduce extHostLabelService and mainThreadLabelService

This PR introduces the extHostLabelService and mainThreadLabelService.
I have tried to follow the patterns that other services do.
I have tested this and seems to work nicely.
@jrieken let me know how it looks to you. Thanks
fixes #75881

Thanks, merging in.


Property "salt-byte-size" is used to set hashBytesize attribute instead of saltByteSize

This piece of code is from PasswordHash.java, line 231 (method configure()):
if (props.getProperty(PARAM_SALT_BYTE_SIZE) != null) {
setHashByteSize(Integer.parseInt(props
.getProperty(PARAM_SALT_BYTE_SIZE)));
This makes that when the user set the property 'salt-byte-size', hashByteSize is set instead of saltByteSize

Thanks for reporting this issue!

NP. I'm using this with your JDBCRealm for glassfish and I was trying to configure it to use 32 bytes for hash and salt. I realized though that the configuration does not matter because the password checking uses the number of bytes actually stored.
BTW, thank you to provide this and the JDBCRealm. There's not much for salted password for glassfish (what is a shame), and yours is a pretty solid one.

Yes, hash and salt size do not affect your existing hashes. They only affect new hashes. By the way, I also updated the glassfish-jdbc-realm-salted project by now.
Yes, I was quite surprised that nobody else on this world ever wanted to use hashed password with glassfish...


chore(package): bump up typescript to latest

Description:
2.6 is out. - just bump up, not enabling new strict options yet.
Related issue (if exists):

Coverage remained the same at 97.261% when pulling 87f5fc0030b522e31b0f9da70c3173dff1f2be83 on kwonoj:bump-ts into 3b66a0bddf0e4a6bc8320e9a1c8e70be676a20a4 on ReactiveX:master.


Verify that "Pâclișa" is listed in the dropdown menu when searched

Description:
"Pâclișa" should appear in the dropdown menu with correct spelling and locality information.
Preconditions:
The website is up and running.

Step 1
Type "Pâclișa" in the search bar.
Expected results:
The dropdown is listing "Pâclișa" as the first location in the dropdown menu.

Step 2
Observe the dropdown menu.
Expected results:
"Pâclișa" is displayed and selectable from the dropdown menu.


Pass caller scope to component manager's create.

In Ember we are only using dynamicScope (since that is all that is exposed), but the callerScope is also needed to allow us to properly target actions to their calling context.
The dynamicScope tracks the direct component heirarchy without regard to blocks/yielding etc. This is a perfect analogue to the way Ember tracks .parentView through a component structure.
The callerScope tracks the current calling context. This means it is aware of blocks yielding (which changes the self in the yielded block), and is the correct analogue to the way Ember tracks the target of any actions within a template block.
For example, given:
{{#component-a}}
  {{component-b bar="bar"}}
{{/component-a}}

From within component-b the .parentView (derived from dynamicScope) should match component-a, but the targetObject of component-b should not be component-a (since component-a is not calling it).
This change allows us to completely remove the manual DynamicScope#targetObject tracking in Ember.

I also considered changing DynamicScope#child to accept the callerScope which would have let us calculate the proper targetObject in Ember, but it seems that calling context is directly related to ComponentManager#create (and completely unrelated to DynamicScope).

The required changes in Ember (and a few tests) are in https://github.com/emberjs/ember.js/pull/14217.


Problem with overworld again

Hey my Friend
i have a problem again but now with not duplicate dat datei
here is the dat datei
http://www.file-upload.net/download-11382552/temp.dat.html

and the last server log with this bug
http://www.file-upload.net/download-11382574/2016-03-11-2.log.html

hello anywhere here?

I think the author is busy with real life and school. I'll bug him if I see him next in teamspeak.

thanks

Sorry I took so long to get back, I've been really busy.  The .dat file appears fine, although is that the fml-server-*.log and not latest.log?

no sorry last log i dont have now only this two files

Can you please get me a listing with names and versions of every mod in the instance including the forge version?

puh.
Okay give me plz a day
270 mods

<IP_ADDRESS>4  this is the forge

That is a lot of mods, I'm amazed you have not had other problems. As well have not run out of block Ids. I mean you do get 3000+ ids but packs of these sizes can run out. Just out of scientific curiosity can you do a block id dump using NEI. It would be under options in NEI when you have it open in an inventory.

the block.csv? or other csv files?

I think the block.csv

So here the Files block and item but this is not with Rocketry
http://www.file-upload.net/download-11408217/block.csv.html
http://www.file-upload.net/download-11408218/item.csv.html

You're about out of Ids, I would watch adding any more mods.
Also @zmaster587 look at that log there are a few ids at the 8000 range. That is outside the 4096 limit that MC normally has?

okay what can i do now?

This is the same isse with the sky misbehaving right?

Is this issue still occuring?

I can confirm that we seem to be experiencing the same issue with the sky on our small server - here's what I know:
The issue started when we updated galacticraft (all three files) to 1.7-<IP_ADDRESS>4 in our custom pack - no other changes.
It's not just the sky, other things also behave as if on the moon - low gravity (though falls from heights that would be harmless on the moon still do fall damage), no sound (since the moon has no atmosphere to propagate sound through)... Luckily there is no "oxygen setup is invalid" suffocation, at least.
After reading this thread we had a look at ID's and we have roughly 3000 block ID's and 8000 item ID's - this may be just a coincidence, but could be worth keeping in mind. In fact, what's the standard limit for item ID's? And would NotEnoughId help there too?
As for the mod list, we have the following in common with what Golgatron posted:
ae2, ae2 stuff, agricraft
bdlib, big reactors, Bookshelf, buildcraft
chicken chunks, code chicken core, cofh core, cofh lib
decocraft, dragon API
electricraft, enchiridion, ender IO, ender zoo, extra cells, extra utilities
flood lights, forestry
galacticraft core, galacticraft planets, gendustry, generators
ichun util, IGW, ic2, ic2 nuclear control, immersive engineering, immersive integration,
JABBA, journeymap
magneticraft, mantle, mariculture deluxe, mekanism, mekanism tools, mekanism generators, micdoodle core, MFR, morpheus
natura, NEI, numina
openblocks, opencomputers, openglasses, openmods lib, openperipheral
pneumaticraft, progressive automation, project red (all except mechanical)
railcraft, redstone arsenal, rotarycraft
security craft, simply jetpacks, steve's carts, storage drawers, sync
thermal foundation, thermal expansion, thermal dynamics
waila, wawla
I'm afraid that doesn't narrow it down much, but it's all I have for now.

What was the previous build of galactic craft you were running?

The no sound thing is kinda odd.. I don't mess with the sound at all.  I believe standard limit is 4096 for block IDs.

Apparently this problem was 2fold, if GC cannot regiser it's moon, it assigns the moon provider to the overworld, and 2, I forgot to not register the dimension if GC is installed.

You may have to start the server twice to fix it.


Auto-validate for apiKey type

fixes https://github.com/syndesisio/syndesis/issues/5615

PR Storybook available here


tota11y is incompatible with requireJS (via closure compiler)

On line 78 of /plugins/link-text/index.js there is no check to ensure that axs is defined.
let extractedText = axs.properties.findTextAlternatives(
                el, alts);

and I've seen this when clicking the Link text test:
Uncaught TypeError: Cannot read property 'properties' of undefined
  (anonymous function) @ tota11y.js:12651
  jQuery.extend.each @ tota11y.js:672
  jQuery.fn.jQuery.each @ tota11y.js:437
  run @ tota11y.js:12636
  activate @ tota11y.js:10118
  handlePluginClick @ tota11y.js:113
  $checkbox.buildElement.onClick @ tota11y.js:10074
  jQuery.event.dispatch @ tota11y.js:4733
  elemData.handle @ tota11y.js:4419

I'm also able to trigger similar errors for rules other than the Headings rule tracing back to a similar problem with axs not being defined in /plugins/shared/audit.js for config = new axs.AuditConfiguration();
I'm still trying to track down additional information as I'm including the script when pages are rendered in the CMS I'm using. I haven't yet figured out if it is part of the CMS wrapping, or code on the rendered page that could be interfering. It appears that the use of requirejs on a page in the CMS may interfere, as pages without that appear to be working.

I'm not sure if it is related to #84
I was using:

and when I did so and checked the global axs object I was seeing only an Audit object and two of the audit functions. When I load in on other pages that don't use requirejs I'm seeing the entire axs object. I was getting more of an error when I tried a script tag to load the file as there was conflict between requirejs and webpack.

I'm not sure if it is related to #84
I was using:

and when I did so and checked the global axs object I was seeing only an Audit object and two of the audit functions. When I load in on other pages that don't use requirejs I'm seeing the entire axs object. I was getting more of an error when I tried a script tag to load the file as there was conflict between requirejs and webpack.

Hey @jraller,
I've made a note to dive into this tomorrow - didn't want to keep you in the dark.
Jordan

Got an update for you :)
I went ahead and made a new directory containing require.js, tota11y.min.js, and an index.html file. I also created a simple main.js file which exports an integer.

    <title>tota11y + requirejs</title>

Hello, world!

Running this I can confirm that axs.properties is undefined. Strange! I went ahead and subbed out tota11y.min.js for axs_testing.js (linked here: https://github.com/GoogleChrome/accessibility-developer-tools/blob/master/dist/js/axs_testing.js) and found the same result.
So, I can confirm that attempting to evaluate Accessibility Developer Tools (axs_testing.js, which tota11y uses under the hood) results in some weird clashing of the word require.
I'll sync up with the folks from Google and see if they have a solution in mind, hang tight - sorry to keep you waiting.

Thank you for tracking that down.

Okay this popped up again! I'll look into it ASAP, hopefully it's a quick fix.

@jasonday it hitting this over at http://www.llbean.com/ (#105)

I would like to use this tool on my project - but requirejs... Any help wanted ? I may have time and context to give an hand.

I'm still experiencing this issue.


Review Parts Inventory - preparation for beta build

What has to be done
Review Pizza Build and identify current available inventory with Edwin.
Purpose of this exercise, is to identify missing parts to be ordered in preparation of Beta Build
How do you know it has to be done
All inventory columns are completed.
If the quantity identified in "needed" column is not correct, or not precise enough, just update accordingly.
https://drive.google.com/file/d/1vqoaHk_54RKiV9V2NL35gHngVxuSySWt/view?usp=sharing

This looks like a duplicate of #834

I think it's one for your inventory and one for mine, @martukas

Yes I created two, one for each build.  But #775 is a duplicate.

Inventory complete


Bump vendir to version 0.17.0

Update vendir.rb formulae to bump the version to v0.17.0

Looks great! SHAs, links, and version are all correct.
Thanks for the bump!


Move tests into Jest

We need to move out of Karma due to lack of support and security vulnerabilities

Tackled in https://github.com/britecharts/britecharts/pull/1001


AnimationPlayer Quick and Simple Fixes? (Possibly for Godot 2.15?)

In Godot 2.14, animating using a AnimationPlayer and I am having a painfully slow experience. The issue is the timing in AnimationPlayer is done by seconds and not frames.
Can we add an interim fix that will show the frame number of wherever the timeline head is? Right now I am trying to make a simple NES era style animation and I find that I need to keep my calculator open and keep converting seconds to frames by taking the seconds and dividing it by 30 in order to get the frame number.
I'm thinking adding something like this should be simple, no?
I would also like to see previewing Animation by scrubbing the playhead in the timeline.
Thoughts?

Funnily enough I asked the same thing yesterday and got a nice response from reduz. It would most likely be  3.1 feature. See #10752

I'm tempted to try adding this myself. I have never worked on as advanced an app as Godot though :/

I recommend the Godot team gain inspiration by how After Effects handles its keyframing system. Here is an example video but feel free to investigate others. I am not saying Godot should copy this system by the way. Just a suggestion to gain from the UI design/features: After Effects Tutorial - Keyframes & Interpolation

Duplicate of #6149


gobject-introspection 1.48.0 fails to build on Darwin

Issue description
One of the OSX-specific patches for gobject-introspection fails to apply cleanly.
Steps to reproduce
$ nix-env -iA nixpkgs.gobjectIntrospection
installing ‘gobject-introspection-1.48.0’
download-from-binary-cache.pl: could not download ‘https://cache.nixos.org/5c1qhskrp8kk8a8d7kzz4z3g7x50ax19.narinfo’ (Curl error 77)
download-from-binary-cache.pl: could not download ‘https://cache.nixos.org/0nnzbl0vs21358lr4gsgbwbqjqn9f9i9.narinfo’ (Curl error 77)
these derivations will be built:
  /nix/store/zv7zshbgx2lz40n63awc8d3vma8d5ja8-gobject-introspection-1.48.0.drv
download-from-binary-cache.pl: could not download ‘https://cache.nixos.org/5c1qhskrp8kk8a8d7kzz4z3g7x50ax19.narinfo’ (Curl error 77)
download-from-binary-cache.pl: could not download ‘https://cache.nixos.org/0nnzbl0vs21358lr4gsgbwbqjqn9f9i9.narinfo’ (Curl error 77)
building path(s) ‘/nix/store/0nnzbl0vs21358lr4gsgbwbqjqn9f9i9-gobject-introspection-1.48.0-dev’, ‘/nix/store/5c1qhskrp8kk8a8d7kzz4z3g7x50ax19-gobject-introspection-1.48.0’
unpacking sources
unpacking source archive /nix/store/1n0k85m5dnrlwc91y9z0fzhnyjv1qg9b-gobject-introspection-1.48.0.tar.xz
source root is gobject-introspection-1.48.0
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file gobject-introspection-1.48.0/build/win32/vs9/gi-install.vsprops
patching sources
applying patch /nix/store/5sflxlfqc6cf4slbw36b46lj4wspcn76-absolute_shlib_path.patch
patching file giscanner/scannermain.py
Hunk #1 succeeded at 100 (offset 6 lines).
Hunk #2 succeeded at 239 (offset 6 lines).
patching file giscanner/shlibs.py
Hunk #1 succeeded at 58 (offset 5 lines).
Hunk #2 succeeded at 135 (offset 6 lines).
patching file giscanner/utils.py
Hunk #1 succeeded at 113 (offset 4 lines).
applying patch /nix/store/n2mx8ixc5xib21vwhkvl98kkl7wlp9xd-darwin-fixups.patch
patching file giscanner/ccompiler.py
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file giscanner/ccompiler.py.rej
builder for ‘/nix/store/zv7zshbgx2lz40n63awc8d3vma8d5ja8-gobject-introspection-1.48.0.drv’ failed with exit code 1
error: build of ‘/nix/store/zv7zshbgx2lz40n63awc8d3vma8d5ja8-gobject-introspection-1.48.0.drv’ failed

Technical details

System: Darwin Kernel Version 15.4.0 (OSX El Capitan 10.11.4)
Nix version: 1.11.2
Nixpkgs version: 16.09pre82421.d27848a

I belive that was addressed by 0452b58f0fac57b50291de9b541e47388ccea7e1

Pinging @clacke: is this still an issue for you? I was just able to install gobjectIntrospection with the latest nixpkgs.

http://hydra.nixos.org/job/nixpkgs/trunk/gobjectIntrospection.x86_64-darwin is green, so I am assuming this is working now.


feat: differential JS bundle based on user agent

This commit adds support for serving a different bundle to different
user agents. This means that every client will get a JS bundle that is
perfectly optimized for the features it supports.
Closes #38

I'm going to close this PR, as discussed offline. I won't delete the branch in case we want to revisit this sometime in the future.


metacity install fails on Ubuntu-20.04

Description
jobs:
  test_jdk11:
    name: OpenJDK 11 + SonarCloud code analysis
    runs-on: ubuntu-20.04
    steps:
      - name: Install metacity window manager for background tests
        run: sudo apt-get install metacity

fails with
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/main/p/pulseaudio/libpulse0_13.99.1-1ubuntu3.10_amd64.deb  404  Not Found [IP: <IP_ADDRESS> 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Fetched 28.7 MB in 1s (53.2 MB/s)
Error: Process completed with exit code 100.

Area for Triage:

Packages? (Sorry, I'm not sure what the "Area for Triage" is.)
Question, Bug, or Feature?:

Bug
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Image version

Image version where you are experiencing the issue.

20210606.1

Expected behavior
metacity installs without issues.
Actual behavior
Installation  of metacity fails as a dependency cannot be found: http://azure.archive.ubuntu.com/ubuntu/pool/main/p/pulseaudio/libpulse0_13.99.1-1ubuntu3.10_amd64.deb
Repro steps
A description with steps to reproduce the issue. If your have a public example or repo to share,
please provide the link.

See https://github.com/hexatomic/hexatomic/runs/2819373126?check_suite_focus=true

Hello @sdruskat , you should run sudo apt-get update before any installation commands

Okay, I'll do that, thanks.


Babel and esperanto

See: #24

Oh, I should add a prepublish hook.

@sparhami's original implementation was in ES6 and then we ported it back for a few reasons:
#1: We have a rule at Google that all our JS needs to run without a build step. It is somewhat fine if that is only true for one browser.
#2: We need tight control over the actual JS running in the browser in this low level library. Using let scares me, not because I don't like it (it is awesome), but because I don't know babel's code gen well enough and if it did something based on try-catch it would be really bad for performance.
#3 We want to use this with closure, so we need to make sure that if we have a build process the closure comments are in the output and there is a straight forward way to build it into a goog.module.

Th prepublish script compiles everything from src/ to lib/ so that you can require things in node normally, the dist works for the browser (compiles with a UMD so people can use it with commonjs, AMD, or globals)
Babel won't ever compile to a try-catch, here's how it compiles let variables, as you can see, all of the common cases are very simple to compile, unless you start doing weird already non-performant things.
2b) If that's still too much, it's easy to blacklist individual transformers if you are afraid they could accidentally do something bad.
Babel should maintain code comments (almost) anywhere you put them. If you put them in some crazy place where there isn't anywhere to attach the comment to an AST node then it will dump the comment at the end of the file.

Rebased, is there anything I can do here to get this in?

I'll talk to @sparhami in person on Monday. Will get back to you.

@cramforce: Any word on this? Using only the module syntax give's a pretty good size reduction.

I'm not sure about making the gulpfile use babel, the gulp-cli from npm does not work with it for me. I had to manually npm i gulp-babel as npm i failed due to what I assume is the build not working due to not having gulp-babel.
I don't think that someone should need to go out of the way to make it work just to build the project.

@sparhami You need to update the global babel cli, this can be fixed with npm scripts with a local install.

When running gulp, I get:
ReferenceError: The plugin "utility.inlineEnvironmentVariables" collides with another of the same name
It launches the browsers for tests, but never gets past that. Running gulp unit by itself works fine.

Probably my fault setting this up, I'll look at this when I get home

Could you make this pull request against the babel-and-esperanto branch instead?

Any progress on this? I believe it is about time to move on to use ES6. I think almost everybody has a build process in his project, so building incremental-dom prior to using it ain't a bad thing. This is even more true since incremental-dom is meant to be a low level library which should ease the process of building a DOM, but should be interfaced thru some higher level wrapper, as said in the overview :wink:

Sorry for not getting back to this, I'll take a look at it now

@sparhami can this be closed now that #79 is in?

#79 is still on the es6 branch, but I think I have already taken most of the changes from this PR, so I'll close it.


Hi! I want to try your code

Hi. I was finding react based comfyui project and came across your repository.
I was able to run this on my comfyui and now I want to make changes to UI using tailwindcss.
It looks like react project code is already built and the output html/css/js is directly used in comfyui.
I am not sure from where to start and how to build.
Could you give me simple guide please ?

Hi, the bind between the comfy ui server and the html pages from React build can be found here
https://github.com/stavsap/ComfyUI-React-SDK/blob/main/__init__.py
it is linking the route (root) and the fetch of the static files from "web" folder. so you can build whatever react project you like and make a build and put it in the web folder.
get familiar with this file first.  then you can modify other aspects such as base route and static folder etc...
the react demo project of this repo is in "app" folder but you can have it any desired location. what matters eventually is the static build.

Hi, the bind between the comfy ui server and the html pages from React build can be found here
https://github.com/stavsap/ComfyUI-React-SDK/blob/main/__init__.py
it is linking the route (root) and the fetch of the static files from "web" folder. so you can build whatever react project you like and make a build and put it in the web folder.
get familiar with this file first. then you can modify other aspects such as base route and static folder etc...
the react demo project of this repo is in "app" folder but you can have it any desired location. what matters eventually is the static build.

Hey, thanks for your reply! I've forked your repository and started adding my stuff. I was able to run/edit and add my own react project. I really appreciate your base code project. It was the only one with react that I could find!

great, have fun!


Share Video on Whatsapp ERROR

When I share a video on whatsapp, whatsapp says the file is not of type IMAGE. If I select share by e-mail or other destination, share it correctly.
The same file, if I share it with any program as "ES File Explorer" from android gallery or using the native operating system, WhatsApp is shared smoothly.
code:
window.plugins.socialsharing.share('Here is your Video', 'Your Video', 'file://mnt/sdcard/1/2.mp4');

Editing SocialSharing.java ....
private Uri getFileUriAndSetType(Intent sendIntent, String dir, String image, String subject, int nthFile) throws IOException {
// we're assuming an image, but this can be any filetype you like
String localImage = image;
sendIntent.setType("video/*");
return Uri.parse(localImage);
}
But not changes...

Only i edit /platforms/android/src/mobi/roshka/cordova/shareplugin/SharePlugin.java
Line 61:
sendIntent.setType("video/*");
Line 66:
String[] mime = {"video/*"};
Now works for Share the videos on WhatsApp ! :)

Hi Pablo,
thanks for your effort and sharing your fix. Is there a way to get your compiled version with that fix? Because #165 is still open.
Thanks.

@krakostzakos I'd love to merge a backward compatible cross-platform fix for this issue. If anyone can point me to a fork or PR then I'd be happy to do it.


Bumping podspec version

The podspec version has not been updated in 8 months, this will allow people to update to newer changes.

@rs can you push a new tag / pod trunk push? thanks.

@thedrick I will take care of this, in a few days. I need to make sure the changes in this version are not breaking compatibility with the older ones, case in which we should be bumping to a major version.


Seems like the Azure Portal interface has change a bit and the page may need an update

It seems like the interface for the Azure Portal has changed a bit, such as the button Edit (In Monitor) being replaced by Customize. This page may benefit from a review. Thank you.
[Enter feedback here]

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

ID: 75687a2c-c9e0-262f-197b-4b88b8e6d27d
Version Independent ID: 58bd1e87-6399-d276-7258-b5022d1019a8
Content: Monitor Azure Storage services with Azure Monitor for Storage - Azure Monitor
Content Source: articles/azure-monitor/insights/storage-insights-overview.md
Service: azure-monitor
Sub-service: ****
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@AdelaManea Good observation and thanks for the feedback!
Assigning @mrbullwinkle for visibility, review and document enhancement consideration as appropriate.

I appreciate the really quick response! Just a heads up, as I continued reading a few more things looked changed in the interface than I realized initially, so I recommend a review of the whole page not just what I mentioned specifically. I don't know how you usually review these changes so I thought I would mention it. Have a great day!

@AdelaManea Sorry for the delay and thank you for helping us to improve the docs. = D
I made an internal work item to review and update this doc, and added it to our backlog.
#please-close


minimum-stability issues

composer require not working as described in the readme

I am getting same issues in above image with below code.
{
"name": "ephyre/voxilo-cakephp-teams-plugin",
"minimum-stability" : "dev",
"prefer-stable" : true,
"repositories": [
{
"type": "vcs",
"url": "git@bitbucket.org:ephyre/voxilo-cakephp-teams-plugin.git"
}
]
}

Hello @phpexpert00784
Is your problem actually even related to this project?

Its a another project. But i am very thankfull if you help me out

@phpexpert00784 You need to do something like described in https://github.com/hettiger/larawire#installation
In your case since you're using type vcs you may use something like
            ...
            "dist": {
                "url": "git@bitbucket.org:ephyre/voxilo-cakephp-teams-plugin.git",
                "type": "vcs"
            }
            ...

Just make sure you define a package in the repositories section first and then add it to the require section. That should do the trick. If that doesn't help you, have a look at the composer documentation. You should be up and running in no time. :-)


label cannot be provided as a keyword

The readme mentions:

If you are calling it in a loop, or with different variations, you can include a label on the filename:

flamegraph(label: "rspec") {
  # your code here
}

This is not accurate, as it results in:
     ArgumentError:
       unknown keyword: :label

If the library wants to support both a normal parameter and a keyword arg, it could use:
def flamegraph(_label = nil, label: _label, open: true, ignore_gc: false, interval: 1000, &block)

Thanks for reporting! I'm not sure which I really intended 🤔
I think I'm alright with keeping it a positional argument, and updating the docs.

Fixed the docs, and added some tests around this. Included in 0.2.0


[UI]: Update home "Latest Updates"

Add missing products that were completed in 2022:

ABRFC QPE 1hr
NCEP STAGE4 MOSAIC QPE PRECIP 1hr, 6hr, 24hr

Ignoring CNRFC as those products are not usable as is (polar sterographic source projection issue).

CC @FHanbali


GivWenZen doesn't parse some data types with the latest version of FitNesse

Greetings!
Upgrading FitNesse from a 2014 version to latest resulted in some compatibility issues with GivWenZen. Many tests started to fail and a quick debugging session showed that all affected scenarios incorporate the Hash Table markup syntax. The hash table is correctly matched by the regular expression, however it is passed as a String to the @DomainStep method which is expecting a Map.
Example scenario:
|given|a person with data !{first_name: "Bob", last_name: "Martin"}|
...

@DomainStep("a person with data (.*)")
public void createPersonWithData(Map<String, String> data) {
    // do something
}

Side by side debugging of the old and new versions showed that after the update PropertyEditorParser#canParse starts to return false for the Hash Table. Further research showed that there wasn't a proper editor registered for the data type.
I found that there was a MapEditor class in the fitnesse.slim.converters package of the older version I was using. The MapEditor class was replaced at some point in time with MapConverter class.
I also spotted the ConverterRegistry class. Then I did a few tweaks to PropertyEditorParser class:
    public static Converter getPropertyConverterFor(Class<?> paramerterType) {
        return ConverterRegistry.getConverterForClass(paramerterType);
    }

    public boolean canParse(Class<?> paramerterType) {
        return getPropertyConverterFor(paramerterType) != null;
    }

    public Object parse(Object paramerter, Class<?> paramerterType) throws Exception {
        Converter propertyConverter = getPropertyConverterFor(paramerterType);
        return propertyConverter.fromString(paramerter.toString());
    }

And tests started passing - the hash table syntax was successfully parsed and passed as a Map to the @DomainStep method.
I can open a PR if you find the proposed solution reasonable.
Cheers! :beers:

Please open the PR
On Mon, Jun 3, 2019, 12:48 PM Veselin Stoyanov<EMAIL_ADDRESS>wrote:

Greetings!
Upgrading FitNesse from a 2014 version to latest resulted in some
compatibility issues with GivWenZen. Many tests started to fail and a quick
debugging session showed that all affected scenarios incorporate the Hash
Table markup syntax
http://fitnesse.org/FitNesse.FullReferenceGuide.UserGuide.FitNesseWiki.MarkupLanguageReference.MarkupHashTable.
The hash table is correctly matched by the regular expression, however it
is passed as a String to the @DomainStep method which is expecting a Map.
Example scenario:
|given|a person with data !{first_name: "Bob", last_name: "Martin"}|
...
@DomainStep("a person with data (.*)")
public void createPersonWithData(Map<String, String> data) {
// do something

}
Side by side debugging of the old and new versions showed that after the
update PropertyEditorParser#canParse starts to return false for the
Hash Table. Further research showed that there wasn't a proper editor
registered for the data type.
I found that there was a MapEditor class in the
fitnesse.slim.converters package of the older version I was using. The
MapEditor class was replaced at some point in time with MapConverter
https://github.com/unclebob/fitnesse/blob/master/src/fitnesse/slim/converters/MapConverter.java
class.
I also spotted the ConverterRegistry
https://github.com/unclebob/fitnesse/blob/master/src/fitnesse/slim/converters/ConverterRegistry.java
class. Then I did a few tweaks to PropertyEditorParser class:
public static Converter getPropertyConverterFor(Class<?> paramerterType) {

    return ConverterRegistry.getConverterForClass(paramerterType);

}

public boolean canParse(Class<?> paramerterType) {

    return getPropertyConverterFor(paramerterType) != null;

}

public Object parse(Object paramerter, Class<?> paramerterType) throws Exception {

    Converter propertyConverter = getPropertyConverterFor(paramerterType);

    return propertyConverter.fromString(paramerter.toString());

}

And tests started passing - the hash table syntax was successfully parsed
and passed as a Map to the @DomainStep method.
I can open a PR if you find the proposed solution reasonable.
Cheers! 🍻
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/weswilliams/GivWenZen/issues/7?email_source=notifications&email_token=AABVJ7PTVJI7EK2B3IZXM63PYVYRZA5CNFSM4HSQFI52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXLYIHA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABVJ7LYU7TEX6TXPQWCTODPYVYRZANCNFSM4HSQFI5Q
.


Decommission old Fedoras from being supported

I think this is what you were originally going for in 36f725c5ac8fcc34a5d5ffea8eeba39d6876aa45 right?

I got a bit gun shy on this one early in the morning w/o coffee, but it should go away now that all fedora releases ship with EPEL enabled.


Feature Request: Some styling options to be configurable in settings

While I love the design principles and overall look, everyone likes to tinker, just think how many apps have themes ;-)
For some such as me, who are "hard of seeing" some elements on the screen are a bit of a problem.
So personally I would prefer that the tiles stand out a bit more from the background when off, and be a bit less bright when on.
Also I find the faint subLabel very hard to read.
I asked on discord about A way to set the tile default "on" background colour but it seems there isn't one.
I had a look in the code and found the opacity settings, and thought that just being able to tweak those in the setup screen would most likely be enough, to adjust the contrast.
Obviously being able to set default font sizes for each element would also be a great help to the visually challenged.
Perhaps you might address these options in a future release ?
Thanks
PS not a criticism !!

Regarding tile contrast:
The contrast settings (opacity) as we have now were a recommendation from our UI expert. It turned out to be nicely visible on "real" screens (PC/tablett) and on the smaller (320x480) TouchPanel devices. The newer (480x480) panels, which are not widely used so far, have obviously a different brightness curve. They appear darker and there is less contrast at low intensity levels. It becomes better if a brighter background is set like a dark grey or blue. You have one of those new panels and so you see the above effect.
I could make the opacity settings for the tiles  (on and off) configurable as system wide config parameter. It needs a little caution and make sure there are no side effects but should be doable.
Regarding font sizes:
This a different story. Could you please move this topic to a seperate issue. Thanks.

Thanks for considering this!
I already adjusted to a dark blue and it does help some. If you do add settings, could this also include the text / subtext please ;-)


Move Forwardable integration tests to a Ruby script

Similar to how the Array tests are a assertion style integration test for inline buffer that is invoked once.
https://github.com/artichoke/artichoke/blob/028fb100d978c9319ee825e24905826d39323c00/artichoke-backend/src/extn/core/array/inline_buffer.rs#L370-L384
The existing tests for Forwardable are a mess of inlined Ruby code in Rust test modules:
https://github.com/artichoke/artichoke/blob/028fb100d978c9319ee825e24905826d39323c00/artichoke-backend/src/extn/stdlib/forwardable.rs#L28-L71

Closed in GH-629.


Link to "Office 365 License Reporting and Management Tool -Assign Remove Licenses in Bulk" is not working any more.

Refers to https://gallery.technet.microsoft.com/Office365-License-cfd9489c which is not available any more. Couldn't find the "new" target.

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

ID: cccdd91a-7f05-abd5-ed94-e82152b86914
Version Independent ID: 3532d0a8-119c-f7d0-0d4f-a865ad32570f
Content: Manage user access to Microsoft Teams - Microsoft Teams
Content Source: Teams/user-access.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@almacho Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @almacho, thank you for your feedback.
This tool/script is not available anymore. You can use the Admin Center to manage license in bulk now.

I merged the article update. Thanks!


Check if bottom of page was reached

In some cases, the last element can be very short and will never be the only visible element. That causes some awkward situations when you click the last link on a navbar, it doesn't get activated.
So, I added a check that if we are at the bottom of the page, the last element in the items array will be the active one. We could put this check behind a prop trigger but I don't think it is necessary?

I'll close this until I get the checks to pass


MPI snooker update

Update to the MPI version of MCcubed to use the snooker walk algorithm.

Can you redirect the PR into the demc branch? That will make things much easier for everyone.  Because your changes stem from that branch, the mpi branch has my own edits, and conflicts with your PR.
Thanks.


Download Harms - Timeout and Re-Trigger

As a Ministry or IAO user
I want to be able to re-trigger the download harms function if the process times out
so that I am not unreasonably delayed

Assumptions & Scope
This story reflects the need for Ministry/IAO users to be able to re-trigger the download for harms process in the event of a system timeout event due to a network or other error beyond the user's control.
We will need to determine a reasonable amount of time to assume that the process has timed out. The time will also likely differ depending on if the records packaging is going through the standard pod/lane, vs the large file size pod/lane.
When the time threshold is reached, the user that actioned the download feature should be notified that the process has 'timed out' and they will be able to re-trigger the download for harms.
What is IN scope?
Re-activating the download for harms feature when the process has timed out
Notifications for users that the process has timed out
Acceptance Criteria
Scenario 1: Download for Harms - Standard Package Timeout

GIVEN a user has trigged the download for harms
AND the package is in the standard package pod for processing
WHEN the processing time reaches XX hours
THEN the download for harms function will re-activate
AND the user can re-trigger the download for harms process again

Scenario 2: Download for Harms - Standard Package Timeout Notification

GIVEN a user has triggered the download for harms
AND the package is in the standard package pod for processing
WHEN the processing time reaches XX hours
THEN the user will receive a notification indicating: "The download for harms package has timed out, please try again."

Scenario 3: Download for Harms - Large Package Timeout

GIVEN a user has trigged the download for harms
AND the package is in the large package pod for processing
WHEN the processing time reaches XX hours
THEN the download for harms function will re-activate
AND the user can re-trigger the download for harms process again

Scenario 4: Download for Harms - Large Package Timeout Notification

GIVEN a user has triggered the download for harms
AND the package is in the Large package pod for processing
WHEN the processing time reaches XX hours
THEN the user will receive a notification indicating: "The download for harms package has timed out, please try again."
...

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design
@xxx - please link the Design here
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

As discussed at stand up today - here is the story for re-triggering the package download feature when the process times out. We can use this functionality for future download features relating to records.
cc @lmullane @KyEggleston @liseandtea @sumathi-thirumani-aot @abin-aot

Note that we will need to come up with what is considered a reasonable amount of time to assume a timeout has occurred. For the large package lane, it would make sense if that timing is different than the standard package time.

Note from refinement - dev team to update the hours for this user story, based on the cron jobs that will be used to handle this.

Likely hood of occurring is low. Will be handled as part of the redesign.


Reduce dependencies of test::stream

test::stream has a dependency on a small part of websockets and also transitively pulls in tcp.hpp from ASIO. I believe this can be resolved with forward declarations.

teardown.hpp is pretty harmless except for the tcp.hpp part

I think we're allowed to forward declare stuff from other boost libs, after all they are frozen at the same version so the source is predictable.


Move Stepper Input to core

Follow on from #1855

Lungo Goal: push to core if Jake happy

Found a few items to address. Will add feedback to teams channel by EOD.

Feedback added to teams channel

URL: https://storybook.saltdesignsystem.com/?path=/story/lab-stepper-input--default
When dev picks this up let me know and we can discuss these to go over any questions and possible remediation suggestions.
Bordered Example (Usability not accessibility):
When the component receives focus initially the value does not increase/decrease when using arrow keys or when selecting the up/down buttons using a mouse. These are initially disabled.
After a number is entered the value does increase/decrease when using arrow keys and when selecting the up/down buttons using a mouse.
Read-only Example:
Does not convey it is read-only status to screen reader users. It says “Stepper Input Spin button editable 5”
Validation Example:
Does not convey the validation state to screen reader users. Please note: I did modify the visible label as that was the only way the status was being conveyed but is not going to accurately reflect the experience when implemented.
Refresh Adornment & Controlled Example:
Screen readers do not covey anything when the refresh button is pressed
Custom Buttons Example:
The plus and minus buttons are in the focus order. These should be removed similar to the up/down arrow buttons in the other examples.

Macc Goal: no work planned, capacity issues


Fixes #87, options property is now binded to directive. Using angular…

Fixes #87, options property is now binded to directive. Using angular 2.2.0

Resolved with https://github.com/jkuri/ng2-uploader/pull/129


Messaging: Action updates for US & EU

Messaging
Context
From Brett:
The context is that we'd like to fix a bug in Action matching using "HTML selectors." Michael's metabase queries above show a small number of users who are depending on the broken functionality. Basically, they are using (for example) foo as a matcher, when they most likely need to be using .foo to match a class or #foo to match an ID. foo should only match HTML elements (i.e. ). I am far from a product analytics product/frontend/query expert, but I hope that made sense. :)
Tiina proposed we email these ~100 users and ask them to double check their actions, and then merge our fix a week or two later.
Format
1 email, giving 1 week notice.
Audience / Targeting
Targeted based on org_ids from Pipeline

Hows this @bretthoerner ?

I like it a lot, but I think we can be even more specific.
We should call out that it looks like they are using a "bare" string in an action selector that isn't a regular HTML type. It is most likely they want to add a . or a # to any bare selector strings they have.

Better?

Looks great to me, thanks!

Oh, /cc @Twixes

Oh, did you have a date in mind? I think Tiina mentioned 2 weeks, but I'll set a reminder for whatever you think and merge then.

Thank you for jumping in Joe!
I do have some notes on the message. I'm afraid in its current form it's essentially impossible to action. There are three problems, in an increasing order of significance:

Insights are also affected, and accounted for in the lists of orgs that Brett sent.

"Your team uses a string without a prefix in at least one selector that isn't targeting a regular HTML element" – fully correct technically, but I had to read it three times to understand what it means. I think an example would be tremendously useful. I think we should start with something like:

We noticed your team has some actions or insights that don't use CSS selectors properly. Specifically, a few of your event filters seem to select an element class or ID without the required . or # prefix. This has worked so far, but on XX/XX/XX we'll fix a bug to fix this wrong behavior!

We can definitely leave out "isn't targeting a regular HTML element", since that's just a heuristic used internally to determine what "seems to select an element class or ID without the required [...] prefix".

The affected customers have many insights and dashboards. Without links to the offending items, the message is pointless. Nobody's going to start sifting through literally everything in their PostHog project just to potentially some find misconfigurations, which may actually be completely insignificant in their case.
We already have the list of these offending items (insights per organization and actions per organization), so the only question is: can we parametrize the message based on such a mapping? @joethreepwood

Thanks Michael! Will definitely tighten the message a little.
For mapping, it should be possible if I can get the data. Customer.io enables us use Liquid HTML to personalize content by pulling in attributes. To do that though, I'd need each of the actions we want to reference mapped to individual users. Customer.io, because of how the integration is setup, doesn't have a conception of organizations.
Basically I'd need a table that looks like this, covering all impacted users.

email
action_name_1
action_name_2

<EMAIL_ADDRESS>name_of_broken_action_1
name_of_broken_action_2

<EMAIL_ADDRESS>name_of_broken_action_1
name_of_broken_action_2

<EMAIL_ADDRESS>name_of_broken_action_1
name_of_broken_action_2

With that, I can then create Liquid tags to reference each action_name_x field, and insert those into an email that lists based on some logic statements.
This would be manageable for a small number of actions, but could get very difficult if we have a very large number of actions because I'd have to create this by hand for each one. It would also get tricky for users if we're creating a very long list of actions.
The question then is, can we get this data and how many actions are we going to have to reference per user?

Well, between 1 and 30 actions/insights. Does this solution scale to such numbers and variability?

I can manage doing about 30. It's just not going to be a pretty email for people with more than 10.

Makes sense, made a query for this exact format:
EU – Metabase and CSV
US – Metabase and CSV

@joethreepwood Per our chat, sending updated version with insight/action names instead of IDs:
US – Metabase and CSV
EU – Metabase and CSV

Hm, that US link keeps giving me not found errors. Can you DM?


Run custom/multiple formatters

Running additional formatters may catch more syntax problems without invoking the compiler.
Also users may wish to use a different formatter / error detector.
e.g. https://github.com/uncrustify/uncrustify might be an extra formatter for many C-like languages.

https://sparkbox.com/foundry/go_vet_gofmt_golint_to_code_check_in_Go shows why multiple formatters/linters should be used (in addition to compiling) to ensure the generated code is accurate.  Not very important yet as the go code is rarely compilable atm, but we'll get there very soon.

c.f. https://github.com/adsharma/py2many/issues/191 wrt go formatters/linters.


WPP.chat.sendTextMessage not work

Description
I'm using WPP in my project. I use WPP.chat.sendTextMessage to send message. When I call this api for the second time I am getting this error. I think it is due to version update of whatsapp. It can be called normally in version 2.2320.10 but an error will be reported in version 2.2321.6

Environment

WhatsApp version: 2.2321.6
WA-JS version(s): latest
Browser: Chrome 113.0.5672.126

Steps to Reproduce

use api to send a message（We found that the message will be blocked and not sent successfully）
use api to send a message again the error happen

WA-JS v2.24.1 is Working

#1126

O envio realmente não está sendo realizado, a mensagem não é enviada mesmo na última versão da biblioteca.

Fixed at https://github.com/wppconnect-team/wa-js/releases/tag/v2.24.1


Add dbt test for address consistency

Tests that make sure all addresses are stored in consistent, lowercase format.

added generic test is_address_lowercase which should be applied to every address
added make test which runs dbt test
started working on schema description

Second commit modifies the dbt models to make sure tests actually pass.
Interesting side-effect is that calling make run (or selectively materializing asset for which test exists) will actually run tests as the final step, even though I did not touch any configuration.

Ready to merge., love the new CI.


zopen clean --unused cleaning more than it should

In the below command, I specify that I want to clean the bash package, but it is also cleaning other packages containing bash
zopen clean -u bash
/home/itodoro/zopen/usr/local/zopen/bash/bash-<IP_ADDRESS>31007_025655.zos
1: bash/bash-<IP_ADDRESS>30920_202747.zos <- Removed
2: bash/bash-5.2.15 <- Removed
3: bash/bash-<IP_ADDRESS>31007_025655.zos  <-  current
4: cmake/CMake-heads.v<IP_ADDRESS>30301_161451.zos/share/bash-completion <- Removed
5: cmake/CMake-heads.v3.27.6/share/bash-completion <- Removed
6: CMake/CMake-heads.v3.27.6/share/bash-completion <- Removed
7: cli/cli-trunk/share/bash-completion <- Removed
8: githubcli/githubcli-DEV/share/bash-completion <- Removed
9: githubcli/githubcli-DEV.20231106_205638.zos/share/bash-completion <- Removed
10: githubcli/githubcli-DEV.20231107_213716.zos/share/bash-completion <- Removed
11: githubcli/githubcli-DEV.20231107_214756.zos/share/bash-completion <- Removed
- Removal of unused package versions complete

@IgorTodorovskiIBM for the ones that were 'overly cleaned', are they dev packages?

should we be adding 'findutils' to our base set of tools we package up so that we can have a reliable find (with -print0) and xargs (with -0) ?

githubcli

Some are (CMake, cli), and are not (cmake, githubcli)

should we be adding 'findutils' to our base set of tools we package up so that we can have a reliable find (with -print0) and xargs (with -0) ?

I'm ok with expanding our embedded tools as long the package doesn't grow too big. findutils is only 2mb so it should be ok. We could even add moreutils for parallel


Change Find service name as we're accepting undergraduate courses

Context
We need to update the new service name for Find, so that we can enable Teacher Degree Apprenticeship (TDA) courses.
The new service name is:
Find teacher training courses
Guidance to review

Check each page changed on this PR on the review app and the service name should match with the above.
Is there any other place mentioning postgraduate that we should change?

What this PR does not do?
It doesn't change the links. This will be done in a future card/PR.

 Update the name of the Find service, and remove reference to postgraduate on Find and Apply


Roll Flutter Engine from 7d5a120a601b to 39b29d041cc2 (1 revision)

https://github.com/flutter/engine/compare/7d5a120a601b...39b29d041cc2
2024-01-04<EMAIL_ADDRESS>[fuchsia] Remove LoggingSocketTest.UseSyslogOnFuchsia test (flutter/engine#49524)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Add command-line flag to control Amber relaxation

For some uses of the predicted models, the relaxation step using Amber is not necessary. This pull request adds the --use_amber_relaxation flag to the run_alphafold.py and run_docker.py files to control whether or not the relaxation step is run. The default is True and preserves the existing behavior.
Co-authored-by: @terwill

Also, a Docker image for testing is available at cctbx/amber_alphafold.

Thank you, I added this feature in https://github.com/deepmind/alphafold/commit/57a2455e5fab752d8df430ae1d0334e1a21b548c


Lack of mstatus.FS for fcsr creates architectural side-channel

An OS targeting RV64IMAC running on an RV64IMACZfinx system has to work as-is. Without mstatus.FS gating fcsr access:

Userspace that tries to use Zfinx instructions will succeed but the lack of context switching means independent processes will clobber each other
Malicious processes can use fcsr as an architectural communication primitive that is not visible to the OS

Any instructions that read or write to fcsr have to be disabled by default and have a means to be explicitly enabled by the OS.

Hi @jrtc27
The context switching covers all integer registers, the difference is there is no extra floating point register to save/restore.
The context is extended to include FCSR, so this should always be saved/restored.
I'm not sure that the RV64IMACZfinx system has to work "as-is", you have to make changes for an RV64IMACF system, and so it is reasonable to make a simpler change for the RV64IMACZfinx system, isn't it?
Providing the context includes FCSR then I think the problems are solved.
Tariq

Hi @jrtc27
The context switching covers all integer registers, the difference is there is no extra floating point register to save/restore.

I realise this.

The context is extended to include FCSR, so this should always be saved/restored.
I'm not sure that the RV64IMACZfinx system has to work "as-is", you have to make changes for an RV64IMACF system

No you don't. For F, any instruction that accesses floating-point state, be it a floating-point register or fcsr, will trap with an illegal instruction exception if [ms]status.FS is 0. An OS that is not aware of F will not set it to non-0 and therefore the hart will behave as if the instructions don't exist.

, and so it is reasonable to make a simpler change for the RV64IMACZfinx system, isn't it?

No. This is precisely why threads like https://lists.riscv.org/g/security/topic/proposal_for_stateen_csrs/83156476?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,83156476 exist, to try and a more extensible mechanism than mstatus.FS etc as there are only so many bits in mstatus.

Providing the context includes FCSR then I think the problems are solved.

That first part is the problem. An OS written for RV64IMAC has to work unmodified on an RV64IMACZfinx system without any security issues. Even if it were reasonable to require OSes written today to dynamically support every current extension at run time (but not require), which it is emphatically not, Zfinx was conceived strictly after RV64IMAC and therefore it is impossible for an OS written before Zfinx was created to know about it.

This ties into the (yet to be defined) discovery mechanism. A future OS will need to discover the extensions and adapt accordingly. There is no backwards compatibility requirement here. In this particular case FPSR will be considered part of the context as a result of discovering Zfinx.
Any FP instructions on an RV64IMAC core will trap, and the OS may emulate them in the handler.
This is not the case for the Zfinx version.
There's nothing in the spec that says it's backwards compatible - why do you state that it must be? Can you give me some more background for your argument?

Interestingly table jump from Zce has the same problem - it introduces TBLJALVEC which is part of the context. If the OS doesn't know about it then it can be used as a very nice side channel as it's XLEN bits.
So I think your proposal is that mstatus.FS behaviour is unchanged - but only relates to FCSR, so the FCSR will default to being inaccessible.

Interestingly table jump from Zce has the same problem - it introduces TBLJALVEC which is part of the context. If the OS doesn't know about it then it can be used as a very nice side channel as it's XLEN bits.

Yes, that needs an off-by-default enable bit, though that extension is rather inflexible and not very RISC-V-like so I'm personally not convinced it's a good idea.

So I think your proposal is that mstatus.FS behaviour is unchanged - but only relates to FCSR, so that FCSR will default to being inaccessible.

Yes, that sounds sensible to me. Note that this includes instructions that access FCSR as a side-effect, either because their behaviour depends on FRM or because they update bits in FFLAGS, not just the explicit CSR instructions themselves.

I agree the side-channel matter is a problem.  We can choose to close it either with FS or with the state-enable proposal.  I guess I favor doing it with FS, since that's already the sanctioned mechanism for fcsr, and so it's less divergent.

This is already covered by the state-enable proposal.  To quote:

Initially, the following bits are proposed to be defined in mstateen0, hstateen0, and sstateen0:
bit 0   Custom state
bit 1   fcsr for Zfinx and related extensions (Zdinx, etc.)

Bit 1 applies only for the case when floating-point instructions operate on X registers instead of F registers.  Whenever misa.F = 1, bit 1 of mstateen0 is read-only zero (and hence read-only zero in hstateen0 and sstateen0 too).  For convenience, when the stateen CSRs are implemented and misa.F = 0, then if bit 1 of a controlling stateen0 CSR is zero, all floating-point instructions cause an illegal instruction trap (or virtual instruction trap, if relevant), as though they all access fcsr, regardless of whether they really do.

This is already covered by the state-enable proposal. To quote:

Initially, the following bits are proposed to be defined in mstateen0, hstateen0, and sstateen0:
bit 0   Custom state
bit 1   fcsr for Zfinx and related extensions (Zdinx, etc.)

Bit 1 applies only for the case when floating-point instructions operate on X registers instead of F registers.  Whenever misa.F = 1, bit 1 of mstateen0 is read-only zero (and hence read-only zero in hstateen0 and sstateen0 too).  For convenience, when the stateen CSRs are implemented and misa.F = 0, then if bit 1 of a controlling stateen0 CSR is zero, all floating-point instructions cause an illegal instruction trap (or virtual instruction trap, if relevant), as though they all access fcsr, regardless of whether they really do.

I should have read my own link :)
I'm not a huge fan of that approach, reusing mstatus.FS seems a bit nicer, but both work and it doesn't really matter at the end of the day. Is the dependency of Zfinx on that proposal being tracked somewhere? And what is the state of that proposal; is there a risk it will stall and hold up Zfinx (which could be avoided by having Zfinx use mstatus.FS)? Also, if the Zfinx spec is going to call out that mstatus.FS is hard-wired to zero and does not affect fcsr then I think it should also explicitly call out the use of the state enable CSRs; otherwise people will miss it (or omit both and cover those solely in the privileged architecture manual, since AFAIR the F chapter in the unprivileged spec doesn't talk about mstatus.FS at all).

The simplest resolution is to reinstate mstatus.FS - it's the known good solution.
All CSR access to fcsr and all FP ops will trap if it's zero.

Sorry for jumping the gun.  JohnH already thought this one all the way through, and I support his line of reasoning.  I'm closing this issue as "done".

I believe it was premature to close this; Smstateen provides the mechanism for this bug to be fixed, but then Zfinx needs to depend on Smstateen, which is not currently specified

@aswaterman I think it's worth adding a cross reference into the spec about the presence of the state enable.


Move set up repository, installing and initializing and the getting started into it's own getting started section

I don't think the getting started is in a well enough shape to guide a citizen developer. If people have no exposure before to Python, the current getting started does not explain the following topics well enough:

Mention python needs to be installed
Selecting the Python interpreter in vscode
How to write your first test
How to run a test with test explorer / pytest
Should we guide the user through setting up a requirements.txt?
Should we guide the user in setting up a venv?


Is the kernel produced for RVR correct?

I have an X training vector passed in that is of shape (2,2219), but the RVR fit() function calls RegressionARD's fit() using a kernel K that is of shape (7,7). This results in my coefficients (coef_) being of size 7, which doesn't seem correct since my n_features is 2219.
is there an error in the get_kernel function?

So you have data set with n_samples = 2, n_features  = 2219?
Algorithm assumes that input X is of size [n_samples,n_features], initial kernel matrix is of size [1,1]. Kernel matrix is iteratively increased to include all relevant vectors, note that maximum number of relevant vectors is equal to n_samples, in your case it can not be larger than 2. So n_features should not be 2219, however coef_ attribute obviously should not have shape (7,).
I have no idea how kernel size can become larger than n_samples, since I use 'pairwise_kernels' from sklearn for kernel construction !
I would suggest you to make small detailed ipython notebook illustrating problem, or share data so I can run experiment ( if it is not sensitive ). You can make pull request and contribute to user_examples folder.
Thanks for help.

Sorry that was a typo the shape is (7,2219). So 7 samples.

Yes in your case maximum kernel size can be (7,7) as I explained in previous answer.

RVM does not assign weight to each feature , it uses features only for kernel construction and then
works in vector space spanned by vectors of kernel matrix, so you really can not determine weight for
each feature.

If you want weight for each feature you can use RegressionARD model


Get color-theme while server render

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

While ssr you can't get user system color theme. It not saved in cookie and browser don't send Sec-CH-Prefers-Color-Scheme
Like this #209, #204, #100
Describe the solution you'd like

Send Accept-CH: Sec-CH-Prefers-Color-Scheme on every request, and read Sec-CH-Prefers-Color-Scheme if it exist
Describe alternatives you've considered

Alternative you can save color-theme in cookie or combine this techniques
Additional context

We use code like this
const themeHeader = 'Sec-CH-Prefers-Color-Scheme';

serverInit(req: IncomingMessage, res: ServerResponse) {
  const cookies = Cookie(req, res);

  const systemTheme = req.headers[
    themeHeader.toLowerCase()
  ] as SystemThemeName;
  const userTheme = cookies.get(storeName) as ThemeName;

  if (systemTheme) this.systemTheme = systemTheme;
  if (userTheme) this.userTheme = userTheme;

  res.setHeader('Accept-CH', themeHeader);
},

Since I ran into this issue myself, I created my own version of this module but will slightly less functionality (doesn't support forcing color mode on specific pages).
However, it does support the Sec-CH-Prefers-Color-Scheme header and the preferred color mode is stored in a cookie instead of localStorage, thus it allows full SSR support.
https://github.com/Eschricht/nuxt-color-mode

Would be amazing to get @Eschricht 's implementation merged into this module.


Bug: different IP address in error message

I'm trying to connect <IP_ADDRESS> but the error message says it's failed to connect <IP_ADDRESS>

<IP_ADDRESS> is YOUR ip address (this is typical MySQL thing - by default you can't connect from any external IP address). You can use tunnel or you can ask your DBA to grant permissions to<EMAIL_ADDRESS>user or something liek that.


Tick version, rerendered if needed

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Need keystoneauth1 (ref. https://github.com/conda-forge/keystoneauth1-feedstock/pull/2)


Add lint: private plugin fn should be named only plugin

This style follows the convention of app.add_plugins((player::plugin, movement::plugin));

Just throwing my hat in :)
I'd argue module_plugin is arguably better naming. Yes, there is a bit of a "stutter", but there are tangible upsides.
When inspecting profiling tools, or something like bevy_mod_debugdump, visually functions are most often not given along with their full path, so only plugin will be shown, and needing to click through on every instance of plugin would be annoying.
IDE symbol search tools and "grepability" also are undeniably better with module_plugin. While one can still symbol search "plugin" and get all plugins, with module_plugin you can explicitly search for a single plugin without need to have them all listed, then visually scan the list for which files they are in.
If there is a panic/stack trace that for some reason doesn't have full debug symbols, the full path might not be down, so the information may be "a panic occurred in plugin".
Same with any kind of reflection/instrumentation that references the function name, just plugin won't be helpful without additional information.
My final thoughts are that it's a bit longer but for the above reasons it has upsides over just plugin, and I see no objective upsides for just plugin (discoverability is just as good), but would be happy to hear of any.

@tbillington thanks for the input! I have thought about these as well, so let me go through them.

When using profiling tools, or something like bevy_mod_debugdump, visually functions are most often not given along with their full path, so only plugin will be shown, and needing to click through on every instance of plugin would be annoying.

I don't believe any profiling tool actually prints the plugin names, though. Why would it? This argumentation is fully valid for systems, but IMO not for plugins

IDE symbol search tools and "grepability" also are undeniably better with module_plugin. While one can still symbol search "plugin" and get all plugins, with module_plugin you can explicitly search for a single plugin without need to have them all listed, then visually scan the list for which files they are in.

You can just grep for module::plugin and get the place where it is added in the "super plugin" one level above

If there is a panic/stack trace that for some reason doesn't have full debug symbols, the full path might not be shown, so the information may be "a panic occurred in plugin".

I don't think I've ever encountered a panic inside a plugin's .build that has a stack trace pointing to the plugin? Also, I believe that not having full debug symbols is a tradeoff a user is already taking with the full knowledge that debugability will suffer, so I don't think we should optimize much in this regard.

Same with any kind of reflection/instrumentation that references the function name, just plugin won't be helpful without additional information.

I don't believe there really is any reflection stuff for plugin functions? I think the instrumentation you care about is at the level of public plugins, which should be structs anyways

My final thoughts are that it's a bit longer but for the above reasons it has upsides over just plugin, and I see no objective upsides for just plugin (discoverability is just as good), but would be happy to hear of any.

By splitting your functionality into subplugins, most new files you create will start with the following boilerplate:
use bevy::prelude::*;

pub(super) fn plugin(app: &mut App) {
  todo!();
}

Having the same name everywhere enables you to use tooling like VS Code snippets to write plugin and have that autocomplete to the above. Any friction introduced in a process that is done in nearly every file is pretty damning imo and personally leads me to consider not splitting something into multiple files out of laziness. On a smaller note, for module_plugin, your super plugin will either look like this:
use bevy::prelude::*;

// It's common to have many subplugins in a game
mod foo;
mod bar;
mod baz;
mod quux;
mod something_else;

// boilerplate comes here
use foo::foo_plugin;
use bar::bar_plugin;
use baz::baz_plugin;
use quux::quux_plugin;
use something_else_plugin;

pub(super) fn plugin(app: &mut App) {
  app.add_plugins((
    foo_plugin,
    bar_plugin,
    baz_plugin,
    quux_plugin,
    something_else_plugin,
  ));
}

or the following
use bevy::prelude::*;

// It's common to have many subplugins in a game
mod foo;
mod bar;
mod baz;
mod quux;
mod something_else;

pub(super) fn plugin(app: &mut App) {
  // This is pretty ugly imo
  app.add_plugins((
    foo::foo_plugin,
    bar::bar_plugin,
    baz::baz_plugin,
    quux::quux_plugin,
    something_else::something_else_plugin,
  ));
}

again, the last point is fairly minor; there are worse things in life than foo::foo_plugin aesthetically. I mostly care about the boilerplate that goes into new files.

I hadn't considered stuff like renaming etc. honestly I'm happy with either suggestion at this stage. I'm sure if I start using it I'll be over it on like 5 seconds xD

Just wanted to add I appreciated the detailed write up ^^


Follow Electron's security guidance

We should be doing the things called out in the electron security docs as we're designed to load remote content, which could be insecure. ⚠

electronegativity is such a nice tool that we can use to spot security concerns.
To install:
npm install -g asar
npm install @doyensec/electronegativity -g

To run:
electronegativity -i .

that's awesome! can an action item for this work be to add that to run in our pipelines/build steps??

Yes, I'd love to do so but right now it has some bugs on my machine so let me spend some more time to investigate.

electronegativity v1.3 (latest) is using typescript-estree to parse typescript files. The version of TypeScript currently supported by this parser is 3.2.1 while ours is 3.5.2. Besides, I tried downgrading our version to 3.2.1 and it's still not running well and caused some false alarms.
Therefore, I think that we still need to do manually validation for electron security issues and re-visit this tool in the future when it's mature enough. Right now, we can follow their awesome security checklist here:
https://doyensec.com/resources/us-17-Carettoni-Electronegativity-A-Study-Of-Electron-Security-wp.pdf


Celery Async query execution timeout doesnt impact Superset queue while running big SQL statements parallelly

While DB async query execution is enabled and running SQL statements parallelly, the celery worker responds with a timeout after the SQLLAB_ASYNC_TIME_LIMIT_SEC is reached, however, Superset still keeps the process in a pending state and doesnt move into next task that is in waiting state(ready to execute)
Celery worker: celery worker --app=superset.tasks.celery_app:app --pool=prefork -O fair --loglevel=DEBUG --autoscale=50,1
SQLLAB_ASYNC_TIME_LIMIT_SEC = 300
RESULTS_BACKEND = RedisCache(host=CELERY_REDIS_HOST,
port=REDIS_PORT, key_prefix=CACHE_PREFIX)
Expected results
Once celery worker timeout, superset should exit the process and move to the next ready task
Actual results
superset waits for at pending state even though celery worker times out.
Screenshots

How to reproduce the bug

Enable Async query execution for a database, with celery workers.
Go to SQL lab and run a query that returns a result in say 3 minutes, run at least 5 tasks like this.
After timeout is reached, the Celery worker responds with a hard time out reached, exiting the process.
Superset UI still shows the process as in pending state.
Stop a pending query on Sql lab UI and run a small SQL( which returns the result immediately), Superset still shows the process in pending state and never gets the result back.

Environment
(please complete the following information):

superset version: 1.2
python version: 3.7
node.js version: v16.5.0
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ x] I have reproduced the issue with at least the latest released version of superset.
[ x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

@robdiciuccio @craig-rueda @dpgaspar

Closing this due to inactivity over the last couple years. If anyone can still repro this in current Superset, holler. We're happy to revisit/reopen.

Hello, still face the same issue here, any update?
Version: 4.0.1