Receive mwc coins notification for http, mqs & tor

We want to see the message box that funds are received.

Tested. Everything works fine. Got congrats message boxes for http, tor & mqs with both notifications and without notifications.

Tested. Everything works fine. Got congrats message boxes for http, tor & mqs with both notifications and without notifications.


python312Packages.spython: 0.3.12 -> 0.3.14

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.spython is: Streamlined singularity python client (spython) for singularity
meta.homepage for python312Packages.spython is: https://github.com/singularityhub/singularity-cli
meta.changelog for python312Packages.spython is: https://github.com/singularityhub/singularity-cli/blob/0.3.14/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.3.14 with grep in /nix/store/vsfln32s6zf6jgk6pp015bickyl7v3fr-python3.12-spython-0.3.14
found 0.3.14 in filename of file in /nix/store/vsfln32s6zf6jgk6pp015bickyl7v3fr-python3.12-spython-0.3.14

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

cwltool
python311Packages.spython
python312Packages.spython

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vsfln32s6zf6jgk6pp015bickyl7v3fr-python3.12-spython-0.3.14 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.spython https://github.com/r-ryantm/nixpkgs/archive/ef58b536a1d7f3de8456bb069575df8a81923b31.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ef58b536a1d7f3de8456bb069575df8a81923b31#python312Packages.spython

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vsfln32s6zf6jgk6pp015bickyl7v3fr-python3.12-spython-0.3.14
ls -la /nix/store/vsfln32s6zf6jgk6pp015bickyl7v3fr-python3.12-spython-0.3.14/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

cwltool
cwltool.dist
python311Packages.spython
python311Packages.spython.dist
python312Packages.spython
python312Packages.spython.dist

Maintainer pings
cc @fabaff for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

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

6 packages built:

cwltool
cwltool.dist
python311Packages.spython
python311Packages.spython.dist
python312Packages.spython
python312Packages.spython.dist


Flask App Import Path Confusion

Summary: The test cases for the Flask app (test_routes.py) required manual adjustment of the import paths (from src.app import app had to be updated to from src.app.app import app).
Details: This caused initial test failures when the test client attempted to access the app object, reporting that it lacked attributes like config. The import path needed to reflect the correct module structure.
Affected Areas: Test imports in /tests/test_routes.py.
Dependencies: None.

Updated import statements to reflect the proper path: from src.app.app import app.


Install JAR under the hood for python users (like pydl4j does)

Right now, users can't just install konduit, they have to clone this repo, build a jar, copy the jar and set a path variable.
we should have a mechanism like pydl4j in place that takes care of all of that without users knowing about it. that could in fact be in pydl4j itself, as this was built to be a jar manager in the first place.

BTW, since we're already using Java here, what's the downside with just using Maven?

it will use maven either way (pydl4j does so under the hood). for instance, we use batteries-included mvnw here, which is already a good option. the point is to make it as simple as possible for "basic python users" to use our software. and telling them to first install mvn etc., they'll likely just move on.

I plan to do something like that for the JavaCPP-based distributions. It'll probably be using some Bash script like mvnw yeah...

ideally, I'd like to expose a tiny cli tool like this:
konduit build

and this build step would, e.g., clone this repo, run mvnw with the proper options (maybe even inferring the platform used somehow?) and putting the resulting uberjar into, say, ~/.konduit/konduit.jar so your python code will automatically look there.

Sounds like a conda-pack. Yeah, sure, I'd see that as part of my stuff as well.

@saudet @maxpumperla  Kinda curious if there was any follow up here given previous discussions.

@agibsonccc patiently wait 5 more minutes for my next PR

Not really, is this something that needs to get done right away? I mean if it's just copying pydl4j, might as well do it. For example, I'm not sure I'll be able to support already installed versions of Python, for example, just like Anaconda installs its own version of Python.

So of note here is @sshepel starting to work on the CI here. Once we're up on maven central, this should be a lot easier. Figured I'd flag now to be sure.

@maxpumperla this is related I believe: https://github.com/KonduitAI/konduit-serving/pull/61

yeah, I know :) we have basic support for this already, so we could theoretically close the issue. but: once we have actual maven central releases I don't want people to build the project entirely from scratch (even if they don't know that's happening). leaving this open until then.

closing now, since pydl4j interop seems to work with the latest PR #82


Update objc dependency to 0.2

I just published version 0.2 of the objc crate, changelog here: https://github.com/SSheldon/rust-objc/blob/master/CHANGELOG.md#020
Main differences are gnustep support, (optionally) more type checking, removed the libc dependency, and fixed a bug in the space reserved for ivars when declaring classes.
By removing the libc dependency, objc can't break glutin anymore by having a mismatch between libc versions :)
This requires servo/cocoa-rs#120 to be merged first, which also means the Travis checks will fail until then.
Testing: verified glutin still compiles and tests pass, verified the window example looks good.

Seems to refer to a 0.3 version of cocoa which doesn't exist?

Cocoa has been published.

Thanks!
Do cocoa and objc have to be tied to a specific version? If so, it can still break :-/

Yeah, it can still break, but as long as cocoa and objc are good about their versioning, it can only break by someone making a change to glutin, it won't suddenly happen to users. Being good about versioning can be hard, though, as demonstrated by the libc issue I caused with my bump to objc :P
To get rid of the requirement that cocoa and objc be on specific version together, we'd have to stop using the msg_send! macro on types from the cocoa crate. Or cocoa would have to export its own version of the msg_send! macro.
Using types from other libraries is still pretty hard :/


TypedArray.slice has optional parameters

Motivation
As can be seen in the documentation, TypedArray.slice has two optional parameters, begin and end. However, js_sys exposes this function with both parameters required only.
Proposed Solution
ArrayBuffer does implement the second parameter properly by exposing slice and slice_with_end (begin is not optional in that API for some reason). TypedArray should do a similar thing, but split into three function calls.

I believe the initial intention was to expose the most flexible version, but new methods without the optional parameters can also be added!


Allow non-semver version for generic packages

Feature Description
I think it would be nice if it was possible to upload packages with non-semver version.
My usecase for this is to have unstable perview versions for each commit to main with the commit hash as the version.

already implemented: https://github.com/go-gitea/gitea/pull/20531 will be in 1.17.0


Honor reset without the app capability

Fixes #157: Don't ignore reset capability when appActivity/appPackage are used instead of app.

LGTM, but @imurchie should also review. It'd also be nice if there were some tests, even just unit tests.

Looks good. I second a unit test or two.

Great, I'll do unit tests. I'm not too used to Appium code and won't have much time this week, so I will probably do it at the weekend only.

Cool1 Let us know if we can help.

Unit tests added!

Looks good to me. Can you squash into a single commit, and we can proceed? Thanks!

thanks for adding tests @tiagoshibata! Also looks like there are conflicts that may need to be resolved

Squashed and rebased with master.

Functional build passed: https://team-appium.ci.cloudbees.com/job/Appium-android-driver/372/
Thanks for this!


How to implement port.readline()?

Synchronous readline: how to do it?

What are you trying to do?

I would like to call something like response = port.readline(); instead of using the event-driven ReadLine parser, or polling the port with "port.read()".
My device implements a protocol where it expects that I only send a new message after having received the response from the previous message sent.

What happens?

If I use readline parser and send multiple writes, it is cumbersome to match the "writes" with the respective "responses", since the writes are sent all at once, and the responses arrive shortly after (at least according to my console logs). Sample code below:
const SerialPort = require('serialport');
const ReadLine = require('@serialport/parser-readline');
const api = require('./myApi');

SerialPort.list()
  .then(portInfos => {
    portInfos.filter(pinfo => pinfo.manufacturer === 'FTDI')
      .forEach(async portInfo => {
        const port = new SerialPort(portInfo.path, {
          baudRate: 3000000,
          parity: 'even',
          dataBits: 7,
          rtscts: true,
          autoOpen: false,
        }).setEncoding('ascii');

        const parser = port.pipe(new ReadLine({
          delimiter: '\r\n',
          encoding: 'ascii',
        }));
        parser.on('data', data => {
          console.log('Rx', data);
          console.log();
        });

        port.open();

        const serialMessage = api.createReadMessage(api.SERIAL);
        const batteryMessage = api.createReadMessage(api.BATTERY);

        for (const message of [serialMessage, batteryMessage]) {
          port.write(message);
          console.log('Tx', message.trim());
        }
      });
  });

Output:

Tx :0A0300070004E8
Tx :0A03000B0002E6
Rx :0A0308000004670000000A76
Rx :0A03040064006427

What should have happened?

