#68 Restored verify lifecycle for ZPM

@daimor this looks good to me other than the issues on 2020.1; any idea what's up there? Might be worth adding verbose output? We also support junit test result reporting - not sure what the best way to pick up test results would be in GitHub Actions though.

Yeah just polishing it for GitHub actions, locally it works well now.
JUnit is cool, yes, it needs some investigation on how to deal with here.


feat(words): add finetune

See https://github.com/autowarefoundation/autoware/actions/runs/6237022660/job/16929649433?pr=3848

@shmpwk could you approve this? It's blocking https://github.com/autowarefoundation/autoware/pull/3848 Thanks :slightly_smiling_face:


PacReq:

Types
No response
URL
https://aur.archlinux.org/packages/vmware-workstation
Building guide
No response
Additional context
No response

I guess it's too complicated as now VMware since become part of Broadcom and I hate issues about the module updated for every newest kernel or newest kernel update for kernel-longterm


Add types for svelte-filepond

This PR:

upgrades svelte to ^3.31 because the SvelteComponentTyped required to do this was added in that release.
adds types for the both the default export and re-exported FilePond exports
updates rollup-plugin-svelte to v6.1.1, which fixes a broken require that was throwing when running the build

There's also a v7.x.x of rollup-plugin-svelte but it requires upgrading rollup to v2, a new major.

updates the dist/ folder of this package (this could possibly be removed as npm run build is also the prepublish action?)

Fixes #13

Thanks Nick going to check this out as soon as possible.

@rikschennink : is this PR ok for you ? 😃

@pierre-H Haven't gotten around to it yet.

I hope this could be merged soon


[5.9] [Immediate] Workaround for loading merged frameworks in immediate mode

Explanation: Some frameworks (e.g. AppKit) that previously had a separate swift overlay have been merged in the beta macOS 14 SDK. This caused missing symbol errors in swift immediate mode when targetting an older OS with a new SDK, because we do not currently support ld$previous mappings for symbols in JITLink. This commit extends an existing workaround previously used for Foundation to cover additional frameworks by automatically pulling in the overlay libswift library on older OSes.
Risk: Low. Only affects immediate mode. Only affects specific frameworks that are already missing symbols in Swift.
Testing: Manually on a macOS 13 host using a 14 beta SDK; for each framework I found a symbol that migrated and ensured it did not cause JIT errors after this change.
Issue: rdar://110371405
Reviewer: @mikeash

Some frameworks that previously had a separate swift overlay have been merged in macOS 14. This is causing symbols to not resolve if using the new SDK but running on an older OS in immediate mode. Ideally we would handle this automatically in JITLink as is done by the system linker, but in the meantime add a workaround to load the correct libraries manually.
rdar://110371405
(cherry picked from commit e7590072569f267bb4885657e84c591d69505899)

@swift-ci please test


Add French translation for the README file

Pull Request : Add French translation for the README file

[x] I read the README file
[ ]  I have checked that the code is compiling and working
[ ]  I have added appropriate comments in-between the code for better understanding of the algorithm
[ ]  I've updated the changes in TrackingProgress.md

Added README_FR.md in README Translations/
Added French in languages list
Sorted languages in alphabetical order in all README file

Thank you for adding this translation and sorting the languages into alphabetical order.


Get-OctopusDeployment doesn't return package names

Get-OctopusDeployment doesn't return the package name.  Just the version.  Example output:
"Package             : {@{Name=; Version=20160909.6}, @{Name=; Version=20160909.6}}"
At about line 131 of Get-OctopusDeployment (14ac53c) you’ll find
Name = $ds.Actions.properties.'Octopus.Action.Package.NuGetPackageId'.value
However 'Octopus.Action.Package.NuGetPackageId' doesn't seem to be what the package ID is called.  If I change the above to:
Name = $ds.Actions.properties.'Octopus.Action.Package.PackageId'.value
It then works.  To test I just created a function called Get-OctopusDeployment2 with that on amendment and it returned the packageIds.

Hi there! I just released 0.6.0 which should fix this issue. Before you download it please take a read at #234 , specially at the list of missing cmdlets


README File - "Insert Who is Assign Too Here"

I have used our Working Documentation (WordDoc within Images) to form the basis of our README file. This was a collaborative effort within Thursdays (19th Jan) day one design brief


Responsive Header Navigation

Tracking issue for responsive header navigation
Search component:

[ ] Moves to the far left of the header at smaller breakpoints
[ ] Search results fill up width of screen
[ ] Turns into icon only at smaller breakpoints

Top Nav:

[ ] Is hidden in Header component at smaller breakpoints
[ ] Displays above SideNav at smaller breakpoints
[ ] Accordian dropdown for menu items

See @broccolini 's mockup in https://github.com/primer/blueprints/pull/14#issuecomment-476848630


very few AtTimer commands generated by gen_sentences.js

The balance of timers have been tuned, I don't think we need more.


How to Use on Mac

I'm trying to run this program in order to decrypt and convert my audiobook to m4b but am running into errors.  I have an up-to-date Mac.  I have installed homebrew / ffmpeg and I ran the install programs listed on the page.  I am unfamiliar with these programs but I created the following in an attempt to convert a book from aax to m4b.
AAXtoMP3 --A [********] e:m4b Users/Rabbit/Desktop/TheKingsMenAllFortheGameSeriesBook3_ep6.aax
The *s are  my authentication code.
I tried running the program aaxtomp3 but this will stall and I need to open a new terminal window.
I receive the error "bash: AAXtoMP3: command not found"
Could you help me troubleshoot how to get this working?
Thank you!

Run bash AAXtoMP3 ... or make the script executable with chmod +x AAXtoMP3 then you can exec the script by putting ./AAXtoMP3 ...

Apologies for the questions.
This is the code I've got so far, but I'm having trouble getting the authcode to work.  I know that this is the correct code, but am unsure how to format it in the code.
/Users/Rabbit/Downloads/AAXtoMP3-master/AAXtoMP3 --authcode ******** -e:m4b -s /Users/Rabbit/Desktop/TheKingsMenAllFortheGameSeriesBook3_ep6.aax

So something like
./Users/Rabbit/Downloads/AAXToMP3 --authcode 123A456 -e:m4b -s /Users/Rabbit/Desktop/TheKingsMenAllFortheGameSeriesBook3_ep6.aax

Hmm looks like my audiblecode is wrong then.  Thank you for your help!

This code is continuing to produce an error.  I double checked that my audiblecode is correct.
/Users/Rabbit/Downloads/AAXtoMP3-master/AAXtoMP3 -e:m4b --authcode ******** /Users/Rabbit/Desktop/TheKingsMenAllFortheGameSeriesBook3_ep6.aax
ERROR Missing authcode
Usage: AAXtoMP3 [--flac] [--aac] [--opus ] [--single] [--chaptered]
[-e:mp3] [-e:m4a] [-e:m4b] [--authcode ]
[--target_dir ] [--complete_dir ] [--validate]
{FILES

Try putting the authcode in ~/.authcode and omit that from the input.


Update stable version in repo from 1.1.2 to 1.2.0

Think about update stable version to 1.2.0
Version: stable=1.1.2 (110 days old) => latest=1.2.0 (15 days old)
Installs: stable=817 (85.37%), latest=98 (10.24%), total=957
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.2.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Is there any reason to delay adding this adapter to stable any longer?
Please drop a commit if you know any reason to refrain from adding.
If there is no response until 14.9.2024 we could decide to update anyway.

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.2.0 but in the meantime an update to version 1.2.1 is suggested.
So this issue will be closed and replaced by an updated one.
@mcm1957 for evidence


ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>21588): insufficient funds: insufficient funds

Hi Zama !
I have a question about deploying erc20 token.
I download the project then install packages after that  I enter pnpm : pnpm run fhevm:start
it says :
`mpiled 3 Solidity files successfully (evm target: cancun).
gatewayContractAddress written to gateway/.env.gateway successfully!
node_modules/fhevm/gateway/lib/PredeployAddress.sol file has been generated successfully.
Nothing to compile
No need to generate any newer typings.
ACL address 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0 written successfully!
node_modules/fhevm/lib/ACLAddress.sol file generated successfully!
TFHE Executor address 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8 written successfully!
node_modules/fhevm/lib/FHEVMCoprocessorAddress.sol file generated successfully!
KMS Verifier address 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD written successfully!
node_modules/fhevm/lib/KMSVerifierAddress.sol file generated successfully!
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>11464): insufficient funds: insufficient funds

Please replace TFHEExecutor for one of these options wherever you are trying to read its artifact:

fhevm/lib/TFHEExecutor.sol:TFHEExecutor
fhevmTemp/fhevm/lib/TFHEExecutor.sol:TFHEExecutor

For more info go to https://hardhat.org/HH701 or run Hardhat with --show-stack-traces
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>21588): insufficient funds: insufficient funds
.....
privateKey 717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6
ownerAddress 0x305F1F471e9baCFF2b3549F9601f9A4BEafc94e1
GatewayContract was deployed at address:  0xc8c9303Cd7F337fab769686B593B87DC3403E0ce
Account 0x97F272ccfef4026A1F3f0e0E879d514627B84E69 was succesfully added as an gateway relayer`

