text:
Use a Buffer for the header buffer to avoid fromCharCode calls

The performance increase might be hard to pick out from benchmarks due to the fact that it only deals with headers, and it depends on how many fields are actually present. I ended up removing _headerBufferLimit and fixing the buffer limit at 200, although I'm not sure if you really wanted that. This is the direction I went with my own parser after using the fromCharCode and concatenation approach for a while. It seems to work well.

Good idea. This is definitely not on the critical path, but hey, I like things being fast everywhere : ).
I've done some initial benchmarking of String.fromCharCode() vs. Buffer.toString(), and it seems to be well worth it:
https://gist.github.com/1303338
Node 0.4:
Options:
  Buffer Size : 200 bytes
  Runs        : 5

.....

String.fromCharCode: 27.91 mb/sec (+/- 0.51)
Buffer.toString: 381.98 mb/sec (+/- 188.50)

Node 0.5:
Options:
  Buffer Size : 200 bytes
  Runs        : 5

.....

String.fromCharCode: 38.90 mb/sec (+/- 1.60)
Buffer.toString: 1235.45 mb/sec (+/- 18.57)

I still need to find some link that slav (mraleph) from the v8 team posted about what I believed was a similar benchmark, but otherwise those numbers should speak for themselves.
Anyway, I'll need to do a little more work before merging this:

Your patch adds a new variable _headerCursor which is not needed as _marker is unused for the relevant states,
It doesn't remove the now unneeded _headerValue variable
While you detect buffer overflows within a single header field/value, a malicious client may include an unlimited amount of header fields/values in his message which are aggregated by the part object, eventually letting the attacker eat up all your memory / exploit the heap limit in node 0.4.

That being said, I'll merge this once I get the chance to make the needed changes.
--fg

Your patch adds a new variable _headerCursor which is not needed as _marker is unused for the relevant states,

Yeah, I was wondering if I was being redundant.

It doesn't remove the now unneeded _headerValue variable

I thought about it but decided to keep it for consistency's sake.

While you detect buffer overflows within a single header field/value, a malicious client may include an unlimited amount of header fields/values in his message which are aggregated by the part object, eventually letting the attacker eat up all your memory / exploit the heap limit in node 0.4.

I figured you were planning on implementing something like that. This is what I came up with after messing around a bit. It was just the first thing I noticed that could be improved.

I figured you were planning on implementing something like that. This is what I came up with after messing around a bit. It was just the first thing I noticed that could be improved.

I hope I didn't sound like I was unhappy or something! I'm very grateful for you looking over this parser.
After thinking about this approach a little more I'm still somewhat unsure about whether I want to allocate 200 bytes for each parser instance. I'm probably crazy, but I really like my parser to allocate as little as possible.
Anyway, I think I'll decide based on a more realistic benchmark where I'll test messages with lots of parts and very small part bodies. If your approach makes a noticeable difference there, I'll go for it.

I hope I didn't sound like I was unhappy or something! I'm very grateful for you looking over this parser.

Ah, sorry if I sounded annoyed or something, didn't mean to. I just meant to say that I figured you would want to add something like that, and that I intentionally didn't implement it myself.

After thinking about this approach a little more I'm still somewhat unsure about whether I want to allocate 200 bytes for each parser instance. I'm probably crazy, but I really like my parser to allocate as little as possible.

Fair enough. I was unsure about it originally too. Though I tend to think, the memory v8 ends up allocating for the concatenation of the headers might be roughly the same in the end. A Buffer still feels more rigid to work with though.

Anyway, I think I'll decide based on a more realistic benchmark where I'll test messages with lots of parts and very small part bodies. If your approach makes a noticeable difference there, I'll go for it.

Yeah, it seems hard to benchmark and it also seems sort of trivial compared to parsing large files. I never ran conclusive benchmarks, but I was just drawn to this method because it seems cleaner to me (and possibly faster).

I'll put an inner while-loop into the header field/value stats that will do a single += slice()

Yeah, that's a good idea. It's probably better to be designing for the regular case. I sometimes forget the fact that the chunks will rarely ever be 1 byte each. I think I should do something like that for my json parser now.

authors: chjj felixge

repo: felixge/node-multipart-parser


text:
Will React Spreadsheet do Calculations?

First of all, love what you have implemented so far.
Just wondering if there is a plan for this component to eventually do some basic calculations like math and simple functions like sum() and average().
Since it is called spreadsheet (as opposed to data table) it feels like it should be on the roadmap but I thought I'd check.

Hey, thanks for the question! I won't be doing substantial additional work on this thing - but I'll gladly merge all solid pull requests, so if anybody needs that (and wants to share with the community), I'd be grateful.
I'm leaving the issue open in case anybody wants to grab it!

source: gharchive/issue

authors: felixrieseberg thesunny

license: mit

license_type: permissive

license_source: bigquery


text:
Deven branch

Before issuing a pull request, please see the contributing page.
Please complete this pull request.

Is the PivotCodeTELEOP test code? If so, can we name it as such?

The PivotCodeTELEOP is a TeleOp with only the pivot code.

Ok- I will merge this for now, but we may need to think about renaming that or organizing it better, since it would be a good idea to have that for every subsystem.

source: gharchive/pull-request

license_source: github-api


text:
Preflight Checklist

