text:
Move env-cmd and eslint from devDependencies to dependencies

This PR solves #199.
It is only a fix, we need to figure out how to really install dev tools in devDependencies...
cc @AleBlondin

@benja-M-1 C'est ok pour moi !

repo: theodo/theodo-stack-generator


text:
remove dependency on EmojiSymbols and use macro to create mapping

This should make the addition of new emoji much easier and allow the automatic creation of tables

Pull Request Test Coverage Report for Build 775032572

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 0.0%

Totals

Change from base Build 774879195:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls

source: gharchive/pull-request

authors: coveralls theogf

license: MIT

license_type: permissive

license_source: github-api


text:
Upgrade from 1.0 to 1.1 fails

When attempting to upgrade a repository created by:
$ sqitch --version
sqitch (App::Sqitch) 0.9991

using a newer version:
$ sqitch --version
sqitch (App::Sqitch) 0.9992

the following error is generated:
* From 1.0 to 1.1
psql:/usr/local/lib/perl5/App/Sqitch/Engine/Upgrade/pg-1.1.sql:3: ERROR:  constraint "changes_script_hash_key" of relation "changes" does not exist

                             Table "sqitch.changes"
     Column      |           Type           |             Modifiers
-----------------+--------------------------+------------------------------------
 change_id       | text                     | not null
 script_hash     | text                     |
 change          | text                     | not null
 project         | text                     | not null
 note            | text                     | not null default ''::text
 committed_at    | timestamp with time zone | not null default clock_timestamp()
 committer_name  | text                     | not null
 committer_email | text                     | not null
 planned_at      | timestamp with time zone | not null
 planner_name    | text                     | not null
 planner_email   | text                     | not null
Indexes:
    "changes_pkey" PRIMARY KEY, btree (change_id)
    "changes_project_script_hash_key" UNIQUE CONSTRAINT, btree (project, script_hash)
 Foreign-key constraints:
    "changes_project_fkey" FOREIGN KEY (project) REFERENCES sqitch.projects(project) ON UPDATE CASCADE