If I could devise a function like
function sendAndReceive(message, port) {
    port.write(message);
    response = port.readline();
    console.log('Tx', message);
    console.log('Rx, response);
    console.log();
    return response();
}

Then I could have my code like this:
batteryResponse = sendAndReceive(batteryRequestMessage, port);
serialNumberResponse = sendAndReceive(serialNumberRequestMessage, port);

and get this output:

Tx :0A0300070004E8
Rx :0A0308000004670000000A76
Tx :0A03000B0002E6
Rx :0A03040064006427

Versions, Operating System and Hardware

<EMAIL_ADDRESS>Node.js v10.15.3
Windows 10
FTDI (custom device)

Well I came up with this, which is not a proper "readLine" method, but seems to work for a possible "sendAndReceive" implementation. I am not sure if this is reliable, though. Sorry if this is not the right place to ask, but any help is appreciated.
const sendAndReceive = (message, port) => new Promise((resolve) => {
  port.write(message);
  const parser = port.pipe(new ReadLine({
    delimiter: '\r\n',
    encoding: 'ascii',
  }));
  parser.on('data', data => {
    parser.removeAllListeners('data');
    resolve(data);
  });
});

Well I came up with this, which is not a proper "readLine" method, but seems to work for a possible "sendAndReceive" implementation. I am not sure if this is reliable, though. Sorry if this is not the right place to ask, but any help is appreciated.
const sendAndReceive = (message, port) => new Promise((resolve) => {
  port.write(message);
  const parser = port.pipe(new ReadLine({
    delimiter: '\r\n',
    encoding: 'ascii',
  }));
  parser.on('data', data => {
    parser.removeAllListeners('data');
    resolve(data);
  });
});

Thanks for this.  On initial testing, it looks good.  I will continue testing it, and hopefully it will solve my issue especially when running every 1 to 10 milliseconds.
Cheers

Unfortunately, it works great until you hit it hard.  Responses get mixed up when running fast.


Supavisor maintenance in ap-southeast-2 (Sydney) region has caused "Connection terminated unexpectedly" errors

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
We're seeing lots of "Connection terminated unexpectedly" errors in our app since recent maintenance on Supavisor in ap-southeast-2 (Sydney) region:

To Reproduce
Still trying to reproduce reliably, but it feels very much like this same issue I dealt with a couple of month ago: https://github.com/supabase/supavisor/issues/344
Expected behavior
You know, not errors.
Screenshots
See above.
System information
N/A
Additional context
I've submitted a support request too. Haven't heard back yet.

The only response I've received from Supabase about this so far:

Thank you for contacting Supabase Support. I am forwarding this to the pooler team to further investigate it.

@abc3 @chasers Is that y'all? I'd love to at least get some insight as to what was changed in that maintenance window.

Hey @haydn, sorry that you are experiencing a similar issue again. During maintenance, we deployed a new version but rolled it back after a few hours, so it should be working as before. The reason I haven’t responded to your support ticket yet is that I am still investigating the root cause. However, I will now focus on resolving the problems you're facing with the old version

@haydn, is it better now? Feel free to respond here or in the support ticket

@abc3 Thanks, it's looking good! Close to 0 errors in the past 2 hours. 👍


Files for building Cypress with Packer

Need to bump version in cypress.yml to alpha6 too...can you add that to this PR?


Syntax Error IE 11

In at least version 1.2.4 and 1.2.5 I've experienced a syntax error in IE 11. Not getting a full stack trace and difficult to debug given the capability of IE11s developer tools.

We're stuck at version 1.2.0 now until this is fixed. Was discovered when bumping the patch version to 1.2.4 (and trying 1.2.5 had the same issue).

Thank you for reporting @derekr! We're working on a fix in #45

Hey @derekr a fix is available in 1.2.6. Could you try it out and verify if it resolves this issue?

@logason that seems to have fixed it! Thanks for the quick turn around.

Awesome @derekr, thank you for acting fast on trying it out! 💃


rename display.binaryPrefix to display.size.binaryPrefix - does not work in config.jsonc [BUG]

Be sure to read the FAQ before submitting a new issue.

General description of bug:
Updated to 2.19.0-1 from 2.18.1-1 on Arch Linux saw this message:
Jsonconfig Error 'display.binaryPrefix' has been renamed to 'display.size.binaryprefix' Sorry for another break change.

What happened: I modified the config.jsonc from
"binaryPrefix": "jedec" to "display.size.binaryPrefix": "jedec" and I received the error: Jsonconfig Error: Unknown display property
What should happen: Fastfetch should work as expected and display memory and disk as GB not GiB
Fastfetch version used:  2.19.0 x86_64
Did it work in an older version:  yes 2.18
Where did you get the binary:  Arch repo using pacman
Does this issue still occur in the latest dev build?

Often helpful information:
Screenshot:

The content of the configuration file you use (if any):
// Paste here

},
12    "display": {
13    "separator": " - ",
14    "binaryPrefix": "jedec"
15    },
Output of fastfetch -c ci.jsonc --format json:

// Paste here

Output of fastfetch --list-features:
// Paste here

If fastfatch crashed or froze
Paste the stacktrace here. You may get it with:
# You may need Ctrl+C to stop the process if it freezes
gdb -q -ex 'set confirm off' -ex run -ex 'bt full' -ex quit --args /path/to/fastfetch

If you are able to identify which module crashed, the strace can be helpful too
strace /path/to/fastfetch --multithreading false -s {MODULE} --pipe

If you cannot do the instructions above, please upload the core dump file:
If fastfetch is slow
Use time fastfetch --stat to show time usage for each module.
If an image or logo didn't show

The image protocol you used:
The terminal you used:
Upload the image file here, or paste the image URL:
Does it work with --logo-width {WIDTH} --logo-height {HEIGHT}?

If fastfetch behaves incorrectly on shell startup

The bug is reproducible with a clean shell configuration (i.e. fastfetch is the only line in .zshrc or ~/.config/fish/config.fish):
Does sleep 1 before running fastfetch work?

I figured it out.
New code:
"size": {"binaryPrefix": "jedec"}


Discuss: For v5, start requiring folks to use ALKILN_ at the start of their env vars?

To make sure devs don't override important env var values, like PATH, etc. [with their custom secret/sensitive env vars. E.g. vars like usernames and passwords, or whatever else they want to keep private or set in their environment.]

Quick summary of an conversation about this:
We are already filtering out things like PATH in ALKilnInThePlayground. Those variables, if they cause issues, would already have been causing issues on github too.
Reasons to force ALKILN_ at the beginning of vars:

we can't possibly know all of the env vars that are used in other programs or libraries, and there will be new ones added often.
debugging these issues could be rather confusing, and take a while to figure out the bug (though we haven't seen anything like this in the wild yet).

Reasons to not:

counter to 1) above: most libraries we use, like cucumber and puppeteer, do and will continue to prefix their env vars, like CUCUMBER_. So folks shouldn't run into issues there, and we can add those prefixes to the "dangerous_env_var_list" in ALKilnInThePlayground.
We'd make people invest of lot of effort now (and likely continued effort) to change and keep using ALKILN_ vars everywhere.
we could warn folks to change their variables, without making forcing it or breaking people.

We generally landed not forcing this, implementing 3) in the meantime, and seeing what happens.


Add support for critical fileystems thresholds

Currently we do only create warning alarms which do not trigger core.
I added configurable warning and critical thresholds. Critical thresholds will also set off core.
Additionally we are working in getting warnings into core as well for our devices

@b3rnard0 @BjoernT Going to bump this to 10.1.7. Because the backport needs to be worked back into OSAD and rpc-maas repos for Juno, this is going to take a bit longer.

@claco That's ok

Juno will be tracked at https://bugs.launchpad.net/openstack-ansible/+bug/1455999 since it still belongs to osad. I guess we can remove the juno-backport-potential tag


Variables are being coerced into strings by apollo-client in some situations

Hi,
I am noticing that the variables passed to a query are being coerced. I would like to know whether this is intended behavior or it is an error? Here is an example:
    const query = gql`
      query authorDetails ($id: String) {
        author(id: $id) {
          name
          books {
            id
            title
          }
        }
      }
    `;

    client
      .query({ query, variables: { id: [1, 2, undefined, null, {}] } })
      .then(handleSuccess)
      .catch(logError);

In the above case, my resolver on the backend receives args of { id: '1,2,,,[object Object]' }. Not sure if it is this package or apollo-server that is doing coercing the id to string. I would normally expect something like this to throw an error.
I would appreciate if someone can clear this for me. Thanks for the great package.

I don't think doing type checking on the variable values should be Apollo Client's responsibility - it should simply follow the query structure.

Fair, we can leave it at that. However, this is a desireable check. I can even do the check on the application side but the issue is that after the coersion I have less information about the incoming parameter. This I think is a bad default. So i am enquiring which package is doing that?

I think this is something your server is doing. Apollo client simply JSON-serializes the variables and passes them down, which shouldn't be doing any coercion.
Are you using grpahql-js?

