Incorrect rewrite for Enterprise_TargetRule_Model_Resource_Index

Hi all,
We're about to migrate our store to PHP7 and I've been testing it with the Inchoo patch installed (great job btw!), and noticed this in the system.log file:
ERR (3): Notice: Array to string conversion  in /{server_path}/app/code/core/Enterprise/TargetRule/Model/Resource/Index.php on line 315
ERR (3): Notice: Undefined property: Enterprise_TargetRule_Model_Resource_Index::$Array  in /{server_path}/app/code/core/Enterprise/TargetRule/Model/Resource/Index.php on line 315

which is supposed to be fixed by rewriting the above class to Inchoo_PHP7_Model_Resource_Index.
After using Xdebug to dig into it, it seems that the rewrite XML specified in this module's config.xml is incorrect, and the resource model class Enterprise_TargetRule_Model_Resource_Index is still being instantiated.
I believe the rewrite should actually be:
<enterprise_targetrule_resource>
    <rewrite>
        <index>Inchoo_PHP7_Model_Resource_Index</index>
    </rewrite>
</enterprise_targetrule_resource>

I've tested this change and it loads Inchoo_PHP7_Model_Resource_Index correctly, which fixes the issue. I'll also file a pull request with a fix.
Thanks!

Pull request merged, thanks.


"Your Iterations" tab not consistent with my submissions

As per the below screenshot, I've submitted two iterations, but it shows Iteration 1 (which failed wrongly) as being the latest.

This would be an issue for @iHiD or @ErikSchierboom.
This repository does not deal with the UI of the website.


fix: Revert "fix: reverse order of request callback params (#335)"

This reverts commit a732f8dfbcf8aa68c8d04ef89890d166506baa20.

TBR = @kinwa91
My original PR to do this was a very bad no good mistake.


Problem to merge code of BookingProduct in old laravel bagisto

Hello,
I have to use Webkul\BookingProduct webkul package in my old bagisto version. Webkul\BookingProduct package is available in a new version of bagisto. Currently, I am working on laravel 5.6 with bagisto and the new version is 6.0 with velocity theme and BookingProduct(product type - Downloadable, Bundle, Virtual, Grouped, etc) features and I have to use this both features in my existing project. So how to use bagisto new features in my old environment.
Anyone please give me a solution and guide me on an easy way to use new functionality in my old environment.
Thanks.

@testforpostman7
You have to upgrade your old version into the latest version, as there are lots of changes in 1.0.0 version or higher so kindly upgrade your Project by saving the backup file of your old project.

@vaishaliwebkul I have made so many customization in old version of bagisto. So can you suggest me any other solution.
Thanks.

@testforpostman7
probably all your customization is added into a separate package ?? if yes then you can easily add this package into the new project.

@testforpostman7
no revert from last 1 month so closing this.
I hope the solution works for you.


Auto-add parenthesis to callable completions

"python.autoComplete.addBrackets": true

I have the same problem.

For what it's worth, the expected behavior at the moment is for this to not work; anything under python.autoComplete has either moved to python.analysis (e.g., python.analysis.extraPaths), or hasn't been implemented. The list of currently supported options are in this repo's README.

This happens when "python.languageServer" is set to anything other than Jedi.
People also encountered this problem here: https://github.com/microsoft/vscode-python/issues/12786

To give an update, this has been spec'd out (under a more descriptive name than "brackets"), but isn't yet implemented.

This issue has been fixed in version 2020.8.2, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#202082-20-august-2020
You can enable this by setting:
{
    "python.analysis.completeFunctionParens": true
}

If you were already using python.autoComplete.addBrackets, your setting should be automatically ported. (We took this opportunity to name this more descriptively than the old addBrackets setting.)

For my case, using VS code for Flutter/Dart, I resolved this error by disabling the Preview LSP (Language Server preview) which I had earlier enabled to remedy another VS Code error - Data analyser stopped working.

referring to this issue, has it been fixed ? because it's not working for me with Pylance, thanks. https://github.com/microsoft/pylance-release/issues/180#issuecomment-1396780954

See https://github.com/microsoft/pylance-release/issues/3831. Should be fixed in the prerelease bits.


Add files via upload -fact/ matters in the/ world

LORD GOD ALMIGHTY, The UNCREATED CREATOR who owns the Spirit that is in everyone, and who laid the foundation of the World 🌎 Humans are living in, wants everyone irrespective of Religion, Nation, Language and Worldview, to CC. Commit and Contribute meaningfully and righteously to make our wonderful World greater, and hinder the evil trinity, nay, Lucifer Pride Satan, the Unrighteous Mammon, and the Mother of Harlots who hate Humanity so terribly, from accessing the code of Sustainability and Survival of the mysterious generation in far future that co-exist with this extraordinary generation.

My name is Chukwu Innocent Okechukwu, Spiritual name PETAP AMEN MESJJ, please I request for your collaboration, commit and contribution to push these vitals.

As The Only Holy and Wise Good GOD ALMIGHTY who dealt with me very deeply one on one, ordered and charged me, we all can collectively and inclusively put Racism, War, and Religious troubles to death, and chase away Lucifer Pride Satan who has been Violating, Assaulting and Merchandising Humanity to his spiritual dimension (VAM)


Clean up implementation

This PR cleans up a few pieces of the implementation, without changing the interface. It sets CMake 3.20 as a minimum version, but enables policies through 3.25. It also adds missing quotes, abstains from promoting the Pytest::Pytest target to the global scope, drops some unused mark_as_advanced calls, and enables version ranges and component checking in find_package.
Fixes #1

These are all great updates, thanks @alexreinking !


Develpment: Improve exception assertions in server tests

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[ ] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[ ] I chose a title conforming to the naming conventions for pull requests.

Server

[ ] Important: I implemented the changes with a very good performance and prevented too many (unnecessary) database calls.
[ ] I followed the coding and design guidelines.
[ ] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[ ] I added pre-authorization annotations according to the guidelines and checked the course groups for all new REST Calls (security).
[ ] I documented the Java code using JavaDoc style.

Motivation and Context

A follow-up PR of https://github.com/ls1intum/Artemis/pull/6588, deals with assertions related to exceptions. There are a few instances where assertThrows and assertDoesNotThrow instead of the corresponding AssertJ assertion.
Description

Also an architecture test has been added, checking that no JUnit assertions are used in server tests
Review Progress

Code Review

[ ] Code Review 1
[ ] Code Review 2

Test Coverage
unchanged

Codecov Report

Merging #6603 (3e1d071) into develop (cf74c01) will decrease coverage by 4.45%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6603      +/-   ##
=============================================
- Coverage      84.94%   80.50%   -4.45%
+ Complexity     13321    13312       -9
=============================================
  Files           1093     2361    +1268
  Lines          42898    90659   +47761
  Branches        4439    13383    +8944
=============================================
+ Hits           36440    72985   +36545
- Misses          4007     9726    +5719
- Partials        2451     7948    +5497

see 1318 files with indirect coverage changes

Flag
Coverage Δ

client
76.53% <ø> (?)

server
84.94% <ø> (-0.01%)
:arrow_down:

Continue to review full report in Codecov by Sentry.

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


introduce concat in order to merge string in defacl query