the launch-fhevm.sh

# npx hardhat clean
mkdir -p fhevmTemp
cp -L -r node_modules/fhevm fhevmTemp/
npx hardhat compile:specific --contract fhevmTemp/fhevm/lib
npx hardhat compile:specific --contract fhevmTemp/fhevm/gateway
mkdir -p abi
cp artifacts/fhevmTemp/fhevm/lib/TFHEExecutor.sol/TFHEExecutor.json abi/TFHEExecutor.json

PRIVATE_KEY_GATEWAY_DEPLOYER=$(grep PRIVATE_KEY_GATEWAY_DEPLOYER .env | cut -d '"' -f 2)
npx hardhat task:computePredeployAddress --private-key "$PRIVATE_KEY_GATEWAY_DEPLOYER"

npx hardhat compile:specific --contract contracts

npx hardhat task:computeACLAddress
npx hardhat task:computeTFHEExecutorAddress
npx hardhat task:computeKMSVerifierAddress
npx hardhat task:deployACL
npx hardhat task:deployTFHEExecutor
npx hardhat task:deployKMSVerifier

rm -rf fhevmTemp

npx hardhat task:launchFhevm --skip-get-coin true

Did you first setup your .env file? Or at least did you do cp .env.example .env?
Another recommended solution first, before launching a local fhevm node, is to try the mocked mode as well : npm run test:mock.

Hi Jat Thanks for the response
my .env
export INFURA_API_KEY="key"
export MNEMONIC="dog huge boring street rookie possible cycle funny occur file present special anxiety law merge"
export PRIVATE_KEY_GATEWAY_DEPLOYER="717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6"
export PRIVATE_KEY_GATEWAY_OWNER="717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6"
export PRIVATE_KEY_GATEWAY_RELAYER="7ec931411ad75a7c201469a385d6f18a325d4923f9f213bd882bbea87e160b67"

# Block explorer API keys
# export ARBISCAN_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
# export BSCSCAN_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
export ETHERSCAN_API_KEY="UMF1FZKK8NIF6MY889IDWMSXBAUED7Z9PD"
# export OPTIMISM_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
# export POLYGONSCAN_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
# export SNOWTRACE_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"

the pnpm test:mock returns
furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm test:mock

><EMAIL_ADDRESS>test:mock /Users/furkandemirel/test/zama/fhevm-hardhat-template
> hardhat test --network hardhat

Nothing to compile
No need to generate any newer typings.
Nothing to compile
No need to generate any newer typings.
Nothing to compile
No need to generate any newer typings.
Code of Mocked Pre-compile set at address: 0x000000000000000000000000000000000000005d
gatewayContractAddress written to gateway/.env.gateway successfully!
node_modules/fhevm/gateway/lib/PredeployAddress.sol file has been generated successfully.
ACL address 0x2Fb4341027eb1d2aD8B5D9708187df8633cAFA92 written successfully!
node_modules/fhevm/lib/ACLAddress.sol file generated successfully!
TFHE Executor address 0x05fD9B5EFE0a996095f42Ed7e77c390810CF660c written successfully!
node_modules/fhevm/lib/FHEVMCoprocessorAddress.sol file generated successfully!
KMS Verifier address 0x12B064FB845C1cc05e9493856a1D637a73e944bE written successfully!
node_modules/fhevm/lib/KMSVerifierAddress.sol file generated successfully!
ACL was deployed at address: 0x2Fb4341027eb1d2aD8B5D9708187df8633cAFA92
Error HH701: There are multiple artifacts for contract "TFHEExecutor", please use a fully qualified name.

Please replace TFHEExecutor for one of these options wherever you are trying to read its artifact:

fhevm/lib/TFHEExecutor.sol:TFHEExecutor
fhevmTemp/lib/TFHEExecutor.sol:TFHEExecutor