I'm using apollo-server with express

I think I'd be surprised if this was done by apollo client. Have you tried putting in similar variables in GraphiQL and seeing if the same thing happens?

Okay, i can check that and report back in the evening. Thanks for the suggestion.

Hi, reporting back. The issue does not occur through graphiql.
Here is my query in graphiql
{
  author(id: [1, 2, undefined, {}]) {
    name
    books {
      id
      title
    }
  }
}

The response is:
{
  "errors": [
    {
      "message": "Argument \"id\" has invalid value [1, 2, undefined, {}].\nExpected type \"String\", found [1, 2, undefined, {}].",
      "locations": [
        {
          "line": 2,
          "column": 14
        }
      ]
    }
  ]
}

Note: I skipped the null value from my original example above as that causes a SyntaxError in graphiql.
Thanks for taking a look at this.

@a-s-o wait a second, this doesn't quite reproduce. Can you pass the id in the variables panel of GraphiQL? Instead of inline in the query? And see if it still works the same.

One of the solutions that we can implement here, is a quick check of variables, according to their declared type. If the type is something simple like String! or Int!, it is fairly easy to check.

We've done some testing with other GraphQL servers available and it seems to be the problem of the graphql reference implementation? Here is a link that demonstrates the same problem: link. Here is another link with a pad that demonstrates correct type checking in case of an inline array: link.
Type checking is not a responsibility of the client. Although, I have implemented some simple type checking in #522, we are thinking twice before merging it to master.

This is confirmed as an issue with GraphQL-JS itself, and therefore an issue with any JavaScript GraphQL server based on it; read below.
Here's the file where the parsing for scalar types is defined. You can see:

parseValue simply coerces to a string no matter what, this is what is used for variables
parseLiteral actually checks the type of the AST node, this is used for the inline arguments

I'd say we should report this issue on graphql-js, and perhaps submit a PR, since it's definitely unexpected to me that there is no validation at all on strings or numbers passed via variables.


[BD-6] Run tests with python3.8

Thanks for the pull request, @morenol! I've created BLENDED-383 to keep track of it in Jira.
When this pull request is ready, tag your edX technical lead.


Capybara possibly not passing form values to Devise

I have a integration spec for testing a Devise signup:
it "by visiting and filling out the signup page" do
  visit new_member_registration_path
  fill_in('Name:',                     :with => 'Rob Doe' )
  fill_in('member_email',              :with =><EMAIL_ADDRESS>)
  fill_in('member_email_confirmation', :with =><EMAIL_ADDRESS>)
  fill_in('member_password',           :with => 'secret')
  fill_in('Company or Venue Name:',    :with => 'Venue Name')
  fill_in('Contact Number:',           :with => '040544404440')
  click_button('Sign up')
  page.current_path.should == root_path
end

In a browser, this process fill out a form and redirects to the root_path.   In this spec, however the email and password fields are left blank when the form is posted, resulting in validation errors.  I know they are getting filled in to the field as when I save_and_open_page before the click_button they are all there.
I've tested this in Rails 3.0.7 and Rails 3.1.0.rc1    with both rack-test 0.5.7 and rack-test 0.6.0 with the same error

;m having the same issue as above
not sure if this is capybara specific or not?


Implement deleting a privacy declaration

Is your feature request related to a specific problem?
We don't currently have a way to delete privacy declarations. We need to add that flow.
Describe the solution you'd like
Privacy declarations are an array field on systems, so we'll likely have to do some filtering to implement this.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
https://github.com/ethyca/fidesplus/issues/598

Closed by https://github.com/ethyca/fides/pull/2664


Constant propagation for addition

@facebook-github-bot import

gonna close this for now, but you can reopen when you come back to it


Welcome release source code and pretrained model, Thanks

Dear Friends,
Thanks your great work, as title, welcome you release code as soon as possible.
Many thanks.

Hi there,
Thanks for your interest - we are intending to release the code in the next few months with a fully updated version and some more interesting results.

Thanks your great work,  as title, welcome you release code as soon as possible.

Curious how it's going :)

Thank you for your interest in this work. We have initially uploaded the source code. However, it's not the final optimal one. If there are any issues plz contact me. Thanks


Async write transactions ObjC API

This pull request to enable asynchronous transactions in Objective-С SDK. The feature will be exposed to Swift SDK in the later pull requests.
    [realm asyncTransactionWithBlock:^{
        [StringObject createInRealm:realm withValue:@[@"string"]];
    } onComplete:^{
        // optional handling
    }];

    [realm beginAsyncWriteTransaction:^{
        [StringObject createInRealm:realm withValue:@[@"string"]];
        [realm commitAsyncWriteTransaction];
    }];

    RLMAsyncTransactionId asyncTransactionId = [realm beginAsyncWriteTransaction:^{
        // ...
    }];
    [realm cancelAsyncTransaction:asyncTransactionId];

Why is there a projection test failing?

You need to add REALM_ASYNC_WRITES to the Package.swift file testCxxSettings so that your tests are ran at least for SPM.


Fix optimum model inference compatibility with transformers >= v4.30.0

In this PR we add a workaround to fix pipeline inference with optimum models compatibility with transformers>=v4.30.0. Coming from infer_framework  which should be modified to be compatible with optimum models

A test appears to fail:
2023-06-13T11:46:36.1199562Z FAILED exporters/onnx/test_exporters_onnx_cli.py::OnnxCLIExportTestCase::test_trust_remote_code - AssertionError: 0 is not true : 1

A test appears to fail:
2023-06-13T11:46:36.1199562Z FAILED exporters/onnx/test_exporters_onnx_cli.py::OnnxCLIExportTestCase::test_trust_remote_code - AssertionError: 0 is not true : 1

