wsk action invoke processImage action doesn't see uploaded Cloudant image IDs

How to determine what's not tying up properly?
wsk action invoke processImage -p imageId <image id> fails saying that
error: The requested resource does not exist.  even though all the debug sequences generated by ./bluepic.sh --install do work with that image id (with the exception of bluepic/processCallback - but it is not clear to me what are the correct arguments to this wsk. )
The log says nothing at all when I wsk action invoke processImage
The log  complains that bluepic/processCallback is
Unable to convert value of type Optional<protocol<>>:
file Foundation/NSSwiftRuntime.swift, line 269

local.env says
 # Kitura server
 export KITURA_host="barneyrt.mybluemix.net"
 export KITURA_port=80
 export KITURA_schema="http://"

Tags and weather are written to the Cloudant data when the debug sequences are invoked.
For more detail please see this StackOverflow question

I believe the issue is the quotes around both KITURA_host and KITURA_schema.   The sequence is just spitting back whatever error message it gets from Swift - in this case I'm pretty sure it's getting  a null response from the request to the Kitura server, which is the root cause of the Unable to convert value of type Optional<protocol<>>:  file Foundation/NSSwiftRuntime.swift, line 269 error message.
Here's what Mine looks like:
# Kitura server export KITURA_host=bluepic-dev.mybluemix.net export KITURA_port=80 export KITURA_schema=http://
When you look at the document in Cloudant, do you see that the weather conditions and tags have been written to the database?
I'm in the process of rewriting the sequence into an orchestrator action that will give us better error messages.

@triceam thanks.
This is the situation now:

the app does write a "person"  tag to the Cloudant  database
the app does write the location and weather conditions to the Cloudant  database
BUT the "person" tag doesn't show up as a button on theses IOS app
BUT $ wsk action invoke processImage -p imageId ef3c12d52ad264ad77e3501855efa61c gives error: The requested resource does not exist. (code 271368) where ef3c12d52ad264ad77e3501855efa61c is the _id of the db record tagged properly by the app upload
the OpenWhisk web console log shows { "imageId": "ef3c12d52ad264ad77e3501855efa61c", "response": "HTTP 200" } for kituraCallback at the timestamp of the IOS app uploading the image ... so this would confirm that the local.env is set up correctly.
BUT the OpenWhisk web console log shows nothing at all at the time of the failing wsk action invoke processImage
the error code does seem to be randomly generated. Two consecutive attempts to processImage will produce two different error codes ... not thatI'd know where to look for the codes' meanings ;-) so hopefully your new actions' error message will render more info

BTW I think I tried every export combination with and without quotes in local.env. Anyhow have reverted to no-quotes now and re-installed the actions and deployed the Bluepic server app again - results above subsequent to this.

@triceam Oh yes it does! In the time it took me to write the comment above and have a cup of tea the "person" tag appeared on the IOS app's info page of the uploaded image. Takes a fair time to get there.

The error "The requested resource does not exist" probably is coming from an issue communicating with the server - meaning it can't find the server.  The processCallback action is slightly different since its an intermediary step. Instead of imageId you need to pass in cloudantId:  wsk action invoke bluepic/processCallback -p cloudantId <cloudant id> -b

Yeah, the sequence takes a while if its doing a cold-start on the actions.   If you have the cloudant id, have verified the data gets persisted, and want to test the callback step faster, then just user processCallback like the comment  https://github.com/IBM-Swift/BluePic/issues/283#issuecomment-228384264

IF processCallback is successful, it pushes a notification to the client app immediately.  If not, the client app doesn't get updated data until that data is requested from the Kitura server again

@triceam thanks. Gradually getting my head around what's going on.


ext-imap

Describe the feature
ext-imap
Hi 👋
First of all thanks for your work on this 💟
I am currently stuck, because I don't really know how to install/enable the imap extension. Can you give me any hints?
Thanks
Btw currently I am trying to install imagick for all versions like this and want to install imap too:
#!/bin/bash

PHP_VERSIONS="7.4 7.3"

