Hovering over map cancels other hovering actions

For example when resizing a jquery ui dialog with a openlayers map inside. If moving too quickly the mouse will hover the map instead of the resize-corner-div and it will stop resizing.
Example can be seen here:
https://jsfiddle.net/Ja7v2/2/
Another example is when trying to drag an external 'draggable' onto the map. If moving too fast it will stop dragging, example can be seen here: (Try and drag the red box onto the map)
https://jsfiddle.net/Ja7v2/4/
I notice a problem today when using jsfiddle. It is complaining that jsfiddle is on https but jquery scripts are being fetched through http. There is a shild icon to the right in the url-field where you can approve of it downloading from http(if using chrome).

Forgot to mention that this is 1.2.13.


Update k8s-tools image

Description
Changes proposed in this pull request:

Update Alpine packages

Related issue(s)

/cla-recheck


MacOS - zooming with gestures?

Is it possible to get gesture based zooming to allow for use of the trackpad to navigate through a file? For example - pinch in zoom out and vice-versa to zoom in?
This currently only works by holding down Control and scrolling up and down.
OS: MacOS 10.13.1
BN Version: 1.1.1020-dev Personal

Fixed in 1.1.1133

AWESOME <3


[WIP] Events and Actions

This adds events, actions and id.
The “Events & Actions” demo is a simple example that shows how how events and the ‘update’ action work.
The “Update by ‘id’” demo shows how ‘id’ can be used to reference an ‘element’

This implements the items in issue https://github.com/swipe-org/swipe/issues/24


Strip GPIO Pin is not accepted

Hello,
I installed McLighting here from GitHub on a Wemos D1 Mini.
In the definitions.h I set the Neopixel pin to GPIO 5 and then flashed the firmware on the Wemos.
However, the GPIO 3 is always displayed in the web interface, which is wrong.
The query with http://IP/config also shows the GPIO 3.
How do I get that switched to the GPIO 5?
I would be really grateful for help!
greeting
Scripthase

It's been dealt with.
#define USE_WS2812FX_DMA 0 must be commented out for it to work!


Link to native browser

Is it possible to link to the native browser from within themablebrowser? I have tried target="_system" but this opens the link inside themablebrowser. URL scheming seems to work, but is not preferable and apparently not supported by Safari.

This solves the problem: http://www.telerik.com/blogs/details/cross-window-communication-with-cordova's-inappbrowser


Enable finer grained control when creating polygon with UV Editor

Modifies 'auto-completion' of polygon to take into account the UV editor scale. Enables the
user to select points closer to each other than the current threshold of 8 pixels if they wish to do so.
Fixes #38240
Before:

After:

Thanks!

Cherry-picked for 3.2.2.


Crash when navigating between Scene on Android. Memory leak ?

[X] Review the documentation: https://docs.viromedia.com/
[x] Search for existing issues: https://github.com/viromedia/viro
[X] Use the latest ViroReact release: https://docs.viromedia.com/docs/releases

Environment
Please provide the following information about your environment:

Development OS: Windows,
Device OS & Version: Android 9
Version: ViroReact 2.16.0, React Native 0.59.3
Device(s): Huawei P20 EML-L09

Description
Great thank you for your library. It is a great job. We are building a City Quest where users are navigating between 10 scenes. There is a lot of 3D assets (~100 Mo in total). I could reproduce the problem with a very simple project (see code below).
On android, the app crash when navigating between scene (from 5 to 10 times) using the replace method. The crash is similar on debug and release variant. I suspect a memory leak (see profiler screenshot) : the heap is always growing when a new scene is displayed. It seems the previous scene is still retaining memory.
Reproducible Demo
Complete reproducible demo https://github.com/beauvaisbruno/virobugs/tree/scene-navigation
import {AppRegistry, View} from 'react-native';
import {Viro3DObject, ViroAmbientLight, ViroARScene, ViroARSceneNavigator} from "react-viro";
import React from "react";

const SceneOne = ({sceneNavigator}) => {
  return <ViroARScene>
    <ViroAmbientLight color={"#aaaaaa"}/>
    <Viro3DObject
      source={require("./res/heavy0.glb")}
      type="GLB"
      position={[0, 0, -2]}
    />
    <Viro3DObject
      source={require("./res/clickable0.glb")}
      type="GLB"
      position={[0, 0, -1]}
      onClick={() => {
        sceneNavigator.replace({scene: SceneTwo});
      }}
    />
  </ViroARScene>;
};
const SceneTwo = ({sceneNavigator}) => {
  return <ViroARScene>
    <ViroAmbientLight color={"#aaaaaa"}/>
    <Viro3DObject
      source={require("./res/heavy1.glb")}
      type="GLB"
      position={[0, 0, -2]}
    />
    <Viro3DObject
      source={require("./res/clickable1.glb")}
      type="GLB"
      position={[0, 0, -1]}
      onClick={() => {
        sceneNavigator.replace({scene: SceneOne});
      }}
    />
  </ViroARScene>;
};

const Navigator = () => {
  return <View style={{flex: 1}}><ViroARSceneNavigator
    initialScene={{scene: SceneOne}}
    apiKey={"SOME_API_KEY"}/>
  </View>;
};

AppRegistry.registerComponent('virobugs', () => Navigator);

res.zip
debugLogcat.log
debugErrorOnlyLogcat.log

we have the same problem with galaxy tab S5e

I could reproduce the crash with a 7Mo asset. After ~40 loading the app crash.

7MoAsset.zip

I can avoid crash if unmount then remount ViroARSceneNavigator. But you lost your origin and the transition is not as smooth as the ViroARSceneNavigator navigation functions.
import {AppRegistry, View} from 'react-native';
import {Viro3DObject, ViroAmbientLight, ViroARScene, ViroARSceneNavigator} from "react-viro";
import React, {useState} from "react";

const SceneOne = (props) => {
  return <ViroARScene>
    <ViroAmbientLight color={"#aaaaaa"}/>
    <Viro3DObject
      source={require("./res/heavy1.glb")}
      type="GLB"
      position={[0, 0, -2]}
    />
    <Viro3DObject
      source={require("./res/clickable1.glb")}
      type="GLB"
      position={[0, 0, -1]}
      onClick={() => {
        props.navToScene(SceneTwo);
      }}
    />
  </ViroARScene>;
}

const SceneTwo = (props) => {
  return <ViroARScene>
    <ViroAmbientLight color={"#aaaaaa"}/>
    <Viro3DObject
      source={require("./res/heavy0.glb")}
      type="GLB"
      position={[0, 0, -2]}
    />
    <Viro3DObject
      source={require("./res/clickable0.glb")}
      type="GLB"
      position={[0, 0, -1]}
      onClick={() => {
        props.navToScene(SceneOne);
      }}
    />
  </ViroARScene>;
}

const Navigator = () => {
  const [scene, setScene] = useState({current:SceneOne});
  const navToScene = (newScene) => {
    setScene(null);
    const clear = setTimeout(() => {
      setScene({current:newScene});
      clearTimeout(clear);
    }, 1);
  }
  if (!scene)
    return null;
  return <View style={{flex: 1}}>
    <ViroARSceneNavigator
      initialScene={{
        scene:scene.current, passProps: {navToScene}
      }}
      apiKey={"SOME_API_KEY"}/>
  </View>;
};

AppRegistry.registerComponent('virobugs', () => Navigator);

Good news! I'm trying with createBottomTabNavigator and react-navigation. In TabNavigator, I'm set unmountOnBlur: true, crash is gone. Hope this help! :)


Is working on IOS 8.0?

What is minimum deployment target?

Hello!
The minimum deployment target is 10.0.


Added torrent.on events to documentation

Added the other torrent.on events to the documentation.

Thanks! This is a good start. I will add some more information after merge :)

Changes here: https://github.com/feross/webtorrent/commit/7a7c4a8b8c49f5c92b7c20ff439bc8614f7d607e


Version .4.0 does not work on linux

Describe the bug
Version .4.0 does not work on linux
To Reproduce
Steps to reproduce the behavior:

Download
Install
Try to open
See error

Expected behavior
To work as version 0.3.1 has.
Screenshots

Additional context
System:
Kernel: 4.15.0-20-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm Distro: Linux Mint 19 Tara

sudo apt install curl solves it


[Bug] Web HTML Renderer not scrolling on iPad on Demo App

Hi,
I noticed that in the HTML renderer on iPad that this won't scroll. It appears to work on my Android.
https://weblaze.dev/pluto_grid/build/web/#feature/row-lazy-pagination

Bounce, bad bot

Bounce,  bad bot


Revert "sync with google/fonts"

Reverts googlefonts/axisregistry#70

This didn't fix anything.  It simply resets this repository to the same set of merge conflicts that were present before we attempted to sync with upstream...


Is logger working as expected ?

What steps will reproduce the problem?
Create a console Controller :
namespace console\controllers;

use yii\console\Controller;
use yii\console\ExitCode;
use yii\helpers\Yii;

class TestController extends Controller
{
    public function actionIndex()
    {
        Yii::debug('test/index');
        try {
            $this->stdout("CLI is working\n");
            return ExitCode::OK;
        } catch (\Exception $e) {
            Yii::error($e->getMessage());
            throw $e;
        }
    }
}

create the logger config in console.php
    'logger' => [
        'targets' => [
            [
                '__class' => \yii\log\FileTarget::class,
            ],
        ],
    ],

run the CLI
./vendor/bin/yii test

What is the expected result?
I'm expecting a log file in the directory runtime/logs/
What do you get instead?
nothing is created because we have two problems :

the logger yii\log\Logger does not extend yii\base\Component
Because of that, the property _targets is not populated as expected. a property targets is created

the logger is never flushed at the end of the application lifecycle
It works only when there is an error which is handled by yii\base\ErrorHandler which perform the flush

if ($this->logger instanceof \yii\log\Logger) {
    $this->logger->flush(true);
}

Perhaps, this issue should be copied to yiisoft/yii-core for the flush part
Additional info

Q
A

Yii version
3.0@dev

PHP version
7.2.8

Operating system
Mac OS

done ;) I'm preparing another one for the part in core.


Fix mobile

Generally fix the mobile version of the game
The game in actually totally non-functional on mobile! Oops... 😨
When @Thenlie changed the input to separate boxes this broke the input for mobile devices since they do not have an external keyboard. When testing on dev tools it is not noticeable since you have a keyboard...

[ ] User can actually input answers on mobile
[ ] Letters below user input are clickable
[ ] Change letters below to QWERTY layout
[ ] Small styling tweaks are made to the forms and game
[ ] Site is debugged on a real mobile device, not dev tools

Branch created
git fetch origin
git checkout 60-refactor/mobile


CodebaseResourceDetailsView Page not found for scan_codebase pipeline results

