chromium: 74.0.3729.157 -> 75.0.3770.80

Motivation for this change
https://chromereleases.googleblog.com/2019/06/stable-channel-update-for-desktop.html
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Tested stable on x86_64: YouTube, WebGL, audio, Speedometer, Octane 2.0 are working
Tested dev on x86_64: YouTube, WebGL, audio are working
Not seeing any severe Linux bugs listed on https://crbug.com

Updated with test results, please merge.

@ivan can you prepare the backport PR for this?

@andir #62745 prepared but untested


Error 8 when sending with p12 certificate. No problem with pem.

I have an app that is working fine using PEM key and certificate. I want to use the p12 directly to avoid having to run openssl to get the PEM key and certificate out of it so I simply changed my options to this:
var apnOptions = {
    pfx: p12Filename,
    production: !sandbox
};

var apnConnection = new apn.Connection(apnOptions);

It looks like the connections are being opened and the push notifications being sent but the outcome is that it's always error 8, no matter if using a development or production certificate. The weird thing is that the PEM key and cert were created from that same P12 files (both production and development) that I'm using for this test.
Any clue at what might be wrong?

So, using the p12 file and the above mentioned syntax works?


Feat/new launch mode

New launch modes and session types

@hpohekar please can you approve this.  cc: @prmukherj

@prmukherj Hi Prithwish - Using this "feat/new_launch_mode" branch, I ran some meshing and solver mode regressions using the old launch method via FLUTE. They are running fine as you are maintaining the backward compatibility.
To use the new launch modes via FLUTE - I will start an email discussion with you and @seanpearsonuk .


Rendering issues on android when navigating

Hey, I'm pretty new to nativescript and I've tried to use the nativescript-pager in one of my apps. I'm currently facing an issues on android with the latest version. I'm using angular and have the following navigation structure:

app (containing a side drawer)

home

overview (containing the pager)
other page

details

On the /home/overview page five items are shown within a nativescript-pager using an angular template for rendering. When selecting an item the /details page is opened via RouterExtensions. When navigating back to /home/overview page and swiping through the pager, the items on the first and last index are not rendered anymore. The general behavior indicates a recycling issues on the underlying android PagerView.
When navigating to another page within /home and back to /home/overview the pager works as expected again.
I couldn't reproduce the error on the emulator but only on physical devices. It happens with version 9.3.7 and after, before that it seems to work properly.
Versions

NativeScript: 5.2.0
Angular: 7.2.7
Plugin: nativescript-pager @ 9.3.15
Devices:

Moto Z Play (Android 8.0.0)
Samsung Galaxy Tab A (Android 8.1.0)

Sample repo
I created a sample project from the default angular / SideDrawer template:
https://github.com/nilshohmann/NativeScriptPagerIssue
To reproduce the error just tap on any of the items in the pager to open the details page. Then navigate back and swipe through the pager items. The items at index 0 and 4 are now missing. When navigating to the settings page (via the side drawer) and back to the items page all items are rendered again.

@triniwiz Still an issue

@sifex what type of array are you using ?

@triniwiz No array, static templating on NS Vue


MVVM tutorial missing building blocks for mapping the VM

Making data binding to the values of sibling components is much less common than binding to a VM derived from a model. This tutorial contains no example of generating a VM from a model (without default properties) and do not serve as building blocks to get to that point. Since in a real world application data should be loaded from somewhere, mapped to a VM, and then displayed, this misdirect adds an unnecessary roadblock. Nobody finishing this will be able to take the next step in the MVVM process.
Providing an example of mapping a VM from another data source, which I assume would need to be done in the code-behind, is a much more important building block than the first 2 examples. I recommended replacing them with that kind of example or making a clear progression to another tutorial that focuses on it.

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

ID: 9905cd00-f3a1-7bdd-d678-ef6c71fb53b7
Version Independent ID: 9905cd00-f3a1-7bdd-d678-ef6c71fb53b7
Content: Data binding and MVVM - .NET MAUI
Content Source: docs/xaml/fundamentals/mvvm.md
Product: dotnet-mobile
Technology: dotnet-maui
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @cabbruzzese
It's a fair comment. We actually have a completely separate tutorial on MVVM - https://learn.microsoft.com/en-us/dotnet/maui/tutorials/notes-mvvm/
The doc you saw should link to the tutorial. There's also https://learn.microsoft.com/en-us/dotnet/architecture/maui/ for more content about MVVM.


[fix] fix keystore index regression

My previous PR #48, broke the index, because I mistakenly used return instead of continue. This PR fixes that.
This was an obvious mistake from my part, sorry 😅

my fault as well; hasnt been published yet, thanks for fixing.


Add Skip.SetTestPipelineVersion

Add Skip.SetTestPipelineVersion to allow overiding the SetTestPipelineVersion step for template pipelines.
Resolves https://github.com/Azure/azure-sdk-tools/issues/1664

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


Tweak MANIFEST.in

I think we should decide what the source distribution should contains. There are basically two options:

All files required to install the package
All files under source control

Currently, we're mixing these things, because we're including e.g. .github/ and readthedocs.yml, but not mkdocs.yml or docs/. WDYT?

OK, I'd also prefer this behavior. I'll submit a PR.


Organise scripts

seems like we get a build fail?

<EMAIL_ADDRESS>test /home/travis/build/me-box/databox
./node_modules/mocha/bin/mocha
sh: 1: ./node_modules/mocha/bin/mocha: not found
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.
Done. Your build exited with 1.

Looks unrelated to this pr to me but I'll check it out shortly. I'll try
and look into the Travis setup today too. Has a chat with @toshbrown
yesterday too and he was also going to.
On 21 Sep 2017 00:05, "Hamed Haddadi"<EMAIL_ADDRESS>wrote:

seems like we get a build fail?
<EMAIL_ADDRESS>test /home/travis/build/me-box/databox
./node_modules/mocha/bin/mocha
sh: 1: ./node_modules/mocha/bin/mocha: not found
npm ERR! Test failed. See above for more details.
The command "npm test" exited with 1.
Done. Your build exited with 1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/me-box/databox/pull/91#issuecomment-331005250, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKP4A1nTyD39g8ci7SJ2UiTOG3I6iXfks5skZopgaJpZM4PehnX
.

Yep, I'm working on testing so enabled Travis. This is not a problem merging.


Start working on the fathers page

Philip Schaff 38 Volume set has been compiled into json form and ready to be sent to the Database

Church fathers is up and running for the time being

More fixes were made to the church fathers page


Does MFEM support any higher oder (p>1) nonconforming finite element space on conforming 2D triangular mesh?

Hello @cuiyu-he, could you clarify what you mean by a nonconforming space on a conforming mesh?

Hi, Nonconforming finite element space is a special type of finite element
space. For example, The first order nonconforming FE space is CR space.
Conforming mesh means there’s is no hanging nodes in the mesh.
On Tue, May 3, 2022 at 7:50 PM Will Pazner @.***> wrote:

Hello @cuiyu-he https://github.com/cuiyu-he, could you clarify what you
mean by a nonconforming space on a conforming mesh?
—
Reply to this email directly, view it on GitHub
https://github.com/mfem/mfem/issues/2994#issuecomment-1116767739, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4FYY73ZR3B6LHVJWLJOQTVIG3T7ANCNFSM5VADRSTA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best,
Cuiyu

MFEM supports low-order Crouzeix-Raviart elements, but not their higher-order generalizations. MFEM does have fairly comprehensive DG support, which can be viewed as a nonconforming finite elements, but I am assuming you are not referring to DG.

Hi Pazner, thanks for the clarification. Could MFEM group possibly consider adding higher order non-conforming FE space into the library? For example, the specific type introduced in "Matthies, G., Tobiska, L. Inf-sup stable non-conforming finite elements of arbitrary order on triangles. Numer. Math. 102, 293–309 (2005). https://doi.org/10.1007/s00211-005-0648-8". Many thanks!

Hi, Cuiyu,
We are always interested in adding useful features like this. If you know of a student, or some other colleague, who could invest the time in this I'm sure we would be happy to offer any advice or guidance on the MFEM specific issues.
Best wishes,
Mark

Dear Mark,
Thanks! Unfortunately, I currently do not have a student or other person in
mind that could help. However, if I have time this summer, I would be happy
to help. Of course, any help from the MFEM team is greatly appreciated.
Best,
Cuiyu
On Tue, May 17, 2022 at 3:08 PM Mark L. Stowell @.***>
wrote:

Hi, Cuiyu,
We are always interested in adding useful features like this. If you know
of a student, or some other colleague, who could invest the time in this
I'm sure we would be happy to offer any advice or guidance on the MFEM
specific issues.
Best wishes,
Mark
—
Reply to this email directly, view it on GitHub
https://github.com/mfem/mfem/issues/2994#issuecomment-1129220922, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4FYY7ZZBCT7VARFZUMZRLVKPVCLANCNFSM5VADRSTA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok. Thanks! I will submit a pull request. Since probably other FEM
libraries also do not have higher order nonconforming FEM (If you know
there is any, please kindly let me know!), it would be a plus for MFEM :).
Besides, the implementation should be relatively simple, from my point of
view, given the smart design of the basis functions. So I really hope your
team could consider it. :) Many thanks!
On Wed, May 4, 2022 at 10:43 AM Will Pazner @.***>
wrote:

I think if such a feature were proposed in a pull request, the team would
be happy to review it. I don't believe a feature like this is currently on
the roadmap.
—
Reply to this email directly, view it on GitHub
https://github.com/mfem/mfem/issues/2994#issuecomment-1117408280, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4FYY7UX6ZTC62J7G3KO5TVIKEIVANCNFSM5VADRSTA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Best,
Cuiyu

Hi Tzanio,
Good to hear from you too! I would love to help and will start working on
it soon.  Will reach back to your team for technical help!
Many Thanks again for the quick responses!
Best,
Cuiyu
On Wed, May 4, 2022 at 10:56 AM Tzanio Kolev @.***>
wrote:

Hi @cuiyu-he https://github.com/cuiyu-he, good to hear from you!
As Will said, this is not on our roadmap because our applications don't
seem to need it, but it will certainly be good to have it. (I am also
partial
https://onlinelibrary.wiley.com/doi/10.1002/(SICI)1099-1506(199910/11)6:7<533::AID-NLA175>3.0.CO;2-7
to non-conforming elements 😄)
We will put it on our todo list, but if someone in the MFEM community can
help that will be appreciated.
Tzanio
—
Reply to this email directly, view it on GitHub
https://github.com/mfem/mfem/issues/2994#issuecomment-1117426905, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4FYYYACBS2AKYF5CRM45LVIKF3VANCNFSM5VADRSTA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add Security Feature tests