Referenced by:
    TABLE "sqitch.dependencies" CONSTRAINT "dependencies_change_id_fkey" FOREIGN KEY (change_id) REFERENCES sqitch.changes(change_id) ON UPDATE CASCADE ON DELETE CASCADE
    TABLE "sqitch.dependencies" CONSTRAINT "dependencies_dependency_id_fkey" FOREIGN KEY (dependency_id) REFERENCES sqitch.changes(change_id) ON UPDATE CASCADE
    TABLE "sqitch.tags" CONSTRAINT "tags_change_id_fkey" FOREIGN KEY (change_id)  REFERENCES sqitch.changes(change_id) ON UPDATE CASCADE`

Did you originally build v0.991 from a Git clone instead of a release? It looks like that patch has already been applied to your code. You can fix it by running these commands:
ALTER TABLE sqitch.changes DROP CONSTRAINT changes_project_script_hash_key;
ALTER TABLE sqitch.changes ADD UNIQUE (script_hash);

Then run the the upgrade again.

For posterity: this also happens when two deploy sql files are identical in content (this is unusual in practice, as sqitch add inserts comments which are unique to each file).

@pdl Ah-ha. That issue was the reason for the 1.1 upgrade. Prior to that, the script hash had to be unique. 1.1 lets it be the project name and script hash.

source: gharchive/issue

authors: kabel-innovu pdl theory

repo: theory/sqitch


text:
Fix Scrutinizer CI code coverage

For some reason, Scrutinizer is not calculating code coverage.  Let's investigate and resolve this.

Fixed via 67bac658c0f0b28b3321d8c656d79aa94c35c35f and e5585df7624420b4bbb6d61f8b9cbd9f66c853c2

repo: thephpleague/commonmark-ext-table


text:
Add ResourceInterface::getMeta()

Breaking change.
We use this method in Scope::toArray(). Should we include it into the interface or not?

I think its a good idea to add it to the interface.

authors: Nyholm matthewtrask

repo: thephpleague/fractal

license: mit

license_source: bigquery


text:
Trello "An unknown application"

Calling the class with parameter name don't seems to apply it to Trello.
$Trello = new Trello([
            'identifier' => c('TRELLO_KEY'),
            'secret' => c('TRELLO_SECRET'),
            'callback_uri' => Http::url(),
            'name' => c('APP_NAME'),
            'expiration' => 'never',
            'scope' => 'read,write'
        ]);

The value of APP_NAME get passed in the URL, but the result on the Trello auth-page is "An unknown application" instead of the expected value.

Turns out the length should be at least 5-chars (no documented on Trello side either, discovered by trial-and-error).
Should the Trello class throw an exception if name length is <=4 chars ?  What do you think ? (I can do an MR for it if the proposition makes sense)

I'm not sure if this should be this package's responsibility to validate that, especially if it's not documented. However, if you would like to consider it, please
Also please note that Trello is not included as an out of the box provider in V2, however integrating custom providers is easy there.
Thanks!

authors: alegag bencorlett


text:
Library status

It's really unfortunate that the two most popular libraries in this area (https://packagist.org/?query=oauth2 client) appear to no longer be maintained.
What I wonder:

Is there a reason these libraries are no longer being maintained? Are there other popular methods besides OAuth2 that I might have missed?
How can we ensure that this library starts being maintained again? Is there a procedure for this within thephpleague?
If this library becomes maintained again, will we formulate a migration path from HWIOAuthBundle and mark that bundle as deprecated? The organization (HWI, https://hardware.info/) has ceased to exist. It's easier to maintain one library instead of two, and this aligns with The League's philosophy: "A problem shared is a problem halved."

See #1039

This library is still maintained, but we are volunteers who do this in our free time. 😅
This question is best directed at PHP League leadership.
I'm not familiar with HWIOAuthBundle. It's not a PHP League package, so I'm a little confused. Are you suggesting the PHP League take over maintenance?

I've just released version 2.8.0 of oauth2-client, which includes many of the open pull requests, including support for PHP 8.4.
Version 3.0 of oauth2-client will drop the Guzzle requirement and fully support PSR-18.

OAuth2 is not an authentication protocol, it's an authorization protocol, so the whole idea of this library is wrong - @mathieudz

This library doesn't try to use OAuth2 as an authentication protocol. It's not a one-size-fits-all solution. Rather, it abstracts the most common behaviors that developers need to build and provides a way for developers to build on top of the abstraction to support any number of providers.

@ramsey You're right, my comment was for HWIOAuthBundle, not this library, which is quite different. I mixed up the tickets.

authors: mdzt-axi ramsey stephanvierkant


text:
Unable to specify custom fields

in League\OAuth2\Client\Provider\Facebook.php line 103 we have this code:
$fields = [
'id', 'name', 'first_name', 'last_name',
'email', 'hometown', 'picture.type(large){url,is_silhouette}',
'cover{source}', 'gender', 'locale', 'link', 'timezone', 'age_range'
];
I am unable to add other fields, like birthday.
Thank you.

Hey @araratpoghosyan! The fields you listed provide some default values that don't require extra permission to access. The oauth2-facebook package is designed to help you easily obtain an access token and then leaves it up to you to make authenticated requests however you like.
If you've requested access to a field that requires extra permissions, you can just send an authenticated request with the fields you would like to receive.
Assuming you've requested the user_birthday permission.
use League\OAuth2\Client\Provider\Facebook;
use League\OAuth2\Client\Provider\AppSecretProof;

$baseUrl = Facebook::BASE_GRAPH_URL.'v2.8';
$appSecretProof = AppSecretProof::create($config['app_secret'], $token->getToken());
$params = http_build_query([
	'fields' => 'id,name,birthday',
	'access_token' => $token->getToken(),
	'appsecret_proof' => $appSecretProof,
]);
$response = file_get_contents($baseUrl.'/me?'.$params);

// Raw JSON response from the Graph API
var_dump($response);
// Response as a plain-old PHP array
$data = json_decode($response, true);
var_dump($data);

authors: SammyK araratpoghosyan


text:
Should the manipulation package be bundle to uri-components package

the uri-manipulations package only contains objects and function that manipulates URI objects based on the URI components package. Having both package separated means that everytime uri-components is updated we need to look if we did not break the uri-manipulations package. by merging both package into one we:

reduce possible BC break
ease maintenance

All the functions have been moved to the uri-components package. But a question remain should the following functions be kept on the uri-components object or should it be move the the uri-schemes repo instead:

Uri\resolve (a copy of this function already exists in form of the Uri\create function already present in the uri-scheme repository.
Uri\relativize (if the resolve function is moved then this one which is complementary should move too)
Uri\is_absolute
Uri\is_network_path
Uri\is_absolute_path
Uri\is_relative_path
Uri\is_same_document

These functions can be safely move their and I believe they belong to the schemes repo and not so much to the uri-component one. AS they returns info about the uri but don't quite interact with the URI components.

the functions listed have been moved to the scheme repo

repo: thephpleague/uri-components


text:
Using different class names

Is there a way to use a different classname other than .modal?
I get this error when changing the modal option:
VanillaModal: VanillaModal target must exist on page.
https://jsfiddle.net/2pftt4xj/

The css in the jsfiddle needs to be updated to the new class modals, then it seems to work.
https://jsfiddle.net/2pftt4xj/1/

authors: markjanzer mphm

repo: thephuse/vanilla-modal


text:
genshinstats.get_spiral_abyss() method returns Yanfei character name as 'Feiyan'

i assume this is how they do in chinese, but here is my output:

also charcter icon too haha:
https://upload-os-bbs.mihoyo.com/game_record/genshin/character_icon/UI_AvatarIcon_Feiyan.png

Yup, that's a problem with how Mihoyo handles the endpoint. Normally you only get returned the character's id, rarity, and icon, I have to get the name by pulling it out of the icon. Multiple other characters already have this issue so I can just add it for Yanfei no problem.
Thanks for informing me.

authors: pokurt thesadru

repo: thesadru/genshinstats


text:
fix(sdk): add null reference check

Add a null reference check also for actualRightController in
VRTK_SDKManager::SetupControllers().

Why is this needed? Does the GearVR have no controller at all?

Disregard, just saw this in your PR:

it does not support motion or pointer based controllers
😅

authors: bddckr gpvigano

repo: thestonefox/VRTK


text:
BUG: Do not add another scale after min_length scale_factor reached

Results in a dask.array chunk size of 0, which causes errors.

Addresses: https://github.com/InsightSoftwareConsortium/itkwidgets/issues/554

repo: thewtex/ngff-zarr


text:
QrImage exported from both

/C:/flutter/.pub-cache/hosted/pub.dartlang.org/qr_flutter-4.0.0/lib/qr_flutter.dart:7:1: Error: 'QrImage' is exported from both 'package:qr_flutter/src/qr_image.dart' and 'package:qr/src/qr_image.dart'.
QrImage constructor exists in both packages.
Steps to reproduce:
add qr: ^3.0.0 dependency in your pubspec.yaml

this problem still exist in qr_flutter ^4.0.0

@RajendraAVerma @maazkhan1998 as the maintainer seems inactive, I have fixed the issue in my PR: https://github.com/theyakka/qr.flutter/pull/204
And uploaded a new version of the package (4.1.0): https://pub.dev/packages/qr_widget

authors: RajendraAVerma maazkhan1998 vanyasem


text:
High severity vulnerability

  Package         tar
  Patched in      >=4.4.2
  Dependency of   rollup-plugin-scss [dev]
  Path            rollup-plugin-scss > node-sass > node-gyp > tar
  More info       https://npmjs.com/advisories/803

A solution would be to update in packages.json node-sass version to latest

tar has been fixed
node-gyp has been fixed
node-sass is working on it: https://github.com/sass/node-sass/issues/2625
Updating package.json shows same audit warning, so I will wait until node-sass is fixed.

@thgh , This is no longer an issue; if you still want to close the issue.

Alrighty

authors: ZaDarkSide thgh web3devin

repo: thgh/rollup-plugin-scss


text:
Deleted disqus, added dark theme and search

Deleted disqus, added dark theme and search
Link checker
The links will be checked by the build agent automatically once you create or update your PR.
You can use the following command to check the broken links locally.
docker run --rm -it --network=host --name=linkchecker ghcr.io/linkchecker/linkchecker --check-extern --no-warnings http://0.0.0.0:4000/

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


text:
chore: refactor Engine onboarding page

Revamps most of the Engine onboarding flows.
Logged out

No Engine instances

Clicking Add Engine Instance

Cloud-hosted link goes to the form.
Self-hosted link goes to https://portal.thirdweb.com/engine/getting-started
Importing an Engine URL

Multiple Engines in the list

Edit an Engine

Removing an Engine

Unauthorized

Cannot reach Engine

Connected w/ Back button

📝 Changed routes:

/dashboard/engine

(view full size)

Commit 7d2260be1c25a91ce58003a152e38dd8b3ee2729 (https://thirdweb-ndxnb3fbj.thirdweb-preview.com).

authors: arcoraven jnsdls

repo: thirdweb-dev/dashboard


text:
support errorMessage field for mined but reverted userops

This commit adds support for handling error messages in mined transactions. The MinedTransaction type in types.ts now includes an optional errorMessage field. In the mineTransactionWorker.ts file, the code has been updated to retrieve and store the error message if the userOpReceipt is not successful. This allows for better error handling and reporting for mined transactions.

PR-Codex overview
This PR adds functionality to capture error messages for mined transactions and updates mineUserOp function to handle user operation receipts.
Detailed summary

Added errorMessage field to transaction types
Updated mineTransactionWorker.ts to handle error messages for user operation receipts

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

tested:
{
	"result": {
		"queueId": "346eff2c-8fab-4f89-b6e1-0888d7e765aa",
		"status": "mined",
		"chainId": "421614",
		"fromAddress": "0xEf553047b160395c2e14268860660A3F55f09141",
		"toAddress": "0x71B6267b5b2b0B64EE058C3D27D58e4E14e7327f",
		...
		"errorMessage": "UserOp failed with reason: 'not minter.' at txHash: 0x21904b8721a876711444788a8ec81d11cde7ad42c6a5a07ec1349a65af6150b0",
		...
	}
}

repo: thirdweb-dev/engine


text:
Modular Contracts: token minting API integration

Problem solved
Integration for Modular Contracts. Specifically, ERC-20, ERC-721 and ERC-1155 core contracts and MintableERCxxx extension contracts.
Changes made

[ ] Public API changes: list the public API changes made if any

import { mintWithSignature, mintWithPermissions } from "thirdweb/modular/erc20";
import { mintWithSignature, mintWithPermissions } from "thirdweb/modular/erc721";
import { mintWithSignature, mintWithPermissions } from "thirdweb/modular/erc1155";

[ ] Internal API changes: explain the internal logic changes

How to test

[ ] Automated tests: link to unit test file
[ ] Manual tests: step by step instructions on how to test

Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
0x8dff5c0ef4A8c86d4eD8Cb20a14FEe7efa080e09

PR-Codex overview
This PR focuses on adding modular ERC721, ERC1155, and ERC20 functionalities with minting, setting sale configurations, and granting minter roles.
Detailed summary

Added mintWithPermissions, mintWithSignature, generateMintSignature exports for ERC721, ERC1155, and ERC20.
Added setSaleConfig and grantMinterRole exports for ERC20.
Updated ABI files for minting, setting sale config, and granting roles.
Added event handling functions for ContractURIUpdated, ExtensionInstalled, ExtensionUninstalled, URI, and Transfer events.

The following files were skipped due to too many changes: packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/events/Transfer.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/events/Approval.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/events/OwnershipHandoverCanceled.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/OwnershipHandoverCanceled.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/events/OwnershipHandoverCanceled.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/events/RolesUpdated.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/RolesUpdated.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/events/RolesUpdated.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/events/OwnershipHandoverRequested.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/OwnershipHandoverRequested.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/events/OwnershipHandoverRequested.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/ApprovalForAll.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/events/ApprovalForAll.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/events/OwnershipTransferred.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/OwnershipTransferred.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/events/OwnershipTransferred.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/Transfer.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/Approval.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/events/TransferBatch.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/events/TransferSingle.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/events/ConsecutiveTransfer.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/renounceOwnership.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/renounceOwnership.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/renounceOwnership.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/cancelOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/cancelOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/cancelOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/requestOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/requestOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/requestOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/name.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/name.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/name.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/owner.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/owner.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/owner.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/symbol.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/symbol.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/symbol.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/decimals.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/contractURI.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/contractURI.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/contractURI.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/totalMinted.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/totalSupply.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/totalSupply.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/startTokenId.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/DOMAIN_SEPARATOR.ts, packages/thirdweb/src/extensions/prebuilts/deploy-modular-core.test.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/getSupportedCallbackFunctions.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/getSupportedCallbackFunctions.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/getSupportedCallbackFunctions.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/getInstalledExtensions.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/getInstalledExtensions.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/getInstalledExtensions.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/uri.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/nonces.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/rolesOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/rolesOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/rolesOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/tokenURI.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/ownerOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/balanceOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/balanceOf.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC20/read/mint.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/getApproved.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/totalSupply.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/tokensOfOwner.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC721/read/mint.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC1155/read/mint.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/balanceOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/hasAnyRole.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/hasAnyRole.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/hasAnyRole.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/allowance.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/hasAllRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/supportsInterface.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/hasAllRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/supportsInterface.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/hasAllRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/supportsInterface.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/balanceOfBatch.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/multicall.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/multicall.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/multicall.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/isApprovedForAll.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/isApprovedForAll.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/burn.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/renounceRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/renounceRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/renounceRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/setContractURI.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/setContractURI.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC20/write/grantRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC721/write/grantRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC1155/write/grantRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/approve.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/setContractURI.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC20/write/setSaleConfig.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC721/write/setSaleConfig.ts, packages/thirdweb/src/extensions/modular/__generated__/MintableERC1155/write/setSaleConfig.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/read/ownershipHandoverExpiresAt.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/ownershipHandoverExpiresAt.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/read/ownershipHandoverExpiresAt.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/transferOwnership.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/transferOwnership.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/transferOwnership.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/transfer.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/explicitOwnershipOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/grantRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/approve.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/grantRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/grantRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/revokeRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/tokensOfOwnerIn.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/revokeRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/revokeRoles.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/read/explicitOwnershipsOf.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/mint.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/burn.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/mint.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/installExtension.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/installExtension.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/installExtension.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/completeOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/completeOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/completeOwnershipHandover.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/setApprovalForAll.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/setApprovalForAll.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/uninstallExtension.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/uninstallExtension.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/uninstallExtension.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/transferFrom.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/mint.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/burn.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/transferFrom.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC721Core/write/safeTransferFrom.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/safeTransferFrom.ts, packages/thirdweb/src/extensions/modular/write/mintableERC1155.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC1155Core/write/safeBatchTransferFrom.ts, packages/thirdweb/src/extensions/modular/__generated__/ERC20Core/write/permit.ts, packages/thirdweb/src/extensions/modular/write/mintableERC20.ts, packages/thirdweb/src/extensions/modular/write/mintableERC721.ts, packages/thirdweb/scripts/generate/abis/modular/ERC20Core.json, packages/thirdweb/scripts/generate/abis/modular/ERC1155Core.json, packages/thirdweb/scripts/generate/abis/modular/ERC721Core.json

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#3228  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nkrishang and the rest of your teammates on  Graphite

authors: joaquim-verges nkrishang

repo: thirdweb-dev/js


text:
Request for another example: like the Board example, but using createResource and/or real documents

The examples are really helpful, but without another example that uses some multi-field data, it's hard to generalize from the current examples. Part of the reason is that the examples treat all of the data as basically IDs; rather than displaying any additional content, they are just displaying IDs. The other missing piece is that these examples are using simple data that is synchronous, whereas real use cases more likely use createResource and/or data from async functions such as fetches. As I adapt the current examples to use real data from createResource, it feels like things get complicated quickly.

I've made the website repo (https://github.com/thisbeyond/solid-dnd-site) public now so you can raise PRs against it that we can collaborate on for more examples.
Regarding async - typically I would use an explicit order field for ease of syncs across devices which would make a good example. That said, I'm not sure how things get more complicated with async - would be good to see an example from you of the challenges encountered.

@martinpengellyphillips Thanks for publishing the docsite, that'll make it cleaner to make a variation on an example. I'll try to make a clear example of what I'm talking about.

Closing for now, since the docsite is its own repo

authors: hangtwenty martinpengellyphillips

repo: thisbeyond/solid-dnd


text:
Add more React meetups

Let's add some React meetups to the README.
If you are new to contributing to the repository, please read through the contributing guidelines.
If you need help with making your first contribution, please reach out on our discord channel.
Please note
This issue will stay open so multiple people can contribute 👍

Can I work on this?

HI @Asmit2952 !
This issue is open for multiple contributors to work on.
Read through the contributing guidelines and create a PR with your react additions.

Great! Will work on it now

repo: thisdot/tech-meetups


text:
[BUG]: Default stroke color doesn't work

I have black (the top left color) as the default stroke color.
Whenever I add a new field the stroke color is as shown in the screenshot below.
The default font color (white in my case) works fine as can be seen in the screenshot.

@EricClaeys A few things

Currently the stroke colour against the field will not reflect the default colour, this is by design and intended to reflect the fact that the field is using the default. After the field has been saved it will change to the default.
In the screenshot above there is no 'Stroke Size' so nothing will appear

Cheers
Alex

I request a change to the design based on an inconsistency which confuses me:

The "Colour" field shows the default colour, if one is set, otherwise the gray/black boxes.  This makes perfect sense.
The "Stroke Colour" field ALWAYS shows the gray/black boxes, regardless of whether or not a default Stroke Color is set.

This is inconsistent.  I suggest having BOTH fields show the default color if one is set, otherwise the gray/black boxes.
After some more testing I noticed the default stroke color does in fact work, but the "Stroke Colour" drop down doesn't show the default until AFTER a stroke size it set AND the field is saved.

Fix added - In testing will be committed with other changes

authors: Alex-developer EricClaeys

repo: thomasjacquin/allsky


text:
Doesn't work in Chromium

Using the current version of Chromium on Ubuntu 16.04:

It's likely compatible with Chromium, so I recommended removing the browser shield.

Version 56 is not compatible with css grid.
Update your browser.

Just verified that it's working in the latest Chromium.

authors: hmaesta nikolas thomaspark

repo: thomaspark/gridgarden


text:
Setup an example website using the library

You can grab Big Fish and Brick & Steel from the original repo to serve as samples. Importantly, we want to see all those new variables working... So here are the title_page metadata for each:
Big Fish
Title: Big Fish
Credit: written by
Author: John August
Source: based on the novel by Daniel Wallace
Notes:
	FINAL PRODUCTION DRAFT
	includes post-production dialogue
	and omitted scenes
Copyright: (c) 2003 Columbia Pictures

Brick & Steel
Title:
	_**BRICK & STEEL**_
	_**FULL RETIRED**_
Credit: Written by
Author: Stu Maschwitz
Source: Story by KTM
Draft date: 1/27/2012
Contact:
	Next Level Productions
	1588 Mission Dr.
	Solvang, CA 93463

Both missing some values but will give us an opportunity to examine the resultant JSON object.

Incidentally, the version of the Big Fish screenplay in the Matt Daly repo features an introductory sentence in Action markup (meaning plain-text sentence)... This is absent from the version that now ships with Highland 2...
Adding it to the version in Highland 2 yields an Action line, as expected really. Puzzling that it is omitted from one I presume to be a later version... but maybe it was omitted because it's not strictly a good example of the proper screenplay spec.


text:
Add Support for Usage Mode: Backup Power

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
I'd like to use my SB2 AC as a addon-battery for my already existing solar plant on my roof.  I don't have additional solar panels connected to the SB2 AC, i just want to be able to charge surplus energy coming from my roof to the SB2.  Preferably, I'd like it automated, when HA detects that I have surplus energy so it automatically switches the SB2 mode to "backup power" and charges it through the outlet.
Describe the solution you'd like
I'd like to request to add the "backup power" mode to usage modes for the AC model..
Describe alternatives you've considered
manually changing the mode in anker app.
Additional context
Do you need any info or log from the SB2 AC?

Hi, yes lots of various Api exports are needed to get all the new structures supported by AC model.
You can use the HA service to export the config, but gives just the picture with the current Api library.
Support for new features will require you to use newer versions of Api library for testing against your system and maybe re-run exports or test individual Api methods with the system before they can be added to the HA integration.
Please have a look to the libary and the solarbank fields issue that is tracked there. Any exports can be uploaded there.
HA integration can only be enhanced once the Api library fully supports the new feature.

Here is another library issue  to track your request.

@Vehekk did you create already an export from your SB2 AC in HA when using your main account?
You should create a complex schedule with peek and off peek first, using various combinations of weekdays and month to get the full possible schedule structure in the export. Also prior exporting, enable the new backup mode in the App to see which code it will use in the Api export.

@thomluther not yet, i'm currently not able to access my system while on a work trip. Will report more information and possible a export next week.

To my knowledge if you use Anker Smart Meter, then Anker SB2 AC automatically charge the battery with the power which otherwise goes to the grid.
I was very surprised about that.
So no need to do some automations.

That makes sense of course.
Yet, it will be helpful to get various exports to be able to switch the mode or schedule settings via Api. Especially high and low peek times may fluctuate and Anker App cannot adopt automatically.

To my knowledge if you use Anker Smart Meter, then Anker SB2 AC automatically charge the battery with the power which otherwise goes to the grid. I was very surprised about that. So no need to do some automations.

It's not working that well if you have several systems on different phases. A single E1600 "site" will take the entire meter; even if you could share it between devices you would not be able to balance across systems or return 800W per phase. The only thing you could do was adding one Anker power meter per inverter 👏👏👏. I'm happy to have one set of current transformers in the restricted space...
The more flexible solution would be using a Shelly 3EM which is not yet supported by Anker for the E1600 AC.
Right now it would be nice if the "System Einspeisevorgabe" slider was working with the current E1600 AC firmware instead of returning to 0. Unless Anker is adding another API variable to specify a charging rate (right now all you can do is turning on emergency mode which will cause the E1600 AC to suck as much energy as it can get from all bodily openings it has including the grid-directed inverter) this system will be not that useful as energy storage controlled by Home Assistant.

That makes sense of course. Yet, it will be helpful to get various exports to be able to switch the mode or schedule settings via Api. Especially high and low peek times may fluctuate and Anker App cannot adopt automatically.

Would full access to a system be useful? Right now mine is sitting in a corner collecting dust, waiting for Anker to integrate Shelly power meters. I'm going to reuse its batteries for an E1600 Pro so it's not that bad but right now it's a brick sitting in my guest room.

Would full access to a system be useful? Right now mine is sitting in a corner collecting dust, waiting for Anker to integrate Shelly power meters. I'm going to reuse its batteries for an E1600 Pro so it's not that bad but right now it's a brick sitting in my guest room.

If I get full Owner access to a AC System that might help testing against the API. But I cannot do anything before mid Jan.

Would full access to a system be useful? Right now mine is sitting in a corner collecting dust, waiting for Anker to integrate Shelly power meters. I'm going to reuse its batteries for an E1600 Pro so it's not that bad but right now it's a brick sitting in my guest room.

If I get full Owner access to a AC System that might help testing against the API. But I cannot do anything before mid Jan. And even then progress won't be quick, so I would probably need that for a couple of weeks.

Let's return to it then.
There seem to be a few more problems with the way the integration is using the API which is (as far as I have understood the support's replies) going to change with the next firmware release (which might "take a few weeks"). While the Anker app is always correctly reporting the charge level of the whole system the integration is reporting the charge of the inverter's built-in battery most of the time

and I don't see any bug that would cause this in the source. And even the Anker app can't get the additional BP1600s to charge in "emergency mode"; if the built-in batteries are full the inverter is pulling 1.1kW from the grid and sending it into nowhere. 🤦

The Screenshot you show is a calculated entity by the library, based on battery packs and SOC. If that goes down to main device in between then the response may show no installed battery packs for any reason. You need to double check if battery pack count remains stable. If it does, there may be another bug in the library for new AC device type.
Keep in mind that the shown entity is just a theoretical value. It never can reflect the real Energy in the battery. Use the Soc entities instead to monitor the fill level.

@noseshimself actually I'm not sure how you can give me Owner access to your system, since you have to use an Anker account with password to create an owning system with your BT connected AC device.
Either you would have to share the account including PW, or I would have to give you an account with PW. Either way, just one person can use it as owner for the time being.

authors: Vehekk noseshimself thomluther yhammeke

repo: thomluther/ha-anker-solix


text:
Manage global and personal filters

Users can create personal filters (only the owner che see it) or global filters (any user can see it, but only the owner can delete it).

@thomst thanks for merging.
Anyway I think global filters should still be editable by its owner, like personal filters.

@thomst thanks for merging.
Anyway I think global filters should still be editable by its owner, like personal filters.

Anyway I think global filters should still be editable by its owner, like personal filters.

@pyMan Since everyone could mess up the admin-page of each other user by creating stupid global filters, I decided to implement an extra permission for handling global filters. They can now commonly created, edited and deleted by all those users having that permission.

Anyway I think global filters should still be editable by its owner, like personal filters.

@pyMan Since everyone could mess up the admin-page of each other user by creating stupid global filters, I decided to implement an extra permission for handling global filters. They can now commonly created, edited and deleted by all those users having that permission.

As soon as I find the time to update the README and add some tests for handling global filters I will create a new release.
@pyMan Thanks for your support.

As soon as I find the time to update the README and add some tests for handling global filters I will create a new release.
@pyMan Thanks for your support.

Anyway I think global filters should still be editable by its owner, like personal filters.

@pyMan Since everyone could mess up the admin-page of each other user by creating stupid global filters, I decided to implement an extra permission for handling global filters. They can now commonly created, edited and deleted by all those users having that permission.

Cool and it works! Thank you

Anyway I think global filters should still be editable by its owner, like personal filters.

@pyMan Since everyone could mess up the admin-page of each other user by creating stupid global filters, I decided to implement an extra permission for handling global filters. They can now commonly created, edited and deleted by all those users having that permission.

Cool and it works! Thank you

authors: pyMan thomst

repo: thomst/django-admin-filter


text:
Portfolio Component

Description
This allows user to create their learning summary report at the end of the unit.
Fixes # (issue)
No issues
How Has This Been Tested?
Created the file and previewed the document
#Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as
expected)
[x] Documentation (update or new)

Hi Samadhi,
You have identified the component Portfolio correctly. Mentioned all the details including path, purpose, and interactions.
continue with migration.
Thanks!

repo: thoth-tech/documentation


text:
Add the left pointing flatMap operator

This operator is the same as flatMap >>- except that it takes the function
parameter on the left and the optional on the right. It is also right
associative which can be nice for chaining to the right.

:+1: merge away

repo: thoughtbot/Runes


text:
Remove dead link to El Capitan and Homebrew problem

El Capitan and Homebrew problem was fixed by further OS X updates
Document was removed from Homebrew docs: https://github.com/Homebrew/homebrew/commit/dd1625af7a10588fc8679a060de0bda60985b0ab

Thanks! Merged.

authors: bikolya croaky

repo: thoughtbot/laptop


text:
Uninstallation instructions

I looked into the README, the wiki and the website and couldn't seem to find information on how to uninstall the patch.

To uninstall thcrap, remove the thcrap folder and the shortcuts generated (by default on the desktop and the start menu). That's all.

authors: Chirunos brliron

repo: thpatch/thcrap

license: unlicense


text:
Feature/merch website

I created a form for the order, and I wanted to test it to see if it delivers it to netlify.

closing due to v2 of website

repo: thrd-coffee-company/thrd-site


text:
update build and coverage badges to use github actions

For build: https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow#adding-a-workflow-status-badge-to-your-repository
For coverage, it seems it's not supported, but can be uploaded to codecov, see https://github.com/codecov/codecov-action.

Badges implemented

Badges implemented

authors: abom xmonader

repo: threefoldtech/js-ng


text:
issue with threebot start command

I have started theebot by threebot start when trying to stop it threebot server  , i got below
(js-ng-JVcG1psT-py3.6) root@246413201fd5:~/js-ng# threebot stop

Threebot server Stopped

(js-ng-JVcG1psT-py3.6) root@246413201fd5:~/js-ng# threebot start
2020-07-08 08:40:12.499 | DEBUG    | jumpscale.entry_points.threebot:test_privileged_ports_bind:38 - nginx: the configuration file /tmp/tmp1ur6dnl8 syntax is ok
2020-07-08 08:40:12.499 | DEBUG    | jumpscale.entry_points.threebot:test_privileged_ports_bind:38 - nginx: configuration file /tmp/tmp1ur6dnl8 test is successful
Threebot server is running already or ports gedis:16000
are being held by your system
Please use threebot stop to stop your threebot server or free the ports to be able to start the threebot server

(js-ng-JVcG1psT-py3.6) root@246413201fd5:~/js-ng# threebot stop
Threebot server Stopped

(js-ng-JVcG1psT-py3.6) root@246413201fd5:~/js-ng# threebot start
2020-07-08 08:40:29.299 | DEBUG    | jumpscale.entry_points.threebot:test_privileged_ports_bind:38 - nginx: the configuration file /tmp/tmp6vax2axo syntax is ok
2020-07-08 08:40:29.299 | DEBUG    | jumpscale.entry_points.threebot:test_privileged_ports_bind:38 - nginx: configuration file /tmp/tmp6vax2axo test is successful
Threebot server is running already or ports gedis:16000
are being held by your system
Please use threebot stop to stop your threebot server or free the ports to be able to start the threebot server
(js-ng-JVcG1psT-py3.6) root@246413201fd5:~/js-ng#

js-ng

Author: alichaddad <chaddada@greenitglobe.com>
Date:   Tue Jul 7 16:44:00 2020 +0200

    fix filesystem find_many

Did you start the a gedis server manually?

no
even am restart the whole container (that hold  threebot) and only start 3bot server , same error comes

authors: Pishoy abom


text:
Monitoring package for crucial grid wallets

Description
A package that can be configured to monitor crucial grid wallets and escalate if they go too low

Added to the backlog, right now we have a good solution that reports on telegram many things including the wallets if they reach a specific threshold. (so probably this can go to later)

Added to the backlog, right now we have a good solution that reports on telegram many things including the wallets if they reach a specific threshold. (so probably this can go to later)

authors: robvanmieghem xmonader

repo: threefoldtech/js-sdk


text:
3bot admin: kubernetes updates (more sizes, public ip, extension)

[ ] kubernetes sizes support https://github.com/threefoldtech/js-sdk/issues/1836
[ ] kubernetes allow extending: https://github.com/threefoldtech/js-sdk/issues/2224
[ ] kubernetes public ip support https://github.com/threefoldtech/js-sdk/issues/2223
[ ]  Kubernetes delete button https://github.com/threefoldtech/js-sdk/issues/2350
[ ]  Kubenetes list nodes for deployed solutions https://github.com/threefoldtech/js-sdk/issues/2351

Done
Branch
development_vdc_kube
PR
https://github.com/threefoldtech/js-sdk/pull/2447

Verifying

authors: MElborolossy RafyAmgadBenjamin xmonader


text:
Testing: SAL

Description
We need to test different functions under Jumpscale/sal to make sure that it is working as expected.
Steps to accomplish the task

Gather all the requirements for each SAL and list them in the traceability matrix.
Design the test cases according to those requirements and report them in TestQuality
Execute the test cases and report different bugs (Manual execution)
Automate those test cases

Modules under testing
Jumpscale/sal:

[ ] bash
[ ] bcdbfs
[ ] bind
[ ] btrfs
[ ] disklayout
[ ] dnsmasq
[ ] fs
[ ] hostfile
[ ] kvm
[ ] netconfig
[ ] nettools
[ ] nfs
[ ] nginx
[ ] nic
[ ] openvswitch
[ ] process
[ ] qemu_img
[ ] rsync
[ ] samba
[ ] shorewall
[ ] sshd
[ ] ssl
[ ] tls
[ ] ubuntu
[ ] ufw
[ ] unix
[ ] windows

What should be delivered?
1- Traceability matrix
2- Test cases description in testquality
3- Automation test cases

bash moved to tools so it will be tested in tools.
Start working on fs.

repo: threefoldtech/jumpscaleX


text:
Could not connect to machines created from the dashboard using mycelium on windows

Description :
while testing Mycelium on Windows and Myceloumflut
Mycelium worked fine on Windows. I could easily ping Mycelium using ping -6  <mycelium_ip> and communicate with other machines having mycelium installed and the binary running :

but could not do the same to machines deployed from the grid from windows

Can you try to ping the IP instead of trying to ssh to it?

@LeeSmet pinging ips works fine with me

Given that ping works fine, this indicates that mycelium itself seems to be functioning as expected and delivers packets. Connection timed out would suggest then that the tcp connection handshake, or later ssh connection handshake doesn't complete, i.e. packets are lost/dropped. I'd suggest to try and ssh to the machine using another transport (regular ipv6/public ipv4 if that is available/wireguard). If that works, check if there are firewall rules and what those are, if the ssh server is listening on addresses which include the mycelium interface, and  if there is nothing there, tcpdump the mycelium interface to see if any packets actually do come in for the ssh connection

Mycelium worked fine on Windows
but could not do the same to machines deployed from the grid from windows

Hi @khaledyoussef24
Could you try to change Windows with other OS, like Linux or macos with mycelium binary from this repo (not from myceliumflut repo)

Working fine on both linux and macos
And has the abiltiy to connect to machines with mycelium created on the grid

OK, i can reproduce it, using command line mycelium, not the flutter one.
Did few scenarios

windows to Linux(my PC)

ping OK
ssh OK

2.Linux (my PC) to Linux on grid

ping OK
SSH OK

Windows to Linux on grid

ping OK
ssh : failed

ssh: connect to host 4d3:395f:77d0:e398:ff0f:0:400:2 port 22: Connection timed out

I got the error log
thread 'tokio-runtime-worker' panicked at C:\Users\Administrator\mycelium\mycelium\src\tun\windows.rs:64:40:
range end index 1452 out of range for slice of length 1400
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

And found that max packet size and MTU are 1400 instead of 1500.
Sent the fix on #484

myceliumflut latest version made by Iwan worked fine and while running the app ,I could connect to machines on the grid using mycelium ip

It was using myceliumflut.  shall we consider this as done ?

shall we consider this as done ?

It will be done after #484 getting merged.
The binary i sent to you is a PoC of this solution.

authors: LeeSmet iwanbk khaledyoussef24

repo: threefoldtech/mycelium


text:
Add the contract manual list to Your Contracts page

Description
Add the https://manual.grid.tf/playground/contracts_list.html link to the information on your contract page.

Verified,
Devnet, 000eea2.
TC2162 - List Deployments
https://manual.grid.tf/playground/contracts_list.html
https://manual.grid.tf/tfchain/tfchain.html

Verified:

Devnet
ec2ed3d

authors: A-Harby ramezsaeed

repo: threefoldtech/tfgrid-sdk-ts


text:
Yggdrasil connect in production is crashing.

Button just crashes the app.

Fixed


text:
The process of detecting dirty bits in a chunk will not stop.

Thank you for sharing your research results !
During the process of a producer filing a chunk, the detection of dirty bits within the chunk after it is filed will not stop. Is this situation something that requires intervention to terminate, or should one wait for an extended period of time?

Once you see this, you can continue... It is normal, and bug-free lol

authors: csuastt liuzhenO

repo: thu-ml/RoboticsDiffusionTransformer


text:
add web demo/models/datasets to ICML 2022 organization on Hugging Face

Hi, congrats for the acceptance at ICML 2022. We are having an event on Hugging Face for ICML 2022, where you can submit spaces(web demos), models, and datasets for papers for a chance to win prizes. The hub offers free hosting and would make your work more accessible to the rest of the community. Hugging Hub works similar to github where you can push to user profiles or organization accounts, you can add the models/datasets and spaces to this organization: https://huggingface.co/ICML2022, after joining the organization using this link https://huggingface.co/organizations/ICML2022/share/BpynfJtfsOTktlmXYoKNqqCnyufKLFXuay, let me know if you need any help with the above steps, thanks.

Hi, thanks a lot for your invitation. I have joined this organization.

@wuhaixu2016 great thanks, let me know if you need any help setting up a gradio demo for Flowformer on Hugging Face, here is how to get started https://huggingface.co/course/chapter9/1?fw=pt

repo: thuml/Flowformer


text:
Occasional crash related to push

Maybe at the time of network change.
type: crash
osVersion: google/shiba/shiba:14/AP2A.240905.003/2024092900:user/release-keys
package: com.fsck.k9:39005
process: com.fsck.k9
processUptime: 53541 + 412 ms
installer: dev.imranr.obtainium

java.util.ConcurrentModificationException
	at java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:1061)
	at java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:1084)
	at com.fsck.k9.controller.push.PushController.updatePushEnabledListeners(PushController.kt:309)
	at com.fsck.k9.controller.push.PushController.updatePushers(PushController.kt:214)
	at com.fsck.k9.controller.push.PushController.access$updatePushers(PushController.kt:34)
	at com.fsck.k9.controller.push.PushController$launchUpdatePushers$1.invokeSuspend(PushController.kt:153)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1012)
	Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@6d2bb45, java.util.concurrent.Executors$FinalizableDelegatedExecutorService@926f29a]

This will be fixed by #8225 and should be included in 8.0b2.

Apparently I missed your description and didn't think of other ways than removing an account to trigger that crash. Changing the network is just another way to trigger the same crash.

authors: cketti jayb-g

repo: thunderbird/thunderbird-android


text:
[QUESTION]

First check

[x] I used the GitHub search to find a similar issue and didn't find it.
[x] I searched the FastAPI documentation, with the integrated search.
[x] I already searched in Google "How to X in FastAPI" and didn't find any information.

Description
How can I define Enum into request model?
class Processors(enum.Enum):
    Python = 'python'

class PostRepository(BaseModel):
    file: str
    processor: Processors

I have such endpoint:
@app.post('/repositories', status_code=201)
async def post_repositories(request: PostRepository):
    pass

After starting application, FastAPI don't take Enum field:

The SwaggerUI I find often has trouble displaying Enums. Try the redoc docs at /redoc instead of /docs to see if it's displayed.  You can also check the /openapi.json document directly to make sure your Enum is included.
You can still test the endpoint using your enum value, SwaggerUI just doesn't include it in the body for some reason. Might be fixed once Pydantic starts declaring enums as schemas in the next version? Not sure.

Could you try this?
class Processors(str, enum.Enum):
    Python = 'python'

class PostRepository(BaseModel):
    file: str
    processor: Processors

Thanks for the help here everyone! :clap: :bow:
I imagine you solved your problem, so thanks for closing the issue :+1:

authors: Hedgehogues dbanty tiangolo zamiramir

repo: tiangolo/fastapi


text:
📝 Update docs on Pydantic using ujson internally

The docs currently suggest that Pydantic uses ujson for faster JSON parsing. This seems to not be the case since ca. 2020, so I think at this point it's safe to remove this line from the docs.

Great, thanks @mvasilkov! ☕

authors: mvasilkov tiangolo


text:
增加忘记密码功能，优化文档说明

1.增加忘记密码功能
2.优化文档说明

新功能

repo: tianmiantech/WeFe


text:
在navigationView和下面的viewController中间加一个固定的view，viewcontroller被加入的view盖住了一部分，求解

求解

在navigationView和下面的viewController中间加一个固定的view，viewcontroller被加入的view盖住了一部分，求解


text:
New App: IFPA Events

Adds a new app:

The International Flipper Pinball Association (IFPA) is a organizing body for competitive pinball
The app will show you upcoming tournaments within the radius of a defined location

This is the first app I'm submitting, so please let me know there's anything that needs changes or adjustments.
Note: Second attempt after issues with #2653

I have read the CLA Document and I hereby sign the CLA

repo: tidbyt/community


text:
Serve GIF file instead of webp in server mode

Currently render command has a switch (--gif) to create a GIF file. But when you use serve command, this option is missing. I am trying to use this with a device than doesn't have webp available, but GIF is supported. Is it possible to add such support? Thanks

Definitely open to a PR for this (pixlet serve --gif).

repo: tidbyt/pixlet


text:
Fix for Uploader sporadically crashing on Macs

See https://trello.com/c/6MjMZWOb for more details.

Pinging @jebeck for review - two-line change.

 [uploader][bug] Uploader Crashes after fresh install on new Mac with new Chrome.

repo: tidepool-org/chrome-uploader


text:
Error

Traceback (most recent call last):
File "/usr/local/bin/gdmkdir.py", line 10, in
from gdcmdtools.mkdir import GDMkdir
File "/usr/local/lib/python2.7/dist-packages/gdcmdtools/mkdir.py", line 19, in
from gdcmdtools.base import GDBase
File "/usr/local/lib/python2.7/dist-packages/gdcmdtools/base.py", line 7, in
from apiclient.discovery import build
File "/usr/local/lib/python2.7/dist-packages/apiclient/init.py", line 1, in
from .base import APIClient, APIClient_SharedSecret
File "/usr/local/lib/python2.7/dist-packages/apiclient/base.py", line 3, in
from urllib3 import connection_from_url
ImportError: No module named urllib3

Hi jayantanth,
How do you install gdcmdtools?
Could you try to install requests? It should fix your problem.
$ sudo pip install requests

authors: jayantanth tienfuc

repo: tienfuc/gdcmdtools


text:
Update support and compatibility docs for 3.20 EP1

Product Version(s):
Calico Enterprise
Issue:
Update support and compatibility
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@Glen-Tigera  FYI

LGTM!

authors: ctauchen sabags

repo: tigera/docs


text:
Reconcile performance hotspots secrets

Description
Reconcile for elastic access for performance-hotpots, similar to the one for AD Jobs and Intrusion Detection

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

/merge-when-ready

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it.

authors: freecaykes marvin-tigera

repo: tigera/operator


text:
fix: broken link in account-balance.md

I noticed this link was broken when I was looking through the nodejs docs

Thanks for noticing this and submitting the fix!

authors: emschwartz lewisdaly

repo: tigerbeetle/tigerbeetle


text:
Remove required_approvals and stick to using bors

So we can implement the workflow @matklad suggested here.

bors r+

bors r+

bors r+
My mistake, I thought github settings changes auto-saved but I had to scroll down and click "save" :facepalm:

bors r+
This should pass now that https://github.com/tigerbeetledb/tigerbeetle/pull/388 is merged.

@batiati can you take a look at this flaky CI failure?: https://github.com/tigerbeetledb/tigerbeetle/actions/runs/3895100141/jobs/6650260999

bors r+
(Trying again to merge this; hopefully will have better luck with the flaky test).

can you take a look at this flaky CI failure?:

I suspect it is actions/upload-artifact@v3's fault, the artifact is not being restored sometimes. I'll change the CI to use actions/cache@v3, the same action used by the Go client CI.

authors: batiati cb22 sentientwaffle

repo: tigerbeetledb/tigerbeetle


text:
feat: Add Vue3 Provide/Inject Plugin

This PR adds a new plugin for Vue3 using Ziggy via the Provide/Inject Composition API. Using the advanced Vue set up, I ran into my problem when trying to use route() in setup(). I saw a possible solution in https://github.com/tighten/ziggy/issues/454#issuecomment-906418423 but it didn't feel like a super maintainable solution, also mixins are not recommended in Vue3 anymore.

Note: I'm not familiar with microbundles, so if anything needs to be edited in package.json, please let me know.

For this to work, you have to update your mix alias like below:
mix.alias({
    ziggy: path.resolve('vendor/tightenco/ziggy/dist/vue3'),
});

and the import of ZiggyVue3:
import { createApp } from 'vue';
import { ZiggyVue3 } from 'ziggy';
import { Ziggy } from './ziggy';
import App from './App';

createApp(App).use(ZiggyVue3, Ziggy);

The route() helper will still be registered globally and you gain the below functionality:

Thanks for the PR! Making inject work out of the box like this would be awesome. Would it be possible to accomplish this using our existing Vue plugin? Could be just tweak it a bit and add app.provide('route', route)?

@bakerkretzmar I can def give it a shot to add it to the existing Vue plugin, but on the Vue 2 docs the provide/inject API is only supported in v2.2.0+. If you're not worried about that requirement, I'll circle back later today!

@bakerkretzmar After spinning up a Vue2 Inertiajs demo, I don't think it will be possible with one plugin. I believe that the Vue2 provide/inject is only from parent to child component and not possible globally. I could be wrong if you have better Vue2 chops than I do and want to give it a shot, sorry.

I was about to make a similar PR so I'll add my 2 grains of salt, it's definitely possible to support it in a single plugin
The prefered method is to export a "useRoute" method which will return the route method created when installing the plugin

This is pretty much how:
import route from './index.js';

let installedRoute = null;

export const ZiggyVue = {
  install: (v, options, property = 'route') => {
    installedRoute = (name, params, absolute, config = options) => route(name, params, absolute, config);
    v.mixin({
      methods: {
        [property]: installedRoute,
      },
    });
  },
};

export const useRoute = () => installedRoute;

I think we can probably get this working without a separate Vue 3 plugin, Vue has a version property we can check. Something like import { version } from 'vue' and then if we're on Vue 3, we call app.provide().
I don't want to split it out into two different plugins if possible.

@bakerkretzmar Well, I have a version not using inject provide that does that, I'd like to use inject provide as well, the problem is with the ìmport { inject } from 'vue'; because we can't have dynamic imports and the ìnject` doesn't exist in vue 2 it woud likely throw an error