Note that this is not an issue for the docker and rootfs pipelines.
Likely related to the codebase/ prefix in the resources path.

I have been working on this, and yes, it is due to the codebase/ prefix. The prefix codebase/ appears twice in the url (line 2).

@tdruez, I have been studying this bug for a while now and here are the possible solutions

In scanpipe.py, the results are stored in CodebaseResource model with path = resource_data.pop("path"). This path already contains codebase prefix in it. So one solution is to remove the prefix from here.
The other solution is to rewrite codebase_path property and remove codebase prefix from it.

Hi @AvishrantsSh thanks for your input on this one.

In scanpipe.py, the results are stored in CodebaseResource model with path = resource_data.pop("path"). This path already contains codebase prefix in it. So one solution is to remove the prefix from here.

Yes that would work, but we also need to remove the prefix in other places such as in create_discovered_packages as the codebase resource is retrieve in the db using the path.

The other solution is to rewrite codebase_path property and remove codebase prefix from it.

That would work as well, the problem with that approach is that we would keep storing the "codebase/" prefix for all codebase resource in the database to then clean it each time. It would be better to not store it in the first place.

Both of your solutions would work fine as workaround but a better approach would be to enhance the VirtualCodebase to offer an API that would return paths without the root. VirtualCodebase.walk(skip_root=True) is available to not include the root as a resource, but we should add a way to not include the root in all the returned paths.
I'll look at it with @pombredanne on the toolkit side.

@AvishrantsSh see the fix at https://github.com/nexB/scancode.io/commit/4d46a386efcebb43d3413b8142353d33d37ac67d


allow bot on zoom subdomains for enterprise accounts

Allow extension on zoom subdomains e.g. enterprise.zoom.us
Probably not the best way to do it because it also matches somethingzoom.us but here's a start at least.

Apparently zoom can sometimes use a subdomain even for a personal account even if you visit a zoom.us URL. Like usweb04.zoom.us or something. This change is also needed for that.

Interesting! I've seen the usweb04 type in the wild too but figured it was still a paid acct, just not paid enough to get their own name :)


ADA issue with textarea

Hi. I have a client who is VERY ADA compliant with their sites. Think insurance policies, etc.
There is an issue with the generated <textarea> element coming from the reCaptcha plugin. In the DOM, it's directly after the iframe and has an id of g-recaptcha-response. Simply, it's just missing a form label that corresponds with that specific textarea input field. Is this something that can be added with the next release? Or is there something I can do? Theoretically, I could add a static label from my end and call it a day but...then I'm not even sure what the statistics are on screen readers and Javascript or if it's disabled even.
Thoughts? Suggestions?

+1

+1

You might want to look at the v3 support in the most recent release. That uses a wholly invisible reCAPTCHA that just returns a confidence score for the request. This might alleviate some of your issues. Example hosted at https://recaptcha-demo.appspot.com/recaptcha-v3-request-scores.php

+1

Why is this closed? Current v3 does not address this issue, the textarea is still missing a form label. This can be easily fixed by adding aria-hidden: true

This is still an issue. Any plans to add the aria-hidden: true to the ?

This still seems like a rather simple fix. Rather than closing, I think just add a aria-hidden=true or a visibly hidden label with correct for attr.


Lack of Convert Chaining

Hello,
I'm loving the plugin so far, but it would be great if the plugin can preform multiple converts in the order of the converts.
I have the following converting rules:
# auto pair and convert
'<|' -> '<|>'
'(<|>)' -> '⟨|⟩'
'((<|>))' -> '⟪|⟫'
'---\n\n|' -> '---\n|\n---'

# Selection Insert Rules
'<'  -> '<' + '>'

# Brackets
'((<|' -> '⟪|'
'>|))' -> '⟫|'
'(<|' -> '⟨|'
'>|)' -> '⟩|'
'[(<|' -> '⦗|'
'>|)]' -> '⦘|'
'[⟨|' -> '⦗|'
'⟩]|' -> '⦘|'

