Remix integration

Hi, this template can support Remix or not?

Hi,
At the moment we haven't tried using Remix in combination with Metronic. We will check it and consider using Metronic in future releases if we see demand.


Update README.md

The plugin manager referenced was deprecated and now n++ has its own built-in one.

Thanks for your contribution! Always good to see someone is reading the docs :-)


enable jda nas for more architectures

this adds jda nas support for the following architectures:
linux-x86
linux-aarch64
linux-arm
win-x86-64
win-x86
darwin

m1 support is currently missing

the test pass on my machine 😿

the tests pass on my machine 😿

CI server fails with  org.springframework.beans.BeanInstantiationException: Failed to instantiate [moe.kyokobot.koe.KoeOptions]: Factory method 'koeOptions' threw exception; nested exception is java.lang.RuntimeException: java.lang.UnsatisfiedLinkError: /opt/buildagent/temp/buildTmp/lava-jni-natives/1658100533975/libudpqueue.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /opt/buildagent/temp/buildTmp/lava-jni-natives/1658100533975/libudpqueue.so)


Unable to build with CustomHTTPHeaders enabled; v10 / Mapbox 10.3.0

Describe the bug
Build failing with CustomHttpHeaders enabled
To Reproduce

clone example app or init new one:

react-native init sample
cd sample
npm install rnmapbox/maps#main --save

follow this instruction (edit Podfile)

follow  this instruction (add code to AppDelegate)

install pods:

cd ios
pod install

try to build with Xcode

Expected behavior
Build succeed
Actual behavior
Build failed (see description below)
Versions:

Platform: iOS
Platform OS: 15.4
Device: Phone13
Emulator/ Simulator: yes
Dev OS: OSX 12.3 (M1 Apple Silicon)
@rnmapbox/maps Version 10.0.0-beta.0
Mapbox GL version 10.3.0
React Native Version 0.67.4

Additional context
First build will fail with: MGLCustomHeaders.h' file not found
So I added $(SRCROOT)/../node_modules/@rnmapbox/maps/ios/RCTMGL as suggested in #922
that leads to another error:
ld: warning: directory not found for option '-L/Users/spooner/Library/Developer/Xcode/DerivedData/RNMapboxGLExample-famczcunoxcdrhgahdjdddciibsb/Build/Products/Debug-iphonesimulator/react-native-mapbox-gl'
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_MGLCustomHeaders", referenced from:
      objc-class-ref in AppDelegate.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Showing All Messages
Undefined symbol: _OBJC_CLASS_$_MGLCustomHeaders

Thank you for help!

Update:
After browsing source code for a while is looks like this is not implemented in v10? Obviously now instructions are for v8.

We have cust http in v10 with different impl


waterfallDialog turn should pass the result coming from adaptive-cards forms

In waterfall step I just send adaptive-card activity like this
await step.context.sendActivity(MessageFactory.attachment(CardFactory.adaptiveCard(someCard)))
return Dialog.EndOfTurn

this adaptive-card includes input field with submit button.
then, in the next turn I couldnt see the submitted data in step.result.
Of course I can grab it from step.context.activity.value but I'm expecting to get it like I get a simple text response.
The simple PR I can do for it is right here:
https://github.com/Microsoft/botbuilder-js/blob/d4255c382189476dff5cc0879ec8d2f29b1162ce/libraries/botbuilder-dialogs/src/waterfallDialog.ts#L150
just to pass dc.context.activity.text OR dc.context.activity.value but I wonder if this is the optimal solution .

Thank you for the input. We are thinking of ways to incorporate interaction with cards into the dialog system.
Your solution of using step.context.activity.valu is a good way to do it for now.

@shmuelgutman this is going to be very brittle. The issue is there's no guarantee that the user will fill in the form and press submit as their next action.  They could send you text which means the result passed to the next step will not be the forms value.  If you really want to wait for the form to be submitted then you should use an ActivityPrompt with a custom validator like this:
this.addDialog(new ActivityPrompt('formPrompt', async (prompt) => {
    // Only validate incoming messages
    const activity = prompt.recognized.value;
    if (activity.type === ActivityType.Message) {
        if (activity.value) {
            // Return value from prompt
            prompt.recognized.value = activity.value;
            return true;
        } else {
            // Reprompt user to fill in form
            await prompt.context.sendActivity(`Please fill in form and press "submit" button.`);
        }
    }
    return false;
});

Then to call the prompt from your waterfall:
async (step) => {
    const form = MessageFactory.attachment(CardFactory.adaptiveCard(someCard));
    return await step.prompt('formPrompt', { prompt: form });
},
async (step) => {
    const values = step.result;
}

Alright, got it, make sense.
BTW, ActivityPrompt is an abstract class, I guess you meant to define a new class that extends ActivityPrompt, but wait, does it should be an abstract class? I thought Prompt is the base class for all prompts.

@shmuelgutman I'd like to echo shmuelgutman in asking if ActivityPrompt really needs to be an abstract class. Rest of you have thoughts on this? Right now im extending it with no real extended functionality solely because its marked as abstract

A short example showing how to accomplish this within your JS code has just been added to:
https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-howto-add-media-attachments?view=azure-bot-service-4.0&tabs=csharp#additional-resources in the Additional Resources section. This should be publicly available once that update goes live.


onIds, onOpened, onReceived can't called on AndroidX

Description:
Hi...
I am after install latest react natiave and latest onesignal too,
i am follow all instalation intruction. but after use onIds,onReceived,onOpened has not called.
i have add OneSignal.configure() too. Please how to fix this
Environment
"react-native-onesignal": "^3.2.14",
"react-native": "0.60.4",
"react": "16.8.6",
Steps to Reproduce Issue:

Install react native
install onesignal and linking
implement onesignal
can't called

Anything else:
nothing response
thanks very much

I am facing the same issue.
RN 0.60
OneSignal 3.3.0
AndriodX
the listeners for newly registered app are not getting fired. The fixes in onesignal new release (3.3.0) fixed the existing apps which were already using and were registered with onesignal.

@rgomezp
I am facing the same issue.
RN 0.60
OneSignal 3.3.0
AndriodX
the listeners for newly registered app are not getting fired. The fixes in onesignal new release (3.3.0) fixed the existing apps which were already using and were registered with onesignal.

thank for your answer, after upgrading react-native-onesignal, i found this problem
`Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.

Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app
Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app > project :react-native-onesignal
Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app > project :react-native-onesignal > com.onesignal:OneSignal:3.11.1`

are you found problem like that ?

@rgomezp
I am facing the same issue.
RN 0.60
OneSignal 3.3.0
AndriodX
the listeners for newly registered app are not getting fired. The fixes in onesignal new release (3.3.0) fixed the existing apps which were already using and were registered with onesignal.

thank for your answer, after upgrading react-native-onesignal, i found this problem
`Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.

Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app
Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app > project :react-native-onesignal
Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app > project :react-native-onesignal > com.onesignal:OneSignal:3.11.1`

are you found problem like that ?

i have fixed this. just add into file app/build.gradle
https://github.com/geektimecoil/react-native-onesignal/issues/805#issuecomment-514217308

@rgomezp
I am facing the same issue.
RN 0.60
OneSignal 3.3.0
AndriodX
the listeners for newly registered app are not getting fired. The fixes in onesignal new release (3.3.0) fixed the existing apps which were already using and were registered with onesignal.

thank for your answer, after upgrading react-native-onesignal, i found this problem
`Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.

Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app
Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app > project :react-native-onesignal
Could not find androidx.cardview:cardview:28.0.0.
Required by:
project :app > project :react-native-onesignal > com.onesignal:OneSignal:3.11.1`

are you found problem like that ?

i have fixed this. just add into file app/build.gradle,
but there warning for remove manual linking.
#805 (comment)

in your android/app/build gradle go to dependencies and replace this line
implementation(project(':react-native-onesignal'))
with this
implementation(project(':react-native-onesignal')){
exclude group: 'com.google.android.gms'
exclude group: 'com.android.support', module: 'cardview-v7'
}


add @see: pluck, project and map

I think better than this would be if these four would refer either all to one another or at least all refer to their horizontal and vertical neighbors (so that, for instance,, pluck might refer to prop and project but possibly not to props):

single object
multiple objects

single property
prop
pluck

multiple properties
props
project

They're not entirely parallel, since they have different return types, but they make sense as a group that would all make reference to one another.
I don't think that map belongs in this group.  It does something else, even if it can be used to implement, say pluck in terms of prop.

Modified @see by your suggestion, @CrossEye

:herb:
Thank you very much!


Setup script refactor

Fixes #60, #79.
What's still missing:

Fedora support - does anyone use that? Do we care?
Can be easily added later when there are people to use that on daily basis.
[x] Arch Linux: "python" => "python2" everywhere (including all other scripts) - setup should be fine with the alias now - we'll add choice for py version later; do a systemd unit override for this - something like Exec=/usr/bin/python2 ...
[x] include frequently used systemd unit overrides (usergroup-root and stuff)
[x] OS / device detection / selection - let's just ask the user and don't over-complicate things
[x] pass ${monitorAlexa} as boolean
[x] config handling cleanup / refactor

Need to do:

once this is merged, edit wiki:

[x] delete gpio lib manual install from wiki
[x] change using usergroup-root override (now included in repo)
[x] change using the reboot override
[x] Raspberry Pi: add "dtparam=audio=on" to /boot/config.txt
This enables on-board audio via Device Trees.
[x] remove creating / setting alexapi home directory in PA section in the wiki

proper testing

Probably later:

non-interactive install - cli parameters or some sort of config file - this is important for testing / CI

So I gave this a lot of testing and fixing so it should hopefully be okay.
@alexa-pi/coreteam Please test and confirm, if it's okay or not. Thanks!

I've installed and run this successfully on a Pi running Raspbian, and I got it to work on a CHIP too.
For the CHIP, I still had to:
1.) edit /etc/opt/AlexaPi/config.yaml to change device from "raspberrypi" to "chip"
2.) follow the wiki to set up a "run as root" configuration
3.) set output device to "plughw:1" for my external sound card.  (This one obviously depends on hardware, but is really the only practical way to use AlexaPi on CHIP right now.)
It is slightly misleading to ask the user what device they are using then not have it reflected in the imported config.yaml file.  How hard would it be to change that during install?
Also, since it isn't running as root out of the gates, install doesn't "just work".  I'm assuming that if a CHIP user managed to get that far they could figure it out, but what are thoughts on making root a default for CHIP and Orange Pi since we know we need it right now anyway?