Not import { inject } from 'vue', import { version } from 'vue'. version exists in Vue 2 and 3.

I don't think you understood the issue, the problem is with microbundle --external none then if we import { version } from vue then it won't matter the version because it will bundle vue and use the vue installed in ziggy, which is a problem. This is what I'm saying, anything importing something from vue is a problem with this configuration

I don't think you understood the issue, the problem is with microbundle --external none then if we import { version } from vue then it won't matter the version because it will bundle vue and use the vue installed in ziggy, which is a problem. This is what I'm saying, anything importing something from vue is a problem with this configuration

Okay, so I have read up on this a little more and just pushed an update to this PR.
@Tofandel I tested your solution and it works, but it may present some uneeded complexity with the options of changing the route name and the ability to turn off the global mixin in favor of an import with useRoute(). A user can just not install the plugin into the Vue instance and import route diretly with import route from '../../../../vendor/tightenco/ziggy/dist'; if they want to.
In the new implementation I just pushed I also decided to remove the below line since the new version leaved the Vue 2 implementation unaffected.
app.config.globalProperties.route = _route;
The new version allows the Vue 2 implementation to work without any breaking changes and provides Vue 3 with Provide/Inject, also without chaning the installation steps. Mixins are available in Vue 3 but there are many places in the docs saying they are no longer recomended. There are many blog posts out there listing the reasons why. I tested all the below implementations and can confirm they work. So this version provides a clear break in the plugin to align with Vue best practices, Vue 2 - Mixin is okay, Vue 4 Provide/Inject.