However, when I press the keys ( <,
it results in (<|>) (| represents the cursor)
which is not ideal since I have other rules (['(<|' -> '⟨|'] & ['(<|>)' -> '⟨|⟩'])
that should convert these into angled brackets.
I'm not sure how to optimize it on the performance side, but if you could still continue to loop through the list after something is converted, that would make the plugin even more versatile.
For example, when I press the keys ( <:

['<|' -> '<|>'] will trigger along with the default bracket auto pair, turning it into (<|>)
Then, the plugin will loop through all the rules after the one that has triggered, so anything after '<|' -> '<|>'
['(<|>)' -> '⟨|⟩' ], which happens to match, will further convert the text into '⟨|⟩'

Please consider adding this feature as it will make the plugin a lot more powerful.

I am not sure if this is related, but if you use characters (only tested * and _) that Obsidian auto pairs by default, the conversion doesn't work.
These are the relevant rules:
'<|' -> '<|>'
'<_|>' -> '|'
'<_|_>' -> '|'
'<*|>' -> '|'
'<*|*>' -> '|'

When I press < + _ or < + *, none of the rules except for the first one triggers.

I am not sure if this is related, but if you use characters (only tested * and _) that Obsidian auto pairs by default, the conversion doesn't work. These are the relevant rules:

Indeed, * and _ will trigger the default auto pair rules of Obsidian, and its priority is so high that the plugin can't change. When you type _， for the plugin, the input will be __ instead of _， which can't be recognized.
I guess there are two solutions.

Disable the default auto pair in Obsidian Editor settings and let the plugin take control

Use special trigger char to bypass, for example

'<s-|>' -> '|'
'<|' -> '<|>'

Convert chain is an appealing idea, but how to implement it might not be trivial, I will think about it anyway.
For now, for your cases, I would probably disable the default auto pair in Obsidian and write rules like this:
'((<|))' -> '⟪|'
'⟪>|' -> '⟪|⟫'

'(<|)' -> '⟨|'
'⟨>|' -> '⟨|⟩'

'([|)' -> '⦗|'
'⦗]|' -> '⦗|⦘'

# disable auto pair brackets and let the plugin take over
'(|' -> '(|)'
'[|' -> '[|]'

the process to write  '⟪|⟫':

type two (, the rule '(|' -> '(|)' will turn it into ((|))
type <, the rule '((<|))' -> '⟪|' will turn it into  '⟪|'
type >, the rule '⟪>|' -> '⟪|⟫' will turn it into '⟪|⟫

That is what you are looking for?


tests/kernel/mem_protect/obj_validation fails build on some boards after recent changes

After https://github.com/zephyrproject-rtos/zephyr/pull/25641 : for boards mps2_an385, frdm_k64f, etc.:
01:39:38.262 /home/buildslave/workspace/zephyr-upstream/zephyr/tests/kernel/mem_protect/obj_validation/src/main.c: In function 'dyn_object_release':
01:39:38.262 /home/buildslave/workspace/zephyr-upstream/zephyr/tests/kernel/mem_protect/obj_validation/src/main.c:173:30: error: the comparison will always evaluate as 'true' for the address of 'test_dyn_mutex' will never be NULL [-Werror=address]
01:39:38.262   173 |  zassert_not_null(&test_dyn_mutex, "Can't allocate dynamical kobj");
01:39:38.262       |                              ^~
01:39:38.262 cc1: all warnings being treated as errors

Full sanitycheck build log: https://ci.linaro.org/view/lite-iot-ci/job/zephyr-upstream/5651/PLATFORM=mps2_an385,ZEPHYR_TOOLCHAIN_VARIANT=zephyr,label=docker-xenial-amd64-13/console

@pfalcon  which toolchain are you using?

ok, i see above you are using zephyr sdk. Not able to reproduce this locally and in Zephyr's CI, wonder why this warning is active in your environment.
This is still an issue that needs to be fixed, @maksimmasalski  you are checking the address, not the pointer.

The full picture can be seen here: https://ci.linaro.org/view/lite-iot-ci/job/zephyr-upstream/5650/ . The compile warning-as-error happens synchronously for both Zephyr SDK 0.11.4 and gnuarmemb gcc-arm-none-eabi-9-2019-q4-major-x86_64-linux.tar.bz2.
But it happens for disco_l475_iot1, frdm_k64f, mps2_an385, nucleo_f401re, and doesn't happen for cc3220sf_launchxl, frdm_kw41z, nucleo_f103rb, qemu_cortex_m3.
I have to admit I didn't try to reproduce locally - I usually do, but last couple of times I figure we were duplicating effort with a few other folks, so I decided to shoot a ticket first.
I'd also guess it's more or less clear there's a typo, in zassert_not_null(&test_dyn_mutex, "Can't allocate dynamical kobj"); , the & looks stray (unless there's a bigger logic error in context).


Easily exclude specific columns

I have started using this package, and I think a useful addition would be a way to exclude specific columns.
There are often a few columns that aren't particularly useful to keep track of. Perhaps something along these lines:
use Motomedialab\SimpleLaravelAudit\Traits\AuditableModel;

class User extends Model
{
    use AuditableModel;

    public function excludeFromAudit(): array
    {
        return [
            'created_at',
            'updated_at',
            'last_login_at',
            'remember_token',
        ];
    }
}

Just an idea thrown out there, let me know what you think! :)

Hey Lewis,
Completely agree on this - it's not worth logging out information that isn't particularly relevant or will be duplicated.
I'm away this week and limited internet but feel free to PR and we can collab on that - but the above looks good.
Thanks!

#6 closes this.

Thanks for the PR @lewislarsen. Merged and tagged as v1.3.0 👍


adding episode 27

this is mostly a placeholder while we hash out what we wanna do re: audio compression/resampling

this is mostly a placeholder while we hash out what we wanna do re: audio compression/resampling

Interesting question about file size. The current version is ~150 kbit/s, and we could drop it to 96 or 128 pretty happily.
That said, my vote is to ship this one :shipit:, and encode the next one differently. 30Mb isn't perfect, but I don't think it should block us. If we want to re-encode historical episodes we can shrink this one while we're going through the back-catalogue, ready for hockey-stick growth and things going viral 😜

Interesting question about file size. The current version is ~150 kbit/s, and we could drop it to 96 or 128 pretty happily.
That said, my vote is to ship this one :shipit:, and encode the next one differently. 30Mb isn't perfect, but I don't think it should block us. If we want to re-encode historical episodes we can shrink this one while we're going through the back-catalogue, ready for hockey-stick growth and things going viral 😜

…wait  … …who's supposed to merge this?
I feel like there's an answer in the podcast episode, but it's not been published so I can't check.

…wait  … …who's supposed to merge this?
I feel like there's an answer in the podcast episode, but it's not been published so I can't check.

MERGED!!!

MERGED!!!

Is anybody else hyped to listen to the latest episode???

Is anybody else hyped to listen to the latest episode???

We have a fan! Pressure is ON!!!

We have a fan! Pressure is ON!!!


Fix #2689: Do not propagate tailPosLabels inside finally block.

Inside a finally block, we lose the property that we are in tail position of any label. This is because the code of the finally block is implicitly followed by some test to re-throw a caught exception or further return a returned value.

Review by @gzm0. I have manually tested that this fixes run/t10032.scala in 2.12.1.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3566/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4696/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3568/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/4698/
Test PASSed.


Added JUnit tests to Schedule

TODO: REDO/UNDO tests

Pull Request Test Coverage Report for Build 382

8 of 8 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.9%) to 75.885%

Totals

Change from base Build 371:
1.9%

Covered Lines:
2464

Relevant Lines:
3247

💛  - Coveralls


docs(): improve migration docs

Changed

improved wording of upgrade instructions

:rocket: Welcome to Baloise ChatOps based GitOps Bot :tada:
- If you want to enable preview environments for this PullRequest, comment with `/preview`.
- If you want to disable the preview environment for this PR, comment with `/undeploy`.
- If you need help or want to see the docs, comment with `/help`.

Make sure to refresh this page after submitting a command.
Preview environments can be redeployed automatically if you enable the webhook for updates to the source branch. :new:

Have fun building awesome apps! :hammer:  :whale2:  :truck:  :ship:


Keywordprg returns not-found

I have tried using DevdocsKeywordprg module and have set in my options via vim.opt.keywordprg=":DevdocsKeywordprg". It correctly calls it but it never finds documentation even though I have tested on function such as useState, which entry definitely exists in React docs. Can be verified by opening Devdocs and searching for it. Calling it as a command i.e. DevdocsKeywordprg useState does not return results either.
Furthermore, I am sure LSP is not overwriting it because I get notified by devdocs and my mapping for calling it is:
map("n", "<leader>K", "<cmd>norm! K<cr>", { desc = "Keywordprg" })

Steps to reproduce:

Set keywordprg to ":DevdocsKeywordprg"
Go to any textobject which should have documentation for it
Execute `:DevdocsKeywordprg" on it
ERROR [nvim-devdocs] No documentation found for <textobject>

If you've tried using it in actual code then it's not yet implemented, see #61.
But it should work in the docs preview and you don't have to set the mappings yourself, it will replace K by default.

Thank you for answer @luckasRanarison I saw the issue #61 but I though the limitation is that LSPHover is overriding it. With different keymap this doesn't seem to be a problem. But I guess issue is somewhere else as well. I am closing the issue.

The tricky part of that is the re-implementation of the K key functionalities.


[Dev Home]Dev Home does not seem to make use of NavigationView's back button, making navigation around the app inconsistent

Dev Home version
No response
Windows build number
No response
Other software
No response
Steps to reproduce the bug
Description
Contrast with other navigation views in Windows, like Settings. When you navigate into an area, you get a back button in the top left that replaces the hamburger button and can be used to get back to where you are.
If I go into Machine Configuration -> Clone repositories, I have to click "Cancel" to get back to where I was. There is no back stack being used.
Expected result
No response
Actual result
No response
Included System Information
No response
Included Extensions Information
No response

Some of the work is already done for this, however some of the pages use an "inner" navigation, i.e. within a page you have multiple steps. Those steps sometimes do not happen in the root frame but rather an inner frame that might also needs to be taken into account.
This behavior can be currently also observed by navigating deeper into the "Machine configuration" page and then switching between any other navigation entry and the "Machine configuration" entry; the state of the "Machine configuration" tab is restored. If this behavior is not a blocking issue for the back button, I would gladly create a PR for this.

@krschau @EricJohnson327
Here is the Figma guidance for Global Back button

Bug 44310341: [Dev Home]Dev Home does not seem to make use of NavigationView's back button, making navigation around the app inconsistent


User Interface

Need a user interface. Command line interface would be fine.

Hello, mwhit74. I have tried to implement something that I think might be useful. See: pull request.

Sorry just getting back to you. I pulled your code the other day and it is a big help. I tweaked the style, not your fault I don't have a style guide recommendation published, and fixed a small typo. I also integrated it directly with the rest of the code. It works very well.
Thanks for your help. :)


Collaborators without Git LFS produce errors when merging upstream changes

According to https://help.github.com/articles/collaboration-with-git-large-file-storage/, it seems that collaborators should be able to contribute without forcing install of Git LFS, but they just won't have access to the large files- only the pointer files.
This is fine for my purpose- I want to be able to let contributors generate the large files and PR them back into the original repo, and they don't need the actual files that have already been generated, the pointer files suffice. I'd actually prefer to periodically move the new large files over to Git LFS, so that I can check certain aspects of the file as it's being PR'ed.
However, when attempting to merge upstream changes without Git LFS, collaborators without Git LFS receive git: 'lfs' is not a git command. See 'git --help'.
Is there a best practice for dealing with forks and PRs when it comes to Git LFS?

That command is likely coming from some git config left over from uninstalling Git LFS. If you've never installed it, Git will be completely oblivious about LFS.

Clear any filter.lfs config settings.

$ git config --global --unset "filter.lfs.clean"
$ git config --global --unset "filter.lfs.smudge"
$ git config --global --unset "filter.lfs.required"

2. Remove any LFS pre-push hooks:

        $ rm .git/hooks/pre-push

> Is there a best practice for dealing with forks and PRs when it comes to Git LFS?

Every user and collaborator should be using Git LFS to be effective. You won't be able to make PRs changing LFS content without it.

Hi again!
So, there's very little chance that Git LFS was installed on the machine previously. If it helps, the collaborator was using Mac OSX- so maybe this should just be documentation of a possible issue for the future. If this crops up again, I'll try those commands and see if the issue continues.
As for the all users having Git LFS- my particular use case (distributing work units) doesn't require that :-)
Anyway, I guess this issue can be closed for now, and I'll just ask for it to be reopened if I can reproduce the issue reliably.

BTW If you install Git LFS and want to remove it, running "git lfs uninit" will remove those config settings too.


invalid byte sequence in UTF-8: upload_to_testflight can't process ipa files larger than 4GB

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

Recently I got this invalid byte sequence in UTF-8 error when uploading my ipa file to testflight. When I traced down the error and examine the output from unzip -Z -1 I found there's some file name containing characters like ö or å.
These files have been in the app for quite a long time, and before they can be processed without any problems. I noticed that the last successful build was much smaller (about 2.3G) while now the ipa has grown massively into 6G. Could this be the problem?
Command executed

bundle exec fastlane send_to_testflight "scheme:com.test.app" --verbose
Complete output when running fastlane, including the stack trace and command used

[✔] 🚀
DEBUG [2021-12-10 15:13:29.33]: Checking if there are any plugins that should be loaded...
Successfully loaded Appfile at path '/path/to/Appfile'
- apple_id<EMAIL_ADDRESS>-------
DEBUG [2021-12-10 15:13:29.56]: Using scheme: com.test.app
INFO [2021-12-10 15:13:29.57]: ---------------------------
INFO [2021-12-10 15:13:29.57]: --- Step: opt_out_usage ---
INFO [2021-12-10 15:13:29.57]: ---------------------------
INFO [2021-12-10 15:13:29.57]: Disabled upload of used actions
INFO [2021-12-10 15:13:29.57]: ------------------------------
INFO [2021-12-10 15:13:29.57]: --- Step: default_platform ---
INFO [2021-12-10 15:13:29.57]: ------------------------------
INFO [2021-12-10 15:13:29.57]: Driving the lane 'ios send_to_testflight' 🚀
INFO [2021-12-10 15:13:29.58]: -----------------------------
INFO [2021-12-10 15:13:29.58]: --- Step: setup_circle_ci ---
INFO [2021-12-10 15:13:29.58]: -----------------------------
INFO [2021-12-10 15:13:29.58]: Not running on CI, skipping CI setup
INFO [2021-12-10 15:13:29.58]: ---------------------------------------
INFO [2021-12-10 15:13:29.58]: --- Step: app_store_connect_api_key ---
INFO [2021-12-10 15:13:29.58]: ---------------------------------------
INFO [2021-12-10 15:13:29.62]: ----------------------------------
INFO [2021-12-10 15:13:29.62]: --- Step: upload_to_testflight ---
INFO [2021-12-10 15:13:29.62]: ----------------------------------
INFO [2021-12-10 15:13:29.62]: Creating authorization token for App Store Connect API
DEBUG [2021-12-10 15:13:29.63]: App identifier (com.test.app)
INFO [2021-12-10 15:13:34.63]: Ready to upload new build to TestFlight (App: xxxxxxxx)...
INFO [2021-12-10 15:13:34.73]: ▸ warning [/Users/shifei.chen/Repo/ios-app/artifacts/com.test.app.ipa]:<PHONE_NUMBER> extra bytes at beginning or within zipfile
INFO [2021-12-10 15:13:34.73]: ▸   (attempting to process anyway)
WARN [2021-12-10 15:13:34.73]: Lane Context:
INFO [2021-12-10 15:13:34.73]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios send_to_testflight"}
ERROR [2021-12-10 15:13:34.73]: invalid byte sequence in UTF-8
INFO [2021-12-10 15:13:34.75]: Successfully generated documentation at path '/Users/shifei.chen/Repo/ios-app/fastlane/README.md'
+------+---------------------------+-------------+
|                fastlane summary                |
+------+---------------------------+-------------+
| Step | Action                    | Time (in s) |
+------+---------------------------+-------------+
| 1    | opt_out_usage             | 0           |
| 2    | default_platform          | 0           |
| 3    | setup_circle_ci           | 0           |
| 4    | app_store_connect_api_key | 0           |
| 💥   | upload_to_testflight      | 5           |
+------+---------------------------+-------------+
ERROR [2021-12-10 15:13:34.76]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Search query: invalid byte sequence in UTF-8
URL: https://api.github.com/search/issues?q=invalid byte sequence in UTF-8+repo:fastlane/fastlane
➡  Any fastlane command: `gsub': invalid byte sequence in UTF-8 (ArgumentError)
https://github.com/fastlane/fastlane/issues/18723 [closed] 6 💬
a week ago
➡  [pilot] The resource 'betaAppReviewSubmissions' does not allow 'DELETE'
https://github.com/fastlane/fastlane/issues/18408 [open] 22 💬
12 hours ago
➡  windows  bale erro
https://github.com/fastlane/fastlane/issues/18755 [closed] 4 💬
28 Jul 2021
and 46 more at: https://github.com/fastlane/fastlane/search?q=invalid byte sequence in UTF-8&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
bundler: failed to load command: fastlane (/usr/local/lib/ruby/gems/2.7.0/bin/fastlane)
Traceback (most recent call last):
47: from /usr/local/opt/ruby@2.7/bin/bundle:23:in <main>' 	46: from /usr/local/opt/ruby@2.7/bin/bundle:23:in load'
45: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.2.22/exe/bundle:37:in <top (required)>' 	44: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/friendly_errors.rb:128:in with_friendly_errors'
43: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.2.22/exe/bundle:49:in block in <top (required)>' 	42: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli.rb:24:in start'
41: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/base.rb:485:in start' 	40: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli.rb:30:in dispatch'
39: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor.rb:392:in dispatch' 	38: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command'
37: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/command.rb:27:in run' 	36: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli.rb:474:in exec'
35: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli/exec.rb:28:in run' 	34: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in kernel_load'
33: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in load' 	32: from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in <top (required)>'
31: from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in load' 	30: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/bin/fastlane:23:in <top (required)>'
29: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off' 	28: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/commands_generator.rb:42:in start'
27: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/commands_generator.rb:353:in run' 	26: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
25: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:117:in run!' 	24: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
23: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 	22: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
21: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/commands_generator.rb:109:in block (2 levels) in run' 	20: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
19: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane' 	18: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:45:in execute'
17: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:45:in chdir' 	16: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:49:in block in execute'
15: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/lane.rb:33:in call' 	14: from Fastfile:228:in block (2 levels) in parsing_binding'
13: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/fast_file.rb:159:in method_missing' 	12: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
11: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:229:in execute_action' 	10: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:229:in chdir'
9: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:255:in block in execute_action' 	 8: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
7: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action' 	 6: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/actions/upload_to_testflight.rb:34:in run'
5: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/pilot/lib/pilot/build_manager.rb:27:in upload' 	 4: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/pilot/lib/pilot/manager.rb:85:in fetch_app_platform'
3: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:32:in fetch_app_platform' 	 2: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:45:in fetch_info_plist_file'
1: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:79:in fetch_info_plist_with_unzip' /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:79:in split': invalid byte sequence in UTF-8 (ArgumentError)
47: from /usr/local/opt/ruby@2.7/bin/bundle:23:in <main>' 	46: from /usr/local/opt/ruby@2.7/bin/bundle:23:in load'
45: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.2.22/exe/bundle:37:in <top (required)>' 	44: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/friendly_errors.rb:128:in with_friendly_errors'
43: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/gems/2.7.0/gems/bundler-2.2.22/exe/bundle:49:in block in <top (required)>' 	42: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli.rb:24:in start'
41: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/base.rb:485:in start' 	40: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli.rb:30:in dispatch'
39: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor.rb:392:in dispatch' 	38: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command'
37: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/vendor/thor/lib/thor/command.rb:27:in run' 	36: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli.rb:474:in exec'
35: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli/exec.rb:28:in run' 	34: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in kernel_load'
33: from /usr/local/Cellar/ruby@2.7/2.7.5/lib/ruby/2.7.0/bundler/cli/exec.rb:63:in load' 	32: from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in <top (required)>'
31: from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in load' 	30: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/bin/fastlane:23:in <top (required)>'
29: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off' 	28: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/commands_generator.rb:42:in start'
27: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/commands_generator.rb:353:in run' 	26: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
25: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:117:in run!' 	24: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
23: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 	22: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
21: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/commands_generator.rb:109:in block (2 levels) in run' 	20: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
19: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane' 	18: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:45:in execute'
17: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:45:in chdir' 	16: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:49:in block in execute'
15: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/lane.rb:33:in call' 	14: from Fastfile:228:in block (2 levels) in parsing_binding'
13: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/fast_file.rb:159:in method_missing' 	12: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
11: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:229:in execute_action' 	10: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:229:in chdir'
9: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:255:in block in execute_action' 	 8: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
7: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action' 	 6: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane/lib/fastlane/actions/upload_to_testflight.rb:34:in run'
5: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/pilot/lib/pilot/build_manager.rb:27:in upload' 	 4: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/pilot/lib/pilot/manager.rb:85:in fetch_app_platform'
3: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:32:in fetch_app_platform' 	 2: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:45:in fetch_info_plist_file'
1: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:79:in fetch_info_plist_with_unzip' /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.198.1/fastlane_core/lib/fastlane_core/ipa_file_analyser.rb:79:in split': \e[31m[!] invalid byte sequence in UTF-8\e[0m (ArgumentError)

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
11.6

Ruby
2.7.5

Bundler?
true

Git
git version 2.34.1

Installation Source
/usr/local/lib/ruby/gems/2.7.0/bin/fastlane

Host
macOS 11.6 (20G165)

Ruby Lib Dir
<EMAIL_ADDRESS>

OpenSSL Version
OpenSSL 1.1.1l  24 Aug 2021

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
13.1

Swift Version
5.5.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
opt_out_usage
default_platform(:ios)

CERT_REPO                     = "git@github.com:company/some-repo-holding-certificates"
TEAM_ID              = "some team id"
TESTFLIGHT_TEAM_ID   = "some team id 2"
ASC_API_ISSUER_ID    = "some issuer id"
ASC_API_KEY_ID       = "some key id"
WORKSPACE_DIR                 = "./ios-app.xcworkspace"
ARTIFACTS_DIR                 = "./artifacts"
DESTINATION                   = "generic/platform=iOS"

platform :ios do
  before_all do
    setup_circle_ci
  end

  desc "TestFlight Distribution"
  lane :send_to_testflight do |values|
    # Arguments
    scheme                = values[:scheme]

    # Variables
    is_dev =              scheme.start_with?("dev.")
    ipa_file              = "#{ARTIFACTS_DIR}/#{scheme}.ipa"
    testflight_team_id    = TESTFLIGHT_TEAM_ID

    # Prepare App Store Connect API Key
    app_store_connect_api_key(
      key_id: ASC_API_KEY_ID,
      issuer_id: ASC_API_ISSUER_ID,
      key_content: "#{ENV["ASC_API_KEY"]}",
      # Use base64 encoded cert content to avoid newline character issues
      # See https://github.com/fastlane/fastlane/issues/17340
      is_key_content_base64: true
    )

    # Distribute to TestFlight
    if (!is_dev) then
      upload_to_testflight(
        app_identifier:                     scheme,
        ipa:                                ipa_file,
        team_id:                            testflight_team_id,
        skip_waiting_for_build_processing:  true,
        beta_app_feedback_email<EMAIL_ADDRESS>        beta_app_description: "iOS app",
        demo_account_required: true,
        distribute_external: true,
        notify_external_testers: false,
        beta_app_review_info: {
          contact_email<EMAIL_ADDRESS>          contact_first_name: "Foo",
          contact_last_name: "Bar,
          contact_phone: "+123445789",
          demo_account_name<EMAIL_ADDRESS>          demo_account_password: "password",
          notes: "some notes"
        },
        localized_app_info: {
          "default": {
            feedback_email<EMAIL_ADDRESS>            marketing_url: "https://www.company.com",
            privacy_policy_url: "https://www.company.com",
            description: "iOS app",
          }
        },
        localized_build_info: {
          "default": {
            whats_new: "We improved the app increasing the stability and fixing bugs.",
          }
        }
      )
    end
  end

`./fastlane/Appfile`
<EMAIL_ADDRESS># Your Apple email address

fastlane gems

Gem
Version
Update-Status

fastlane
2.198.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.4.0

bundler
2.2.22

uri
0.10.0

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.5

public_suffix
4.0.6

addressable
2.8.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.540.0

aws-sigv4
1.4.0

jmespath
1.4.0

aws-sdk-core
3.124.0

aws-sdk-kms
1.52.0

aws-sdk-s3
1.109.0

babosa
1.0.4

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.4

unf_ext
0.0.8

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.3

excon
0.89.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

multipart-post
2.0.0

ruby2_keywords
0.0.5

faraday
1.8.0

http-cookie
1.0.4

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.5

gh_inspector
1.1.3

jwt
2.3.0

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.16.0

googleauth
1.1.0

httpclient
2.8.3

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.1.1

retriable
3.1.2

webrick
1.7.0

google-apis-core
0.4.1

google-apis-androidpublisher_v3
0.14.0

google-apis-playcustomapp_v1
0.6.0

google-apis-iamcredentials_v1
0.8.0

google-apis-storage_v1
0.10.0

google-cloud-env
1.5.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-cloud-storage
1.35.0

json
2.6.1

mini_magick
4.11.0

naturally
2.2.1

optparse
0.1.1

plist
3.6.0

rubyzip
2.3.2

security
0.1.3

simctl
1.6.8

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.21.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2021-12-10

I believe this issue is connected to the PR #17825 which introduced unzip. However it seems like unzip has problems with encodes other than UTF-8, see discussions about this here
So perhaps you have to choose between these two things: either only use UTF-8 characters in your file names while making massive IPAs, or pick whatever file names but keep the final IPA small.

Closed since the PR is merged in version 2.200.0.


Improve demo bundling

We can minimize the bundling config, and also push (most) of the jspm_packages directory to the gh-pages branch. Hopefully it will reduce the amount of errors you can get during bundling

Perhaps it might make sense to present the issues we have in the context of updating the demo-kendo from the embedded sample app to Guy; I would guess that our development setup would be encountered at many places.

This comment is not visible enough IMO. If we publish (a large part) of jspm_packages, then files we forget to bundle are still served.

Ideally we do just want to have jspm_packages served in production though as it is also useful for dynamic loading scenarios.

Can you please explain this?

Sure.
So by bundling we mean concatenating (and minifying) all files in the jspm_packages folder, into a single file (lets say app-bundle.js). Instead of the browser having to fetch every file in the jspm_packages folder (in hundreds of different requests), the browser just has to download one file: app-bundle.js. This means that (if all works well) you don't have to include the jspm_packages folder when deploying, you just need to deploy the app-bundle.js.
Bundling is done by JSPM, but you have to tell JSPM which files to include in the bundle. It does some magic by looking up all files used by your application, but it misses a lot. That's why we have the bundles.json file.
But what happens if we forget to include a file in this bundle configuration? Then the file won't be included in the app-bundle.js. As we (at the moment) don't have the jspm_packages folder in our gh-pages branch, it won't be able to download the missing file from there either. So, we get a 404.
It may be better to do this the other way around. We copy the entire jspm_packages folder, but exclude the files/folders we have included in the bundle configuration, and are thus in the bundle. This could reduce the amount of issues we have, as I stated in the paragraph above, because if we forget to bundle a file, JSPM can always get it from the jspm_packages folder.

So, I eventually got it working, but reverted this a few minutes ago. The jspm_packages folder contains 4500 files and is about 50MB, so you don't really want to push that to Github for every minor change. So, I excluded some folders, which brought the number of files down significantly, but increased the complexity of the bundling config. I don't think we can deal with this complexity, as it's hard enough to get the normal skeleton bundled, let alone a heavily customized bundle config, so I reverted the change.
I have improved the bundle config however, by removing all references to versions. So if we update dependences, we won't have to update the bundle config, or fix 404's if we forget ;)


Added more supported search query types in MedplumClient

Coverage: 93.895%. Remained the same when pulling e9f355bb8588bca8198f48f74728e64574e0e80f on cody-more-search-query-types into a73061e0b4044c5a23c204897d39b29b8fd17bf6 on main.


Hacking friday

[x] Make correct format for addresses from extension

[ ] Get blockNumber from transaction

[ ] Research why balance too low occurs (polkadot chain was default)

[ ] Check fiat on-ramp

[ ] formatic is now magic 🤣


fix(GHSA-64g7-mvw6-v9qj): upgraded shelljs

Encountered cascading issues including a weird checksum mismatch on a typescript patch.

Tried deleting yarn.lock and reinstalling in vain.
Ended up upgrading both yarn and typescript to the next minor version and it worked...


Python sup regression

New Branch for the Supervised regression exercise sheet in Python

Exercise .Rnw and .pdf for Python
Exercise .Rnw and .pdf for R and Python (unspecific phrasing)
Solution .ipynb Jupiter Notebook
I2ML_env.yml in supervised-regression folder to prevent merge conflicts (cleaned requirement list)

 Python Exercise 2: Regression I2ML


Rule ID missing from Modsecurity Audit logs

Hello All,
we have a setup of ModSecurity + Modsecurity-Nginx from master. we are using JSON format for modsecurity Auditlog. logs contain messages section that contain information about the rules that triggered it.
like below example .
{"message":" Inbound Points Exceeded|Total Incoming Points: 5|example.com|F|2","details":{"match":"Matched \"Operator Ge' with parameter 5' against variable TX:INCOMING_POINTS' (Value: 5' )","reference":"","ruleId":"214930","file":"/etc/nginx/modsec/waf/20_Outgoing_FiltersEnd.conf","lineNumber":"32","data":"","severity":"2","ver":"","rev":"1","tags":["WAF","FiltersEnd"],"maturity":"0","accuracy":"0"}}]}}
But every now and then we are seeing empty messages section in Audit logs this is making it harder to track which rule is blocking the requests. like below example here messages section is empty [].
{"transaction":{"client_ip":"xx.xx.xx.xx","time_stamp":"Tue Jul  7 14:15:51 2020","server_id":"474b1dfa0a32e45055d8b70069a09292af72bbe6","client_port":0,"host_ip":"xx.xx.xx.xx","host_port":443,"unique_id":"159413135176.639672","request":{"method":"POST","http_version":1.1,"uri":"/xmlrpc.php","headers":{"User-Agent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0","X-Forwarded-Proto":"https","CF-Visitor":"{\"scheme\":\"https\"}","Content-Length":"475","X-Forwarded-For":"xx.xx.xx.xx","CF-IPCountry":"DE","Host":"example.com","Accept-Encoding":"gzip","Connection":"Keep-Alive","CDN-Loop":"cloudflare","CF-RAY":"5af22e0fea0fbf69-SIN","Content-Type":"application/x-www-form-urlencoded","CF-Request-ID":"03cb3b1df20000bf69d5851200000001","CF-Connecting-IP":"xx.xx.xx.xx"}},"response":{"http_code":403},"producer":{"modsecurity":"ModSecurity v3.0.4 (Linux)","connector":"ModSecurity-nginx v1.0.1","secrules_engine":"Enabled","components":["WAF_Apache\""]},"messages":[]}}
Also SecDefaultAction is set to have auditlog
SecDefaultAction \
        "phase:1,deny,log,auditlog"