This is not related to the fix added for Optimum's model inference but directly from https://github.com/huggingface/transformers/pull/23959 and our test which checks that loading this model shouldn't be possible without setting the option trust_remote_code=True (now possible since https://github.com/huggingface/transformers/pull/23959)


chore(deps): update common-dev-assets digest to 3d44f8a

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
d3a341c -> 3d44f8a

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 1.1.13 :tada:
The release is available on:

GitHub release
v1.1.13

Your semantic-release bot :package::rocket:


Problem setting up the environment on Windows 10

I follow the next steps to setup Youtube GPT on Windows
Python = 3.7
Pip = 10.0.1

Steps

Clone repo
Setup virtual environment with python -m venv myenv
Activate environment /myenv/Scripts/activate.bat
Install dependencies pip install -r requirements.txt
Execute streamlit run app.py

When i execute the last step, i got the following traceback:
  File "C:\Users\ignac\AppData\Local\Programs\Python\Python37\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Users\ignac\AppData\Local\Programs\Python\Python37\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Projects\repos\desktop\youtube-gpt\myenv\Scripts\streamlit.exe\__main__.py", line 5, in <module>
  File "c:\projects\repos\desktop\youtube-gpt\myenv\lib\site-packages\streamlit\__init__.py", line 55, in <module>
    from streamlit.delta_generator import DeltaGenerator as _DeltaGenerator
  File "c:\projects\repos\desktop\youtube-gpt\myenv\lib\site-packages\streamlit\delta_generator.py", line 193, in <module>
    DataFrameSelectorMixin,
  File "c:\projects\repos\desktop\youtube-gpt\myenv\lib\site-packages\streamlit\delta_generator.py", line 328, in DeltaGenerator
    def __getattr__(self, name: str) -> Callable[..., NoReturn]:
  File "C:\Users\ignac\AppData\Local\Programs\Python\Python37\lib\typing.py", line 755, in __getitem__
    return self.__getitem_inner__(params)
  File "C:\Users\ignac\AppData\Local\Programs\Python\Python37\lib\typing.py", line 251, in inner
    return func(*args, **kwds)
  File "C:\Users\ignac\AppData\Local\Programs\Python\Python37\lib\typing.py", line 774, in __getitem_inner__
    result = _type_check(result, msg)
  File "C:\Users\ignac\AppData\Local\Programs\Python\Python37\lib\typing.py", line 135, in _type_check
    raise TypeError(f"Plain {arg} is not valid as type argument")
TypeError: Plain typing.NoReturn is not valid as type argument

Try with Python 3.9 or higher


[iOS] AppStore: ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _ptrace.

ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _ptrace. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/Though you are not required to fix the following issues, we wanted to make you aware of them:ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.
ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _ptrace. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/Though you are not required to fix the following issues, we wanted to make you aware of them:ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.

ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _ptrace. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/Though you are not required to fix the following issues, we wanted to make you aware of them:ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.

i have submitted release build but by default it takes debug build

Hi @Mallika-Tung
does this workaround work for you?
If it doesn't could you please provide
your updated  flutter doctor -v?
Thank you

I have not used UIWebview in the entire project .Even no third party plugin also does not using UIWebview ,still it warning coming.
ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs .

possible duplicate https://github.com/flutter/flutter/issues/37850

Yes, duplicate of https://github.com/flutter/flutter/issues/37850.


cover art download and if possible retain capitalization of track titles

I'll submit a pull request if I can figure it out

in the meantime there should be plenty of programs out there to complete metadata and rename by metadata

artist, album and track titles should be fixed now.
please rename the issue if it works for you. (see readme.md for information on how to upgrade)
In the future please open one issue per request/problem.


[BUG] "Casting between unsupported types" error for fixed type and index type

Describe the bug
I'm trying to write something that uses a Fixed(32, 24) type and a Fixed(64, 48) type for data. In a loop, I have a variable step that increments in the loop and is of type Index. I'm trying to perform an operation (add) with the Fixed(32, 24) type and the Index type, and store the result in the Fixed(64, 48) variable. However, I get the error "[Data Type] Casting between unsupported types. src type: index, dst type: fixed(58, 24)". I tried changing the type of the destination variable to Fixed(58, 24), but that resulted in the same error, so I'm guessing that the issue is in the add operation between the Fixed(32, 24) type and the Index type. However, this doesn't seem to strictly be an add issue either, since originally it was a shift operation, but that still gave the same error.
To Reproduce
import allo
from allo.ir.types import int32, bool, index, Fixed, float32

theta_type = Fixed(32, 24)
mult_type = Fixed(64, 48)

def test(theta: theta_type):
    current_sin: theta_type = 0.0
    for step in range(20):
        mult_intermed_cos: mult_type = 0.0
        mult_intermed_cos = current_sin + step

s = allo.customize(test)
print(s.module)
mod = s.build(target="llvm")

Buggy output
raise DTypeError(allo._mlir.exceptions.DTypeError: [Data Type] Casting between unsupported types. src type: index, dst type: fixed(58, 24)
Expected behavior
Expect the program to run correctly, and for the types to automatically cast so that the correct result is stored in mult_intermed_cos with the Fixed(64,48) datatype.

Hi @cshi15, thanks for raising the issue. Currently there is no direct casting from index type to fixed type in Allo, which will be added later. A temporary workaround is to explicitly cast step to integer type, i.e., int(step)

Thank you, that works for the add operation! However, when I changed it back to the shift operation (<<), I got the following RuntimeError: Typing rule is not defined with input types (<class 'allo.ir.types.Int'>, <class 'allo.ir.types.Fixed'>). If I cast current_sin as an int, it runs, but I'm not sure if casting this way would lead to incorrect behavior? I'm generally confused about when I need to cast and when I don't, and if it's possible to cast something as an Allo dtype (for example, casting something as Fixed)

Hi @cshi15, this is not a very common use case. In Allo, we suppose both operands of the << are integers. Can you tell us what you plan to do here?
In general, Allo does not require users to write explicit data casting as long as there exists a valid casting rule. We mostly follow the C/C++ convention to construct the casting rules. If some types are not supported by the operation, then Allo will error out just like this case.

@cshi15 wants to use this for a cordic core so the val >> n is essentially shorthand for dividing by 2^n. This is something Vitis HLS supports but I understand if you don't want to allow this. Will allo do strength reduction for dividing by 2^n?

@andrewb1999 thanks for clarifying! I just implemented the fixed point shifting operations in Allo (#243). @cshi15 Please pull the latest commit, reinstall Allo by pip install -v -e ., and try again for this case. The generated module is listed below for your reference:
module {
  func.func @test(%arg0: !allo.Fixed<32, 24>) attributes {itypes = "s", otypes = ""} {
    %cst = arith.constant 0.000000e+00 : f32
    %0 = allo.float_to_fixed(%cst) : f32 -> !allo.Fixed<32, 24>
    %alloc = memref.alloc() {name = "current_sin"} : memref<!allo.Fixed<32, 24>>
    affine.store %0, %alloc[] {to = "current_sin"} : memref<!allo.Fixed<32, 24>>
    affine.for %arg1 = 0 to 20 {
      %cst_0 = arith.constant 0.000000e+00 : f32
      %1 = allo.float_to_fixed(%cst_0) : f32 -> !allo.Fixed<64, 48>
      %alloc_1 = memref.alloc() {name = "mult_intermed_cos"} : memref<!allo.Fixed<64, 48>>
      affine.store %1, %alloc_1[] {to = "mult_intermed_cos"} : memref<!allo.Fixed<64, 48>>
      %2 = arith.index_cast %arg1 : index to i32
      %3 = affine.load %alloc[] {from = "current_sin"} : memref<!allo.Fixed<32, 24>>
      %4 = allo.shl_fixed(%3, %2) :(!allo.Fixed<32, 24>, i32) -> !allo.Fixed<32, 24>
      %5 = allo.fixed_to_fixed(%4) : !allo.Fixed<32, 24> -> !allo.Fixed<64, 48>
      affine.store %5, %alloc_1[] {to = "mult_intermed_cos"} : memref<!allo.Fixed<64, 48>>
    } {loop_name = "step", op_name = "S_step_0"}
    return
  }
}

Feel free to comment if there are additional issues.


Bump rekor, fulcio, sigstore deps to avoid pulling in vulnerable go-tuf version.

Summary
go-tuf has a vulnerability assigned: GHSA-66x3-6cw3-v5gj.
The versions of github.com/sigstore/fulcio, github.com/sigstore/rekor, and github.com/sigstore/sigstore still pull in the vulnerable version.
By bumping those versions, the vulnerable versions will not be pulled in anymore.
Release Note
NONE

Thanks for the change! Some test failures.
FWIW, only Cosign actually uses go-tuf directly and was affected.

@haydentherapper thanks for the quick update! I've fixed the tests + run the deps update.

I think this one can be closed now.


GPIO Viewer

In file included from C:\Users\jhmax\AppData\Local\Temp.arduinoIDE-unsaved2024124-5872-1df5n7z.rb36\gpioviewer\gpioviewer.ino:8:
c:\Scatchbook\libraries\GPIOViewer\src/gpio_viewer.h: In member function 'int GPIOViewer::readGPIO(int, uint32_t*, pinTypes*)':
c:\Scatchbook\libraries\GPIOViewer\src/gpio_viewer.h:525:33: error: 'analogGetChannel' was not declared in this scope; did you mean 'analogChannel'?
525 |         uint8_t analogChannel = analogGetChannel(gpioNum);
|                                 ^~~~~~~~~~~~~~~~
|                                 analogChannel
exit status 1
Compilation error: exit status 1
Hi everyone, I'm trying to install the GPIO Viewer on the ESP32 Dev Module and it keeps giving me this error, can you please advise me what I'm doing wrong when I did everything according to the instructions and the Youtube video? Thank you and have a nice day.

Your probably not on the latest version of ESP32 boards for Arduino.  Update to the latest version.

In file included from C:\Scatchbook\gpioviewer\gpioviewer.ino:8:
c:\Scatchbook\libraries\GPIOViewer\src/gpio_viewer.h: In member function 'int GPIOViewer::readGPIO(int, uint32_t*, pinTypes*)':
c:\Scatchbook\libraries\GPIOViewer\src/gpio_viewer.h:525:33: error: 'analogGetChannel' was not declared in this scope; did you mean 'analogChannel'?
525 |         uint8_t analogChannel = analogGetChannel(gpioNum);
|                                 ^~~~~~~~~~~~~~~~
|                                 analogChannel
exit status 1
Compilation error: exit status 1
https://docs.espressif.com/projects/arduino-esp32/en/latest/installing.html
I tried the ESP update from this page, then restarted the Arduino IDE and it says this. I'm already an old man of 60 years, so I can't move about it somehow :-( Thank you for your effort!

You have to do the board update through the Arduino IDE in the boars manager.

Do you have a name please, besides the ones I have installed?

Do you have a name please, besides the ones I have installed?

You have an alpha version installed (3.0.0a) in the dropdown menu, choose version 2.0.14

I don't have this version.

2.0.11 should work

Bingo! It works! Thank you very much for your quick help and have a nice night! Greetings from the Czech Republic! Hello!

Glad it works!


kv_cache dir error

❓ General Questions
Can Someone explain the create_tir_paged_kv_cache error? I was once able to build my android app correctly and now upon reconstructing this .tar file and implementing it into my app, I get this error related to create_tir_paged_cache requires 4 inputs but only 0 inputs were provided. Pointers are greatly appreciated!

Updated my android submodule and that solved it. I guess I could Update the CMAKE list to point to the TVM I created from source (Which I needed to create the android.tar file) hope this helps someone!


Update go.mod

Previous version used a grailbio/base and v.io/v23 that were broken.
Also gogo proto needs to be a 1.3.1 now.

The tests don't pass, but at least it builds now.


🌱 Update helm chart index.yaml to v0.14.0

What this PR does / why we need it:
This PR updates index.yaml for v0.14.0. Automatically generated by make update-helm-repo.

/lgtm
/approve


Domoticz code not working due to refresh token (where to find, no explanation given)

In the DOMOTICZ system i need to fill in a Refresh Token ... where do i find it and to my knowledge it is only generated after i have access the system for the first time ... but the system will not start without that ... what do i do wrong?

Feedback for Flopp999 on NIBEUplink plugin for Domoticz
In case of manual installing:
Put plugin.py, requirements.txt and NIBEUplink.zip in that folder.
The first time I ran this I did not have the .zip file and the plugin
stopped at that point with an error message.
With the authorization, I could do the things you advised, including
copying the code from the low, I however found the following errors:
021-10-17 10:55:19.630 NIBE FLOPP: (NIBE FLOPP) Systems found:2
2021-10-17 10:55:22.313 NIBE FLOPP: (NIBE FLOPP) SMO40 Updated
2021-10-17 10:55:49.239 Error: (NIBE FLOPP) Device creation failed,
Hardware/Unit combination (2:222) already exists in Domoticz.
2021-10-17 10:55:50.669 NIBE FLOPP: (NIBE FLOPP) F2120 Updated
2021-10-17 10:55:50.266 Error: CPlugin:CDevice_init, illegal Unit number
(256), valid values range from 1 to 255.
2021-10-17 10:55:50.267 Error: Device refresh failed, Device object is not
associated with a plugin.
2021-10-17 10:56:20.527 NIBE FLOPP: (NIBE FLOPP) SMO40 Updated
2021-10-17 10:56:49.674 Error: CPlugin:CDevice_init, illegal Unit number
(256), valid values range from 1 to 255.
2021-10-17 10:56:49.674 Error: (NIBE FLOPP) Device creation failed,
Hardware/Unit combination (2:-1) already exists in Domoticz.
IDx 79 is weird:
79
NIBE FLOPP
-1
NIBE FLOPP - version
Interface Control
Unknown
0,
Hope this helps, I renamed the systems to what my system has (SMO40 and
F2120), now I have to figure out what the error messages are …
Op wo 13 okt. 2021 om 21:03 schreef flopp999 @.***>:

no problem, do that in the weekend and reply
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flopp999/NIBEUplink-Domoticz/issues/32#issuecomment-942626959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV6HLCXV2K6VYOFGH3GSAKDUGXJXRANCNFSM5FPNNZ4A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

missing ZIP-file is fixed in version 0.88 https://github.com/flopp999/NIBEUplink-Domoticz/tree/0.88
Last week I came up that there will be problem with system 2 and higher. Since there is 127 IDs for System 1 and then I just add 130 to the IDx for System 2, this creates an error since there is a risk that ID 127 + 130 will be used in System2
Would it be possible for you to send a list for all IDx you have for NIBE plugin, then I maybe can find a solution. Thanks

Hi Flopp999,
I've been trying to get your script working and i manage to get the initial reading working and getting the values from my nibe system. But the problem i have is it will not refresh the data, and I'm not sure where to find the refresh token?
The log file states the following:
2021-12-10 03:27:27.160522 ===onStart===
2021-12-10 03:27:27.160656 Refresh too short
2021-12-10 03:27:37.092566 onHeartbeat
2021-12-10 03:27:37.242625 onConnect
2021-12-10 03:27:37.242969 Entered CheckInternet
2021-12-10 03:27:37.243092 Ping
2021-12-10 03:27:37.369153 Internet is OK
2021-12-10 03:27:37.369473 Get Token
2021-12-10 03:27:37.420691 Status = 400
2021-12-10 03:27:37.421414 onDisconnect called for connection 'Get Token'.
I've set something random in the refresh filed to get it to start, but i just can't seem to get my head around where the refresh token is, could you please help me out?
regards,
Z

Hi zeebos,
what version do you use?
When you start the plugin it should print the Refresh token in the DZ log.

Hi flopp999,
Thank you for answering, I'm running 0.89 version. And thank you for point out the obvious, if you look you find...appologies for my lack of eye sight. Thank you for great work, very appriciated!

Hi @flopp999,
I can ont find the refresh token in the DZ log... What should I look for?
2022-01-07 19:49:49.682 Error: NIBEUplink: (NIBEUplink) Status 400
2022-01-07 19:49:49.683 Error: NIBEUplink: (NIBEUplink) {'Status': '400', 'Headers': {'Cache-Control': 'no-cache, no-store, max-age=0, must-revalidate', 'Pragma': 'no-cache', 'Content-Length': '27', 'Content-Type': 'application/json; charset=utf-8', 'Server': 'Microsoft-IIS/10.0', 'X-AspNetMvc-Version': '5.2', 'X-AspNet-Version': '4.0.30319', 'X-Powered-By': 'ASP.NET', 'Set-Cookie': ['ARRAffinity=65ae3a5d9eea21abf7c1467a88d0de16bfb107af58080e2103c4141da03474d1;Path=/;HttpOnly;Secure;Domain=api.nibeuplink.com', 'ARRAffinitySameSite=65ae3a5d9eea21abf7c1467a88d0de16bfb107af58080e2103c4141da03474d1;Path=/;HttpOnly;SameSite=None;Secure;Domain=api.nibeuplink.com'], 'Date': 'Fri, 07 Jan 2022 18:49:48 GMT'}, 'Data': b'{"error":"invalid_request"}'}

Hi
Did you follow all steps?
Did you get a long token when you get the token in the address bar?

Hi @flopp999,
I would say yes. I followed all the steps it is only the refresh token that is missing. I would say?
Any suggestion on what could be wrong?
Thanks.

Same here, I got the access code from the address bar, and the module does retrieve data.
But I couldn't find and refresh token in the logs. And when Domoticz is restarted the connection is lost.

it is working for me

Do you get any error codes that would be helpful

Hi, thanks for your fast reply!
This is a copy-paste from the logs.
2022-01-09 21:50:16.204 Status: Nibe: (Nibe) Started.
2022-01-09 21:50:16.204 Status: Nibe: (Nibe) Entering work loop.
2022-01-09 21:50:17.568 Status: Nibe: (Nibe) Initialized version 0.89, author 'flopp999'
2022-01-09 21:51:57.604 Error: CPlugin:CDevice_init, illegal Unit number (256), valid values range from 1 to 255.
2022-01-09 21:51:57.615 Error: Device refresh failed, Device object is not associated with a plugin.
2022-01-09 21:52:07.814 Error: CPlugin:CDevice_init, illegal Unit number (256), valid values range from 1 to 255.
2022-01-09 21:52:07.815 Error: (Nibe) Device creation failed, Hardware/Unit combination (18:-1) already exists in Domoticz.
There is a device added with idx -1 and the subtype and data field seem incorrect:
32563	Nibe		-1	Nibe - version	Interface Control	Unknown	0,

Hi @flopp999 ,
I got it working but I do not know what I made so it started working... I changed owner and access rights on some of the files in the NIBElink directory. I also fiddles with the settings in the plugin especially the last three parameters. Then at one place I got the refresh token in the log.
Thanks for the support


Change setting argument in rultor

@rultor merge

@rultor merge

@baudoliver7 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@baudoliver7 Done! FYI, the full log is here (took me 5min)


Previews for GIF

This library might be useful: https://github.com/koral--/android-gif-drawable

Extra: add toggle in Gallery mode, if the toggle is ON then animate GIFs (this should be persisted preference).

Implemented in:

#403


Fix decoding of AS-PATH for long-ish attr

The current implementation incurs counter wrap when the path is longer than an uint8.
I debugged using the following test-case, but I am not sure how to include it properly in the test-suite:
func TestASPathDecode(t *testing.T) {
	update := []byte{2, 72, 0, 0, 18, 29, 0, 0, 218, 13, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43, 0, 2, 82, 43}

	asPathAttr  := &ASPathAttr{}
	err := asPathAttr.Decode(PathAttrFlags(1<<6), update)
	if err != nil {
		t.Errorf("failed to decode: %s", err)
	}
}

thanks!


Excalidraw link not opening file?

I'm on 28.2 on a MacBook and everything's working well, except that I can't get the Excalidraw link to open after the file's been created and saved. Clicking on the link yields "No Match" and asks me to create a new header. Path, etc., are all correct and the file exists. Any hints?

I'm having a similar issue. Is there an configuration missing?

Same issue here. FYI, I have installed excalidraw as a PWA via chrome and I can double click the .excalidraw files and open them in chrome.

Are you sure the file was successfully converted to .svg?
I'm also on 28(doom) and Macbook Pro.
I've had some issues after installing(using brave instead of chrome doesn't work).
After switching to chrome, excalidraw_export command threw some errors so the .svg was not created.
It turns out --rename_fonts=true caused the issue, so I made a fork invoking this command without the flag.
After that, it started to work fine.

I think there should be this icon:

I'm on MacOS though, so maybe it's different

@PiotrBosak Thank you. It's hidden in the setting menu.

But how  strange it is there is no File handling API flag in chrome flag.


Removed the built-in overlay from ReorderableListView.

The current implementation of ReorderableListView creates its own Overlay widget to handle the dragging of its items. However, this is causing layout problems for apps that are trying to use shrinkWrap, as the overlay is not constrained.
This PR removes this and has the ReorderableListView depend on the surrounding overlay provided by MaterialApp. If one isn't found it will throw an error.
Fixes: #76150
I added a new test to verify an error if no surrounding overlay is found. Also removed two golden tests that would need to be updated as the dragged item is no longer painting in the list itself (they were of no real testing value either).
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

I thought there was a reason why we added the overlay (e.g. to make sure that you can't drag an item outside of the list). Why do we not need that anymore?

As far as I remember I had removed it, but we put it back near the end of development as it was causing some tests to fail or some other reason.
I don't think having a built-in overlay prevents the item from being dragged outside the list, as it doesn't appear to be clipping it (and I am not sure we would want it to from a UI perspective). The list already handles the case of dragging outside the list and just puts the gap at the edge of the list and the item will animate back to that gap if dropped outside the list.
In addition, it is inconsistent with the other two reorderable list widgets as they both rely on the surrounding overlay widget.
Therefore I don't see much value in keeping the build-in overlay here as it provides little value and is breaking the shrink-wrap case as it doesn't shrink wrap around the list.
Or am I missing something here?

I don't think having a built-in overlay prevents the item from being dragged outside the list, as it doesn't appear to be clipping it (and I am not sure we would want it to from a UI perspective).

I thought there was a comment in the code explaining why there is an internal Overlay, but looks like it got lost during the refactor. Prior to the refactor, this is what it said:
https://github.com/flutter/flutter/blob/ff05ca2503437ca35ea07551aeda5a6b1d5d35bb/packages/flutter/lib/src/material/reorderable_list.dart#L175
And looking at the Overlay I would expect it to be clipping (it's the default value for https://master-api.flutter.dev/flutter/widgets/Overlay/clipBehavior.html and we don't seem to change it...). Is that not working?
Whether not drawing outside the list itself is a bug or a feature, I actually don't know... The more I think about it the more I am leaning towards it should draw outside of the list. So, if that was the only reason, maybe we should remove it...

And looking at the Overlay I would expect it to be clipping (it's the default value for https://master-api.flutter.dev/flutter/widgets/Overlay/clipBehavior.html and we don't seem to change it...). Is that not working?

I just tried it and it seemed to paint the dragged item over the app bar and such just fine. I will take another look to see if I was just holding wrong or something.

Whether not drawing outside the list itself is a bug or a feature, I actually don't know... The more I think about it the more I am leaning towards it should draw outside of the list. So, if that was the only reason, maybe we should remove it...

That's pretty much the conclusion that led me to this PR. If you do come up with a case for the built-in overlay, just let me know.

I just tried it and it seemed to paint the dragged item over the app bar and such just fine. I will take another look to see if I was just holding wrong or something.

Ok, I checked again, and I was holding it wrong. It does clip, but as mentioned before I don't think that is the behavior we want here. It is inconsistent with the other reorderable list widgets and if someone really wants the dragged item to clip, they can wrap it with their own overlay.

Gold has detected about 6 untriaged digest(s) on patchset 2.
View them at https://flutter-gold.skia.org/cl/github/79024


Added support for requirements.txt

PR Checklist

[ ] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] Documentation in docs is updated

Description of changes

Added functionality to check which dependency specification format is used (pyproject.toml vs requirements.txt)
Added a requirements.txt parser

Codecov Report

Merging #84 (ffaa841) into develop (78884bf) will decrease coverage by 7.8%.
The diff coverage is 35.1%.

@@            Coverage Diff            @@
##           develop     #84     +/-   ##
=========================================
- Coverage     92.6%   84.7%   -7.9%
=========================================
  Files           24      26      +2
  Lines          718     822    +104
=========================================
+ Hits           665     697     +32
- Misses          53     125     +72

Impacted Files
Coverage Δ

deptry/dependency_management_detector.py
28.5% <28.5%> (ø)

deptry/requirements_txt_dependency_getter.py
31.8% <31.8%> (ø)

deptry/pyproject_toml_dependency_getter.py
76.0% <100.0%> (ø)

tests/test_cli.py
100.0% <100.0%> (ø)

tests/test_dependency_getter.py
100.0% <100.0%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Save as file and async

when i save as file , it use sync. how can i change .execute() to executeOnExecutor(AsyncTask.THREAD_POOL_EXECUTOR)?
i try to extend and overwrite the method but constructor is private

#97 Is the one I am going to merge it soon. So that It can be customizable.

I have the same issue and i extended the class to fix it. But there are more methods and variables which are not public to call from extended class. Methods on SaveSettings class, BitmapUtil class BrushDrawingView object and saveFilter method in PhotoEditorView.


Move SchemaRepository SQL Statements into SQLStatements static class

There are some SQL Statement still sitting in code. Move to SQLStatements static class.

Done.


errors in bash completions in zsh on macOS

Bash completions in zsh in macOS do not work correctly. the first command e.g. tid e[TAB] works correctly, but then the subcommands of this fail to load, instead the main commands are listed again as well as the following error:
_tid_get_args:2: bad option: -a

I had a quick look into the completions, and by changing
    IFS=", " read -r -a RAW_PATH <<< "$COMP_LINE"

to
    IFS=", " read -r -A RAW_PATH <<< "$COMP_LINE"

the issue was fixed. I do not however know the implications of this on the bash completions on other platforms.

Hmm, perhaps we can just copy tid.bash to tid.zsh, change that and call it a day?

I suppose so, it's a shame to need to do it for a small case change though :/

I did check, and it would break bash, unfortunately :(


WIP: add indoclink for fixing multilingual linking issue.

This PR is trying to fix #18403, I am not sure whether it is the best solution, but it did work, as we:

keep same link content for english and other languages, no need to change for each l10n team;
if there is no content under current dir, it would NOT throw error like ref and relref did;
the custom shortcode indoclink is maintained by us, not hugo bulitin shortcode, that means we could do more things about customization without upstream support.

Thanks.

For demo purpose, I edited content/zh/docs/concepts/scheduling/kube-scheduler.md and content/en/docs/concepts/scheduling/kube-scheduler.md, it would be removed after we agreed this proposal.
And I would also add relative guide inside localization for document, so this linking issue should NOT trouble our contributors next time.

/cc @tengqm  @sftim

What's indoclink short for? I couldn't work it out.

@sftim, in-doc-link? Perhaps the name could be changed (lang_prefix)
@Colstuwjx , the shortcode seems to prefix the lang string to the link (which is a manual process now)? Is it possible to use Hugo's ref shortcode?

As I understand it, SIG Docs has settled on leaving the Markdown as normal markdown and instead addressing localization and fallback to English via custom rendering to HTML.
With that in mind @Colstuwjx, are you OK to /close this?

Yes, totally understand.


🔗 replace supportedChains with networks in config

related to #408
Breaking changes:

deprecated supportedChains props in Config
deprecated chain helper functions
Change ChainId type to number
move Chain, Config types to packages/core/src/constants/types for outside access

New:

add a new networks: Chain[] prop in Config to accept any Configs define in packages/core/src/model/chain (or outside Config when ready)
expose networks with const {networks} = useConfig()

Misc:

doc update
put chain-specific tests to separate files

@gasolin is on fire 🔥 🔥 🔥
I will find time today or tomorrow to review it :)
Don't forget about emoji in description :D

@tt-marek any suggestions?

@gasolin Great work. Added a few comments. This is a bit tricky refactoring, I think we should not break compatibility completely in one step. Let me know what you think about comments.

@tt-marek comment addressed, please review again

looking forward, will this support useDapp to be able switching between multiple networks and provide your own network such as smartBCH?

looking forward, will this support useDapp to be able switching between multiple networks and provide your own network such as smartBCH?

not yet because of backward compatibility, but will make it way easier to provide your own network in the next major version
for switching between multiple networks, could take a look https://github.com/EthWorks/useDApp/issues/416

no problem from reading on multiple networks and having a switch, the problem is when sending transaction (useContractFunction) gives an error same as here: https://github.com/EthWorks/useDApp/issues/297 (trying with network 10000, smartBCH)
would it be better to open PR with new chain or wait for the update so can do useContractFunction properly?

@marekkirejczyk any feedback for this PR?

cool its merged! so now is it possible to specify own custom chain?
if so, does this require to use networks  property in config?
would love to see an example!

We still need:

test the newest version on master (lot's of changes, sanity check)
add changset and publish npm
a quick tutorial adding a network to a project
a quick tutorial adding a network to useDApp

@gasolin
Thank you for the great work! ❤ Sorry for being slow to review. Promise I'll do better 🙏
Would you like to take on any of 1,3,4?

@gasolin I published npm, however ChainId is still enum, do you want to work on it?

@gasolin Thank you for the great work! ❤ Sorry for being slow to review. Promise I'll do better 🙏 Would you like to take on any of 1,3,4?

will check if I can do some doc improvement


Feature request: load whole request from a file

It's possible that HTTPie has such a feature already, but I was unsuccessful in trying to find it.
What enhancement would you like to see?
To have a possibility to load the whole request (URL, HTTP method, headers, payload, etc.) from a file.
What problem does it solve?
The use case is to have a library of requests stored as a hierarchy of directories and files. It should be platform-independent, so it works with HTTPie on any platform it runs on.
What is it good for?
When working on an API project, I want to have a library of API requests consisting of prepared complete request files that I can simply execute using HTTPie, so I don't have to look for URLs, headers, parameters, payloads, etc. in documentation or even in a source code every time I need to make a request.
Such library for a single project may look like the following:
project
|
+ users
| |
| + create.http
| + update.http
| + delete.http
| + list.http
|
+ products
  |
  ...

Currently, I'm always creating such a library for API request payloads, storing them in files. But that's not enough to make a request. I still have to look what URL, headers, and other parameters a specific API endpoint or request requires. I can have a separate library of HTTPie commands for each payload or search them in the shell history, but it would be great to have a single file containing everything needed to make a valid API request, so the only information I need to provide to HTTPie is that file:
http --request project/users/list.http

HTTPie is currently even able to create those request files (see below), I just didn't find a way to load them.
Provide any additional information, screenshots, or code examples below
Possible solution using shell script
An easy solution would be to store request commands as shell scripts, for example project/users/create.sh might contain the following:
http [parameters] [method] <url> < ./create.json

I would have two files for each request – a shell script and a payload file (if it needs one).
The problem with this solution is that it's platform-dependent. Those shell scripts would work with bash only.
Proposed solution
I have managed to find a feature that is basically doing the first half of what I need. It's the Offline mode and the --offline parameter. The following command saves the whole request including the payload into the file request.http (without actually sending any request):
http --offline [parameters] [method] <url> < payload.json > request.http

The file it produces contains the whole RAW HTTP request as is being sent, everything needed to make a request:
POST /api/endpoint HTTP/1.1
User-Agent: HTTPie/2.3.0
Accept-Encoding: gzip, deflate
Accept: application/json, */*;q=0.5
Connection: keep-alive
Content-Type: application/json
Content-Length: 8
Host: test.dev

payload

It's possible to send such request using for example netcat:
nc <domain> <port> < request.http

But I didn't find a way to do the same with HTTPie. I have tried the analogy to the nc command (http <domain> < request.http), but HTTPie considers the file to be just a payload.
I would like to have a possibility similar to the following:
http --request request.http

How I would expect it to work:

If a request file is provided, HTTPie reads all request parameters (URL, method, headers, payload, etc.) from there
If any parameter is provided on the command line, it overwrites the value from the request file

Current issues:

The URL parameter is mandatory. It would be nice to read it from the file also, but if it would be against the HTTPie's design, it wouldn't be a big issue. I can provide only the domain part in the URL parameter and have the whole URL path part loaded from the file.
HTTPie can save the request to a file but it cannot read it back, or I didn't find a way to do that.

Alternative solution
Everything is the same as in the proposed solution, but instead of RAW HTTP request data, the request file contains HTTPie parameters in some form (e.g. similar to default options in the config.json file).

Actually duplicates #758

@danslapman Yeah, it looks like the same thing, so this issue may be closed as a duplicate, thank you.

Closing as duplicate. Thanks for the request, though!


Build is not getting queued when 'VSTS Developer Tools Build Tasks' is added in TFS 2017 build definition

I have entered all required parameters and saves the task, When I clicked the “Queue new build” link it shows error message “There are issues with the request or definition….”, When I disable the task and Queue a build again it works fine. Please advise how to resolve this.
TFS Version : TFS 2017
Task Version: 1.1.41
Input file type: VSIX file

It looks like you're using the "Publish task"? Have you tried removing and re-adding the task?
Please post the Build Definition json for this task:

Like this, that should tell me exactly what values are configured:

And what also could help is if you can intercept the json reply that's generated when queueing the build using your browser developer tools or fiddler. It may contain more information about the issues with the definition.
If you want to send them offline, please send it to<EMAIL_ADDRESS>

I just tested the publish task on TFS 2017u1RC and that works as expected. I do get an error that my agent doesn't have npm installed, do you have Node installed and added to the %path% of the system or the service user so the build can find it?

@jessehouwing ,
Json from build definition:
{
   "enabled": true,
   "continueOnError": false,
   "alwaysRun": false,
   "displayName": "Publish Extension",
   "timeoutInMinutes": 0,
   "task": {
     "id": "xxx-xxx-xxx-xxx-xxx",
     "versionSpec": "*",
     "definitionType": "task"
   },
   "inputs": {
     "connectTo": "VsTeam",
     "connectedServiceName": "xxx-xxx-xxx-xxx-xxx",
     "connectedServiceNameTFS": "",
     "fileType": "vsix",
     "vsixFile": "C:\\Test\\Test.vsix",
     "rootFolder": "",
     "localizationRoot": "",
     "patternManifest": "vss-extension.json",
     "publisherId": "xxxxx",
     "extensionId": "",
     "extensionTag": "",
     "extensionName": "",
     "extensionVersion": "",
     "updateTasksVersion": "false",
     "extensionVisibility": "private",
     "extensionPricing": "free",
     "outputVariable": "",
     "shareWith": "",
     "arguments": "",
     "cwd": ""
   }
 }

Node server is installed in the TFS server and other build tasks are getting executed correctly.
Thank you,
Ranuka

Not seeing anything that stands out from the json that helps me diagnose the issue. Next step would be to get a fiddler trace from trying to queue the build when the definition is in broken state.

@jessehouwing : Found the issue Jesse, Issue is Node path was not added as you mentioned. Thank you.


Can't insert text where the cursor is

Hi,
I've got a few issues and I'm not sure what I'm doing wrong:

When I insert a code block, I cannot delete it. Sometimes it can be deleted, but most of the time I can't. It looks like if I press the backspace, it's deleting a white space and then loses focus.
I've got a custom  component that is supposed to add tags wherever the cursor is. It works fine with plain text, but once I add a code block, or table, it behave weirdly; it doesn't insert the tag where I click inside the block.
If I inserted a code block and I click above it to add a tag, if there's no text above the code block, the page breaks and returns the following error:

Uncaught Error: No CodeBlockEditor registered for language=null meta=null
at CodeBlockEditorContainer (CodeBlockNode.js:136:11)
at renderWithHooks (react-dom.development.js:16305:18)
at mountIndeterminateComponent (react-dom.development.js:20074:13)
at beginWork (react-dom.development.js:21587:16)
at beginWork$1 (react-dom.development.js:27426:14)
at performUnitOfWork (react-dom.development.js:26557:12)
at workLoopSync (react-dom.development.js:26466:5)
at renderRootSync (react-dom.development.js:26434:7)
at recoverFromConcurrentError (react-dom.development.js:25850:20)
at performSyncWorkOnRoot (react-dom.development.js:26096:20)

Hey, to help you further, please reproduce the problems you experience in a codesandbox, and give me some steps to reproduce. Chances are, you've encountered some bugs, but I do need to reproduce them on my side to resolve them.
Thank you,

Hi, Thank you very much for the prompt response. I might not be doing something right, but I'll try to be as explicit as possible and I'll also leave some comments in the code.
What I'm trying to achieve is that I want to have my own dropdown button with values that represents "tags" and if I click anywhere in the editor and then select the tag, I expect the tag to be inserted where the cursor was. Also, I would like to be able to delete the code blocks after inserting them and saving them into the DB, but for whatever reason, sometimes it works, and sometimes it doesn't; but most of the time it doesn't.
The codesandbox is this: https://codesandbox.io/p/sandbox/stoic-napier-232h24?file=%2Fsrc%2FApp.css%3A3%2C21
The code is inside App.tsx
The issues are the following:

If I add a code block and I want to add a “tag” from the "Tags" button, the page breaks.

If I add a "table" or an "admonition" and I try to add a “tag”, it behaves weirdly.

If I add a code block and I save it into the DB, next time when I refresh the page I can’t delete the code block. I think that might be due to the back-end parsing the code block in a way unsupported by the editor.

This is how it's being done with regards to the code block -

And this is what happens further.
a) Sent from the editor to the DB -

b) Received in the db -

c) Retrieved in the front end -

After this, I cannot delete the code block anymore. I managed to reproduce the error on the live demo on the editor's documentation page as well, but I'm not sure what caused it, because I can't do that anymore.
Thanks again.

Thanks for the reproduction instructions. I've traced down the problem to an erratic ref not being correctly passed by the code block editor. Will look for a solution, probably a button of some sort. It's a known issue with code mirror, unfortunately.
As per the sandbox - I'm afraid that the direction you've taken is not going to work out. The proper way to extend the editor is with plugins that interact with the lexical API, including its selection mechanisms and node insertion/manipulation. I understand that this takes a bit more of an investment, as you need to understand how the plugins work (looking at their source code is actually not so scary), and you need to learn a bit of Lexical if you're not familiar with it, however, the model is robust and solves quite a few problems.

Hi @petyosi ,
Thank you for your reply.
I'll choose a different approach for the "Tags" then.
However, I've found two more bugs in the documentation live demo:

Click in the middle of a text and insert a code block. Click on "Diff mode" and then click on "Rich text". The page breaks.
Click on an empty space, insert a code block, click underneath it and add some text. Click on "Diff mode" and then click on "Rich text" again. The code block extends and covers a lot of text underneath.

Thanks for reporting those! I just pushed a fix for it.


(1password) Fix 1Password installation regarding issue 1618

Description
I added the last line, which will execute the 1Password exe in the local Appdata with the arguments "setup" and "--silent" which will complete the installation and make it available to the user in the start menu and appwiz. This is probably not the prettiest solution but it works.
Motivation and Context
Open issue regarding this fix: #1618
How Has this Been Tested?
The installation was tested on a Windows 10 VM with the latest 1Password binary from the official source.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[X] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[X] All files are up to date with the latest Contributing Guidelines
[X] The added/modified package passed install/uninstall in the chocolatey test environment.
[X] The changes only affect a single package (not including meta package).

I've been trying to look at this since this morning (ie. 8 hours ago).

:x: Package verification failed, please review the Appveyor Logs and the provided Artifacts before requesting a human reviewer to take a look.


Silence the deployer ethers provider

Deployer sometimes outputs this to the terminal
========= NOTICE =========
Request-Rate Exceeded  (this message will not be repeated)

The default API keys for each service are provided as a highly-throttled,
community resource for low-traffic projects and early prototyping.

While your application will continue to function, we highly recommended
signing up for your own API keys to improve performance, increase your
request rate/limit and enable other perks, such as metrics and advanced APIs.

For more details: https://docs.ethers.io/api-keys/
==========================

The default provider needs to be overriden to silence this message:
https://github.com/ethers-io/ethers.js/issues/1036

Turning off all logs doesn't work
https://github.com/ethers-io/ethers.js/issues/379

There is probably no need to override anything. Simply make sure you pass in your own keys. Or if you do sub-class it, return your own default keys to the static getApiKey method. :)

@ricmoo Thanks for dropping by :)
This is a sort of a special case where the user doesn't know what an Ethereum provider is, doesn't have an API key to insert and will be running this only once (in a while).
We want to be more chain-agnostic anyway so I think we will move away from using the default ethers provider.

We're now using the provider URL from config.json
https://github.com/api3dao/airnode/commit/27f22f30c66708d51ae9409bf3ed28ed06487faf#diff-5663c2c90283b2e61f87d95800ccea766b06ceb858857e46acdb5e48840b6ea8R21


 In my experience contributors always fail this rule and have to then figure out how to amend their commit message and then how to force push to a branch.
All this has to be done by the new contributor before they can even see if their change passes in CI. This is not an experience that encourages new contributions and is unnecessary considering commit message formats can be trivially fixed by the maintainer when the PR is squashed+merged.
I vote for lowering the severity of this check from error to warning....and I am more than happy to manually communicate the guideline to the contributor in a comment in the PR. Anyone else agree or have an alternative suggestion?
@ipfs/javascript-team

Can we add the commitlint step as an allowed failure in Travis, so it's easier to see? I'm all for lowering the barrier of entry for this. My only concern is that if commitlint is a warning it's solely up to the maintainer to ensure they're correcting the commit on squash as we likely aren't going to see it in CI unless it's an error.
This isn't a huge concern though, I'd rather see this be made easier for contributors and risk the occasional oversight on merge.

That said it's pretty easy to add commit linting as a pre-push test and catch this stuff before it makes it to CI.

@achingbrain im in favor of a pre-push hook but this option still has the issue @alanshaw is talking about, even though the error printed to the terminal is very helpful and a link is also printed explaining everything.

what do you think, personally i like this ^^ instead of running it in the CI.

but this option still has the issue @alanshaw is talking about, even though the error printed to the terminal is very helpful and a link is also printed explaining everything.

As you mentioned I think this still has unnecessary friction for contributors. I think it printing as a warning is fine, but it shouldn't block pushes.

so commit lint as a warning
should we run it only on ci, only on git hook or both ?

Could the commit message lint be a separate step on travis that could fail independently? This would be a good indicator for the maintainers, but new contributors would still get feedback from the CI if the actual change is correct.
I would then expand it to a general lint step, with the commit message, dependencies and code linting.

I'm strongly against commitlint errors and warnings showing up on contributors PRs. It adds friction, is demoralising. I just experienced that trying to offer up an improvement js-cid.
My feeling is that we should be nurturing PRs from the community, and do everything we can to make that a plesant experience. As a maintainer, I review the PR, and communicate with the contributor about it until I am personally happy to merge it and take responsibility for the changes. That includes squashing the commits when merging a PR and ensuring the squashed commit message meets our guidlines.
That being the case, I'd like to reduce commit linting down to just changes to master. I'd be happy to remove it all together.

@olizilla Would that mean that I'd need to manually check a passing CI run to see if things pass the commit lint?

it means you need to squash and change the commit message to something good for the changelog

it means you need to squash and change the commit message to something good for the changelog

Yes, but I won't have an automatic indicator that the commit message didn't conform.

To me it feels like the easiest approach for this is to remove commitlint altogether and move to a squash only merge strategy for anyone who isn't already doing this. Lead maintainers should already be aware of the commitlint rules.
We could leave it on for master to at least be notified we're doing it wrong, but there is no corrective path for mistakes, which we have anyway with squashing. Since modifying commits in master is a no no, the best you get here is a note for next time to squash better.

so regarding this issue we are all in agreement right ?
each of us should change .travis.yml accordingly

So to be explicit about the change so we can sign off and close this, we are proposing:

Removing commitlint from the travis file, - npx aegir commitlint --travis
a PR should be made to the readme here to remove it from the template.
Maintainers should always squash PRs and use that as a mechanism to create clean, changelog friendly commit messages.
We should update https://github.com/ipfs/community/blob/master/CONTRIBUTING_JS.md to mention this.

 Even I sometimes forget to lint things locally, so even for myself it's a good indicator whether things are correct or not.

 Even I sometimes forget to lint things locally, so even for myself it's a good indicator whether things are correct or not.

I think this is going to vary quite a bit by maintainer. I edit nearly every squash I do. Perhaps updating the travis.yml file in the readme here to show how to add that as an allowed failure would be a good middle ground to eliminating it altogther?


New WebView for Windows via WebView2 & WebUI 3

Plannings to start implement use of latest WebView2 via WebUI 3 on Windows
https://docs.microsoft.com/en-us/microsoft-edge/webview2/
https://microsoft.github.io/react-native-windows/docs/winui3
https://docs.microsoft.com/en-us/windows/apps/winui/winui3/
https://github.com/MicrosoftEdge/WebView2Samples/search?q=addhostobjecttoscript&unscoped_q=addhostobjecttoscript

How should messaging between js and react native windows done if there is no AddWebAllowedObject in use? Try use AddHostObjectToScript https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2.addhostobjecttoscript?view=WebView2-dotnet-0.9.628-prerelease

I will wait that my 2 PRs are merged before i will try to implement any new WebView2
https://github.com/react-native-webview/react-native-webview/pull/1617
https://github.com/react-native-webview/react-native-webview/pull/1623

About AddWebAllowedObject : For WebView2 - which will be included as part of WinUI 3 - you would be able to do something similar to AddWebAllowedObject by using https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/icorewebview2?view=webview2-0.9.622#addhostobjecttoscript. I'm not sure if there is a nicer WinRT API so you might need to use the COM API instead.

Will we ever be able to pass complex objects into and out of our API's https://github.com/MicrosoftEdge/WebView2Feedback/issues/292

Is there an update on this?
Really like to see react-native-webview using WebView2.

Who manage do implement this?

Discussion continues in https://github.com/microsoft/microsoft-ui-xaml/issues/5610