Note: There are several ways to check if provide is undefined or parsing out the Vue version. If you prefer another syntax just let me know. Also, version > 2 was an attempt to potentially future proof it a little assuming the composition API is here to stay.

Vue 2 - Unaffected
<template>
    route
    url
</template>

Vue 3 - Options API
<template>
    route
    url
</template>

Vue 3 - Composition API
<template>
    route
    url
</template>

@bakerkretzmar Updated the PR with the code from the below as discussed.
https://stackblitz.com/edit/vitejs-vite-zuznmu

@c-fitzmaurice thanks a lot!

The check should not have been on the version but just whether or not vue is available, as the composition api is available in vue 2 with an official package

Interesting find, then I guess users of vue2 composition API will have to provide it manually in their root component

So this version provides a clear break in the plugin to align with Vue best practices, Vue 2 - Mixin is okay, Vue 3 - Provide/Inject.

The ideal would be to use composables with the Vue Composition API
What is a "Composable"?

In the context of Vue applications, a "composable" is a function that leverages Vue's Composition API to encapsulate and reuse stateful logic.

Provide / Inject serve to pass information from a parent component to another child component, without going through the parent component.
With the "Composition API" option, using Provide/Inject is not best practice in Vue 3.

authors: Tofandel bakerkretzmar c-fitzmaurice psr-cookies