SecDefaultAction \
        "phase:2,deny,status:403,log,auditlog"

Also any rule does not conatin "noauditlog" in the rules action part. can someone point why rule id are missing from logs or what can be missing
Thanks

Hi @rahulbhatu,
Thanks for the report. It could be a regression on libModSec v3/master. As a workaround can you use v3.0.4?
Formatted JSON for easy readability -
{
   "message":" Inbound Points Exceeded|Total Incoming Points: 5|example.com|F|2",
   "details":{
      "match":"Matched \"Operator Ge' with parameter 5' against variable TX:INCOMING_POINTS' (Value: 5' )",
      "reference":"",
      "ruleId":"214930",
      "file":"/etc/nginx/modsec/waf/20_Outgoing_FiltersEnd.conf",
      "lineNumber":"32",
      "data":"",
      "severity":"2",
      "ver":"",
      "rev":"1",
      "tags":[
         "WAF",
         "FiltersEnd"
      ],
      "maturity":"0",
      "accuracy":"0"
   }
}

{
   "transaction":{
      "client_ip":"xx.xx.xx.xx",
      "time_stamp":"Tue Jul 7 14:15:51 2020",
      "server_id":"474b1dfa0a32e45055d8b70069a09292af72bbe6",
      "client_port":0,
      "host_ip":"xx.xx.xx.xx",
      "host_port":443,
      "unique_id":"159413135176.639672",
      "request":{
         "method":"POST",
         "http_version":1.1,
         "uri":"/xmlrpc.php",
         "headers":{
            "User-Agent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0",
            "X-Forwarded-Proto":"https",
            "CF-Visitor":"{\"scheme\":\"https\"}",
            "Content-Length":"475",
            "X-Forwarded-For":"xx.xx.xx.xx",
            "CF-IPCountry":"DE",
            "Host":"example.com",
            "Accept-Encoding":"gzip",
            "Connection":"Keep-Alive",
            "CDN-Loop":"cloudflare",
            "CF-RAY":"5af22e0fea0fbf69-SIN",
            "Content-Type":"application/x-www-form-urlencoded",
            "CF-Request-ID":"03cb3b1df20000bf69d5851200000001",
            "CF-Connecting-IP":"xx.xx.xx.xx"
         }
      },
      "response":{
         "http_code":403
      },
      "producer":{
         "modsecurity":"ModSecurity v3.0.4 (Linux)",
         "connector":"ModSecurity-nginx v1.0.1",
         "secrules_engine":"Enabled",
         "components":[
            "WAF_Apache\""
         ]
      },
      "messages":[

      ]
   }
}