This is all intentional, since the root platforms should be discouraged generally as insecure and some people might use the dummy platform when they don't need GPIO and the rest should be warned before using it.  Not even telling the user is not much of a warning.  Thanks for pointing this all out!
So I'm gonna:

set the default sound devices for CHIP ... and for Orange Pis too, because they usually have an internal mic
set the platform in the config for CHIP and Orange Pi to dummy as default, since raspberrypi obviously won't work and this leaves a working, secure voice-activation only install
include a function that's gonna tell the user that currently the only way for a button or LEDs to work on their device is the insecure root stuff and if they really wish to use it - if yes, then just activate the root override and set the platform in the config

Sounds okay?

For 3, perhaps cleaner way of doing that is to separate CHIP/OrangePi root override into a separate script with "on/off" switch? So security minded people may want to switch button/LED off once they tried them out.

So I've been thinking about it for the last hour and I still don't feel very keen about doing it since it's just two commands (cp/rm & systemctl daemon-reload) which can easily be found on the wiki. Currently the install is more of a one-way thing than a program which allows options. I'd like to get there in the future however. Also, the user would still have to set another platform in the config when disabling the override. I don't know, it might be just my mood. Hit me up with more reasons why we should do it now. Also I'd like it in the future if the setup script could do stuff like upgrading and stuff, where on/offing things would make also sense.
BTW, I've found https://github.com/FlavourSys/bash-installer-framework which is something we might use in the future - a lot has happened here so let's just finish it as it was designed and do other improvements in other PRs.

I am all for the "on/offing" things in the future. After the issue on the HiFiBerry GPIO conflict last night (also with TFT screens, other hats), I think a modular "device announced" approach makes more sense. Any thoughts on what I wrote up a while back?

@renekliment
I'm perfectly fine with keeping root access as something that needs to be configured.  I wanted to open the discussion, since it would be easy for a user to think they had done everything required to get AlexaPi to work on the CHIP, then to have it fail.
I think it might be worthwhile to have something to inform the user about next steps--maybe a string of text during the install about running as root if CHIP or Orange Pi has been suggested.  And either include a blurb there about modifying the "device" in config.yaml or adjust it automatically.
However, I know there are bigger changes in the works, and if they are planned to help remove some of these stumbling blocks I'm okay with merging this and moving on.  Realistically, this stuff is in the wiki.
There's nothing wrong with the PR -- just things that seemed like good additions as I was installing it.

@maso27 Don't get me wrong, you have fair points there. We're totally including the stuff in the setup script as mentioned above.

@illperipherals Feel free to open a PR. I don't have it on my todo / priority list.

Alright, so:

The default audio devices should work better now.
The default device_platform is dummy now, which works everywhere, so we don't have broken-by-default installs. Raspberrys are set-up correctly, because they work rootless.
I wanted to set it up automatically even for root platforms, but that would take additional time with writing, testing and we would have no progress. So for OPis and CHIP, there is a message that tells users to follow the wiki if they want LEDs / button. We should do the automatic setting in the future though. I think it is important. I just feel like if I don't merge this soon, I won't have the strength to finish it later.

@alexa-pi/coreteam So since this is only a step forward and now it shouldn't confuse OPi / CHIP users, I'm for merging this if there are no other issues. Please test and tell me if it's okay to go.
The automatic configuration of root-only platforms is something someone else could take up. It should be fairly easy, since we have the config_set function, the root override is right there in the repo now, we can use sed for classic init script, etc. It's just a matter of using a few commands in the handle_root_platform function which already receives the platform name as it's argument. And a bit of testing of course.

Works with CHIP!
I'd say we should merge it.

Great! Merging this and hoping I can finish the other PR soon, so we can make a new release and take a vacation :-)
Thank you for testing Mason!

Also, anyone feel free to take the automatic root platform setup, it's easy.

Huh.  I guess I should've tested the Raspberry Pi again, instead of just focusing on the CHIP with #82.  Sorry folks!


Exporter: correctly convert UV texture transforms

Previous to this change, the values in the Mapping node in Blender were copied straight into the KHR_texture_transform object. This is incorrect because the Mapping node is applied in Blender's UV space, which is related to glTF's with the u,v->u,1-v conversion. That meant that a Mapping node that eg. translates up would be exported as a KHR_texture_transform that translates down because of the
differing directions of the V axis.
The correct thing to do is to calculate the equivalent transform in the other UV space.
This was added to the common module because the importer would need to apply the same conversion to get the right Mapping node from a KHR_texture_transform.

Thank you! :)

@emackey can you think of any reason we shouldn't enable the "Texture Transforms" checkbox by default? I'd see more of an argument for default=false if the alternative was to bake the transform into UVs, but currently we just ignore it. Seems like adding a transform is a pretty manual and explicit step in Blender, and we may as well use the extension when appropriate.

Yeah, that sounds good.  Can the exporter be smart enough (or is it already?) to avoid writing the extension when it isn't needed?  Certainly when the transform node is missing, but maybe also when the transform is just the identity transform.

Not sure, but I agree that should be a requirement.

It is already (smart enough).
https://github.com/KhronosGroup/glTF-Blender-IO/blob/c48a4891e2a7cd09df031c817825ac4dd295219f/addons/io_scene_gltf2/blender/exp/gltf2_blender_get.py#L388-L396

That being the case, who would ever disable the tex transform box?  Can we just remove the UI for it?

Fine to remove it, yeah 👍

@scurest The math here is better than before, but doesn't seem quite right yet.  The Z rotation direction appears reversed, and I don't think the offset is correct when a rotation is applied.

Hm. convert_texture_transform is computing (change UV space)∘(texture transform)∘(change UV space). Changing UV space is (u, v) -> (u, 1-v); write it as Trans[0, 1] Scale[1, -1]. Write the texture transform as Trans[t_x, t_y] Rot[ϑ] Scale[s_x, s_y]. Then I did

And evaluated the translation