repo: tighten/ziggy


text:
Jigsaw node module integration

I'd like to discuss before a decision is made to or not to merge.  And I'm open to transferring ownership of the node module to tightenco so it's all within the same family.
The current module can be found here - https://github.com/JoshMoreno/node-jigsaw
After using Jigsaw the past few weeks, I've really taken a liking to it.  There were just a few things I thought could be better.
Problems

CSS only changes don't get injected.
It causes a full page reload. Not a big deal, but a bit of a drag when styling interactive components (i.e. menu only visible when triggered from a user click).
tasks dir has quite a bit of hardcoded config
This will make future upgrades more difficult for the user and possibly for maintainers to have to document/explain.
Production webpack build isn't self contained
It builds to source which muddies up the development commits.
Build process requires two independent steps
Currently a user has to have webpack compile production assets then have jigsaw do it's thing.

Solutions
So not all of the above require a separate node module to solve, but I think it's where the solution belongs. And though I'm hesitant on separating this from the main package, I do think the benefits outweigh the cons.

Create our own watcher and only run a jigsaw build $env when we need to do so. That way the right files are getting changed at the right time.
Pull into the module and let the user override anything with a simple Object.assign. Also has the benefit of one less folder in the root. A small but very satisfying win in my book.
Can be solved with a mix.inProduction() check. But this needs to run after jigsaw build production.
The module essentially has the same path() function to check where jigsaw is installed. But this time it's installed in the node_modules/.bin so we can have a script that does jigsaw build production && npm run production.