For more info go to https://hardhat.org/HH701 or run Hardhat with --show-stack-traces
 ELIFECYCLE  Command failed with exit code 1.
 ```

 I probably miss something but I don't know where. I am looking forward to your responses !
 Thanks

What OS are you using? If you use Windows, you should use the WSL. Otherwise, are you sure you are using the last main branch? Please retry by pulling last current main branch in a new clean directory.

Hi Jat,
I probably miss something that's why I would like to share with you my logs.
I use Mac m3 os 14.6
my node version is

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % node -v
v20.15.0

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % npm -v
10.7.0

Create a new directory
clone repo

 git clone https://github.com/zama-ai/fhevm-hardhat-template.git

then check branch

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % git pull origin main
From https://github.com/zama-ai/fhevm-hardhat-template
 * branch            main       -> FETCH_HEAD
Already up to date.

Update env

export INFURA_API_KEY="key"
export MNEMONIC="dog huge boring street rookie possible cycle funny occur file present special anxiety law merge"
export PRIVATE_KEY_GATEWAY_DEPLOYER="717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6"
export PRIVATE_KEY_GATEWAY_OWNER="717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6"
export PRIVATE_KEY_GATEWAY_RELAYER="7ec931411ad75a7c201469a385d6f18a325d4923f9f213bd882bbea87e160b67"

# Block explorer API keys
# export ARBISCAN_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
# export BSCSCAN_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
export ETHERSCAN_API_KEY="key"
# export OPTIMISM_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
# export POLYGONSCAN_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"
# export SNOWTRACE_API_KEY="zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz"

then pnpm install

+ ts-generator 0.1.1
+ ts-node 10.9.2
+ typechain 8.3.2
+ typescript 5.5.4
+ typescript-eslint 8.0.1

><EMAIL_ADDRESS>preinstall /Users/furkandemirel/test/new_zama/fhevm-hardhat-template
> node tasks/checkNodeVersion.js

><EMAIL_ADDRESS>postinstall /Users/furkandemirel/test/new_zama/fhevm-hardhat-template
> DOTENV_CONFIG_PATH=./.env.example pnpm typechain

><EMAIL_ADDRESS>typechain /Users/furkandemirel/test/new_zama/fhevm-hardhat-template
> cross-env TS_NODE_TRANSPILE_ONLY=true hardhat typechain

Compiled 23 Solidity files successfully (evm target: cancun).

Done in 7.7s

after that

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm fhevm:start

><EMAIL_ADDRESS>fhevm:start /Users/furkandemirel/test/new_zama/fhevm-hardhat-template
> make run-full && ./scripts/fund_test_addresses_docker.sh && ./launch-fhevm.sh

/Library/Developer/CommandLineTools/usr/bin/make generate-fhe-keys
ghcr.io/zama-ai/kms-service-dev:v0.7.1
v0.7.1: Pulling from zama-ai/kms-service-dev
Digest: sha256:63ef4519b44e03e78a3071fa920536ab938d080367de4059871068cce3ab2ac8
Status: Image is up to date for ghcr.io/zama-ai/kms-service-dev:v0.7.1
ghcr.io/zama-ai/kms-service-dev:v0.7.1

What's next:
    View a summary of image vulnerabilities and recommendations → docker scout quickview ghcr.io/zama-ai/kms-service-dev:v0.7.1
611486092ee675b538bfa7cbb747cb65a31ed85f014a14faed1134cb1e2e17d9
Successfully copied 253MB to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res
temp-container
/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res/keys
###########################################################
Keys creation is done, they are stored in /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res/keys
###########################################################
/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/network-fhe-keys
/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/kms-fhe-keys
###########################################################
All the required keys exist in /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res/keys
###########################################################
Copying PUB/ServerKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/network-fhe-keys, please wait ...
Copying PUB/PublicKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/network-fhe-keys, please wait ...
Copying PRIV/FhePrivateKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/kms-fhe-keys, please wait ...
[+] Running 7/7
 ✔ Network zama-dev_default              Created                                                                                0.0s
 ✔ Container zama-dev-fhevm-validator-1  Healthy                                                                                20.8s
 ✔ Container zama-dev-kms-validator-1    Healthy                                                                                5.8s
 ✔ Container zama-dev-gateway-store-1    Started                                                                                0.3s
 ✔ Container zama-dev-kms-core-1         Healthy                                                                                5.8s
 ✔ Container zama-dev-connector-1        Started                                                                                5.9s
 ✔ Container zama-dev-gateway-1          Started                                                                                20.9s
sleep a little to let the docker start up
sleep 5
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"BA3E57E4FC0EB4DF4A0CD11778FC1BE154CA8CFDABD993C4B038AF806FD97546","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"4622EE7FDE9ACD4F1F8C91F7DA4E662A4341429C04139259AAA45159D223DC90","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"D5E8BD5AEF9A9964B3DCC0A3151C55EAEA69893790C0F5DB5B90F8C6F2498F79","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"96593C58779A46BD7F5818C68D61390C6A0E5863C8C684860AE60DE51DA98B08","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"E080C49DD8DCC3DDAA1D6E1A263222C8BD7D16BD6C8E791162CD8947C7CB72BD","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"581FDDADC2E06A6ABFB94A5F25F824A300243B6A1D3454EFFCD8A386CB55D71A","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"8DB2E58520A6A951D04CD4BCC8C2FD31F3116F8D90FB03FDF94EA5A49F403F2A","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
Generating typings for: 22 artifacts in dir: types for target: ethers-v6
Successfully generated 56 typings!
Compiled 22 Solidity files successfully (evm target: cancun).
Generating typings for: 3 artifacts in dir: types for target: ethers-v6
Successfully generated 30 typings!
Compiled 3 Solidity files successfully (evm target: cancun).
gatewayContractAddress written to gateway/.env.gateway successfully!
node_modules/fhevm/gateway/lib/PredeployAddress.sol file has been generated successfully.
Generating typings for: 12 artifacts in dir: types for target: ethers-v6
Successfully generated 52 typings!
Compiled 11 Solidity files successfully (evm target: cancun).
ACL address 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0 written successfully!
node_modules/fhevm/lib/ACLAddress.sol file generated successfully!
TFHE Executor address 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8 written successfully!
node_modules/fhevm/lib/FHEVMCoprocessorAddress.sol file generated successfully!
KMS Verifier address 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD written successfully!
node_modules/fhevm/lib/KMSVerifierAddress.sol file generated successfully!
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>11404): insufficient funds: insufficient funds
    at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
    at async SimpleTaskDefinition.action (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/tasks/taskDeploy.ts:31:15)
    at async Environment._runTaskDefinition (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:359:14)
    at async Environment.run (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:192:14)
    at async main (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/cli/cli.ts:323:7)
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>02876): insufficient funds: insufficient funds
    at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
    at async SimpleTaskDefinition.action (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/tasks/taskDeploy.ts:44:16)
    at async Environment._runTaskDefinition (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:359:14)
    at async Environment.run (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:192:14)
    at async main (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/cli/cli.ts:323:7)
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>19150): insufficient funds: insufficient funds
    at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
    at async SimpleTaskDefinition.action (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/tasks/taskDeploy.ts:57:16)
    at async Environment._runTaskDefinition (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:359:14)
    at async Environment.run (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:192:14)
    at async main (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/cli/cli.ts:323:7)
privateKey 717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6
ownerAddress 0x305F1F471e9baCFF2b3549F9601f9A4BEafc94e1
GatewayContract was deployed at address:  0xc8c9303Cd7F337fab769686B593B87DC3403E0ce
Account 0x97F272ccfef4026A1F3f0e0E879d514627B84E69 was succesfully added as an gateway relayer

also the pnpm: test says

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm test

><EMAIL_ADDRESS>test /Users/furkandemirel/test/new_zama/fhevm-hardhat-template
> hardhat test

bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)

  EncryptedERC20
    1) "before each" hook for "should mint the contract"

  TestAsyncDecrypt
    2) "before all" hook for "test async decrypt bool"

  0 passing (265ms)
  2 failing

  1) EncryptedERC20
       "before each" hook for "should mint the contract":
     ProviderError: failed to check sender balance: sender balance < tx cost (0 < 10627512): insufficient funds: insufficient funds
      at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
      at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
      at async deployEncryptedERC20Fixture (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/test/encryptedERC20/EncryptedERC20.fixture.ts:10:20)
      at async Context. (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/test/encryptedERC20/EncryptedERC20.ts:14:22)

  2) TestAsyncDecrypt
       "before all" hook for "test async decrypt bool":
     ProviderError: rpc error: code = Unknown desc = execution reverted
      at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async CustomProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/CustomProvider.ts:23:41)
      at async HardhatEthersProvider.estimateGas (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/internal/hardhat-ethers-provider.ts:246:27)
      at async /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:235:35
      at async Promise.all (index 0)
      at async HardhatEthersSigner._sendUncheckedTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:256:7)
      at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
      at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
      at async Context. (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/test/gatewayDecrypt/testAsyncDecrypt.ts:18:21)

This is weird, I was unable to reproduce your error. Also I don't know why in your logs I am seeing this:
[+] Running 7/7
 ✔ Network zama-dev_default              Created

which does not appear on my machine when retrying your test from a fresh cloned repo. On my Mac M3 I only see:
[+] Running 6/6
✔ Container zama-dev-kms-core-1         Healthy                                                                                0.0s
✔ Container zama-dev-kms-validator-1    Healthy                                                                                0.0s
✔ Container zama-dev-gateway-store-1    Running                                                                                0.0s
✔ Container zama-dev-fhevm-validator-1  Healthy                                                                                15.6s
✔ Container zama-dev-connector-1        Running                                                                                0.0s
✔ Container zama-dev-gateway-1          Started

Furthermore, can you tell me what happens now when you try pnpm test:mock from a fresh cloned repo?

Hi Jat,
Thanks for your quick response
First of all I try increase sleep time but it did not help
the logs:

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm fhevm:stop

><EMAIL_ADDRESS>fhevm:stop /Users/furkandemirel/test/new_zama/fhevm-hardhat-template
> make clean

/Library/Developer/CommandLineTools/usr/bin/make stop-full
[+] Running 7/7
 ✔ Container zama-dev-gateway-store-1    Removed                                                                              0.4s
 ✔ Container zama-dev-gateway-1          Removed                                                                             10.2s
 ✔ Container zama-dev-connector-1        Removed                                                                             10.1s
 ✔ Container zama-dev-kms-core-1         Removed                                                                             10.1s
 ✔ Container zama-dev-kms-validator-1    Removed                                                                             10.3s
 ✔ Container zama-dev-fhevm-validator-1  Removed                                                                             10.2s
 ✔ Network zama-dev_default              Removed                                                                              0.1s
rm -rf network-fhe-keys
rm -rf kms-fhe-keys
furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm fhevm:start

><EMAIL_ADDRESS>fhevm:start /Users/furkandemirel/test/new_zama/fhevm-hardhat-template
> make run-full && ./scripts/fund_test_addresses_docker.sh && ./launch-fhevm.sh

/Library/Developer/CommandLineTools/usr/bin/make generate-fhe-keys
ghcr.io/zama-ai/kms-service-dev:v0.7.1
v0.7.1: Pulling from zama-ai/kms-service-dev
Digest: sha256:63ef4519b44e03e78a3071fa920536ab938d080367de4059871068cce3ab2ac8
Status: Image is up to date for ghcr.io/zama-ai/kms-service-dev:v0.7.1
ghcr.io/zama-ai/kms-service-dev:v0.7.1

What's next:
    View a summary of image vulnerabilities and recommendations → docker scout quickview ghcr.io/zama-ai/kms-service-dev:v0.7.1
aa2db390ebf70741f214491aaa5685c7bd3ae36371e379c27e6b49527f64d436
Successfully copied 253MB to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res
temp-container
/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res/keys
###########################################################
Keys creation is done, they are stored in /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res/keys
###########################################################
/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/network-fhe-keys
/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/kms-fhe-keys
###########################################################
All the required keys exist in /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/res/keys
###########################################################
Copying PUB/ServerKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/network-fhe-keys, please wait ...
Copying PUB/PublicKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/network-fhe-keys, please wait ...
Copying PRIV/FhePrivateKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/test/new_zama/fhevm-hardhat-template/kms-fhe-keys, please wait ...
[+] Running 7/7
 ✔ Network zama-dev_default              Created                                                                              0.0s
 ✔ Container zama-dev-fhevm-validator-1  Healthy                                                                             21.0s
 ✔ Container zama-dev-kms-validator-1    Healthy                                                                              6.0s
 ✔ Container zama-dev-kms-core-1         Healthy                                                                              6.0s
 ✔ Container zama-dev-gateway-store-1    Started                                                                              0.5s
 ✔ Container zama-dev-connector-1        Started                                                                              5.8s
 ✔ Container zama-dev-gateway-1          Started                                                                             20.8s
sleep a little to let the docker start up
sleep 5
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"6BDBD3EF60B0313DB08AC9F9F492E69135BBAA914F7F654AE23762A5CD1D212E","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"F7D034BCFA5FB3B4AEEF1CCDBBF2696E952A1953A69113C81C6488ACB890A203","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"1A5A9A04552082C9BE647018933CE483ACCFB78FAB44AF455BC9645CA5C09761","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"36C3F94DE17AA00A59304D8A5BB08B6022261BFB0F5C8E169714702B627E758A","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"0B288868DD5B21E6522DE1F9A59B8D0A55741AEC7CFB8E1195F904EF69784B1B","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"8CCDE512B054FEB03B08FFE67D376EE029AD18B9C8BB65AA2ABE79460B2FB5C3","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"83189B10838DA41C89261E0A6B447F0BDC1041AF02759A3B8305D196E0D0D6A8","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
Generating typings for: 22 artifacts in dir: types for target: ethers-v6
Successfully generated 56 typings!
Compiled 22 Solidity files successfully (evm target: cancun).
Generating typings for: 3 artifacts in dir: types for target: ethers-v6
Successfully generated 30 typings!
Compiled 4 Solidity files successfully (evm target: cancun).
gatewayContractAddress written to gateway/.env.gateway successfully!
node_modules/fhevm/gateway/lib/PredeployAddress.sol file has been generated successfully.
Generating typings for: 12 artifacts in dir: types for target: ethers-v6
Successfully generated 52 typings!
Compiled 11 Solidity files successfully (evm target: cancun).
ACL address 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0 written successfully!
node_modules/fhevm/lib/ACLAddress.sol file generated successfully!
TFHE Executor address 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8 written successfully!
node_modules/fhevm/lib/FHEVMCoprocessorAddress.sol file generated successfully!
KMS Verifier address 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD written successfully!
node_modules/fhevm/lib/KMSVerifierAddress.sol file generated successfully!
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>2031): insufficient funds: insufficient funds
    at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
    at async SimpleTaskDefinition.action (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/tasks/taskDeploy.ts:31:15)
    at async Environment._runTaskDefinition (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:359:14)
    at async Environment.run (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:192:14)
    at async main (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/cli/cli.ts:323:7)
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>7578): insufficient funds: insufficient funds
    at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
    at async SimpleTaskDefinition.action (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/tasks/taskDeploy.ts:44:16)
    at async Environment._runTaskDefinition (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:359:14)
    at async Environment.run (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:192:14)
    at async main (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/cli/cli.ts:323:7)
An unexpected error occurred:

ProviderError: failed to check sender balance: sender balance < tx cost (0 <<PHONE_NUMBER>4325): insufficient funds: insufficient funds
    at HttpProvider.request (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/providers/http.ts:96:21)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async HardhatEthersSigner.sendTransaction (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async ContractFactory.deploy (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
    at async SimpleTaskDefinition.action (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/tasks/taskDeploy.ts:57:16)
    at async Environment._runTaskDefinition (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:359:14)
    at async Environment.run (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/core/runtime-environment.ts:192:14)
    at async main (/Users/furkandemirel/test/new_zama/fhevm-hardhat-template/node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/cli/cli.ts:323:7)
privateKey 717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6
ownerAddress 0x305F1F471e9baCFF2b3549F9601f9A4BEafc94e1
GatewayContract was deployed at address:  0xc8c9303Cd7F337fab769686B593B87DC3403E0ce
Account 0x97F272ccfef4026A1F3f0e0E879d514627B84E69 was succesfully added as an gateway relayer

then I clone repo again but I failed all test :/
the logs

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pwd
/Users/furkandemirel/newzama/fhevm-hardhat-template
furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm install
Lockfile is up to date, resolution step is skipped
Packages: +764
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

   ╭──────────────────────────────────────────────────────────────────╮
   │                                                                  │
   │                Update available! 9.9.0 → 9.11.0.                 │
   │   Changelog: https://github.com/pnpm/pnpm/releases/tag/v9.11.0   │
   │                Run "pnpm add -g pnpm" to update.                 │
   │                                                                  │
   │         Follow @pnpmjs for updates: https://x.com/pnpmjs         │
   │                                                                  │
   ╰──────────────────────────────────────────────────────────────────╯

Progress: resolved 764, reused 764, downloaded 0, added 764, done

dependencies:
+ extra-bigint 1.1.18
+ sqlite3 5.1.7

devDependencies:
+ @eslint/js 9.9.0
+ @nomicfoundation/hardhat-chai-matchers 2.0.7
+ @nomicfoundation/hardhat-ethers 3.0.6
+ @nomicfoundation/hardhat-network-helpers 1.0.11
+ @nomicfoundation/hardhat-toolbox 3.0.0
+ @nomicfoundation/hardhat-verify 1.1.1
+ @openzeppelin/contracts 5.0.2
+ @trivago/prettier-plugin-sort-imports 4.3.0
+ @typechain/ethers-v6 0.4.3
+ @typechain/hardhat 8.0.3
+ @types/chai 4.3.17
+ @types/eslint__js 8.42.3
+ @types/fs-extra 9.0.13
+ @types/mocha 10.0.7
+ @types/node 18.19.44
+ @typescript-eslint/eslint-plugin 8.0.1
+ @typescript-eslint/parser 8.0.1
+ chai 4.5.0
+ cross-env 7.0.3
+ dotenv 16.4.5
+ eslint 9.9.0
+ eslint-config-prettier 8.10.0
+ ethers 6.13.2
+ fhevm 0.5.8
+ fhevmjs 0.5.2
+ fs-extra 10.1.0
+ globals 15.9.0
+ hardhat 2.22.8
+ hardhat-deploy 0.12.4
+ hardhat-gas-reporter 1.0.10
+ hardhat-ignore-warnings 0.2.11
+ hardhat-preprocessor 0.1.5
+ lodash 4.17.21
+ mocha 10.7.3
+ prettier 2.8.8
+ prettier-plugin-solidity 1.3.1
+ rimraf 4.4.1
+ solhint 3.6.2
+ solhint-plugin-prettier 0.0.5
+ solidity-coverage 0.8.12
+ ts-generator 0.1.1
+ ts-node 10.9.2
+ typechain 8.3.2
+ typescript 5.5.4
+ typescript-eslint 8.0.1

><EMAIL_ADDRESS>preinstall /Users/furkandemirel/newzama/fhevm-hardhat-template
> node tasks/checkNodeVersion.js

><EMAIL_ADDRESS>postinstall /Users/furkandemirel/newzama/fhevm-hardhat-template
> DOTENV_CONFIG_PATH=./.env.example pnpm typechain

><EMAIL_ADDRESS>typechain /Users/furkandemirel/newzama/fhevm-hardhat-template
> cross-env TS_NODE_TRANSPILE_ONLY=true hardhat typechain

Compiled 23 Solidity files successfully (evm target: cancun).

Done in 7.3s
furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm test:mock

><EMAIL_ADDRESS>test:mock /Users/furkandemirel/newzama/fhevm-hardhat-template
> hardhat test --network hardhat

Nothing to compile
No need to generate any newer typings.
Generating typings for: 10 artifacts in dir: types for target: ethers-v6
Successfully generated 48 typings!
Compiled 10 Solidity files successfully (evm target: cancun).
Generating typings for: 3 artifacts in dir: types for target: ethers-v6
Successfully generated 38 typings!
Compiled 3 Solidity files successfully (evm target: cancun).
Code of Mocked Pre-compile set at address: 0x000000000000000000000000000000000000005d
gatewayContractAddress written to gateway/.env.gateway successfully!
node_modules/fhevm/gateway/lib/PredeployAddress.sol file has been generated successfully.
ACL address 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0 written successfully!
node_modules/fhevm/lib/ACLAddress.sol file generated successfully!
TFHE Executor address 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8 written successfully!
node_modules/fhevm/lib/FHEVMCoprocessorAddress.sol file generated successfully!
KMS Verifier address 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD written successfully!
node_modules/fhevm/lib/KMSVerifierAddress.sol file generated successfully!
ACL was deployed at address: 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0
TFHEExecutor was deployed at address: 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8
KMSVerifier was deployed at address: 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD
privateKey 717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6
ownerAddress 0x305F1F471e9baCFF2b3549F9601f9A4BEafc94e1
GatewayContract was deployed at address:  0xc8c9303Cd7F337fab769686B593B87DC3403E0ce
Account 0x97F272ccfef4026A1F3f0e0E879d514627B84E69 was succesfully added as an gateway relayer
bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)

  EncryptedERC20
    1) should mint the contract
    2) should transfer tokens between two users
    3) should not transfer tokens between two users
    4) should be able to transferFrom only if allowance is sufficient

  TestAsyncDecrypt
    5) "before all" hook for "test async decrypt bool"

  0 passing (43ms)
  5 failing

  1) EncryptedERC20
       should mint the contract:
     Error: Transaction reverted: function returned an unexpected amount of data
    at EncryptedERC20.trivialEncrypt (fhevm/lib/Impl.sol:258)
    at EncryptedERC20.asEuint64 (fhevm/lib/TFHE.sol:5521)
    at EncryptedERC20.add (fhevm/lib/TFHE.sol:4695)
    at EncryptedERC20.mint (contracts/EncryptedERC20.sol:46)
    at EdrProviderWrapper.request (node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/hardhat-network/provider/provider.ts:433:41)
    at async HardhatEthersSigner.sendTransaction (node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async send (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:313:20)
    at async Proxy.mint (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:352:16)
    at async Context. (test/encryptedERC20/EncryptedERC20.ts:21:25)

  2) EncryptedERC20
       should transfer tokens between two users:
     Error: Transaction reverted: function returned an unexpected amount of data
    at EncryptedERC20.trivialEncrypt (fhevm/lib/Impl.sol:258)
    at EncryptedERC20.asEuint64 (fhevm/lib/TFHE.sol:5521)
    at EncryptedERC20.add (fhevm/lib/TFHE.sol:4695)
    at EncryptedERC20.mint (contracts/EncryptedERC20.sol:46)
    at EdrProviderWrapper.request (node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/hardhat-network/provider/provider.ts:433:41)
    at async HardhatEthersSigner.sendTransaction (node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async send (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:313:20)
    at async Proxy.mint (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:352:16)
    at async Context. (test/encryptedERC20/EncryptedERC20.ts:48:25)

  3) EncryptedERC20
       should not transfer tokens between two users:
     Error: Transaction reverted: function returned an unexpected amount of data
    at EncryptedERC20.trivialEncrypt (fhevm/lib/Impl.sol:258)
    at EncryptedERC20.asEuint64 (fhevm/lib/TFHE.sol:5521)
    at EncryptedERC20.add (fhevm/lib/TFHE.sol:4695)
    at EncryptedERC20.mint (contracts/EncryptedERC20.sol:46)
    at EdrProviderWrapper.request (node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/hardhat-network/provider/provider.ts:433:41)
    at async HardhatEthersSigner.sendTransaction (node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async send (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:313:20)
    at async Proxy.mint (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:352:16)
    at async Context. (test/encryptedERC20/EncryptedERC20.ts:106:25)

  4) EncryptedERC20
       should be able to transferFrom only if allowance is sufficient:
     Error: Transaction reverted: function returned an unexpected amount of data
    at EncryptedERC20.trivialEncrypt (fhevm/lib/Impl.sol:258)
    at EncryptedERC20.asEuint64 (fhevm/lib/TFHE.sol:5521)
    at EncryptedERC20.add (fhevm/lib/TFHE.sol:4695)
    at EncryptedERC20.mint (contracts/EncryptedERC20.sol:46)
    at EdrProviderWrapper.request (node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/hardhat-network/provider/provider.ts:433:41)
    at async HardhatEthersSigner.sendTransaction (node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async send (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:313:20)
    at async Proxy.mint (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/contract.ts:352:16)
    at async Context. (test/encryptedERC20/EncryptedERC20.ts:161:25)

  5) TestAsyncDecrypt
       "before all" hook for "test async decrypt bool":
     Error: Transaction reverted: function returned an unexpected amount of data
    at TestAsyncDecrypt.trivialEncrypt (fhevm/lib/Impl.sol:258)
    at TestAsyncDecrypt.asEbool (fhevm/lib/TFHE.sol:5308)
    at TestAsyncDecrypt.asEbool (fhevm/lib/TFHE.sol:5314)
    at TestAsyncDecrypt.constructor (contracts/TestAsyncDecrypt.sol:35)
    at EdrProviderWrapper.request (node_modules/.pnpm/hardhat@2.22.8_ts-node@10.9.2_@types+node@18.19.44_typescript@5.5.4__typescript@5.5.4/node_modules/hardhat/src/internal/hardhat-network/provider/provider.ts:433:41)
    at async HardhatEthersSigner.sendTransaction (node_modules/.pnpm/@nomicfoundation+hardhat-ethers@3.0.6_ethers@6.13.2_hardhat@2.22.8_ts-node@10.9.2_@types+node_vkquq6dcbonnprw62xwpjnn4ua/node_modules/@nomicfoundation/hardhat-ethers/src/signers.ts:125:18)
    at async ContractFactory.deploy (node_modules/.pnpm/ethers@6.13.2/node_modules/ethers/src.ts/contract/factory.ts:111:24)
    at async Context. (test/gatewayDecrypt/testAsyncDecrypt.ts:18:21)

╭───────────────────────────────────────────────────────╮
│                                                       │
│   New Hardhat release available! 2.22.8 -> 2.22.12.   │
│                                                       │
│   Changelog: https://hardhat.org/release/2.22.12      │
│                                                       │
│   Run "pnpm install hardhat@latest" to update.        │
│                                                       │
╰───────────────────────────────────────────────────────╯
 ELIFECYCLE  Command failed with exit code 5.

I managed to run successfully all tests, both in regular local node fhevm mode, as well as in mocked mode, on a clean instance of a Ubuntu VM, as well as on my Mac OS M3. And I am still unable to reproduce any of the issues you mentionned.
Btw something looks strange with your Node.js version, I see in your logs this message when you run pnpm test:mock : bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?). Did you try what is suggested in the logs, i.e npm run build?

Hi @furkandemireleng I noticed your error was due to the fact that you changed the default mnemonic phrase inside your .env file.
I just pushed a fix on this repo, now you can use and test in mocked mode even when using a custom mnemonic phrase or custom private keys. Notice however that for some reason, I only partially solved the issue when NOT using mocked mode, ie only initial deployment is fixed, but I am still getting Gateway error when testing in this case. I spent a bit too much time trying to solve this, but I think this is a limitation of current KMS docker image, which will be solved in next release.
So currently you have two choices:
1/ Either you reuse default values inside if .env file , meaning you do cp .env.example .env: in this case you could use either the real local fhevm node and tests : ie pnpm fhevm:start then pnpm test, or either use succesfully mocked mode for testing : pnpm test:mock (this is recommended anyways for devX)
2/ If you really want to use a custom .env with your own mnemonic phrase/private keys, then this only work in mocked mode : pnpm test:mock.
Don't forget to pull latest main branch which I have just updated if you want to use a custom .env file.

Hello @furkandemireleng I have good news: I just pushed another fix which will let now use even the real fhevm node (non-mocked mode) with any custom .env file you want. So you can now pull latest changes from main branch and do pnpm i, then use your own mnemonic and private keys inside the .env file , and then run the real tests with pnpm fhevm:start then pnpm test.
Of course, mocked mode is also still supported as well with any value you put in .env, via pnpm test:mocked.
If you confirm this solves all your issues I would like to close this issue asap. Thanks.

Hi @jatZama  !
Yes ! It solves. When I pull them make start

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm fhevm:start

><EMAIL_ADDRESS>fhevm:start /Users/furkandemirel/newzama/fhevm-hardhat-template
> ./scripts/precomputeAddresses.sh && ./scripts/rewrite-docker-compose.sh && make run-full && ./scripts/fund_test_addresses_docker.sh && ./launch-fhevm.sh

ACL address 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0 written successfully!
node_modules/fhevm/lib/ACLAddress.sol file generated successfully!
TFHE Executor address 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8 written successfully!
node_modules/fhevm/lib/FHEVMCoprocessorAddress.sol file generated successfully!
KMS Verifier address 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD written successfully!
node_modules/fhevm/lib/KMSVerifierAddress.sol file generated successfully!
gatewayContractAddress written to gateway/.env.gateway successfully!
node_modules/fhevm/gateway/lib/PredeployAddress.sol file has been generated successfully.
Successfully created .env.docker with the aggregated environment variables.
Processed docker-compose/docker-compose-full.yml.template and wrote result to docker-compose/docker-compose-full.yml
/Library/Developer/CommandLineTools/usr/bin/make generate-fhe-keys
ghcr.io/zama-ai/kms-service-dev:v0.7.1
v0.7.1: Pulling from zama-ai/kms-service-dev
Digest: sha256:63ef4519b44e03e78a3071fa920536ab938d080367de4059871068cce3ab2ac8
Status: Image is up to date for ghcr.io/zama-ai/kms-service-dev:v0.7.1
ghcr.io/zama-ai/kms-service-dev:v0.7.1

What's next:
    View a summary of image vulnerabilities and recommendations → docker scout quickview ghcr.io/zama-ai/kms-service-dev:v0.7.1
9582e182637b181e7f63a65fec307c384605c2dcd87018147000b4e85689b21e
Successfully copied 253MB to /Users/furkandemirel/newzama/fhevm-hardhat-template/res
temp-container
/Users/furkandemirel/newzama/fhevm-hardhat-template/res/keys
###########################################################
Keys creation is done, they are stored in /Users/furkandemirel/newzama/fhevm-hardhat-template/res/keys
###########################################################
/Users/furkandemirel/newzama/fhevm-hardhat-template/network-fhe-keys
/Users/furkandemirel/newzama/fhevm-hardhat-template/kms-fhe-keys
###########################################################
All the required keys exist in /Users/furkandemirel/newzama/fhevm-hardhat-template/res/keys
###########################################################
Copying PUB/ServerKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/newzama/fhevm-hardhat-template/network-fhe-keys, please wait ...
Copying PUB/PublicKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/newzama/fhevm-hardhat-template/network-fhe-keys, please wait ...
Copying PRIV/FhePrivateKey/408d8cbaa51dece7f782fe04ba0b1c1d017b1088 to /Users/furkandemirel/newzama/fhevm-hardhat-template/kms-fhe-keys, please wait ...
[+] Running 6/6
 ✔ Container zama-dev-kms-validator-1    Healthy                                                                                21.0s
 ✔ Container zama-dev-kms-core-1         Healthy                                                                                21.0s
 ✔ Container zama-dev-gateway-store-1    Running                                                                                0.0s
 ✔ Container zama-dev-connector-1        Running                                                                                0.0s
 ✔ Container zama-dev-fhevm-validator-1  Healthy                                                                                41.1s
 ✔ Container zama-dev-gateway-1          Started                                                                                31.0s
sleep a little to let the docker start up
sleep 5
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"265DE76C27243D9A03C18B3A4C0F730BB469BAD52D7B024C54E30997D21E3C1F","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"BBF1D698918DB4C2A7F73FFF9E997920ACFC18F046734441A645B7969FFD10DE","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"8634E6EF771FBE8B21E2935F89ED9F0B845B00F1A43B86C1E416D9ACEFF14128","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"60AE30BEB209D4E4CED467F785ED5090077938391DF0D2B2714FFA21BF0277D3","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"547F91789F068EE212D7E7A27AC2E364693531CC91132FB6C17B82B51573EE9E","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"86B848FF420EE564BC5FDA36A77413C5252FD825CDBB1E55F79C78D8CBB81FDC","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"A38A2E2780B48582C107A62E423C20FD77467C67A4D13114CBB8EB602A956026","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"0789E442BA21F7D508DEFDB2351885C6335CED3582C3C5A257DCFC4616D2920E","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
INFO: global keys loaded from: /root/.ethermintd/zama/keys/network-fhe-keys
INFO: global keys are initialized automatically using FHEVM_GO_KEYS_DIR env variable
{"height":"0","txhash":"2C91BEE94DBC3B4A08551CE7BF23CAAA477B44C3A3C610AB28A8DA51F95FE21D","codespace":"","code":0,"data":"","raw_log":"[]","logs":[],"info":"","gas_wanted":"0","gas_used":"0","tx":null,"timestamp":"","events":[]}
Generating typings for: 24 artifacts in dir: types for target: ethers-v6
Successfully generated 58 typings!
Compiled 25 Solidity files successfully (evm target: cancun).
Generating typings for: 10 artifacts in dir: types for target: ethers-v6
Successfully generated 50 typings!
Compiled 10 Solidity files successfully (evm target: cancun).
Generating typings for: 3 artifacts in dir: types for target: ethers-v6
Successfully generated 40 typings!
Compiled 4 Solidity files successfully (evm target: cancun).
ACL was deployed at address: 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0
TFHEExecutor was deployed at address: 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8
KMSVerifier was deployed at address: 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD
privateKey 717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6
ownerAddress 0x305F1F471e9baCFF2b3549F9601f9A4BEafc94e1
GatewayContract was deployed at address:  0xc8c9303Cd7F337fab769686B593B87DC3403E0ce
Account 0x97F272ccfef4026A1F3f0e0E879d514627B84E69 was succesfully added as an gateway relayer

then I made a mock

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm test:mock

><EMAIL_ADDRESS>test:mock /Users/furkandemirel/newzama/fhevm-hardhat-template
> hardhat test --network hardhat

gatewayContractAddress written to gateway/.env.gateway successfully!
node_modules/fhevm/gateway/lib/PredeployAddress.sol file has been generated successfully.
ACL address 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0 written successfully!
node_modules/fhevm/lib/ACLAddress.sol file generated successfully!
TFHE Executor address 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8 written successfully!
node_modules/fhevm/lib/FHEVMCoprocessorAddress.sol file generated successfully!
KMS Verifier address 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD written successfully!
node_modules/fhevm/lib/KMSVerifierAddress.sol file generated successfully!
Nothing to compile
No need to generate any newer typings.
Generating typings for: 10 artifacts in dir: types for target: ethers-v6
Successfully generated 48 typings!
Compiled 10 Solidity files successfully (evm target: cancun).
Generating typings for: 3 artifacts in dir: types for target: ethers-v6
Successfully generated 38 typings!
Compiled 4 Solidity files successfully (evm target: cancun).
Code of Mocked Pre-compile set at address: 0x000000000000000000000000000000000000005d
ACL was deployed at address: 0xf162A696Ea1441D1250DFf40f37694Ea3284Aab0
TFHEExecutor was deployed at address: 0x8632ae1E429F0BB3897d49937E0d78B999ac4Db8
KMSVerifier was deployed at address: 0x39af75d7870A3067286c4EeD89B47cf56bdE4daD
privateKey 717fd99986df414889fd8b51069d4f90a50af72e542c58ee065f5883779099c6
ownerAddress 0x305F1F471e9baCFF2b3549F9601f9A4BEafc94e1
GatewayContract was deployed at address:  0xc8c9303Cd7F337fab769686B593B87DC3403E0ce
Account 0x97F272ccfef4026A1F3f0e0E879d514627B84E69 was succesfully added as an gateway relayer
bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)

  EncryptedERC20
    ✔ should mint the contract (55ms)
    ✔ should transfer tokens between two users (181ms)
    ✔ should not transfer tokens between two users (151ms)
    ✔ should be able to transferFrom only if allowance is sufficient (490ms)

  TestAsyncDecrypt
gas paid by relayer (fulfil tx) :<PHONE_NUMBER>1000n
gas paid by user (request tx) :<PHONE_NUMBER>18042n
    ✔ test async decrypt bool (290ms)
11:59:59 PM - Fulfilled decrypt on block 25 (requestID 1)
92346846812262n
    ✔ test async decrypt uint4 (258ms)
11:59:59 PM - Fulfilled decrypt on block 28 (requestID 2)
    ✔ test async decrypt uint8 (149ms)
11:59:59 PM - Fulfilled decrypt on block 31 (requestID 3)
    ✔ test async decrypt uint16 (205ms)
11:59:59 PM - Fulfilled decrypt on block 34 (requestID 4)
    ✔ test async decrypt uint32 (163ms)
11:59:59 PM - Fulfilled decrypt on block 37 (requestID 5)
    ✔ test async decrypt uint64 (131ms)
12:00:00 AM - Fulfilled decrypt on block 40 (requestID 6)
    ✔ test async decrypt address (160ms)
12:00:00 AM - Fulfilled decrypt on block 43 (requestID 7)
    ✔ test async decrypt several addresses (153ms)
12:00:00 AM - Fulfilled decrypt on block 46 (requestID 8)
    ✔ test async decrypt mixed (308ms)
12:00:00 AM - Fulfilled decrypt on block 50 (requestID 9)
    ✔ test async decrypt uint64 non-trivial (180ms)
12:00:00 AM - Fulfilled decrypt on block 53 (requestID 10)
    ✔ test async decrypt ebytes256 non-trivial (157ms)
12:00:01 AM - Fulfilled decrypt on block 56 (requestID 11)
    ✔ test async decrypt ebytes256 non-trivial with snapshot [skip-on-coverage] (236ms)
12:00:01 AM - Fulfilled decrypt on block 59 (requestID 12)
    ✔ test async decrypt mixed with ebytes256 (173ms)

  17 passing (4s)

then I make a pnpm test it gives me an error says
Gateway didn't response correctly
logs:

furkandemirel@Furkan-MacBook-Pro fhevm-hardhat-template % pnpm test

><EMAIL_ADDRESS>test /Users/furkandemirel/newzama/fhevm-hardhat-template
> hardhat test

bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)

  EncryptedERC20
    ✔ should mint the contract (7548ms)
    ✔ should transfer tokens between two users (18156ms)
    1) should not transfer tokens between two users
    ✔ should be able to transferFrom only if allowance is sufficient (39694ms)

  TestAsyncDecrypt
11:52:39 PM - Fulfilled decrypt on block 54 (requestID 1)
gas paid by relayer (fulfil tx) :<PHONE_NUMBER>000000n
gas paid by user (request tx) :<PHONE_NUMBER>000n
    ✔ test async decrypt bool (10210ms)
11:52:54 PM - Fulfilled decrypt on block 57 (requestID 2)
7500000000000000n
    ✔ test async decrypt uint4 (10178ms)
11:53:09 PM - Fulfilled decrypt on block 60 (requestID 3)
    ✔ test async decrypt uint8 (10149ms)
11:53:24 PM - Fulfilled decrypt on block 63 (requestID 4)
    ✔ test async decrypt uint16 (10152ms)
11:53:39 PM - Fulfilled decrypt on block 66 (requestID 5)
    ✔ test async decrypt uint32 (10141ms)
11:53:54 PM - Fulfilled decrypt on block 69 (requestID 6)
    ✔ test async decrypt uint64 (9665ms)
11:54:09 PM - Fulfilled decrypt on block 72 (requestID 7)
    ✔ test async decrypt address (10203ms)
11:54:24 PM - Fulfilled decrypt on block 75 (requestID 8)
    ✔ test async decrypt several addresses (10166ms)
11:54:54 PM - Fulfilled decrypt on block 81 (requestID 9)
    ✔ test async decrypt mixed (25111ms)
11:55:09 PM - Fulfilled decrypt on block 84 (requestID 10)
    ✔ test async decrypt uint64 non-trivial (10160ms)
11:55:37 PM - Fulfilled decrypt on block 89 (requestID 11)
    ✔ test async decrypt ebytes256 non-trivial (22807ms)
    ✔ test async decrypt ebytes256 non-trivial with snapshot [skip-on-coverage]
11:56:12 PM - Fulfilled decrypt on block 95 (requestID 12)
    ✔ test async decrypt mixed with ebytes256 (24915ms)

  16 passing (5m)
  1 failing

  1) EncryptedERC20
       should not transfer tokens between two users:
     Error: Gateway didn't response correctly
      at Object.reencrypt (node_modules/.pnpm/fhevmjs@0.5.2_encoding@0.1.13/node_modules/fhevmjs/lib/node.cjs:2712:15)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Context. (test/encryptedERC20/EncryptedERC20.ts:127:26)

 ELIFECYCLE  Test failed. See above for more details.

Thanks for your effort Jat. I hope my answers or logs helped Zama :)

The last error you got is a known issue with current version of Gateway which is unstable giving flaky results. Next release (end of october) we will publish a more stable gateway service. For now, to solve this, you should either re-run your tests (several times if needed until all your tests pass without the Error: Gateway didn't response correctly), or either just run your tests always in mocked mode.
I will close this issue for now, since I could not do anything more on this topic before next release.


[main] Upgrade to latest dependencies

Markus bumping image -markusthoemmes
/cc knative-sandbox/networking-wg-leads
/assign knative-sandbox/networking-wg-leads
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/networking 1c6e5ff...8ef6314:
  > 8ef6314 Reintroduce DNS caching into the proxy image (# 592)

/hold
For the Actions.

/unhold


Item changing when relog into the game.

Is there a mod that incompatible or changing it?

Another user said that the peeper can switch to another item when reloading and vice versa. I think this is an oversight on my and Evaisas part with item IDs.
This will be resolved next update.


NaN accuracy while training

In all small tests I've run so far, train and dev accuracy start reasonable then become NaN after a while.

Just configuration issues on my own machine. Things appear to work fine on our cluster.


octave: non-existing linker path

brew doctor output
% brew doctor
Your system is ready to brew.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
% brew config
HOMEBREW_VERSION: 4.4.12
ORIGIN: https://github.com/Homebrew/brew
HEAD: 3001afe88112c13b5aafdd92e097680897060881
Last commit: 21 hours ago
Branch: stable
Core tap JSON: 16 Dec 12:42 UTC
Core cask tap JSON: 16 Dec 12:42 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 14
Homebrew Ruby: 3.3.6 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.3.6/bin/ruby
CPU: 14-core 64-bit arm_brava
Clang: 16.0.0 build 1600
Git: 2.39.5 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 15.2-arm64
CLT: <IP_ADDRESS>.1.1733547573
Xcode: 16.2
Rosetta 2: false

What were you trying to do (and why)?
Attempt to install control` package on octave failed due to non-existing linker path.
What happened (include all command output)?
octave:1> pkg install -forge -verbose control
downloading tarball(s) from:
- https://packages.octave.org/download/control-4.1.0.tar.gz
mkdir (/var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T/oct-fvBVdD)
untar (/var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T/control-4.1.0-JcHsDy.tar.gz, /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T/oct-fvBVdD)
checking for mkoctfile... /opt/homebrew/Cellar/octave/9.3.0/bin/mkoctfile-9.3.0 --verbose
checking for octave-config... /opt/homebrew/Cellar/octave/9.3.0/bin/octave-config-9.3.0
...<deleted>...
clang++ -std=gnu++17 -c  -fPIC -I/opt/homebrew/Cellar/octave/9.3.0/include/octave-9.3.0/octave/.. -I/opt/homebrew/Cellar/octave/9.3.0/include/octave-9.3.0/octave -I/opt/homebrew/Cellar/octave/9.3.0/include  -pthread -g -O2  -Wall -Wno-deprecated-declarations   common.cc -o /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T//oct-DD7Qiz.o
clang++ -std=gnu++17 -I/opt/homebrew/Cellar/octave/9.3.0/include/octave-9.3.0/octave/.. -I/opt/homebrew/Cellar/octave/9.3.0/include/octave-9.3.0/octave -I/opt/homebrew/Cellar/octave/9.3.0/include  -pthread -g -O2  -Wall -Wno-deprecated-declarations -o __control_slicot_functions__.oct  /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T//oct-pYUwFC.o /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T//oct-DD7Qiz.o  slicotlibrary.a  -bundle -undefined dynamic_lookup -bind_at_load -bundle_loader /opt/homebrew/Cellar/octave/9.3.0/bin/octave-9.3.0 -L/opt/homebrew/Cellar/octave/9.3.0/lib/octave/9.3.0 -L/opt/homebrew/Cellar/octave/9.3.0/lib -bundle -undefined dynamic_lookup -bind_at_load -bundle_loader /opt/homebrew/Cellar/octave/9.3.0/bin/octave-9.3.0  -L/opt/homebrew/opt/openblas/lib -lopenblas  -L/opt/homebrew/opt/gcc/bin/../lib/gcc/current/gcc/aarch64-apple-darwin23/14 -L/opt/homebrew/opt/gcc/bin/../lib/gcc/current/gcc -L/opt/homebrew/opt/gcc/bin/../lib/gcc/current/gcc/aarch64-apple-darwin23/14/../../.. -lemutls_w -lheapt_w -lgfortran -lquadmath   -loctinterp -loctave
ld: warning: duplicate -bundle_loader option, '/opt/homebrew/Cellar/octave/9.3.0/bin/octave-9.3.0' ignored
ld: warning: search path '/opt/homebrew/opt/gcc/bin/../lib/gcc/current/gcc/aarch64-apple-darwin23/14' not found
ld: warning: search path '/opt/homebrew/opt/gcc/bin/../lib/gcc/current/gcc/aarch64-apple-darwin23/14/../../..' not found
ld: library 'emutls_w' not found
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [__control_slicot_functions__.oct] Error 1