echo "Remove all available PHP configs"
rm -rf /usr/local/etc/php/*

brew install imagemagick

for version in $PHP_VERSIONS
do
    echo "Install PHP $version"

    brew reinstall shivammathur/php/php@$version
    brew link --overwrite --force php@$version

    echo "Extension: imagick"
    if ! pecl list | grep imagick >/dev/null 2>&1;
    then
        echo "Install and enable: imagick"
        yes '' | pecl install imagick
    else
        echo "Already installed, but enable: imagick"
        echo "extension=imagick.so" >> /usr/local/etc/php/$version/php.ini
    fi

    php -v
    php -m | grep imagick
done

symfony local:php:refresh
symfony local:php:list

Is there anything easier 😄
cc @localheinz

@OskarStark I would recommend using shivammathur/extensions tap. It now has both imagick and imap.
https://github.com/shivammathur/homebrew-extensions
PHP_VERSIONS="7.4 7.3"

echo "Add taps"
brew tap shivammathur/php
brew tap shivammathur/extensions

echo "Remove all available PHP configs"
rm -rf /usr/local/etc/php/*

for version in $PHP_VERSIONS
do
    echo "Install PHP $version"

    brew reinstall shivammathur/php/php@$version
    brew link --overwrite --force php@$version

    echo "Extension: imagick"
    brew reinstall shivammathur/extensions/imagick@$version
    brew reinstall shivammathur/extensions/imap@$version

    php -v
    php -m | grep imagick
    php -m | grep imap
done

symfony local:php:refresh
symfony local:php:list

Oh thank you very much, it works like a charm:
#!/bin/bash

PHP_VERSIONS="7.1 7.2 7.3 7.4 8.0"
EXTENSIONS="imagick imap"

echo "Add taps"
brew tap shivammathur/php
brew tap shivammathur/extensions

echo "Remove all available PHP configs"
rm -rf /usr/local/etc/php/*

for version in $PHP_VERSIONS
do
    echo "Install PHP $version with: $EXTENSIONS"

    brew reinstall shivammathur/php/php@$version
    brew link --overwrite --force php@$version

    for extension in $EXTENSIONS
    do
        echo "Extension: extension"
        brew reinstall shivammathur/extensions/$extension@$version
    done

    php -v
    for extension in $EXTENSIONS
    do
        php -m | grep $extension
    done
done

symfony local:php:refresh
symfony local:php:list

I will open another feature request for amqp which is a bit hacky now:
    echo "Extension: amqp"
    if ! pecl list | grep amqp >/dev/null 2>&1;
    then
        echo "Install and enable: amqp"
        yes '/usr/local/Cellar/rabbitmq-c/0.10.0' | pecl install amqp
    else
        echo "Already installed, but enable: amqp"
        echo "extension=amqp.so" >> /usr/local/etc/php/$version/php.ini
    fi

Sorry for reopening this PR, but I receive:

This is my current Script:
#!/bin/bash

# This is based on:
# * https://github.com/shivammathur/homebrew-php
# * https://github.com/shivammathur/homebrew-extensions

PHP_VERSIONS="5.6 7.0 7.1 7.2 7.3 7.4 8.1 8.0" # last one is used as default PHP version
EXTENSIONS="amqp imagick imap pcov redis"

echo "Add taps (--force-auto-update)"
HOMEBREW_DEVELOPER=1 brew untap shivammathur/php
brew tap shivammathur/php --force-auto-update
HOMEBREW_DEVELOPER=1 brew untap shivammathur/extensions
brew tap shivammathur/extensions --force-auto-update

echo "Remove all available PHP configs"
rm -rf /usr/local/etc/php/*

for version in $PHP_VERSIONS
do
    echo "Install PHP $version with: $EXTENSIONS"

    brew reinstall shivammathur/php/php@$version
    brew link --overwrite --force php@$version

    for extension in $EXTENSIONS
    do
        if [ "$extension" = "pcov" ] && { [ "$version" = "5.6" ] || [ "$version" = "7.0" ]; }; then break; fi

        echo "Extension: $extension"

        if [ "$extension" = "redis" ]; then
            brew remove redis@$version || true
            brew remove igbinary@$version || true
            brew remove msgpack@$version || true
        fi

        brew reinstall shivammathur/extensions/$extension@$version
    done

    php -v
    for extension in $EXTENSIONS
    do
        php -m | grep $extension
    done
done

symfony local:php:refresh
symfony local:php:list

Any clue?

@OskarStark
I had to fork imap-uw from homebrew-core into this tap as core no longer accepts patches to it.
Please run brew uninstall imap-uw as suggested by the error and then re-run your script.

This works, thanks!


Physics precision: lower fixed_delta_seconds does not necessarily improve precision

Carla Version: <IP_ADDRESS>, binary release tarballs
Environment: Ubuntu 20.04
Description
We tried to find an optimal (tradeoff between precision and performance) fixed_delta_seconds value for our reinforcement learning environments. We noticed however that a lower value does not always make the physics more sane, sometimes accelerations start to fluctuate heavily.
Consider the following code, which sets up a vehicle in a scene and makes it accelerate and brake, afterwards plots velocities and accelerations.
import carla
from math import sqrt

# initialise carla with our default map
client = carla.Client("localhost", 2000)
client.set_timeout(5)
world = client.load_world("Town06")

settings = world.get_settings()
settings.fixed_delta_seconds = 0.045
settings.synchronous_mode = True
settings.no_rendering_mode = True
world.apply_settings(settings)
blueprints = world.get_blueprint_library()

print(world.get_map().get_spawn_points()[1])

# spawn our favourite car
default_car = blueprints.find("vehicle.tesla.model3")
#position = carla.Transform(carla.Location(x=350, y=12.5, z=3), carla.Rotation(yaw=180))
position = carla.Transform(carla.Location(x=626.831238, y=-13.563108, z=0.300000), carla.Rotation(yaw=180))
vehicle = world.spawn_actor(default_car, position)

for i in range(20):
    try:
        world.tick()
    except:
        print("Skipped tick")

weather = carla.WeatherParameters(
    cloudiness=80.0,
    precipitation=30.0,
    sun_altitude_angle=70.0)

world.set_weather(weather)

# workaround unrealistic Carla phenomenas
physics_control = vehicle.get_physics_control()
physics_control.gear_switch_time=0.01
physics_control.damping_rate_zero_throttle_clutch_engaged=physics_control.damping_rate_zero_throttle_clutch_disengaged
vehicle.apply_physics_control(physics_control)
vehicle.apply_control(carla.VehicleControl(throttle=0, brake=1, manual_gear_shift=True, gear=1))
for i in range(9):
    try:
        world.tick()
    except:
        print("Skipped tick")

world.get_spectator().set_transform(position)

#exit()

# full throttle in the beginning
vehicle.apply_control(carla.VehicleControl(throttle=1.0))
print("Full throttle")
for _ in range(20):
    try:
        world.tick()
    except:
        print("Skipped tick")

# use norm of velocity and accel vectors (maybe try to disregard z?)
def norm(vector):
    return sqrt(vector.x**2 + vector.y**2 + vector.z**2)

# log all vehicle data in lists
accel_log = []
velocity_log = []
throttle_log = []
brake_log = []
z_log = []

# accelerate up to 20m/s and then apply throttle=0.82 to stay there until set location
throttle_changed = False
throttle = 1.0
while vehicle.get_location().x > 0:
    try:
        world.tick()
    except:
        print("Skipped tick")
    a = vehicle.get_acceleration()
    a_x = 0 if a.x == 0 else -norm(a)*a.x/abs(a.x)

    v = vehicle.get_velocity()
    v_x = 0 if v.x == 0 else -norm(v)*v.x/abs(v.x)
    if not throttle_changed and v_x > 20: # 20 40
        throttle = 0.475 # 0.48 0.77
        print(f"Apply throttle={throttle} and hold speed")
        throttle_changed = True

    vehicle.apply_control(carla.VehicleControl(throttle=throttle))

    accel_log.append(a_x)
    print(a_x)
    velocity_log.append(v_x)
    throttle_log.append(throttle)
    brake_log.append(0.0)
    z_log.append(a.z)

# now change throttle and brake to see the impact on the velocity
throttle = 0.0
brake = 0.0

print(f"Apply throttle={throttle}, brake={brake}")
vehicle.apply_control(carla.VehicleControl(throttle=throttle, brake=brake))

# break the loop at some coordinate or when the velocity is low enough
while vehicle.get_location().x > -300:
    try:
        world.tick()
    except:
        print("Skipped tick")
    a = vehicle.get_acceleration()
    a_x = 0 if a.x == 0 else -norm(a)*a.x/abs(a.x)

    v = vehicle.get_velocity()
    v_x = 0 if v.x == 0 else -norm(v)*v.x/abs(v.x)
    if v_x < 2:
        print("Vehicle stopped")
        break

    accel_log.append(a_x)
    throttle_log.append(throttle)
    brake_log.append(brake)
    velocity_log.append(v_x)
    z_log.append(a.z)
else:
    print("Vehicle has driven outside the test area")

import matplotlib.pyplot as plt

# first plot the velocities, accels, throttle and brake values by tick number (implicit indexing)
plt.plot(velocity_log, label="v")
plt.plot(accel_log, label="a")
plt.plot(z_log, label="z cooridnate")
# throttle and brake are scaled *10 to make them readable
plt.plot([10*t for t in throttle_log], label="throttle*10")
plt.plot([10*b for b in brake_log], label="brake*10")
plt.legend()

plt.show()

For settings.fixed_delta_seconds = 0.05 the plots looks as follows:

In detail:

For settings.fixed_delta_seconds = 0.045 the plots looks as follows:

In detail:

This looks clearly worse compared to the higher value. Also it is really bad compared to settings.fixed_delta_seconds = 0.02:

In detail:

Discussion
The fluctuations of the acceleration seems to be related to a tiny variation of z-coordinate of the map, however without a really small delta_second value this affects the reported accelerations values significantly which is really bad for our purposes. Even with
def norm(vector):
    return sqrt(vector.x**2 + vector.y**2)

i.e. leaving out the z-coordinate the results are similarly bad, thus the fluctuations are not due to the z-component of the acceleration!
Could you look into this, i.e. making the simulation more realistic even with bigger values for delta_second? Especially the oscillations happening really worry us. This is just a simple case which we tracked down, there might be many more unreliable situations in complex scenarios. We heavily rely on acceleration values and this affects as negatively since we have to make the delta_seconds value really low in order to reduce such phenomena.

I expect a productive discussion on this topic. @DSantosO please, when your plate is not too full, have a look at this.

Still an issue.

@DSantosO please, let's debug this

@DSantosO please, let's debug this

Hello @hh0rva1h,
Sorry about the delay.
Here we need to consider several points.
We need to consider that the acceleration that we provide from the API is not the 'real' acceleration because the physics solvers usually do not provide this variable. We compute it using a simple backward finite differences derivative using the previous velocity and the current one and dividing it by the delta time. The oscillations that you see are a usual problem when computing numerical derivatives and need to be addressed carefully.
Anyway, these oscillations should not be interpreted in any way as a problem with the physical simulation, only of the way of computing the acceleration. To check this, we should look at actual physical quantities like the velocity and the position, but I will come back later to that.
In your specific case, if you want to compute the acceleration in a more accurate way, you should do it as a post-process using the velocity and/or the position. You can take advantage that you are using a fixed delta time and use a more advanced numerical differentiation method. You can start checking central finite differences from the velocity that uses also two points but instead of the current, uses the next one and should be more stable. Also you have can try a second-order derivative from the position. Here you can check the simplest formulas. If those ones are not good enough you can try higher-order methods that involve more points but should give you better results.
The second important point is to understand what it means to decrease the delta time.
In CARLA we have two different types of delta time: the general one between render frames and the physics one. This is inherited from UE4 and PhysX and makes sense because if you want to use a dt of, let's say, 0.05s, the physical simulation would not make sense at all. For this reason, there are some physics substeps to compensate for that. In previous releases, the target physical dt was 0.016666s and now, since 0.9.11, it is by default 0.01s and can be configured via the API. Here and here you can check more about that. In this context, it is understandable that the oscillations were growing with the decrease of it. The physical dt on all your simulations were the same but the formula for computing the acceleration was worse).
I have prepared a couple of plots to show this based on a modified version of your script. They are not really convergence plots because I will need to synchronize the simulation a bit better but for matching everything but they are ok to have a broad picture.

This a plot of the velocity for several different dt.

For a constant dt=0.04 variating the physical dt with 1,2,4,8 physical substeps. Here you can see the errors that showed up when the physical dt is too high.

For the z-acceleration, it is a bit similar. With a constant dt (the one that we use to compute the acceleration), the same error as the velocity is there.

Hello @hh0rva1h,
Sorry about the delay.
Here we need to consider several points.
We need to consider that the acceleration that we provide from the API is not the 'real' acceleration because the physics solvers usually do not provide this variable. We compute it using a simple backward finite differences derivative using the previous velocity and the current one and dividing it by the delta time. The oscillations that you see are a usual problem when computing numerical derivatives and need to be addressed carefully.
Anyway, these oscillations should not be interpreted in any way as a problem with the physical simulation, only of the way of computing the acceleration. To check this, we should look at actual physical quantities like the velocity and the position, but I will come back later to that.
In your specific case, if you want to compute the acceleration in a more accurate way, you should do it as a post-process using the velocity and/or the position. You can take advantage that you are using a fixed delta time and use a more advanced numerical differentiation method. You can start checking central finite differences from the velocity that uses also two points but instead of the current, uses the next one and should be more stable. Also you have can try a second-order derivative from the position. Here you can check the simplest formulas. If those ones are not good enough you can try higher-order methods that involve more points but should give you better results.
The second important point is to understand what it means to decrease the delta time.
In CARLA we have two different types of delta time: the general one between render frames and the physics one. This is inherited from UE4 and PhysX and makes sense because if you want to use a dt of, let's say, 0.05s, the physical simulation would not make sense at all. For this reason, there are some physics substeps to compensate for that. In previous releases, the target physical dt was 0.016666s and now, since 0.9.11, it is by default 0.01s and can be configured via the API. Here and here you can check more about that. In this context, it is understandable that the oscillations were growing with the decrease of it. The physical dt on all your simulations were the same but the formula for computing the acceleration was worse).
I have prepared a couple of plots to show this based on a modified version of your script. They are not really convergence plots because I will need to synchronize the simulation a bit better but for matching everything but they are ok to have a broad picture.

This a plot of the velocity for several different dt.

For a constant dt=0.04 variating the physical dt with 1,2,4,8 physical substeps. Here you can see the errors that showed up when the physical dt is too high.

For the z-acceleration, it is a bit similar. With a constant dt (the one that we use to compute the acceleration), the same error as the velocity is there.

By the way, I forgot to mention that in the IMU sensor, we are providing a better approximation for the acceleration(using a second-order computation from the position of the sensor). It can also worth a try to check if this works for you, but any acceleration computed using the central differences formula should be better than any backward that we could provide in runtime.

By the way, I forgot to mention that in the IMU sensor, we are providing a better approximation for the acceleration(using a second-order computation from the position of the sensor). It can also worth a try to check if this works for you, but any acceleration computed using the central differences formula should be better than any backward that we could provide in runtime.

Hello @hh0rva1h, Sorry about the delay.
Here we need to consider several points. We need to consider that the acceleration that we provide from the API is not the 'real' acceleration because the physics solvers usually do not provide this variable. We compute it using a simple backward finite differences derivative using the previous velocity and the current one and dividing it by the delta time. The oscillations that you see are a usual problem when computing numerical derivatives and need to be addressed carefully. Anyway, these oscillations should not be interpreted in any way as a problem with the physical simulation, only of the way of computing the acceleration. To check this, we should look at actual physical quantities like the velocity and the position, but I will come back later to that. In your specific case, if you want to compute the acceleration in a more accurate way, you should do it as a post-process using the velocity and/or the position. You can take advantage that you are using a fixed delta time and use a more advanced numerical differentiation method. You can start checking central finite differences from the velocity that uses also two points but instead of the current, uses the next one and should be more stable. Also you have can try a second-order derivative from the position. Here you can check the simplest formulas. If those ones are not good enough you can try higher-order methods that involve more points but should give you better results.
The second important point is to understand what it means to decrease the delta time. In CARLA we have two different types of delta time: the general one between render frames and the physics one. This is inherited from UE4 and PhysX and makes sense because if you want to use a dt of, let's say, 0.05s, the physical simulation would not make sense at all. For this reason, there are some physics substeps to compensate for that. In previous releases, the target physical dt was 0.016666s and now, since 0.9.11, it is by default 0.01s and can be configured via the API. Here and here you can check more about that. In this context, it is understandable that the oscillations were growing with the decrease of it. The physical dt on all your simulations were the same but the formula for computing the acceleration was worse).
I have prepared a couple of plots to show this based on a modified version of your script. They are not really convergence plots because I will need to synchronize the simulation a bit better but for matching everything but they are ok to have a broad picture.
 This a plot of the velocity for several different dt.
 For a constant dt=0.04 variating the physical dt with 1,2,4,8 physical substeps. Here you can see the errors that showed up when the physical dt is too high.
 For the z-acceleration, it is a bit similar. With a constant dt (the one that we use to compute the acceleration), the same error as the velocity is there.

I'm curious about the relationship between frame time and physics sub-step time. If the frame time is 0.05 and the physics sub-step time is 0.01, will the physics be processed 5 times per frame? If the frame time is 0.2, will the physics stop processing after reaching the maximum sub-steps (10 in this case)?


Analysis of deterministic affine dynamics

Is this really not supported?
julia> b = [1.0]
1-element Array{Float64,1}:
 1.0

julia> prob = @ivp(x' = x + b, x(0) ∈ Singleton([1.0]))
InitialValueProblem{LinearControlContinuousSystem{Float64,IdentityMultiple{Float64},IdentityMultiple{Float64}},Singleton{Float64,Array{Float64,1}}}(LinearControlContinuousSystem{Float64,IdentityMultiple{Float64},IdentityMultiple{Float64}}([1.0], [1.0]), Singleton{Float64,Array{Float64,1}}([1.0]))

julia> sol = solve(prob, T=4.0)
ERROR: ArgumentError: the system type LinearControlContinuousSystem{Float64,IdentityMultiple{Float64},IdentityMultiple{Float64}} is currently not supported

Side note (probably an issue with MathematicalSystems):
julia> prob = @ivp(x' = -x + b, x(0) ∈ Singleton([1.0]))
ERROR: LoadError: Base.Meta.ParseError("\"*\" is not a unary operator")
Stacktrace:
 [1] @ivp(::LineNumberNode, ::Module, ::Vararg{Any,N} where N) at .julia/dev/MathematicalSystems/src/macros.jl:970
in expression starting at REPL[19]:1
caused by [exception 1]
Base.Meta.ParseError("\"*\" is not a unary operator")

Side note (probably an issue with MathematicalSystems):

yes, i think this one is reported https://github.com/JuliaReach/MathematicalSystems.jl/issues/194

i take back https://github.com/JuliaReach/MathematicalSystems.jl/issues/221 , that normalization does not apply (because U is the universal set, so discretization fails). on the other hand i think that the proper fix is to make the @ivp macro be more precise, as proposed in https://github.com/JuliaReach/MathematicalSystems.jl/issues/221

this is an alternative for the OP:
julia> A = hcat(1.0); b = [1.0];

julia> prob = @ivp(AffineContinuousSystem(A, b), x(0) ∈ [1.0]);

julia> sol = solve(prob, T=4.0);

So it is not a problem of this package, sorry. From my side this can be closed.

The OP is now fixed on the MathematicalSystems.jl side, and we can do
prob = @ivp(x' = x + [1.0], x(0) ∈ Singleton([1.0]))
sol = solve(prob, T=4.0)
plot(sol, vars=(0, 1))

i'll add this example as a test before closing the issue.


close stash and inventory simultaneously

This is going to be resolved in an upcoming fix I'm planning to redesign how the panels are laid out. I'm going to change GameScreen to have a LEFT and RIGHT panel which will act as "button" groups to control which single panel is shown there, or null for hide all panels. You can actually see in GameScreen that I've already added the fields, but I haven't implemented them. So, if you set RIGHT to inventory it will automatically hide anything there and unhide the inventory panel. It's my hope that during this I can also try and eliminate having soo many public fields to GameScreen members. There are too many public fields in most of the in-game related code because I haven't figured out a proper flow yet.


Crashes with sound channel increase.

Getting pretty frequent crashes when using anything greater than 16 for sound channels.
Client is 1.16.5 (7060)
Platform is Windows 10.
Release used is v1.6.0.
Also using https://github.com/hannesmann/vanillafixes v1.3 (DXVK).
Have also heard of others crashing when using vanilla-tweaks.
Perhaps setting the default sound channels to 64 is not a good idea?

Judging by the client version, you're playing on Turtle WoW, am I correct? Perhaps this is a new issue prompted by some new TWoW update, as >16 sound channels definitely used to be stable in the past.

Can confirm that, on a non-Turtle WoW client, >16 is still stable.

Owner

Judging by the client version, you're playing on Turtle WoW, am I correct? Perhaps this is a new issue prompted by some new TWoW update, as >16 sound channels definitely used to be stable in the past.

Yep, I am playing on turtle wow. Also I can't say for certain that the crashes are caused by increasing sound channels, but it definitely appears to be the case. I have tested with 32,64. And crashes can happen quite sporadically and consistently. I will do some testing without the dxvk version of vanillafixes.

I recently had also random crashes/freezes (playing on t-wow) and i wondered already why and how because it never happened before. Now i seen this threat here, will also try using only 16 channels for sound and report if i still have this freezes/crashes.
Was spending hours testing my hardware and scanned my memory cause i thought it's that, but it only crashed in WoW...

24 hours tested - no crashes anymore after reducing the sound channels to 16.... thanks at the post creator cause i thought its my hardware that is screwed.


Authenticate with custom endpoint over websockets

Same motivation as #278, but using websockets instead.  It was confusing that I could manually supply an endpoint using rest and it would be ignored if going over sockets.
This PR aims to do for websockets what #278 did for the rest provider, i.e., to allow the client to authenticate with a custom endpoint such as auth/facebook.

Is this PR made obsolete by #336 ?

Yeah but I wanted to get the docs and the client in order before I closed it so that I could explain why and how you can do what you want to do 😄

So let's keep this open as a reminder then, I'll be very grateful to be explained how to do this in 1.0. Thanks.

We haven't created a guide for it so would gladly take a PR to the docs for one, but you can easily change up the default path/endpoint on any of the authentication plugins that support it. All of the options are outlined in the docs.
For example, for OAuth2: https://docs.feathersjs.com/api/authentication/oauth2.html#default-options


Document maturity levels in sandbox

Add link to code of conduct, test Prow
Add test runner script (empty)
Document maturity levels in sandbox

@evankanderson looks like this PR needs a rebase :disappointed:


Icons missing in 0.50.2

I just checked the latest 0.50.2 version and it seems that icons are not displayed in buttons:

Ahh - sorry!
I was having problems with element-plus initialisation so I ended up removing that and fontawesome setup from the plugin (https://github.com/describo/crate-builder-component/commit/eaba93608a8eda6ab4e754f84f78091643206c15#diff-03797d0496d3cd9aa299f2dd7379185057c1d82d5efe28df40e27a2941f62e38). I added the element-plus css to the app but not the fontawesome imports (fixed by https://github.com/describo/crate-builder-component/commit/13664a8a9da881ad0015c3697efdcd709cd89099#diff-c40060953cc2aa01da23fa42fbbf3d196850091f87289a1f6ac8d71008342b65).
That said, I'm not sure how this will affect you in the react app. If we need to add this back in to the plugin initialisation code let me know.

Closing as this is fixed. If it causes issues in the react app please reopen.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 652

Questions ?
Please refer to the Backport tool documentation


[WIP] Porting of raven-js code

showReportDialog
wrap

_ignoreNextOnError
_handleOnErrorStackInfo

_patchFunctionToString
_instrumentTryCatch

fill (verify whether it's correct and update if necessary)
_breadcrumbEventHandler

htmlTreeAsString

_keypressEventHandler

_instrumentBreadcrumbs (w. options to enable/disable specific instrumentation through new BreadcrumbIntegration({ dom: false }) etc.)

_captureUrlChange
wrapConsoleMethod
attach missing mechanisms data

Codecov Report

Merging #1438 into master will decrease coverage by 10.87%.
The diff coverage is 46.97%.

@@            Coverage Diff             @@
##           master   #1438       +/-   ##
==========================================
- Coverage   82.37%   71.5%   -10.88%
==========================================
  Files          48      39        -9
  Lines        1901    1193      -708
  Branches      441     227      -214
==========================================
- Hits         1566     853      -713
- Misses        324     329        +5
  Partials       11      11

Impacted Files
Coverage Δ

packages/node/src/transports/base.ts
89.18% <ø> (ø)
:arrow_up:

packages/node/src/handlers.ts
21.59% <ø> (ø)
:arrow_up:

packages/minimal/src/index.ts
100% <100%> (ø)
:arrow_up:

packages/core/src/base.ts
98.78% <100%> (+1.21%)
:arrow_up:

packages/hub/src/hub.ts
98.36% <100%> (ø)
:arrow_up:

packages/node/src/parsers.ts
88.88% <100%> (+0.84%)
:arrow_up:

packages/utils/src/string.ts
17.77% <15%> (-2.23%)
:arrow_down:

packages/utils/src/supports.ts
42.1% <16.66%> (-4.77%)
:arrow_down:

packages/utils/src/is.ts
52.17% <50%> (-1.16%)
:arrow_down:

packages/core/src/logger.ts
62.5% <62.5%> (ø)

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 67afb24...93cb8b4. Read the comment docs.


Android crash Fatal Exception: java.lang.UnsatisfiedLinkError dlopen failed: library "libTrustWalletCore.so" not found

Describe the bug
Greetings! I released android app with wallet-core library and started to get a lot of crashes in crashlytics
Fatal Exception: java.lang.UnsatisfiedLinkError
dlopen failed: library "libTrustWalletCore.so" not found
Crash occurs at the beginning of the app in line
System.loadLibrary("TrustWalletCore")
To Reproduce
add line System.loadLibrary("TrustWalletCore") inside of onCreate of Application class
Expected behavior
Library is loaded successfully
Screenshots

Hi @taras1vovchenko, which version of TrustWalletCore do you use? How do you import TrustWalletCore in your app?
Are you able to reproduce the problem locally?
Did you take a look at the examples here: https://github.com/trustwallet/wallet-core/tree/master/android

Thanks for the response!
I used in production build version 4.0.11
I imported library using github packages
maven(
url = uri("https://maven.pkg.github.com/trustwallet/wallet-core")
) {
credentials {
username = "..."
password = "..."
}
}
Everything was set up step-by-step by your guide.  I've tried to launch and test the app on several devices, but I didn't have any issues with the library. I checked your official example and a few other examples on GitHub, and I have almost the same code

Hi @taras1vovchenko, probably, there is a mistake in android package config.
@AndrewChupin if you have time, could you please advice what could be the problem?


⭐ Add Age-Calculator and README.md file

Age Calculator
Age-Calculator is a kotlin based android application
Tech

Kotlin language
xml language
Android Studio

Hey @Suryansh1720001
your app is not visible in changes please check
https://github.com/aadityamp01/Androapps/pull/109/files

Hello @aadityamp01
Yes, that was the issue of the submodule. Now Please check the changed files will show there only.
Thank you

Hello @aadityamp01
Please merge it, if you satisfy with this.
Thank you

Hey @Suryansh1720001
Thanks for your contribution into Androapps!


Power Platform CLI doesn't delete files when using pac solution unpack

When I export and unpack a solution that has had an entity removed from it into a directory that contains a previously extracted solution contents the files for the the contents don't get deleted even though I gave it the --allowDelete flag.
Steps to reproduce:

Create a solution and add an entity to it
Export the solution
Unpack it using pac solution unpack --zipfile solution.zip --allowDelete --allowWrite --clobber
Remove the entity from the solution
Export the solution again
Unpack it again using pac solution unpack --zipfile solution.zip --allowDelete --allowWrite --clobber

The command output says that it is deleting files

Expected result
The folder for removed entity gets removed from under Entities/
Actual result
The folder still exists for the entity under Entities/ and still contains all the metadata files
Installed Version: 1.25.5+g24fc1f8
OS: Ubuntu 20.04

Unable to repro with these steps. Are you sure you published your customizations and there is no entity in second solution.zip?

Yes it didn't show up on the customizations.xml file. I'm going to try to replicate it again to make sure I'm not crazy

Unfortunately, PAC CLI code is not open sourced. What Linux version are you using? We usually test on Ubuntu WSL.

I'm using Ubuntu 22.04 with .net 7.0.306 and I installed the tool from the nuget package Microsoft.PowerApps.CLI.Tool
Let me know if there any other details that would be helpful. I also have a recording of the issue occurring if that is helpful for you.

If you run pac telemetry status, it will show you location of log file. Can you attach it or copy relevant block of logs?

Here are the logs from my most recent run
paclog.txt

Unable to repro it on latest version. Feel free to reopen if this is still an issue

Brilliant! Thank you!


fcas_semi_scheduled may be empty

Hi,
Great library, thanks for writing it and making it accessible to everyone.
I think there may be an issue in running earlier years that don't feature semi scheduled gens offering FCAS.
To reproduce what I think is the error, you can run the example code in README and substitute references to 2019 with 2015. I get an error in units._scaling_for_uigf which seems to arise because the fcas_semi_scheduled data frame is empty.
My workaround was to add a check for whether the data frame was empty:
    if not fcas_semi_scheduled.empty:
        # Scale high break points.
        fcas_semi_scheduled['HIGHBREAKPOINT'] = \
            fcas_semi_scheduled.apply(lambda x: get_new_high_break_point(x['UIGF'], x['HIGHBREAKPOINT'],
                                                                         x['ENABLEMENTMAX']),
                                      axis=1)

        # Adjust ENABLEMENTMAX.
        fcas_semi_scheduled['ENABLEMENTMAX'] = \
            np.where(fcas_semi_scheduled['ENABLEMENTMAX'] > fcas_semi_scheduled['UIGF'],
                     fcas_semi_scheduled['UIGF'], fcas_semi_scheduled['ENABLEMENTMAX'])

        fcas_semi_scheduled.drop(['UIGF'], axis=1)

        # Combined bids back together.
        BIDPEROFFER_D = pd.concat([energy_bids, fcas_not_semi_scheduled, fcas_semi_scheduled])
    else:
        # Combined bids back together.
        BIDPEROFFER_D = pd.concat([energy_bids, fcas_not_semi_scheduled])

The tests I have done so far are very close to what NEMDE produces so all seem to be working.
Happy to look at it more and submit a PR if helpful.

Hi @andrewhn
No worries, glad your finding it interesting.
Thanks for pointing out this problem, investigating, and suggesting a fix.
Interesting that it's never come up as an issue before, I would have thought there'd be times in 2019 when no semi scheduled units were bidding into FCAS.
If you want to investigate further and submit a PR that would be really appreciated, otherwise I will try and look at it after addressing #6
Cheers,
Nick

@andrewhn this should be fixed in the latest release, update with pip, see notes here: https://github.com/UNSW-CEEM/nempy/releases/tag/v1.1.3


Start keying connection pools off SSL arguments as well.

This is a proposed patch that begins to implement the requirements for kennethreitz/requests#2863. In particular, it adds hooks to provide additional keyword arguments as part of the key for the connection pool.
There are some outstanding questions. For example:

should we actually just use all the connection pool keyword arguments as part of the key? Why are headers et al exempt?
Are we happy with this API, where connection_from_host picks up the new argument but connection_from_url does not?

Code review encouraged, please. :custard:

headers are handled on a per request, not per connection basis, so there's no reason they need to be included.

@alex Well, that's true-ish, but we have parameters that are added by default to all requests through a given ConnectionPool.

Any feelings about generalizing this beyond SSL?
I'm imagining people might want to key based off sessions (some internal header-related value), resolved ip (as opposed to hostname), source address (a few people brought this up #376), others?
Not sure how many of these usecases we can cover at once, but worth considering while we're touching this part of the plumbing.

Are we happy with this API, where connection_from_host picks up the new argument but connection_from_url does not?

When I wrote these, they were shortcut helpers for fairly specific flows. I'm open to expanding them, or adding more, or getting rid of them.

Any feelings about generalizing this beyond SSL?

It should be trivial to generalise to anything that is in connection_pool_kw, and probably to headers as well. My bigger concern is: will that be too many things?

I'm imagining something like:
def connection_from_key(self, *args):
    ...

def connection_from_request(self, <a bunch of request context>):
    ... logic you can override to convert to a connection_from_key call of your desire

Possibly as a callable you pass instead, whatever makes more sense.

Yeah, that can totally work. Would those be in addition to connction_from_url/connection_from_host?

Probably? ¯\_(ツ)_/¯

So the problem with connection_from_key is that, if it needs to create a new ConnectionPool, it needs to know the scheme, host, and port. Given that we already have a method that basically has that signature (connection_from_host), I think we should either consider changing the name of that method or just accept that that is the base method for keying.
So, in the short term I'm just going to do a small refactor that means we pass all of the relevant connection_pool_kw. I'll also not going to key off headers because they don't actually get set on the relevant ConnectionPool, so it doesn't really matter. This means we'll be keyed off:

scheme
host
port
strict
default timeout
default retries
maxsize
block
arguments that are applied directly to connections (including the SSL ones)

I think that's probably sufficient for now. =)

Ok, I've uploaded a change that does this. It might be a bit heavyweight, so I haven't focused on exhaustively testing it yet, but I'd love feedback. =)

Hm I think this might be going in the wrong direction, we need to go more towards treating a pool as a cache. This means we'll probably need to provide a key (which should strictly be a flat tuple IMO) and a callable that returns a new value (a fn() -> ConnectionPool).
I'm not a fan of the automagically-keying-off-a-bunch-of-things-based-on-the-scheme approach right now. It's starting to look like a half-way adapter registry (not that it's bad, but we need to commit to some direction I think).
For now, I'd be happier with PoolManager having a scheme-based if-statement which replaces the default HTTP tuple key with one that includes more HTTPS-specific stuff.
Does that make sense? Sorry for the fairly vague feedback. :P

@shazow So, can you look back at the commit prior to the HEAD of this branch and confirm whether that looks closer to what you wanted?

Bits that I'd like to avoid:
ssl_kwargs = frozenset(ssl_kwargs.items())

I'd like to avoid the key being a recursive structure. I think it should be a flat well-defined set of values that we're keying on in specific scenarios. Maybe we should even have a set of helpers for each scenario, where given request context it will generate the appropriate key.
One big problem here is that urllib3 still doesn't have a notion of request contexts (or pre-built requests) so serializing that context is tricky. It's also something we need for retry history.
        ssl_kwargs = {
            k: v for k, v in self.connection_pool_kw.items()
            if k in SSL_KEYWORDS
        }

Maybe, at the least, we need some idea of a hashable SSL configuration context? Wiring all of these random SSL-related keywords to be further propagated is likely to yield more pain in the future, especially if some of these values become transient or don't really affect the request itself (but rather just the validation configuration).

So I agree about flat being better than nested. Absolutely. The problem is creating a key that's immutable that the dictionary will know is immutable and it won't barf on. Using a list or dictionary inside a tuple does not an immutable key make.
Also, perhaps since the key object is growing so potentially long, we should look at using a namedtuple simply to make things easier to reason about when handling the keys.

Yeah, if we're moving to a flat structure we're definitely moving to namedtuple. This is frankly more for debugging reasons than anything else: it'll be a bloody nightmare to work out what's going on in a large tuple of random-ish values and easy to subtly get wrong.

Yea, urllib3's internal keying should be well structured and defined, but I'm expecting we'll want to allow third parties to change the keying to their own needs. Or maybe this is over-generalizing.

we'll want to allow third parties to change the keying to their own needs

Does anyone do this now? I'm not sure I see a need for it.

See https://github.com/shazow/urllib3/pull/751#issuecomment-160181929

Would it be possible to have a ruling on a direction to take? I've been hitting this issue while using requests and I'd really like to fix it, but until I know what's going to happen with this patch, there's not much I can do :smile:

@jeremycline Would you be interested in putting together a draft PR for review with the feedback we talked about? Unfortunately we're all pretty busy right now so I'm not sure this issue will move forward on its own any time soon.
Alternatively, could always add a bounty and see what happens. :) If you want to do that, I'd recommend opening a separate umbrella issue for the bounty specifically.

No worries, I completely understand being too busy. I'm happy to give a PR a shot. I should have something that's worth an initial review in the next few days.

Hey everyone in this thread, please take a look at #830 which we're quite happy with as a solution but if you have feedback then now is the time. :)

We can close this in favour of #830 at this point.


Add use-debounce package, debounce shipping and billing country fields

Fixes #22

THANKS! haha just took the example from the shipping integration


[VideoConferenceMute] Plugin is missing on 20H2 installation

Installed today and video conference mute is missing:
ℹ Computer information

PowerToys version:
PowerToy Utility: v0.33.1
Running PowerToys as Admin: Yes
Windows build number: [run "winver"] 19042.867

📝 Provide detailed reproduction steps (if any)

Upgraded from v.0.16.x to 0.33.1 it was missing
uninstalled reinstalled fresh
…

✔ Expected result
option would appear
❌ Actual result
There is no video conference mute visible or installed
📷 Screenshots

@seanmcne
that is expected since it's not in the stable release yet.

Ok got it - the release notes mentioned an experimental release for .33/.34 the week of march 8th so I figured that was the release (as it was 3/22).  I see now that only the releases titled Experimental will include it - thx!

@seanmcne
we had some technical delays.


links parsed twice + nested if href == content?

[http://www.facebook.com/developers/](http://www.facebook.com/developers/)

gives

http://www.facebook.com/developers/

should be

http://www.facebook.com/developers/

It's because of GFM. GFM takes urls and spits out links. If you just want a link that displays the url, put: http://www.facebook.com/developers/.

if i were making it, i would indeed just use a plain url. however, i'm feeding it markdown others have made. i understand this happens as a consequence of extra GFM handling, but does that make it correct?
http://www.facebook.com/developers/
^^ not mis-parsed @ Github, which supports GFM also ^^

there may actually be a perfectly valid use-case for this, because GFM links don't allow you to customize the title attr of the link. like this: http://www.facebook.com/developers/
via
[http://www.facebook.com/developers/](http://www.facebook.com/developers/ "moooooooooooo")

Lately I have been wanting to make GFM optional. Maybe have 4 different switches total:

pedantic: pure 100% conformance in every area. original markdown bugs/poor-behavior is preserved.
improved: marked's current improved behavior, which would enable a lot of the smarter behavior in marked.
gfm: github flavored markdown.
sanitary: sanitize output. don't output any html.

But I don't want to amend any inline processing just to exclude a gfm link nested in an md link.

I've been playing around with a local branch for a little bit now. I've implemented pedantic, gfm, and sanitize so far. I sort of like it. I think I might just keep it.

that sounds good. in the meantime i've upped my DOM > markdown proj. check it out if interested https://github.com/leeoniya/reMarked.js :D
thanks for your help with the barrage of issues i've opened here, too.


Inconsistent focus style

The border highlighting focused elements in Tobira is pretty inconsistent. Sometimes, you have rounded edges, sometimes you have not. Sometimes you have padding, sometimes you have not. Being consistent would be nice.
Example:

Yeah, this pained me for a while now. I'm still unsure how to best fix it. For one, browsers have built-in focus styles that are used if not overwritten.
I would like a solution that just applies to (almost) everything. Otherwise, if we need to adjust it for every single UI element, we will always forget something and this issue will pop up again all the time. Anyone solving this issue should keep that in mind and think of how to define it as generally as possible.
There are two main problems that stopped me from writing a super easy general solution:

Elements which have overflow: hidden can't have an outline outside of them. So they need an outline-offset: -2px or sth like that. But do we want that inset outline for all elements?!  :D
Elements with rounded corners look bad when the outline is not rounded. That's usually not a problem except for elements like in the main navigation where the border radius is in the container, which also has overflow:hidden which only "cuts away" stuff from the first and last element. Currently we solve it like this:"& > li:last-child > a": {
    borderRadius: `0 0 ${SIDE_BOX_BORDER_RADIUS}px ${SIDE_BOX_BORDER_RADIUS}px`,
},
"&:first-child > li:first-child > a": {
    borderRadius: `${SIDE_BOX_BORDER_RADIUS}px ${SIDE_BOX_BORDER_RADIUS}px 0 0`,
},

But this is obviously suboptimal as it's again something one has to do for these elements individually. Not sure if there is a good solution, to be honest.

One learning that I had over time is to use overflow: hidden as little as possible. But I don't think it's possible to avoid everywhere.

I think focus styles have improved a lot thanks to @owi92. As far as I can see, the only obvious things remaining are the focus ring around normal links (in text boxes and in the breadcrumbs). Those need to be rounded and maybe have a bit more padding (i.e. outline-offset).


Update Postgres Plugin for dbt-duckdb to Use ATTACH Syntax and Improve Compatibility

Description:
This pull request updates the Postgres plugin for the dbt-duckdb adapter to align with the latest DuckDB PostgreSQL extension (ATTACH syntax) and introduces improvements to functionality, testing, and error handling.
Changes Made:

Migration to ATTACH Syntax:

Replaced the deprecated CALL postgres_attach syntax with the new ATTACH command, returning the write-to-pg functionality.
Removed deprecated features like overwrite in favor of READ_ONLY.

Enhanced Configuration:

Added support for configuring additional attach options and extension settings, ensuring compatibility with the latest DuckDB Postgres extension features.

Improved Logging and Debugging:

Utilized AdapterLogger to provide clearer and more detailed error messages.
Enhanced traceability of plugin configuration and database attachment processes.

Updated Unit Tests:

Refactored and extended test coverage to validate new functionality and edge cases:

Successful ATTACH with default and custom configurations.
Read/write operations in both read-only and read-write modes.
Handling of PostgreSQL arrays and error conditions for invalid configurations.

Code Refactoring:

Improved code readability and maintainability by introducing helper methods (_set_extension_settings, _build_attach_statement).
Added type annotations for better developer experience and debugging.

Testing:

Verified all test cases pass successfully:

✅ 8 tests executed covering all key scenarios.
🔧 Addressed issues with outdated PostgreSQL array handling and error messages.

All changes validated against DuckDB version 1.1.3.

Impact:

Ensures compatibility with DuckDB’s latest PostgreSQL extension.
Improves user experience with better logging, clearer error messages, and broader configurability.
Streamlines the plugin's codebase for easier maintenance and future updates.

Checklist:

[x] Updated postgres.py to support ATTACH syntax.
[x] Updated test_postgres.py to reflect new features and configurations.

Related Issues:
Unfortunately, due to this issue the testing has to be done outside the VSCode dev container.
#478

Please review the changes and let me know if additional updates or refinements are needed. Thank you for your time and consideration!🚀

related to #478

opened a new PR


[Grid] Grid with flexDirection column collapses in combination with TextField components

When using the Grid component with flexDirection="column" the inner Grid items collapse occasionally when switching between TextFields, but also on mount.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
The grid collapses randomly after making a selection in a Select component or TextField with select prop. This also happens on mount.

Expected Behavior 🤔
Grid children with the xs prop should be and stay fullwidth. A workaround for now is to add {width:'100%'} style to the grid children. I'm pretty sure this issue wasn't present in earlier versions.

Steps to Reproduce 🕹
https://codesandbox.io/embed/charming-driscoll-73nb6
Create a grid like so:
<Grid container flexDirection="column">
  <Grid item xs>
    <TextField />
  </Grid>
  <Grid item xs>
    <TextField select />
  </Grid>
</Grid>

And input some text in the normal input. Then enter a select value and go back to the regular text input.

Context 🔦
Creating a full width grid for forms.

Your Environment 🌎

Tech
Version

Material-UI
v4.4.3

React

Browser

TypeScript

etc.

See #16912

Thanks. Struggling with the same. Did not know about the issue on Chromium


[PE-D][Tester C] Ui of the application could be more user friendly

the not completed and completed panes are quite small and require a lot of scrolling of left right up and down

Labels: type.FunctionalityBug severity.Low
original: danzzzerl/ped#6

The UI card is as is and thus a feature flaw.

The UI card is as is and thus a feature flaw.


Cluster workers not being able to pick up Jobs / double pick up

The following program will create two cluster workers, then one job task. The job task will be marked as failed immediately. Every second the job is marked back as inactive which should be picked up again by a single worker. However occasionally more than one worker is picking up the job cause it to be executed twice.
Is there something wrong with my logic or is this an issue with the cluster implementation in kue?
var kue = require('kue');
var jobs = kue.createQueue();
var cluster = require('cluster');

if(cluster.isMaster){
    cluster.fork();
    cluster.fork();
    jobs.create('test').save();

    setInterval(function () {
        kue.Job.rangeByState( 'failed', 0, -1, 'asc', function( err, jobs ) {
            if(err){
                console.log(err);
            }
            else{
                jobs.forEach( function ( job ) {
                    job.state('inactive').save();
                });
            }
        });
    }, 1000);
}

if(cluster.isWorker){
    jobs.process('test', function ( job, done ) {
        console.log('worker' , cluster.worker.id + ' has control of: ' + job.id + ' | ' +  new Date());
        done('failed');
    });
}
else{
    jobs.on('job failed', function ( errorMessage ) {
        console.log('Job failed');
    })
}

When running the following program the jobs are eventually are not picked up at all.
Note: The done call is never called in this example which causes the state of the jobs to be changed from active to inactive. Instead of failed to inactive like the previous example.
var kue = require('kue');
var jobs = kue.createQueue();
var cluster = require('cluster');

if(cluster.isMaster){
    cluster.fork();
    cluster.fork();
    jobs.create('test').save();

    setInterval(function () {
        kue.Job.rangeByState( 'active', 0, -1, 'asc', function( err, jobs ) {
            if(err){
                console.log(err);
            }
            else{
                jobs.forEach( function ( job ) {
                    job.state('inactive').save();
                });
            }
        });
    }, 1000);
}

if(cluster.isWorker){
    jobs.process('test', function ( job, done ) {
        console.log('worker' , cluster.worker.id + ' has control of: ' + job.id + ' | ' +  new Date());
    });
}
else{
    jobs.on('job failed', function ( errorMessage ) {
        console.log('Job failed');
    })
}

Can you check this against v1 branch also?

@behrad Running the same program throws the following error:
TypeError:  kue.Job.rangeByState is not a function
    at null._repeat (/Users/test/clusterTest.js:18:13)
    at wrapper [as _onTimeout] (timers.js:275:11)
    at Timer.listOnTimeout (timers.js:92:15)

Sorry I've n't created a migration check list yes, rangeByState is moved to queue object :)

@behrad
Changing to kue.rangeByState(..) throws an error as well.
TypeError: kue.rangeByState is not a function

queue = createQueue()
queue.rangeByState...

Same problem is happening as I initially stated:

However occasionally more than one worker is picking up the job cause it to be executed twice.

Note that only a maximum of 2 workers ever pick up the job regardless of how many there are.

@behrad
Has there been any process on this issue?

To be clear, if workers are triggered from a stand alone proc ie node worker.js this is not an issue?

Seeing this regularly now with 2 worker processes, v0.11.1, v0.11.2, and master. Haven't migrated to v1 yet to test

@JperF Have you found the solution?

Hey @victornikitin,
Unfortunately I have not looked into this for more than 2 years. So I am not sure where Kue's code stands nor if this is still an issue.


is this possible to modeling multi turn dialog.......here is new dataset

https://nlp.stanford.edu/blog/a-new-multi-turn-multi-domain-task-oriented-dialogue-dataset/

@loveJasmine haven't looked into this dataset but I would guess it should work, just need to change the data preprocessing so the particular dataset.


Improve content with an example from the provided reference

Improve content of the page with the example available in the following link:
https://cloudarchitected.com/2020/01/using-azure-ad-with-the-azure-databricks-api/
Thanks Alexandre Gattiker for the amazing post! He works for Microsoft.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 088dd54c-b5ef-2e6d-1fe7-8035bdec6ba5
Version Independent ID: 8fb82d4a-f93a-6d49-9cd0-632acb019c90
Content: Authenticate using Azure Active Directory tokens - Azure Databricks - Workspace
Content Source: databricks/dev-tools/api/latest/aad/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@emerrf Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

We have filed a ticket in the Databricks bug tracking system: DOC-2984
We will update this Git issue when the ticket has been resolved. #label:"in-progress".


Correct spelling mistakes

There are some spelling mistakes on the homepage like

"collaborate" instead of "colloborate" is used.

This is one I can found. There could be many.

I'll take a look and fix any I'll find.

Thanks @murkythunder. Feel free to ask if you face any problem with the setup or anything.


Change Music datagen to read from file and add songs

@confluentinc It looks like @ybyzek just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

Thank you for your help @mjsax .  Now that it is committed into 4.0.0-post, do I need to run pint merge?  Or will it automatically propagate to 4.1.x?


Set the Tika server path automatically

Hello,
how can i avoid downloading tika server every time my applications starts?
I would like to download the server and set the path.

See https://github.com/chrismattmann/tika-python#environment-variables specifically number 8, I think that's what you are looking for.


Lifecycle dependencies need to be updated to 2.6.0 they have conflicts with 2.5.1

Same as https://github.com/skydoves/PowerMenu/issues/103

Resolved in the new version 1.2.6. Thanks for reporting this issue!


Update index.md

lodash didn't load properly in your example I updated it in a forked fiddle

Thanks! It looks like unpkg.com has fixed this issue now, so the original example should work again. In the future, we'll probably move our CDN links back to jsDelivr now that they support NPM builds.


Add deprecated message to varlink command

Signed-off-by: Jhon Honce<EMAIL_ADDRESS>

Agree with the deprecation message, but also think we should mark this as hidden to try and force people to podman system service --varlink

LGTM

/lgtm


Does slack-term updates your online status to others?

Hello!
First of all, thanks for this amazing project!
I've been using slack-term for a long time and some coworkers noticed that I'm always "offline" (just the green orb on the names).
I was wondering if slack-term handles it, and if not if it's possible.
I possible I could do it :smile:

Hey, thanks man! No you're right it should be set, I'll have a look if I'm able to reproduce it.


Cypress component tests fail to run when using @react-data-table-component -- ^7.5.2 @styled-components: ^5.3.5

Current behavior
Running Cypress component tests (Cypress ^10.3.0) results in the following error message for all the tests:
"Cannot read properties of undefined (reading 'REACT_APP_SC_ATTR')"

at <unknown> (http://localhost:3000/__cypress/src/node_modules/.vite/deps/react-data-table-component.js?v=22eeef94:649:56)

Desired behavior
The cypress component tests should run correctly
Test code to reproduce
 "@cypress/react": "^6.0.0",
 "cypress": "^10.3.0",
 "vite": "^2.9.9",
"react": "^18.1.0",
"react-data-table-component": "^7.5.2",
 "styled-components": "^5.3.5",

ISSUE COULD BE BECAUSE OF
https://github.com/styled-components/styled-components/blob/main/packages/styled-components/src/constants.ts#L5

No response

Have you made cypress configuration for react with vite?
https://docs.cypress.io/guides/component-testing/component-framework-configuration#React-with-Vite

yes
On Wed, Sep 7, 2022 at 10:18 PM kaungsithar @.***>
wrote:

Have you made cypress configuration for react with vite?
https://docs.cypress.io/guides/component-testing/component-framework-configuration#React-with-Vite
—
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/3775#issuecomment-1239640697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZOMFJDUFZXLOFHOFUBN6HTV5DBORANCNFSM54HJXGEA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Since Cypress runs in Browser environment, it does not have access to node.js's process.env.
We can put virutal process.env variable for cypress tests. Since you are running component tests, we can put following workaround in /cypress/support/component.js
process = process || {env:{}};
process.env = process.env || {};

I have added vite-define-envs-plugins
and added this in plugins
new viteDefineEnvs(["REACT_APP_SC_ATTR", "SC_ATTR"], "process.env")


Tango Application Crashes on rapid motion of the device

Tango Application Crashes on rapid motion of the device.

Is this with the Tablet dev kit or with a Phab2 Pro?

Tab dev Kit

Thanks! This is a duplicate of #52, which we are looking into.


Tagging accounts

Before submitting an issue, make sure you have:

[x] Updated to the lastest version
[x] Read the README
[x] Searched the bugtracker for similar issues including closed ones
[x] Reviewed the sample code in tests and examples

Describe your Question/Issue:
Is there a way to tag accounts on the pictures we post via instabot?

no not yet but feel free to make a pull request!


<ibm-content-switcher state is not correct when there are two or more <ibm-content-switcher

I have two <ibm-content-switcher in my page, when I click the first switcher, the another switcher state is not correct

Could you provide a repro codesandbox/stackblitz, or otherwise some code to reproduce. Testing locally, it seems like I can have as many content switchers, with seperate values, as I like.

all tabindex of the button is -1

Right, I still can't reproduce this locally.
the following code in the storybook works as expected:
<ibm-content-switcher (selected)="selected($event)">
	<button ibmContentOption name="First">First section</button>
	<button ibmContentOption name="Second">Second section</button>
	<button ibmContentOption name="Third">Third section</button>
</ibm-content-switcher>

<ibm-content-switcher (selected)="selected($event)">
	<button ibmContentOption name="Second">Second section</button>
	<button ibmContentOption name="Third">Third section</button>
</ibm-content-switcher>

A full code sample, codesandbox, or stackblitz would help debug this situation.
(This link will give you a stackblitz to start from https://stackblitz.com/fork/carbon-angular-base)

when I select one of the content switch, another is not selected

Could you share the link here? It's still not clear to me how this is happening.

@cal-smith https://stackblitz.com/edit/carbon-angular-base-vvtwfe?file=src%2Fapp%2Fapp.component.html

just add these codes below:

Value1
Volume1

Value2
Volume2

just add these codes below:
`
Value1
Volume1

Value2
Volume2
`

@cal-smith is it a bug?

Can't reproduce and long time passed since the last update to the issue, so closing. Feel free to reopen with reproduction step if still relevant.

Can't reproduce and long time passed since the last update to the issue, so closing. Feel free to reopen with reproduction step if still relevant.


ConditionalPriorDict: fix subset sampling for external 'DeltaFunction' dependencies

[I have no write access on the gitlab repo, so using this as a 'proxy']
Conditional priors cannot be sampled from in a subset if one of the conditional dependencies is outside of the sampled set. This makes sense if that outside dependency has any 'uncertainty' (ie its prior is not fixed/DeltaFunction), but should actually work fine if the dependency outside the subset is fixed or a DeltaFunction.
Code example showing this
#!/usr/bin/env python3
import numpy as np
from bilby.core.prior import (ConditionalPriorDict, ConditionalUniform,
                              IllegalConditionsException, Uniform)

def _tp_conditional_uniform(ref_params, period):
    min_ref, max_ref = ref_params["minimum"], ref_params["maximum"]
    max_ref = np.minimum(max_ref, min_ref + period)
    return {"minimum": min_ref, "maximum": max_ref}

p0 = 68400.0
prior = ConditionalPriorDict(
    {
        "tp": ConditionalUniform(
            condition_func=_tp_conditional_uniform, minimum=0, maximum=2 * p0
        )
    }
)

# ---------- 0. Sanity check: sample full prior
prior["period"] = p0
samples2d = prior.sample(1000)
assert samples2d["tp"].max() < p0

# ---------- 1. Subset sampling with external delta-prior
print("Test 1: Subset-sampling conditionals for fixed 'externals':")
prior["period"] = p0
try:
    samples1d = prior.sample_subset(["tp"], 1000)
    assert samples1d["tp"].max() < p0
    print(f"OK.")
except IllegalConditionsException as e:
    print(f"FAIL ==> Should work, but caught exception: {type(e).__name__}: {e}")

# ---------- 2. Subset sampling with external uniform prior
prior["period"] = Uniform(minimum=p0, maximum=2 * p0)
print("Test 2: Subset-sampling conditionals for 'external' uncertainties:")
try:
    samples1d_fail = prior.sample_subset(["tp"], 1000)
    print("This should not work!")
except IllegalConditionsException as e:
    print(f"OK. ==> Correctly failed, caught exception: {type(e).__name__}: {e}")

The attached commit fixes this. The fix works by including all DeltaFunction priors in the subset ConditionalDict, but still only sampling from the requested keys.
0001-ConditionalPriorDict-fix-subset-sampling-for-conditi.txt
@GregoryAshton @ColmTalbot

Thanks @ReinhardPrix for adding this fix. It is a difficulty not having open access to the git.ligo repository (and I can't figure out how to import MRs between GH and GL).
I have for now manually made the MR in GL: https://git.ligo.org/lscsoft/bilby/-/merge_requests/1289
If you have any comments on it, please feel free to ping me here or by email. I changed some minor things to get the test into the test suite but otherwise it all looked sensible to me.

Great, thanks, Greg!


Adding Hamming metric equations to the vignette

Codecov Report

Merging #61 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #61   +/-   ##
=======================================
  Coverage   92.33%   92.33%
=======================================
  Files           7        7
  Lines         326      326
=======================================
  Hits          301      301
  Misses         25       25

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c8d4dd...5b69b7b. Read the comment docs.


chore: a bunch of dependency updates

One of them patches a vulnerability.
/deploy

You can access the deployment of this PR at https://renku-ci-nb-544.dev.renku.ch

anybody feels like approving the PR? :)

ah sorry, I was waiting for acceptance tests to finish.. and then it was lunchtime 👍 😄


Use maven to download JanusGraph server zip from GitHub

Maven's download-maven-plugin will cache the JanusGraph server zip in ~/.m2, so I don't have to worry about getting a new server zip each time.

solved in https://github.com/awslabs/dynamodb-titan-storage-backend/pull/107


Support fiat input in dual currency field

This PR is an initial effort in dealing with https://github.com/getAlby/lightning-browser-extension/issues/2511 , in its current state it doesn't tweak the rendering of the input field but takes care only of the underlying changes needed to support the currency switch.
To make the implementation effective and reduce code duplication i've moved the switching and conversion logic under the DualCurrencyFieldChangeEvent component that now has an optional boolean  showFiat field instead of  fiatValue .
The onChange event is captured and transformed so that event.target.value is always a string with the value in satoshis (no matter which currency is used as input), event.target is also extended with the following custom fields
valueInFiat: number;
formattedValueInFiat: string;
valueInSats: number;
formattedValueInSats: string;

to provide all the transformed values needed throughout the various ui components.
DualCurrencyFieldChangeEvent is set to default to use fiat input whenever the account is using a fiat currency ( account.currency !== "BTC"), the manual switching is temporarily  binded to the onClick event of the "alt currency"  field

Let me know what you think about this draft, the proposed ux design is obviously not there yet, but i think it is better to get the logic sorted out first.

Wow, thanks for tackling that right away! :100:

Let me know what you think about this draft, the proposed ux design is obviously not there yet, but i think it is better to get the logic sorted out first.

Generally speaking this is great! There might be some nitpicks around naming & event properties but I am well aware this is just a draft so I'll skip that for now. We'll be able to sort those things out as the PR progresses.
So looking forward to finally be able to send 10 USD to a friend without having to lookup rates! :muscle:

I propose to use the bitcoin symbol ₿ as prefix for bitcoin inputs (like for $). The input placeholder will still say "Amount in Satoshis..." so it will be clear that it is asking a bitcoin input denominated in sats.
Both the prefixed symbol and the "fiat amounts" will toggle the main currency  when clicked.
The reason to have a prefix symbol for sats inputs instead of the "sats" suffix proposed in https://github.com/getAlby/lightning-browser-extension/issues/2511 is to keep implementation simple and consistent, since as noted in the issue, implementing a cross-browser growing input field adds quite a lot of complexity.
I think this is overall a pretty good alternative, since it is clear, simple and makes use of the ₿ symbol.
I've changed the dual currency input to automatically set the parameterized "Amount in {{currency}}..." placeholder when no placeholder is passed to the component and i've adapted the code to not pass a placeholder.
Some screenshots:

Looking forwards to your feedback. Also pinging @stackingsaunter  for feedbacks on the design since ux is not my forte.
The latest commit contains all the aforementioned changes.

hey @riccardobl i did some testing. the receive screen is broken that is why tests are failing as well. the right sat amount is not getting reflected to the form change functions in receive screen. it always defaults to 0 can you please try and fix that?

I think i fixed the issues, it seems to be working as expected now. However it think i'll need some help to get the unit tests updated or figure out why they fail

why i can't remove the zero from the set budget form? i have to type currently for eg. 0100 to set budget for 100 sats. if I press back space it throws error

@riccardobl have you tested things up? is it ready for another round of review?

@riccardobl have you tested things up? is it ready for another round of review?
Yes, it should be ready for review

Actually both units are visible

First one being ₿.
The tailing unit proposed in the design, as discussed before, is incredibly complex to implement in code as there is no standard component in html that allows tailing units.
I can make the other two changes.

Hey, yeah both are visable and this is good, but when I enter the screen with input I see only one:

Only after I click on the unit the other appears:

Same happens on "send" screen. I don't know If this was intended or a bug?

Oh ok, it was a bug. Should be fixed now, also i've made the other two changes.

If it's possible it would be great If units itself would have hover unit (and change the cursor state to "hand with a finger" one), because right now it's not easily discoverable by users they can click it (also because of point 1.)

I used hover:text-neutral-400 on both, since they have the same styling and added the pointer cursor, is this is the correct way to adapt the original design?

fixed

@riccardobl Just tested it and that is an awesome improvement. :100:
Can you take a look at the failing unit tests?

There's still and inconsistent behaviour. if i enter 0 and press backspace i can't remove the zero from there. also when entering lower amount via fiat. i can't enter for example i can enter 20 sats but not not 0.01 dollars in the fields
alsong regarding the tests. its weird that they fail. if i remove dual currency field from the screens. tests do work. can you check that ?  fixed the test for DualCurrency component itself

There's still and inconsistent behaviour. if i enter 0 and press backspace i can't remove the zero from there. also when entering lower amount via fiat. i can't enter for example i can enter 20 sats but not not 0.01 dollars in the fields

I can't reproduce these two issues, could you please double check and give me more info ?

@riccardobl

in receive tab. when i enter amount and remove all numbers via backspace 0 still lies there and new numbers get entered before 0. i have to manually select whole number to cleanup the field
in site settings. if  you enter any amount and backspace 0 never vanishes. even after manually selection and trying to remove it + currency conversion seems broken i entered 0.11111 it automatically converted to 165 and it shows 165 dollars = 165 sats
https://github.com/getAlby/lightning-browser-extension/assets/55848322/68012ae6-3688-47e1-b44c-23d19660d004

@pavanjoshi914 @reneaaron could you review this? I think it's good to go

wow! great job! currency field is quite stable now.thanks for your valuable work :rocket:

unfortunately this is working when we input values in the input field itself. but we have this presets
but when we pass the value from outside for example this presets. dual currency field does nothing.
i noticed few things

value field in the component is not used anywhere. in value field such values are passed to the dualCurrencyCompontent. along with "inputValue" we also have to handle "value" here
values from presets are always in sats. so somehow we need to handle currency conversion + showing the converted value in dual currency field

This stems from the modified DualCurrencyField not using the value property internally, instead it uses the inputValue  state that is initialized with the value of the value property, so it won't react to changes of value even when passed as a react state.
This is all due to the fact that the DualCurrencyField presents itself always as a satoshi denominated input and so it has to perform the conversion internally and it needs to update the internal inputValue.
There is also some code in alby that updates the value state passed to the DualCurrencyField with the value coming from the DualCurrencyField onChange callback, so a fix needs also to consider this to avoid a feedback loop.
I believe it is not an easy issue to solve, but i thought to it deeply and i've figured out the workaround in my last commit,  it is not the prettiest code, but it should work reliably.

Could you review that workaround? @pavanjoshi914 and maybe @reneaaron or @bumi ?
This is constantly requested by many users

there are still few of the tests need to be fixed


Fix different issues in datatypes notebook

fixes #225

I get the following error for these exercises:

solution_addition_multiplication()
solution_circle_area()
solution_quadratic_equation()

I get the following error for these exercises:

solution_dict_return_value()
solution_dict_return_value_delete()

@despadam, I addressed the reported issues in https://github.com/empa-scientific-it/python-tutorial/pull/230/commits/5409bac44467d41929c6d90bbbe49a7ecf83cb17, please have a look


[Swift 4.2] Update Miller-Rabin Primality Test

Checklist

[x] I've looked at the contribution guidelines.
[x] This pull request is complete and ready for review.

Description

References #748
There were no necessary code changes for Swift 4.2.
Removed the  snippet requested

Thanks for the update 👍


Dev Test: New Splash Screen

From https://github.com/phetsims/joist/issues/408 https://github.com/phetsims/joist/issues/407 and https://github.com/phetsims/joist/issues/349 we have made the following changes to the splash screen:

It should be sized proportionally to the screen size
It should show a pulsing animation while downloading

I published an Energy Skate Park: Basics version here that has these changes.  It will need to be tested on all of our supported platforms because it uses new preload code + css that may have platform-specific issues.
http://www.colorado.edu/physics/phet/dev/html/energy-skate-park-basics/1.3.1-dev.6/energy-skate-park-basics_en.html
Before setting the entire QA team loose on this, it would be best if @ariel-phet could review the current implementation for design issues (sizing and how the pulse-download animation looks).  If all is well, then we can expand the testing.  If your internet connection is too fast, you may have trouble seeing the download part of the animation.  You can use Chrome Dev Tools to throttle your download speed.  View => Developer => Developer Tools=> Network => "No throttling" (in the top right) can be changed as desired.

A reminder to test phetsims/joist#408 phetsims/joist#407 when this gets to the QA team.

@samreid all looks good to me

Thanks @ariel-phet.  A reminder to the QA team during testing to test out phetsims/joist#408 phetsims/joist#407 in particular.

@samreid anything to add before @phet-steele takes over

It's all set, let me know how it goes.

@samreid looks good on our supported platforms. All linked issues have been taken care of as well.

Thanks @phet-steele, I'll merge this to master and it will be ready for new deploys from master.

I'll proceed in https://github.com/phetsims/joist/issues/391, many thanks @phet-steele


[IMP] Extend NiftiDataLoader Operator to output Image object

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

NiftiDataLoader operator currently outputs a np.ndarray. Need to extend this to wrap in an Image object with correct meta/header information to more easily work with existing MAP workflows.
Describe the solution you'd like

NiftiDataLoader with Image object as IN_MEMORY output.
Describe alternatives you've considered

An alternative would be to use the original DICOM images and take advantage of existing operators, but this is just not possible in some cases where Nifti files are the only form of data.
Additional context

An enhancement like this could enable a workflow such as processing a large batch (10,000+) of Nifti images for rapid inference.

@vikashg

The MONAI Core LoadImage function with its nii reader also output MetaTensor, essentially Torch Tensor with the few piece of metadata returned from nii reader. The Deploy App SDK inference operators' internal and the InMemImageReader had been updated to support MetaTensor in v0.5.
So, we'll consider supporting MetaTensor on the inference operator input type, hence feeding the MetaTensor from nii data loader directly to the inference operator.


Added click support on chart data

getSegmentsAtEvent is not available for Line and Radar charts.

Added support for line, radar and bars. Checked if functions exists rather than type checking in order to avoid string type equals.

Great. But it seems to be you missed changes for dist file.

Dist package built. At the moment the onclick function is assigned using & isolated scope - the listener will be attached on each chart because of the wrapping function. It can be changed to = if required

@carlcraig Could you help to review this MR?

Looks good, will publish a release soon.

Published version 1.0.13, thanks for the contribution :+1:


[BUG] Community Script Editor "Not Found" and never added to transformed pages

Problem Area
[ ] Page Transformation: Error during the use of page transformation from PnP PowerShell
[ ] Page Transformation: Error during the use of page transformation from .Net
[x] Page Transformation: Page is not looking correct after transformation
[ ] Modernization Scanner: something went wrong...
Expected or Desired Behavior
Insert the modern community script editor web part, via the <FixedWebParts> node, during the classic publishing page transformation process. Note- I'm referencing a classic script editor web part within the above mentioned node in hopes of triggering the mapping...maybe this is the wrong approach to begin with?
Observed Behavior
Classic publishing page transformation completes as expected, minus the presence of the modern community script editor web part which isn't inserted into the transformed page. A warning in the generated log file indicates "Modern web part not found".
Steps to Reproduce

Classic SharePoint publishing site hosted in Microsoft 365 (source)

Modern communication site hosted in Microsoft 365 (destination)

Attached files - Convert-PublishingPages.ps1; webpartmapping.xml; pagelayoutmapping.xml.
webpartmapping.zip

The custom page layout in question is <PageLayout Name="EnterpriseWikiCustom" ... >

Follow these instructions to install the community script editor and set the required flag on the PnP PowerShell cmdlet. Once the community script editor is deployed to the app catalog (I tried both site collection and tenant), add the app to the modern communication site so it's visible in site contents.

Run the PowerShell script via .\Convert-PublishingPages.ps1 -SourceSitePartUrl "<SOURCE_SITE>" -TargetSitePartUrl "<TARGET_SITE>" -PartTenant "<TENANT>"

@gabrielbray : Did you test in a new PS shell, there's caching going on and a new shell will clear that.

Hey @jansenbe I was looking over the documentation again and I neglected to allow custom scripting via PowerShell on the destination site. I'll follow-up if that doesn't clear up the issue.

Hi @gabrielbray : did you manage to get things working?

Hi @jansenbe I was able to get back to it last night and it's working now. Appreciate the follow up!


free cam optional change

I tested the basics but not everything, further testing might be good.

Hey emrecankarabacak.
Thanks for your help! I had to manually merge / override the files. Please make sure that next time all your commits are signed. (I don't want to take credit from you.)


Develop and test the first iteration of model to recommend players

Performed statistical analysis of all players and players who featured in recent seasons to get their all-time stats and recent stats.
Prepared recommendations for anchors and power hitters based on their strike rates and averages.

Based on the results from EDA first iteration for recommendation model was created with inning segments along with KPIs strike rate and average.  A criteria was decided for each segment and a sorted list was the output


"Uncaught ReferenceError: window is not defined" using client-side only plugin

Version
v2.8.1
Reproduction link
none
Steps to reproduce
Install 'vue-pdf' package:
npm install -s vue-pdf
Import it as a plugin, since it is a client-side only component:

vue-pdf.js:

import Vue from 'vue'
import VuePdf from 'vue-pdf'

Vue.use(VuePdf)

nuxt.config.js:

…
plugins: [
   {src: '~/plugins/vue-pdf.js', ssr: false}
],
build: {
   vendor: [
      'vue-pdf'
   ]
}
…

What is expected ?
The component works great; No error is displayed.
What is actually happening?
Uncaught ReferenceError: window is not defined is displayed in the console.

This question is available on Nuxt community (#c9401)

You need to either add .client.js to your filename or { mode: 'client' } in your plugin import as the window is defined only on the browser and thats a client side component! Hope it helped

Check out this working solution https://github.com/FranckFreiburger/vue-pdf/issues/148

@zardilior This is actually my solution to this particular issue 😂 I shared it in that Github issue after finding the solution.
Thanks for linking the solution btw, I forgot to do it 🙂

lol :P how dumb, anyway leaving it for others who end up here

@EmmanuelJego by any chance you didn't had issues with resizing of the viewport too?

@zardilior Nop, sorry. What is your issue ?

I figured I has the same component in two v-if therefore it rerendered it, solved it though it was the resizing


Additional steps required to enable each of Azure Defender for servers features?

Thank for excellent documentation here. This matrix helps a lot in understanding which Azure Defender features are supported for servers:
https://docs.microsoft.com/en-us/azure/security-center/security-center-services?tabs=features-windows#supported-features-for-virtual-machines-and-servers-
Would you be able to add additional column relating to enablement that would save customers a lot of time?
It would be valuable to understand whether enablement of each Azure Defender feature requires additional steps (Yes/No) or the feature is automatically enabled for all resources in scope when Azure Defender for servers is switched on for an Azure subscription.
For example to enable:

"Native vulnerability assessment" feature additional steps are required to deploy Qualys scanner, e.g., with Azure Policy
"File integrity monitoring" feature additional steps are required to configure Azure Log Analytics workspace.

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

ID: 20c81719-d8d4-2eb3-a5a9-1cc35dd04bec
Version Independent ID: 8288bd95-d44e-8b1c-accb-0b221a71cd73
Content: Azure Security Center's features according to OS, machine type, and cloud
Content Source: articles/security-center/security-center-services.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@pemsft
Thanks for your feedback! We will investigate and update as appropriate.

@pemsft
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Hi @pemsft, thanks for the feedback and for taking the time to help us improve the docs.
This documentation page is going to get refreshed in the coming months, and we'll consider that suggestion when making the updates. For now, all the necessary extras you're looking for are within the relevant feature pages.
I'm going to close this issue, but feel free to comment again here or open a new one if you have additional requests.
#please-close


EU4ToVic2: Test a possible de-ironmanning solution

There are claims that a save game replayer tool can de-ironman tools. This should be tested with the converter to see if it does so in a way that meets our needs.
https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-136#post-19160471

Also, this technique might be the one to put in the FAQ: https://forum.paradoxplaza.com/forum/index.php?threads/the-eu4-to-v2-converter-project.707362/page-133#post-19130643
Or maybe this one: http://www.reddit.com/r/paradoxplaza/comments/2wd2fb/pls_help_me_deironman_a_savegame/copqzrz


New LRI

update link to point to new LRI and update link in readme to point to new COS

Thank you @ptitzler


fix/package-lock

node version: 12.18.3
npm version: 6.14.6

@angle943 after updating node to v14.16.0 and npm to v7.6.3, I still have a few changes. But I think these are okay?


Unified UX component container for widget systems

Since Symfony is meant as an application framework (as opposed to static websites) I think it would be great if the UX initiative offered a unified widget or component management system which allowed building dashboards, applications, and admin interfaces more easily and interactively. Several of the components for building dashboards are already part of the UX bundle (forms, charts, etc.) but I feel like the missing piece is the container that pulls the pieces together.
Think of it like a widget manager or dashboard container that loads the individual components and includes methods for dragging components around, minimizing or hiding components. Much like the windowing system of an OS it doesn't care what it displays but it takes care of loading and positioning of different components.
This would simplify developing an Ecommerce dashboard, where you may want to display sales totals, or new customer signups and displayed components may be added, removed or moved. Or maybe you are building an application with multiple tool and property panels. Instead of everybody making their own component manager, I think it could be a great functionality to offer out of the box.
Some examples:
Wordpress Dashboard has some very basic widget container functionality.
OpenCart Dashboard
3rd party options:
Golden Layouts
Dragula
These could be wrapped around stimulus or twig components offering 2 levels of feature complexity but both are JS based and I believe going a fully Hotwire/Turbo/Stimulus route is better and more in line with the future plans of the UX bundle.
If the container system was made to wrap any components being rendered it would also allow mixing any and all of the currently supported frontend systems (Vue, React, Twig, Stimulus) on a single page and moving data between them.

Hey!
This sounds bold, but interesting. It's not an area that I have a lot of experience with as a developer (I mean, it's not something I've ever had to built before). So, the interface would be... something like this? https://golden-layout.com/examples/ And you're adding Twig/Live components from your system to different sections, with options for the data that should be passed into each? Or would it be more configured like EasyAdmin, where you have configuration that would select and add your components to the page?
Again, no idea if this makes sense for UX - but it's always fun to brainstorm and find out :).
Cheers!

Exactly. I think it would be part of your twig template instead of being configured by easyadmin. You could add easy admin forms into it though to make a blog post form like wordpress where you can pull different sections to other positions or minimize them. Or like the Wordpress widget page where you can rearrange fields. Or if you make an Ecommerce app you may have a dashboard that shows recent orders, sales charts, a map with customer locations, inventory, etc. and each of the boxes is draggable.
By making it a wrapping container that loads other components, you would be able to load twig components that interact with your symfony controllers and React components into the same page. If it was done as part of the twig component bundle you would need to load any React or Vue components as twig components which would require modifying their code which may be difficult for larger apps. I think for larger libraries, something like an OpenOffice editor it would be best to keep the code separate and use the container to display them on the same page. This also allows erecting barriers between components that are uncrossable unless specifically passing the data from one container to another.
This could be done using Turbo Frames which work kind of like an Iframe if I understood it correctly. We would need an outer container, a way to define sub containers, a method for passing data between them, and controls for the interaction (drag, minimize, hide, full screen, etc).

Well I use a Sylius/ResourceBundle with a Sylius/GridBundle to achieve something like that. You can define each field as twig template -> https://github.com/Sylius/SyliusGridBundle/blob/1.13/docs/field_types.md#twig-twig which in my case is a TwigComponent.
What's more I've got live components which are responsible for handling (in nice ajax way) defined resources (dashboard lists).

This is exactly why I think this type of component is needed. From the looks of it this is loading a twig component into a data table field. Think more like the interface of a program like Photoshop or Visual Studio with docking panels that can be rearranged.
By making each panel act like it's own iframe (wrapped by a container) you gain a lot of freedom and security. Not to mention separation. You could have a Top navigation using React, a sidebar and main window using Twig components and unless you choose to pass data between them using the container as a bridge they wouldn't know the others exist.
Your method is just rendering a bunch of layout pieces in a set of divs but keeping it as a single page made of smaller pieces. It doesn't allow drag and drop, minimizing, hiding of widgets, and any live components need to be specifically coded for each use case.


write map_sample_ID

Via CLI
cg get family -c custXXX -n family_id

Scout holds both external and internal names for family and sample IDs


🐛 Incorrect deposit amount reported via error message at proposal -> governance action time

Sender: None
Taken at: https://sanchogov.tools/proposal_discussion/16
Fields:

Add a comment: I have nearly tAda 100k in my SanchoNet Demos wallet. When I attempt to submit an info governance action I am told that I need at least 50k tAda to submit the action, and so the action cannot be submitted.

Browser: Chrome 127 (Windows 10)
Screen size: 1368x912
View screen recording
Open #104 in Usersnap
Powered by Usersnap.

error message reporting incorrect value for proposal deposit size (is currently 100K on Sancho)

Not sure why this goes wrong, perhaps it is pulling incorrect params from getItemFromLocalStorage(PROTOCOL_PARAMS_KEY);
https://github.com/IntersectMBO/govtool/blob/develop/govtool/frontend/src/hooks/forms/useCreateGovernanceActionForm.ts#L243

And @Ryun1 gov action deposit on Sancho Beta is 100k - that can be checked on the:
Dev Console > Application > Local storage > protocol_params (pic rel)

@MSzalowski @Ryun1 Yes, it is an error on the modal in the PDF. We didn't know this state existed in localstorage, we will implement a dynamic value change in the modal depending on the state in localstorage

@MSzalowski We have updated the PDF package to version 0.3.5, it is ready for import

This is fixed


can u please add onClick event code in the sample

There is a default click event  of treeview at here, if you want to write a custom click listener, you'd better refer to it.

Thank you very much..


AWS documentation for security group

LGTM

It would be nice if this modification of the security group was optional.  If you pass in your own, could you opt out of the opening of the ports?  I have a security group that has the necessary ports open ONLY to my IP, and would rather not have to go shut down the SSH and Docker ports (open to <IP_ADDRESS>) from the console every time.


Get-LatestOSBuild function doesn't work on Server Core

The following error is returned when you run the Get-LatestOSBuild function on Server Core.
Retrieving the COM class factory for component with CLSID {00000000-0000-0000-0000-000000000000} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)
This is due to the absence of the COM object 'HTMLFile' which is used to parse the release information. Internet Explorer is needed for this COM object to work and it is not installed on Server core.

Resolved in v2206.2