Hope all the above makes sense.
Any thoughts or concerns?

Give it a test run.
composer.json
{
  "repositories": [
    {
      "type": "vcs",
      "url": "https://github.com/JoshMoreno/jigsaw"
    }
  ],
  "require": {
    "tightenco/jigsaw": "dev-jigsaw-node-module-integration"
  }
}

then..
composer install && npm install && npm run watch

Try changing some blade templates (reload), sass (inject), and js (reload).
Then to build production. Which should give you a build_production folder with optimized css and js. Source assets should be left unoptimized.
npm run jigsaw

This looks very intriguing! I'll give it a test run...

One important issue that I can foresee is that this breaks Mix versioning, i.e. you couldn't include the following in your master template:
<link rel="stylesheet" href="{{ mix('css/style.css', 'assets/build') }}">

...since, as far as I can tell, you're essentially running jigsaw build to build the site before assets are compiled, meaning no Mix manifest will exist when the mix() helper runs. This is why the current process includes building assets into source first, and then running jigsaw build to copy them to build_local or build_production.

Ahhh. Yes. Good catch. So this really only affects number 3 right?

Production webpack build isn't self contained
It builds to source which muddies up the development commits.

I'll need to good think about this one. 🤔
But in the meantime and perhaps moving forward I can revert the changes to solve number 3. I'll do some tests tomorrow to make sure mix() is working correctly.

@damiani Yea I don't see a decent way of solving number 3. Every possible solution feels dirty and hacky. We definitely need to run webpack before running  jigsaw. I've reverted the changes that attempted to solve this.
Also added versioning, aka mix(), to the master.blade.php so it's more complete out of the box.
Any other concerns or things I can improve on here?

authors: JoshMoreno damiani

repo: tightenco/jigsaw


text:
refactor: Improves file structure and typings

This pull request refactors the codebase to make contributions faster by

Updating the file structure by moving modules into it's own files.
Make types to be more strict.

Next to that, it also

Fixes the dependencies
Adds editor.config for fast formatting

overall restructuring looks great. I did not understand your comment on "Make types to be more strict." Which change is doing this?

overall restructuring looks great. I did not understand your comment on "Make types to be more strict." Which change is doing this?

overall restructuring looks great. I did not understand your comment on "Make types to be more strict." Which change is doing this?

I’ve updated types specially around filters and logical filters and utility methods where they were being used. Instead of using generic type T in every method, now the use type FieldTypes which is union of primitive values. Also instead of having object as return type, they’re strictly typed.

authors: JigarJoshi designcode

repo: tigrisdata/tigris-client-ts