error: pkg: error running 'make' for the control package
error: called from
    configure_make at line 117 column 9
    install at line 202 column 7
    pkg at line 619 column 9
octave:2>

Note that:
% ls /opt/homebrew/opt/gcc/bin/../lib/gcc/current/gcc/
aarch64-apple-darwin24

What did you expect to happen?
Package should install. With self-compiled octave I see:
clang++ -std=gnu++17 -I/usr/local/include/octave-10.0.0/octave/.. -I/usr/local/include/octave-10.0.0/octave -I/usr/local/include  -pthread -ggdb3 -O2 -march=native -mcpu=native -flto=thin  -Wall -Wno-deprecated-declarations -o __control_slicot_functions__.oct  /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T//oct-wQ6p9k.o /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T//oct-zBcofN.o  slicotlibrary.a  -bundle -undefined dynamic_lookup -bind_at_load  -L/usr/local/lib -bundle -undefined dynamic_lookup -bind_at_load  -L/opt/homebrew/opt/openblas/lib -lopenblas  -L/opt/homebrew/lib -L/opt/homebrew/Cellar/gcc/14.2.0_1/bin/../lib/gcc/current/gcc/aarch64-apple-darwin24/14 -L/opt/homebrew/Cellar/gcc/14.2.0_1/bin/../lib/gcc/current/gcc -L/opt/homebrew/Cellar/gcc/14.2.0_1/bin/../lib/gcc/current/gcc/aarch64-apple-darwin24/14/../../.. -lemutls_w -lheapt_w -lgfortran -lquadmath  -L/opt/homebrew/lib -bundle_loader /usr/local/bin/octave-10.0.0
copyfile /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T/oct-rC69gC/control-4.1.0/src/__control_helper_functions__.oct /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T/oct-rC69gC/control-4.1.0/src/__control_slicot_functions__.oct /var/folders/ds/5xsh6x4914x78jswflyz20c40000gn/T/oct-rC69gC/control-4.1.0/inst/aarch64-apple-darwin24.1.0-api-v59
The control package was installed into the directory
/Users/dmitri/.local/share/octave/api-v59/packages/control-4.1.0.