Running ldap2pg with Postgres 15 introduced the following error:
File /usr/local/lib/python3.9/dist-packages/ldap2pg/script.py, line 133, in synchronize
    count = manager.sync(syncmap=config['sync_map'])
  File /usr/local/lib/python3.9/dist-packages/ldap2pg/manager.py, line 331, in sync
    pgacl = self.inspector.fetch_grants(schemas, pgmanagedroles)
  File /usr/local/lib/python3.9/dist-packages/ldap2pg/inspector.py, line 266, in fetch_grants
    rows = self.fetch_shared_query(
  File /usr/local/lib/python3.9/dist-packages/ldap2pg/inspector.py, line 292, in fetch_shared_query
    rows = list(conn.query(None, self.shared_queries[name]))
  File /usr/local/lib/python3.9/dist-packages/ldap2pg/psql.py, line 122, in query
    cur.execute(sql, *args)
  File /usr/local/lib/python3.9/dist-packages/ldap2pg/psql.py, line 168, in execute
    return super(FactoryCursor, self).execute(query, *a, **kw)
psycopg2.errors.AmbiguousFunction: operator is not unique: text || char
LINE 12:   priv || '_on_' || objtype AS key,                          ^
HINT:  Could not choose a best candidate operator. You might need to add explicit type casts.
Please file an issue at https://github.com/dalibo/ldap2pg/issues with full log.

In Order to fix this I adapted the acl default query to utilize the concat function instead of ||

You're awesome, thanks. Could you add an entry in CHANGELOG ?

You're awesome, thanks. Could you add an entry in CHANGELOG ?

I wasn't sure about the versioning and added the comment to 5.9...if you would prefer it in 5.10 please let me know.

That's fine. I used to review Changelog before releasing. Someting titling unreleased entry as Unreleased.


Update issue templates

Pull Request Test Coverage Report for Build 77

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.971%

Totals

Change from base Build 62:
0.0%

Covered Lines:
126

Relevant Lines:
137

💛  - Coveralls


fix(api): fix entry point in api package

Pull Request Test Coverage Report for Build 732259417

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 732243328:
0.0%

Covered Lines:
553

Relevant Lines:
553

💛  - Coveralls


[python] Support Python 3.12

Issue and/or context: #1849
Changes: Just a check to see what happens with 3.12.
Notes for Reviewer: This PR is not for review.
Status as of 2024-02-05: numba 0.58 is not yet ready for Python 3.12.
$ docker run --rm -it --entrypoint=/bin/bash python:3.12-bookworm
root@20d715ac5ab7:/# pip install numba==0.58
Collecting numba==0.58
  Downloading numba-0.58.0.tar.gz (2.6 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.6/2.6 MB 32.5 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-417bk_qg/numba_1954fc6d020f4c6087042050c24f72c3/setup.py", line 51, in <module>
          _guard_py_ver()
        File "/tmp/pip-install-417bk_qg/numba_1954fc6d020f4c6087042050c24f72c3/setup.py", line 48, in _guard_py_ver
          raise RuntimeError(msg.format(cur_py, min_py, max_py))
      RuntimeError: Cannot install on Python version 3.12.1; only versions >=3.8,<3.12 are supported.
      [end of output]

$ docker run --rm -it --entrypoint=/bin/bash python:3.11-bookworm
root@d8f7153f52c6:/# pip install numba==0.58
Collecting numba==0.58
  Obtaining dependency information for numba==0.58 from https://files.pythonhosted.org/packages/f7/b6/8800604a3380aa94af830c30839db93077c7fe2812a48ce7d4400d75ba9c/numba-0.58.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl.metadata
...
Installing collected packages: numpy, llvmlite, numba
Successfully installed llvmlite-0.41.1 numba-0.58.0 numpy-1.25.2

Status as of 2024-02-13: numba 0.59 is installable on Python 3.12.

Re-trying with rebase on #2122 which has since been merged, for #1849

Most strange. At
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/7891284152/job/21535281973?pr=2108
I see
Run python scripts/show-versions.py
  python scripts/show-versions.py
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.12.2/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.12.2/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.12.2/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.12.2/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.12.2/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.12.2/x64/lib
Traceback (most recent call last):
  File "/home/runner/work/TileDB-SOMA/TileDB-SOMA/scripts/show-versions.py", line 13, in <module>
    import tiledbsoma
  File "/home/runner/work/TileDB-SOMA/TileDB-SOMA/apis/python/src/tiledbsoma/__init__.py", line 111, in <module>
    from ._general_utilities import (
  File "/home/runner/work/TileDB-SOMA/TileDB-SOMA/apis/python/src/tiledbsoma/_general_utilities.py", line 13, in <module>
    from pkg_resources import DistributionNotFound, get_distribution
ModuleNotFoundError: No module named 'pkg_resources'
Error: Process completed with exit code 1.

Yet when I run docker run --rm -it --entrypoint=/bin/bash python:3.12.2 and use
from pkg_resources import DistributionNotFound, get_distribution
try:
    print(get_distribution("tiledbsoma").version)
except DistributionNotFound:
    print("unknown")

I get no such error 🤔

See https://docs.python.org/3/whatsnew/3.12.html for information on why you may see this error.  The default packages have changed in 3.12 for a virtual environment.

gh-95299: Do not pre-install setuptools in virtual environments created with venv. This means that distutils, setuptools, pkg_resources, and easy_install will no longer available by default; to access these run pip install setuptools in the activated virtual environment.

Rather than modifying _general_utilities.py, why not just add setuptools to the list of dependencies for the package?
On python 3.7-3.11, it will already be installed and available, so little to no overhead. and it lets you keep the version code identical over all releases.

@bkmartinjr thanks for thinking of what I did not! I'll try that.
However, I would also note
https://stackoverflow.com/questions/76043689/pkg-resources-is-deprecated-as-an-api
so maybe we keep what I have as a transition, then drop the 3.7 compatibility block once we fully drop support for Python 3.7?
Thoughts?

Yep, just (actually) read the docs. What you did looks right to me - sorry for the noise!


Cannot export value on deconstruction

For example, the following two cases cannot be scanned by l10-dev:
import * as vscode from 'vscode';
const {
  l10n: { t },
} = vscode;
const { l10n: aaa } = vscode;

console.log(t('Hello {0}', ['yiliang114']));
console.log(aaa.t('Hi {0}', ['yiliang114']));

Yeah we support:
import { l10n } from 'vscode';
import { l10n: aaa } from 'vscode';

which you can see in the tests. but not what you're talking about here. This is because we do this statically (we have to) and our tree-sitter query needs to be expanded to support this syntax.

Yeah we support:
import { l10n } from 'vscode';
import { l10n: aaa } from 'vscode';

which you can see in the tests. but not what you're talking about here. This is because we do this statically (we have to) and our tree-sitter query needs to be expanded to support this syntax.

Uh-huh, I'm also used to looking for all the ways to use it from unit tests.
I think you have added a label named Backlog, which means this feature will be added later?

Backlog means we would like to do this but it's not currently being worked on.


Revert Replace Windows system probe socket endpoint localhost:3333 with named pipe (#29028)

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on


Crosshair gap

Often the voxel at the center of the crosshair is of the most interest. Therefore, tools like Slicer3D and MRIcroGL (shown below) provide an option for a gap at the crosshair intersection. NiiVue should also provide this option.

Once the recent PR is merged, the voxel atlas live demo will include an interactive Crosshair Gap slider.


Getting started - Android - Extending ReactActivity

The Getting started section for Android - item 4 should probably be changed to something like this - if your MainActivity inherits from ReactActivity:
import com.github.xinthink.rnmk.ReactMaterialKitPackage;
...
protected List getPackages() {
return Arrays.asList(
new MainReactPackage(), new ReactMaterialKitPackage());
}

Feel free to submit a pull request to change that yourself! :+1:

Thanks for reporting. I'll update the example code later.
The lib may be used it in a pure RN project or a hybrid one, it's very hard to meet everyone's need. I think  it should be put in the guide, that the way linking the lib is up to you, depends on the architecture of the project.


Support class auto import with its type

Clear and concise description of the problem
If declare and export a class.
export default class Foo {

}

While directly use it for construct a new instance. Yeah it works properly.
const foo = new Foo();

However if use this class for type hint, TypeScript will not recognize it.
const foo: Foo = new Foo();
           ^^^

function myFunc(foo: Foo) {
                     ^^^
}

Error: 'Foo' refers to a value, but is being used as a type here. Did you mean 'typeof Foo'?

typeof Foo will be the type of Foo's constructor, that is new () => Foo, like StringConstructor of String;
You have to import that class explicitly, then it will work.
import type Foo from "../classes/Foo";

Suggested solution
Do not use typeof import(xxx) in the auto-imports.d.ts, use export xxx from instead. Just like it in latest Nuxt auto import method.
const Foo: typeof import('../classes/Foo')['default'];

change to
export Foo from '../classes/Foo';

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

我也遇到了相同的问题，现在有解决方案吗？
I ran into the same problem, is there a solution now?

My solution using InstanceType:
// Api.ts
export class Api {
  ...
}

// auto-imports.d.ts
declare global {
  ...
  const Api: typeof import('./src/apis/Api')['Api']
}

// other file
let someApi: InstanceType<typeof Api> = new Api()

// or
type ApiType = InstanceType<typeof Api>
let someApi: ApiType = new Api()
function myFunc(api: ApiType) {
  ...
}

我也有这个问题, 当我使用导入 threejs 中的部分类的时候会报这个错, 如果不加 type, 那就是导入的类, 如果加上 type, 那就是导入的类型, 希望能有个参数控制两者都能使用
 AutoImport({
	imports: [
		{
	      from: 'three',
	      imports: ['Group'],
		 // type: true
	    }
	]
} )

Same here for three, it works to auto-import either as types or values, but not both.

如果在自动导入的 .d.ts 文件中使用以下声明即可同时导入变量及其类型。
If this declaration is used in the auto import .d.ts file, variables and types can be imported at the same time.
import _0 from "classes/Foo";
import _1 from "classes/Bar"
import _2 from "classes/Baz"

declare global {
    export { default as Foo, Foo1, Foo2 } from "classes/Foo";
    export { default as Bar, Bar1, Bar2 } from "classes/Bar";
    export { default as Baz, Baz1, Baz2 } from "classes/Baz";
}

其中，Foo 是默认导出，Foo1、Foo2 是命名导出，其它同理。
顶部导入语句中的变量名称随意，此处使用下划线加数字表示，因为名称并不重要。但是不能不写，如果不写，则下方导出的变量类型全部都是 any。并且导入和导出语句需要都写一遍路径。
Foo is the default export, Foo1 and Foo2 are named exports, same to others.
Feel free to name the variables from the top import statements, which are represented by underscore with numbers here, because the names are unimportant. But it cannot be removed, otherwise all exported variable types will be "any". So both import and export statements require to type the path.
此外，如果你使用了 Nuxt，则只能使用命名导出而不能使用默认导出，这是因为 Nuxt 的自动导入功能对默认导出使用文件名而非变量名命名。糟糕的是，Nuxt 将文件名进行了小驼峰化处理，这导致了作为一个类却使用了小驼峰的名字，看起来非常不适宜。
In addition, if you are using Nuxt, you can only use named exports and cannot use default exports because Nuxt's auto import feature names default exports with the filename instead of the variable name. Unfortunately, Nuxt has camelized the file name, which result in the class using a camel name, looks very inappropriate.


Cancel open file => popup with javascript error

Using a fresh Camunda Modeler 1.1.1, I click on "Open a Diagram" then I cancel the operation. There is a popup with an error that appeared. This is also the case if I cancel using the cross icon of the popup.

Closed via https://github.com/camunda/camunda-modeler/issues/337

To be fixed with next Camunda Modeler release. Fixed in the nighty builds already.


Update User.fetch to get a valid login list on mobile

Details
Fixes an issue where sending an array for names for API.get returned an incorrect response when on mobile.
Fixed Issues

Fixes https://github.com/Expensify/Expensify.cash/pull/2169#issuecomment-814533130
Tests

Log into E.cash with an email address that doesn't have any secondary logins
Navigate to Settings > Profile
Confirm you only see only + Add Phone Number and not ` + Add Email Address

QA Steps

Repeat test steps.
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

E.com screenshot with no secondaries:

Web

Mobile Web

Desktop

iOS

Android

Issue is only on iOS and Android, but added screenshots for all of them to be sure

Merging since Marc approved.


⚠ Spryr has degraded performance

In 861fa9c, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4612 ms

Resolved: Spryr performance has improved in ac9ec87 after 10 minutes.


drill-6-3: add a number of tests for fixed JIRAs

@krystaln Can you please review the PR? Added a couple test cases after bug fix.
http://<IP_ADDRESS>:8080/job/Framework-Regression/587/console

Looks good. +1


Clangxx warnings on osx in Release build

Warnings need to be inspected and suppressed with NDEBUG or alternatively with CXX flags, if not critical.
https://travis-ci.com/github/tudat-team/tudat-feedstock/builds/173666185

Current Azure clang build is warning-free.


A colab.ipynb example for workflow

/home/fight/Desktop/Autoformer/Autoformer-main/predict.ipynb

I create a colab example like informer does in his repository,hopeful this would help people by using amazing model autoformer

Cool, thanks for your great work.
If you want, you can raise a pull request, then I can merge this into this repo (Just up to you)~

sure,It's my pleasure


Conditional views

Prior to this change, applying conditions to a view required annotating
all fields individually.
This change allows views to be defined as view :name, if: condition,
using the same ->(field_name, object, options) { ... } callbacks as
used on fields. These callbacks are propagated to the fields, and are in
addition to (not in replacement of) any checks defined on the fields.
Tests are added to cover the logic of unless and if, and
Field#skip? is altered to allow a field to have both unless and if
defined.
Defining a view-level condition on an child blueprint does not affect
the parent view of the same name - this behavior may be unexpected, and
it is advised not to add conditions to inherited views, since this may
represent a security flaw.
Checklist:

[ ] I have updated the necessary documentation
[x] I have signed off all my commits as required by DCO
[ ] My build is green

I concur with @lessthanjacob. But I'd also like to understand the use-case better. Why would you want to make all fields in a view conditional? Couldn't that check be moved to the caller, where it chooses which view to render?


Noty version: V3.1.0
Browser: Google chrome 59
OS: Mac OSX 10.11
jsFiddle link (if available): null

I think you forgot to include css files.


[Swift 2] Update Quick to work with xctool

Addresses https://github.com/Carthage/Commandant/pull/31#issuecomment-142467074.

The tests are passed, so I'm gonna merge this.


Can't get this to work with Heroku and MongoLab

The server is up and running as well as a mongolab instance however their is no clear indication as to what you do next.  In the index.js their are several fields that look like they need to be filled out and Its not clear where you get the db connection and any app id or keys..
I used replaced the mongolab URI from my deployed system (im guessing thats what I needed to do) but where do you get myAppId and MasterKey.. If you say inside of parses admin I did grab those but I dont think thats right.. where can I find these keys or set them?
var api = new ParseServer({   databaseURI: process.env.DATABASE_URI || 'mongodb://localhost:27017/dev',   cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',   appId: 'myAppId',   masterKey: 'myMasterKey' });
Could you please be more descriptive on how to do this step by step because I'm sure lots of people will be wanting to know.

Take a look at this step by step instructions: https://parse.com/docs/server/guide#deploying
For myAppId and MasterKey, you can specify anything you want. If you're migrating, you'll want to set those to what they were from your hosted Parse app. Check out the migration guide here: https://parse.com/docs/server/guide#migrating

Yea I did, still not 100% clear, you or who ever wrote it , wrote it from a stand point if you know or have done it a few times.  There should be more of nicer newbie how to guide.  I followed all instructions for Heroku and MongoLab using the startup git depo here.  I did a test curl post to the server and all I got was cannot post returned.. so obviously I'm missing something and that would lead to documentation.  I know it might seem trivial to someone who has done this but I would ask that someone takes the time to really do more detailed on.  If I can get it up and running I dont mind but I'm a bit stuck since the depo seems more coded towards local than the other hosted option.. Im sure you understand and with massive announcement and struggle for people it would be in parse's best interest to provide more detailed docs.. thanks..

If you got "Cannot POST" then the routes aren't being hit... Check the mount path of the server and your client.  The default on the server is /parse, the old path on parse was /1.  Make sure you're curl-ing against the right path.


Allow the specification to be specified as a URL.

Changes proposed in this pull request:

Allow a specification to be specified as a URL that is downloaded when the App runs. In combination with the existing mock features, this makes it a single command to run a mock server for any published API.

Do you have a few tests for this PR?
In particular I'm interested in how this would work for specs without defined operation ids.
For context, I could see this being awesome for mocking external API service during development or even as part of a testing pipeline so that you automatically get the default/example response combined with request validation.

Thanks @mjp4,
I'm indeed wondering the same as @perrystallings. Another option would be to include this in the CLI instead, if that's the only place where it would be useful.

Thanks both, I've added a test.
I don't have an immediate proposal for handling APIs without Operation IDs, the ones I'm interested in all do.
As it stands, and combined with #1874 and #1870, it has the potential to provide useful dummy output in many situations.
I was also thinking of submitting a PR for a resolver that maps arbitrary Operation IDs to functions without making assumptions about module structure. Something like:
class DictResolver(connexion.Resolver):
    def __init__(self, handler_dict):
        def function_resolver(operation_id):
            function = handler_dict.get(operation_id)
            if function is not None:
                return function
            msg = f'Cannot resolve operationId "{operation_id}"! Supported operations: {list(handler_dict.keys())}'
            raise ValueError(msg)

        self.function_resolver = function_resolver

OPERATIONS = {
    "OperationOne": lambda: ("Body Text", 200)
}

resolver = DictResolver(OPERATIONS),

coverage: 94.207% (-0.007%) from 94.214%
when pulling 27e753cfe5498c45b3d4d3125fbffc66974b1928 on mjp4:allow-url-spec
into 3e64fe46e9b8f63f605bdd5a77ad06704c4805b3 on spec-first:main.

@RobbeSneyders I think this is ready to go in?


Update MD file on new branch 2017-54-03_15-12-29

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

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


Missing emails inside folder

Expected behavior
All emails inside a folder shall be visible inside the same folder in K9.
Actual behavior
Updating folder does not download all (new) emails. It silently skipped two emails, but later emails from the same thread were included. When checking the same account on PC, emails are visible.
The behaviour is permanent(ie. "hidden" emails don't appear even when polled again and again). I have not tried resetting folder cache yet. Please let me know if I can provide any more info.
Steps to reproduce

Pull down inside a folder to poll server
New emails arrive
Verify emails list with emails on another device

Environment
K-9 Mail version: 5.208
Android version: 5.1.1
Account type (IMAP, POP3, WebDAV/Exchange): IMAP

Please use the latest (stable) version of K-9 Mail and provide a debug log. See https://github.com/k9mail/k-9/wiki/LoggingErrors


doc: reorganize SQL docs

Created 'Atlas Schemas'
Moved SQL Resources, SQL Column Types, Input Variables and Projects under 'Atlas Schemas'
Moved DDL under 'Concepts'

CI red


Add support for signing SMB2

Hi,
I am trying to add support for signing for SMB v2 packets. I am using the client here: https://github.com/sahlberg/libsmb2
I have tried to add support here: https://github.com/amandeepgautam/gss-ntlmssp/commit/453653d6f7fa103ebff6232850b94a1562dcfaeb, but this does not yet work and I cannot figure out why. Can you please look?

Hi Aman,
can you give me more details about what is not working ?
The changes you make are reasonable, although I need to check if what you do is correct when a key exchange key is not requested.

I get the following error:
Session setup failed with (0xc0000022) STATUS_ACCESS_DENIED.  (-13)
It is from here: https://github.com/sahlberg/libsmb2/blob/a884d37f05cb96ea24d83429b6e0ea6b76509d43/lib/libsmb2.c#L503
I am hoping that the calculations are probably not correct or I am missing something. But cannot figure out why.

Looking at your patch the change you make for encrypted_session_key is incorrect, when NTLMSSP_NEGOTIATE_KEY_EXCH is not set then there is no encrypted_random_session_key to be sent around.
Why did you change that, what problem are you trying to resolve with that change ?

Your patch attempts to send the session key in the clear to the server, it would introduce a total breach of security.

I get the following error:
Session setup failed with (0xc0000022) STATUS_ACCESS_DENIED. (-13)
It is from here: https://github.com/sahlberg/libsmb2/blob/a884d37f05cb96ea24d83429b6e0ea6b76509d43/lib/libsmb2.c#L503
I am hoping that the calculations are probably not correct or I am missing something. But cannot figure out why.

ACCESS_DENIED may be due to numerous reasons, I am not familiar with libsm2 but a tree connect usually happens after authentication and access denied at that point simply means your user has no access. Is there evidence that this is due to an issue in NTLMSSP ?

I am very unfamiliar with SMB etc. so my patch is mostly based on experimentation. Here is how I thought this needs to be done:
Details about the internal setup:
We have 2 versions of client:
a) one using ntlmssp plugin with libsmb2 ()
b) other using libsamba (https://github.com/samba-team/samba/)
and for experimentation we also built:
c) native ntlmssp support with libsmb2 (libsmb2 comes with a very minimal support for ntlmssp)
(a), (c) share the same code. (b) is a different implementation.

Looking at your patch the change you make for encrypted_session_key is incorrect, when NTLMSSP_NEGOTIATE_KEY_EXCH is not set then there is no encrypted_random_session_key to be sent around.
Why did you change that, what problem are you trying to resolve with that change ?

In packet traces captured for (b), I saw session key being sent. So, thought that maybe that is why I am getting ACCESS_DENIED. Hence the change. I can revert that bit.

Your patch attempts to send the session key in the clear to the server, it would introduce a total breach of security.

Apologies. I am very new to this.

ACCESS_DENIED may be due to numerous reasons, I am not familiar with libsm2 but a tree connect usually happens after authentication and access denied at that point simply means your user has no access. Is there evidence that this is due to an issue in NTLMSSP ?

Using (b), (c) I can access the file. So, I concluded the changes I have made do not work.

Using (b), (c) I can access the file. So, I concluded the changes I have made do not work.

If you can provide me pcap traces of a working and a non-working case I
can help you establish if a NTLMSSP issue is likely or if there is a
configuration difference you need to clear first.
Simo.
--
Simo Sorce
RHEL Crypto Team
Red Hat, Inc

Sure. Let me get those to you. Will update in few mins.

Please find the attached network traces

Please find the attached traces for 3 traces. the names are corresponding to the options (a), (b) and (c).
traces.zip

@simo5 I looked into this more. Comparing with (c), I identified that there is a difference in how ntlmv2 response is calculated and made the following change: https://github.com/amandeepgautam/gss-ntlmssp/commit/368a1e0cfaf4e695950f8e3f9fceb517879c0c5f#diff-8f904654e790490f29504524e46f5b71L125.
We should pass target_info instead of client_target_info as suggested in this document as well: http://davenport.sourceforge.net/ntlm.html#theNtlmv2Response
It is still not working after this change, so let me know if you agree with it.

Aman, completely ignore davenport's stuff, it is often wrong.
Microsoft published the full protocol in MS-NLMP, that's your reference, if you read ntlmssp source code you will see many references to sections of the document.
Replying back the server target_info is wrong in general, because the target_info must contain only what the client understands it supports.
If there are missing/additional fields we need to figure out why. Blindly copying over target_info is not going to help you as you will claim things to the servert that the client code is then not aware of. The client and server behavior expectations will go out of sync then.

@amandeepgautam in the failing one (A) you are not negotiating the same NTLMSSP flags as the successful one.
Can you show me the code around where you call the GSSAPI interface in the non-working example and the working one ?

Aman, completely ignore davenport's stuff, it is often wrong.
Microsoft published the full protocol in MS-NLMP, that's your reference, if you read ntlmssp source code you will see many references to sections of the document.
Replying back the server target_info is wrong in general, because the target_info must contain only what the client understands it supports.
If there are missing/additional fields we need to figure out why. Blindly copying over target_info is not going to help you as you will claim things to the servert that the client code is then not aware of. The client and server behavior expectations will go out of sync then.

Sure.

@amandeepgautam in the failing one (A) you are not negotiating the same NTLMSSP flags as the successful one.
Can you show me the code around where you call the GSSAPI interface in the non-working example and the working one ?

@simo5 In the non-working case we set the flags here(in the plugin): https://github.com/simo5/gss-ntlmssp/blob/75e3840fc7d7471235a8e1edaf114b0ba735e377/src/gss_sec_ctx.c#L127 (and following lines) and we get the response from the server and then do the negotiation.
In the working case (Option C), libsmb2 generates the packet and flags related part is here:
https://github.com/sahlberg/libsmb2/blob/a884d37f05cb96ea24d83429b6e0ea6b76509d43/lib/ntlmssp.c#L164
Why do you think that flag negotiation can lead to a difference?

Sol one key difference is that NTLMSSP_NEGOTIATE_KEY_EXCH is set only if you pass the GSS_C_CONF_FLAG to the api when you gss_init_sec_context(), are you requesting any flags when making that call ?
Admittedly we may want to set that flag also when just requesting integrity (GSS_C_INTEG_FLAG only), it would make sense, so I would accept a patch in hat sense if required.
Another difference I noiticed is that gssntlmssp never sets the NTLMSSP_NEGOTIATE_VERSION, I forgot why, possibly an omission error, but I do not think it should make a difference for your case.
We should definitely concentrate on getting the key exchange flag set first, given that has security relevance and it is possible your server requires it and doesn't like it when the client does not set it.

I just realized you are using the lower level API in libssh ... ok, in that case please just add NTLMSSP_NEGOTIATE_KEY_EXCH to the neg_flags and you'll also need NTLMSSP_NEGOTIATE_SIGN for sure if you want to do signing.

@simo5 hmm...will try that. A quick question though: why does Option C, which also seems to be doing signing not require those flags?

@simo5 tried with the NTLMSSP_NEGOTIATE_KEY_EXCH flag and things work now. So, what is the take away here: if NTLMSSP_NEGOTIATE_SIGN is there, enforce NTLMSSP_NEGOTIATE_KEY_EXCH flag so that things work?
Also, do you not think that it is worth investigating why NTLMSSP_NEGOTIATE_SIGN does not work without NTLMSSP_NEGOTIATE_KEY_EXCH? It should right?

@simo5 updated the change here: https://github.com/amandeepgautam/gss-ntlmssp/commit/1a73db97a9c6c1e9d935760040bbcce660c81058
Let me know if I should send out a pull request.

On Tue, 2019-12-10 at 16:54 -0800, Aman Deep Gautam wrote:

@simo5 hmm...will try that. A quick question though: why does Option C, which also seems to be doing signing not require those flags?

In the traces you sent I see those flags.
--
Simo Sorce
RHEL Crypto Team
Red Hat, Inc

On Tue, 2019-12-10 at 17:08 -0800, Aman Deep Gautam wrote:

@simo5 tried with the NTLMSSP_NEGOTIATE_KEY_EXCH flag and things work
now. So, what is the take away here: if NTLMSSP_NEGOTIATE_SIGN is
there, enforce NTLMSSP_NEGOTIATE_KEY_EXCH flag so that things work?
Also, do you not think that it is worth investigating why
NTLMSSP_NEGOTIATE_SIGN does not work without
NTLMSSP_NEGOTIATE_KEY_EXCH? It should right?

Yes investigation would be nice, not clear if it should, there may be
other flags that influence that as well as server side minimum security
settings.
Simo.

On Tue, 2019-12-10 at 17:40 -0800, Aman Deep Gautam wrote:

@simo5 updated the change here: https://github.com/amandeepgautam/gss-ntlmssp/commit/1a73db97a9c6c1e9d935760040bbcce660c81058
Let me know if I should send out a pull request.

A pull request to extract the SSPI session key is fine, but I can't add KEY_EXCH as a default flag as that will make the library incompatible with some of the uses.
Key Exchange is required only when SIgning and/or Sealing are requested.
If you are using the gssapi interface that means setting ths GSS_C_CONF_FLAG flag, if you are using the lowe rinterface directly you just need to use set the flag on your own for now.
Simo.

On Tue, 2019-12-10 at 17:40 -0800, Aman Deep Gautam wrote: @simo5 updated the change here: amandeepgautam@1a73db9 Let me know if I should send out a pull request.
A pull request to extract the SSPI session key is fine, but I can't add KEY_EXCH as a default flag as that will make the library incompatible with some of the uses. Key Exchange is required only when SIgning and/or Sealing are requested. If you are using the gssapi interface that means setting ths GSS_C_CONF_FLAG flag, if you are using the lowe rinterface directly you just need to use set the flag on your own for now. Simo.

How about if we set the flag only with NTLMSSP_NEGOTIATE_SIGN:
https://github.com/simo5/gss-ntlmssp/blob/75e3840fc7d7471235a8e1edaf114b0ba735e377/src/gss_sec_ctx.c#L143?
So, if someone requests GSS_C_REPLAY_FLAG flag, that would mean we set NTLMSSP_NEGOTIATE_SIGN and NTLMSSP_NEGOTIATE_KEY_EXCH. Is that an acceptable change?
In our case, we use gss_init_context api and request the following flags: https://github.com/sahlberg/libsmb2/blob/2a58027e8464667a0b0215c3bac71b28dca7bf50/lib/krb5-wrapper.c#L358

On Tue, 2019-12-10 at 16:54 -0800, Aman Deep Gautam wrote: @simo5 hmm...will try that. A quick question though: why does Option C, which also seems to be doing signing not require those flags?
In the traces you sent I see those flags.
…
-- Simo Sorce RHEL Crypto Team Red Hat, Inc

A little digression, getting back to an old comment: In option (c), we do not even negotiating NTLMSSP_NEGOTIATE_SIGN (or NTLMSSP_NEGOTIATE_KEY_EXCH). How is it working there?

On Tue, 2019-12-10 at 17:40 -0800, Aman Deep Gautam wrote: @simo5 updated the change here: amandeepgautam@1a73db9 Let me know if I should send out a pull request.
A pull request to extract the SSPI session key is fine, but I can't add KEY_EXCH as a default flag as that will make the library incompatible with some of the uses. Key Exchange is required only when SIgning and/or Sealing are requested. If you are using the gssapi interface that means setting ths GSS_C_CONF_FLAG flag, if you are using the lowe rinterface directly you just need to use set the flag on your own for now. Simo.

How about if we set the flag only with NTLMSSP_NEGOTIATE_SIGN:

You can have signing without key exchange (when using NTLMv1 for example).

https://github.com/simo5/gss-ntlmssp/blob/75e3840fc7d7471235a8e1edaf114b0ba735e377/src/gss_sec_ctx.c#L143
?

I think I would agree adding by default the request to use KEY_EXCH in the GSS_C_INTEG_FLAG case, I think that's the main bug here.

So, if someone requests GSS_C_REPLAY_FLAG flag, that would mean we set NTLMSSP_NEGOTIATE_SIGN and NTLMSSP_NEGOTIATE_KEY_EXCH. Is that an acceptable change?

GSS_C_REPLAY_FALG is in no way related to key exchange

In our case, we use gss_init_context api and request the following flags: https://github.com/sahlberg/libsmb2/blob/2a58027e8464667a0b0215c3bac71b28dca7bf50/lib/krb5-wrapper.c#L358

In this case I think you should use GSS_C_INTEG_FLAG to indicate you want to do signing later.
Even though SMB Signing is done outside of the NTLMSSP provider.
HTH.

FYI: I pushed a few commits to master to add KEY_EXCH also when just GSS_C_INTEG_FLAG is requested.
Let me know if that is sufficient.

@simo5 yeah that is sufficient. I will get a pull request for extracting the keys.

Ok, in that case I'll close this issue as resolved.


Consider adding ROR as identifier for entities

Spawned from https://github.com/citation-file-format/citation-file-format/issues/328#issuecomment-1772582570. Examples:

https://ror.org/04bwf3e34 (DLR)
https://ror.org/00rbjv475 (Netherlands eScience Center)

As to how to approach this: under entity, add ror as key that can take the identifier.
authors:
- name: the authors
  ror: 04bwf3e34

Need to look into this but maybe [a-z0-9]{9}0[a-z0-9]{8}?
See https://github.com/ror-community/ror-schema/blob/a985c6e97293c0ebcc50aae89a2092c557c1dbec/ror_schema_v2_0.json#L116

Made PR #484

Closing as fixed in #484.


Set project compartment on Project and ProjectMembership

This is prep work for exposing a limited view of Project and ProjectMembership to project admin users.
The sequence of events will be:

Deploy this PR
Run super admin reindex
Future PR to expose the resources

Coverage: 93.911% (+0.003%) from 93.908% when pulling e4d52498dd56e9d7b26e6943c9ae9c5155f1188a on cody-set-project-compartment-on-project into 92c7eff56ae385f875d35a2bd6680bc982480712 on main.


update MANIFEST.in, enable check manifest hook

Pull Request Checklist:

[x] pre-commit hooks are installed/active in my local clone ($ pre-commit install)
[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #xyz

[ ] (If applicable) Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)

[ ] Link to issue (:issue:number) and pull request (:pull:number) has been added

[ ] bumpversion patch has been called on this branch

What kind of change does this PR introduce?

Updates manifest and enables the check manifest hook

Does this PR introduce a breaking change?
No.
Other information:

Pour des raisons qui m'échappent, git 2.37 ne fonctionne toujours pas sur doris...
Aussi, je recopie ici la description du readme de "check-manifest":

Are you a Python developer? Have you uploaded packages to the Python Package Index? Have you accidentally uploaded broken packages with some files missing? If so, check-manifest is for you.

Mes réponses: Yes, No, No.
Ainsi donc, je propose de mettre ce problème plus bas sur la pile. On attendra le moment où on se rend compte qu'il vaudrait mieux envoyer xscen sur pypi (ce qui n'est pas dans nos plans même long terme, il me semble?).


remove portMapEquals in service

Please provide a description of this PR:
portMapEquals can be replaced by maps.Equals.

Hi @yeedove. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@yeedove: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
f6e0c3ff611cadccfdb335d2b2b085db8e373c3b
link
true
/test integ-security-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yeedove: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
f6e0c3ff611cadccfdb335d2b2b085db8e373c3b
link
true
/test integ-security-istiodremote

integ-security_istio
f6e0c3ff611cadccfdb335d2b2b085db8e373c3b
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yeedove: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio
f6e0c3ff611cadccfdb335d2b2b085db8e373c3b
link
true
/test integ-security-istiodremote

integ-security_istio
f6e0c3ff611cadccfdb335d2b2b085db8e373c3b
link
true
/test integ-security

integ-security-multicluster_istio
f6e0c3ff611cadccfdb335d2b2b085db8e373c3b
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


optimize: Can CMA-ES bleed goroutines?

In IterateGlobal there is a WaitGroup to make sure that the whole list of evaluations is finished before the parameters can be updated. However, we can also stop because of function evaluations. Let's say that the number of allowed function evaluations is 199, and there are 200 functions in the list. Let's also say nTasks = 8. If the first 7 hit that waitgroup because there are no more function evaluations, but then the 8th one hits the function evaluation limit, and so it never calls IterateGlobal again, are the other goroutines waiting forever on that waitgroup?

This was fixed with #352


x86 openwrt  启动后，访问5998(1080)，访问不成功；

root@OpenWrt:~# docker run --device /dev/net/tun --cap-add NET_ADMIN -ti -e PASSWORD=li1 -v $HOME/.ecdata:/root -p <IP_ADDRESS>:5999:5901 -p <IP_ADDRESS>:5998:1080 hagb/docker-easyconnect:7.6.3
WARNING: logging deactivated (can't log to stdout when daemonized)
iptables v1.8.2 (nf_tables): Chain 'MASQUERADE' does not exist
Try iptables -h' or 'iptables --help' for more information. iptables v1.8.2 (nf_tables): Couldn't load match state':No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
Use of uninitialized value $proto in socket at /usr/bin/tigervncserver line 357.
Use of uninitialized value $proto in socket at /usr/bin/tigervncserver line 357.
Use of uninitialized value $proto in socket at /usr/bin/tigervncserver line 357.
Use of uninitialized value $proto in socket at /usr/bin/tigervncserver line 357.
New '18993ec3394f:1 (root)' desktop at :1 on machine 18993ec3394f
Starting applications specified in flwm
Log file is /root/.vnc/18993ec3394f:1.log
Use xtigervncviewer -SecurityTypes VncAuth,TLSVnc -passwd /root/.vnc/passwd 18993ec3394f:1 to connect to the VNC server.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.
(node:85) DeprecationWarning: Calling an asynchronous function without callback is deprecated.

尝试加上 -e IPTABLES_LEGACY=1


Implement chainable async array transformers

This is a proof-of-concept implementation of the new chainable and thenable asynchronous array transformation mechanism.
Changes summary:

Add new AsyncArray class which is an abstraction of an asynchronously retrieved array that can be transformed or iterated with asynchronous functions.
Add new metasync.for(arrayOrPromise) function to instantiate an AsyncArray.
Move array-related metasync functions to a separate module to avoid cyclic dependency.
Add a simple test.

TODO list:

Investigate the performance cost of such solution, maybe it can be a lightweight thenable without the need for full-blown promises, or there may be other possible optimizations.
Maybe implement a similar mechanism for any iterable objects, not just arrays.
Maybe support functions returning promises as callbacks of AsyncArray methods.

Refs: https://github.com/metarhia/MetaSync/issues/17#issuecomment-280790478
Refs: https://github.com/metarhia/MetaSync/issues/37

/cc @tshemsedinov

Landed on master in 6f6c0b9a3cb04f6bbea8b00b9ef359077fe1327e.

@metarhia/architecti @metarhia/inquisitori if there are any questions or suggestions about either this implementation or the idea in general, feel free to continue discussion in https://github.com/metarhia/MetaSync/issues/37.


fix: add tech preview warning

Adding warning for size x2 of standard instances (subject to change dynamically in near future)
Warning is displayed only when user specifies size (no default sizes are included)
Verification
[wtrocki@graphapi app-services-cli (add-warning-kafka-size ✗)]$ rhoas kafka create --name=test --provider=aws --region us-east-1 --dry-run  --size=x2
Selected Kafka size is available under technology preview
Dry run successful, arguments are valid
[wtrocki@graphapi app-services-cli (add-warning-kafka-size ✗)]$ rhoas kafka create --name=test --provider=aws --region us-east-1 --dry-run  --size=x1
Dry run successful, arguments are valid
[wtrocki@graphapi app-services-cli (add-warning-kafka-size ✗)]$

[wtrocki@graphapi app-services-cli (add-warning-kafka-size)]$ rhoas kafka create --dry-run
? Name: test
? Cloud Provider: aws
? Cloud Region: us-east-1
? Instance type: x2
Selected Kafka size is available under technology preview
Dry run successful, arguments are valid
[wtrocki@graphapi app-services-cli (add-warning-kafka-size)]$

The messages dont fit well when only one size is available:

Is that for developer instance? Something might have changed on backend since I have tested that

The messages dont fit well when only one size is available:

Is that for developer instance? Something might have changed on backend since I have tested that

Yes, it was developer instance.

{
   "instance_types":[
      {
         "id":"developer",
         "display_name":"Trial",
         "sizes":[
            {
               "id":"x1",
               "display_name":"1",
               "ingress_throughput_per_sec":{
                  "bytes":1048576
               },
               "egress_throughput_per_sec":{
                  "bytes":1048576
               },
               "total_max_connections":100,
               "max_data_retention_size":{
                  "bytes":10737418240
               },
               "max_partitions":100,
               "max_data_retention_period":"P14D",
               "max_connection_attempts_per_sec":50,
               "max_message_size":{
                  "bytes":1048576
               },
               "min_in_sync_replicas":1,
               "replication_factor":1,
               "supported_az_modes":[
                  "single"
               ],
               "lifespan_seconds":172800,
               "quota_consumed":1,
               "quota_type":"RHOSAKTrial",
               "capacity_consumed":1,
               "maturity_status":"preview"
            }
         ]
      },
      {
         "id":"standard",
         "display_name":"Standard",
         "sizes":[
            {
               "id":"x1",
               "display_name":"1",
               "ingress_throughput_per_sec":{
                  "bytes":52428800
               },
               "egress_throughput_per_sec":{
                  "bytes":104857600
               },
               "total_max_connections":3000,
               "max_data_retention_size":{
                  "bytes":1073741824000
               },
               "max_partitions":1500,
               "max_data_retention_period":"P14D",
               "max_connection_attempts_per_sec":100,
               "max_message_size":{
                  "bytes":1048576
               },
               "min_in_sync_replicas":2,
               "replication_factor":3,
               "supported_az_modes":[
                  "multi"
               ],
               "quota_consumed":1,
               "quota_type":"RHOSAK",
               "capacity_consumed":1,
               "maturity_status":"stable"
            },
            {
               "id":"x2",
               "display_name":"2",
               "ingress_throughput_per_sec":{
                  "bytes":104857600
               },
               "egress_throughput_per_sec":{
                  "bytes":209715200
               },
               "total_max_connections":6000,
               "max_data_retention_size":{
                  "bytes":2147483648000
               },
               "max_partitions":3000,
               "max_data_retention_period":"P14D",
               "max_connection_attempts_per_sec":200,
               "max_message_size":{
                  "bytes":1048576
               },
               "min_in_sync_replicas":2,
               "replication_factor":3,
               "supported_az_modes":[
                  "multi"
               ],
               "quota_consumed":2,
               "quota_type":"RHOSAK",
               "capacity_consumed":2,
               "maturity_status":"preview"
            }
         ]
      }
   ]
}

Looks like developer instances have maturity status as "preview" which doesn't seem right. Business required only x2 standard to be under that. @pb82 can we change that?

@wtrocki Bilgin said developer should be preview: https://issues.redhat.com/browse/MGDSTRM-8476?focusedCommentId=20262665&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-20262665

@rkpattnaik780 Tech preview from developer should be removed in 30 minutes timeframe.

Developer is now listed as stable.


mysqldump no longer in image?

I'm running this on q Synology docker setup and did a backup of the internal database with the command docker exec nginx-proxy-manager sh -c 'mysqldump -u nginxproxymanager -ppassword123 nginxproxymanager --single-transaction --quick --lock-tables=false > /config/backup/nginxproxymanager-backup.sql' >/dev/null 2>&1
But since I update the docker to the latest image a few days ago, I get an error telling me mysqldump is no longer there:
sh: mysqldump: not found
Do I need a full path to use mysqldump? If so, what is the full path?

With the latest image, mysql is no longer used.  Instead, sqlite is now the used database.  So I guess that if you want to backup the DB, you just need to copy database.sqlite (under the folder you mapped to /config).

Thanks for quick reply. I was already backing up the entire contents of /config So that would be enough than :)


New version: Cloudflare.cloudflared version 2022.11.0

Result: Installation Failed

Manifest
Add/Remove Programs

Name
cloudflared

Version
2022.11.0

Publisher
cloudflare

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 4041
Microsoft Reviewers: Open in CodeFlow

This package requires elevation to operate. It's failing validation because it's launching in a user context.

@wingetbot waivers Add Validation-Executable-Error

/azp run


Fullscreen Screencapture does not work on WIndows10

Original issue is about testing the league_of_steel (it captures screen using Dx9), but there is an easier way to reproduce it using miniview - which is less complex and Windows 10 build-in functionality:

cargo install miniview
miniview --fullscreen --from-path <some png image>
Press 'Print Screen' key
Open mspaint.exe and press Ctrl-V

Expected: screen you can see on your display
Actual result: white image/black screen with white image on it
This issue is observed only on Windows 10 with Intel Graphics. On Windows 7 it works fine.
Also it seams to be only problem with .fullscreen(true) option set - windowed mode works fine
Any ideas what might be wrong?

I think this is may be more windows issue - it works on windows 18xx, but not on 1909.

Closing. Reopen if this is still an issue.


multiplier cut-off when no horizontal label

The problem is that the multiplier gets cut-off when no horizontal axis label is used. This is not an easy problem to solve.

A fixed padding is required. Otherwise mouse tracking becomes very difficult.
We can't just increase the padding below the chart because most of the cookbook examples look bad (too much white space).
Maybe we should move the multiplier inside the data area?

A normal chart reader may confuse/find inconvenient if the multiplier is moved inside the chart area.
It appears to be a problem for x-axis only.
Is it possible to add a default one white space in x label to solve this issue?

default one extra white space in x label

@Bhandejiya I think you're right. This solution is not ideal because most charts don't use multiplier notation, however it seems better than the alternative (being cut off).

I just made the change 16cb018155bbf469b59606ba9b0ba7abbdc806f9
... but every image has more whitespace below the chart now.


Use github hosted ARM64 based MacOS runners in binaries workflow

Our self-hosted runner is stuck and I wondered why we just not use the new macos arm64 runners of github?
Let's see if the binaries job works on this and produces an artifact. @ffakenz would be good if you could give them a try on your machine.

[x] CHANGELOG update not needed
[x] Documentation update not needed
[x] Haddocks update not needed
[x] No new TODOs introduced

@ffakenz reported that these binaries work on his machine. Merging it.


Make Codeforces rank color look good in both light and dark mode

Make Codeforces rank color look good in both light and dark mode .Hex code for each rank can be found here

hey! can i work on this

@siddarthpai yeah, you can work on it! Do attach the screenshots of how each rank text looks in both light mode and dark mode in the PR.


verifier should not be changing invalid measured boot policy name to accept-all

Is your an issue a feature request? If so, please raise it as an enhancement

Keylime version: current latest, 4f69d9f

Description
When a measured_boot_policy_name is set an invalid value, during the verifier start
it is changed to accept-all policy.
Expected behavior vs. actual behavior
accept-all policy is benevolent and therefore using it as a default is insecure, especially if a user
wanted to use some different policy. E.g. there could be a typo in policy name.
Although the Warning is presented in a verifier log, such a thing can
remain unnoticed and a user can be under impression that the expected policy is in place.
Steps to reproduce problem

Set measured_boot_policy_name to an invalide name, e.g. elchecking and start the verifier.

Relevant logs
WARNING - Invalid measured boot policy name elchecking -- using accept-all instead.

Should we error during startup or use a reject-all policy instead? I'm more for the first one.

Error out I believe.


[Suggestion] reactor shutdown and risks

When working on reactors i found quite disappointing that you can break a working nuclear reactor (or a just turned off one) without any problem, moreover if you break a high temperature reactor, heat and part of the fuel just disappears without consequences.
I also think that despite the lack of immersion, this is really helpful when you have to test complex designs so i don't know if that is intentional.
I love this mod and i'm sure that there are already great plans for a better implementation, so i don't want to make a long term and complex suggestion, but in my opinion there are a couple of relatively simple tweaks that can add a little more immersion.
When a player turn of the reactor, he have to wait until heat reach a safe level.
If a player try to break the reactor while running, or when heat is too high 2 things happens:

an aoe poison effect with power related to the residual amount of nuclear material in the reactor for radiation emission.
a explosion proportional to the stored heat in the reactor, and maybe, if the temperature is high enought a partial fusion.
for a creative users that just want to test a reactor setup, poison is not a problem and maybe a creative only item that make heat instantly disappear can be added.

Thank you very much for this great mod and i'm looking forward to see how it will develop.

Oh yes, all that sort of stuff will be added when radiation is introduced - hold onto your hats!


Add "or" to highlight @keywords

Not really sure about if "or" is considered a keyword theoretically.
However the current nix-mode in Emacs does display it as such, and hence i thought it was missing here.

or is a contextual keyword. In { or = 1; }.or or 42, only the third or is a keyword.
We should only mark or inside select node as keyword.

@calbrecht thanks! I've merged #24 so I'll close this. As @oxalica mentions, the or should probably only be highlighted within a select, so I'll probably make that change later.

Oh, per the tests, looks like we now have the behavior we want any way, so maybe no follow up changes needed. :sweat_smile:


Blazor WASM .net 7.0.11 build with Fido2 release 3.0.1

Following code, client side, throwing exception.
Code
@page "/"
@using System.Text.Json;
@using Fido2NetLib;
Webauthn Recreate Issue
<button class="btn btn-primary" @onclick="test">Click me to recreate
@exception
@code {
string jsonData = "{"rp":{"id":"test.azurewebsites.net","name":"WebAuthn","icon":"https://test.azurewebsites.net/\"},\"user\":{\"name\":\"driver@driver.com\",\"id\":\"ZHJpdmVyQGRyaXZlci5jb20\",\"displayName\":\"driver@driver.com\"},\"challenge\":\"QHcEA7xeJRx3_SZV4uoFQQ\",\"pubKeyCredParams\":[{\"type\":\"public-key\",\"alg\":-7},{\"type\":\"public-key\",\"alg\":-257},{\"type\":\"public-key\",\"alg\":-37},{\"type\":\"public-key\",\"alg\":-35},{\"type\":\"public-key\",\"alg\":-258},{\"type\":\"public-key\",\"alg\":-38},{\"type\":\"public-key\",\"alg\":-36},{\"type\":\"public-key\",\"alg\":-259},{\"type\":\"public-key\",\"alg\":-39},{\"type\":\"public-key\",\"alg\":-8}],\"timeout\":60000,\"attestation\":\"direct\",\"authenticatorSelection\":{\"authenticatorAttachment\":\"platform\",\"requireResidentKey\":true,\"userVerification\":\"required\"},\"excludeCredentials\":[],\"extensions\":{\"uvm\":true},\"status\":\"ok\",\"errorMessage\":\"\"}";
string exception = string.Empty;
private void test()
{
    try
    {
        var deviceResponse = CredentialCreateOptions.FromJson(jsonData);
        exception = $"worked as expected {JsonSerializer.Serialize(deviceResponse)}";
    }
    catch (Exception ex)
    {
        exception = $"failure {ex.ToString()}";
    }
}

}
Exception being thrown:-
 System.NotSupportedException: ConstructorContainsNullParameterNames, Fido2NetLib.PublicKeyCredentialRpEntity Path: $.Rp. ---> System.NotSupportedException: ConstructorContainsNullParameterNames, Fido2NetLib.PublicKeyCredentialRpEntity at System.Text.Json.ThrowHelper.ThrowNotSupportedException_ConstructorContainsNullParameterNames(Type ) at System.Text.Json.Serialization.Metadata.ReflectionJsonTypeInfo1[[Fido2NetLib.PublicKeyCredentialRpEntity, Fido2.Models, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].GetParameterInfoValues() at System.Text.Json.Serialization.Metadata.JsonTypeInfo.Configure() at System.Text.Json.Serialization.Metadata.JsonTypeInfo.g__ConfigureLocked|143_0() at System.Text.Json.Serialization.Metadata.JsonTypeInfo.EnsureConfigured() at System.Text.Json.Serialization.Metadata.JsonPropertyInfo.get_JsonTypeInfo() at System.Text.Json.WriteStack.PeekNestedJsonTypeInfo() at System.Text.Json.Serialization.JsonConverter1[[Fido2NetLib.PublicKeyCredentialRpEntity, Fido2.Models, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].TryWrite(Utf8JsonWriter , PublicKeyCredentialRpEntity& , JsonSerializerOptions , WriteStack& ) at System.Text.Json.Serialization.Metadata.JsonPropertyInfo1[[Fido2NetLib.PublicKeyCredentialRpEntity, Fido2.Models, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].GetMemberAndWriteJson(Object , WriteStack& , Utf8JsonWriter ) at System.Text.Json.Serialization.Converters.ObjectDefaultConverter1[[Fido2NetLib.CredentialCreateOptions, Fido2.Models, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].OnTryWrite(Utf8JsonWriter , CredentialCreateOptions , JsonSerializerOptions , WriteStack& ) at System.Text.Json.Serialization.JsonConverter1[[Fido2NetLib.CredentialCreateOptions, Fido2.Models, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].TryWrite(Utf8JsonWriter , CredentialCreateOptions& , JsonSerializerOptions , WriteStack& ) at System.Text.Json.Serialization.JsonConverter1[[Fido2NetLib.CredentialCreateOptions, Fido2.Models, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].WriteCore(Utf8JsonWriter , CredentialCreateOptions& , JsonSerializerOptions , WriteStack& ) Exception_EndOfInnerExceptionStack at System.Text.Json.ThrowHelper.ThrowNotSupportedException(WriteStack& , NotSupportedException ) at System.Text.Json.Serialization.JsonConverter1[[Fido2NetLib.CredentialCreateOptions, Fido2.Models, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]].WriteCore(Utf8JsonWriter , CredentialCreateOptions& , JsonSerializerOptions , WriteStack& ) at System.Text.Json.JsonSerializer.WriteCore[CredentialCreateOptions](Utf8JsonWriter , CredentialCreateOptions& , JsonTypeInfo1 ) at System.Text.Json.JsonSerializer.WriteString[CredentialCreateOptions](CredentialCreateOptions& , JsonTypeInfo1 ) at System.Text.Json.JsonSerializer.Serialize[CredentialCreateOptions](CredentialCreateOptions , JsonSerializerOptions ) at WebAuthnIssue.Client.Pages.Index.test()
`
Does not occur locally and only on azure app service. App service is configured for .net 7.
Any ideas how this can be resolved?

I believe this is directly related to #380

Reading the various posts I believe the following should work. Again works locally but not on app service:
@page "/"
@using System.Text.Json;
@using Fido2NetLib;
Webauthn Recreate Issue
<button class="btn btn-primary" @onclick="test">Click me to recreate
@exception
@code {
private readonly JsonSerializerOptions _jsonOptions = new FidoBlazorSerializerContext().Options;
string jsonData = "{"rp":{"id":"test.azurewebsites.net","name":"WebAuthn","icon":"https://test.azurewebsites.net/\"},\"user\":{\"name\":\"driver@driver.com\",\"id\":\"ZHJpdmVyQGRyaXZlci5jb20\",\"displayName\":\"driver@driver.com\"},\"challenge\":\"QHcEA7xeJRx3_SZV4uoFQQ\",\"pubKeyCredParams\":[{\"type\":\"public-key\",\"alg\":-7},{\"type\":\"public-key\",\"alg\":-257},{\"type\":\"public-key\",\"alg\":-37},{\"type\":\"public-key\",\"alg\":-35},{\"type\":\"public-key\",\"alg\":-258},{\"type\":\"public-key\",\"alg\":-38},{\"type\":\"public-key\",\"alg\":-36},{\"type\":\"public-key\",\"alg\":-259},{\"type\":\"public-key\",\"alg\":-39},{\"type\":\"public-key\",\"alg\":-8}],\"timeout\":60000,\"attestation\":\"direct\",\"authenticatorSelection\":{\"authenticatorAttachment\":\"platform\",\"requireResidentKey\":true,\"userVerification\":\"required\"},\"excludeCredentials\":[],\"extensions\":{\"uvm\":true},\"status\":\"ok\",\"errorMessage\":\"\"}";
string exception = string.Empty;
private void test()
{
    try
    {
        var deviceResponse = JsonSerializer.Deserialize<CredentialCreateOptions>(jsonData, _jsonOptions);
        exception = $"worked as expected {JsonSerializer.Serialize(deviceResponse)}";
    }
    catch (Exception ex)
    {
        exception = $"failure {ex.ToString()}";
    }
}

}

@joegoldman2 did you try deploying on the app service?

Hi @joegoldman2 @Yomist
I've prepared a repo https://github.com/s21-himesh/WebAuthnIssue
I've pushed to an app service/ web app https://webauthnfido.azurewebsites.net/ so you can see the exception.
Let me know, if you need anything else.

@s21-himesh Will you be able to update to .NET 8.0 once it's released? This will likely be fixed once we cross-target .NET8.0 (soon).

@iamcarbon ideally not as we have a released prepared and this is the last outstanding issue. Is there any workaround for this? Can anyone explain why it works local vs app service?

@Regenhardt Hi Marlon, you appear to have the same error message I'm experiencing on this ticket 81709.  Can you assist with explaining how this can be resolved?

This can be solved using the Fido2.BlazorWebassembly lib in the frontend. It's not on NuGet yet, but you can just copy the code (or copy the whole project to your own solution, or add as submodule) and it should work. You can check the BlazorWasmDemo for an example, I believe the Program.cs has the needed setup and the UserService the actual usage.

I believe this will be fixed when either the Blazor lib is released as NuGet package, or all the libs are updated or multi-targeted to net7.0 for newer apps.
The models are packaged for net6.0, losing "unneeded" metadata. Here, the needed metadata is in the saved FidoBlazorSerializerContext, ready to be used for serialization.
In your case, compiling the serializer context in net7.0 creates the newer version of serialization that includes code generation. Unfortunately though, the code cannot be properly generated, as that information isn't in the NuGet package of the models.
You could of course have your app target net6.0 in order to make it use the former serialization logic, until the Fido2 lib is updated or the Blazor lib is on NuGet.
A mid point could be to add another lib to your solution that targets net6.0 and includes the serializer context, but I haven't tested this.

For anyone else who hits this issue I've updated the repo available at https://github.com/s21-himesh/WebAuthnIssue with the work around.


luci-theme-openwrt-2020: button rendering (wireguard/ advanced-reboot)

Hi
Using current OpenWrt/ master on ipq806x/ nbg6817 (also seen on ipq40xx/ map-ac2200)
master/r12964-35f208da3c
src-git packages https://git.openwrt.org/feed/packages.git^a4d19d8
src-git luci https://git.openwrt.org/project/luci.git^d0daa2c
src-git routing https://git.openwrt.org/feed/routing.git^f71d733
src-git telephony https://git.openwrt.org/feed/telephony.git^bf49bc5

I notice a strange rendering for the buttons used in luci-app-wireguard and luci-app-advanced-reboot, all other buttons I've seen so far seem to work fine - and it's working nicely using luci-theme-bootstrap.

Interface wg0

		<input class="cbi-button cbi-button-apply" type="button" name="qrcode_wg0" value="Show/Hide QR-Code" onclick="toggle_qrcode(this)" />

<form method="post" action="/cgi-bin/luci/admin/system/advanced_reboot/alternative_reboot">
				<input type="hidden" name="token" value="XXX" />
				<input id="altreboot-button" type="submit" class="cbi-button cbi-button-apply important" value="Reboot to alternative partition..." />
			</form>

<form method="post" action="/cgi-bin/luci/admin/system/advanced_reboot/reboot">
						<input type="hidden" name="token" value="XXX" />
						<input id="reboot-button" type="submit" class="cbi-button cbi-button-apply important" value="Reboot to current partition" />
					</form>

</fieldset>
<form method="post" action="/cgi-bin/luci/admin/system/advanced_reboot/power_off">
	<input type="hidden" name="token" value="XXX" />
	<input id="poweroff-button" type="submit" class="cbi-button cbi-button-apply important" value="Perform power off..." />
</form>

The attached images have been made from firefox 74/ linux, but I'm seeing the same with chromium 81/ linux.

FYI, just came across this as well (luci-app-advanced-reboot), seeing the same thing here. Thanks!

Also in luci-app-commands.

Also seeing this same behavior.

We have to add btn css class to all button input html sections.
<input class="btn cbi-button ...." type=....>

I can confirm that this indeed works for both luci-app-advanced-reboot and luci-app-wireguard.

Yep, works here as well - thanks! Are there plans to get these changes generically added in? Or make the needed changes, and submit PR's?
Thanks again.

Could someone explain how to:

We have to add btn css class to all button input html sections.
<input class="btn cbi-button ...." type=....>

I am seeing this also in VPN-Policy-Routing and would like to take care of it, please?

Could someone explain how to:

We have to add btn css class to all button input html sections.
<input class="btn cbi-button ...." type=....>

I am seeing this also in VPN-Policy-Routing and would like to take care of it, please?

In luci-app-commands you see this flaw too.

@feckert @pkgadd @cybrnook sorry it disappeared from my radar last year. Most of my luci apps are fixed, VPR is pending merge of the principal package.

@feckert @pkgadd @cybrnook sorry it disappeared from my radar last year. Most of my luci apps are fixed, VPR is pending merge of the principal package.

Thanks Stan, take your time buddy 🥇

Don't worry, all the packages I've been using are fixed by now.
The rest will need to be reported and fixed as they get noticed, contrary to the original belief the past fixes have shown that it's not a defect in the theme code, but that the individual luci apps need to declare the correct button styles..

I was able to fix locally while waiting for Stan's PR to merge, thanks for the hints guys!

LuCI base is transitioning towards using <button> elements and providing an additional .btn CSS class to style <input> elements like buttons. Ideally - where possible - apps should replace <input class="btn cbi-button" value="Label" ...> with just <button ...>Label</button>. In cases where this is not feasible (e.g. non-JS legacy CBI forms where you need actual submit buttons) a simple class="btn" should be sufficient.

LuCI base is transitioning towards using <button> elements and providing an additional .btn CSS class to style <input> elements like buttons. Ideally - where possible - apps should replace <input class="btn cbi-button" value="Label" ...> with just <button ...>Label</button>.

Is the <button> element supported in 19.07 tree or just snapshots?


Fix stack overflow due to circular call

Thanks for the PR.  I'll add this and publish a new release ASAP.


Make bevy_math's libm feature use libm for all f32methods with unspecified precision

Objective
Closes #14474
Previously, the libm feature of bevy_math would just pass the same feature flag down to glam. However, bevy_math itself had many uses of floating-point arithmetic with unspecified precision. For example, f32::sin_cos and f32::powi have unspecified precision, which means that the exact details of their output are not guaranteed to be stable across different systems and/or versions of Rust. This means that users of bevy_math could observe slightly different behavior on different systems if these methods were used.
The goal of this PR is to make it so that the libm feature flag actually guarantees some degree of determinacy within bevy_math itself by switching to the libm versions of these functions when the libm feature is enabled.
Solution
bevy_math now has an internal module bevy_math::ops, which re-exports either the standard versions of the operations or the libm versions depending on whether the libm feature is enabled. For example, ops::sin compiles to f32::sin without the libm feature and to libm::sinf with it.
This approach has a small shortfall, which is that f32::powi (integer powers of floating point numbers) does not have an equivalent in libm. On the other hand, this method is only used for squaring and cubing numbers in bevy_math. Accordingly, this deficit is covered by the introduction of a trait ops::FloatPow:
pub(crate) trait FloatPow {
    fn squared(self) -> Self;
    fn cubed(self) -> Self;
}

Next, each current usage of the unspecified-precision methods has been replaced by its equivalent in ops, so that when libm is enabled, the libm version is used instead. The exception, of course, is that .powi(2)/.powi(3) have been replaced with .squared()/.cubed().
Finally, the usage of the plain f32 methods with unspecified precision is now linted out of bevy_math (and hence disallowed in CI). For example, using f32::sin within bevy_math produces a warning that tells the user to use the ops::sin version instead.
Testing
Ran existing tests. It would be nice to check some benchmarks on NURBS things once #14677 merges. I'm happy to wait until then if the rest of this PR is fine.

Discussion
In the future, it might make sense to actually expose bevy_math::ops as public if any downstream Bevy crates want to provide similar determinacy guarantees. For now, it's all just pub(crate).
This PR also only covers f32. If we find ourselves using f64 internally in parts of bevy_math for better robustness, we could extend the module and lints to cover the f64 versions easily enough.

Marking this as contentious because of increased maintenance burden and potential confusion for new contributors, but I think that doing something like this is a good idea if we actually want to support the libm feature.