a) Ensure virt-launcher pod securityContext type is
virt_launcher.process
b) Make sure the virt-launcher pod is not priviledged.
Signed-off-by: Kedar Bidarkar<EMAIL_ADDRESS>
What this PR does / why we need it: Add test-cases related to security-features
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/retest

/lgtm
/approve

/retest


Track how far each team is on scoreboard

On scoreboard show nE nM nH for easy med hard
Would have to track the current page of the difficulty-level being done by the scorer.

How to do this:
Forward button is enabled if current is not x.
X is enabled if next is x.
Count up from the bottom.

Closed by 3532dee2.


Add information for all included algorithms or techniques.

This pull request provides the information for all algorithms included in this project, placed in the new ALL_ALGORITHMS folder (rename if doesn't seem good). As requested in #2, the readmes follow the same structure of Overview->How it works->How the code works. Let me know if something doesn't seem alright!

I reviewed your request. The documentation is excellent, yet these are the suggested modifications:

Use the directory of the algorithm itself rather than creating an ALL_ALGORITHMS directory.
In case of the absence of an algorithm directory, like in shift, substitution, and viginere cipher; create the directory and then add a markdown file in it.

Thank you for your contribution.

Thank you for your review! I moved the files to their respective directories and created three more for the algorithms that don't yet have a dedicated directory, I hope this suits your preferences!


Added new Sudoku Calculator

Fixes Issue🛠

Closes #1675
Description👨💻

Sudoku calculator which can calculate user given sudoku, generate new sudoku
Type of Change📄

[x] New feature (non-breaking change which adds functionality)

Checklist✅

[x] I am an Open Source contributor
[x] I have performed a self-review of my code
[x] My code follows the style guidelines of this project
[x] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

@vansh-codes Please add your calculator in main index file of project.

@vansh-codes Please add your calculator in main index file of project.

@Nihal4777 Sorry, I didnt get your point. Index file is already in the root folder
Heres the folder structure

Actually you should add your calculator in index file of project.

So that it appears on homepage.

Hii @Nihal4777
Actually I did some issues with branchs so now I am not able to add in this branch
I have one more PR, I have added this calculator to index.html in that PR
You can refer and merge that PR also: #1840
Thank you


add language scopes to atom language config gets

Atom's config is not fully supported at the moment. Config like the following is currently ignored:
"*":
  welcome:
    showOnStartup: false
  linter:
    lintOnChange: false
    clearOnChange: true
  core: {}
".shell.source":
  editor:
    tabLength: 4
".python.source":
  editor:
    tabLength: 4
".java.source":
  editor:
    tabLength: 4
".gfm.source":
  editor:
    showInvisibles: false
    softWrap: true
    tabLength: 4

atom-beautify currently ignores the language specific tabLength and other settings and uses the default tabLength of 2 in this case. This commit fixes that issue by specifying the scope in the language files.

I did not know that Atom had a language scope for those editor settings! This is excellent, thank you!

So I now realize that it was not just these languages that did not support this. If you would like I can try to expand support for this style of configuration to the other languages as well.

That would be great, thanks! This is definitely something I wanted to support, I just did not know that Atom had scoping for settings like this.

@tcl16 I am going to merge this now. Feel free to submit another Pull Request for those other languages you wish to add. Thank you for contributing!

Published to v0.28.9


Wall scroll changes color depending on the angle you look at it from

seems to be fixed in #503 ?


[Draft] Full rewrite

I was looking into doing this today, and I started writing the exact same module (down to the same name, hehe) so I figure I'd just fork & submit a PR instead of fragmenting npm unnecessarily. :smile:
Here is a draft, not complete. Some things:

filename is now required as the input for the transpiler, since that's what browserify transforms expect
opt.transform now matches the way browserify resolves and handles transforms. Currently uses resolve.sync since the async API would cause a lot more code complexity.
added subarg handling for --transform in CLI
added alias -t in CLI
added a small test; note the devDependencies have their versions pinned to reduce the chance that patches will break the tests
basedir can be specified from API/CLI to resolve differently
added standard linting, npmignore, and some tweaks to readme.

Something to still figure out is the general user-experience of the CLI/API, especially for whole directories (like babel does). I'm not sure whether vinyl-fs or something similar could help clean the code up.
Directories:
# Option A: input is a directory, like babel does
transpilify src -t brfs --out-dir dist/

# Option B: input is globs, output is resolved based on cwd
transpilify src/**/*.js -t brfs --out-dir dist/

Single-file:
# input is a single file, user wants to specify output file instead of piping
# same flag as babel
transpilify src/index.js -t brfs --out-file dist/index.js

# this will throw an error, expected --out-dir
transpilify src/**.js -t brfs --out-file dist/index.js

/cc @hughsk since this tool could be useful for glslify modules :smile:

hey @mattdesl, this is really great, thanks for your help. :)
code looks good to me. i gave you write access to this repo and the npm module, feel free to merge and publish when you feel it's complete.
i think your ideas for the CLI/API are great, i had something similar in mind last night but just wanted to get a minimum transpiler using browserify transforms pushed so we could start iterating.

regarding CLI/API: do we want to merge the browserify config from the package.json local to filename into our options? my initial feeling is yes.

I'm not sure if it's a good idea to merge package.json config, because:

This isn't applying transforms to node_modules (dependencies) which is where the browserify config is really important.
If you use transpilify on pre-publish then you don't need the package.json config "browserify" field on npm anymore. Having it there might lead to source being transformed twice (first by transpilify, then by browserify on bundle).

However something similar might be worth considering to allow users to setup config without long shell commands. :smile:
Pushed vinyl-fs which seem to handle a lot of the file streaming/copying for us. It is not part of the programmatic API but it seems like neither is Babel's multi-output option.

@mattdesl haha, I was thinking of suggesting we write up something like this earlier today :P Thanks for the heads up!
+1 on ignoring package.json transforms in this case, maybe transpilify.transform (or transforms) instead of browserify.transform might be a good place to put them instead? Would love it to become something as simple as what we have now for browserify transforms. I've tried setting up packages on npm that use babel but it always seems to add a lot of boilerplate and extra thought :(

:+1: transpilify.transform.
also @hughsk gave you write access as well just in case. :)

Ok, I am going to merge and continue iterating on master.


build climate project github pages using gridsome

clone to org incubaid_archive

[x] climate - gridsome

[x] build climate github pages @ehab-hassan

@sasha-astiadi Climate had a lot of errors when trying to run, I dont know if that go online before I think fixing the errors and try to run at Github pages ll waste time.

there is no data it just template website
GitHub page :
https://incubaid-archive.github.io/climate_archive/
repo :
https://github.com/incubaid-archive/climate_archive


Web Map "Elevation Test Maps" references services/layers that do not exist

Item id 9d4dc007131247db9cef7d3abb3aade9   references the following services/layers that do not exist:
https://nsec.esri.com/ags/rest/services/Hosted/SignificantEvents/FeatureServer/0
NOTE: this web map is referenced by the web mapping application 73b4fe7ed79345b9ba082128c266bd63   "Elevation Test Maps App".

Web map deleted.


make some changes

testing github actions

sorry, I made a PR against the wrong repo

@teikjun  Is this an effort to figure out why GitHub Actions is failing on the docs?

@pdimens Yes! I initially thought the issue was because actions@github was mispelled as actions@gihub. But after testing, i found that it wasn't the problem.
It seems like an issue with npm ci, but I'm still looking up how to resolve this

Ah, thank you. I wish I could be more help, but this is quite far out of my skillset. Are others experiencing this error as well?

It's the first reported issue. The documentation for GitHub Actions was added to Docusaurus just a month ago, so there hasn't been other reports yet.
I'm not familiar with how to fix this either, so I'll let my teammate handle it. Thanks for reporting the issue! :)


:warning: remove experimental gate from probe format

What kind of change does this PR introduce?
feature and breaking change

[X] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
--format probe is  gated behind SCORECARD_EXPERIMENTAL=1
What is the new behavior (if this is a feature change)?**

--format probe is no longer gated behind SCORECARD_EXPERIMENTAL=1

Also delete finding and structured results formats as they weren't used

[ ] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes
NONE (prepping for release)

Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

A new --format option "probe" is available.

I'm fine dropping this PR if you want to keep it gated still during the prerelease stage.


[webRTC / macOS] onPermissionRequest not called on HeadlessInAppWebView

[x] I have read the Get Started - Installation section
[x] I have read and done the Get Started - Setup Android section
[x] I have read and done the Get Started - Setup iOS section
[x]  I have read and done the Get Started - Setup macOS section
[x] I have already searched for the same problem
[x]  I have read and done the Get Started - Setup WebRTC on macOS section

Environment

Technology
Version

Flutter version
3.3.4

Plugin version
6.0.0-beta.8

Android version

iOS version
16.0

macOS version.
12.5.1.

Xcode version
14.0.1

Device information:
MacBook Air x86 with macOS Monterey 12.5.1
Description
Expected behavior:
Using HeadlessInAppWebView when I call the javascript snippet:
navigator.mediaDevices.getUserMedia({audio:true}).then((e)=>console.log(e)).catch((e)=>console.log(e))
whether inside a loded page, or by calling headlessWebView.webViewController.evaluateJavascript in my dart code, then I expect to enter the then or the catch clause of my javascript promise.
Current behavior:
instead I get the message:
JavaScript execution returned a result of an unsupported type
I have tested the same code on an iPhone simulator and it is working as intended.
Steps to reproduce

In the example app edit the code for class headless_inapp_webview.screen.dart
In the initState method add the onPermissionRequest callback

onPermissionRequest: (controller, request) async {
        return PermissionResponse(
            resources: request.resources,
            action: PermissionResponseAction.GRANT);
      },

Replace the javascript code in the button that evaluate javascript code by this:

await
headlessWebView?.webViewController.evaluateJavascript(
                        source:
                            """navigator.mediaDevices.getUserMedia({audio:true}).then((e)=>console.log(e)).catch((e)=>console.log(e));""");

Here is a sample of the class

import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';
import 'package:flutter_inappwebview/flutter_inappwebview.dart';

import 'main.dart';

class HeadlessInAppWebViewExampleScreen extends StatefulWidget {
  @override
  _HeadlessInAppWebViewExampleScreenState createState() =>
      new _HeadlessInAppWebViewExampleScreenState();
}

class _HeadlessInAppWebViewExampleScreenState
    extends State<HeadlessInAppWebViewExampleScreen> {
  HeadlessInAppWebView? headlessWebView;
  String url = "";

  @override
  void initState() {
    super.initState();

    var url = !kIsWeb
        ? Uri.parse("https://flutter.dev")
        : Uri.parse("http://localhost:${Uri.base.port}/page.html");

    headlessWebView = new HeadlessInAppWebView(
      initialUrlRequest: URLRequest(url: url),
      initialSettings: InAppWebViewSettings(),
      onWebViewCreated: (controller) {
        print('HeadlessInAppWebView created!');
      },
      onConsoleMessage: (controller, consoleMessage) {
        print("CONSOLE MESSAGE: " + consoleMessage.message);
      },
      onLoadStart: (controller, url) async {
        setState(() {
          this.url = url.toString();
        });
      },
      onLoadStop: (controller, url) async {
        setState(() {
          this.url = url.toString();
        });
      },
      onUpdateVisitedHistory: (controller, url, isReload) {
        setState(() {
          this.url = url.toString();
        });
      },
      onPermissionRequest: (controller, request) async {
        print(request);
        return PermissionResponse(
            resources: request.resources,
            action: PermissionResponseAction.GRANT);
      },
    );
  }

  @override
  void dispose() {
    super.dispose();
    headlessWebView?.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
            title: Text(
          "HeadlessInAppWebView",
        )),
        drawer: myDrawer(context: context),
        body: SafeArea(
            child: Column(children: <Widget>[
          Container(
            padding: EdgeInsets.all(20.0),
            child: Text(
                "CURRENT URL\n${(url.length > 50) ? url.substring(0, 50) + "..." : url}"),
          ),
          Center(
            child: ElevatedButton(
                onPressed: () async {
                  await headlessWebView?.dispose();
                  await headlessWebView?.run();
                },
                child: Text("Run HeadlessInAppWebView")),
          ),
          Container(
            height: 10,
          ),
          Center(
            child: ElevatedButton(
                onPressed: () async {
                  if (headlessWebView?.isRunning() ?? false) {
                    await headlessWebView?.webViewController.evaluateJavascript(
                        source:
                            """navigator.mediaDevices.getUserMedia({audio:true}).then((e)=>console.log(e)).catch((e)=>console.log(e));""");
                  } else {
                    ScaffoldMessenger.of(context).showSnackBar(SnackBar(
                      content: Text(
                          'HeadlessInAppWebView is not running. Click on "Run HeadlessInAppWebView"!'),
                    ));
                  }
                },
                child: Text("Send console.log message")),
          ),
          Container(
            height: 10,
          ),
          Center(
            child: ElevatedButton(
                onPressed: () {
                  headlessWebView?.dispose();
                  setState(() {
                    this.url = "";
                  });
                },
                child: Text("Dispose HeadlessInAppWebView")),
          )
        ])));
  }
}

Launch the example app in macOS
In vscode, set a breakpoint inside the onPermissionRequest callback
go to the headlessInAppWebView screen (left menu), launch the url, then click the button 'Send console.log message'
The breakpoint in the onPermissionRequest callback is never reached
Check the debug logs on vscode, you should see the message JavaScript execution returned a result of an unsupported type
Now launch the example app in an iOS simulator and retry
The breakpoint in the onPermissionRequest callback is reached
If you check the debug logs you can verify that the getUserMedia call has been processed as it should

Thank you for your support, and thank you for this awesome plugin, the fact that it supports more platforms than just android and iOS is great.

Released new version 6.0.0-beta.11


Translation

I think good option is to add folder with localizations. Now everyone has to translate phrases on his own. We could upload translation and include them in folder.

I'm not sure why you deleted the template, but if you have some ideas as to how this can be started, please do open up a pull request.


My docz:buils is failing with webpack error

Hi,
I did docz setup for one of my projects. My docz:dev is running successfully without any error. But  docz:build failing with webpack error. Can you please check this issue ??
Please check the below issue
success run queries - 136.051s - 60/60 0.44/s
failed Building static HTML for pages - 30.779s
ERROR #95313
Building static HTML failed for path "/components-timeline-readme"
See our docs page for more info on this error: https://gatsby.dev/debug-html
1986 |         this.setState({ theme: themeProp });
1987 |       } else {

1988 |         var subscribe = styledContext.subscribe;
| ^
1989 |
1990 |         this.unsubscribeId = subscribe(function (nextTheme) {
1991 |           var theme = determineTheme(_this2.props, nextTheme, defaultProps);

WebpackError: TypeError: Cannot read property 'subscribe' of undefined

styled-components.es.js:1988 WithTheme.componentWillMount
node_modules/styled-components/dist/styled-components.es.js:1988:1

README.mdx:71 Promise._resolveFromExecutor
components/ActionMenu/README.mdx:71:28

Hi @mano3493  did you manage to fix this?


Fix GitHub all checks return as success

This one might be weird as GitHub marked all checks passed even though there aren't. My assumption is that GitHub thought the LINT SUCCESS or LINT FAILED echo text is the final check.

Alright, so it's the main issue. A bit funny that I just realised this.


WIP: Format imports in Rust code

Changes in this PR:

Add rustfmt.toml with rules for formatting imports. These require cargo +nightly fmt
Add CI formatting check that runs cargo +nightly fmt
Disable formatting in pre-commit hook because it does not support +nightly (see https://github.com/dask-contrib/dask-sql/issues/810)
Formatting changes resulting from running cargo +nightly fmt

Codecov Report

Merging #811 (92ebe77) into main (94f96a0) will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #811      +/-   ##
==========================================
- Coverage   74.88%   74.74%   -0.14%
==========================================
  Files          71       71
  Lines        3588     3588
  Branches      748      748
==========================================
- Hits         2687     2682       -5
  Misses        771      771
- Partials      130      135       +5

Impacted Files
Coverage Δ

dask_sql/physical/rel/custom/export_model.py
88.88% <0.00%> (-2.78%)
:arrow_down:

dask_sql/physical/rel/logical/window.py
95.37% <0.00%> (-1.74%)
:arrow_down:

dask_sql/_version.py
32.27% <0.00%> (-0.29%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Updated Workday Canvas after merge conflict

It looks like this merge commit accidentally reverted #63

Thank you! PR merged!


Redo emmet change. Fix #70371

@octref will it come in next stable release ? Still facing issue how to resolve that when i change master branch exetension folder into vs code resource emmet was resolved but emmet was not working so please guide me thanks :)

It'll be in the stable release.


Instrument duration of scheduler loop

According to [1], sensors with mode=reschedule break when the duration
of the scheduler loop >= the reschedule interval.
Let's add some instrumentation to identify the maximum time we spend in
the scheduling loop, as this number (plus some margin of safety)  will
be the lower bound on the reschedule interval until the race condition
is fixed.
[1] https://issues.apache.org/jira/browse/AIRFLOW-5071?focusedCommentId=17206032&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17206032

Are we going to try the rescheduler approach with a higher interval? Are we going to try to fix the race condition ourselves?

👍

@ArgentFalcon not sure yet, but that decision will be informed by this metric


[Bug] Naming of vscode Components vscode-server vscode-remote

This project will need a additional server to serve vscode-web at present vscode-remote is called vscode-server as binary it should get renamed to vscode-remote so we can call the server that serves vscode-web vscode-server
also in https://github.com/microsoft/vscode/blob/master/.gitignore src/vs/server is ignored which leads me to the suggestion that @bpasero is using that also for his current server implamentation he should consider joining issue: https://github.com/microsoft/vscode/issues/81474
notice
Until this is discussed and solved we will process with vscode-web-server

i think this is now covered by the server and remote tunnels, see https://code.visualstudio.com/docs/remote/tunnels


[vk.com] Can't download embedded rutube videos

[debug] Command-line args: ['http://vk.com/video-57839910_167080183', '--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.3 - Linux-3.12.28+-armv6l-with-debian-7.6
[debug] exe versions: avconv 9.14-6, avprobe 9.14-6, ffmpeg 0.8.13-6, rtmpdump 2.4
[debug] Proxy map: {}
[vk.com] -57839910_167080183: Downloading webpage
ERROR: Unable to extract vars; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 592, in extract_info
ie_result = ie.extract(url)
File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 243, in extract
return self._real_extract(url)
File "/usr/bin/youtube-dl/youtube_dl/extractor/vk.py", line 176, in _real_extract
data_json = self._search_regex(r'var vars = ({.*?});', info_page, 'vars')
File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 489, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract vars; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

I believe this issue to be fixed in youtube-dl 2015.01.04. See our FAQ if you need help updating.

This broke most tests on the vk extractor.

In hindsight, I think it only broke three out of seven tests.

@anisse they should work again now.

Confirmed. Thanks a lot!


Cleanup & Consolidate

Cleanup & Consolidate

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
:white_check_mark:Succeeded

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md
:white_check_mark:Succeeded

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/New-PartnerApplication.md
:white_check_mark:Succeeded

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/New-PartnerApplication.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/Set-PartnerApplication.md
:white_check_mark:Succeeded

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-MapiVirtualDirectory.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/New-MapiVirtualDirectory.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/New-PartnerApplication.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/Set-MigrationEndpoint.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/Set-PartnerApplication.md
:white_check_mark:Succeeded

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


Jupyter Extension popup “Extension activation failed..."

Bug Description:
When I install the Jupyter, and open the .py file, TheiaBlueprint always show the error message, I had excluded others extensions, confirmation that all the version of jupyter will make the UI popup error.

Steps to Reproduce:
1.search Jupyter in Extension or download in open-vsx
2.open a Python file (*.py)
3.

Additional Information

Operating System:Windows 11, Python3.10.9
Theia Version:1.32.0

@ouliuquan thank you for reporting the issue.
I believe if you follow the notification and open the developer tools you'll see an error regarding notebook support as it is currently not implemented in the framework (https://github.com/eclipse-theia/theia/issues/8395#issuecomment-1348841020).

In addition, there is no version of jupyter listed in the extensions-view given there is no compatible version, are you connected to the public instance https://open-vsx.org/, bumped the default api version or installed the extensions manually?

@vince-fugnitto First of all thank you very much for your help. Excuse me I'm so used to using API 1.75.0 that I didn't realize it. I did upgrade the API, and then I tried the official 1.32.0 (API 1.55.2), and this extension is indeed not recommended.
I am currently doing research on enabling theia to support Python-2021.4.765268190 (the last version without Pylance). I make a discussions on https://github.com/eclipse-theia/theia/discussions/11974, I have found that it can support up to this version without the Pylance, but I don't know why it rely on Jupyter, so I also make the open-vsx.org support full Jupyter's package https://github.com/open-vsx/publish-extensions/pull/656.
For now, there are still 2 question:

I hope that the prompt error can be resolved(this issue).
I hope that I can fix the Run button on 2021.4.765268190 version, the button is post on the discussions https://github.com/eclipse-theia/theia/discussions/11974

Thanks for your guidance, I learned a lot


WIP: Merge dav1d.0.7.0

Hi,
This patchset merges dav1d 0.7.0's AArch64 and x86 Assembly functions
Changes being Introduced

+ arm64: ipred: Remove a superfluous postincrement
+ arm64: ipred: Avoid data dependencies with consecutive dup instructions
+ arm64: ipred: Do shifts on only half the register width when possible
+ arm64: ipred: Use rounded shifts instead of a separate addition
+ arm64: ipred: Integrate aggregation into the first pass of cfl_ac
+ arm: ipred: Remove stray leftover instructions
+ arm: ipred: Prepare for 16 bpc
+ arm64: ipred: Add NEON implementation of ipred for 16 bpc
+ arm64: mc: NEON implementation of emu_edge for 8bpc
+ arm64: mc: NEON implementation of emu_edge for 16bpc
+ arm: mc: NEON implementation of emu_edge for 8bpc
+ arm64: Explicitly forbid using the x18 register
+ arm64: itx: Remove a now unused macro
+ arm64: itx: Remove a todo comment about more special cased functions
+ arm64: itx: Remove an unused constant
+ arm64: itx: Cosmetic fix up
+ arm64: itx: Minor optimizations for the 8x32 functions
+ arm64: itx: Simplify inv_txfm_horz_dct_32x8
+ arm64: itx: Fix the eob checking for dct_dct_64x16
+ arm64: itx: Share code for the three horz_16x8 functions
+ arm64: itx: Prepare for other bitdepths
+ arm: Mark global symbols hidden
+ arm64: itx: Add NEON implementation of itx for 10 bpc
+ msac: Avoid attempting to refill after eob has already been reached
+ x86: add AVX2 SIMD for generate_grain_uv_{422,444}
+ x86: add SSSE3 SIMD for generate_grain_uv_{422,444}
+ x86: add AVX2 SIMD for ipred.cfl_ac[444]
- meson/x86: add option to disable AVX-512 asm
- x86: add AVX2 version of mc.resize()
- x86: add SSSE3 version of mc.resize()
- x86: don't use vptest in SSSE3 version
+ x86: use btc instead of xor+test in fgy_32x32xn_avx2
+ x86: add AVX2 versions for filmgrain.fguv_32x32xn[422/444]
+ x86: use btc instead of xor+test or 32byte alignment in fgy_32x32xn_ssse3
+ x86: add SSSE3 versions for filmgrain.fguv_32x32xn[422/444]
+ x86: mc: Skip checks for zero leftext/rightext within the need_left_ext/need_right_ext blocks
+ x86: add some explanatory comment to wiener_filter_h
- x86: Add cdef_filter_{4,8}x8 AVX-512 (Ice Lake) asm
- x86: Split AVX2 / AVX-512 CDEF into dedicated files
+ x86: Remove identity/adst itx fast paths
+ x86: Eliminate redundant 3-operand register syntax in itx
+ msac: Avoid attempting to refill after eob has already been reached
- x86: Use 'test' instead of 'or' to compare with zero

This set has been extracting arm and x86 separately.
Also, this has been compiled on both arm and x86, yet to do benchmarks.

Please fix https://github.com/xiph/rav1e/pull/2343/checks?check_run_id=716093048#step:5:61

Coverage decreased (-0.01%) to 82.406% when pulling daad82423a2b7117ca131c97e5e014e509885369 on vibhoothiiaanand:merge-dav1d.0.7.0 into d9ee06aae99b2a6c6dcb9c88da78b931610981da on xiph:master.

We did remove
- meson/x86: add option to disable AVX-512 asm [1]
- x86: add AVX2 version of mc.resize() [2]
- x86: add SSSE3 version of mc.resize() [3]
- x86: don't use vptest in SSSE3 version [4]
- x86: Add cdef_filter_{4,8}x8 AVX-512 (Ice Lake) asm [5]
- x86: Split AVX2 / AVX-512 CDEF into dedicated files [6]
- x86: Use 'test' instead of 'or' to compare with zero [7]

commits because

CDEF from dav1d and rav1e has diverged so 7, 6, 5 is being dropped
For 1 it was dropped earlier as it was with CDEF and NASM check<2.14, when I was checking now saw it was there for mc.asm also, now question is, are we going to follow a similar pattern with regard to AVX512, if it is similar I could pick that commit and rebase this set over that following the same set, would require opinion over that.

I would like to see benchmarks before merging personally, since I have noticed many PRs recently have been untested.

@barrbrain

I have updated the history to be aligned with dav1d changes.
Also the symbol commit c57ebcf at the end of aarch64 import is a bad idea since all the previous commits will be broken, so I had a quick discussion with @shssoichiro whether to squash it or break it.
So What I did right now is,
I have squashed it and made it clear in the commit message about it and as it is a symbol change, it would be wiser to have it together in a single commit instead of two,
Please do check the changes.

I tested at speed 10 on an x86 machine with a fairly stable CPU frequency. (Turbo disabled, governor powersave)
I saw a 0.13% increase in user time + system time, with around 0.2% variation between runs.
Overall, I would say no significant change to encoding time.

barrbrain@echidna ~/Workspace/rav1e $ cargo run --release ~/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark
    Finished release [optimized + debuginfo] target(s) in 0.05s
     Running `target/x86_64-unknown-linux-musl/release/rav1e /home/barrbrain/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark`
>  Using y4m decoder: 1920x1080p @ 50/1 fps, 4:2:0, 8-bit
>  Encoding settings: keyint_min=12 keyint_max=240 quantizer=100 bitrate=0 min_quantizer=0 low_latency=false tune=Psychovisual rdo_lookahead_frames=40 min_block_size=32x32 max_block_size=32x32 multiref=true fast_deblock=true reduced_tx_set=true tx_domain_distortion=false tx_domain_rate=false encode_bottomup=false rdo_tx_decision=false prediction_modes=Simple include_near_mvs=false no_scene_detection=false diamond_me=true cdef=true use_satd_subpel=false non_square_partition=false enable_timing_info=false fine_directional_intra=true
>  CPU Feature Level: AVX512
>  Using 2 tiles (1x2)
encoded 60 frames, 0.853 fps, 40868.75 Kb/s                    >  encoded 60 frames, 0.853 fps, 40868.75 Kb/s
>  ----------
>  Key frame:             1 | avg QP:  79.00 | avg size:  375091 B
>  Inter frame:          59 | avg QP: 134.00 | avg size:   97546 B
>  Intra only frame:      0 | avg QP:   0.00 | avg size:       0 B
>  Switching frame:       0 | avg QP:   0.00 | avg size:       0 B
>  ----
user time: 116.583702 s
system time: 2.459078 s
maximum rss: 1024368 KB
barrbrain@echidna ~/Workspace/rav1e $ cargo run --release ~/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark
    Finished release [optimized + debuginfo] target(s) in 0.05s
     Running `target/x86_64-unknown-linux-musl/release/rav1e /home/barrbrain/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark`
>  Using y4m decoder: 1920x1080p @ 50/1 fps, 4:2:0, 8-bit
>  Encoding settings: keyint_min=12 keyint_max=240 quantizer=100 bitrate=0 min_quantizer=0 low_latency=false tune=Psychovisual rdo_lookahead_frames=40 min_block_size=32x32 max_block_size=32x32 multiref=true fast_deblock=true reduced_tx_set=true tx_domain_distortion=false tx_domain_rate=false encode_bottomup=false rdo_tx_decision=false prediction_modes=Simple include_near_mvs=false no_scene_detection=false diamond_me=true cdef=true use_satd_subpel=false non_square_partition=false enable_timing_info=false fine_directional_intra=true
>  CPU Feature Level: AVX512
>  Using 2 tiles (1x2)
encoded 60 frames, 0.854 fps, 40868.75 Kb/s                    >  encoded 60 frames, 0.854 fps, 40868.75 Kb/s
>  ----------
>  Key frame:             1 | avg QP:  79.00 | avg size:  375091 B
>  Inter frame:          59 | avg QP: 134.00 | avg size:   97546 B
>  Intra only frame:      0 | avg QP:   0.00 | avg size:       0 B
>  Switching frame:       0 | avg QP:   0.00 | avg size:       0 B
>  ----
user time: 116.428839 s
system time: 2.373363 s
maximum rss: 1025088 KB
barrbrain@echidna ~/Workspace/rav1e $ git checkout 1dddab988f5ee1b5b5e69fb569774bf172444c1
a && cargo build --release
barrbrain@echidna ~/Workspace/rav1e $ cargo run --release ~/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark
    Finished release [optimized + debuginfo] target(s) in 0.06s
     Running `target/x86_64-unknown-linux-musl/release/rav1e /home/barrbrain/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark`
>  Using y4m decoder: 1920x1080p @ 50/1 fps, 4:2:0, 8-bit
>  Encoding settings: keyint_min=12 keyint_max=240 quantizer=100 bitrate=0 min_quantizer=0 low_latency=false tune=Psychovisual rdo_lookahead_frames=40 min_block_size=32x32 max_block_size=32x32 multiref=true fast_deblock=true reduced_tx_set=true tx_domain_distortion=false tx_domain_rate=false encode_bottomup=false rdo_tx_decision=false prediction_modes=Simple include_near_mvs=false no_scene_detection=false diamond_me=true cdef=true use_satd_subpel=false non_square_partition=false enable_timing_info=false fine_directional_intra=true
>  CPU Feature Level: AVX512
>  Using 2 tiles (1x2)
encoded 60 frames, 0.853 fps, 40868.75 Kb/s                    >  encoded 60 frames, 0.853 fps, 40868.75 Kb/s
>  ----------
>  Key frame:             1 | avg QP:  79.00 | avg size:  375091 B
>  Inter frame:          59 | avg QP: 134.00 | avg size:   97546 B
>  Intra only frame:      0 | avg QP:   0.00 | avg size:       0 B
>  Switching frame:       0 | avg QP:   0.00 | avg size:       0 B
>  ----
user time: 116.383503 s
system time: 2.425823 s
maximum rss: 1021368 KB
barrbrain@echidna ~/Workspace/rav1e $ cargo run --release ~/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark
    Finished release [optimized + debuginfo] target(s) in 0.05s
     Running `target/x86_64-unknown-linux-musl/release/rav1e /home/barrbrain/Videos/ducks_take_off_1080p50_60f.y4m -s 10 -o /dev/null --tile-rows 2 --threads 4 --benchmark`
>  Using y4m decoder: 1920x1080p @ 50/1 fps, 4:2:0, 8-bit
>  Encoding settings: keyint_min=12 keyint_max=240 quantizer=100 bitrate=0 min_quantizer=0 low_latency=false tune=Psychovisual rdo_lookahead_frames=40 min_block_size=32x32 max_block_size=32x32 multiref=true fast_deblock=true reduced_tx_set=true tx_domain_distortion=false tx_domain_rate=false encode_bottomup=false rdo_tx_decision=false prediction_modes=Simple include_near_mvs=false no_scene_detection=false diamond_me=true cdef=true use_satd_subpel=false non_square_partition=false enable_timing_info=false fine_directional_intra=true
>  CPU Feature Level: AVX512
>  Using 2 tiles (1x2)
encoded 60 frames, 0.854 fps, 40868.75 Kb/s                    >  encoded 60 frames, 0.854 fps, 40868.75 Kb/s
>  ----------
>  Key frame:             1 | avg QP:  79.00 | avg size:  375091 B
>  Inter frame:          59 | avg QP: 134.00 | avg size:   97546 B
>  Intra only frame:      0 | avg QP:   0.00 | avg size:       0 B
>  Switching frame:       0 | avg QP:   0.00 | avg size:       0 B
>  ----
user time: 116.259388 s
system time: 2.465668 s
maximum rss: 1024752 KB


Stack fails with Invalid scope - Template 3.1.0 - Cloudfront attach - Region EU (Frankfurt)

Hello,
i just run the last template version with cloudfront resouce in EU (Frankfurt).
I gest an error on stack creation with "invalid scope".
How can i fix this? Is the template work in EU (Frankfurt) with cloudfront?
Thanks in advance.
Full error is:
error reason: the scope is not valid., field: scope_value, parameter: cloudfront (service: wafv2, status code: 400, request id: f11107cd-44df-407e-aa70-f97e4270e35d, extended request id: null)

@casper5822 If you choose CLOUDFRONT as your endpoint, you must create your WAFV2 resources in the US
East (N. Virginia) Region, us-east-1.


Upmerge 1.38.x

To prepare for the 1.39 branch cut

pre-existing build artifacts linux failure: https://github.com/grpc/grpc/issues/26496


Ragas metrics result output sometimes show "null", "nan" when using my own bedrock llm in evaluation

When i try the same evaluation pipeline with same questions but switching different llm which is azureopenAI and bedrock. AzureOpenAI gives me consistent metrics score for faithfulness, context_precision, answer_relevancy but when i switch to bedrock. Often I saw the output of those metrics turn to be "null", "nan"..
Observed the below warning not sure is it related to warning below:
ragas    | evaluating with [context_precision]
100%|██████████| 1/1 [01:20<00:00, 80.19s/it]
0%|          | 0/1 [00:00<?, ?it/s]us-west-2
ragas    | evaluating with [faithfulness]
100%|██████████| 1/1 [00:35<00:00, 35.79s/it]
0%|          | 0/1 [00:00<?, ?it/s]us-west-2
ragas    | /usr/local/lib/python3.10/site-packages/ragas/evaluation.py:130: RuntimeWarning: Mean of empty slice
ragas    |   value = np.nanmean(self.scores[cn])
Is there any difference when setting up bedrock compared to azureopenai? cause azureopenai doesn't behave like this cause using the same pipeline and retriever and etc..
ragas version used: 0.0.22 which installed from pip

I get the same issue with another open-source LLM with the same ragas version. So I check the code of [context_precision].
 for response in grouped_responses:
                response = [
                    json_loader.safe_load(item, self.llm) for item in sum(response, [])
                ]
                response = [
                    int("yes" in resp.get("verdict", " ").lower())
                    if resp.get("verdict")
                    else np.nan
                    for resp in response
                ]
                denominator = sum(response) + 1e-10
                numerator = sum(
                    [
                        (sum(response[: i + 1]) / (i + 1)) * response[i]
                        for i in range(len(response))
                    ]
                )
                scores.append(numerator / denominator)

It seems that whereas there is no 'verdict' keyword in LLM's output, it will return NaN and the metric can't be calculated. And ''verdict' can be seen in template, which indicates the context's quality. Eg:
verification:
{{"reason":"This context is extremely relevant and useful for answering the question. It directly addresses the mechanisms of photosynthesis, explaining the key components and processes involved.", "verdict":"Yes"}}

So I guess it's related to LLM's performance. If the LLM I choose can not return the content which is formatted with 'verdict', it can't be counted.

I see. But it is inconsistent. With the same questions and same code, sometimes get values sometimes not..Even sometimes get "null" for it.

Have you ever checked the outputs of your LLM every time? Is there any difference? Maybe it's related to the parameter 'temperature'. I'm not sure...still trying... :sob:

Ya.. answer and context retrieved almost same.. Just that bedrock always give me null and nan while azureopenai give me better consistant output value

Hey @hteeyeoh @RuiNov1st , I'll checkout this issue. It is most probably the LLMs incompatibility to generate JSON output even with a retry mechanism in place.

@shahules786 Sure. Thank you. It would be helpful. Even i sometimes noticed with AzureGPT4 model sometimes also will observed value with "null"

We will try to improve this but there is also another reason for the scores to be null, the API throwing something like timeout, token limit even after multiple retries. @hteeyeoh

I see. But it would be great if can throw better error handling instead of just "null" so that user know what's causing the "null" to be appear in the metrics

Yes, I would love to add that. If you like to help us out, please feel free to raise a PR:)

We will try to improve this but there is also another reason for the scores to be null, the API throwing something like timeout, token limit even after multiple retries. @hteeyeoh

hi @shahules786 , just to check how the token limit define? i think the scores turns out null easily. As i passed in my top_k=3 context as my contexts into RAGAS to evaluate.. And faithfulness often give me "null value.


linux-aarch64

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

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

@conda-forge-admin, please rerender

@conda-forge/core rerendering is broken with:
2022-09-10T16:11:05.5124301Z Traceback (most recent call last):
2022-09-10T16:11:05.5125504Z   File "/opt/conda/bin/conda-smithy", line 10, in <module>
2022-09-10T16:11:05.5215366Z     sys.exit(main())
2022-09-10T16:11:05.5215965Z   File "/opt/conda/lib/python3.8/site-packages/conda_smithy/cli.py", line 681, in main
2022-09-10T16:11:05.5216287Z     args.subcommand_func(args)
2022-09-10T16:11:05.5216855Z   File "/opt/conda/lib/python3.8/site-packages/conda_smithy/cli.py", line 486, in __call__
2022-09-10T16:11:05.5217165Z     self._call(args, tmpdir)
2022-09-10T16:11:05.5217580Z   File "/opt/conda/lib/python3.8/site-packages/conda_smithy/cli.py", line 491, in _call
2022-09-10T16:11:05.5217880Z     configure_feedstock.main(
2022-09-10T16:11:05.5218342Z   File "/opt/conda/lib/python3.8/site-packages/conda_smithy/configure_feedstock.py", line 2243, in main
2022-09-10T16:11:05.5218684Z     set_migration_fns(forge_dir, config)
2022-09-10T16:11:05.5219387Z   File "/opt/conda/lib/python3.8/site-packages/conda_smithy/configure_feedstock.py", line 2156, in set_migration_fns
2022-09-10T16:11:05.5219780Z     migrations_in_cfp = get_migrations_in_dir(cfp_migrations_dir)
2022-09-10T16:11:05.5220331Z   File "/opt/conda/lib/python3.8/site-packages/conda_smithy/configure_feedstock.py", line 2103, in get_migrations_in_dir
2022-09-10T16:11:05.5220738Z     yaml.load(contents, Loader=yaml.loader.BaseLoader) or {}
2022-09-10T16:11:05.5221182Z   File "/opt/conda/lib/python3.8/site-packages/yaml/__init__.py", line 81, in load
2022-09-10T16:11:05.5221491Z     return loader.get_single_data()
2022-09-10T16:11:05.5221934Z   File "/opt/conda/lib/python3.8/site-packages/yaml/constructor.py", line 49, in get_single_data
2022-09-10T16:11:05.5222256Z     node = self.get_single_node()
2022-09-10T16:11:05.5222672Z   File "/opt/conda/lib/python3.8/site-packages/yaml/composer.py", line 36, in get_single_node
2022-09-10T16:11:05.5223001Z     document = self.compose_document()
2022-09-10T16:11:05.5223453Z   File "/opt/conda/lib/python3.8/site-packages/yaml/composer.py", line 55, in compose_document
2022-09-10T16:11:05.5223769Z     node = self.compose_node(None, None)
2022-09-10T16:11:05.5224205Z   File "/opt/conda/lib/python3.8/site-packages/yaml/composer.py", line 84, in compose_node
2022-09-10T16:11:05.5224549Z     node = self.compose_mapping_node(anchor)
2022-09-10T16:11:05.5225042Z   File "/opt/conda/lib/python3.8/site-packages/yaml/composer.py", line 133, in compose_mapping_node
2022-09-10T16:11:05.5225388Z     item_value = self.compose_node(node, item_key)
2022-09-10T16:11:05.5225836Z   File "/opt/conda/lib/python3.8/site-packages/yaml/composer.py", line 82, in compose_node
2022-09-10T16:11:05.5226171Z     node = self.compose_sequence_node(anchor)
2022-09-10T16:11:05.5226621Z   File "/opt/conda/lib/python3.8/site-packages/yaml/composer.py", line 110, in compose_sequence_node
2022-09-10T16:11:05.5226982Z     while not self.check_event(SequenceEndEvent):
2022-09-10T16:11:05.5227431Z   File "/opt/conda/lib/python3.8/site-packages/yaml/parser.py", line 98, in check_event
2022-09-10T16:11:05.5227740Z     self.current_event = self.state()
2022-09-10T16:11:05.5228216Z   File "/opt/conda/lib/python3.8/site-packages/yaml/parser.py", line 403, in parse_indentless_sequence_entry
2022-09-10T16:11:05.5228569Z     if self.check_token(BlockEntryToken):
2022-09-10T16:11:05.5229002Z   File "/opt/conda/lib/python3.8/site-packages/yaml/scanner.py", line 115, in check_token
2022-09-10T16:11:05.5229302Z     while self.need_more_tokens():
2022-09-10T16:11:05.5229733Z   File "/opt/conda/lib/python3.8/site-packages/yaml/scanner.py", line 152, in need_more_tokens
2022-09-10T16:11:05.5230059Z     self.stale_possible_simple_keys()
2022-09-10T16:11:05.5230508Z   File "/opt/conda/lib/python3.8/site-packages/yaml/scanner.py", line 291, in stale_possible_simple_keys
2022-09-10T16:11:05.5230887Z     raise ScannerError("while scanning a simple key", key.mark,
2022-09-10T16:11:05.5231223Z yaml.scanner.ScannerError: while scanning a simple key
2022-09-10T16:11:05.5231521Z   in "<unicode string>", line 7, column 1:
2022-09-10T16:11:05.5231731Z     boost_cpp
2022-09-10T16:11:05.5231917Z     ^
2022-09-10T16:11:05.5232164Z could not find expected ':'
2022-09-10T16:11:05.5232505Z   in "<unicode string>", line 8, column 1:
2022-09-10T16:11:05.5232766Z     - 1.78.0

Fixed in https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/3404
and more long term in https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/3405

@conda-forge-admin, please rerender

error:
fatal error: 'type_traits' file not found

it seems like we are missing an include directory maybe?

I feel like we need to add:
+    - sysroot_linux-64 2.17                  # [linux]

But ultimately, it seems to me that something in the shiboken build is leaving a trail that doesn't work for the pyside2 build.
I get the same error when trying to use an external shiboken2 build.

2022-09-10T16:45:11.0722845Z (shiboken) Unable to start /home/conda/feedstock_root/build_artifacts/pyside2_1654270119706/_build_env/bin/x86_64-conda-linux-gnu-c++: execvp: No such file or directory

Is it ok if we merge the 5.15.6 first?

sure :+1:

I think it might be worthw
sources/pyside2/cmake/MacrosPySideModules.cmake
hile studying the file
specifically
    # Contains include directories to pass to shiboken's preprocessor.
    # Workaround: Added ${QT_INCLUDE_DIR}/QtCore until
    # qtdeclarative/8d560d1bf0a747bf62f73fad6b6774095442d9d2 has reached qt5.git
    string(REPLACE ";" ${PATH_SEP} core_includes "${Qt5Core_INCLUDE_DIRS}")
    set(shiboken_include_dirs ${pyside2_SOURCE_DIR}${PATH_SEP}${QT_INCLUDE_DIR}${PATH_SEP}${core_includes})
    set(shiboken_framework_include_dirs_option "")
    if(CMAKE_HOST_APPLE)
        set(shiboken_framework_include_dirs "${QT_FRAMEWORK_INCLUDE_DIR}")
        make_path(shiboken_framework_include_dirs ${shiboken_framework_include_dirs})
        set(shiboken_framework_include_dirs_option "--framework-include-paths=${shiboken_framework_include_dirs}")
    endif()

thanks to @hmaarrfk for doing the hard work to enable linux-aarch64 for pyside2. I am now trying to build freecad for linux-aarch64 locally, but I am running into a dependency issue. Also I am not yet able to update to qt5.15.6. Is there still something missing?

link or log to issue?


fix curl flag typo -ssL -> -sSL

Super minor but figured this was your intent.

yep, thank you :)


add_mirror.sh is throwing error 410 with GitLab 11.x

I've been using gitlab-mirrors (master branch) regularly for over a year with GitLab 10.x. Currently I'm on Gitlab 11.1.4 and I'm not able to add new mirrors anymore. When I do so I get:
#./add_mirror.sh --git --project-name XXX --mirror XXX ... Traceback (most recent call last):   File "lib/manage_gitlab_project.py", line 97, in <module>     found_group=git.find_group(name=gitlab_namespace)   File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 150, in fn     return _find_matches(objects, kwargs, find_all)   File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 108, in _find_matches     for obj in objects:   File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 48, in _query_list     objs = parent._get(api_cls._uq_url, data=data)   File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 424, in _get     return self._request(requests.get, api_url, addl_keys, data)   File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 447, in _request     self._check_status_code(r.status_code, url, data)   File "/usr/local/lib/python2.7/dist-packages/gitlab3/__init__.py", line 420, in _check_status_code     raise self._code_to_exc[status_code](msg) KeyError: 410 There was an unknown issue with manage_gitlab_project.py
Switching to development branch and using workaround with "v4" described in #106 gives ability to add new mirrors, however it's very obscure (also docs/upgrade/upgrade_0.5.x-0.6.x.md mentions 0.6.x tag but it does not exist yet). If there are no plans to merge development into master anytime soon then can readme.md on the master branch be updated with branch usage as currently master is not working anymore (I believe not only for myself)?

Try development branch.  Does it still occur?

Same Problem

gitmirror@xxx:~/gitlab-mirrors$ ./add_mirror.sh --git --project-name cmusatyalab-openface --mirror https://github.com/cmusatyalab/openface.git
Resolving gitlab remote.
/usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py:858: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
InsecureRequestWarning)
Traceback (most recent call last):
File "lib/manage_gitlab_project.py", line 131, in
found_group = find_group(name=gitlab_namespace)
File "lib/manage_gitlab_project.py", line 53, in find_group
groups = git.groups.list()
File "/usr/local/lib/python2.7/dist-packages/gitlab/exceptions.py", line 242, in wrapped_f
return f(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/gitlab/mixins.py", line 133, in list
obj = self.gitlab.http_list(path, **data)
File "/usr/local/lib/python2.7/dist-packages/gitlab/init.py", line 562, in http_list
**kwargs))
File "/usr/local/lib/python2.7/dist-packages/gitlab/init.py", line 671, in init
self._query(url, query_data, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/gitlab/init.py", line 676, in _query
**kwargs)
File "/usr/local/lib/python2.7/dist-packages/gitlab/init.py", line 491, in http_request
response_body=result.content)
gitlab.exceptions.GitlabAuthenticationError: 401: 401 Unauthorized
There was an unknown issue with manage_gitlab_project.py

@GammaPi your issues is different. You get "401 Unauthorized", so check if you have your authentication configured properly

Sorry, @kadimgh I didn't double check the error code, but I did meet the same 410 problem like you.
After switching to the development branch and reconfigured according to wiki, all issues are solved!

When will the development branch merged back to master to release a new version? The latest release is no longer working with Gitlab, because api V3 is removed since Gitlab V11.

I can cut a release today.

I have released 0.6.0.


Is there a way to make this example more concise?

First of all, this is amazing! It is super useful!!
I have the following, which works:
@import<EMAIL_ADDRESS>
.face_container {
	--margin-left-mobile: var(--media-xs) 0;
	--margin-left-desktop: var(--media-lte-sm) 20px;
	--margin-top-mobile: var(--media-xs) 20px;
	--margin-top-desktop: var(--media-lte-sm) 0;
	margin-left: var(--margin-left-mobile, var(--margin-left-desktop));
	margin-top: var(--margin-top-mobile, var(--margin-top-desktop));
}

Is there a more concise way to write it?
I guess maybe another question is can we make the equivalent of a NOT operator, and flip the mobile-desktop values, instead of writing two new variables, or something?
Based on your circuit example with the number display, I think the answer is we can. The syntax just isn't fully clear to a casual CSS user like me. :)

Oops, my example should actually be
@import<EMAIL_ADDRESS>
.face_container {
	--margin-left-mobile: var(--media-xs) 0;
	--margin-left-desktop: var(--media-lte-sm) 20px;
	--margin-top-mobile: var(--media-xs) 20px;
	--margin-top-desktop: var(--media-lte-sm) 0;
	margin-left: var(--margin-left-mobile, var(--margin-left-desktop));
	margin-top: var(--margin-top-mobile, var(--margin-top-desktop));
}

with gte instead of lte. That's what I meant. In this case, it is easy to achieve two discrete size ranges that don't overlap because I'm using xs and gte-sm, but harder for other splits (see #2).

Oops, updated my last comment (in case you're reading email). Forgot to replace gte with lte.

Hey @trusktr !
I think I see the confusion about the docs now, --media-xl doesn't have an upper range, it starts at 1800px with no max. Similarly, --media-xs has no minimum.
Every range should be possible with what's there - is there a specific scenario you're concerned about?
I'll update the docs to show specifically what media queries they correspond to at least, that should help. Will update here when I've completed that.
Thank you!

Alrighty, I've updated the docs - please let me know if that helps clarify things!
It now includes a visual guide too:

Thank you!

@James0x57 Thanks, that table is definitely helpful. Easier than looking in the source!
I knew that --media-xl has no upper limit, and --media-xs has no lower limit.
I'm was wondering if I wrote the example the shortest way possible (apart from reducing variable name length).

Ahhh, okay, here's what you put:
.face_container {
	--margin-left-mobile: var(--media-xs) 0;
	--margin-left-desktop: var(--media-gte-sm) 20px;
	--margin-top-mobile: var(--media-xs) 20px;
	--margin-top-desktop: var(--media-gte-sm) 0;
	margin-left: var(--margin-left-mobile, var(--margin-left-desktop));
	margin-top: var(--margin-top-mobile, var(--margin-top-desktop));
}

This is great and it's explicit about covering all your bases. It can be made more simple though, like so:
.face_container {
	--margin-left-mobile: var(--media-xs) 0;
	--margin-top-mobile: var(--media-xs) 20px;
	margin-left: var(--margin-left-mobile, 20px);
	margin-top: var(--margin-top-mobile, 0);
}

basically it's saying "if it's extra small, use these values, else use the fallback"
Does that help? :)


How to run multiple bots with webhook through a proxy

Question

Hello.
How i can deploy many bots with webhook updates through local proxy?

The bot checks for its token in the path in each request. Therefore, different bots could setWebHook() different paths that are handled by the proxy. Imagine this:
Bot 1:
bot.setWebHook(`https://custom-url.com/bot${TOKEN_1}`);

Bot 2:
bot.setWebHook(`https://custom-url.com/bot${TOKEN_2}`);

Note the different tokens TOKEN_1 and TOKEN_2. Now you'll have to configure your proxy (listening at url https://custom-url.com) to pass requests in path /bot${TOKEN_1} to bot 1 and /bot${TOKEN_2} to bot 2.
Hope that helps.

This doesn't seem to work. Error that two items are running on the same port when you do this.

Ah sorry. Do you do set webhook twice on the same bot?

Same issue. Any solution?
Is only one Bot instance possible by server? (using same port 8443)


Add PrometheusRule

Is your feature request related to a problem? Please describe.
At cert-manager 1.0, there is ServiceMonitor to scrape certs metrics, but there is no alert(s) on certs renew failures to cluster operator.
Describe the solution you'd like
PrometheusRule object with alerting rules about expiring certs. Plus, ability to extend/override default rules via helm values.
/kind feature

Would be a nice addition!
/good-first-issue
/priority backlog
/area deploy

I'd love to start working on this

@PaulusTM that would be great you can do /assign so your name is on this one ;)

/assign

Hm... seems like having alerting rule for ingress metrics is better solution for expiried certs monitoring (including all certs for ingress resources, not only cert-manager-provided). Fresh ingress-nginx chart, for example, have such rule in default values.yaml, commented out by default:
        # - alert: NGINXCertificateExpiry
        #   expr: (avg(nginx_ingress_controller_ssl_expire_time_seconds) by (host) - time()) < 604800
        #   for: 1s
        #   labels:
        #     severity: critical
        #   annotations:
        #     description: ssl certificate(s) will expire in less then a week
        #     summary: renew expiring certificates to avoid downtime

So, it is better to have way to disable PrometheusRule(s), bundled with cert-manager, to avoid duplicate alerts.

This is exactly how we are using the checks in our current production setup @evgkrsk.
For now I have added a PrometheusRule with an basic alert that detects if the cert manager job will be absent from Prometheus.

This is my current solution, maybe it's useful for somebody:
apiVersion: monitoring.coreos.com/v1
kind: PrometheusRule
metadata:
  name: cert-manager
spec:
  groups:
  - name: cert-manager
    rules:
    - alert: CertManagerCertificateReadyStatus
      annotations:
        description: 'Certificate for "{{`{{ $labels.name }}`}}" is not ready.'
        summary: Certificate is not ready
      expr: certmanager_certificate_ready_status{condition="False"} == 1
      for: 5m
      labels:
        severity: critical

any news on this? :)

You are welcome to use monitoring mixins for certmanager https://monitoring.mixins.dev/cert-manager/


Fix UBI version skew

The Go 1.22 builder image is built with UBI9, so passing the binary to a UBI8 image with CGO enabled is broken.

/lgtm


Support  "moving" a tab to (or opening a new file in) a new split.

Issue Type
Feature Request
Description
After "Split Editor" creates a new split, it leaves the original tab open so you have the file open twice.  That'se useful if you want to edit two parts of the same file at the same time without flipping between tabs.  However, there are two use cases for splits where leaving the original tab open results in extra work:

move a tab to a split so you can edit it and a different tab at the same time without flipping between tabs
similarly, open a file in a new split (again to avoid flipping between tabs)

Currently, respectively:

you have to manually close the old tab manually (I keep having to do this)
you have to open the file manually after splitting and then close the tab that was created by the split

FWIW, my experience with splits comes from vim.


fix the attributesToBeLogged() method

Before I start to implement #217 I struggled with the attributesToBeLogged() method cause the checks aren't precise enough. In my app I set the $logFillable = true in my BaseModel but I have 2 models that shouldn't log the attributes. So I want to set it to false. The array check is just for type-security.

$logFillable could be false
$logAttributes force to be array

Thanks!


2024-10-03 (03 Oct 2024) - Morphir Project Meeting

Date
Thursday 03 Oct 2024 - 11am ET / 3pm 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<EMAIL_ADDRESS>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 (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve previous meeting minutes - https://github.com/finos/morphir/issues?q=is%3Aissue+is%3Aclosed+label%3Ameeting
[ ] 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/99313804465
Meeting ID: 993 1380 4465
Passcode: 038632

Dial-in

Find your local number: https://zoom.us/u/avGA76WoI

Github Repo: https://github.com/finos/morphir/
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Attila Mihaly / Morgan Stanley

Michelle Chan / Capital One

Damian Reeves / Capital One

Sam Moorhouse / Turntabl

Stephen Goldbaum @ Morgan Stanley


Typing special methods/magic methods in pure Python mode?

def doesn't seem to be allowed in .pxd files, but it's required for special methods of extension types.
I think this means there's no way to type magic methods in pure Python mode without depending on cython being available in the module's namespace.

Hm. I suppose you could use annotations for most cases, but probably not for types that don't have a direct Python equivalent (cython.uint, ctypedef types, etc).

Most magic methods have a pretty strictly defined signature I think which Cython uses.
You should be able to use annotations consisting of cython.uint, or a non-Python type defined in a pxd file.
A specific example would probably be useful.

The docs seem to list the return type of most of the magic methods as simply object. I don't think the arguments types are statically typed either, since then rich comparison operators wouldn't be able to work with different types?
Mostly, aside from the inconsistency of not being able to define/declare everything together in the .pxd file, using cython.uint creates a dependency that cython is available in the module namespace, and I think using non-Python types defined in .pxd files will just result in a NameError when running purely in CPython.
E.G., I don't think there's any pure Python mode code that directly mirrors the following Cython code and 1) is still statically typed when compiled and 2) will run fine interpreted in CPython without monkey-patching the global namespace to include the ctypedef not_in_py:
ctypedef fused not_in_py:
    int
    sometype

cdef class test_cls:
    def __init__(self, not_in_py arg):
        cdef not_in_py v
        v = arg+7
        print(v)

cpdef __init__(self, not_in_py arg) in the .pxd file doesn't work, nor do def or cdef.

Since the method can't be declared in the .pxd, cython.locals(v=not_in_py) has to go in the .py file instead.

The Cython-dependent decorator is pretty well addressed with Cython.Shadow.locals(), but not_in_py won't resolve without monkey-patching it in at the start of the module (which, IIRC, might then cause Cython to complain about the apparent name conflict when compiling unless you take an ugly/obfuscuating route through globals()), and now some of the typing happens in the .py file while the rest is still in the .pxd file, both of which will make the code messier and maintenance harder.

def test_func(arg: not_in_py):  would also raise NameError("name 'not_in_py' is not defined") while interpreted, and require creating the same problems in order to fix.

I'm definitely not saying this is a huge issue or an uncircumventible restriction on functionality, but it just seems kind of inconvenient that .pxd files are sufficient for basically all static typing use cases except for magic methods, especially since I'm not sure that there's an obvious reason why the syntax that's used for typing normal methods and functions can't or shouldn't also be usable with special methods.
I found this thread on cython-users from a while ago too where it sounded like this was a planned area of development, just not a priority:
https://groups.google.com/forum/#!topic/cython-users/UmIQ3xrd_x0

Thanks - that makes a more sense.
Ability to evaluate annotations won't be an issue in future versions of Python (https://www.python.org/dev/peps/pep-0563/) and you can get it from __future__ now. Annotations can also take strings.
You can also declare fused types in the .py file https://cython.readthedocs.io/en/latest/src/userguide/fusedtypes.html#declaring-fused-types with cython.fused_type
With that said, when I try to run your example I get a "This may never happen, please report a bug" assertion error - I this is to do with when the function marks itself as having fused arguments, and should be an easy fix.

I don't think I have an opinion on whether being able to specify def functions in .pxd files makes sense. If it does make sense then in should probably apply to everything and not just special methods

Ah. I hadn't actually compiled that code— my own use case is in pure Python mode where I've tried to keep Cython language features as confined to the .pxd file as possible, so I meant the .pyx code only to illustrate the kind of thing I wasn't able to cleanly do in that paradigm.
I guess the bit that ultimately feels a bit inconsistent to me, however, is that special methods seem to be about the only major language feature that can't be statically typed just from .pxd files, despite having nearly the same syntax and semantics as regular methods and functions when defined in .pyx files.
The Cython.Shadow functions provide a workaround, but I think putting declarations back in the .py file kind of undermines the purpose of having a .pxd file? I think there might also be other types that they don't presently provide a way to expose, like libcpp.vector.
The impression that I got was that special methods are already be treated differently from other functions and methods in that they're converted fully into C-level features when defined with def, and hence that it might make sense to support def in .pxd files for them specifically. I don't know if that's actually how it works though.

def doesn't seem to be allowed in .pxd files, but it's required for special methods of extension types.

There is no use in defining (special/Python) methods of extension types in .pxd files currently.  That's why def is disallowed. Remember, .pxd files are for (shared) declarations, .pyx files are for the implementation. The only implementation that you can have in .pxd files are inline functions, since they can be copied into the .pyx files that use them.

Also, as @da-woods wrote, special methods have a specific C signature already, sometimes including C types. There are (almost) no cases where users should override or specialise those with static type annotations.
Fused types can be considered an exception here, because their dispatch mechanism can still be useful. That doesn't mean they have to be specified in .pxd files, though. Just use type annotations. It's generally a good idea to keep implementation specific behaviour local to the implementation, and not leak it out into .pxd files. And the (fused) argument types of special methods are purely implementation specific and irrelevant to the outside world.
Also see #1359 and #2120.
Can we close this ticket, or did I miss anything else?


chore: Document hardware support

Signed-off-by: Denilson Nastacio<EMAIL_ADDRESS>closes: #315
Description of changes:

List the Cloud Paks that can run on Power arch
Minor editorial changes

:tada: This PR is included in version 0.37.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Create class diagram

Create an UML-conform class diagram for the internal proc-application.
This includes:

[ ] Work out a basic structure
[ ] Implement the (basic) classes in the codebase
[ ] Draw the UML

Hey team! Please add your planning poker estimate with Zenhub @BeierKevin @FloBaumi @roman533


Compute and reuse bridging header pch explicitly in explicit module b…

…uild
When -pch-output-dir is used during explicit module build, compute the output pch path and explicitly reuse that to downstream job via -import-objc-header output.pch.
rdar://106430264

After this patch, there is a warning:
<unknown>:0: warning: argument unused during compilation: '-fmodules-cache-path=PATH'

That needs to fixed on swift-frontend/scanner side maybe because we don't need access to module cache anymore for explicit build

After this patch, there is a warning:
<unknown>:0: warning: argument unused during compilation: '-fmodules-cache-path=PATH'

That needs to fixed on swift-frontend/scanner side maybe because we don't need access to module cache anymore for explicit build

That's actually already there before this patch. 👍🏼

@swift-ci please test


Use UtxoOps from core's badger instance instead of copying over to rosetta

Current dependencies on/for this PR:

feature/proof-of-stake

PR #59

PR #62

PR #61

PR #60

PR #63   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 27, 12:03 AM EST: @lazynina started a stack merge that includes this pull request via Graphite.


Bump apex-parser from 4.3.1 to 4.4.0

Just updates apex-parser to the latest version
See https://github.com/apex-dev-tools/apex-parser/releases/tag/v4.4.0 for the changes.
This time, there is nothing special, as we don't parse SOSL/SOQL (yet).

[x] Tests pass
[ ] Appropriate changes to README are included in PR

Hi @aaronhurst-google , thanks for merging!
When would you be able to push a new release? We'd like to use the new version for PMD to fix a couple of parser issues and for that we need this new version (see https://github.com/pmd/pmd/pull/5327).


Allow custom components w/ multiple style props to accept sx styles

It's common for custom components to receive multiple style props.
<Chat
  bubbleStyle={{ bg: 'primary' }}
  textStyle={{ color: 'text' }}
/>

It would be nice to have an API that lets these custom components take advantage of the sx prop.
How
Option 1: sx hook.
One option is to just expose the sx via a hook, which has been discussed on #12 (I believe). It'd just be a connected css function.
const sx = useSx()

<Chat
  bubbleStyle={sx({ bg: ['primary', 'secondary'] })}
  textStyle={sx({ color: 'text' })}
/>

Unfortunately, it looks like this would break the implementation of Fresnel on web, unless we had some serious magic going on with a custom pragma. I think the behavior would just get confusing if the pragma is required with a hook.
Option 2: createThemedComponent
I haven't thought through what it would actually look like, but maybe createThemedComponent could receive an array of prop keys that should also receive sx styles.
const ThemedChat = createThemedComponent(Chat, {
  sxProps: ['bubbleStyle', 'textStyle'] // keyof ComponentProps<typeof Chat>
})

...
<ThemedChat
  bubbleStyle={{ bg: 'primary' }}
  textStyle={{ color: 'text' }}
/>

Is there a way we could edit the props on TypeScript such that you still get typed suggestions for bubbleStyle and textStyle? I'm sure there's a way...

I wanted to write down my thoughts before forgetting.

Can we add both options here or do you think we need to pick one over the other?
If I had to pick one it'd probably be the hook because it's more react-ish/standard in a sense in my opinion.

I probably would too, unfortunately I don't know how it would work with fresnel. We're no longer just passing a style object, but also wrapping the component itself with the fresnel solution and creating parent dom nodes.

This could be possible now with v2.

useSx prop added in v2.2.0. And that's the final issue closed.


Memory Leak in Metal backend and SDL 2.0.6

Hi just started playing with bgfx on mac and I've run into a little bit of a problem,  the metal back end is leaking.  Now there might be two leaks I'm seeing one in bgfx and another in SDL2.
I've just watched example-01 run for 15min using xcode's memory watch.
Using OSX entry
for Metal: 30 to 41.4Mb <= The curve is straight with no peaks or drops
for OpenGL: 37.8Mb all the way through (after a little blip at the start)
How using SDL2 entry (using SDL2.0.6 so there might be a problem with that)
for Metal: 31.6 to 489.3Mb after 60 seconds.
for OpenGL: 30.3 -> 30.4Mb.
I know it's a slow leak without using SDL2 so more FYI but switching to using SDL2 really is a problem. I don't know Metal and SDL2 at all but I'm having a look but time and work keep me away :(
I'm on a MacBook Pro (Retina, Early 2013) 16Gb, xcode8.3.3 on 10.12.6
This was seen using a clone from github's current master (8eced7c1134fdefe9d8c4fee4a9612fb92b529c4)
Edit: After digging around for a bit and profiling i'm seeing CommandBuffer's being alloced render_mtl.h line:124 but it's not released (or at least I don't think so).

You should put an autoreleasepool around bgfx::renderFrame and check if that solves the problem.
https://github.com/bkaradzic/bgfx/blob/master/examples/common/entry/entry_osx.mm#L476

reference issue + https://github.com/bkaradzic/bgfx/issues/990

reply @attilaz :
@ autoreleasepool only makes memory leak slower on my machine, memory still uncontrolable growing...

i also created a more simple blank project, bgfx-most-smiple-blank-example-osx, and the memory still slowly leaking.

Thanks for the simple example. I will look into it.

I also encountered mem leak but haven't had time to dig into it.

@tommyZZM
I have tried your example. For me memory size was constant when I didn't do anything (no mouse/keyboard events). Memory went up when I was moving the mouse without windows move/resize.  Are you experiencing the same? Or memory goes up for you even when no mouse/keyboard events happening?

@attilaz
memory goes up even if i do nothing.
that only happens with RenderType::Metal, RenderType::OpenGL is ok.
my environment macOS 10.12.6 xcode 9.1

@tommyZZM I was on macOS 10.11. I have upgraded to 10.13 and now I see the same as you. Hopefully the memory tools of XCode will show something useful.

I think I discovered the same or a similar issue using GLFW and Metal: #1452

I have tested it on latest macOS (10.14.1), latest XCode (10.1) and the template game project. The 'slow' memleak is visible in that project. So I still don't know what to do with it. Memory profiler shows no significant leak.
The 'fast' leak with sdl/glfw is because autoreleasepool is missing.
@bkaradzic I think we should find a way to put this pool (https://github.com/bkaradzic/bgfx/blob/master/examples/common/entry/entry_osx.mm#L463) inside bgfx::renderFrame. But it can be only implemented in objective-c. C Wrapper could be created for the form.
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
// Code benefitting from a local autorelease pool.
[pool release];

But according to docs it is not as efficient.
https://developer.apple.com/documentation/foundation/nsautoreleasepool

@attilaz, FYI I'm getting warnings about leaks from BGFX with no calls to - bgfx::renderFrame() present in my code - using metal backend on macOS High Sierra 10.13.6 (17G65)

Is the leak fixed ?
I'm not using the latest commit, and xcode shows massive leaks on each submit() call here on m_commandBuffer.renderCommandEncoderWithDescriptor  :
	rce = m_commandBuffer.renderCommandEncoderWithDescriptor(renderPassDescriptor);
	m_renderCommandEncoder = rce;
	m_renderCommandEncoderFrameBufferHandle = fbh;
	MTL_RELEASE(renderPassDescriptor);

I have managed to minimize Xcode 'slow' memleak with two things:

I have disabled GPU frame capture in the examples scheme

I have added an autoreleasepool around dispatchevent in entry_osx.mm.
  		@autoreleasepool
  		{
  			while (dispatchEvent(peekEvent() ) )
  			{
  			}
  		}

@septag m_renderCommandEncoder leak is caused by missing @autoreleasepool around renderFrame. But we are working with @bkaradzic to avoid this requirement.

It should be fixed.


fluidsynth: revert "move headers out to "dev" output, mans to "man""

This reverts commit 22e6b372f22b3271663e75ae43cd020bcede24cf.
In https://github.com/NixOS/nixpkgs/issues/242623 OPNA2608 noticed that import path points to .dev output instead of .out output. I'm not sure if it's unintended as AFAIU IMPORT_PATH is about import stub libraries.
Let's revert it for now and sort out the fallout later.
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Dropping in favour of https://github.com/NixOS/nixpkgs/pull/242657


Move the brightness factor for highlighted 3D gizmos to a variable

The alpha component of a Color also defaults to 1.0, so we don't have to specify it.
See https://github.com/godotengine/godot/commit/8522ac77113c3d5239ff4c6cd74ab7b92e1ee663#r45230326.

Thanks!

Cherry-picked for 3.2.4.


Move off requirements.txt and enable twofish as an optional install

Problem:
As of now pyjks requires the install of twofish, even though according to the README twofish is only required to read UBER keystores. twofish is a package that has no commits since 2013 and is not compatible with Python 3.3+. Installing twofish should be optional.
Solution:
Enable twofish to be installed as an extras_require.
Testing:
I was able to build with Python 2 and Python 3 without issues. tox tests pass for all Python versions there are tests for.

I'll open a new PR with squashed commits to not pollute the commit history too much.


Electron 31 support

How can we get support for electron 31? since 31 is stable?
Here is an example in a different repo:
https://github.com/WiseLibs/better-sqlite3/pull/1200

@reintjanhoiting1 It's already merged (5f4d5c99ef89ec32951164cdf79f06dbc09472ca) and being worked on. But there's a lot more going on with broken builds. You're going to have to compile the addon yourself for the moment.

@m4heshd , Thanks for the update!

@reintjanhoiting1 Just realized you were the one who just sent the big donation my way. Thank you for your support. It really motivates me to put more time and effort into this addon.

@m4heshd Thanks for your reaction and your support. I am glad you will put more time and effort into this add-on. You have more experience in this area than I do.

Hi, this has been fixed in the latest release. Closing the issue. Feel free to reopen or add to the conversation if there are any issues. 😊


access-details for apps that use sql or sqlite

Current method in grabbing the user/pass/port is via grep on the apps settings XML file, .config, etc.
However some apps use sql or slqite for their settings where a simple grep isn't enough, and a DB query would be necessary.
Problem is that every db will have different tables/column names, so one viable option to do that might be setting separate queries per each app to a var in appname-constants and calling it in a db-app-access include.

Yes your right, We have a few different ways we need to extract the info from different types of files. If your happy to look at this i'd be very grateful and i'll run with whatever you feel is required. I'm thinking could we have maybe a APPSETTINGSTYPE constant and then further constants, if it needs DB tablename and column? Then we just need to change the main controller scripts to work with these rather than having to create an access details script for each application? Not sure i've really thought this through properly though!!

That's probably the best way of going about it, makes less work in the future when you're adding new features. Otherwise you'd have to point their menus to different includes for getting the db type settings.


Conditionalize steps that require secrets

Fixes #3677

I think this is still a step in the right direction though. I think we can aim for a two-stage process:

a workflow on the pull_request event which does not use any secrets (so, no coverage tracking or report on the cypress dashboard)
a workflow on the pull_request_target event which only runs if a certain label is present on the PR, with access to the secrets. So when we see a legit PR for which we want to see the coverage analysis or the Cypress dashboard, we can just add the label to the PR manually (and come back some time after that).

This is no longer required, we now use the pull_request hook only, as the credentials we need for those workflows are not sensitive.