Step-by-step reproduction instructions (by running brew commands)
see above

Try doing
brew reinstall gcc

and see if that helps.

I tried and it did not help.

As far as I can tell for darwin24 octave has to be compiled on darwin24 (not darwin23).

Closing in favour of https://github.com/Homebrew/homebrew-core/issues/201376


sub --dir blacklist

I see a CLI parameter --dir which might cause the tool to scan for licenses in a certain directory.
I expect the tool traverse also all subdirectories in that directories.
I would love to have an option to omit certain subdirectories and files in arbitrary depth.
Maybe exclude via a glob?
Use case examples:
scan all files in ./myProject/ but do not traverse any of the following directories: .git, node_modules, vendor, .venv, .pipenv and do not scan files like license.js
structure be like
|- myImages
\- myProject
   |- README.md
   |- .git/...   << ignore
   |- webUI
   |  |- node_modules/...  << ignore
   |  |- package.json
   |  |- index.js
   |  |- workspaces
   |  |  \- license
   |  |    |- node_modules/...  << ignore
   |  |    |- package.json
   |  |    \- license.js        << ignore
   |  \- LICENSE.mit
   |- serverA
   |  |- LICENSE
   |  \- serve
   |     \- .pipenv/...  << ignore
   \- serverB
      |- vendor/... << ignore
      |- composer.json
      |- index.php
      \- License