Hi @zimmerle
sorry for the confusion we are already using ModSecurity v3.0.4 and Modsecurity-Nginx v1.0.1.

Hi @zimmerle
Anything else I can check for the missing rule ID in the audit logs. I tried some tests but no luck yet.
Thanks
Rahul

Update --
I came across this threadhttps://github.com/SpiderLabs/ModSecurity/issues/1866 and based on @kanitan's comment i checked my modsecurity config file i had this in my config.
SecAuditEngine RelevantOnly SecAuditLogRelevantStatus "403"
After commenting #SecAuditLogRelevantStatus "403" in config file all the audit logs entries now contains Rule IDs
so now the problem is, if SecAuditLogRelevantStatus "403" was meant to record all the actions that produced 403 statuscode even if its not blocked by modsecurity and some other ways then i am performing some actions that gives me 403 statuscode but are not recorded in audit logs.

wat?????????????????


Add goreleaser to publish signed binaries

Hi team,
I just wanted to introduce goreleaser as it simplifies the publishing, distribution and signing of assets.
You can see an example here: https://github.com/anchore/grype/releases/tag/v0.73.1
The next step would be to provide a container with weaver in it as it could be used as a base image for container instead of a vanilla container like ubuntu
Happy to discuss this further as this PR probably won't work on the first try. Those things are a bit hard to get right without testing them first.
Let me know your thoughts.

Hi @veggiemonk, what benefits does gorelease offer in comparison to tagging and releasing manually with something like go tag -a v0.X.Y && git push origin v0.X.Y?