[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Name of the service
ELK
URL of the service
https://elk.zone/home
GitHub URL to a recipe that has already been created by someone else or you
No response
Features you want implemented
Just integrate ELK . ELK is a multiaccount web-based Mastodon client with PWA functionality

Hi @fabiocosta0305 !
Isn't ELK a Self-Hosted instance of Mastodon? If so, you should use the Mastodon recipe instead

Nope... It uses Mastodon Protocol but has a new, more Twitter-like
interface. You can even use ELK as a client for other Mastodon Instances
Em ter., 24 de jan. de 2023 às 14:53, André Oliveira <
@.***> escreveu:

Hi @fabiocosta0305 https://github.com/fabiocosta0305 !
Isn't ELK a Self-Hosted instance of Mastodon? If so, you should use the
Mastodon recipe instead
—
Reply to this email directly, view it on GitHub
https://github.com/ferdium/ferdium-recipes/issues/298#issuecomment-1402353013,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGNDHOTNGSRTLIC6TRUD2LWUAJJJANCNFSM6AAAAAAUFMB6FQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Obrigado!
Fabio Emilio Costa                 São Bernardo do Campo - SP - Brazil
@.***            Linux User #416439(counter.li.org)
ICQ #:173799674                                  @.***
Google+: http://plus.google.com/+FabioEmilioCosta
Facebook: http://facebook.com/fabiocosta0305
Blog: hogwartslinux.wordpress.com
"Copie. Seja Legal. Não seja trouxa! Use Software Livre!"

Isn't ELK a Self-Hosted instance of Mastodon? If so, you should use the Mastodon recipe instead

No, Elk is not Mastodon instance (although some instance might use Elk as their UI instead), but a WebApp client for Mastodon which supports multi-account login inside. Similar to Ivory on iOS or Megalodon on Android.

authors: SpecialAro fabiocosta0305 nattadasu

repo: ferdium/ferdium-recipes

license: MIT


text:
🛑 Support is down

In 3ec64ad, Support (https://support.jegtheme.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Support is back up in fe0dd58 after 9 minutes.

repo: ferdysopian/jegmontol


text:
[FEAT] Dynamic filter feature

It would be great if the Pager allowed you to filter in place, the pager could have a property with a filter function on it, then when we modify the filter the pager would update in place.
An Example would be we:
We have 20 pages some with cards representing women some representing men.
A user then changes a settings view to say they only want to see men.
The filter is applied in place.
At the moment you could call the server and then get back your filtered data and reset the pager however I feel like this isn't nearly as good a solution as having the pager support filtering functionality.
At the moment if I try to performa filtering on the data after it's initial setup I get ContiguousArrayBuffer.swift:575: Fatal error: Index out of range. I suspect this is because the data behind the pager has been refreshed.
I could have a look at how to implement this myself if you point me in the right direction but I suspect this will be beyond my swiftui abilities :(
Thanks once again for creating the pager, it's a much needed project

problem is that the page isn't updated. You have items:
1  2  3  4  5  6

if you're on item 4 and filter even numbers, then there's a crash because you haven't updated the page accordingly. This related to #279 , I'll be making a quick fix there but ideally this would be handled by the client

Thanks, that makes sense will handle this issue on the client side

authors: fermoya fred-bowker

repo: fermoya/SwiftUIPager


text:
Fix Vault config example to point to correct wasm source path

The example for using the Vault Config Provider points to the wrong path for the Wasm source.
Signed-off-by: Kate Goldenring kate.goldenring@fermyon.com

Already fixed in #984

authors: kate-goldenring lann

repo: fermyon/spin


text:
Exercise spin up --key-value in tests

Main question is whether this should be covered in the existing KV test (as is done here) or broken out into a separate test.
(It would also be nice to generate a random init pair but at the moment it is a bit painful to tell the guest module what the random values are.)

having it in same test is fine, but we just need to ensure that the key/value pair is random to avoid false negatives
one of the thing we do currently in this test is to do the kv operations with in lib.rs. what we could do instead is to have those operations triggered by calling the http endpoint.
so we can do things like
key=`random key`
value=`random value`

spin up --key-value $key=$value
actual_value=curl http://localhost:3000/get?key=$key
assert $value == $actual_value

I do this in some synthetic monitors that we have and it seems to work just fine.

@rajatjindal That sounds good but I can't figure how to do it without significant surgery.  The issue is getting the dynamically generated random strings into the URL, because the URL is hardwired into the checks function.  If I try to pass the values in via  the call the checks, it fails because assertions requires an actual fn rather than a closure (i.e. cannot capture the variables from the outer scope).  And I can't pass the values as arguments to the assertions lambda, because that has to conform to ChecksFunc which has no scope for custom data.
I could change the definition of ChecksFunc, but that's used widely.  Or have an alternative assertions_extra of a function type that accepts extra data, but not sure how that would pan out as you need to have exactly one.
I'll continue to noodle but if you have any thoughts then I'd be glad of the advice!

could we do something like:
 let key = "some-random-key";
 env::set_var("KV_TEST_INIT_KEY", key.to_string());

and then
async fn checks(
            metadata: AppMetadata,
            // TODO: investigate why omitting these two next parameters does not
            // cause a compile time error but causes a runtime one
            _: Option<BufReader<ChildStdout>>,
            _: Option<BufReader<ChildStderr>>,
        ) -> Result<()> {
            println!(
                "random key is {}",
                env::var("KV_TEST_INIT_KEY").unwrap_or("".to_string())
            );
            assert_http_response(

but it won't work if we try to reuse the testcase (may still work if we reuse test app).
Rajat 🏃♂ and  hide.

@rajatjindal Oh, sorry, I forgot to update!  I found a way to let assertions accept a closure and with a bit of bonus cloning it seems to work now.  So it is ready for re-review.

@kate-goldenring That was entirely @rajatjindal's idea so all the credit is to him!  I agree it is nifty!

thank you for fixing this @itowlson

authors: itowlson rajatjindal


text:
🛑 Fenixcred Tomcat is down

In 1c56113, Fenixcred Tomcat (http://fenixcred.noip.us:8080/updater) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fenixcred Tomcat is back up in a2e2e77 after 20 minutes.


text:
Find sln files in multi-root workspace

I have a vscode workspace with multiple root directories, each containing a single solution file at the root.  The solution explorer is only finding the solution file in the top directory, and there is no way for me to add the solution from the second root directory to the explorer.

@mcdevmc This could be solved by this PR - #38 Support for Workspaces
So for I didn't receive any feedback...

I'd like one too as well. Can't use the extension until this is donc. thanks

same here, I'm investigating in my company to use Visual Studio Code with this extension you guys have been working on (btw thanks a lot for this extension!), here's the screenshot:

This is really needed for monorepos.

authors: AbbyDeng julichan majkinetor mcdevmc vlesierse


text:
Inconsistent with TextDecoder API

Not sure where does it belong, but Buffer stringifies some utf-8 chars differently than TextDecoder:
var uint8 = new Uint8Array([236, 134, 219])

var str1 = new TextDecoder('utf8').decode(uint8) //��

var str2 = Buffer.from(uint8).toString('utf8') //���

This module aims for compatibility with node's Buffer rather than TextEncoder/Decoder, but as of version 8, it appears node's behavior with respect to replacement character insertion has changed. I'll start looking into this, if anyone knows off hand what changed in node, please let me know.

@jessetane another think I spotted is inconsistent with node Buffer utf8 replacement cases:
Buffer.from([ 0xC0, 0xB1 ]).toString()
//'��' in browser
//'�' in node

I use v8.1.2

I glanced at the changelog for 8 and pulled the new tests, looks like quite few other things may have changed too... anyone out there already been thinking about this update yet?

@jessetane Nope, I have not looked into the changes. Not sure what exactly changed. If you want to look into it, that would be great
You can pull in the latest node.js tests by running ./bin/download-node-tests.js. We don't have to make all the new tests pass in one go, but can merge them in selectively until they all pass. That's what I've done in the past.

Node's Buffer is now backed by the Typed Arrays hence var str2 = Buffer.from(uint8).toString('utf8') results in var str2 = Buffer.from(uint8).toString('utf8') //��

authors: NekR dfcreative feross jessetane

repo: feross/buffer


text:
Should resources/ go into webtorrent-fixtures ?

https://github.com/feross/webtorrent-app/tree/master/resources
https://github.com/feross/webtorrent-fixtures/tree/master/fixtures

@rom1504 I know they look like they contain similar files, but they're actually serving different purposes. The fixtures are for the test suites in the various webtorrent repos, but the resources/ folder is for torrents that we're actually going to ship by default in the application.
We want users to understand how the app works as soon as they open it, so they'll see some torrents the first time. They can delete them if they want and they won't come back.

repo: feross/webtorrent-app


text:
当服务器返回的数据非json时取不到response._raw

服务器返回的是true,而客户端用uploadAccept或uploadSuccess事件都拿不到正确的response._raw，只能拿到一个空字符串。用的是分片上传
uploader.on('uploadSuccess', function(file, response){ console.log(response._raw) })

uploadAccept事件的倒数第2次能取得数据，但最后一次不行。

原因找到了。CuteFile函数负责将文件切片。这个里面的有段file.remaning = pending.length;把它改成
file.remaning = pending.length - 1; 就可以了

改file.remaning = pending.length - 1会有其他错误，最后只能在uploadAccept里做判断

@kangforceking ，改源码不太好吧，这也不是BUG，限定服务器只能返回JSON格式数据就好了。

在uploadAccept怎么获取 response headers 求解

authors: LSL1618 YoungSx kangforceking

repo: fex-team/webuploader


text:
Uncaught RuntimeError: abort(OOM)

OS: windows 10
Browser: Brave (Version 1.23.71 Chromium: 90.0.4430.72 (Official Build) (64-bit)
the ffmpeg command
ffmpeg -i myfile.mp4 -i watermark.png -filter_complex "overlay=(W-w)/2:(H-h)/2" temp.mp4
where myfile.mp4 is about 100Mb of size
In wasm, looks like this
      await ffmpeg.run(
        '-i',
        'tempVideo.mp4',
        '-i',
        'tempLogo.png',
        '-filter_complex',
        'overlay=(W-w)/2:(H-h)/2',
        'temp.mp4'
      );

Commands runs to a point, then throws the
[fferr] pthread sent an error! blob:http://localhost:4200/e85d344e-e7d0-4077-9e95-93b09522743d:1: Uncaught RuntimeError: abort(OOM). Build with -s ASSERTIONS=1 for more info.
Running the example on the ffmpeg.wasm page works fine. I am able to use the command in grabbing screenshots, works fine too. I'm taking it a step further with trying to add overlay to a video, and that's where the errors are coming from

Since I feel like my issue might actually have the same root cause, tacking on to yours:
Something regarding how ffmpeg allocates memory on a per-frame basis (maybe for interframe compression) is causes memory failures in ffmpeg.wasm (ie.Uncaught RuntimeError: abort(OOM)).
I am able to write 10,000 JPEG images of 1920x1080 resolution to MEMFS, and convert those to an mp4 video, with no errors.
As soon as I start increasing the resolution of each frame, thats when I get OOM crashes. For example, at 4k (3840x2160) I can only transcode 14 frames into an mp4 before ffmpeg.wasm crashes.
MEMFS seems to have no issues holding the 10,000 images. The issue comes from ffmpeg.

OS: MacOS 12.6.5
Browser: Chrome 113.0.5672.126
Version: ffmpeg.wasm v0.11.6

I'm getting the same error while executing the following command in a loop. I am extracting parts of an mp3 file based on the timestamps on a subtitles file. It executes fine for exactly 200 iterations then crashes. I'm on node 16.20.1
ffmpeg.run("-i", parsedAudioFilePath.base, "-ss", startTimestamp, "-to", endTimestamp, "-c", "copy", fragmentFilename);

Full error:
if(l){ra=oa?require("path").dirname(ra)+"/":__dirname+"/";ta=function(a,b){wa||(wa=require("fs"));xa||(xa=require("path"));a=xa.normalize(a);return wa.readFileSync(a,b?null:"utf8")};va=function(a){a=ta(a,!0);a.buffer||(a=new Uint8Array(a));assert(a.buffer);return a};1<process.argv.length&&(ka=process.argv[1].replace(/\\/g,"/"));ja=process.argv.slice(2);process.on("uncaughtException",function(a){if(!(a instanceof ca))throw a;});process.on("unhandledRejection",u);la=function(a){process.exit(a)};f.inspect=

RuntimeError: abort(RuntimeError: abort(OOM). Build with -s ASSERTIONS=1 for more info.). Build with -s ASSERTIONS=1 for more info.
    at process.u (/home/davide/code/node/subs-audio-splitter/node_modules/@ffmpeg/core/dist/ffmpeg-core.js:25:109)
    at process.emit (node:events:513:28)
    at emit (node:internal/process/promises:140:20)
    at processPromiseRejections (node:internal/process/promises:274:27)
    at processTicksAndRejections (node:internal/process/task_queues:97:32)

Getting the same error, Here is the log:
{type: 'stderr', message: 'ffmpeg version 5.1.4 Copyright (c) 2000-2023 the FFmpeg developers'}
classes.js?v=664023e1:47 {type: 'stderr', message: 'ffmpeg version 5.1.4 Copyright (c) 2000-2023 the FFmpeg developers'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  built with emcc (Emscripten gcc/clang-like repla…3.1.40 (5c27e79dd0a9c4e27ef2326841698cdd4f6b5784)'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  built with emcc (Emscripten gcc/clang-like repla…3.1.40 (5c27e79dd0a9c4e27ef2326841698cdd4f6b5784)'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  configuration: --target-os=none --arch=x86_32 --…nable-libfribidi --enable-libass --enable-libzimg'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  configuration: --target-os=none --arch=x86_32 --…nable-libfribidi --enable-libass --enable-libzimg'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavutil      57. 28.100 / 57. 28.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavutil      57. 28.100 / 57. 28.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavcodec     59. 37.100 / 59. 37.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavcodec     59. 37.100 / 59. 37.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavformat    59. 27.100 / 59. 27.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavformat    59. 27.100 / 59. 27.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavdevice    59.  7.100 / 59.  7.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavdevice    59.  7.100 / 59.  7.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavfilter     8. 44.100 /  8. 44.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libavfilter     8. 44.100 /  8. 44.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libswscale      6.  7.100 /  6.  7.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libswscale      6.  7.100 /  6.  7.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libswresample   4.  7.100 /  4.  7.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libswresample   4.  7.100 /  4.  7.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libpostproc    56.  6.100 / 56.  6.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  libpostproc    56.  6.100 / 56.  6.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: "Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':"}
classes.js?v=664023e1:47 {type: 'stderr', message: "Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':"}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    major_brand     : qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    major_brand     : qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    minor_version   : 0'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    minor_version   : 0'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    compatible_brands: qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    compatible_brands: qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    creation_time   : 2024-09-03T08:22:43.000000Z'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    creation_time   : 2024-09-03T08:22:43.000000Z'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Duration: 00:02:42.67, start: 0.000000, bitrate: 2745 kb/s'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Duration: 00:02:42.67, start: 0.000000, bitrate: 2745 kb/s'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Stream #0:0[0x1](und): Video: h264 (High) (avc1 …, 2739 kb/s, 39.51 fps, 60 tbr, 600 tbn (default)'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Stream #0:0[0x1](und): Video: h264 (High) (avc1 …, 2739 kb/s, 39.51 fps, 60 tbr, 600 tbn (default)'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      creation_time   : 2024-09-03T08:22:43.000000Z'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      creation_time   : 2024-09-03T08:22:43.000000Z'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      handler_name    : Core Media Video'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      handler_name    : Core Media Video'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      vendor_id       : [0][0][0][0]'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      vendor_id       : [0][0][0][0]'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      encoder         : H.264'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      encoder         : H.264'}
classes.js?v=664023e1:47 {type: 'stderr', message: 'Stream mapping:'}
classes.js?v=664023e1:47 {type: 'stderr', message: 'Stream mapping:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))'}
classes.js?v=664023e1:47 {type: 'stderr', message: '[libx264 @ 0xdf38f0] using cpu capabilities: none!'}
classes.js?v=664023e1:47 {type: 'stderr', message: '[libx264 @ 0xdf38f0] using cpu capabilities: none!'}
classes.js?v=664023e1:47 {type: 'stderr', message: '[libx264 @ 0xdf38f0] profile High, level 5.1, 4:2:0, 8-bit'}
classes.js?v=664023e1:47 {type: 'stderr', message: '[libx264 @ 0xdf38f0] profile High, level 5.1, 4:2:0, 8-bit'}
classes.js?v=664023e1:47 {type: 'stderr', message: '[libx264 @ 0xdf38f0] 264 - core 164 - H.264/MPEG-4…qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00'}
classes.js?v=664023e1:47 {type: 'stderr', message: '[libx264 @ 0xdf38f0] 264 - core 164 - H.264/MPEG-4…qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00'}
classes.js?v=664023e1:47 {type: 'stderr', message: "Output #0, mp4, to 'output_overlay.mp4':"}
classes.js?v=664023e1:47 {type: 'stderr', message: "Output #0, mp4, to 'output_overlay.mp4':"}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    major_brand     : qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    major_brand     : qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    minor_version   : 0'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    minor_version   : 0'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    compatible_brands: qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    compatible_brands: qt  '}
classes.js?v=664023e1:47 {type: 'stderr', message: '    encoder         : Lavf59.27.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    encoder         : Lavf59.27.100'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Stream #0:0(und): Video: h264 (avc1 / 0x31637661…), 1290x2796, q=2-31, 60 fps, 15360 tbn (default)'}
classes.js?v=664023e1:47 {type: 'stderr', message: '  Stream #0:0(und): Video: h264 (avc1 / 0x31637661…), 1290x2796, q=2-31, 60 fps, 15360 tbn (default)'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    Metadata:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      creation_time   : 2024-09-03T08:22:43.000000Z'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      creation_time   : 2024-09-03T08:22:43.000000Z'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      handler_name    : Core Media Video'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      handler_name    : Core Media Video'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      vendor_id       : [0][0][0][0]'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      vendor_id       : [0][0][0][0]'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      encoder         : Lavc59.37.100 libx264'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      encoder         : Lavc59.37.100 libx264'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    Side data:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '    Side data:'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A'}
classes.js?v=664023e1:47 {type: 'stderr', message: '      cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A'}
classes.js?v=664023e1:50 {progress: 0, time: 0}
classes.js?v=664023e1:50 {progress: 0, time: 0}
App.tsx:82 Progress: 0%, Current time: 0
classes.js?v=664023e1:47 {type: 'stderr', message: 'frame=    1 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    '}
classes.js?v=664023e1:47 {type: 'stderr', message: 'frame=    1 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    '}
classes.js?v=664023e1:50 {progress: 0, time: 0}
classes.js?v=664023e1:50 {progress: 0, time: 0}
App.tsx:82 Progress: 0%, Current time: 0
classes.js?v=664023e1:47 {type: 'stderr', message: 'frame=   38 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    '}
classes.js?v=664023e1:47 {type: 'stderr', message: 'frame=   38 fps=0.0 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    '}
classes.js?v=664023e1:50 {progress: 0, time: 0}
classes.js?v=664023e1:50 {progress: 0, time: 0}
App.tsx:82 Progress: 0%, Current time: 0
classes.js?v=664023e1:47 {type: 'stderr', message: 'frame=   47 fps= 26 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    '}
classes.js?v=664023e1:47 {type: 'stderr', message: 'frame=   47 fps= 26 q=0.0 size=       0kB time=00:00:00.00 bitrate=N/A speed=   0x    '}
classes.js?v=664023e1:47 {type: 'stderr', message: 'Aborted(OOM)'}message: "Aborted(OOM)"type: "stderr"[[Prototype]]: Object
classes.js?v=664023e1:47 {type: 'stderr', message: 'Aborted(OOM)'}

authors: benz2012 deedeedev seanmavley wonderkidshihab


text:
Documentação do Lean Inception

Documentação do Lean Inception
Issue

#59
Descrição

Foi criada uma página de documentação sobre os resultados obtidos no Lean Inception
Tipos de Mudanças

[ ] Bug fix (alteração ininterrupta que corrige um problema)
[ ] Nova feature (mudança ininterrupta que adiciona funcionalidade)
[ ] Breaking change (correção ou recurso que faria com que a funcionalidade existente não funcionasse como esperado)
[x] Documentação (adição ou remoção de algum artefato)

Checklist:

[x] Meu código segue os padrões de estilo deste projeto.
[ ] Minha alteração requer uma alteração na documentação.
[x] Atualizei a documentação de acordo.

tudo ok, lembra de criar o PR para a devel da próxima vez. e criar a branch a partir dela também.


text:
Getting ORC-WER breakdown

Is there a simple way to get the WER break-down into ins/del/sub when computing the ORC-WER?

At the moment, it is not implemented. But we planned to integrate it. Since you are interested, I will take care to implement it.
Do you have a suggestion, how it should be obtained? ins/del/sub aren't unique values.
Do people expect to get the same as Kaldi?
I thought about adding my Kaldi wrapper, so that the optimization is done in python/cython, but the final WER is obtained with Kaldi (Editdistance is the same, but Kaldi additionally reports the ins/del/sub).

Thanks for the pointer, I forgot that kaldialign exists. The code will be much cleaner with kaldialign, then a wrapper around kaldi could be, since adding a pip dependency is simple.

Now the code uses kaldialign to calculate insertions, deletions and substitutions. Hence, the generated files have now this information:
.../meeteval/example_files$ python -m meeteval.wer orcwer -h 'hyp*.stm' -r 'ref*.stm'
Wrote: .../hyp_orcwer_per_reco.json
Wrote: .../hyp_orcwer.json

.../meeteval/example_files$ cat hyp_orcwer.json
{
  "errors": 18,
  "length": 184,
  "insertions": 0,
  "deletions": 14,
  "substitutions": 4,
  "error_rate": 0.09782608695652174
}

.../meeteval/example_files$ cat hyp_orcwer_per_reco.json
{
  "recordingA": {
    "errors": 4,
    "length": 124,
    "insertions": 0,
    "deletions": 0,
    "substitutions": 4,
    "error_rate": 0.03225806451612903,
    "assignment": [
      "Alice",
      "Alice",
      "Bob",
      "Bob",
      "Alice",
      "Alice",
      "Alice",
      "Alice"
    ]
  },
  "recordingB": {
    "errors": 14,
    "length": 60,
    "insertions": 0,
    "deletions": 14,
    "substitutions": 0,
    "error_rate": 0.23333333333333334,
    "assignment": [
      "Bob",
      "Bob",
      "Alice",
      "Alice"
    ]
  }

Let me know, when you need more features or if a modification could simplify an integration in another framework.

repo: fgnt/meeteval


text:
adding start date and estimated time

I am using the api json to insert new tasks from our erp system (ms sql) with python 3.5  with kanboard on MySQL. I'm using pythons requests to add tasks.   currently have the tasks being created if they do not exist.  I would like to add in the tasks table date_started and time_estimated.  I am updating directly in the MySQL tasks table but having an issue with the date_started.  what format do you use in the tasks date_started column?

unix timestamp

thank you. got it working.

authors: fguillot sstecker

repo: fguillot/kanboard


text:
Remove UI folder

We've decided to remove UI for now, and wrap everything into one helpers folder.

I've just removed the UI message handler for now.

authors: LukeFinch limitlessloop

repo: fignite/helpers


text:
Add new company: [IBM]

Company Name?
IBM
What's the company main business today?
IT services, cloud computing, and enterprise software
What did the company do in the early days?
Sell physical, punch card based tabulating machines.
What caused the company to pivot?
Computers
Source?
https://www.ibm.com/ibm/history/ibm100/us/en/icons/tabulator/

Added. I hope this doesn't make the HN crowds angry. But I think it's still a good lesson to learn from.
Thanks a lot!

Added. I hope this doesn't make the HN crowds angry. But I think it's still a good lesson to learn from.
Thanks a lot!

authors: derekpankaew fikrikarim


text:
Client Allocation Request for: gdzkzy

Client Allocation Questions
Core Information

Name: gdzkzy
Website / Social Media: https://www.gdzkzy.cn/
Region: Greater China
DataCap Requested: 5TiB
Addresses to be Notarized: f0442671
Notary Requested: ozhtdong

@zkzy0407 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/673 Is this one yours?


text:
Folder not combining on pasting

Description
If I have two folder with the same name but different content they wont be combined. they will either replace the old content with the new content or just make the same folder with "- copy" added on.
Steps To Reproduce

Create a folder with a name in a directory.
Add a file to it.
Create a new folder with the same name but another place
Add a file with a different name
Cut on of the folders and paste it were the other one is

Expected behavior
It should bring up the conflict dialog and ask me to what I want to do and add a combine button. So the content merged.
Files Version
1.9.24
Windows Version
10.0.19043.1151
Relevant Assets
debug.log
debug_fulltrust.log

If you choose replace in the conflict dialog it should merge the folders and replace files if they have the same name. Could you confirm this?

When I tried that it seemed to just delete the original files in there. However continuing to use it I've seen that some file just wont copy, usually there left in the original place witch it wasn't,

Just tried it again brings up the prompt I click replace existing and it just made folder name - copy versions. Didn't edit or add any data in the original non - copy folder.

Are you in a local folder? Not a network folder or something?

Its a local folder. Seem to happen sometimes didn't do it for the next folder I did. I'll upload the updated logs if that helps.
debug.log
debug_fulltrust.log

@gave92 any ideas on this?

Nope, as I can't reproduce.

Closing due to it not happening for a long time.

repo: files-community/Files


text:
Add the ability to drag tabs into other windows

Firefox has this. Open two windows then drag and drop the tabs into another window. It's useful if you want to have a side by side pane view of different folders.

FYI I used the "Give Feedback" link and was redirected here, no mention about "issue templates" or anything.


text:
Calm down rectangle selection

It seems that our Rectangle Selection is not aware of the fact
that brain and fingers are not connected.
So if you click and move a mouse a tiny bit, it already gets triggered.
This is something not really pleasant, as it might cancel shift selection
of the grid, or to unregister AllView_Item pressed, actually preventing
activation in one-click mode.
This PR verifies that the mouse has moved sufficiently to indicate
rectangle selection (the value is hard-coded right now - please
let me know if you have better ideas).
BTW, probably the better solution is radius, rather than checking
the dimensions, but I doubt the ROI :smile:

Also here this issue is back #2749?

Also here this issue is back #2749?

@gave92 - doesn't happen to me. Also see no reason why it would. 🤔

@gave92 - fixed.. by rebasing to master :smile:

@Don-Vito uops xD I just assumed it already was. Thanks

BTW, probably the better solution is radius, rather than checking
the dimensions, but I doubt the ROI 😄

@Don-Vito If you want radius you can use the vector-distance-formula like so:
private double CalcVectorDistance(int x1, int y1, int x2, int y2)
{
    return Math.Sqrt(Math.Pow((x2 - x1), 2) + Math.Pow((y2 - y1), 2));
}


text:
add strings for update dialog

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #5489

Details of Changes
Add details of changes here.

Added missing strings for dialog

Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Screenshots (optional)

@winston-de could you guess why some people are reporting this in debug.log?
It looks like the empty content dialog issue is related to another dialog , by the time DownloadUpdatesConsent is called there's another dialog open..
`2021-07-23 14:58:33.2965|WARN|CheckForUpdatesAsync|Could not fetch updates.
System.Exception: An async operation was not properly started.
Only a single ContentDialog can be open at any time.
at System.Runtime.InteropServices.McgMarshal.ThrowOnExternalCallFailed(Int32, RuntimeTypeHandle) + 0x21
at __Interop.ComCallHelpers.Call(__ComObject, RuntimeTypeHandle, Int32, Void*) + 0xbe
at __Interop.ForwardComStubs.Stub_3[TThis, TResult](__ComObject, Int32) + 0x37
at Windows.UI.Xaml.Controls.ContentDialog.ShowAsync() + 0x18
at Files.Helpers.AppUpdater.d__3.MoveNext() + 0xdd`

@yaichenbaum I'm curious, have you made the latest update mandatory? I've never seen that dialog :)

I've been making them mandatory for a couple of months, I'm not sure why this only started working recently :D

I've been making them mandatory for a couple of months, I'm not sure why this only started working recently 😂

Oops see #5436, so much for "Cosmetic changes", I've never fixed anything by mistake 😂

authors: gave92 winston-de yaichenbaum


text:
Revert "chore: add semgrep"

Reverts finisterra-io/terraform-aws-elasticache-redis#6

This PR is included in version 1.0.5 :tada:


text:
Fix #39 m8 authentication screen issue

Remove javascript and redirect to project website instead of trying to close the window since this is not allowed by browsers anymore. This PR fixes #39 .

Coverage remained the same at 34.37% when pulling 4fb885ffa0ede311ead3a5931b17f29b88245d96 on fix/#39-monoskope-auth-screen-issue into 5ca9b2a6d48a0c02e848dcc3cc1f6649c0075e32 on main.

authors: coveralls jastBytes

repo: finleap-connect/monoctl


text:
03 Oct 2024 - A11y Theme Builder Meeting Minutes

Date
2024-10-03 - 09:15am EDT
Zoom info

Meeting link: https://zoom.us/j/91013899295?pwd=Qnh5UVN1aUZ4ak9tODgvMVNLNUg5Zz09
Meeting id: 910 1389 9295
Password: 123225
Call-in: +1 929 205 6099 US (New York) (Check calendar for more options)

Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] Upcoming demos (@aaronreed708)

[ ] Tuesday 10/01 (@aaronreed708)
[ ] Friday 10/04 (@lwnoble)

[ ] Mentorship project update (@omesh-omg)
[ ] AOB, Q&A & Adjourn (5mins)

Minutes

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] (from last week) Lise to get Omesh and Aaron CSS and responsive breakpoints and behaviors for #820 design

will provide CSS for framework only for now

[ ] (from last week)Aaron and Evan need to break the Epic that will be worked on by the mentee into detailed and digestable issues
[ ] (from last week) Lise to work with Aaron to update video in mkdocs documentation
[ ] (from last week) Lise and Paula to meet re: Theme Builder at Grace Hopper Open Source Day
[ ] (from last week) Cody to look at pre-push hook
[ ] (from last week) Aaron to follow up with author of #1026

Evan K - DFS

Also attended by:
Cody Zuschlag - Nearform
Kathleen Burkhardt - Black Rock
Lise Noble - DFS
Aaron Reed - DFS

Approved in today's call


text:
OSS Supply Chain Working Group - DevOps Automation - June 6, 2023

June 6, 2023
Thursday 06 Jun 2023 - 09:00 EST / 14:00 UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people
[ ] Approve previous meeting minutes
[ ] Review DevOps SIG project board
[ ] Add Items Here
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info
Join Zoom Meeting

https://zoom.us/j/95521041942?pwd=dHgwREU2TzBsS242ak1zYWZsUW9OUT09
Meeting ID: 955 2104 1942
Passcode: 443820
Find your local number: https://zoom.us/u/aesEqmNODb

Github Repo: https://github.com/finos/devops-automation/
Project Board: https://github.com/orgs/finos/projects/33
Working Group Board: https://github.com/orgs/finos/projects/65
Mailing List: Email devops-mutualization+subscribe@finos.org to subscribe to our mailing list

hi - Bruno from Morgan Stanley

authors: brunon johnmark

repo: finos/devops-automation


text:
Complex pure prop mapping

Summary
Remove assertion for non-nullable target set for complex property. We are relaxing this in backend
Ref: https://github.com/finos/legend-engine/pull/1577

How did you test this change?

[x] Test(s) added
[ ] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

@hardikmaheshwari have we checked that the analyze mapping returns the properties of the complex properties as true so this works with query builder out of the box.
Additionally, does the mapping editor, behave if this mapping is loaded. I believe we rely on the target being there for rendering but maybe not.

@hardikmaheshwari have we checked that the analyze mapping returns the properties of the complex properties as true so this works with query builder out of the box. Additionally, does the mapping editor, behave if this mapping is loaded. I believe we rely on the target being there for rendering but maybe not.

@MauricioUyaguari Thanks for looking, yes I loaded the mapping editor and tested it out. It was failing earlier because of asserts which I am removing.
As for query builder you are right analyze mapping won't return the nested properties but it might be a bit tricky to handle cyclic models from the backend so leaving that for now

authors: MauricioUyaguari hardikmaheshwari

repo: finos/legend-studio


text:
Measurable Ratings: enable for non-applications

Would be nice to allow ACTOR and (upcoming LEGAL_ENTITY) objects the ability to describe themselves against the measurable taxonomies

Legal Entity is still upcoming :)

repo: finos/waltz


text:
Jasmine/Karma unit test example

Hello
Would it be possible to get a reference example on how to unit test a controller with an AngularFire/Firebase dependency?

404 page not found…

That's because those links are nearly three years old. The repo is https://github.com/firebase/angularfire-seed and the end-to-end tests are now at https://github.com/firebase/angularfire-seed/tree/master/e2e-tests.

authors: ThibaultJanBeyer jwngr paulsheldrake

repo: firebase/angularfire


text:
fs-bq-schema-views fails to add schema view for second table

[READ] Step 1: Are you in the right place?
yep
[REQUIRED] Step 2: Describe your configuration

Extension name: firestore-bigquery-export (fs-bq-schema-views script)
Extension version: 0.1.1

[REQUIRED] Step 3: Describe the problem
I have 2 instances of firestore-bigquery-export running, which export 2 different collections from firestore.
I've added schema view for 1st instance/collection (firestore* functions and schema view for changelog table).
When I'm trying to add 2nd schema view for another collection/table, I'm getting error and no new schema added to dataset.
Steps to reproduce:
$ npx @firebaseextensions/fs-bq-schema-views \
> --non-interactive \
> --project=REDACTED \
> --dataset=firestore_export \
> --table-name-prefix=instances \
> --schema-files=./instances.json
{"code":409,"errors":[{"message":"Already Exists: Routine REDACTED.firestore_export.firestoreArray","domain":"global","reason":"duplicate"}],"message":"Already Exists: Routine REDACTED.firestore_export.firestoreArray"}
Already Exists: Routine REDACTED.firestore_export.firestoreArray

Expected result
new schema view created
without any errors
Actual result
Error produced and no new schema view.
As a side-note, I've got same error when was creating first schema view, but all functions and schema view for changelog table were created

I'm also getting this. I'm not sure why this is happening. I deleted firestoreArray, firestoreBoolean, firestoreGeopoints, firestoreNumber, firestoreTimestamp from the BigQuery web UI. Look under Resources >  >  in the left sidenav. That solved it for me, and I was able to re-upload the schema.

Hey, looks like this was fixed in #193 - but the package still needs publishing to NPM - we'll get this looked at, thanks.

Still broken.
Maybe, cause npm has some 0.1.3 version published? (https://www.npmjs.com/package/@firebaseextensions/fs-bq-schema-views/v/0.1.3)

Hi the package has now been published, sorry for the delay.

repo: firebase/extensions


text:
how to distribute aab file

i would like to distribute app bundle through this plugin but i can't.
i explored this document, it does not have such a function.
does it have this way?
or do you have a plan it will be implemented?

i got to know firebase_app_distribution doesnt have this way
i will close

platform :android do
desc "My awesome app"
lane :distribute do
build_android_app(task: "bundle", ...)
# build_android_app is a built-in fastlane action.
    firebase_app_distribution(
        app: "1:123456789:android:abcd1234",
        testers: "tester1@company.com, tester2@company.com",
        release_notes: "Lots of amazing new features to test out!",
        android_artifact_type:"AAB",
      android_artifact_path: '../build/app/outputs/bundle/release/app-release.aab',
    )

end

end

platform :android do
desc "My awesome app"
lane :distribute do
build_android_app(task: "bundle", ...)
# build_android_app is a built-in fastlane action.
    firebase_app_distribution(
        app: "1:123456789:android:abcd1234",
        testers: "tester1@company.com, tester2@company.com",
        release_notes: "Lots of amazing new features to test out!",
        android_artifact_type:"AAB",
        android_artifact_path: '../build/app/outputs/bundle/release/app-release.aab',
    )

end

end

authors: nidovic shiratsu


text:
Added topic subscription information retrieval to messaging client

This commit should provide the feature requested in FR #99.

@chong-shao is this something the FCM team is interested in releasing?

@chong-shao there's a product decision to be made here. Do we even want to expose this API in our SDKs? We ought to run this by a PM first.

@hiranya911 synced with our PM. The feedback is that we should not merge this into master branch unless the endpoint has been switched to the new one (which has not been set up yet).
Can we put this is a side branch? Or keeping the PR in open status until the new endpoints are ready? @andirayo

@chong-shao I agree. We can keep the PR open for now.
We also possibly need an API proposal, and at least a semblance of a plan to have the same API exposed in other languages at some point.

repo: firebase/firebase-admin-go


text:
Add MFA info to UserRecord

Discussion
Issue: https://github.com/firebase/firebase-admin-go/issues/421
This PR implements a small part of Multi Factor Authentication (MFA). I do realize this isn't a full implementation, unfortunately I don't have time for that. This PR only implements unmarshalling the MFA info from the REST response into the UserRecord struct.
For structure and naming within the UserRecord, I've decided to be consistent with the Node.js client library, which already has this implemented: https://firebase.google.com/docs/reference/admin/node/admin.auth.UserRecord
Testing

I've updated the existing tests to also incorporate MFA. On the existing testUser, I've added MFA info. Next to that, I've introduced a test user without MFA. In the list endpoints, I replaced every third user with a non MFA user, so the list tests both users with and without MFA info available. All unit tests should be OK.
Unfortunately, I wasn't able to get the integration tests running locally, so I'm not sure whether I did break something there. I did manage to test the code in an actual project with a small local setup and verified that it works.

API Changes

This PR does not change the public API. The REST API already returns the mfaInfo section. This PR merely adds the code to pick it up into Golang structs.

Thanks @jasperkuperus for the PR. It looks mostly good. I've suggested some changes to the public API.
@bojeil-google how do you feel about just releasing the changes to UserRecord without the support for updating MFA settings?

I think it's fine to do so, as long as we keep track of the missing functionality (updating MFA settings). Ultimately, we want to make sure we have feature parity across all languages.

API review process for this has been initiated. Should have some updates by next week.

This API has been approved with some minor changes. The change being removal of the MultiFactorID type and the related Phone constant (we will use FactorID string instead).
@jasperkuperus would you like to push the change to this PR? If you're busy I can merge this as-is, and implement the required changes on top of that.

@jasperkuperus would you like to push the change to this PR? If you're busy I can merge this as-is, and implement the required changes on top of that.

@hiranya911  It's a small change, but I have a rather busy week for me. If you could be so kind to merge it and implement the change on top of that, it'd be of great help, thanks! 😊

authors: bojeil-google hiranya911 jasperkuperus


text:
Added hash input order option when importing users

Implements #313.
This PR includes the implementation of a new hash.inputOrder option for the importUsers() auth methods, with the relevant unit and integration tests and type definitions. See the issue for more information and a usage example.
Note that all unit tests pass on my local machine and all integration tests except admin.auth importUsers() successfully imports users with MD5 to Firebase Auth w/ explicit password-first hash pass as well. It is my understanding from the --hash-input-order documentation that it should apply to the MD5 algorithm as well. However, this integration test fails although the request being made to the Firebase Auth backend looks correct to me. It would be great if someone from the Firebase Auth team took a look into what is going wrong with that test.

Sorry for the delay @jwngr. The API review for your proposed Node.js changes is under way.

authors: bojeil-google jwngr

repo: firebase/firebase-admin-node


text:
[Bug] Remote config thread crashes getting timezone on non-English Windows systems

[REQUIRED] Please fill in the following fields:

Pre-built SDK from the website or open-source from this repo: open-source (self built)
Firebase C++ SDK version: 11.2.0
Problematic Firebase Component: Remote Config
Other Firebase Components in use: Auth
Platform you are using the C++ SDK on: Windows
Platform you are targeting: desktop

[REQUIRED] Please describe the issue here:
We’re seeing the following crash on first launch when initializing remote config. This seems to happen only if the system language is not English (tested with German), and can be resolved by changing the time zone. Afterwards changing the timezone back works fine, possibly due to caching of remote config data.
I believe this is related to the changes in #1332 by @jonsimantov. The crash occurs in line 116 here:
https://github.com/firebase/firebase-cpp-sdk/blob/ab2fd00d2ca41e7ddec8eee9f37c3751f1bb0e13/app/src/locale.cc#L114-L116
Crash log:
OS Version: Windows 10.0.19045 (3086)
Report Version: 104

Crashed Thread: 8596

Application Specific Information:
Fatal Error: Unhandled C++ Exception / 0x7ffe65b6cf19

Thread 8596 Crashed:
0   KERNELBASE.dll                  0x7ffe65b6cf19      RaiseException
1   VCRUNTIME140.dll                0x7ffe2948671f      _CxxThrowException (throw.cpp:74)
2   MyApp.exe                       0x7ff7611db2a1      std::_Throw_range_error (stdexcept:166)
3   MyApp.exe                       0x7ff7611dc598      std::wstring_convert<T>::from_bytes (xlocbuf:396)
4   MyApp.exe                       0x7ff761285361      [inlined] std::wstring_convert<T>::from_bytes (xlocbuf:366)
5   MyApp.exe                       0x7ff761285361      firebase::internal::GetTimezone (locale.cc:116)
6   MyApp.exe                       0x7ff7611f2edc      firebase::remote_config::internal::RemoteConfigREST::SetupRestRequest (rest.cc:136)
7   MyApp.exe                       0x7ff7611f26fa      firebase::remote_config::internal::RemoteConfigREST::Fetch (rest.cc:71)
8   MyApp.exe                       0x7ff76116f2c8      firebase::remote_config::internal::RemoteConfigInternal::FetchInternal (remote_config_desktop.cc:597)
9   MyApp.exe                       0x7ff76116f648      <lambda>::<T> (remote_config_desktop.cc:175)
10  MyApp.exe                       0x7ff761170261      [inlined] firebase::callback::CallbackVariadic<T>::RunInternal (callback.h:341)
11  MyApp.exe                       0x7ff761170261      firebase::callback::CallbackVariadic<T>::Run (callback.h:332)
12  MyApp.exe                       0x7ff7611623e7      firebase::scheduler::Scheduler::TriggerCallback (scheduler.cc:189)
13  MyApp.exe                       0x7ff761162232      firebase::scheduler::Scheduler::WorkerThreadRoutine (scheduler.cc:169)
14  MyApp.exe                       0x7ff76116ab8e      [inlined] std::invoke (type_traits:1574)
15  MyApp.exe                       0x7ff76116ab8e      std::thread::_Invoke<T> (thread:55)
16  ucrtbase.dll                    0x7ffe65731bb1      thread_start<T>
17  KERNEL32.DLL                    0x7ffe668e7613      BaseThreadInitThunk
18  ntdll.dll                       0x7ffe680826f0      RtlUserThreadStart

Steps to reproduce:

Set system language to e.g. German:

Open Windows 10 settings
Select "Time & language" section
Click "Add Language" and select "Deutsch (Deutschland)" / "German (Germany)"
Make German the primary language by moving it to the top of the list of preferred languages
Reboot

Initialize Firebase Remote Config

Hmm, interesting. It looks like a range_error occurs. Could there be a character included in the UTF8 string that can't be specified in UTF16? If that's the case, I think changing from codecvt_utf8 to codecvt_utf8_utf16 could fix this. Do you know what the value of windows_tz_utf8 is?

Also, one thing that would be helpful, on your machine set to German: Could you run the following command in the Windows shell and paste the output here?
tzutil /l
This will list all of the time zones that Windows knows about, so I can see what their localized names are and determine if that's what's causing the issue.

I was able to reproduce this in the debugger. Here is the output from get_tzname():

And here the std::string before the conversion:

The string should be "Mitteleuropäische Zeit", but as you can see the umlaut is not being interpreted correctly. I’m not entirely sure where it’s going wrong, but I believe the input is not actually UTF-8 encoded. Maybe this helps:

And here’s the output from tzutil /l:
tzutil-list.txt

Also, weird that tzutil's time zone list doesn't actually have that time zone you listed. Is that the value of your TZ environment variable?

@triplef Could you build the fix-for-windows-time-zone branch (#1375) and see if that fixes the issue?

Thanks @jonsimantov. I tried that branch and it doesn’t crash any more, but stepping through the code it looks like it’s still unable to get the timezone, and the strings don’t look correct yet:

Thanks for following up. I'll add some tests to make sure the conversion is correct and will follow up shortly. BTW, what's the value of your TZ environment variable? Do you have any other environment variables that contain a time zone that matches any of the tzutil /l entries?

Added a unit test and found the issue—signed char strikes again! So if you pull the latest contents of the branch, it should convert correctly now. Could you give it a try?

I tried the latest branch, but got_time_zone is still false:

I don’t seem to have a TZ environment variable set. To reproduce the bug I think you just need to change your system language to German and the time zone to this (probably also works with other languages/timezones containing non-ASCII characters):

Another question - when got_time_zone ended up false, did it return the UTF-8 time zone name correctly as a fallback?

OK, I think I finally got a proper fix in place. Rather than doing all of this conversion, I just spin up a thread and use SetThreadUILanguage to ensure the returned time zone name is compatible with the IANA conversion library.
Could you grab the latest version of the branch and give it a try?

Thanks @jonsimantov, works great now!
I actually just now remembered that I implemented the same a while ago, but instead of spawning another thread I just set the thread language temporarily – maybe that’s a simpler/faster option? Sorry I did’t remember that earlier...

Thanks so much for the help, @triplef! The change has been merged in, and will be included in the upcoming release of the Firebase C++ SDK (11.3.0) and the Firebase Unity SDK (11.3.0). Closing this bug for now, but feel free to reopen if it happens again.

authors: jonsimantov triplef

repo: firebase/firebase-cpp-sdk


text:
Non-portable path warnings from Protobuf pod

Please update for Swift 5 support.
Thanks!

@OkiRules Thank you for your request. For most of the components Swift 5 should be supported now. Would you be able to provide examples of the issues you have with Swift 5, please?

This is an Apple issue tracked at https://openradar.appspot.com/radar?id=6091887509241856. More discussion at https://github.com/protocolbuffers/protobuf/issues/3218.
We can investigate if we can find any better workarounds. In the meantime, it's safe to ignore the warnings.

I'm going to change the title since the issue is not related to Swift 5.

One workaround is adding pod 'Protobuf', :inhibit_warnings => true to the Podfile.

Sent https://github.com/protocolbuffers/protobuf/pull/6190

It worked, it was enough to change the letter of the folder: Pods/Protobuf/objectivec/google/protobuf  (protobuf -> Protobuf)

protocolbuffers/protobuf#6464 in progress to fix

I'm trying to install 'Firebase/Messaging' it install protobuf etc. I'm using swift 5, deployment ios 11 and i have this issues:

I've tried (cmd + shift + k) delete derived data, pod install, pod update, nothing solved this issue.
Any help?

@devkokodev That looks like a different issue. Perhaps, something in the configuration?  We'll likely need more information about reproducing to help. Please open another issue with that detail.

So, now that the PR in cocoapods is merged... all that is needed is to update the protobuf lib in this repository?
As far as I can tel https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseMessaging.podspec#L52 is the current version, right? As the version differences are not so small, I image it should be with care. @paulb777 this is something in your radar, right?

@BugsBunnyBR A new Protobuf version with that PR needs to be published to CocoaPods. Please enquire in the Protobuf repo about their release plans.  Firebase will automatically pick up a subsequent Protobuf minor release on a pod update.

I thought is was in this release https://github.com/protocolbuffers/protobuf/releases/tag/v3.9.1, but is looks like it is not here yet. Sorry for the misunderstanding.

protocolbuffers/protobuf#6464 in progress to fix

Thank You!! this worked

It worked, it was enough to change the letter of the folder: Pods/Protobuf/objectivec/google/protobuf (protobuf -> Protobuf)

thank you!!! this fixed it.

@OkiRules did you resolved this "Non-portable path warnings from Protobuf pod."
your help is much appreciated.

Not yet as the new build has not been updated for Cocoapods but when it is will inform you.

@OkiRules Thanks for the quick reply..

I think protocolbuffers released a version with the fix
https://github.com/protocolbuffers/protobuf/releases
Can someone take a look at the update process ?

@BugsBunnyBR The fix won't come until Protocol buffers releases 3.10.0.  3.9.2 was a single patch to 3.9.0 fix a crash issue (#3851).

Ohh... I looked for the 6464 PR merge tag and it was in a release... but it was  for version for 3.10 RC1, I should more attention.

Protobuf 3.10.0 has been published to CocoaPods. Doing some additional Firebase integration testing today.

authors: BugsBunnyBR OkiRules devkokodev iatman maksymmalyhin navingp paulb777 psyduck-scar4

repo: firebase/firebase-ios-sdk


text:
InstanceID unit test flake

A second InstanceID test flake logged on travis today in https://travis-ci.org/firebase/firebase-ios-sdk/jobs/536525223
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/InstanceID/Tests/FIRInstanceIDKeyPairStoreTest.m:144: error: -[FIRInstanceIDKeyPairStoreTest testResetIdentity] : Asynchronous wait failed: Exceeded timeout of 5 seconds, with unfulfilled expectations: "Identity should be reset".

This doesn't seem to be coming up any more.


text:
Manually created dynamic links should be subject to allowed/blocked check

Description: Dynamic links can be validated against a block/allow list, which is defined server side in the Firebase Console. This verification should apply to both short and long dynamic links, and be supported by both iOS and Android SDKs.
What’s expected: It’s expected that both iOS and Android will verify both kinds of dynamic link, and if it passes the verification rules defined server side, allow the link to be processed.
What’s observed: On iOS, long dynamic links are not verified, and it’s possible for a link that doesn’t pass the "allowed link" rules to be treated as verified. Short dynamic links are verified, that’s not an issue. This also isn’t an issue on Android, which verifies both short and long dynamic links.
Proposed solution: Ensure the error response from reopenAttribution (which contains information to whether the link was verified or not), should be propagated further up for long dynamic links, so the appropriate decision on whether it’s a verified link can be made. Some method definitions have changed as well to accommodate this, which have now made them asynchronous.

According to the source code all short links are checked when a call to FIRDynamicLinkNetworking class method resolveShortLink:completion: takes place. This method does a HTTP call to reopenAttribution endpoint and receives a response with an error, if the URL is not allowed. The problem is that the same is not true for long dynamic links (aka manually created links) - no call to resolveShortLink:completion: method (or its long links counterpart) is done. Thus all URLs are accepted and considered allowed.
Another part of the problem is that when a call to reopenAttribution endpoint is done the response with the error description is ignored and and error equal to nil is passed to completion callback. Thus, all traces of the issue (the URL being not allowed) are lost.

@palexsua Thanks for the comprehensive PR!  We'll do our best to get a review soon, although it may be a challenge in the very near term with WWDC next week.
One initial question: Is there a way to make the asynchronous API additive instead of breaking? Changing the current API will require holding off on merging this until the next major release.

@palexsua Thanks for the comprehensive PR! We'll do our best to get a review soon, although it may be a challenge in the very near term with WWDC next week.
One initial question: Is there a way to make the asynchronous API additive instead of breaking? Changing the current API will require holding off on merging this until the next major release.

@paulb777 Thank you! I think I can make the asynchronous API additive. Do you want me to open a new PR or update the existing?

@paulb777 @eldhosembabu any update on these changes?

@ncooke3 Thanks for the comments! I'll have a look later today. I've also pushed one more commit as @paulb777 requested for additive changes.

@ncooke3 Addressed your review comments in https://github.com/firebase/firebase-ios-sdk/pull/5853/commits/0c20e3bb6148a8dbd24a4712117ffbd2f4e14c93. Thanks!

@ryanwilson I guess after I've made the changes additive public-api-change label is not relevant anymore, isn't it?

@palexsua Thanks for refactoring. It's still an API change. It's now no longer an API break so we can potentially merge this for a minor update release instead of waiting for the next rarer major release.
The API change will still need an internal API review. cc: @christibbs, @ncooke3

@paulb777 Got it. Thanks!

@palexsua Thanks for refactoring. It's still an API change. It's now no longer an API break so we can potentially merge this for a minor update release instead of waiting for the next rarer major release.
The API change will still need an internal API review. cc: @christibbs, @ncooke3

Thanks for the work @palexsua. I'll kick off the internal API review with @eldhosembabu.

hi @palexsua sorry for reviewing the code late from my side. I've left a few code review comments. Please let me know if you have any questions .

@eldhosembabu Thank you for your review comments! I appreciate. I've pushed the changes and replied to your comments. Please, have a look.

Update from my end: we've kicked off the internal Firebase API review process.

@eldhosembabu @christibbs any update? please, let me know, if any changes are required.

hi @palexsua now we are on our way towards the api review where the new proposed api needs to be approved by the api council...it would take O(weeks) time to get the approval..If we are not getting followup questions, we should get it approved in a week or two. After that we should be able to merge this PR if its all good.

@eldhosembabu Got it. Thank you for the update!

@eldhosembabu @christibbs guys, any update?

@eldhosembabu @christibbs guys, any update?

We're working on the API change approval right now. Thanks for your patience.

@eldhosembabu @christibbs guys, any update?

@eldhosembabu @christibbs guys, any update?

@paulb777 @eldhosembabu @ncooke3 guys, let's merge this PR.

Would also love to see this get merged, if it's ready to go.

Hey @palexsua @sbaruth. Really sorry for the delay. We will prioritize this and get through API review this week.

@christibbs Thanks for taking care of it! Looking forward to hearing the API review verdict ;)

One additional thing: could you provide an example of if/how you're using the new dynamicLinkFromUniversalLinkURL:completion: method in your app?
Is it similar to #6 here? Returning synchronously from application:continueUserActivity:restorationHandler: but using the completion for a side effect?

@christibbs Actually, we do not call dynamicLinkFromUniversalLinkURL:completion: directly in our app, but we rely on code that uses it. The issue I observed was that long dynamic links bypassed any sort of verification and when I traced back the issue I ended up seeing that response from reopenAttribution endpoint was not being "waited for". So, the gist of the proposed fix is to wait for the response and pass allowed/blocked status via completion callback.

@palexsua We got the API approval! @eldhosembabu had one outstanding issue with the implementation, but we can merge once that's resolved.

@christibbs I've addressed the change suggested by @eldhosembabu.

@paulb777 Afaiu, the open callback question is resolved, isn't it? So, now it's only a matter of updating the changelog?

@palexsua Agreed. Sorry about the confusion. I'll merge it here and we can follow up on the changelog separately.

@palexsua Thanks for your patience. And congrats: now you are a Firebase contributor!

@christibbs Thank you! It feels great! 🥇

authors: christibbs eldhosembabu palexs palexsua paulb777 sbaruth


text:
fix(firestore, windows): fix compilation issue on Windows

Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
closes #12359
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (melos run analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

Thanks it works, i tried your changes locally and worked on the example app testing on my app now

@russellwheatley or @exaby73 can someone approve and merge those please we're severely blocked and we need to have a release soon

This fixes the issue on windows. I can confirm.

@Lyokone How long usually PR stay until it gets merged?

@russellwheatley that's what I'm saying, it's not merged to master yet.
or do you mean depend on the fix branch?

Issue fixed.Thank You

authors: Aravind556 BirjuVachhani Lyokone SPiercer

repo: firebase/flutterfire


text:
Broken Firebase Authentication

Description
I am using the latest version of Polymer. I am a new user to Polymer, but it appears like even the most basic of firebase-auth elements will completely break. Any direction or help would be great.
Steps to reproduce

Setup a basic authentication template. Here the one I was using (nesting inside of the 'src' folder).

Serve the database using polymer serve.

Press the button

You will get an error that reads: Uncaught TypeError: Cannot read property 'signInWithPopup' of undefined

The error occurs on line 184 of firebase-auth.html which reads return this._attemptProviderSignIn(this._normalizeProvider(provider), this.auth.signInWithPopup);. Specifically, the error is occuring on this.auth.signInWithPopup
Browsers Affected

[x] Chrome
[ ] Firefox
[ ] Safari 9
[ ] Safari 8
[ ] Safari 7
[ ] Edge
[ ] IE 11
[ ] IE 10

@RoseReatherford firebase-auth is missing "app-name" attribute which should be "app"  that you have defined in firebase-app otherwise firebase-auth will use "default" as app-name for firebase config which is not defined.

@tjmonsi I am just using that as an example. I had my actual values defined, yes.
@khammami I tried doing that and that still receives the same error. Just now, I also tried changing the firebase-app to a name equal to "default" out of curiosity and this resulted in the same error.

@RoseReatherford  just remove app from firebase-app & app-name from friebase-auth
you have malformed attributes on firebase-app (it looks like you have copied web setup from firebase console as is it). here the correct one
<firebase-app
                api-key="[key]"
                auth-domain= "[domain]"
                database-url= "[url]"
                storage-bucket= "[storage]"
                messaging-sender-id= "[id]">
</firebase-app>

https://www.webcomponents.org/element/firebase/polymerfire/elements/firebase-auth

Lemme try it again this week but given my workload, I can't promise :(

Got the same issue with only Chrome Canary
Everything seam fine for IE, Edge, Firebase and Chrome.
Every now and then Chrome Canary behave weirdly, so maybe it's not 'Polymerfire' related.

authors: JoelCode RoseReatherford khammami tjmonsi

repo: firebase/polymerfire


text:
Uncaught FirebaseError: Messaging: This method is available in a Window context. (messaging/only-available-in-window).

i want to use messaging.onMessage(function(payload) {
console.log("Message received. ", payload);
// ...
});
in service worker unable to use this getthing this error.
Uncaught FirebaseError: Messaging: This method is available in a Window context. (messaging/only-available-in-window).

You need to use this function in the client side javascript for your webapp(the one which registers serviceWorker and requests notification permission from the user). This will capture any push messages sent while your webapp is open in browser window and in focus. You should use this to update your webapp UI to respond to the message received. For service worker just initialise firebase messaging. It will handle any messages sent with the "notification:" payload by default.
For e.g below payload is handled by default if you just initialise firebase messaging in your registered serviceWorker
{"to": "dl*******************************************************************************************8********************************************ujj",
"notification":
{"title": "Portugal vs. Denmark",
"body":"5 to 1",
"icon":"https://media.where.com/sql.png"
}
}

i want notification click event on foreground

If you would like to display notifications you can do one of two

Use non persistent notifications
e.g. var notification = new Notification("Hi there!");
Get the service worker registration object(only if you are registering a sw other than the one supplied by default)
registrationobject.showNotification(notificationTitle,
notificationOptions);

I need foreground click event

navigator.serviceWorker.register('sw.js');
function showNotification() {
Notification.requestPermission(function(result) {
if (result === 'granted') {
navigator.serviceWorker.ready.then(function(registration) {
registration.showNotification('Vibration Sample', {
body: 'Buzz! Buzz!',
icon: '../images/touch/chrome-touch-icon-192x192.png',
vibrate: [200, 100, 200, 100, 200, 100, 200],
tag: 'vibration-sample'
});
});
}
});
}
I am using this function its working fine, just need foreground click event on this!  background click event working fine as well

You can try something like this
Notification.requestPermission().then(function(permission){
if(permission==="granted")
{
var notif=new Notification("Hi there!!"); // similiar format as sw.showNotification(). Check
//documentation
console.log("Hi");
notif.onclick = function(event) {
event.preventDefault(); // prevent the browser from focusing the Notification's tab
window.open('http://www.mozilla.org', '_blank');
}
}
});

thanks for the feedback :)
have already implemented this its works fine on desktop but
var notif=new Notification("Hi there!!"); is not supported in mob foreground ,
this is only supporting in both mob and desktop
Notification.requestPermission(function(result) {
if (result === 'granted') {
navigator.serviceWorker.ready.then(function(registration) {
registration.showNotification('Vibration Sample', {
body: 'Buzz! Buzz!',
icon: '../images/touch/chrome-touch-icon-192x192.png',
vibrate: [200, 100, 200, 100, 200, 100, 200],
tag: 'vibration-sample'
});
});
}
});
we will have to adjust foreground onclick notification along with this
any more feedback ?

Using new Notification() is not supported on mobile, instead you can only create notifications from a service worker.
If you want to display a notification from the web page, you need to do the following:
navigator.serviceWorker.ready.then((reg) => {
  reg.showNotification('Hello');
});

To then handle a notification click, you need to add an event listener to your service worker:
self.addEventListener('notificationclick', function(event) {
  const clickedNotification = event.notification;
  clickedNotification.close();

  // Do something as the result of the notification click
  const promiseChain = doSomething();
  event.waitUntil(promiseChain);
});

Learn more here: https://web-push-book.gauntface.com/chapter-05/03-notification-behaviour/#notification-click-event

navigator.serviceWorker.register('sw.js');
function showNotification() {
Notification.requestPermission(function(result) {
if (result === 'granted') {
navigator.serviceWorker.ready.then(function(registration) {
registration.showNotification('Vibration Sample', {
body: 'Buzz! Buzz!',
icon: '../images/touch/chrome-touch-icon-192x192.png',
vibrate: [200, 100, 200, 100, 200, 100, 200],
tag: 'vibration-sample'
});
});
}
});
}
I am using this function its working fine, just need foreground click event on this! background click event working fine as well

Can you provide your sample code..

authors: gauntface phalconjohy sidyyy911 vijayvargiyakhushboo

repo: firebase/quickstart-js


text:
Variation in features extracted by capa while uisng vivisect backend and capa IDA explorer

I've noticed that for a particular sample (70da6872b6b2da9ddc94d14b02302917), the no/type of features getting extracted by capa while using vivisect and capa explorer, are not same. there's some significant mismatch between the features extracted by above mentioned methods.

left:IDA capa explorer results right:extracted by capa using vivisect
For example, receive data on socket (3 matches) and send data on socket (3 matches) (on left) is not present in right screenshot.
Is this something expected? I don't know atm, if this occurring for other files too.

Capa relies on these analysis backends (IDA, vivisect, SMDA, ...) to identify functions, basic blocks, instructions, features, etc. If the backend engines disagree, then there's not too much that capa can do. If you can highlight a few samples with differing analysis, then we can triage why the backends differ and maybe supply patches to those engines to enhance their analysis. Otherwise, unfortunately, its not really in scope to fix this within capa (however, if there's an issue in how we extract from the backend engine, thats definitely a bug! please do share samples with differing analysis for this reason).

Yeah, I already mentioned the hash 70da6872b6b2da9ddc94d14b02302917

Is there any way to know how many features get extracted while running capa on IDA backend?

Also be aware that the standalone tool does some filtering to display less hits. In the example above send data is a "parent" rule for send data on socket so the latter does not get displayed, for example.
To get a feature count you can use scripts/show-featues.py in IDA or use the save feature in the plugin and inspect the resulting JSON.

Also be aware that the standalone tool does some filtering to display less hits. In the example above send data is a "parent" rule for send data on socket so the latter does not get displayed, for example.

I didn't notice that. Later, I ran capa -v <file>and  receive data on socket (3 matches), send data on socket (3 matches) were there with their parent one. But do we need to display the parent one while the children are already displayed both in IDA capa exlorer and terminal, while running capa from CLI with -v.

To get a feature count you can use scripts/show-featues.py in IDA or use the save feature in the plugin and inspect the resulting JSON.

Thanks!

I think this has been answered. Please reopen if you still have issues.

authors: mr-tz r0ny123 williballenthin

repo: fireeye/capa


text:
New feature: Instruction

Summary
Often we want to check for specific instructions and use the basic block scope for this.
Example from check for software breakpoints
  features:
    - and:
      - basic block:
        - and:
          - mnemonic: cmp
          - or:
            - number: 0xCC
            - and:
              - number: 0xCD
              - number: 0x3
      - match: contain loop

I'm not sure if we need complete flexibility, but a way to provide variable operand values would be neat.
Examples:
- instruction: cmp <reg>, 0xCC
- instruction: cmp <mem>, 0xCC
- instruction: cmp <var = anything>, 0xCC

Key Instruction fields:

mnemomic
operands

reg/imm/mem
size
displacement

(prefixes) - optional

Or as a "subscope"?
- instruction:
  - mnemonic: cmp
  - operand1: 0xCC

We could then continue to support the mnemonic feature as an alias for the new instruction feature.
Motivation
An instruction scope would allow for more expressive and concise rules.
Downsides
More complexity for extractors and potential performance hits.

I would love to see this implemented. I'd prefer the subscope route as it would allow user's to easily specify environment specifics like the architecture.
- instruction:
  - arch: i386
  - mnemonic: cmp
  - operand1: eax
  - operand2: ecx

This does sound useful.
I think this will negatively affect performance; however, this is not a good reason to reduce the expressivity of capa. It just lends further support to #602 to investigate better matching algorithms.

the grap tool has a mini-language for declaring patterns of instructions like this. if it makes sense we could try to reuse terms from that project. note, i'm not aware of a large corpus of grap rules, so there's probably not a huge overlap/reuse argument to be made here.
https://github.com/QuoSecGmbH/grap/

can we build out some examples of rules we'd want this feature/scope for? lets list them in this thread.
why? i'm having a little trouble thinking about which features we need/don't need. e.g., do we need to name the registers? can we get by with the existing features (mnemonic, number, offset, arch)?

Just some examples from existing rules where this would be helpful.
      - basic block:
        - and:
          - mnemonic: and
          - number: 0x2 = KdDebuggerNotPresent
      - basic block:
        - and:
          - mnemonic: and
          - number: 0x1 = KdDebuggerEnabled

- and:
              - mnemonic: add
              - or:
                - number/x32: 0x68 = PEB.NtGlobalFlag
                - number/x64: 0xBC = PEB.NtGlobalFlag

- basic block:
          - and:
            - mnemonic: cmp
            - number: 0x5E = '^' (Track 1 separator)
        - basic block:
          - and:
            - mnemonic: cmp
            - number: 0x3D = '=' (Track 2 separator)
        - basic block:
          - and:
            - mnemonic: cmp
            - number: 0x25 = '%' (Track 1 start sentinel)
        - basic block:
          - and:
            - mnemonic: cmp
            - number: 0x42 = 'B' (Format code)
        - basic block:
          - and:
            - mnemonic: cmp
            - number: 0x44 = 'D' (Format code)
        - basic block:
          - and:
            - mnemonic: cmp
            - number: 0x3F = '?' (Track 1 & 2 end sentinel)
        - basic block:
          - and:
            - mnemonic: cmp
            - number: 0x3B = ';' (Track 2 start sentinel)

- basic block:
        - and:
          - or:
            - mnemonic: cmp
            - mnemonic: test
          - or:
            - number: 200 = OK
            - number: 400 = Bad Request
            - number: 401 = Unauthorized
            - number: 403 = Forbidden
            - number: 404 = Not Found

            - and:
              - number: 0xFFFF000F = -65521
              - mnemonic: add
            - and:
              - number: 0xFFF1 = 65521
              - mnemonic: sub

      - basic block:
        - and:
          - mnemonic: cmp
          - number: 32000
      - basic block:
        - and:
          - mnemonic: cmp
          - or:
            - number: 127
            - number: 128

We should think of additional useful feature (combinations) we may not be able to express currently with our rules.
Initially, I like the idea of using the existing features.

authors: mike-hunhoff mr-tz williballenthin


text:
Rules apply only to Firezone's wireguard interface

Fixes #896
One easy performance improvement would be to match against interface index instead of name. I didn't do it since I don't think we take a big performance hit and in case someone deletes and recreate Firezone's interface without using reconfigure

Pull Request Test Coverage Report for Build 9b281871739e8db50ca243970f48ff95163880c4-PR-901

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 67.479%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

apps/fz_wall/lib/fz_wall/cli/helpers/nft.ex
0
3
0.0%

Totals

Change from base Build 4d73df77bce407d9fbfb539d045288f6c6922c16:
-0.04%

Covered Lines:
1052

Relevant Lines:
1559

💛  - Coveralls

authors: conectado coveralls

repo: firezone/firezone


text:
General strategy for processing control panel color info

Determine a general approach to identify the control panel color wheel, and information about its current color.  That might be some kind of angle, or just the current selected color.  It'd also be really great to be able to detect the rate at which the control panel color wheel is turning.

Here is my current strategy:
High-level:

Camera is aimed to look up at the control panel
Find the region inside the inner ring of the lazy susan
Find the 8 colored pie slices
Compute the angle of the color wheel from the relative locations of the pie slices

Example:

Based on input image:

Detailed plan:

Run HSV filter to find colorful parts of the image
Blur (to fill in dark lines from chromatic abberation)
Find blobs, with settings so it only finds the ellipse in the center of the lazy susan
Crop image to that area
For each color:

Run HSV filter to select the appropriate hue
Blur
Find blobs

At this point we should have 8 blobs representing all of the pie slices within the center of the lazy susan, two for each color.  However, it's possible there will be something visually in the way (such as glare or a scratch).
For each pair of colored blobs, compute angle of the line connecting them.  This will give us the azimuth angle of the control panel relative to the robot's heading.  Since we can only get a camera up under the control panel while the robot is relatively square to the front of the control panel, we can treat this as the azimuth angle of the control panel relative to the field.

A note: it appears dramatically faster to find and filter contours than blobs:

authors: jwalthour lindsayvallen


text:
Добавить проверку использования БСП

Везде где используются модули БСП переделать заглушку на проверку использования БСП, в случае неиспользования переводить на методы-аналоги и добавить их в общие модули

Добавил ветку

repo: firstBitSportivnaya/PSSL


text:
firstcontributions/assets#9

Copied media files for github-windows-vs2017-tutorial.

Thank you for working on this.
Please remove the assets for vscode and only keep the ones for vs2017

Closing this in favor of #15

authors: Roshanjossey sowmyaprasaad

repo: firstcontributions/assets


text:
tokenizer in fish_speech.datasets.text.AutoAugTextDataset

Great Project !!!
Reading the source code1 and  code2 I couldn't help but notice that the vocab_size of this tokenizer is only 264, I can't understand Why the vocab_size so small?  Where did this come from?  There seems to be no mention of it.
Thanks~

For some reason, we didn’t train a tokenizer on our corpus, but instead, using bytes only (0-255). This issue is fixed in v1.2 which will be released in next week. 😊

authors: GKCsdfsGKC leng-yue

repo: fishaudio/fish-speech


text:
Can we support flags that require no arguments?

https://github.com/fisherman/fisherman/issues/84

:+1:

The problem is, to implement this the user would need to teach getopts that such and such option does not require arguments. Getopts design is supposed to be minimalistic. I deliberately wanted to avoid using an optstring, but maybe we can have the best of both worlds.
I'll ponder deeply.

Closing as won't fix.

authors: bucaran pickfire

repo: fishery/getopts


text:
Hard code dispatch namespaces for fivetran_utils?

Picks up from #3363
The _get_utils_namespaces() macro in fivetran_utils (source) works just slightly differently from the other get-namespace macros: It includes dbt_utils, alongside itself, in the list of default packages to search in. So folks with Fivetran packages installed might see this error upon upgrading to 0.19.2 / 0.20.0:
Encountered an error:
Compilation Error
  In dispatch: No macro named 'datediff' found
      Searched for: 'fivetran_utils.snowflake__datediff', 'fivetran_utils.default__datediff'

The most straightforward fix for this is just to set this variable in their project, and everything will work as anticipated:
vars:
  fivetran_utils_dispatch_list: ['dbt_utils']

This is closer to the syntax that users will need to have going forward:
dispatch:
  - macro_namespace: fivetran_utils
    search_order: ['dbt_utils', 'fivetran_utils']

At the same time, I want to take backwards compatibility really seriously, since this is otherwise a breaking change in a patch release. So this PR would shamelessly hard code backwards compatibility for that specific behavior.
I don't much like this:dbt_utils isn't actually a dependency of fivetran_utils, so it's conceivable that this might raise an error if dbt_utils isn't installed alongside it. That's true parity with current behavior, though.
I could really go either way on this one!

[skip cii]

🤦 Well, it was worth a shot. Bound to happen anyway given the rebase.

repo: fishtown-analytics/dbt


text:
How to get selected chips list

Hi,
How to get selected chips list? Am I need to maintain a list separately? In that list add  selected chips?

Yes. there seems to be some confusion about how this library is intended to be used, it's strictly a UI tool, you build the display chips from some array - then you use chipSelected and chipDeselected to update your model. You shouldn't expect a UI component like this to keep track of your app state.

Added a convenience method to do this:
Integer[] selectedChips = chipCloud.getSelectedIndexes();
for(Integer i : selectedChips){
  Log.d(TAG, "Selected chip: " + i);
}

Heyy @fiskurgit, I couldn't find the below method which you have said you have added in the library since v2.2.2 !!
chipCloud.getSelectedIndexes();

Could you please help me.

My solution：
`public class TagCloudView extends ChipCloud {
private ViewGroup layout;
public TagCloudView(Context context, ViewGroup layout, ChipCloudConfig config) {
    super(context, layout, config);
    this.layout = layout;
}

public List<Integer> getSelectedTagIndex() {
    List<Integer> index = new ArrayList<>();
    for (int i = 0; i < layout.getChildCount(); i++) {
        ToggleChip chip = (ToggleChip) this.layout.getChildAt(i);
        if (chip.isChecked()) {
            index.add(i);
        }
    }
    return index;
}

private int getIndexByView(View view) {
    for (int i = 0; i < layout.getChildCount(); i++) {
        View child = this.layout.getChildAt(i);
        if (child == view) {
            return i;
        }
    }
    return -1;
}

private boolean keepLastOneCheck(View view) {
    List<Integer> selectedTagIndex = getSelectedTagIndex();
    return !(selectedTagIndex.size() == 1 && selectedTagIndex.contains(getIndexByView(view)));
}

@Override
public void onClick(View view) {
    if (!keepLastOneCheck(view)) {
        return;
    }
    super.onClick(view);
}

}`

Good workaround :)

authors: RahulSDeshpande fiskurgit john990 prashanthd

repo: fiskurgit/ChipCloud


text:
Data streams and repository access via Fission?

I was reading the doc page on  data but I am not sure to what extent Fission supports:

data streams as input and/or output to fission functions
access to data repositories from within a fission function.

Regarding 2., read access will be mandatory, write access would be great as well. I know that write access makes it a stateful function - but is there anything that breaks Fission if a fission functions actually changes data in a repository?

Hi Thomas 🙂
Just to answer your questions:

data streams as input and/or output to fission functions

I don't quite see the use case data streams within a function. Could you give an example of how you plan to use this?
The common use case of serverless platforms is to chop up the data streams into independent events using a message queue, and execute functions for each event separately. Similarly for output, functions could publish (multiple) events.

access to data repositories from within a fission function.

The (non)-statefulness of a function is not a concern of the Workflow engine; it uses the same (public) interface to Fission functions as you would use when invoking a Fission function yourself. So this question would better fit the Fission Repo.
However, to answer your question. You can augment how the Fission environment is deployed in various ways. One way to introduce (stateful) data repositories is to add Kubernetes volumes to the container parameter of the environment specification: https://github.com/fission/fission/blob/master/pkg/apis/fission.io/v1/typefields.go#L221
This should allow you to attach arbitrary ro and rw volumes to functions.

HI Erwin,

Think of a data stream coming from an IoT device. You have no influence on this stream but have to take it as is. Assume it generates micro data - one after the other. Processing these data by a function is less expensive than invoking a Fission function. then you have a serious performance problem. The only way to deal with such a stream is if you manage to aggregate stream elements into chunks of n elements which are then processed by a Fission function. The Fission function of course has to be written such that it can take n elements. How would you code up such a streaming example in a performance efficient manner with fission?

what is fission repo?
If a fission function actually writes to a data repository within the function then I have state. In case it crashes, what should I do then not knowing whether the write operation was successful?

Kubernetes volume is no good because it will be too expensive in terms of performance. better would be to get access to a truly outside data respository such as IPFS which is independent of Kubernetes. I dont know whether this is possible with Fission.

one more question on stateful functions. If I use stateful functions how can I epxress parallelism to let the fission engine know that even so a function writes data to an outside repository it can still execute the function in parallel with other functions?

Hi @tfahringer - I am closing this issue, since there is no specific issue. Feel free to keep commenting, I'll keep watching this issue. :)

authors: erwinvaneyk tfahringer

repo: fission/fission-workflows


text:
require_loginを追加

ログイン要求がされていないため。
/pages
/questions
connected #192

@komagata レビューお願いしますー。

@hattori6789 すごい!!
自分も確認したところ/usersも怪しいです。
users_controllerで
before_action :require_login, only: %w[edit update destroy]
↓
before_action :require_login, only: %w[index edit update destroy]

にしてログイン画面に飛ばした方が良いのか、表示させた方が良いのか気になります。

@Hirotacas 確かusersは以前からログインせずに見られるようになっていました！
旧デザイン

@komagata ログイン要求かけた方が良いでしょうか？

新デザイン/usersがWe're sorry, but something went wrong.になっていますね。

@komagata ありがとうございます。このPR/usersはログイン要求かかってないです。この場合別でPRした方が良いですか？
レビュー依頼後に[WIP]にせずにコメント続けてしまってました、すみませんー。

/pagesと/questionsしかログイン要求していないです。

@hattori6789 では他もお願いできるとありがたいです。

@komagata 承知しました！

authors: Hirotacas hattori6789 komagata

repo: fjordllc/interns


text:
:rocket: 6D-Pose estimation added

:rocket: 6D-Pose estimation added

:rocket: 6D-Pose estimation added

repo: fkenghagho/RobotVQA