call could be like license-scanner --dir=./myProject --ignore-glob=node_modules --ignore-glob=vendor --ignore-glob=.git --ignore-glob='.*env' --ignore-glob=license.js

Let's consider what default ignores should be for standard things

"default ignores" are another story, out of scope of this feature request.


Support retrieving a subset of subscriptions / affiliations

Use case: To help us with things like this https://github.com/project-isizwe/wifi-chat/issues/16#issuecomment-106230623
Affiliation retrieval
Filters affiliations list to those with 'member' affiliation:
<iq type='get'
<EMAIL_ADDRESS>    to='pubsub.shakespeare.lit'
    id='ent1'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub' xmlns:bc='http://buddycloud.org/v1'>
    <affiliations node='princely_musings' bc:affiliation='member' />
  </pubsub>
</iq>

Subscription retrieval
<iq type='get'
<EMAIL_ADDRESS>    to='pubsub.shakespeare.lit'
    id='subscriptions1'>
  <pubsub xmlns='http://jabber.org/protocol/pubsub' xmlns:bc='http://buddycloud.org/v1'>
    <subscriptions bc:subscription='subscribed' />
  </pubsub>
</iq>

Rules
Only moderators and owners can retrieve outcast or none. Only users with a status of subscribed can retrieve data*.