Hi @mwhittaker, it doesn't change the workflow of releasing with git tag -a v0.X.Y && git push origin v0.X.Y.
When a new tag is created (see https://github.com/veggiemonk/weaver/blob/ef19a2c09677f3c6e42e04e5e91918cd71cdbc42/.github/workflows/release.yml#L19-L21), it will automatically build and push signed binaries that will be available with the release on GitHub as shown here https://github.com/anchore/grype/releases/tag/v0.73.1 .
It is also possible to publish a homebrew tap (brew.sh, famous package manager on Mac) but this is not setup in this PR.
The next step would be to provide a container image with weaver in it. It can serve as a base image for application container and remove the need for compiling weaver in the container build step and allows for ko to build weaver applications without ever writing a Dockerfile, therefore reducing the number of steps to deploy.
I think GitHub provides some kind of metrics about the number of downloads if the container is hosted on ghcr.io (GitHub Container Registry). Maybe you want to host that on GCR/Artefacts Registry?
Goreleaser can use ko to build and deploy a Go application in a container. Therefore, the migration a project that already uses Goreleaser to include service weaver would be seamless.
ko produces checksums and SBOMs for applications. Supply chain security is something that needs to be setup at the beginning of a project. It is not impossible to add later but it could become a chore.
This has been my thinking so far. I think a full example would be useful to show the possibilities and the tradeoffs.


[DO NOT MERGE] authorization with autorestv3

Generated using this swagger

Can one of the admins verify this patch?


Webpack is complaining about not being able to stat the build directory

Any ideas on this? If I make the dir ahead of time, there's no issue, but I don't think I should have to?
ENOENT: no such file or directory, stat '/path/to/my/src/.build/91ab6e0cbf68bb050912bfa74de0d9c607e86930fc1685e4d90b08e21e445da9'

Same error here as well how do we fix this?

agree, I have the same error

@cranberyxl @sdkitono @alexanderkagadovsky I will work to fix this bug, but it will take some time.
please use<EMAIL_ADDRESS>

After digging into the problem I've a few issues:

webpack doesn't build a lambda - there is no .build directory
I've fixed this locally using two steps:

when initializing new WebpackFunction I set in props buildDir: '.build'
the webpack configuration is not altered correctly in https://github.com/masahirompp/aws-cdk-webpack-lambda-function/blob/master/lib/builder.ts#L30 . The code I have

    constructor(options) {
        const webpackConfig = require(options.config);
        webpackConfig.entry = options.entry;
        webpackConfig.output = {
            libraryTarget: "commonjs",
            path: options.output,
            hashFunction: "md4",
        };

        this.webpack = webpack(webpackConfig);
    }
``` (I've changed it in builder.js)
After these two steps it worked correctly and there was a `.build` directory in the root folder
* However there is another problem in https://github.com/masahirompp/aws-cdk-webpack-lambda-function/blob/master/lib/builder.ts#L41
the code I have:

build() {
    this.webpack.run((err, stats) => {
        if (stats.hasErrors()) {
            console.log(stats.toString());
        }
        console.log('does build exist: ', require('fs').existsSync(stats.outputOptions.path));

        if (err) {
            throw err;
        }
    });
}

`err` doesn't have errors and errors can be found in `stats` (use debugger to check the variable value because its fails when using console.log)

The most important problem that the callback inside `this.webpack.run` finishes **after** when this code is executed https://github.com/masahirompp/aws-cdk-webpack-lambda-function/blob/master/lib/function.ts#L69

export class WebpackSingletonFunction extends SingletonFunction {
constructor(
scope: Construct,
id: string,
props: WebpackSingletonFunctionProps
) {
const { runtime, handlerDir, outputBasename, handler } = preProcess(props);
super(scope, id, {
  ...props,
  runtime,
 **** code: Code.fromAsset(handlerDir),****
  handler: `${outputBasename}.${handler}`,
});

}
}

which results in that directory is not found. A seemingly logical solution might be to use a promise to wait till the build process is completed but this contradicts the CDK approach where everything is setup inside `constructor`.

@reni11111 I wasn't able to fix this error. I configured webpack with CDK without using this library.

@reni11111 @alexanderkagadovsky sorry to reply late.
I've fixed it.
please use latest version<EMAIL_ADDRESS>

@reni1111 I update the CDK dependencies to the last version. please use latest version.


sax parser with replace_entities = false still replaces entities

<IP_ADDRESS>
require 'bundler/setup'
require 'nokogiri'

class Doc < Nokogiri::XML::SAX::Document
  def characters(chars)
    p chars
  end
end

handler = Doc.new
parser = Nokogiri::HTML::SAX::Parser.new(handler)
parser.parse_memory("<body> &#61 - – &   </body>") do |ctx|
  ctx.replace_entities = false
end

" "
"="
" - "
"–"
" "
"&"
" "
" "
" "

Hi,
Thank for reporting this.
Can you provide the output from nokogiri -v so that we know what your
environment looks like?
-m
On May 10, 2015 11:32 AM, "kostya"<EMAIL_ADDRESS>wrote:

<IP_ADDRESS>
require 'bundler/setup'require 'nokogiri'
class Doc < Nokogiri::XML::SAX::Document
def characters(chars)
p chars
endend
handler = Doc.new
parser = Nokogiri::HTML::SAX::Parser.new(handler)
parser.parse_memory(" &#61 - – & ") do |ctx|
ctx.replace_entities = falseend
" "
"="
" - "
"–"
" "
"&"
" "
—
Reply to this email directly or view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1284.

# Nokogiri (<IP_ADDRESS>)
    ---
    warnings: []
    nokogiri: <IP_ADDRESS>
    ruby:
      version: 2.2.0
      platform: x86_64-darwin13
      description: ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin13]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: "/Users/kostya/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/ports/x86_64-apple-darwin13.0.0/libxml2/2.9.2"
      libxslt_path: "/Users/kostya/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/ports/x86_64-apple-darwin13.0.0/libxslt/1.1.28"
      libxml2_patches:
      - 0001-Revert-Missing-initialization-for-the-catalog-module.patch
      - 0002-Fix-missing-entities-after-CVE-2014-3660-fix.patch
      libxslt_patches:
      - 0001-Adding-doc-update-related-to-1.1.28.patch
      - 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
      - 0003-Initialize-pseudo-random-number-generator-with-curre.patch
      - 0004-EXSLT-function-str-replace-is-broken-as-is.patch
      - 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
      - 0007-Separate-function-for-predicate-matching-in-patterns.patch
      - 0008-Fix-direct-pattern-matching.patch
      - 0009-Fix-certain-patterns-with-predicates.patch
      - 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
      - 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
      - 0014-Fix-for-bug-436589.patch
      - 0015-Fix-mkdir-for-mingw.patch
      compiled: 2.9.2
      loaded: 2.9.2

Is there any update on this issue?
I also think that this test https://github.com/sparklemotion/nokogiri/blob/027a151102083258f5e297c4fecfddca56904a2a/test/xml/test_entity_reference.rb#L175 is not correct, since the block passed to Nokogiri::XML::SAX::Parser.new gets ignored. You have to pass it to #parse in order to get access to Nokogiri::XML::SAX::ParserContext. As @kostya reported it still has no effect though :-/
# Nokogiri (<IP_ADDRESS>)
    ---
    warnings: []
    nokogiri: <IP_ADDRESS>
    ruby:
      version: 2.3.0
      platform: x86_64-linux-gnu
      description: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux-gnu]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: "/var/fejo-dk/fejo-next/vendor/bundle/ruby/2.3.0/gems/nokogiri-<IP_ADDRESS>/ports/x86_64-pc-linux-gnu/libxml2/2.9.2"
      libxslt_path: "/var/fejo-dk/fejo-next/vendor/bundle/ruby/2.3.0/gems/nokogiri-<IP_ADDRESS>/ports/x86_64-pc-linux-gnu/libxslt/1.1.28"
      libxml2_patches:
      - 0001-Revert-Missing-initialization-for-the-catalog-module.patch
      - 0002-Fix-missing-entities-after-CVE-2014-3660-fix.patch
      - 0003-Stop-parsing-on-entities-boundaries-errors.patch
      - 0004-Cleanup-conditional-section-error-handling.patch
      - 0005-CVE-2015-1819-Enforce-the-reader-to-run-in-constant-.patch
      - 0006-Another-variation-of-overflow-in-Conditional-section.patch
      - 0007-Fix-an-error-in-previous-Conditional-section-patch.patch
      - 0008-CVE-2015-8035-Fix-XZ-compression-support-loop.patch
      - 0009-Updated-config.guess.patch
      - 0010-Fix-parsering-short-unclosed-comment-uninitialized-access.patch
      - 0011-Avoid-extra-processing-of-MarkupDecl-when-EOF.patch
      - 0012-Avoid-processing-entities-after-encoding-conversion-.patch
      - 0013-CVE-2015-7497-Avoid-an-heap-buffer-overflow-in-xmlDi.patch
      - 0014-CVE-2015-5312-Another-entity-expansion-issue.patch
      - 0015-Add-xmlHaltParser-to-stop-the-parser.patch
      - 0016-Detect-incoherency-on-GROW.patch
      - 0017-CVE-2015-7500-Fix-memory-access-error-due-to-incorre.patch
      - 0018-CVE-2015-8242-Buffer-overead-with-HTML-parser-in-pus.patch
      - 0019-Do-not-print-error-context-when-there-is-none.patch
      - 0020-xmlStopParser-reset-errNo.patch
      - 0021-Reuse-xmlHaltParser-where-it-makes-sense.patch
      libxslt_patches:
      - 0001-Adding-doc-update-related-to-1.1.28.patch
      - 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
      - 0003-Initialize-pseudo-random-number-generator-with-curre.patch
      - 0004-EXSLT-function-str-replace-is-broken-as-is.patch
      - 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
      - 0007-Separate-function-for-predicate-matching-in-patterns.patch
      - 0008-Fix-direct-pattern-matching.patch
      - 0009-Fix-certain-patterns-with-predicates.patch
      - 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
      - 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
      - 0014-Fix-for-bug-436589.patch
      - 0015-Fix-mkdir-for-mingw.patch
      - 0016-Fix-for-type-confusion-in-preprocessing-attributes.patch
      - 0017-Updated-config.guess.patch
      compiled: 2.9.2
      loaded: 2.9.2

I do also experience this issue with Nokogiri 1.6.8. Here's how I reproduce in irb -r nokogiri:
class Parser < Nokogiri::XML::SAX::Document;def characters(v); p v; end;end
parser.parse("’"){|ctx| ctx.replace_entities = false}
# I get "\u0092" rather than "’"

This is causing some issues later in our application. I'd love to get this bug fixed. Right now the work-around I'm using is to .gsub /&(#\d{3};)/, '!!\1' and then gsub again after processed which fixes my specific case but it is a fragile solution.

If you want a failing test, just replace these lines:
https://github.com/sparklemotion/nokogiri/blob/master/test/html/sax/test_parser.rb#L108
https://github.com/sparklemotion/nokogiri/blob/master/test/html/sax/test_parser.rb#L126
So that replace_entities is set to false and expect 'daddy & me' rather than 'daddy & me'.

As part of my work in #1926, I investigated entity handling and documented its behavior in #3265. Here's a screenshot of the docs:

As you can see, character references and predefined entities will always result in a callback to #characters with the replacement text. This is just how the underlying parsers (libxml2 and xerces) behave.
Sorry it took so long to explain this, and I hope this is helpful.


added npm to dnf install command for rpm-based linux

Updated README

Depending on the distribution you may or may not need a standalone npm package; on Fedora (at least) 'npm' appears to be included in the nodejs package:
nodejs-1:4.4.6-2.fc24.x86_64 : JavaScript runtime
Repo        : @System
It includes version 2.15.5 of npm:
2.15.5
Though there is a standalone npm package:
npm-3.5.4-5.fc24.noarch : Node.js Package Manager
Repo        : fedora
If you try to install it, you will be informed to just, like, chill out, man:
Error: installed package nodejs-1:4.4.6-2.fc24.x86_64 obsoletes npm < 3.5.4-6 provided by npm-3.5.4-5.fc24.noarch
because nodejs provides it by default now.
Maybe updating the readme to suggest that you /may/ need 'npm'.


Domain name dead

The domain name listed in the project description is dead and has been for more than a month.

Yes, thank you. I know about it I just forgot to remove it from GitHub.


Can not see Redis data in Grafana

Summary
Grafana says it's connected to Redis, but I can't get any data.
Relevant information

I am running Grafana and Redis on a docker image from here:  https://github.com/collabnix/redisedge-grafana
Redis is running and has the data I'm looking for in a time series:

Grafana is running and successfully connecting to Redis as a data source:

But I'm only intermittently successful in seeing the data in the dashboard. The query sometimes runs and sometimes doesn't:

@boriskogan81 Do you use docker-compose file from the https://github.com/collabnix/redisedge-grafana?
It's based on the image ajeetraina/grafana-redisedge which was built 6 months ago.
grafana:
    image: ajeetraina/grafana-redisedge
    environment:
      - GF_INSTALL_PLUGINS=redis-app
  #  depends_on:
  #    - prometheus
    ports:
      - 3000:3000

We fixed a couple of connectivity issues since then and fixed race condition in the Grafana.
I would recommend to try grafana/grafana:latest or our nightly build with Redis-app pre-installed:
docker run -p 3000:3000 --name=redis-app ghcr.io/redisgrafana/redis-app:latest

Please let me know if it works for you.

Sorry, I'm new to Docker.
Do you mean that in docker-compose.yaml I should change this:
grafana:
image: ajeetraina/grafana-redisedge
environment:
- GF_INSTALL_PLUGINS=redis-app
depends_on:
- prometheus
ports:
  - 3000:3000

to this?
grafana:
image: grafana/grafana:latest
environment:
- GF_INSTALL_PLUGINS=redis-app
depends_on:
- prometheus
ports:
  - 3000:3000

Sincerely,
Baruch
On Tue, Apr 27, 2021 at 11:00 PM Mikhail @.***> wrote:

@boriskogan81 https://github.com/boriskogan81 Do you use docker-compose
file from the https://github.com/collabnix/redisedge-grafana?
It's based on the image ajeetraina/grafana-redisedge which was built 6
months ago.
grafana:
image: ajeetraina/grafana-redisedge
environment:
- GF_INSTALL_PLUGINS=redis-app
depends_on:
- prometheus
ports:
  - 3000:3000

We fixed a couple of connectivity issues since then and fixed race
condition in the Grafana.
I would recommend to try grafana/grafana:latest or our nightly build with
Redis-app pre-installed:
docker run -p 3000:3000 --name=redis-app ghcr.io/redisgrafana/redis-app:latest
Please let me know if it works for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RedisGrafana/grafana-redis-datasource/issues/190#issuecomment-827890430,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACONT2ZCCDLWSIYZMZ2DI4LTK4JW5ANCNFSM43VNC4YA
.

@boriskogan81 That's correct. Have you tried it? Let me know how it goes.

Thank you so much, it works.
Sincerely,
Baruch
On Sat, May 8, 2021 at 3:23 PM Mikhail @.***> wrote:

@boriskogan81 https://github.com/boriskogan81 Please let me know if you
are able to connect or require further assistance.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RedisGrafana/grafana-redis-datasource/issues/190#issuecomment-835337168,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACONT25SEDBQLZMGAVDGEJDTMUULBANCNFSM43VNC4YA
.


Docker tooling for development

[ ]  Handle os specific directories for quilt when mounting host volumes
[ ] Add other dependencies (testing, etc)
[ ] swap mamba for conda (where possible)
[ ] use requirements files in Dockerfile

with tobler stabilized and mamba working better now, I think this is no longer an issue


[haxe] Get rid of forced saving for compiler completion in 3.3+

A version check is going to be necessary here for backwards compatibility, but it should make for a better experience when using Haxe 3.3.0+.
See https://github.com/HaxeFoundation/haxe/pull/5120

\o/

We still have to save the other files but that's a huge improvement.

Implemented #1318

Fixed


Faucet Design

Implement the new Frequency Faucet Interface design
As a front-end developer,
I want to implement the new Frequency Faucet interface design,
so that users can request test tokens easily and securely, while maintaining design consistency with the Frequency guidelines.
Acceptance Criteria:

Develop the user interface for the Frequency Faucet that aligns with the Frequency Style Guidelines provided in Figma.
Ensure that the interface allows users to seamlessly request and receive test tokens.
Replace reCAPTCHA with hCaptcha to enhance security and improve user experience.
Ensure that the design and user interface are consistent with the style guide available at: Frequency Style Guidelines on Figma.
The development process should utilize resources and code available at the provided links: Testnet Faucet: Live Faucet and Source Code: GitHub Repository.

Note:

There are no new mocks available for this task. The existing UI and UX should be maintained while reskinning the interface to align with the Frequency Style Guidelines as linked in the Figma file.
Development teams need to add and relate all necessary implementation subtasks (e.g., creating UI components, integrating hCaptcha, ensuring API connectivity, aligning with style guidelines) to this story to ensure a comprehensive and well-managed implementation process.

Track the progress and add issues in the Testnet Faucet Project.


[card section carousel]: General tabbing issues

Detailed description
I'm seeing a number of issues related to tabbing...

tabbing doesn't progress panels
tabbing doesn't update progression in pagination
tabbing sometimes messes up pagination and layout calculations
tabbing hidden items if you go away and come back
Can't get to the active panel through tabbing (without going through all the cards) after using pagination controls. Should focus be given to the first card after pagination? We should either consider jumping into the active panel, or consider jumping the carousel back to panel one.
tabbing and then resizing screen has caused pagination layout issues

Steps to reproduce the issue

Go to card section carousel
tab through cards to see behavior.

Additional information

Adding design to this because there may be some unconsidered edge cases here that need to be evaluated.

I'm addressing all these issues in #5035.
The way it currently works is that tabbing goes to the next page automatically, same with shit+tab going back.
https://images.zenhubusercontent.com/193129061/985350a5-89fa-4c3f-863d-09e21dd9ce94/screen_recording_2021_02_04_at_11_54_00_am.mov
If the current page has been changed using the page switch buttons, we can tab into the current cards being presented.
https://images.zenhubusercontent.com/193129061/29492837-195b-4432-9927-1c79cf3df40e/screen_recording_2021_02_04_at_11_58_44_am.mov


'CorsairLightingFirmwareStorageEEPROM' does not name a type; did you mean 'CorsairLightingFirmwareStorageStatic'?

Describe the problem
I try to build the LightingNodePro Code however I get the error
'CorsairLightingFirmwareStorageEEPROM' does not name a type; did you mean 'CorsairLightingFirmwareStorageStatic'?
Every time I try to compile.
However, the .h clearly exists in the Arduino > libraries > Corsair_lighting_protocol directory
I have instlled the CLP bords.
On a side note, I have unos, NodeMCUs, IOT 33's, and lilypads, I wish there was a way to get tiny USB to work with the IOT 33 but sadly I can't figure out how to so I just guess ill have to wait for Arduino to add support for tiny USB to there core. I don't want to risk flashing one of my Unos until I can at least get the code to compile. And I have no idea if It will work on the Lilypad, it's an 23u4 AVR board.
System

OS: Windows 11
Board: Explained above
Device: Lighting Node PRO/smart lighting controler
Version of IDE: Arduino IDE 1.8.16
Version of CLP: 0.15.0
Version of CLP Boards: ??? lattest?
Sketch: LightingNodePRO

Code changes
None
Full error report
Arduino: 1.8.16 (Windows 10), Board: "CLP Arduino Zero (Native USB Port), Lighting Node PRO"// NOTE: I'm using CLP Arduino Zero as it's the closest to iot 33 as its the only adrino sand bord in the list XD. but this should not matter right now as I'm not trying to upload the code just compile it.
In file included from C:\Users\benca\Documents\Arduino\libraries\Corsair_Lighting_Protocol\src/FastLEDController.h:18:0,
             from C:\Users\benca\Documents\Arduino\libraries\Corsair_Lighting_Protocol\src/CorsairLightingProtocol.h:34,

             from C:\Users\benca\AppData\Local\Temp\arduino_modified_sketch_288582\LightingNodePRO.ino:16:

C:\Users\benca\Documents\Arduino\libraries\FastLED\src/FastLED.h:14:21: note: #pragma message: FastLED version 3.004.000
pragma message "FastLED version 3.004.000"
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~

LightingNodePRO:25:1: error: 'CorsairLightingFirmwareStorageEEPROM' does not name a type; did you mean 'CorsairLightingFirmwareStorageStatic'?
CorsairLightingFirmwareStorageEEPROM firmwareStorage;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CorsairLightingFirmwareStorageStatic
LightingNodePRO:26:62: error: 'firmwareStorage' was not declared in this scope
CorsairLightingFirmware firmware(CORSAIR_LIGHTING_NODE_PRO, &firmwareStorage);
                                                          ^~~~~~~~~~~~~~~

C:\Users\benca\AppData\Local\Temp\arduino_modified_sketch_288582\LightingNodePRO.ino:26:62: note: suggested alternative: 'firmware'
CorsairLightingFirmware firmware(CORSAIR_LIGHTING_NODE_PRO, &firmwareStorage);
                                                          ^~~~~~~~~~~~~~~

                                                          firmware

LightingNodePRO:27:1: error: 'FastLEDControllerStorageEEPROM' does not name a type; did you mean 'FastLEDControllerStorage'?
FastLEDControllerStorageEEPROM storage;
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FastLEDControllerStorage
LightingNodePRO:28:34: error: 'storage' was not declared in this scope
FastLEDController ledController(&storage);
                              ^~~~~~~

LightingNodePRO:30:1: error: 'CorsairLightingProtocolHID' does not name a type; did you mean 'CorsairLightingProtocolSerial'?
CorsairLightingProtocolHID cHID(&cLP);
^~~~~~~~~~~~~~~~~~~~~~~~~~
CorsairLightingProtocolSerial
C:\Users\benca\AppData\Local\Temp\arduino_modified_sketch_288582\LightingNodePRO.ino: In function 'void loop()':
LightingNodePRO:40:2: error: 'cHID' was not declared in this scope
cHID.update();
^~~~
C:\Users\benca\AppData\Local\Temp\arduino_modified_sketch_288582\LightingNodePRO.ino:40:2: note: suggested alternative: 'HI2'
cHID.update();
^~~~
HI2
exit status 1
'CorsairLightingFirmwareStorageEEPROM' does not name a type; did you mean 'CorsairLightingFirmwareStorageStatic'?
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

If you want to use Arduino boards, look in the wiki, there is a special guide for that.

Ive looked into the wiki it only covers unos and mega both of witch require flashing witch I said I don't want to risk doing until I can get the original code to compile first.
Not onley this but i have also dug deeper then just the wiki ive looked in to your pr's and have found where you added support for sand boards by utilising tinyUSB however ardrino sandbords dont support tinyUSB in there core so it onley helps 3rd party sand bords like the adafruit fether.
There is nothing in the wiki that explains how to get ardrino sand bords to work. And i am willing to flash one of my unos but first i need to make sure that i can at least get the existing code to compile.
So again how do i solve the issue
CorsairLightingFirmwareStorageEEPROM' does not name a type; did you mean 'CorsairLightingFirmwareStorageStatic'?

@Legion2 He is trying to use "CLP Arduino Zero (Native USB Port)". It won't work because support for SAMD is implemented through TinyUSB. I thought I had a PR in to remove the SAMD boards from CLP boards but I guess I didn't. I can create a PR for this.
@skylinegodzilla CLP boards (SAMD) won't work. It's leftover from an attempt at a different implementation. SAMD boards, like the Zero, are only supported through TinyUSB and don't have an eeprom. You'd have to use the static storage class like in the TinyUSB example.
You should be able to use TinyUSB on this board by installing the adafruit library per the Readme and manually defining USE_TINYUSB in the build parameters. Take a look a the way Legion did this with the boards.txt file in his debug sketch example.

@Spegs21 yes, please create the PR and thanks for your help

@Spegs21
You said you could leave an example on how to set up tinyUSB for unsupported cores? Please do I would love it if I could use one of my ardrino IOT 33 SAMD boards but i could not figure out the core part for tinyUSB

@skylinegodzilla It shouldn't be a problem. I should be able to get to it later this week.

@Spegs21  Thank you so much.

@Spegs21 Hello is There an update on that example?

@skylinegodzilla I started on this but then realized it was going to be harder than I expected. TinyUSB conflicts with the Arduino SAMD core USB implementation and there isn't a way to disable it currently. I started arduino/ArduinoCore-samd#666 to see if they'd be open to at least allow the possibility to use it. It can still be done but it's going to take more time than I expected.

@Spegs21 ok thank you and im guessing there's no way to get this to work using the arduino samd core?

@Spegs21  wow you posted that request to them 5 days ago and they still have not replayed. I would expect them to be more proactive then that.
I'm very appreciative that you guys are responsive.

@skylinegodzilla These things can take some time. I think it's maintained mostly by volunteers.
I did make some changes to the core as I described for testing but there are conflicting definitions of Serial between the core and TinyUSB. So one or the other would need changed and the core definition of Serial is actually in the Arduino API, a different repo.

It looks like the TinyUSB Arduino library already has logic to define the CDC serial differently in some cases. It will just need updated to trigger the change when using the Arduino SAMD core.


Integrate QRAO

What should we add?
Integrate qrao-prototype into Qiskit optimization.

[ ] discuss whether to_ising returns identity matrix as offset instead of returning offset float value

Currently: operator, offset = qp.to_ising()
Newly: operator = qp.to_ising()
In order not to break API, introducing an option to control output may be useful, e.g., to_ising(offset: bool) to return operator and offset if offset=True, otherwise return only operator.

[ ] magic rounding needs to be migrated to sampler
[ ] refactor solve so that QRAO solver can access the problem to be encoded
[ ] discuss whether allow pytest for unit tests because qrao-prototype uses pytest for unit tests.

Some comments to follow up on the above points:

There is an open PR to deprecate offset: https://github.com/qiskit-community/prototype-qrao/pull/14
There is an open issue for migrating magic rounding to the sampler: https://github.com/qiskit-community/prototype-qrao/issues/21
There is a draft PR for generating the encoding on the fly: https://github.com/qiskit-community/prototype-qrao/pull/13, with the corresponding issue at https://github.com/qiskit-community/prototype-qrao/issues/9.

This might be related too #325


lint.yml only runs on push now

This change should fix issue #29 and stop the action from failing on PRs

Merged the PR for the lint.yml change


Solve the parquet conversion problem

Solving the issue in https://github.com/datafusion-contrib/tpctools/issues/6 how the datafusion solves it.

I couldn't verify if this works due to a computer issue. However, if you're encountering a conversion problem, you can try this PR. I will verify it soon.


feat: Add library example exports, add lib aliases

Description
This PR adds example exports to the library source files and imports in the example app. It also adds more test examples and introduces path aliases for the library sources.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] Country symbol

PR Summary:
New package called 'countries'
A base CountrySymbol component (similar to Icon) which is used as the wrapper for all the CountrySymbol components
Imported all the country symbol SVGs from figma
Created a script to:
Format the names of the CountrySymbols (remove special characters, strip country codes, convert to us-eng)
Generate the CountrySymbol components from the SVGs
Optimise the svgs of the resulting CountrySymbol components
Create an index file to export all the CountrySymbol components
Create a countryCodes array and countryMetaMap to be exported for consumers to use
Create a countrySymbolMap for consumers to use to map from countryCode to CountrySymbolComponent
create a lazyMap for use in LazyCountrySymbol component
Created LazyCountrySymbol component which allows consumers to change the symbol using the code prop and uses code-splitting to (hopefully) reduce bundles size
Created relevant stories
Added tests
Added documentation

PR Summary:

New package called 'countries'
A base CountrySymbol component (similar to Icon) which is used as the wrapper for all the CountrySymbol components
Imported all the country symbol SVGs from figma
Created a script to:

Format the names of the CountrySymbols (remove special characters, strip country codes, convert to us-eng)
Generate the CountrySymbol components from the SVGs
Optimise the svgs of the resulting CountrySymbol components
Create an index file to export all the CountrySymbol components
Create a countryCodes array and countryMetaMap to be exported for consumers to use
Create a countrySymbolMap for consumers to use to map from countryCode to CountrySymbolComponent
create a lazyMap for use in LazyCountrySymbol component

Created LazyCountrySymbol component which allows consumers to change the symbol using the code prop and uses code-splitting to (hopefully) reduce bundles size
Created relevant stories

This is looking great. On review I've noticed several of the SVGs have broken on export. I'm trying to find availability for a designer to take a look at this and fix the issues. A quick look through I've spotted at the very least the following needs fixing:

UN
Tuvalu
Virgin Islands (British)
Turks and Caicos Islands
Slovakia
Slovenia
Pitcairn
Peru
Niue
Montserrat
Cayman Islands
Kenya

I've submitted a review request to change 4 flags in Figma

GD
PT
UG
UN

@joshwooding Should this be a major or will that bump it to v2?

Thanks, this had already been removed but I think the latest hadn't been deployed to storybook when you reviewed. You can view the latest here:
https://0d329424.saltdesignsystem-storybook.pages.dev/?path=/story/documentation-country-symbols-country-symbol--page


[CMake] Add a package config file

This makes it easier to depend on the library from another CMake project.

Cool, thanks!


Suggestion for pricing range & certain mods where entry should be in max not min

Hi again,
Issue 1. There are item mods such as increased charges used, reduced item quantity and few other i believe where the number entry should go into max not min (you want to see items with values lower or equal to the one you have) New cluster jewel fits here too i think 8 passive cluster jewels are worth more than 10 or 12 passive ones.
Suggestion 2. Perhaps we dont need a range for pricing at all? say we use only low entry point?
Such search would show us items that are at least as good as the item that we have, people should be able to filter out of items that are MUCH better than the ones they have themselves, this way you are less likely to get no results and max rolls never get undermined when you get them.
hope that makes sense. feel free to clarify if something is unclear
p.s. really appreciate this project and how fast you implemented the fix for flask issue i have mentioned. thanks for your hard work

I also think it's a great idea to be able to choose if a specific attribute should only have min or max limit. specially I would like to see leveling items priced more correctly, by applying only max required level, and being able to control it. (example: if I want to price a req. level 30 item, I would limit the req. level to about 33 or 35 max [not min!] , so that people in those levels searching for similar properties would appreciate them, but I don't want to compare this property to higher levels, because of course they will out-match it)


Add Script to generate the original files and folder structure.

Description
This PR adds a script which combine various files and generates the original folder structure and files.
This is provided for backward compatibility.
Test Steps

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Consider some type of automatic formatting / style enforcement like flake8, black, and isort.
mypy would also be helpful if you want to enforce static typing.


Need Black Box Tests for Frontend

please post tests and test reports for final documentation

Done before the release of testing doc.


[BUG]

Logging
Used the access key id and secret access key in the command for gstreamer
Describe the bug
not able to create the required executables( may be kvs_gstreamer_sample) to stream.
Errors: "bash: ./kvs_gstreamer_sample: No such file or directory" or No such element or plugin, kvssink
One liner description about the use case: Edgility labs is trying to use the kinesis video streams to stream video using our video producer i.e raspberry pi camera interfaced to the raspberry pi 4B.
One liner description about the use case: Edgility labs is trying to use the kinesis video streams to stream video using our video producer i.e raspberry pi camera interfaced to the raspberry pi 4B.
We have followed the steps from the AWS documentation, in specific it is in Amazon Kinesis Video Streams’s developer guide( available till March 31st and week prior to that).
As suggested in step 1,we did setup the account and then followed step 2 and created the kinesis video stream. we have faced an issue in step 3.
Issue: In step 3 we have followed the steps as mentioned in the following link
To Reproduce

We have followed the steps from the AWS documentation, in specific it is in Amazon Kinesis Video Streams’s developer guide( available till March 31st and week prior to that).

As suggested in step 1,we did setup the account and then followed step 2 and created the kinesis video stream. we have faced an issue in step 3.

Issue: In step 3 we have followed the steps as mentioned in the following link
https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/blob/master/docs/raspberry-pi.md#running-the-gstreamer-sample-application-to-upload-a-video-file

We tried to run few commands to stream mentioned below but we were not able to get executables kvs_gstreamer_sample or kvssink. “gst-launch-1.0 -v rtspsrc location=rtsp://YourCameraRtspUrl short-header=TRUE ! rtph264depay ! video/x-h264, format=avc,alignment=au ! h264parse ! kvssink stream-name=YourStreamName storage-size=128”“AWS_ACCESS_KEY_ID=YourAccessKeyId AWS_SECRET_ACCESS_KEY=YourSecretAccessKey ./kvs_gstreamer_sample  </path/to/file>”
We keep getting errors below because of not able to create the required executables
( may be kvs_gstreamer_sample) to stream.
Errors: "bash: ./kvs_gstreamer_sample: No such file or directory"
ASK: We would like to seek assistance from kinesis video support center as soon as possible. If you have any follow up questions, please feel free to reach out to me.

Expected behavior
We need to stream the videos captured in a folder using the SDK
SDK version number
SDK version:f68a506.
commit :disa6302 Pull in frame rate changes from PIC and correct documentation f68a506 13 days ago
Open source building
pi camera is used to capture the video.
Platform (please complete the following information):

OS:Raspbian
Processor:ARMv8
Version  (raspberry pi 4B)

Please follow github instructions to build the SDK properly and generate the executables.

Hi Divya, I tried github documentation but was never able to get the executable. could you please double check the documentation.

@kishorekumarkadari ,
The instructions are correct. Clone->create build directory->run cmake with -DBUILD_GSTREAMER_PLUGIN=ON from build directory -> run make.
Ensure your build step passes

I changed the region and checked the secret access key gst launch is working "gst-launch-1.0 -v v4l2src do-timestamp=TRUE device=/dev/video0 ! videoconvert ! video/x-raw,format=I420,width=640,height=480,framerate=30/1 ! omxh264enc periodicty-idr=45 inline-header=FALSE ! h264parse ! video/x-h264,stream-format=avc,alignment=au ! kvssink stream-name=YourStreamName access-key="YourAccessKey" secret-key="YourSecretKey""
but I'm still getting this error "message ":"The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details." for "AWS_ACCESS_KEY_ID=YourAccessKeyId AWS_SECRET_ACCESS_KEY=YourSecretAccessKey ./kvs_gstreamer_sample </path/to/file>"
how to check on signing method?