text:
Research other email integrations

Research Policies of major email hosts so that we know whether we can do (successfully execute) an integration with them before we even touch the code.
Start with:
1. Outlook
2. Apple Mail Host
If Outlook works, let's go with this, as we know that most our users are Android, so unlikely that they use Apple mail.
Unfortunately, due to the fact that most users are Android users Apple Iphone email client will not be the most popular option.
Email client usage worldwide, collected from 1.1 billion email opens - July 2021
For all users:
https://emailclientmarketshare.com/
#2 is Gmail with 34%
#3 is Apple Mail with 9%
#4 is Outlook with 6%
#5 Yahoo!Mail - 4%
2019 stats:
https://www.statista.com/chart/17570/most-popular-email-clients/
"Gmail has a market share of 25%.
Gmail and Apple iPhone are the two most favored solutions for reading emails. Together, they account for 62% of the email client market share. Data from December 2019 shows that iPhone accounts for 37% of all email opens, followed by Gmail with 25%.
Apple Mail is the next most commonly used email solution, with 10% of all opens, followed by Outlook and Yahoo! Mail with 8% and 6%, respectively, to round out the top 5.
(Email Client Market Share)"

Okay, we should be able to do a Microsoft integration using their new Graph API. Microsoft's identity platform TOS are linked below, but there does not seem to be any additional approval required other than registering the application.
https://docs.microsoft.com/en-us/graph/auth/auth-concepts
https://docs.microsoft.com/en-us/outlook/rest/get-started
https://docs.microsoft.com/en-us/legal/microsoft-identity-platform/terms-of-use

authors: annastoilova mike-audi

repo: tiki/app


text:
Resolve Moshi dependency collision in maven

In the fat-aar build, we are including Moshi dependency since it does not work in integration tests when building aar locally.
In the maven central repository, the pom file includes Moshi as a dependency.
It leads to a dependency collision when importing the SDK from Maven Central: both the tiki-sdk-android binary and the project that is importing it will have Moshi classes.
Acceptance criteria
1 - TIKI SDK Android can be used from a Maven repository without collision
2 - TIKI SDK Android can be built locally and include Moshi dependency

adding this issue to #131

repo: tiki/tiki-sdk-android


text:
UCP: Migrate scalar function Rpad from TiDB

Description
Port the scalar function Rpad from TiDB to coprocessor.
Score

50

Mentor(s)

@andylokandy

Recommended Skills

Rust programming

Learning Materials
Already implemented expressions ported from TiDB

https://github.com/tikv/tikv/tree/master/components/tidb_query/src/rpn_expr)
https://github.com/tikv/tikv/tree/master/components/tidb_query/src/expr)

/pick-up-challenge

authors: hsqlu lonng

repo: tikv/tikv


text:
Resolved TS is not updated with async commit transactions