Only if this matches current functionality otherwise to match current.

Any thoughts on how we could page results? Use case: asking for subscriptions of all-users-auto-subscribed-channel@domain.

It just needs someone to implement RSM for subscription/affiliation
gathering again. It was taken out so we could switch to node memberships
more easily but there's no big reason we can't add it back in again.
I'm also thinking we should implement a 'memberships' stanza which is a
combo of subscription and affiliation.

Steven Lloyd Watkin
Software Engineer
PHP ::: Java ::: Ruby ::: Node.js ::: XMPP :: + many more
<EMAIL_ADDRESS>(email+jid) ::: http://www.evilprofessor.co.uk
Github / Twitter / Flickr / Facebook: lloydwatkin
Organiser of WORLD RECORD breaking charity event:
Scuba Santas ::: http://www.scuba-santas.co.uk
Supporting the RNLI & DDRC - 14th December 2014 - NDAC, Chepstow
On 3 June 2015 at 09:58, Simon Tennant<EMAIL_ADDRESS>wrote:

Any thoughts on how we could page results? Use case: asking for
subscriptions of all-users-auto-subscribed-channel@domain.
—
Reply to this email directly or view it on GitHub
https://github.com/buddycloud/buddycloud-server-java/issues/309#issuecomment-108253510
.