I'm fairly confident in this calculation.
I tested a rotation in the three.js viewer (is this what you're testing with?) and the rotation is indeed different. But looking at the source, I don't think three.js is correct! Looking at GLTFLoader, I see that it sets flipy to false.
https://github.com/mrdoob/three.js/blob/9e49e886d0c11f12e9df978c50dcab1ee0eb6ca7/examples/js/loaders/GLTFLoader.js#L2197
three.js has a UV coordinate system where the bottom-left is (0, 0), like Blender. flipy is accounting for this. But I think  (based on searching the three.js repo for uses of "flipy") flipy is only used to pass UNPACK_FLIP_Y_WEBGL to pixelStorei. It doesn't seem to affect the texture transform in any way and the texture transform values are copied directly into the three.js texture object without any modification
https://github.com/mrdoob/three.js/blob/9e49e886d0c11f12e9df978c50dcab1ee0eb6ca7/examples/js/loaders/GLTFLoader.js#L2197
According to the docs, by default the center of rotation is (0,0), the bottom left corner. So copying them without modification is incorrect because in glTF the rotation should be about the top-left corner.

For your second link, I think you meant this snippet?
https://github.com/mrdoob/three.js/blob/9e49e886d0c11f12e9df978c50dcab1ee0eb6ca7/examples/js/loaders/GLTFLoader.js#L587-L617
Hm, threejs does OK according to this test: https://gltf-viewer.donmccurdy.com/#model=https://raw.githubusercontent.com/KhronosGroup/glTF-Sample-Models/master/2.0/TextureTransformTest/glTF/TextureTransformTest.gltf. But we have a very small test set now, and your description sounds right to me.

Oops, yeah, I meant extendTexture.
I also believe TextureTransformTest is wrong! How was it generated? cc @bghgary
Let's look at the bottom-left test, the one called "Rotation". Without a texture transform, it looks like this, with the arrow pointing to the yellow square

Now the rotatation in the glTF is positive
https://github.com/KhronosGroup/glTF-Sample-Models/blob/ec880043ae0cead374d7e3a965cc8323c51b06e1/2.0/TextureTransformTest/glTF/TextureTransformTest.gltf#L155
So the rotation should be counter-clockwise, ie. towards the red square, not the green square!

I was testing in VSCode, with both the BabylonJS and ThreeJS previews, which are in agreement with each other.
I'm tempted to say that since we have two implementations that can both show a "correct" result for the test model, then if that doesn't match the math explained by the spec, maybe it's the spec that's wrong.  If we can just fix it there and have the implementations continue to work as-is, that seems like the better path.

How was it generated?

I created this asset by hand.

Now the rotatation in the glTF is positive by about 22 degrees

The spec says this for rotation:

Rotate the UVs by this many radians counter-clockwise around the origin. This is equivalent to a similar rotation of the image clockwise.

This matches the result of Babylon and three. I haven't personally checked to see if the example math is correct in the spec.

Okay, I think I understand what's wrong. Essentially we think different directions are counter-clockwise :)
Here is a counter-clockwise rotation in a normal X-right Y-up coordinate system. The matrix is the standard counter-clockwise rotation matrix. This is the matrix that KHR_texture_transform says to use for rotation and is what I've been using.

So for example, taking a point near (1,0) and rotating it towards (0,1) is a counter-clockwise rotation. So these are the exact same rotation (ie. they transform the coordinates in the same way); normal X-right Y-up on the left, glTF X-right Y-down on the right.

So this is what I've been calling a counter-clockwise rotation even though the right side is going clockwise! I guess we should go like this instead (right-side showing the "equivalent similar rotation of the image clockwise")

Then the matrix is

ie. the same as a rotation by -ϑ if you use the other matrix.
So if this is what KHR_texture_transform means, its rotation matrix is wrong.

In terms of what that changes for convert_texture_transform, the conversion glTF->Blender and Blender->glTF are no longer the same.
The calculation going from a Mapping node to a KHR_texture_transform (ie. whats the exporter uses) is the same, its just that when we read off the final line, we just have to negate the rotation angle. This means that the rotation ultimately does not change (instead of being negated). The offset should still be calculated the same way.
For the importer, when we write down the first line of the calculation, we'd similarly need to negate the rotation angle. This means the rotation ultimately does not change (instead of being negated), but the first component of the offset becomes
offset[0] + scale[1] * sin(rotation)

ie. with a + instead of a -.
Sanity check: these two functions are still inverses of each other.
I pushed these changes to my texture_transform_conversion branch. With this change it appears to work in three.js and Babylon.js

@scurest Sounds great!  This PR is already merged, can you open a new PR from the same branch please?


Make role work with chroot images

Also, make sure sudo is installed, else the role will fail since
/etc/sudoers.d won't exist, and the ipmitool stuff won't work.

Thanks!


kube-prometheus: Run node-exporter in host network

Node exporter needs to run in the host network, not in the pod network
in order to pick up network metrics of the node.
Fixes https://github.com/coreos/prometheus-operator/issues/1473

lgtm on


Refactor powervs infra for reusing fields in create cluster cmd

What this PR does / why we need it:
Fixes https://issues.redhat.com/browse/MULTIARCH-2984
Removed some of the dup blocks like validating empty base-domain and generating infraID.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[x] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/retest-required

/lgtm

/retest-required

/assign @csrwng @enxebre

/retest-required

/unhold

/unhold
/retest-required


mididings: (re-)init at unstable-2023-02-03

Description of changes
mididings has a new upstream fork/maintainer @ https://github.com/mididings/mididings
Based on a reversion of commit 03ddc5b29511cbedeff6fe49951ad6ed80b36c65.
This time I've made it principally a pythonPackage, with an application variant including all the optional dependencies.
Things done

Built on platform(s)

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

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

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

mididings
mididings.dist
python310Packages.mididings
python310Packages.mididings.dist

Not sure how to test it though.


ImportError: cannot import name 'runtime_version' from 'google.protobuf

I get the error when trying to run basic.py in the examples folder

Upgrade protobuf

Upgrade protobuf Has to be done after installing neonize

Yep this worked. Thanks.


WIP: Fixes to previous merge

Coverage decreased (-2.6%) to 88.45% when pulling 25c08fc70578d3a573c6441dce9bb9d0908d2525 on inetic:master into 17901a1ec8591825b15cb1cd86517039c9533901 on dirvine:master.


Add Xfer Records OP-1 Drum Utility 1.02

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Driver: Software to make a hardware peripheral recognisable and usable by the system. If the software is useless without the peripheral, it’s considered a driver.

Not sure if this should be submitted to drivers

Closing in favour of https://github.com/caskroom/homebrew-drivers/pull/226


Create Drupal.txt

Default installation files and folders from all the Drupal versions (updated 16/04/2020)

Source?

I've personally downloaded them all, and extracted the info

thank you!


Progress shows incorrect value when Step is set

When ever I have a step assigned to the slider the progress does not correctly display on the slider as shown.
The top number is the progress.value set at initialisation and the sliders have two different slider step counts 4 and 5 respectively.

I am using reanimation V3.5.4 and the latest version of react-native-awesome-slider; V2.5.4

The problem seems like it's not the fault of the package but the useSharedValue() taking time to adopt the value even if done before rendering the slider with the updated values.
I found I could get around this issue by querying the data outside of the slider object then directly input the min, max, and value into the useSharedValue() to get around the slider not re-rendering or updating when progress.value is changed.

const AttributeSlider = ({
attributeName,
attributeNames,
attributeValue,
callbackValue,
minValue = 1,
maxValue = 5,
value = 1,
}) => {
console.log("Attribute Level ", attributeValue);
const min = useSharedValue(minValue);
const max = useSharedValue(maxValue);
const progress = useSharedValue(value);

I hope if anyone else is also suffering from the same issue this can help you.


Configuration error: ERROR: No glob has been specified.

I just installed the module globally. When I run:
flow-coverage-report report -i "src/**/*.js"
straight from the examples (which happens to match my dir structure) I get:
Configuration error: ERROR: No glob has been specified.
Am I doing something stupid here?

@koko236 no, unfortunately it is something stupid, but something that I did ;-)
the flow-coverage-report command line syntax do not need the additional "report" parameter as currently described in the usage info (and it also makes the flow-coverage-report command unable to detect the other options correctly :-( ).
I'm duping this issue with #93 which contains a fix for this.
In the meantime, you can use the following syntax which works as expected: flow-coverage-report -i "src/**/*.js"

Thanks, it works as  intended without the report cmd.  :-)


Update PDF cover with new URL/logo

All is well.

@pczeeuw can you check this pull-request?

@Sander3003
Everything seems fine. The documentation-pr link shows the new cover.


navigation2: 1.0.3-1 in 'galactic/distribution.yaml' [bloom]

Increasing version of package(s) in repository navigation2 to 1.0.3-1:

upstream repository: https://github.com/ros-planning/navigation2.git
release repository: https://github.com/SteveMacenski/navigation2-release.git
distro file: galactic/distribution.yaml
bloom version: 0.10.7
previous version for package: 1.0.2-1

Resolves the build failures in lifecycle and behavior tree with missing a test dependency https://github.com/ros-planning/navigation2/commit/dc3eb0508824a6c12e8fc3b42c6879affe090d91


Add .sh to the 2-space line

[*.{ini,json,rb,yml,sh}]
indent_size = 2
indent_style = space

Already done.


[twitch] strange behavior of ad segments during live streams, not sure if player or yt-dlp issue

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
on embedded yt-dlp for mpc-hc - live streams just freeze during every ad segment, resumes no problem when its over. if i reload the stream at this point, the ad break screen comes up and continues to play at the appropriate time.
only started after i updated to latest release, not ideal of course since it looks like the stream is dead. maybe a relevant config in the client/extractor?
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

This seems more like a change in ffmpeg behavior than yt-dlp


chore: publish development Bintray packages

This commit includes several changes to adapt the CI configuration files
and Bintray publish script to perform development deployments.

Move our Bintray details to the Makefile
Deploy to a new Bintray component if RELEASE_TYPE is snapshot
Call publish-bintray-debian and publish-bintray-redhat in the CI
deployment script
Call the Bintray deployment scripts for RPMs

Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

It works! Check https://bintray.com/resin-io/debian/etcher-devel/1.0.0%2Bf6fcdc7

It should be easy to do the same thing for RPM packages after this.

I updated the PR to do the same thing for RPMs

https://bintray.com/resin-io/debian/etcher-devel is displaying an html-escaped string
Flash OS images to SD cards & USB drives, safe & easy (development version)
I guess after this PR is merged, users will be able to switch between the stable and snapshot versions by just changing their /etc/apt/sources.list.d/resinio-etcher.list?
It would be nice to see this PR also updating https://github.com/resin-io/etcher/blob/master/README.md#installers with RPM-from-Bintray instructions :)

I fixed the HTML encoding issue. I'll push an RPM package and figure out the instruction set :)

I'm assuming there are no further comments here, but let me know if that's not the case. RPM instructions have been sent by a user: https://github.com/resin-io/etcher/pull/1652

Travis Linux snapshot deployments are failing with:
./scripts/publish/bintray.sh -f dist/etcher-electron_1.1.1+4827267_amd64.deb -v 1.1.1+4827267 -r x64 -t snapshot -o resin-io -p debian -c etcher-devel
Please define the following environment variables:
  BINTRAY_USER
  BINTRAY_API_KEY
make: *** [publish-bintray-debian] Error 1
Script failed with status 2

I guess you need to add those encrypted variables to Travis?

Oops, I totally forgot to do so.


Allow pickling

Is it possible to allow pickling of the Limiter class?

Yes, just added it and released v0.2 to PyPI, check out the following test:
https://github.com/pzelasko/cylimiter/blob/5e443b909884243a9ea9b5ae163556af84d812cd/tests/test_limiter.py#L71-L87


Crossdock and Travis are buggy

Requirement - what kind of business use case are you trying to solve?
Ever since #815, the crossdock tests have been broken. This should have been caught immediately, but an error-handling issues in .travis.yml allowed the failed test to be ignored.
Problem - what in Jaeger blocks you from solving the requirement?
The existing crossdock config and Travis CI setup have multiple issues:

DNS config is not set up using dns_search: ., which sporadically causes errors when the a service never initializes, when in fact it has initialized, but the DNS config fails.
Command format (from #815) does not use the executable as the first argument, which is invalid.
Using locally tagged images without specifying :latest causes build failures associated with outdated versions of the image.
When using if/then in .travis.yml, use test || exit 1 to guarantee test succeeds. Otherwise, the then command succeeds regardless of exit code from test.

Proposal - what do you suggest to solve the problem or improve the existing situation?
Fix the above issues.

OK I found that the changes in #815 are actually correct. I still see some spurious errors now and then about a missing executable. I believe this is more of a build issue than a Docker syntax issue. We may not be building the images and/or checking that the binary exists. Either way, keeping issue for other docker-compose/Travis issues I saw.

Turns out MacBook is buggy, not tooling. My bad here.

Please document your findings

OK here it goes:

DNS lookup is a real issue for me, but not widespread enough to warrant the fix I proposed.
bash handles if/then as you would expect. Proof: (if true; then cat $PWD; fi) || echo failure => failure.
Command syntax is correct to drop executable path. Entrypoint is used and arguments are appended to the entrypoint.
make build-crossdock seems to work on Travis, just not locally. There is a real issue with timeouts that can easily be resolved, but I'd like to post a new issue for that. See documentation regarding that issue here: https://docs.docker.com/compose/startup-order.


.css files must be renamed to .scss else TypeError: undefined is not a function (0.3.9)

We've had to rename our CSS files from .css to .scss in order for SC5 Styleguide generation to succeed without error.
Interestingly, you can rename file.css to file.scss but continue to reference file.css in the gulpfile.js and generation succeeds.
gulp.task('styleguide:generate', function() {
return gulp.src('file.css')
.pipe(/* ... */)
// ...

Note that Styleguide sections aren't generated if the reference to file.css in the gulpfile.js is not updated.

This should be fixed in 0.3.10. Please re-open the issue if the problem still occurs.

Thank you; tested it and it is. (thumbsup)


How to detect DrawerClose in contentComponent

I have contentComponent: DrawerContainer
In DrawerContainer i have a button now I want to check text every time drawer cloesed by user
By using following code I am able to get the DrawerClose but I don't know how to pass it to contentComponent: DrawerContainer
const defaultGetStateForAction = DrawerStack.router.getStateForAction;
DrawerStack.router.getStateForAction = (action, state) => {
//use 'DrawerOpen' to capture drawer open event
if (state && action.type === 'Navigation/NAVIGATE' && action.routeName === 'DrawerClose') {
console.log('DrawerClose')
}
return defaultGetStateForAction(action, state);
};

@bradbumbalough yes I want to to detect that drawer is open or closed so I can change my button text based on drawer state.

If you can use anAnimated value, you can upgrade to 3.3.0 after this was merged yesterday:
https://github.com/react-navigation/react-navigation-drawer/pull/40
If you can’t use an Animated value, you can setup a listen on the animated value listener and set state when it’s open or closed.

navigation.state.isDrawerOpen

If you're using react-navigation 2.x, the navigation.state.isDrawerOpen is only available as a prop to the DrawerNavigatorConfig.contentComponent.  If you need a more robust way to determine if the drawer is open outside of the drawer itself, I iterated on the original post from @navneetccna and implemented a "middleware" to capture and expose the drawer state--
const DrawerNavigator:NavigationContainer = createDrawerNavigator(rootRouteConfigs, drawerNavigatorConfig);

let drawerIsOpen = false;

// Implementing a Router "middleware"
const defaultGetStateForAction = DrawerNavigator.router.getStateForAction;

// Hook into the state lifecycle for the Router
DrawerNavigator.router.getStateForAction = (action:NavigationAction, state:any) => {
  if(action.type === DrawerActions.OPEN_DRAWER) {
    drawerIsOpen = true;
  } else if(action.type === DrawerActions.CLOSE_DRAWER) {
    drawerIsOpen = false;
  }

  return defaultGetStateForAction(action, state);
}

export const isDrawerOpen = ():boolean => drawerIsOpen;

I used similar kind of solution but using state
import AppNavigation from '../Navigation/AppNavigation'

export const reducer = (state, action) => {
  const newState = AppNavigation.router.getStateForAction(action, state)
  if (state && action.type === 'Navigation/OPEN_DRAWER') {
  	newState['isDrawerOpen'] = true;
  }
  if (state && action.type === 'Navigation/CLOSE_DRAWER') {
  	newState['isDrawerOpen'] = false;
  }
  return newState || state
}


Add feedback form

🎮 feature Request
Below we can add a label to rate and give feedback to admin so that we can take input from user and try to improve as per the need.
Point down the features
feature points - It will provide direct interaction of user to admin through the site gaining positive response.
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@ananyag309 Remember on thing, the form will came in a popup form and not to big


⚠ Bofrost.de has degraded performance

In 2baf179, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1628 ms

Resolved: Bofrost.de performance has improved in 74ad0e9 after 38 minutes.


Check if the targeted components recovered from failures

The tool injects failures but doesn't check if the targeted components recovered from failures, it's important to add them to determine the pass/fail criteria for the run.

Tools like Cerberus can do intelligent monitoring of different dimensions of a cluster and provide a go/no-go signal.   When the tools observe changes, though, they do not have any knowledge of the cause of the changes.   It is up to tools like Kraken to interpret signal changes from Cerberus and correlate them with the scenario being executed or to do deeper component checks if go/no-go is too simplistic.
A tricky thing here is that a scenario might not simply cause the cluster to transition from good to bad.   Some of the scenarios, especially on large clusters, might cause the cluster to oscillate/bounce from go to no-go repeatedly in Cerberus or require more detailed component checks.
Each scenario should interpret the signal from Cerberus or perform additional checks to determine pass/fail.
As a starting point I'm thinking of a common class or other mechanism for reporting pass/fail which has a default implementation of a simple Cerberus go/no-go check as the most basic form of pass/fail.  Scenarios can then override the simple check with something more applicable to the scenario as needed.
@chaitanyaenr @paigerube14 @yashashreesuresh  Thoughts?  Better approach?

I think I was thinking about doing something where at the end of each iteration (after all scenarios listed in the config are done) it would look at the status of cerberus but also see if the killed pods/nodes have come back and are running/ready. I would keep track of the pods and/or nodes that were crashed during each scenario, the time and the namespace to keep track of how long the certain pods/nodes are down and if they recovered.
For pods I have seen that the pod names come back with the same name, is that always the case?

@mffiedler @paigerube14 Agree that consuming just the Cerberus signal for pass/fail is tricky. So the plan is to have the logic to check if the targeted component recovered fine explicitly and then consume the go/no-go signal from Cerberus after the scenario specific health check to make sure the other components didn't get affected because of the failure. So we will be tracking the killed pods/nodes during the scenario and check on them with a time out in place like @paigerube14 mentioned and in case the scenario succeeds, we then check Cerberus at the end of the iteration to see if the cluster is sane as a whole. Thoughts?
@paigerube14 The pods might not come back with the same name, so think it's better to check the replica count. For example, if we are killing apiserver, we can check using the label to see if there are 3 replicas of the pods up and running within a certain period of time. Thoughts?

Think we should add support in the config to mention a post action and expected output ( can be a simple oc command or a script ) which gets run at the end of the each scenario to compare the current output vs expected output to determine pass/fail. This way, we can mention the check and expected pod count ( 3 in case of apiserver and etcd for example ) in the config instead of baking in the logic into the code since the scenario can change based on the change in the config ( can be an app or system component, can be 3 replicas or 1 replica e.t.c. ). Thoughts?

I think having a separate post action might be helpful in this situation compared to just finding the pod/node that was killed. I think there would be a lot of extra searching going through all the current running pods/nodes to see if it came back.
I'm not exactly sure how we would do this though. I think we would need to reconfigure the config so that you would know which post action script to run after which scenario.
Maybe it could look like the following
scenarios:                                             # List of policies/chaos scenarios to load
- - scenarios/etcd.yml
  - postAction/etcd.sh
- - scenarios/openshift-kube-apiserver.yml
  - postAction/openshift-kube-apiserver.sh
- - scenarios/openshift-apiserver.yml
  - postAction/openshift-apiserver.sh

Thoughts?

It would be nice to have the post_action option native to Powerfulseal/PowerfulSeal config, we created an issue around it: https://github.com/bloomberg/powerfulseal/issues/203. Looks like the latest enhancement can help us with couple of checks: https://github.com/bloomberg/powerfulseal/pull/242. For the stuff which is not possible, we can go with postAction way like @paigerube14 mentioned IMHO.

Closing this since we now have support in Kraken to check for recovery of the targeted components as well as the cluster.


Limit FeeRate change for the UpdateFee msg to prevent sharp changes

Relates to #7666 and #7756
Detailed Problem explanation:
In lnd (lightning) there exist the feeupdate msg which allows channel openers to change the fee of the commitment transaction. For STATIC_REMOTE_KEY channels HTLCs which are part of the Commitment Transaction do have Timeout/Success Transactions which are signed with the same feerate as the Commitment Transaction (see BOLT3 for more details about the HTLC Transaction).
The FeeUpdate is only allowed to be sent by the Channel Opener but it should be in acceptable Limits, because especially for non-achor channels there is no way to accelerate this transaction (only if you pay a miner directly). CLN nodes will check for a specific range and will not allow the feeupdate from happening. If CLN does reject the feeupdate the channel will either be force-closed by the peer (lndk) or the channel becomes unusable and needs to be force-closed eventually by the peer.
This PR fixes 2 Problems:
No valid Fee Estimation by our backend
In case you either wipe your mempool or restart a new bitcoind node you want to connect to your lnd node, there is a short time period where bitcoind is not reporting any fee estimations because it does not have enough data available.
It will report:
bitcoin-cli estimatesmartfee 3
{
  "errors": [
    "Insufficient data or no feerate found"
  ],
  "blocks": 0
}

In such cases lnd would just read this response and the fee estimation would remain zero and then would just enforce the min mempool fee instead. This is a bad choice because when our mempool is big enough this fee rate is always 1 sat/vbyte and does not represent the current fee rate conditions. This PR will return an error in such cases and lnd will use its fallback feerate of 25 sats/vbyte. It is always better to overestimate rather than underestimate in such cases.
Limit Fee Estimation when channel is drained locally
Moreover Lnd reevaluates the MaxFeeRate it is willing to allocate for a Channel every time a feeupdate  msg will be sent. When the channel is locally drained this could lead to a situation where we decrease the feerate all the way to the fee floor which does not reflect the current bitcoin network fee rate correctly and could also lead to our peer rejecting these low fee rate updates. With this PR we do not lower the MaxFeeRate we are willing to allocate for this channel if it would fall below the old fee rate. This guarantees that if we had a high fee rate on a channel, that we do not decrease it when the local balance is drained.
Locking for a Concept Ack here before writing tests.
This change will not fix existing channels which ran into this issue, but will most likely prevent future channels form being unusable when proposing very low fee rate updates leading to the channel-peer rejecting those.
Change Description
This PR limits the FeeRate update to a maximum of 30% of the old feerate. It only applies to non-anchor channels because for those the negotiated fee cannot be changed when resolving on-chain.
Open for discussions whether we want to pursue this route if 30% is too conservative and so one.
Needs some style fixing will solve this in the coming days.
Tests
I currently just updated the unit tests in the lnwallet package. I think it is enough and testing this in the htlcswitch where we drain the channel locally and send consecutively fee updates with the default fee-allocation might not be worth it IMO, what are your takes?

This concept will not fix the problem, stated in https://github.com/lightningnetwork/lnd/issues/7756#issuecomment-1638969967. I need to rework this to make sure we do not scale down the comitment fee all the way to 253 sat/kw.
Hold on for review yet !

Will this PR fix stuck channels or will it only prevent channels from entering a stuck state in the future?

Will this PR fix stuck channels or will it only prevent channels from entering a stuck state in the future?

It cannot undo the feeupdate which happend in the past (your case currently) tho it will prevent low feeupdates in the future.

This change will not fix existing channels which ran into this issue, but will most likely prevent future channels form being unusable when proposing very low fee rate updates leading to the channel-peer rejecting those.

@yyforyongyu: review reminder
@ziggie1984, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@ziggie1984, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@ziggie1984, remember to re-request review from reviewers when ready

@yyforyongyu: review reminder
@ziggie1984, remember to re-request review from reviewers when ready

Suffered from this behaviour on my local node as well now, I think this should be addressed asap, Channel is unusable now until we reach lower feelimits.
2023-12-10 13:30:59.882 [WRN] HSWC: ChannelLink(aa4a1c1313bed1063a9529840062c3263aced0b544b28105e79019f91e9c2bba:2): received warning message from peer: chan_id=ba2b9c1ef91990e70581b244b5d0ce3a26c362008429953a06d1be13131c4aa8, err=update_fee 253 outside range 4724-702240 (currently 1795)

@yyforyongyu: review reminder
@ziggie1984, remember to re-request review from reviewers when ready

Looking good, just a few nits. One thing I think we should do in a followup PR is to make it more clear on how we update fees for anchor vs non-anchor channels here:

Agree I think this relates to https://github.com/lightningnetwork/lnd/issues/8302, which should get rid of the MaxAnchorsCommitFeeRate config setting and always make sure the relay feerate of its average Peers are met.

@ziggie1984, remember to re-request review from reviewers when ready

@ziggie1984, remember to re-request review from reviewers when ready

@ziggie1984, remember to re-request review from reviewers when ready

@ziggie1984, remember to re-request review from reviewers when ready

🚢 would be great for this ship to set sail

@ziggie1984, remember to re-request review from reviewers when ready

@ziggie1984, remember to re-request review from reviewers when ready

need a second reviewer 👀  cc @saubyk

@ziggie1984, remember to re-request review from reviewers when ready

@ziggie1984, remember to re-request review from reviewers when ready

@coderabbitai review

Last Push was just a rebase.

Idk what's going on with CI but there's a lot of complaining checks that I can't figure out why they are failing.

Related to the build cache. Going to put up a fix to reduce the cache size.
@Crypt-iQ you self-requested review on this PR after 2 approvals. Should we block on your review?

Related to the build cache. Going to put up a fix to reduce the cache size. @Crypt-iQ you self-requested review on this PR after 2 approvals. Should we block on your review?

Yes

Needs a rebase.


Problem with permission staff chat plugin

Description
i have problem with luckperms bungeecord when i give helper (and moderator by group.helper) permission to staffchat.join and .read (with message [SC] [+] Nick join the lobby) but they didn't see it
but when i give permission to see afk message they can read it. I wrote to staff chat support they wrote its problem with luckperms, i wrote 5x message on support in 2 days - 0 help, can someone help?
Reproduction Steps
I don't know, help?
Expected Behaviour
All will working
Server Details
bungeecord
LuckPerms Version
v98
Logs and Configs
No response
Extra Details
No response

You can use the verbose command to debug what's going on :)
https://luckperms.net/wiki/Verbose


can the file path be written in URL instead of string ?

    let itemList = objects.dataName
    let fileManager = FileManager.default
    do {
        let documentDirectory = try fileManager.url(for: .documentDirectory, in: .userDomainMask, appropriateFor: nil, create: false)
        let stream = OutputStream(toFileAtPath: documentDirectory.appendingPathComponent(<#T##pathComponent: String##String#>), append: false)
        let csv = try! CSVWriter(stream: stream!)
        try! csv.write(row: ["name", "x", "y", "width", "height"])
        for _ in 0..<(itemList.count-1) {
            try! csv.write(row: [String(describing: objects.dataName.last), String(describing: objects.dataX.last), String(describing: objects.dataY.last), String(describing: objects.boundingX.last), String(describing: objects.boundingY.last)])
        }
                csv.stream.close()
    } catch {
        print("oops something went wrong")
    }

something right this? because I want to create a new file's name for every .csv save files

let documentDirectory = try fileManager.url(for: .documentDirectory, ...
let stream = OutputStream(toFileAtPath: documentDirectory.appending ...

In this case, you can use OutputStream (url:append:) instead of OutputStream(toFileAtPath:append:). e.g.
let documentDirectory = fileManager.urls(for: .documentDirectory, in: .userDomainMask)[0]
let csvFile = documentDirectory.appendingPathComponent("output.csv")
let stream = OutputStream(url: csvFile, append: false)


Stream to chromecast

Feature-Request:
Stream the audio to a chromecast device.
What do you think?

Fell free to fork the project and add the feature you need.
I'm not even sure that something is required at the project level. Maybe a rpi config can do the trick.
As I don't need the feature I'll not work on it.
Good luck for that anyway!


Make .as_proto_move() member functions rvalue-ref qualified.

This proposal is a breaking change.
A number of member functions in the Bigtable library are destructive calls to extract the underlying protobuf in a wrapper class.  These should be rvalue-ref qualified to signal that they are destructive functions.  That is, where we have:
class Foo {
public:
  SomeProto as_proto_move() { return std::move(proto_); }

private:
  SomeProto proto_;
};

That should become:
class Foo {
public:
  SomeProto as_proto_move() && { return std::move(proto_); }

private:
  SomeProto proto_;
};

or even SomeProto as_proto() &&.

Fixed by #1618.


User successfully deleted message shown in user delete confirmation window

https://user-images.githubusercontent.com/24982871/180675033-d96189db-0f76-4208-afcd-20bbeda5fa89.mov

Fixed in https://github.com/wso2/identity-apps/pull/3243


Items in a list are non-unique when using examples

For a graphql field with fake directives like below :
codes: [String] @listLength(min: 1, max: 3) @examples(values: ["1", "2", "3", "4", "5"])
i am getting duplicated results many times. Is there a way to tell the faker that i want the items to be unique?

Would be nice if we have a way to pass a function that receive the params and return the fake data.


Visual bug with dictionaries

Having a weird visual bug where removing an element from the middle of a dictionary which uses > 1 line values causes some really annoying overlap that makes it impossible to keep working. It seems to be purely visual but the only way to fix it is to enter/exit play mode.
Example: http://gfycat.com/ExcellentMammothBooby
Code I was using to reproduce:
public class DictHaver : FullInspector.BaseBehavior
{
    public Dictionary<string, DumbStruct> dict_;

    public struct DumbStruct
    {
        public int i_;
        public string str_;
        public List<int> ints_;
    }
 }

Okay, thanks - this looks like some metadata is getting corrupted. I'll be able to take a look in a few days.

Can you try changing fiGraphMetadata.cs line 260 from
copiedGraphs.Add(metadata._childrenInt[i]);

to
copiedGraphs.Add(metadata._childrenInt[migrations[i].OldIndex]);

Thanks

Just tried it. Appears to have fixed the issue, thanks!

Awesome! Thanks


Piral CLI creation results in build error

Bug Report
For more information, see the CONTRIBUTING guide.
Prerequisites

[x] Can you reproduce the problem in a MWE?
[x] Are you running the latest version?
[x] Did you perform a search in the issues?

Environment Details and Version
Piral CLI Version 0.8.3
Description
Creating a new Piral instance from CLI and trying to run it as an example fails with a build issue.
/Users/kpyfan/git/piral-poc/src/index.tsx:14:14: Cannot resolve dependency 'piral/api'
    at Resolver.resolve (/Users/kpyfan/git/piral-poc/node_modules/parcel-bundler/src/Resolver.js:71:17)
    at async Bundler.resolveAsset (/Users/kpyfan/git/piral-poc/node_modules/parcel-bundler/src/Bundler.js:433:18)
    at async Bundler.resolveDep (/Users/kpyfan/git/piral-poc/node_modules/parcel-bundler/src/Bundler.js:484:14)
    at async /Users/kpyfan/git/piral-poc/node_modules/parcel-bundler/src/Bundler.js:608:26
    at async Promise.all (index 4)
    at async Bundler.loadAsset (/Users/kpyfan/git/piral-poc/node_modules/parcel-bundler/src/Bundler.js:599:21)
    at async Bundler.processAsset (/Users/kpyfan/git/piral-poc/node_modules/parcel-bundler/src/Bundler.js:557:5)
    at async PromiseQueue._runJob (/Users/kpyfan/git/piral-poc/node_modules/parcel-bundler/src/utils/PromiseQueue.js:48:7)

Steps to Reproduce

Initialize a new Piral project using Piral cli (piral new --target piral-poc)
Run Piral instance using Piral cli (piral debug)

Expected behavior
A working piral instance should be stood up and a sample page should render
Actual behavior
Parcel Bundler cannot find one of the dependencies

Hi @kpyfan - thanks for raising the issue.
This is indeed a bug in the template for 0.8.3. Even though this may turn off people we've decided against shipping a hotfix for this. As a workaround just change the export to
export * from 'piral';

Alternatively, go for @next (e.g., piral new --target piral-poc --tag next). This is the 0.9 preview, which should be already good enough for getting the hands dirty, too.
Sorry for the inconvenience! :beers:
(I'll leave the item open until 0.9 is released)

Remark:
For the 0.9 preview to work correctly please also update the tooling to the @next preview level. npm i piral-cli@next. Thanks!

Great, I've applied the fix locally and can confirm that it works. Thanks for the quick response!

We've shipped this now already with a 0.8.4 together with 2 more bug fixes / improvements.


Release notes for 1.0a3

118 commits! https://github.com/simonw/datasette/compare/1.0a2...26be9f0445b753fb84c802c356b0791a72269f25

Remember not to include changes from this:
https://github.com/simonw/datasette/blob/26be9f0445b753fb84c802c356b0791a72269f25/docs/changelog.rst?plain=1#L9-L31

Dropped support for Python 3.7
New Justfile
default_allow_sql setting
#1970
datasette.render_template() now accepts a Context subclass as an alternative to a dictionary
#1955
#1979
#2106
#2007
https://github.com/simonw/datasette/issues/2130
https://github.com/simonw/datasette/issues/1771
https://github.com/simonw/datasette/issues/2079
https://github.com/simonw/datasette/issues/1153

:ref:`default_allow_sql setting <setting_default_allow_sql>`

OK, I've done the small changes - still need to document the big JSON changes though.
Those aren't covered by the regular documentation either so I need to update that.


Gotcha with async prepared statement execution

I don't think this is a bug report as such, more of a gotcha that might be worth mentioning in docs.
The scenario is fetching some data in parallel and inserting each batch as it's received over the network.
Previously with the synchronous api, when calling bind / execute on a prepared statement shared between all batches, there was never a case where execute would execute with bound data other than the data bound immediately before the execute call.
Now with the asynchronous API, it seems it's possible for race conditions to occur in this scenario, where I'm guessing the prepared statement is reset or rebound by another network request handler between binding and executing. This causes occasional errors

SQLite code: 19 execution error: NOT NULL constraint failed: table.id

Can be resolved by queuing up the data to be inserted, or probably by not reusing the prepared statement between batches - haven't tried that yet though.

Interesting, you should be using transactions anyways to insert data anyways as it is a disk operation that can fail. Does using prepared statements on inserts have a speed benefit? It should be mostly an append operation and maybe an index update?

Maybe there is something we can do here @rflopezm. We should put a mutex when a prepared statement is executing to prevent this race condition. This can be done on TypeScript on index.ts no need to modify the C++ code.

manually calling BEGIN TRANSACTION is not the same as using db.transaction. db.transaction has a built in mutex to prevent race conditions between statements. I guess the speed up you are seeing is not because of the prepared statement, is the avoidance of this mutex but you loose the guarantees of consistency.

I finally understood the issue. Unfortunately, the changes I was making won't solve this directly by limiting the threads to one. The issue is queueing work to a thread takes time before the next task must be consumed. There is one easy solution though, which is making bind async. I will do this. It will fix any concurrency issues within the same connection when paired with the changes of #204

@ospfranco I tried a few different methods including the ones above and this was the fastest to insert - we're loading data from an API and inserting 100s of thousands of records across around 100 tables in batches of 200-2000. Using executeBatch was significantly slower (and on par with things like queuing up the batches for insertion rather than letting them insert immediately). We can't easily use db.transaction for this use case because we wanted basically 1 transaction per table which is split across multiple HTTP response batches.
We were originally reusing the prepared statement across simultaneous HTTP response handlers when doing the inserts. Removing that (i.e. going to 1 PS per handler) hasn't changed performance too much and has resolved the issue for us as we were already binding/executing records in a loop within each batch, so no concurrency issues there.
Re making bind async - is that so that it can be queued with the execute calls in the correct order? If so makes sense. If not then not sure it'll help - the issue is basically that bind / execute aren't an atomic unit so the most recent bound data isn't necessarily what you expect if you have multiple in-flight async function calls that might try to call bind / execute on a shared prepared statement.
I think I'm leaning towards this belonging in the category of holding it wrong, but if there's a way to make it more foolproof then awesome :)
Thanks for looking into it 👍🏻

You are not holding it wrong. It is a built-in race condition

New version is out, bind is now async and needs to be awaited and with a single thread you should not face statements getting lost:
let preparedStatement = ...
await preparedStatement.bind(...)
await preparedStatement.execute(...)

Awesome, thanks again @ospfranco ❤


Firestore field expects String value for integerValue

The following snippet will throw int is not a subtype of String:
// ...
final storeApi = FirestoreApi(authorizedClient);
final resp = await storeApi.projects.databases.documents.createDocument(
      Document.fromJson({
        'fields': {
          'intfield': {'integerValue': 55}
        }
      }),
      'projects/$PROJECT_ID/databases/(default)/documents/',
      COLLECTION_ID);

Source of error: https://github.com/dart-lang/googleapis/blob/ee696b1/generated/googleapis/lib/firestore/v1.dart#L5203
I can imagine a scenario where it'd make sense (eg. storing really large numbers) but most of the use-cases would consider this a bug. Is this intentional?

The discovery document for firebase referenced in discovery APIs list, says:
        "integerValue": {
          "description": "An integer value.",
          "format": "int64",
          "type": "string"
        },

Hence, I think this is intentional.
This package is automatically generated APIs. So it probably makes sense to use strings because that can represent large numbers. I would suggest finding/writing a wrapper around this package, to make a nicer API.

This package only provides APIs generated from discovery documents. Through these APIs many google services can be accessed, but the APIs can have rough edges.
A package like package:gcloud attempts to provide some nice wrappers for datastore and cloud storage. It would be nice to have the same for firestore, if someone haven't written it already :)


Fix generating flow name with incrementing number

Fixes #3295

[x] Bugfix (non-breaking change which fixes an issue)

Proposed changes
The logic around generating the name of a newly added tab was broken a while ago so you could end up with multiple tabs called Flow 1.
This PR fixes the logic around detecting if a candidate name already exists.

Coverage remained the same at 67.411% when pulling df70c8a800afdf7b977e22699ecdc641ce1d8caf on flow-name-increment into 6d2793cac6ced524de30ef88e6deb07795382701 on master.


GitHub actions workflow to digital ocean droplet

Many meaningless commits, because I didn't undo commits :) when testing it

solves issue #60


Added Slivers to Dashboard Page. Fixed small typo in README

Fixed small typo in README
Made Column() to a CustomScrollView() with Slivers

Old
New

Even though the current approach works, it has a few problems.

Overflow

The top bar (header) overflows when the phone's font size is increased.
However, this doesn't happen when the font size is decreased.

Increased(Not working)
Decreased(Working)

There is a beginning small lag. ie. When the app starts, the dashboard first only shows the headers. Then after <1 sec or so, the remaining portion of the dashboard shows up.

This is because the first build is used to get the height of the header. With the header height known, the next build can then build the complete layout. ie the entire screen.

Example

@leilanihagen and @daemon29 , you can tell me what do you think about these problems. I was thinking of trying to semi-fix fix the lag problem by at least making the remaining portion of the screen appear gradually in an animation instead of appear suddenly. But that can be in a future pull request!
Let me know if I need to make any changes!

I think the lag happen so clearly in debug mode, I will check if it perform better in release mode


TF_AddGradientsWithPrefix doesn't seem to lock the gradients properly

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Using TF-Java
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS
TensorFlow installed from (source or binary): Maven Central binary
TensorFlow version (use command below): v2.4.1

Describe the current behavior
When training a model I'm hitting a non-determinism issue, the models are initialized identically, and fed identical data in an identical order, with inter-op and intra-op parallelism both set to 1, but I can get complete training failure when building simple MLPs and CNNs on MNIST.
TF-Java uses TF_AddGradientsWithPrefix to construct the gradients. We then wrap that in Optimizers to make a higher level front end to training, similar to the v1 optimizers package, and Keras in v2. As gradients are only available in Graph mode in the C API our code is most similar to the v1 optimizers package. I think we want to have the gating behaviour set to GATE_OP (https://www.tensorflow.org/api_docs/python/tf/compat/v1/train/Optimizer), but that's all implemented entirely in python, and the C API codepath doesn't seem to add the required control dependencies to ensure the gradients are all computed before being back-propped any further (in Python that's performed here - https://github.com/tensorflow/tensorflow/blob/85c8b2a817f95a3e979ecd1ed95bff1dc1335cff/tensorflow/python/ops/gradients_util.py#L692, but there doesn't seem to be an equivalent in the C API here - https://github.com/tensorflow/tensorflow/blob/5dcfc51118817f27fad5246812d83e5dccdc5f72/tensorflow/cc/framework/gradients.cc#L568).
Describe the expected behavior
The model should train identically with identical gradients.
Standalone code to reproduce the issue
See this test in TF-Java - https://github.com/Craigacp/tensorflow-java/blob/03402b30e271a46438c1feff12409095737f3d3e/tensorflow-framework/src/test/java/org/tensorflow/framework/optimizers/GradientDescentTest.java#L121. This test when run complains that out of the 20 runs some of them diverged even when trained using identical graph defs on identical data, for an identical number of steps, when using single threaded computation.

Has anyone had a chance to look at this?

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.

It is still broken, though we've found a work around in Java which induces better locking of the gradients. It's not a proper fix, and so it would be good to have this be fixed in the C++ implementation.


Song recognition giving error

When I tried to recognize the song, it is giving me the following error. How to fix it?
Code:
import asyncio
from shazamio import Shazam

async def main():
  shazam = Shazam()
  out = await shazam.recognize_song('sample.mp3')
  print(out)

loop = asyncio.get_event_loop()
loop.run_until_complete(main())

Error:
Traceback (most recent call last):
  File "D:\programs\shazamio_shazam_t.py", line 11, in <module>
    loop.run_until_complete(main())
  File "D:\Python\lib\asyncio\base_events.py", line 616, in run_until_complete
    return future.result()
  File "D:\programs\shazamio_shazam_t.py", line 7, in main
    out = await shazam.recognize_song('sample.mp3')
  File "D:\Python\lib\site-packages\shazamio\api.py", line 220, in recognize_song
    audio = self.normalize_audio_data(file)
  File "D:\Python\lib\site-packages\shazamio\converter.py", line 45, in normalize_audio_data
    audio = AudioSegment.from_file(BytesIO(song_data))
  File "D:\Python\lib\site-packages\pydub\audio_segment.py", line 728, in from_file
    info = mediainfo_json(orig_file, read_ahead_limit=read_ahead_limit)
  File "D:\Python\lib\site-packages\pydub\utils.py", line 279, in mediainfo_json
    info = json.loads(output)
  File "D:\Python\lib\json\__init__.py", line 357, in loads
    return _default_decoder.decode(s)
  File "D:\Python\lib\json\decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "D:\Python\lib\json\decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

@YashMakan Hello,
At first I thought that the problem was that the mp3 format could not be recognized, but I just checked - everything works.
Do you have it installed ffmpeg?

Yes and when I entered ffmpeg -version.  It returns version 4.2. I am unable to figure out the problem.

@YashMakan give u mp3 file

@dotX12  https://easyupload.io/rgcukg

@dotX12 https://easyupload.io/rgcukg
Hmm, everything works for me stably with your file, you probably have problems with pydub or ffmpeg

https://transfer.sh/1dE2aJk/KWHmwkbzT9.png

ffmpeg version 2021-02-07-git-a52b9464e4-full_build-www.gyan.dev Copyright (c) 2000-2021 the FFmpeg developers
built with gcc 10.2.0 (Rev6, Built by MSYS2 project)
configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libglslang --enable-vulkan --enable-opencl --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint
libavutil      56. 64.100 / 56. 64.100
libavcodec     58.121.100 / 58.121.100
libavformat    58. 67.100 / 58. 67.100
libavdevice    58. 11.103 / 58. 11.103
libavfilter     7.102.100 /  7.102.100
libswscale      5.  8.100 /  5.  8.100
libswresample   3.  8.100 /  3.  8.100
libpostproc    55.  8.100 / 55.  8.100

Yes, I think that my ffmpeg version is old. I am reinstalling it. Thanks for the help.

I reinstalled the new version from the official website i.e ffmpeg version 4.4-essentials_build-www.gyan.dev and now when I run the below code it works
>>> sound = AudioSegment.from_mp3("sample.mp3")
>>>

but...
sound = pydub.AudioSegment.from_file(BytesIO(open("sample.mp3",'rb').read()))

giving the same error i.e json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0).
What should I do now?

@YashMakan, hmmmm.
I seem to have found a solution.
https://github.com/jiaaro/pydub/issues/450

@dotX12 Thanks I will follow the issue jiaaro/pydub#450 for updates. Also, are you using FFmpeg in windows? if so, if possible can you send the FFmpeg... So that I can install the same working version of ffmpeg.

@YashMakan, in windows i use very old version...
https://transfer.sh/jeoDp/ffmpeg-2021-02-07-git-a52b9464e4-full_build.7z
I think you need to read what is in issue and try to do it, because I have a very old version on Windows. On ubuntu, I use the most current version and everything works well for me.

Fixed in 0.5.0.


Create a branch for secondary content

The new branch for secondary content will be patch/content/secondary based on feature/body

Branch created


Check spawn rules filter: minecraft:operator

Check if the spawn rule filter: minecraft:operator is update to date

I believe this was mistakenly added under spawn rules on official docs.
https://learn.microsoft.com/en-us/minecraft/creator/reference/content/entityreference/examples/definitions/nestedtables/operator

Whoops :D


Wants page

Wants page

[ ] list all existing commodities and quantity
[ ] checkbox for commodities list to check off wants
[ ] save

There's crispy forms, model forms, and forms. Model forms is a short form for displaying the model's fields. Crispy forms has to do with rendering the forms.
Forms is what we need, since we want to display all the items in the table as a single form. I'm not sure how well django forms will handle that. I rendered and processed it in react before.


(A11y severity 4) Infinite scroll footer visibility

Allow easier navigation to footer on infinite scroll pages.
It would be nice, though, if we could come up with a way to make the footer available on pages with infinite scrolling. Something like pinning it to the bottom of the window (position: absolute; bottom: 0) and then adding an opacity gradient to the bottom 50 pixels or so of content to make it clear that more content is available below the window. Kind of like what Amazon does with their "Read More".

Closing this as solving #3955 should be enough.


Missing phonemes in Japanese

I am trying to train a Japanese TTS model using piper with espeak-ng as a phonemizer backend, I encountered this when I am processing the dataset. Is there any solutions?

I am on Ubuntu 22.04.

Use espeak directly will solve the problem and the TTS model will work

@SchweitzerGAO It looks like I may need to add some more phonemes to Piper. Without this, some words won't be pronounced correctly.


Need to pair every time

I could pair ble Shining Keyboard after downgrading the Arduino Mbed OS Nano Boards to the 2.1.0 version.
My issue is How can I make the Nano board memorize that it has been paired with other BLE devices before and connect automatically.
BR

I would like to know this too.


Merge prTesting_201908011012 branch to master branch

Docs Build status updates of commit 1bd0e95:
:clock10: Pending: waiting for processors (9 builds ahead of you)
:warning: Docs Build is busy, currently there are 9 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 1bd0e95:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestCon.md
:bulb:Suggestion

Details

split/updateTestCon.md

[Suggestion] Missing attribute: author. Add the current author's GitHub ID.
[Suggestion] Missing attribute: ms.author. Add the current author's Microsoft alias.
[Suggestion] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.
[Suggestion] Missing attribute: ms.topic. Add a valid value to indicate the article type.
[Suggestion] Missing attribute: ms.date. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Move release process doc and update READMEs

Proposed changes
Problem: The release process doc contains information that is not relevant for NKG users, only for developers
Solution: Move the release documentation alongside the other developer documentation, and add versioning and release information relevant for an NKG user to the README
This commit also updates the docs README to include the missing monitoring doc reference.
Closes #896
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that all unit tests pass after adding my changes
[x] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

What's the reason behind leaving the Versioning and Release Planning and Development sections in the docs/developer/release-process.md even after moving it to the higher level readme? I thought that the information for NKG users would be split and moved from the information for developers.

There's also a link to the release process doc in the logging guidelines that needs to be updated: https://github.com/nginxinc/nginx-kubernetes-gateway/blob/main/docs/developer/logging-guidelines.md#evolution


[CXF-7210] Fix StringIndexOutOfBoundsException

The logic goes as follows:

Base- & request-URI are the same, then only add base-URI.
If request-URI starts with base-URI, only add the parts from request-URI that are not already included in base-URI
Otherwise add both base-URI and request-URI

There is a single test failure (see https://builds.apache.org/job/CXF-Trunk-PR/org.apache.cxf.systests$cxf-systests-ws-rm/269/testReport/org.apache.cxf.systest.ws.rm/SequenceTest/testOnewayAnonymousAcksSuppressed/), however that seems to be unrelated to the above changes.


docs/source/environments_101.rst: fix a few typos

Oof, a lot of those were really bad. Thanks for taking the time to correct them!

@arielf The published documentation has been updated. Thanks again!


HOTFIX: Fix compilation error in ConsumerPerformance

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The compilation error was my fault. I tweaked a message and inadvertently added an extra parenthesis.


Can go to definition for compoent directly open the source file in option API?

When I use the Option API, the go definition function jumps to the component option instead of the source file

Duplicate of #1245


Real time client memory leaks fixes

This change was originally made by @mikepulaski in ably-cocoa fork (https://github.com/tupleapp/ably-cocoa/tree/gcd-leaks).

Looks solid. Any ideas why checks aren't passing?

well, it looks weird ... because sometimes they pass and sometimes not. I'll re-run all jobs an we will see if they'll pass or not

I double-checked the failing GCD iOS test and there was an issue with this https://forums.swift.org/t/retain-count-set-to-2-and-no-deinit-called/43571/4
and finally, I changed it to this https://www.swiftbysundell.com/articles/using-unit-tests-to-identify-avoid-memory-leaks-in-swift/#closures
commit here: 0f8e29f9f6089d670a7abf145b754ff6f284d9ea

I would mark each line with retain/release counter, such as "+1 to scheduledBlock, total = 2". Otherwise it's very frustrating to read this with a fresh eye.

why? In this solution, we don't need to check to retainCounter, this was in the previous solution and it was doubtful.

Just to give the next reader a quick idea on what's going on in this test.

I would mark each line with retain/release counter, such as "+1 to scheduledBlock, total = 2". Otherwise it's very frustrating to read this with a fresh eye.

why? In this solution, we don't need to check to retainCounter, this was in the previous solution and it was doubtful.

Just to give the next reader a quick idea on what's going on in this test.

here 6df222c746bc08e4eda0ca94332cc32865fec592


Load Testing on Python Client for Custos

Create a Jmeter setup to do the load testing of API
DOcument all the observations for the final submission.

Done


Remove MSVC support from autotools

Original pull request by Alexey Pavlov (Bitbucket: [Alexey Pavlov](https://bitbucket.org/Alexey Pavlov), ).

Original comment by Alexey Pavlov (Bitbucket: [Alexey Pavlov](https://bitbucket.org/Alexey Pavlov), ).

Any plans to merge it?

Original comment by Alexey Pavlov (Bitbucket: [Alexey Pavlov](https://bitbucket.org/Alexey Pavlov), ).

Reasoning was to migrate to new autotools. But no matter now as CMAKE build present and its too late - issue from 3 years old.


The default constructor for proxy entities must include all the notNull attributes

The primary key will be included in default constructor parameters only if it is not autoIncremented.


docker entrypoint ?

I was able to download the docker tar archive (which took a long time, as it is very large)
However, when I try to run it (using docker run -it mix_net there is an error saying "no command specified"
When I try to specify an entrypoint, such as "/usr/bin/bash", it says "unable to start container".
What is the entrypoint please?

Hi, I think it might be "/bin/bash".
After graduated I couldn't connect to the server I used to use so it was difficult to check.
BTW, I don't know much about docker.
Did I share my docker tar in the wrong way, causing it to be so big?
Please give me some tips.

The command is "bash" not "/bin/bash".
Sorry for giving the wrong answer.

No problem !
It seems to work now, thanks.
You shared the entire docker image, which works, but you could also share the Dockerfile you created the docker with, and maybe the docker-compose.yml file as well.
That way, everybody could rebuild the image on their own, without needing to download the entire image.


How are NavigationView icons implemented?

Hello,
I am trying to understand how icons are displayed in left NavigationView on this app and could not find any reference in the source. I saw that in the ControlInfoData.json file image path like this - "ImagePath": "". What is this? And there is a NavigationViewItemIcons folder but all icons on app look different than these pngs. Also, are these really pngs? Basically I want to understand how I can insert icons for my app which I am modelling on this one. I do not know if this is the right place to put this question. Sorry about that. Any help will be appreciated.
Thanks.

I could get the unicode character to work but it still crashes randomly when I used this character from range PUA EA00-EC00. I am using the character EAFC which is a market icon.
And I could not get my png to work. My icon file is png - I am attaching it here. And I am giving the path as "ImagePath": "ms-appx:///Assets/market.png",

I could get the unicode character to work but it still crashes randomly when I used this character from range PUA EA00-EC00. I am using the character EAFC which is a market icon.

That's strange. I used this unicode character and it worked fine for me: 

And I could not get my png to work. My icon file is png - I am attaching it here. And I am giving the path as "ImagePath": "ms-appx:///Assets/market.png",

Did you also add a reference to the icon in your project? If you don't add a reference to it, the icon will not be copied to the output folder and as such, the app will crash as it can't find the icon.

That's strange. I used this unicode character and it worked fine for me: 
Yes I used same unicode character and it is crashing on alternate launch of app. One successful launch and then next crash.

Did you also add a reference to the icon in your project? If you don't add a reference to it, the icon will not be copied to the output folder and as such, the app will crash as it can't find the icon.

Yes, I missed this step. Now I am able to use the icon. But again same crash on alternate launch.
Crash happens for me for both unicode as well as BitmapIcon. There seems to be a pattern. Crash happens when the icon is rendered. If I make sure that icon is not rendered on launch, then it does not crash. Do I need to release the resource somehow? Thanks for your help.

I think I am using UWP-WinUI2 one since I did not install the project reunion extension. But how can I confirm which one I am using? Also, is there a difference in the UI that is provided by the two? I think both of them give us the Windows 10 UI right? Also I know that Project reunion gives us fluent design. Does WinUI 2 not give us fluent design?
And should I try WinUI3 to see if it solves the problem? Also, I can share the repo with you with my code if you are okay with it.

I am not using Windows 10 Insider Build. Following is the branch (iconCrash) with my code. I have changed the project and solution name.
https://github.com/rajendrasp/Xaml-Controls-Gallery/tree/iconCrash

@smbridges91 Yes I think the ImageLoader does not support Unicode Characters which is likely because it was not needed yet.
@rajendrasp Have your questions been answered or is there anything else I/we can help with? :)

I'm seeing both questions as being answered. Closing after 90 days.


Use default snapshot for all our images

Update to use default snapshot for all our owned images. We pass the mco-imageTagSuffix in e2e test. but the grafana is still using the quay.io/openshift/origin-grafana:4.8.0. This PR is to define the default DefaultImgTagSuffix only in config.go. so we can use this default value in case cannot replace the correct images.
Signed-off-by: clyang82<EMAIL_ADDRESS>

/assign @morvencao

/test test-e2e

/retest

/retest

Remove support for loading and deleting dashboard by slug in grafana 8.x https://github.com/grafana/grafana/pull/35104
that is why the grafana-dev test can be passed. cannot find the grafana dashboard information by using <IP_ADDRESS>:3001/api/dashboards/db/$dashboard_name

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

@clyang82 Is this ready to merge?

/lgtm


Enable solr 6 to run on all ci agents except 4

What
To allow CKAN to run tests on CI machines we need to setup solr 6 on those machines.
Agent 4 will be excluded as that is intended for postgres.

I think you should probably set these on govuk-puppet/hieradata/class/ci_agent.yaml instead and add an exception on ci-agent-4.

In fact you might not even need the exception. It's not like other things like mongodb make the effort to disable themselves for agent 4, just as long as we don't schedule jobs on it.


Add E2E tests for caching behavior

Add E2E tests on Explorer BE API to assert that:

Repeated requests of dataset endpoints are cached by CloudFlare (can assert x-cache: Hit from cloudfront header exists)
/dataset-metadata endpoint is not cached (headers no-store, max-age=0)
[stretch] After replacing a dataset with a new revision and updating collection metadata (e.g. name), the BE API dataset-metadata/ endpoint returns updated response, reflecting the new S3 URL for the dataset and the updated collection metadata.

One goal of these E2E tests is to ensure that CloudFront configuration is not unwittingly changed in a way that breaks our desired caching behavior.  CloudFront is configured via Terraform, and we have no other real means of "testing" its configuration.

Repeated requests of dataset endpoints are cached by CloudFlare (can assert x-cache: Hit from cloudfront header exists)

Adding this test will break our ability to run the e2e smoke test locally, since it relies on AWS Cloudfront to add headers.

Repeated requests of dataset endpoints are cached by CloudFlare (can assert x-cache: Hit from cloudfront header exists)

Adding this test will break our ability to run the e2e smoke test locally, since it relies on AWS Cloudfront to add headers.

Possible to conditionally run only in cloud env?


Implement trade patch list

Describe the bug.
As documented in the pokered et al. projects there is more data being sent around than the Flipper app (or any existing open-source trade tool that I can find) takes in to account. This is referred to in disassembled code as the PatchList.
As far as I know, this applies to at least Gen I and Gen II.
Its 200 bytes and as far as I can tell is meant to be an index in to each half of the ~418 byte trade struct that is transmitted. The issue is that the byte value 0xFE is considered a SERIAL_DATA_NO_BYTE value. Likely an indicator that data was not ready in time so the byte is invalid.
I only have a really basic understanding of the concept at this point and will be doing more testing and debugging work in the near future. But my understanding at the moment is:

After the trade struct is sent, an additional 200 bytes is sent in two parts. I do not believe they are equally sized parts but I could be wrong.
The first part should be able to fixup party_data+0x00 to party_data+0xFC
The second part should be able to fixup party_data+0xFD to party_data+party_data_len
The patch list is simply an index of bytes to patch in order.

Any values in the party_data struct that equal 0xFE are instead set to 0xFF and the address is to the patch list.
A value of 0x00 means don't patch anything.
A value of 0x01 Means byte 0 of this part needs to be modified to be 0xFE in the party_data struct received
A value of 0xnn Means byte nn-1 of this part needs to be modified to be 0xFE in the party_data struct received

I have seen a few oddities in some trades, i.e. weirdly long HP bar that wasn't full after trade, that was resolved after a trip to the poke center.
My goal is to instrument some testing to force 0xFE values in the traded struct from the Flipper in safe locations and see how they are interpreted on the actual gameboy. I suspect I will see the whole trade struct shifted by 1 for each 0xFE that the Flipper transmitted.
Once I complete that, I should be able to instrument both building and sending as well as receiving and parsing patch lists.
Reproduction
I don't quite have a good grasp of the effects. However, a shift can be seen with the following patch:
diff --git a/views/trade.c b/views/trade.c
index fa17ce367e8d..b0a5e3f93655 100644
--- a/views/trade.c
+++ b/views/trade.c
@@ -455,6 +455,24 @@ void trade_enter_callback(void* context) {
         },
         true);

+    /* Test to expose issue #18 */
+    /* Set the pokmeon's level to 0xFE. Levels above 100 are possible but will
+     * roll back down to 100 on the next level obtained (or if you give a rare
+     * candy to a level 255 it will roll to level 0.
+     * https://bulbapedia.bulbagarden.net/wiki/List_of_glitches_(Generation_I)#Leveling_past_100
+     */
+    pokemon_fap->trade_block->party[0].level = 0xfe;
+
+    /* With that byte as 0xFE and no patch list implementation, the next data in
+     * the stsruct is the Pokemon's status condition. Lets set this to level 42.
+     */
+    pokemon_fap->trade_block->party[0].status_condition = 42;
+
+    /* At this point, the traded pokemon will end up being level 42, and its
+     * other stats are going to be all out of whack as well.
+     */
+
+
     // B3 (Pin6) / SO (2)
     furi_hal_gpio_write(&GAME_BOY_SO, false);
     furi_hal_gpio_init(&GAME_BOY_SO, GpioModeOutputPushPull, GpioPullNo, GpioSpeedVeryHigh);

Apply, build, run, and changing no options, trade the Bulbasaur. The level isn't 42 as predicted, its 0 somehow, but the Nickname, OT name, and OT ID are all correctly visibly shifted by 1. Levels in-game can go above 100 with tricks like this, the level glitching out isn't a result of setting level above 100. But, 0xFE being a NOP byte of sorts is true, I just don't fully know how to control it. But, this test can help show correct patch list implementation.

Target Framework
No response
Logs
No response
Anything else?
No response

I've been looking at this on and off a bit when I have time. And while there are still some gaps in what I've found, I believe I have enough info at this point to update the trade routines to take in to account and create a patch list as well as patch incoming data. I'll followup again once I've made some progress.

I've got patch list support fully implemented for both send and receive in the trade-features branch of my fork. Still doing some cleanup of the trade process to clean up extraneous variables, overly complex logic, and hardening the trade states to be less fragile and be able to handle unexpected states from the gameboy. There are still 1 or 2 more things I'm looking to implement, test, and prove out before I open a PR, but, this should be able to be cleaned up in the near future.


Pass connection argument properly to storage_accounts method for Azure metrics collection

Addresses BZ https://bugzilla.redhat.com/show_bug.cgi?id=1349768
Accidentally introduced in https://github.com/ManageIQ/manageiq/pull/8911 while trying to address a storage account / resource group mismatch. If @storage_accounts wasn't already set, it would try to with_metrics_services without an argument, resulting in wrong number of arguments (0 for 1).
This PR passes the argument properly.

@Fryguy @bronaghs I could use help creating even a basic spec for Azure metrics.


Live webcam input

Model as a helper class instance, similar to #5

For more portable projects, could model as an optional param to update.


Extra languages from to the default ones mapped in LanguageUtils.js

Hi, I would like to know if it's possible to add extra languages to the ShakaPlayer (audio, text) from those mapped in the LanguageUtils.js and in case how? For instance, If I want to add an other Spanish language that is not currently supported how can I do it? Thank you in advance.

Hi @pilipicus,
Did you mean adding languages to your content (e g another text track an Spanish or an audio) or adding another language for the localization of our UI (e g, names of the buttons etc)?