What version of TiKV are you using?
Master (35c66d38ff8180f3652643e35575590d9ab57fc1)
Steps to reproduce
Enable failpoints in TiDB (with unmerged https://github.com/pingcap/tidb/pull/22431):
github.com/pingcap/tidb/store/tikv/asyncCommitDoNothing=50%return
github.com/pingcap/tidb/store/tikv/runTTLManager=return
github.com/pingcap/tidb/store/tikv/shortPessimisticLockTTL=return
github.com/pingcap/tidb/store/tikv/twoPCShortLockTTL=return

Set the interval of updating PD physical TS to 2s.
Run tipocket/pbank with async commit and 1PC enabled:
./pbank -case=multi_bank -prepare-sql='set global tidb_enable_async_commit = 1;set global tidb_enable_1pc = 1;'

What did you expect?
CDC works well.
What did happened?
From the monitor, we see some TiKV failed to update the resolved TS, so CDC didn't work.

cc @MyonKeminta @youjiali1995

cc @MyonKeminta @youjiali1995

When doing an unprotected rollback and there is already a write record with the same commit TS, we don't write any write record:
https://github.com/tikv/tikv/blob/7b057aa9bdc0b1c18d4d8a90fd731f461105e62e/src/storage/mvcc/txn.rs#L35
And CDC now only untracks locks according to writes.

When doing an unprotected rollback and there is already a write record with the same commit TS, we don't write any write record:
https://github.com/tikv/tikv/blob/7b057aa9bdc0b1c18d4d8a90fd731f461105e62e/src/storage/mvcc/txn.rs#L35
And CDC now only untracks locks according to writes.

Good catch! Can CDC untrack locks according to deleting locks too? I'm afraid the assumption that every lock deletion has a corresponding write can't hold. @overvenus

Good catch! Can CDC untrack locks according to deleting locks too? I'm afraid the assumption that every lock deletion has a corresponding write can't hold. @overvenus

Good catch! Can CDC untrack locks according to deleting locks too? I'm afraid the assumption that every lock deletion has a corresponding write can't hold. @overvenus

I tried but found it not so easy. The locks are managed by start_ts. However, when deleting a lock, we have no information about the deleted lock. So we cannot find the lock by start_ts and untrack it.

Good catch! Can CDC untrack locks according to deleting locks too? I'm afraid the assumption that every lock deletion has a corresponding write can't hold. @overvenus

I tried but found it not so easy. The locks are managed by start_ts. However, when deleting a lock, we have no information about the deleted lock. So we cannot find the lock by start_ts and untrack it.

cc @5kbpers

cc @5kbpers

I talked with @5kbpers and conclude there are two solutions.

As a simple fix for this issue, we can remove the optimization. Always write an overlapped rollback no matter if it is protected. Then, CDC can track such a rollback.

If we do not want such a constraint of transactions, we can add another data structure to the resolver to track locks by key. Then, we can let the resolver find the key first, then remove the start_ts from the heap. In this solution, we can track locks through lock cf applies.

I talked with @5kbpers and conclude there are two solutions.

As a simple fix for this issue, we can remove the optimization. Always write an overlapped rollback no matter if it is protected. Then, CDC can track such a rollback.

If we do not want such a constraint of transactions, we can add another data structure to the resolver to track locks by key. Then, we can let the resolver find the key first, then remove the start_ts from the heap. In this solution, we can track locks through lock cf applies.

authors: MyonKeminta sticnarf youjiali1995


text:
resolevd_ts: stop serving stale read while applying snapshot

Signed-off-by: linning linningde25@gmail.com

What problem does this PR solve?
Problem Summary:
Applying snapshot is handle by ingesting sst files for different cf one by one, it is not atomic, reading while applying snapshot may get inconsistent result
What is changed and how it works?
What's Changed:
Stop serving stale read while applying snapshot by reset the safe_ts to 0 and stop updating it before starting to apply snapshot and resume the safe_ts after applying snapshot is finished.
Tests

Integration test

Release note

No release note

/test

/test

/rebuild

/merge

/merge

/merge

authors: NingLin-P dianqihanwangzi nolouch


text:
Fix label leaking of thread metrics

Signed-off-by: 5kbpers tangminghua@pingcap.com

What problem does this PR solve?
Issue Number: close #11195
Problem Summary:
Here we buffered all labels (thread IDs), then labels can not be dropped even if threads have been exited.
https://github.com/tikv/tikv/blob/13db52e63a746f546cdf6fa3c779378f228d907c/components/tikv_util/src/metrics/threads_linux.rs#L25-L40
What is changed and how it works?
What's Changed:

Replace Counter with Gauge
Reset metrics after thread IDs updated

Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test

Side effects

Performance regression

Consumes more CPU

Release note
Fix label leaking of thread metrics

@5kbpers tells me that about 200k tokio runtime threads are created in about 1 months. This is really often.
I think we should also make the tokio blocking threads live longer (https://docs.rs/tokio/1.13.0/tokio/runtime/struct.Builder.html#method.thread_keep_alive). Otherwise, we might meet the problem https://github.com/tikv/tikv/pull/7306 again. cc @breeswish

about 200k tokio runtime threads are created in about 1 months.

Amazing!

/merge

/merge

/merge

@sticnarf  Indeed. Nice catch! The current thread behavior will break the fix of #7306. I have created a new issue to track it: https://github.com/tikv/tikv/issues/11204
@kennytm What do you think?

authors: 5kbpers BusyJay breeswish sticnarf


text:
[DNM] gbk_chinese_ci hotfix

Signed-off-by: xiongjiwei xiongjiwei1996@outlook.com

What is changed and how it works?
Close #xxx
What's Changed:
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Please add a release note.
If you don't think this PR needs a release note then fill it with None.
If this PR will be picked to release branch, then a release note is probably required.

/run-build-arm64 comment=true

authors: xiongjiwei zimulala


text:
can't compile nuvolaruntime on Fedora 25

$ rpmbuild -ba nuvolaruntime.spec
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.JkPRxb
+ umask 022
+ cd /home/martin/rpmbuild/BUILD
+ cd /home/martin/rpmbuild/BUILD
+ rm -rf nuvolaruntime-4.4.0
+ /usr/bin/gzip -dc /home/martin/rpmbuild/SOURCES/nuvolaruntime-4.4.0.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd nuvolaruntime-4.4.0
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ rm ./waf
+ rm -rf ./.waf
+ rm branding/default.json
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.dQ5IhL
+ umask 022
+ cd /home/martin/rpmbuild/BUILD
+ cd nuvolaruntime-4.4.0
+ waf-3 configure --prefix=/usr --libdir=/usr/lib64 --nounity
Setting top to                           : /home/martin/rpmbuild/BUILD/nuvolaruntime-4.4.0
Setting out to                           : /home/martin/rpmbuild/BUILD/nuvolaruntime-4.4.0/build
fatal: Not a git repository (or any of the parent directories): .git
Traceback (most recent call last):
  File "/usr/share/waf3/waflib/Scripting.py", line 121, in waf_entry_point
    run_commands()
  File "/usr/share/waf3/waflib/Scripting.py", line 182, in run_commands
    ctx=run_command(cmd_name)
  File "/usr/share/waf3/waflib/Scripting.py", line 173, in run_command
    ctx.execute()
  File "/usr/share/waf3/waflib/Configure.py", line 84, in execute
    super(ConfigurationContext,self).execute()
  File "/usr/share/waf3/waflib/Context.py", line 87, in execute
    self.recurse([os.path.dirname(g_module.root_path)])
  File "/usr/share/waf3/waflib/Context.py", line 128, in recurse
    user_function(self)
  File "/home/martin/rpmbuild/BUILD/nuvolaruntime-4.4.0/wscript", line 187, in configure
    add_version_info(ctx)
  File "/home/martin/rpmbuild/BUILD/nuvolaruntime-4.4.0/wscript", line 77, in add_version_info
    bare_version, n_commits, revision_id = get_git_version()
ValueError: not enough values to unpack (expected 3, got 1)

same behaviour as in diorite

ok, was solved  https://github.com/tiliado/nuvolaruntime/commit/3af85f7d473f6a33ddab2fc7b3d6e689e0c21947

repo: tiliado/nuvolaruntime


text:
Needs NMake/MSVS Support

A project file from different versions
NMake files that MSVS supports

Problems:

Its not built for MSVS libs
Its not built for directory-less include files (package your libs with the source code)
Includes things not found in MSVS (dirent for one)
Might not have a few other symbols found relating to ^
No definition for MSVS under _WIN32 || _WIN64 ifdefs
luaadditions not built correctly or even a little bit

repo: tilkinsc/LuaConsole


text:
Extend OAuth2 access token expiration in console and via tf (once available)

Cognito App Cient now supports configuration of access and refresh token duration, see https://stackoverflow.com/a/63533330/4292075
Apparently it's not yet fully supported by tf, but there's a PR:
https://github.com/hashicorp/terraform-provider-aws/issues/14919

added to https://github.com/tillkuhn/angkor/blob/master/infra/modules/cognito/main.tf
  # Time limit, between 5 minutes and 1 day, after which the access token is no longer valid and cannot be used.
  access_token_validity = 24
  # Time limit, between 5 minutes and 1 day, after which the ID token is no longer valid and cannot be used.
  id_token_validity = 24
  # Time limit in days refresh tokens are valid for. Must be between 60 minutes and 3650 days
  refresh_token_validity = 7
  # Released with 3.32.0 of the TF AWS Provider https://github.com/hashicorp/terraform-provider-aws/issues/14919
  token_validity_units {
    access_token = "hours"
    id_token = "hours"
    refresh_token = "days"
  }

repo: tillkuhn/angkor


text:
WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug

I get this message: WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug in the Logs.
So I report this as a bug.
regards
newmy
2023-09-05T13:27:51+0000:INFO:vwsfriend_base:vwsfriend 0.23.11 (using WeConnect-python 0.56.2, WeConnect-mqtt 0.44.2)
2023-09-05T13:27:51+0000:INFO:session_manager:Could not use token from file /tmp/weconnect.token ([Errno 2] No such file or directory: '/tmp/weconnect.token')
2023-09-05T13:27:52+0000:INFO:agent_connector:It looks like you have an existing database will check if an upgrade is necessary
2023-09-05T13:27:52+0000:INFO:migration:Context impl PostgresqlImpl.
2023-09-05T13:27:52+0000:INFO:migration:Will assume transactional DDL.
2023-09-05T13:27:52+0000:INFO:agent_connector:Database upgrade done
2023-09-05T13:27:52+0000:INFO:vwsfriend_base:Starting up Homekit
2023-09-05T13:27:52+0000:INFO:bridge:Reading homekit accessory config file /config/accessory.config
2023-09-05T13:27:52+0000:INFO:accessory_driver:Loading Accessory state from `/config/accessory.state`
2023-09-05T13:27:52+0000:INFO:accessory_driver:Starting the event loop
2023-09-05T13:27:52+0000:INFO:accessory_driver:Starting accessory VWsFriend on addresses ['192.168.178.108'], port 51234.
2023-09-05T13:27:52+0000:INFO:vwsfriend_ui:VWsFriend is listening on 0.0.0.0:4000)
2023-09-05T13:27:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:27:53+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:27:55+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:27:59+0000:INFO:agent_connector:Found matching vehicle for vin WVGZZZE2ZPP51xxxx in database
2023-09-05T13:27:59+0000:INFO:trip_agent:Vehicle WVGZZZE2ZPP51xxxx provides a parkingPosition and thus allows to record trips based on position
2023-09-05T13:27:59+0000:INFO:warning_light_agent:Vehicle WVGZZZE2ZPP51xxxx has still 0 warning lights on in the database.
2023-09-05T13:27:59+0000:INFO:abrp_agent:Reading abrp tokenfile /config/WVGZZZE2ZPP51xxxx-ABRP.token
2023-09-05T13:27:59+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693919109.0, 'soc': 24, 'est_battery_range': 114, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:27:59+0000:INFO:bridge:Writing accessory config file /config/accessory.config
2023-09-05T13:29:52+0000:INFO:hap_protocol:('192.168.178.184', 54845): Connection made to VWsFriend
2023-09-05T13:30:39+0000:INFO:hap_protocol:('192.168.178.162', 55759): Connection made to VWsFriend
2023-09-05T13:30:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:30:54+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:30:57+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:30:59+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693919109.0, 'soc': 24, 'est_battery_range': 114, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:32:23+0000:INFO:hap_protocol:('192.168.178.162', 55761): Connection made to VWsFriend
2023-09-05T13:33:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:33:53+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:33:58+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:34:05+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693919109.0, 'soc': 24, 'est_battery_range': 114, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:34:24+0000:INFO:hap_protocol:('192.168.178.162', 55764): Connection made to VWsFriend
2023-09-05T13:34:33+0000:INFO:hap_protocol:('192.168.178.162', 55765): Connection made to VWsFriend
2023-09-05T13:36:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:36:55+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:36:57+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:37:00+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693919109.0, 'soc': 24, 'est_battery_range': 114, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:37:42+0000:INFO:hap_protocol:('192.168.178.184', 54846): Connection made to VWsFriend
2023-09-05T13:37:44+0000:INFO:hap_protocol:('192.168.178.162', 55766): Connection made to VWsFriend
2023-09-05T13:39:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:39:53+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:39:55+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:40:05+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693919109.0, 'soc': 24, 'est_battery_range': 114, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:42:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:42:58+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:43:02+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:43:09+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693919109.0, 'soc': 24, 'est_battery_range': 114, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:45:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:45:56+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:45:58+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:46:01+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693919109.0, 'soc': 24, 'est_battery_range': 114, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:48:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:48:53+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:48:56+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:49:01+0000:INFO:state_agent:Vehicle WVGZZZE2ZPP51xxxx went online
2023-09-05T13:49:01+0000:INFO:abrp_agent:ABRP send telemetry {'utc': 1693921721.0, 'soc': 23, 'est_battery_range': 110, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de: Missing telemetry: speed,
2023-09-05T13:51:42+0000:INFO:hap_protocol:('192.168.178.162', 55767): Connection made to VWsFriend
2023-09-05T13:51:52+0000:INFO:vwsfriend_base:Updating data from WeConnect
2023-09-05T13:51:55+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:51:58+0000:WARNING:generic_capability:An unsupported status: 1018 was provided, please report this as a bug
2023-09-05T13:52:12+0000:ERROR:abrp_agent:ABRP send telemetry {'utc': 1693921721.0, 'soc': 23, 'est_battery_range': 110, 'lat': 49.294367, 'lon': 8.648054, 'is_parked': True, 'odometer': 13598, 'is_charging': False, 'power': -0.0} for vehicle WVGZZZE2ZPP51xxxx for account newmy@newmy.de failed with status code 525
2023-09-05T13:52:31+0000:INFO:hap_protocol:('192.168.178.162', 55768): Connection made to VWsFriend
2023-09-05T13:52:32+0000:INFO:hap_protocol:('192.168.178.184', 54848): Connection made to VWsFriend

I checked this, and it seems that the status 1018 is missing from the GenericCapability class. This status only appears when you have disabled some of the mobile online services, and comes together with status 1004 - DISABLED_BY_USER.

I have disabled the personalisation but no other mobile online service.
Any chance to get more information about that?

authors: amenychtas newmy-de

repo: tillsteinbach/VWsFriend


text:
Get parents for a taxonomy term via JSON API

Out of the box, on Drupal 8.4.x the parent relationship is always empty.
Related DO issues

Parent is always empty for taxonomy terms
Make $term->parent behave like any other entity reference field, to fix REST support and de-customize its Views integration

Related #3

A field is parent has been added to the audio itinerary vocabulary.
So the request for itineraries is now ${JSON_API_URL}/${drupalLocale}/jsonapi/taxonomy_term/audio_itinerary?**filter[field_is_parent][value]=1**&sort=weight&include=field_image,field_background_image
The itinerary route fetches all terms and passes them to the StopList component.
The filterStops() method keeps only the terms that have stops.
This approach has been preferred to applying patches that still needs review. Especially because

we are not measuring which side effects will be produced by the patches
the current use case can solved by an extra field that can be easily removed.

repo: tiltfactory/belvue-audioguide