A membership stanza would make a lot of sense.


Bug: server url changes are not saving

Steps to reproduce the behavior
We changed our mattermost server's url, and whenever I try to change it on the desktop app, after attempting to log in, it reverts to the old url
Expected behavior
Server url should not be reverting to the previous url when saving server config
Edition and Platform

Edition: Personal Desktop
Version: 5.2.2
Browser and OS: Chrome on Windows 10

Additional context (optional)

I've tried reinstalling, same issue
Another machine's desktop app works fine, same machine's browser app works fine; other colleagues are not experiencing the same issue on their machines
I'm using tailscale vpn (not sure if this matters)

@yantato Is there a reason your server's SIte URL isn't configured the same as the one that it's being changed to? Looks like there's some kind of redirect going on.

@yantato Is there a reason your server's SIte URL isn't configured the same as the one that it's being changed to? Looks like there's some kind of redirect going on.

Not sure why they didn't config the old url for this, but as i mentioned this only affects one of my machines, all my others are using the desktop app just fine.
I just found this in mattermost forums, it sounds like a similar problem to mine https://forum.mattermost.com/t/cannot-uninstall-fully-on-windows-10/8373/2 - where the guy is having problems connecting with servers, I'm not looking to uninstall the app

@yantato Is this still an issue for you?

Hi @devinbinnie not sure if related to this or not, but a server URL I put in automatically changes from https to http, and doesn't connect after restart. Even if I manually update into https, it's not saved and still see http on server URL setting.
I

Thank you for your quick response. We have fixed the URL at the server side and it's working well now. Good to hear this won't be an issue with the upcoming release. Cheers.

Since this is fixed for upcoming releases, I'm closing this issue as fixed.

Just checked, server url changes are saved, works now


arch: Rename up_[early]serialinit to [arm64|riscv|x86_64][early]serialinit

Summary
The naming standard at:
https://cwiki.apache.org/confluence/display/NUTTX/Naming+of+Architecture%2C+MCU%2C+and+Board+Interfaces
requires that all MCU-private function begin with the name of the architecture, not up_.
follow the change from: https://github.com/apache/nuttx/pull/930
Impact
arm64, riscv-v and x86[_64]
Testing
CI

@xiaoxiang781216 please consider including in the log message the motivation to change the function name, as people suggested in the mailing list. I think a good benefit of getting rid of these tons of up_* inside all arch is it make IDE symbols search easier. Actually almost none IDE is able to resolve NuttX symbol because it uses same symbol name in different arch.

please add a proper commit message to justify the change

Done, @jerpelea @acassis

@acassis @jerpelea @pkarashchenko do you have more comment?

@acassis @jerpelea @pkarashchenko do you have more comment?

Yes. I continue discussion. I think that current change in raw and I do not fully understand the final behaviour. Now we have two functionalities:

Possibility to do very early print from assembly files that can be used even before .data and .bss init. This use some stack-less initialisations and printing
ARCH_earlyserialinit that is called from C code during boot process.
I feel that this PR is mixing things together.

@acassis @jerpelea @pkarashchenko do you have more comment?

Yes. I continue discussion. I think that current change in raw and I do not fully understand the final behaviour. Now we have two functionalities:

Possibility to do very early print from assembly files that can be used even before .data and .bss init. This use some stack-less initialisations and printing

To do this, a new assembly function will be added. The implementation will post after this patch is merged.

ARCH_earlyserialinit that is called from C code during boot process.
I feel that this PR is mixing things together.

ARCH_earlyserialinit is designed to callable in C before OS(mm/sched) fully initialize. arm64 is wrong to assume that ARCH_earlyserialinit can be called in assembly boot code, which will be fixed in the upcoming patch.

But this PR is calling arm64_earlyserialinit from early assembly. So do you propose to merge PR that "breaks the things" and then merge another PR that "fix the things"? What is the point in this instead of doing this properly in 1 PR?

Yes, since the print in assembly is disabled by default, the temp break isn't a big problem.

Currently the arm64_lowputc is implemented as
GTEXT(arm64_lowputc)
SECTION_FUNC(text, arm64_lowputc)
    ldr   x15, =UART0_BASE_ADDRESS
    early_uart_ready x15, w2
    early_uart_transmit x15, w0
    ret

but in C code I see
#if defined(CONFIG_UART1_SERIAL_CONSOLE)
#  define CONSOLE_DEV     g_uart1port         /* UART1 is console */
#  define TTYS0_DEV       g_uart1port         /* UART1 is ttyS0 */
#  define UART1_ASSIGNED  1
#endif

So UART0 may be even not a console UART.
And UART0_BASE_ADDRESS is
 /* Allwinner A64 UART0 Base Address */

 #define UART0_BASE_ADDRESS 0x1C28000

So what if MCU that is running is not Allwinner A64?
I agree that things are broken, but just do not want to go into "even more broken" state

@xiaoxiang781216  So the whole idea of this PR is just to remove up_earlyserialinit?

not remove, rename up_earlyserialinit to arm64_earlyserialinit, which just follow other arch convention. and xxx_earlyserialinit shouldn't be called by boot assembly code.

@pkarashchenko ，My new patch must wait for this patch to be merged.
at new patch, I will call assembly code directly

Ok. Let's move on with this change if the new PR is ready. I do not want to block the process despite I do not have a good explanation why this can't be done in a single PR.

Ok. Let's move on with this change if the new PR is ready. I do not want to block the process despite I do not have a good explanation why this can't be done in a single PR.

@qinwei2004 doesn't have right to modify my PR I think.

Ok. Let's move on with this change if the new PR is ready. I do not want to block the process despite I do not have a good explanation why this can't be done in a single PR.

@qinwei2004 doesn't have right to modify my PR I think.

I think since your fork is a public repo he should be able to (unless you added restrictions there). But from the "owner" perspective I agree that it is not welcomed.
Ok. Let's move on

Ok. Let's move on with this change if the new PR is ready. I do not want to block the process despite I do not have a good explanation why this can't be done in a single PR.

@qinwei2004 doesn't have right to modify my PR I think.

I think since your fork is a public repo he should be able to (unless you added restrictions there). But from the "owner" perspective I agree that it is not welcomed. Ok. Let's move on

by default, only commiter and PMC can modify other people's patch.

Ok. Let's move on with this change if the new PR is ready. I do not want to block the process despite I do not have a good explanation why this can't be done in a single PR.

@qinwei2004 doesn't have right to modify my PR I think.

I think since your fork is a public repo he should be able to (unless you added restrictions there). But from the "owner" perspective I agree that it is not welcomed. Ok. Let's move on

by default, only commiter and PMC can modify other people's patch. Otherwise, the hacker can easily inject the malicious code.

I see. I recall that I was able to push changes to your repo, so didn't know about those restrictions. Thank you for educating me.

@xiaoxiang781216 @jerpelea @acassis
So any change change is needed?? or we can merge this PR
I am waiting for merge my new change