LStacker and SNAP LXD

I have an interest in LStacker again for a new project.
Does it support the SNAP LXD ?   I am asking because SNAP LXD will be the only LXD supported when the Ubuntu 20.04 LTS is released.
thanks
brian

Hi Brian
I have not actively worked on the project in 2 years, it will need to tested against that.
Kind Regards
Brett

On 15 Sep 2019, at 20:57, brian mullan<EMAIL_ADDRESS>wrote:
I have an interest in LStacker again for a new project.
Does it support the SNAP LXD ? I am asking because SNAP LXD will be the only LXD supported when the Ubuntu 20.04 LTS is released.
thanks
brian
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/brettchaldecott/lstacker/issues/1?email_source=notifications&email_token=AABU7BAR7PES4IEYLW6SM2DQJ2AQTA5CNFSM4IW3TJW2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLOMFSA, or mute the thread https://github.com/notifications/unsubscribe-auth/AABU7BDS6MPFDU2OZCPFUFDQJ2AQTANCNFSM4IW3TJWQ.

I can try it and let you know what I find
Brian
On Sun, Sep 15, 2019, 10:53 PM Brett<EMAIL_ADDRESS>wrote:

Hi Brian
I have not actively worked on the project in 2 years, it will need to
tested against that.
Kind Regards
Brett

On 15 Sep 2019, at 20:57, brian mullan<EMAIL_ADDRESS>wrote:
I have an interest in LStacker again for a new project.
Does it support the SNAP LXD ? I am asking because SNAP LXD will be the
only LXD supported when the Ubuntu 20.04 LTS is released.
thanks
brian
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <
https://github.com/brettchaldecott/lstacker/issues/1?email_source=notifications&email_token=AABU7BAR7PES4IEYLW6SM2DQJ2AQTA5CNFSM4IW3TJW2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLOMFSA>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/AABU7BDS6MPFDU2OZCPFUFDQJ2AQTANCNFSM4IW3TJWQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brettchaldecott/lstacker/issues/1?email_source=notifications&email_token=AAM23J4HDH6SIJ6CT7XA63LQJ3YMDA5CNFSM4IW3TJW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6X7YKA#issuecomment-531627048,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM23J45QS7LJHBSFPZW6FTQJ3YMDANCNFSM4IW3TJWQ
.

That would be awesome, thank you so much.

On 16 Sep 2019, at 08:18, brian mullan<EMAIL_ADDRESS>wrote:
I can try it and let you know what I find
Brian
On Sun, Sep 15, 2019, 10:53 PM Brett<EMAIL_ADDRESS>wrote:

Hi Brian
I have not actively worked on the project in 2 years, it will need to
tested against that.
Kind Regards
Brett

On 15 Sep 2019, at 20:57, brian mullan<EMAIL_ADDRESS>wrote:
I have an interest in LStacker again for a new project.
Does it support the SNAP LXD ? I am asking because SNAP LXD will be the
only LXD supported when the Ubuntu 20.04 LTS is released.
thanks
brian
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <
https://github.com/brettchaldecott/lstacker/issues/1?email_source=notifications&email_token=AABU7BAR7PES4IEYLW6SM2DQJ2AQTA5CNFSM4IW3TJW2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLOMFSA>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/AABU7BDS6MPFDU2OZCPFUFDQJ2AQTANCNFSM4IW3TJWQ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brettchaldecott/lstacker/issues/1?email_source=notifications&email_token=AAM23J4HDH6SIJ6CT7XA63LQJ3YMDA5CNFSM4IW3TJW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6X7YKA#issuecomment-531627048,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM23J45QS7LJHBSFPZW6FTQJ3YMDANCNFSM4IW3TJWQ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/brettchaldecott/lstacker/issues/1?email_source=notifications&email_token=AABU7BAPGLYAUMOQ27SLXLTQJ4QMDA5CNFSM4IW3TJW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6YGIQY#issuecomment-531653699, or mute the thread https://github.com/notifications/unsubscribe-auth/AABU7BASL4GOJAV7WJFDU5DQJ4QMDANCNFSM4IW3TJWQ.

could you check the other documentation related Issue I opened before I try this out again?   I want to make sure a couple of my installation assumptions are correct.
thanks
brian


Weird undebuggable error when upgrading from 2.4.0 to 2.4.1

System Info
System:
    OS: macOS 14.2.1
    CPU: (12) arm64 Apple M2 Pro
    Memory: 79.17 MB / 16.00 GB
    Shell: 5.2.21 - /opt/homebrew/bin/bash
Binaries:
    Node: 18.18.2 - ~/.n/bin/node
    npm: 10.2.5 - ~/.n/bin/npm
Browsers:
    Chrome: 120.0.6099.199
    Safari: 17.2.1
npmPackages:
    @remix-run/dev: 2.4.1 => 2.4.1
    @remix-run/express: 2.4.1 => 2.4.1
    @remix-run/node: 2.4.1 => 2.4.1
    @remix-run/react: 2.4.1 => 2.4.1
    vite: 5.0.10 => 5.0.10

Used Package Manager
npm
Expected Behavior
Nothing works.
Actual Behavior
I get this vite error, I am runing the unstable-vite-express template, I've removed all custom code and I still get the error. Fresh template from the Remix repository works fine. I also tried rebuilding my app based on the fresh template (although my current app uses the same server.mjs as in the template).
TypeError: __vite_ssr_import_4__.default is not a function
    at handleRequest (/Users/XXX/web/node_modules/@remix-run/dev/dist/config/defaults/entry.server.node.tsx:18:10)
    at handleDocumentRequestRR (/Users/XXX/web/node_modules/@remix-run/server-runtime/dist/server.js:251:20)
    at async requestHandler (/Users/XXX/web/node_modules/@remix-run/server-runtime/dist/server.js:105:18)
    at async /Users/XXX/web/node_modules/@remix-run/express/dist/server.js:41:22

Figured it was related to the upgrading the isbot version to 4+
This line causes the error
https://github.com/remix-run/remix/blob/0196a1c40df9ecf0d8b1e8133c3136c84401e9cf/packages/remix-dev/config/defaults/entry.server.node.tsx#L6
It should be import {isbot} from 'isbot';

Same as https://github.com/remix-run/remix/issues/8434


Can't compile

Hi, great framework, but I wasn't able to  compile using FlexJS using terminal in mac
or  using FDT because is always pointing to the playerglobal.swc  instead of using the flash folder you provided.
Thanks
Feb 15, 2016 3:23:40 PM com.google.javascript.jscomp.LoggerErrorManager println
SEVERE: /Documents/spriteflexjs/test/bin/js-debug/com/hsharma/hungryHero/screens/InGame.js:28: ERROR - required "flash.utils.getTimer" namespace never provided
goog.require('flash.utils.getTimer');
^
Feb 15, 2016 3:23:40 PM com.google.javascript.jscomp.LoggerErrorManager println
SEVERE: /Documents/spriteflexjs/test/bin/js-debug/com/hsharma/hungryHero/screens/Welcome.js:13: ERROR - required "flash.net.navigateToURL" namespace never provided
goog.require('flash.net.navigateToURL');
^
Feb 15, 2016 3:23:40 PM com.google.javascript.jscomp.LoggerErrorManager println
SEVERE: /Documents/spriteflexjs/test/bin/js-debug/flash/display/DisplayObject.js:17: ERROR - required "flash.utils.getTimer" namespace never provided
goog.require('flash.utils.getTimer');
^
Feb 15, 2016 3:23:40 PM com.google.javascript.jscomp.LoggerErrorManager println
SEVERE: /Documents/spriteflexjs/test/bin/js-debug/flash/display/Stage.js:16: ERROR - required "flash.utils.getTimer" namespace never provided
goog.require('flash.utils.getTimer');

the lib need the flexjs 0.6.
which version flexjs skd  you are useing?

and pls ant the build.xml

I'm using 0.5, Tried to build 0.6 but a lot of errors, I'll wait until the release of 0.6, thanks

no need build,just down it,right click ,show dev build

no need build,just down it,right click ,show dev build

Thanks, I didn't know you can switch to nightly builds.
SpriteflexJs works perfectly now, thanks again


self-assembler assignment results in timeout

It has been reported to me that the the current test for the self-assembler assignment causes a timeout (runtime of 3-5min vs. an allowed maximum of 60s). Since increasing the timeout isn't practical (especially since the bulk-grader doesn't run in parallel), I suggest that we change the test a little bit.

Thoughts about that, @ckirsch @Blazefrost ?

How would you change the test?

Maybe compile selfie once from the C* source and assemble it from the output generated by -s and then compare the resulting binaries.

I thought that is what self-assembler checks...what does it actually check?

See for yourself:
    return check_execution('./selfie -c selfie.c -s selfie1.s -a selfie1.s -m 128 -a selfie1.s -s selfie2.s ',
                           'selfie can assemble its own binary file') + \
        check_execution('diff -q selfie1.s selfie2.s',
                        'both assembly files are exactly the same')```

It seems like both assembling and disassembling takes significantly longer on mipster than just compilation.
Maybe we could:

Compile, disassemble, assemble, and store a selfie binary
Load the binary into a mipster instance and let it compile and store a selfie binary.
Compare the resulting binaries from step 1 and 2

If the assemble step is working correctly, the binary from step 1 should be logically equivalent to the host's selfie and produce the same binary in step 2.

@Blazefrost Sounds good! Please do a PR.


chore: added new data module

chore: clarified tree provider source names
chore: added new data loading module
refacor: refactored the treeview provider for new data module
test: added treeprovider test cases
test: added tests for the builder part of the data module
test: added tests for the loader part of the data module

/lgtm

Beautifully done @TomerFi !
Kudos!


Fixed test to account for leap year days.

This will hopefully unblock all CI failures due to the latest comments in #1203. This new logic checks if there's a leap day within the next year, and if so, subtracts 1 day from the expected day (and accounts for month/year rollovers).
It might be worth it to factor out the logic into different functions, like having a "calculate time difference" function, which we then use to calculate if the "Next" datetime is valid, but I'm not sure how far we want to go down that hole of implementing standard datetime functions. Are there any libraries we can rely on to do these calculations?
Questions for consideration: Is there any logic I'm missing here? Is daylight savings time a consideration? (I don't think so, but I'd like thoughts from others). Are there better solutions?
I guess there are alternatives to solving this problem, like changing the CRL expiration to be 4 years (365 * 4 + 1 days) in the future (instead of 365 days), but that doesn't solve for the 100-year/400-year leap year case, which is most likely unnecessary to consider. Does solving this problem with a change to the CRL expiration being 4 years have anything to be concerned about? Thanks!

bors try

Running the CI test again, after fixing up gcc version 5 to 7 on two of the three Ubuntu 18.04 systems.
bors try

bors try

bors r+

This "Failed to extract linuxDebug18.04.tar.gz" issue is really annoying! I really wonder what causes this error. It appears to be internal to Jenkins?
@ionutbalutoiu I know you've seen this issue before too; does it continue to happen for your team?
Let's try merging again and cross fingers.
bors r+

@johnkord, I agree with you. It's kinda annoying when this is the only failure from the entire pipeline. I've opened issue https://github.com/Microsoft/openenclave/issues/1524 to get this solved.


availability ip datacenter Azure database

Hello.
I want to know what is the risk that the IP  the datacenters (primary or secondary)  change in the future, in what term and under what circumstances it would happen.
Docs:
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-connectivity-architecture#azure-sql-database-gateway-ip-addresses
Thanks.

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

ID: e1a62365-4312-8aad-d2f1-bb5c4184adf1
Version Independent ID: 2ba5b809-8025-d7ee-c756-d6d1bab033fb
Content: Directing Azure traffic to Azure SQL Database and SQL Data Warehouse
Content Source: articles/sql-database/sql-database-connectivity-architecture.md
Service: sql-database
Sub-service: development
GitHub Login: @srdan-bozovic-msft
Microsoft Alias: srbozovi

@jssanta96 Thanks for the comment! We will investigate on this issue and get back to you soon.

@jssanta96 You could use Proxy as your connection policy in which you just need to configure only 2 IPs.  In this mode, all connections are proxied via the Azure SQL Database gateways. To enable connectivity, the client must have outbound firewall rules that allow only the Azure SQL Database gateway IP addresses (usually two IP addresses per region). Choosing this mode can result in higher latency and lower throughput, depending on nature of the workload. We highly recommend the Redirect connection policy over the Proxy connection policy for the lowest latency and highest throughput.
If you want to restrict your outbound connection. You can configure your firewall with primary and secondary IPs of that region. If there is any failover you will be moved to secondary IP and if you have already configured secondary you don't need to worry about that it will work as it is. Also, It's updated on a weekly basis so you need to update your on-premises firewall rules accordingly (unlike SQL DB, other Azure service IP addresses might change over time).
Hope this helps.

@angoyal-msft  thanks for your answer, but before change to proxy mode, i need to know which the possibility the datacenter change the ip (primary or secondary) .All this for service warranty and your available to long-term

@jssanta96  as mentioned earlier. These IPs are updated on weekly basis. So you need to update your on-premises firewall rule weekly.
Hope it helps.

@jssanta96 The Azure SQL Database gateway IP addresses are subject to change but not before a notification process is initiated and a change notice is communicated out to customers.
We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

@Mike-Ubezzi-MSFT  @Mike-Ubezzi-MSFT  thank you for your answers, regarding the explained above, how the proxy mode would work with a database with failover in another region?

@jssanta96 Let me investigate.

@jssanta96 If the primary has been triggered for a fail-over event, traffic directed to the primary will be routed to the secondary. This is regardless of the connection mode:
Creating and using active geo-replication

If for any reason your primary database fails, or simply needs to be taken offline, you can initiate a failover to any of your secondary databases. When failover is activated to one of the secondary databases, all other secondaries are automatically linked to the new primary.

You can manage replication and failover of an individual database or a set of databases on a server or in an elastic pool using active geo-replication. You can do that using:

The Azure portal
PowerShell: Single database
PowerShell: Elastic pool
Transact-SQL: Single database or elastic pool
REST API: Single database

@Mike-Ubezzi-MSFT  Then for example :
My main database, which is located in the south central region of the USA and has enabled the failover to a database in Central Canada, I should not move the addresses (primary and secondary) of my firewall rules,?


Wandb init fails when on inferring environment from Git

I am trying to run jobs via a Kubernetes cluster and my job fails whenever it reaches wandb.init with the following error:
wandb: ERROR Abnormal program exit
Traceback (most recent call last):
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 996, in init
    wi.setup(kwargs)
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 133, in setup
    self._wl = wandb_setup.setup()
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_setup.py", line 318, in setup
    ret = _setup(settings=settings)
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_setup.py", line 313, in _setup
    wl = _WandbSetup(settings=settings)
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_setup.py", line 299, in __init__
    _WandbSetup._instance = _WandbSetup__WandbSetup(settings=settings, pid=pid)
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_setup.py", line 107, in __init__
    self._settings = self._settings_setup(settings, self._early_logger)
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_setup.py", line 136, in _settings_setup
    s._infer_run_settings_from_environment(_logger=early_logger)
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_settings.py", line 1392, in _infer_run_settings_from_environment
    program_relpath = self.program_relpath or _get_program_relpath_from_gitrepo(
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_settings.py", line 138, in _get_program_relpath_from_gitrepo
    root = repo.root
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/lib/git.py", line 46, in root
    return self.repo.git.rev_parse("--show-toplevel")
  File "/yes/envs/titan/lib/python3.9/site-packages/git/cmd.py", line 639, in <lambda>
    return lambda *args, **kwargs: self._call_process(name, *args, **kwargs)
  File "/yes/envs/titan/lib/python3.9/site-packages/git/cmd.py", line 1184, in _call_process
    return self.execute(call, **exec_kwargs)
  File "/yes/envs/titan/lib/python3.9/site-packages/git/cmd.py", line 984, in execute
    raise GitCommandError(redacted_command, status, stderr_value, stdout_value)
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
  cmdline: git rev-parse --show-toplevel
  stderr: 'fatal: detected dubious ownership in repository at '/nfs'
To add an exception for this directory, call:

	git config --global --add safe.directory /nfs'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/nfs/repr_comparison/scripts/source_training/train.py", line 136, in <module>
    run(args)
  File "/nfs/repr_comparison/scripts/source_training/train.py", line 84, in run
    wandb.init(
  File "/yes/envs/titan/lib/python3.9/site-packages/wandb/sdk/wandb_init.py", line 1037, in init
    raise Exception("problem") from error_seen
Exception: problem

/nfs/ here is a cluster-level name pointing to my specific Kubernetes volume claim.
I have tried passing in wandb.Settings(program_relpath=os.path.join(os.getenv("SCRIPT_DIR"), "train.py"), disable_git=True, save_code=False) (as per https://github.com/wandb/wandb/issues/1565) but it still seems to check for git when I run it.
Since I launch these in Docker containers, it's not as simple as me just running the suggested line of  git config --global --add safe.directory /nfs

Hi @pugantsov
Thanks a lot for reporting this issue. It is indeed seems like a bug. In the meantime. I would suggest using an environment variable to setup  program_relpath path. Hence when it reaches the problematic part of the code it will only evaluate the first part and avoid raising the exception.
You could do something like this:
import os
import wandb

os.environ["WANDB_PROGRAM_RELPATH"] =  ...
run = wandb.init(settings=wandb.Settings(disable_git=True, save_code=False))

We will be working on fixing this issue and hopefully it will be included in one of the upcoming releases.

But this disabled saving the code, which is quite handy for me (and most people I assume)?
Is there some other workaround? and what exactly is WANDB_PROGRAM_RELPATH?

But this disabled saving the code, which is quite handy for me (and most people I assume)?
Is there some other workaround? and what exactly is WANDB_PROGRAM_RELPATH?

@neel04 you could try removing the save_code=False (i just followed the pattern provided by @pugantsov).
We do catch the above git exception (exc.GitCommandError) in the case of code saving setup, so if that is the error you are seeing save_code should work for you.
WANDB_PROGRAM_RELPATH would be the relative path to your program from the current working directory (the directory where we by default initialize all the wandb files).

@neel04 and @pugantsov I looked at the code again and i see that we have error handling for the case you are reporting. Which version of wandb are you using?
Could you update to the latest and see if you still experiencing this issue?

Hi @pugantsov @neel04
Would you be interested to test out this branch to verify that we actually fixed your issue?
you could install it like this:
pip install git+https://github.com/wandb/wandb.git@WB-13236

I tested it locally with a malformed git folder and it seems to fix all instances of the git invocation


python38Packages.cornice: 5.2.0 -> 6.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.cornice is: "Build Web Services with Pyramid"
meta.homepage for python38Packages.cornice is: "https://github.com/mozilla-services/cornice"
meta.changelog for python38Packages.cornice is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.0.0 with grep in /nix/store/4py7r7sc2cvv7331pc4wmi57qg112p5x-python3.8-cornice-6.0.0

found 6.0.0 in filename of file in /nix/store/4py7r7sc2cvv7331pc4wmi57qg112p5x-python3.8-cornice-6.0.0

directory tree listing: https://gist.github.com/484180814dc956102829db902e306276

du listing: https://gist.github.com/b0441c4ce862dbdbb9e2e1116df64866

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

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.cornice
python39Packages.cornice

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4py7r7sc2cvv7331pc4wmi57qg112p5x-python3.8-cornice-6.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4py7r7sc2cvv7331pc4wmi57qg112p5x-python3.8-cornice-6.0.0
ls -la /nix/store/4py7r7sc2cvv7331pc4wmi57qg112p5x-python3.8-cornice-6.0.0/bin

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

2 packages built:

python38Packages.cornice
python39Packages.cornice

Maintainer pings
cc @costrouc for testing.

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

2 packages built:

python38Packages.cornice
python39Packages.cornice


Error CodeLab Firebase Cloud Functions, cannot send notification by FCM.

[REQUIRED] Codelab info
CodeLab Firebase Cloud Functions [10. New Message Notifications](https://firebase.google.com/codelabs/firebase-cloud-function
[REQUIRED] Project setup
I clone project from here.
First I follow CodeLab Firebase Hosting FriendlyChat, and I can complete it.
After that, I started to learn CodeLab Firebase Cloud Functions from 6. The Functions Directory by copy folder "codelab-friendlychat-web-main\cloud-functions-start\functions" into my existed CodeLab Firebase Hosting FriendlyChat.
I can follow instuction then success to 8. Welcome New Users
Then, I skip 9. Images moderation, because I think I do not need to know.
[REQUIRED] Describe the problem
Then at 10. New Message Notifications, I follow instruction and coding. But when I test FriendlyChat web, it did not have notification message to display.
I went to my FriendlyChat project on Firebase Console. Goto Functions and found there error.
Error: An error occurred when trying to authenticate to the FCM servers. Make sure the credential used to authenticate this SDK has the proper permissions. See https://firebase.google.com/docs/admin/setup for setup instructions. Raw server response: "<HTML>
It cannot send notification by FCM.
Belows are more detail

I am not sure, why there is security error problem. Because I follow instruction.
below is my cloud function code.
// TODO(DEVELOPER): Import the Cloud Functions for Firebase and the Firebase Admin modules here.
// Import the Firebase SDK for Google Cloud Functions.
const functions = require('firebase-functions');
// Import and initialize the Firebase Admin SDK.
const admin = require('firebase-admin');
admin.initializeApp();

// TODO(DEVELOPER): Write the addWelcomeMessages Function here.
// Adds a message that welcomes new users into the chat.
exports.addWelcomeMessages = functions.auth.user().onCreate(async (user) => {
    functions.logger.log('A new user signed in for the first time.');
    const fullName = user.displayName || 'Anonymous';

    // Saves the new welcome message into the database
    // which then displays it in the FriendlyChat clients.
    await admin.firestore().collection('messages').add({
        name: 'Firebase Bot',
        profilePicUrl: '/images/firebase-logo.png', // Firebase logo
        text: `${fullName} signed in for the first time! Welcome!`,
        timestamp: admin.firestore.FieldValue.serverTimestamp(),
    });
    functions.logger.log('Welcome message written to database.');
});

// TODO(DEVELOPER): Write the blurOffensiveImages Function here.

// TODO(DEVELOPER): Write the sendNotifications Function here.
// Sends a notifications to all users when a new message is posted.
exports.sendNotifications = functions.firestore.document('messages/{messageId}').onCreate(async (snapshot) => {
    // Notification details.
    const text = snapshot.data().text;
    const payload = {
        notification: {
            title: `${snapshot.data().name} posted ${text ? 'a message' : 'an image'}`,
            body: text ? (text.length <= 100 ? text : text.substring(0, 97) + '...') : '',
            icon: snapshot.data().profilePicUrl || '/images/profile_placeholder.png',
            click_action: `https://${process.env.GCLOUD_PROJECT}.firebaseapp.com`,
        }
    };

    // Get the list of device tokens.
    const allTokens = await admin.firestore().collection('fcmTokens').get();
    const tokens = [];
    allTokens.forEach((tokenDoc) => {
        tokens.push(tokenDoc.id);
    });

    if (tokens.length > 0) {
        // Send notifications to all tokens.
        const response = await admin.messaging().sendToDevice(tokens, payload);
        await cleanupTokens(response, tokens);
        functions.logger.log('Notifications have been sent and tokens cleaned up.');
    }
});

below are firebase packages version in package.json
"dependencies": {     "@google-cloud/vision": "^2.4.0",     "firebase-admin": "^9.9.0",     "firebase-functions": "^3.14.1"   }
Please advise me, how can I fix this proble?
Thank you very much

same issue with me

same issue with me

same issue with me

Hi nickf2k,
Can you solve this solution by yourself? Because I has remain stuck this problem.

same issue with me

Hi nickf2k,
Can you solve this solution by yourself? Because I has remain stuck this problem.

Try it: admin.initializeApp({
credential: applicationDefault()
});
instead of admin.initializeApp()

Hi nickf2k,

I try to use your solution but it has error when deploy functions to firebase.
Error: Failed to load function definition from source: Failed to generate manifest from function source: ReferenceError: applicationDefault is not defined
I am not sure about your firebase-admin version and firebase-functions version. Please advise me about package.json.
Below is my package.json
{
  "name": "friendlychat-codelab",
  "description": "Firebase SDK for Cloud Functions codelab",
  "dependencies": {
    "@google-cloud/vision": "^2.4.0",
    "firebase-admin": "^10.2.0",
    "firebase-functions": "^3.21.2"
  },
  "devDependencies": {
    "eslint": "^4.12.0",
    "eslint-plugin-promise": "^3.6.0"
  },
  "engines": {
    "node": "12"
  },
  "private": true
}

same issue with me

Hi nickf2k,
Can you solve this solution by yourself? Because I has remain stuck this problem.

Try it:
 admin.initializeApp({
    credential: applicationDefault()
});

instead of admin.initializeApp()

Hi nickf2k,
Thank you for your help again.  I just solve about this problem.
I set Enabled at Cloud Messaging API (Legacy) in Project Settings.

Now my FriendlyChat project can use FCM.
But, I notice, why Firebase Cloud Messaging use FCM "Legacy"?
If you or anyone in here know, please describe me.
Thank you very much.

Thanx! this solved mu issue !!


Running into GOPATH Error despite having GOPATH set; nothing in log.

This may be me doing something wrong rather than an issue, but I can't seem to figure out what's going wrong.
I've installed using the OS X instructions for Sublime Text 3. When I run it and open a channel, I get the following error:

GOPATH Error
No valid GOPATH found in your shell startup scripts or Sublime settings. Please read the GOPATH section in the Sourcegraph Sublime README to learn how to manually set your GOPATH.

My user settings Sourcegraph.sublime-settings file looks like this:
{
	"GOPATH": "/gopathworkspace1:/gopathworkspace2:/gopathworkspace3",
	"LOG_LEVEL": 3
}

Despite that, the log file /tmp/sourcegraph-sublime.log does not exist.
In sublime console, I see something like this, and not much else that is relevant:
[open_channel] Opening channel in browser: ['open', 'https://sourcegraph.com/-/channel/Dmitri-9af8c...']
Running shell command: open https://sourcegraph.com/-/channel/Dmitri-9af8c...
Running shell command: pwd
[network] Sending post request params: {"Action": {"Fix": "No valid GOPATH found in your shell startup scripts or Sublime settings. Please read the GOPATH section in the Sourcegraph Sublime README to learn how to manually set your GOPATH.", "Error": "GOPATH Error"}, "CheckForListeners": true}
[network] Sending POST request to URL: https://grpc.sourcegraph.com/.api/channel/Dmitri-9af8...
[network] Server responded with code 200

Any ideas on what I'm doing wrong? Thanks!

This is due to a check we do to make sure the GOPATH exists, "ls $GOPATH". When GOPATH is multiple directories, we are throwing an error. We need to stop assuming GOPATH is one directory.

The best design would keep the GOPATH as a string literal (unchanged from
$GOPATH), and pass it into the env argument for any calls to
subprocess.Popen. For the scenarios in which we use GOPATH/bin/..., we
should really just add GOPATH to a PATH variable and pass that into the
subprocess.Popen call.
On June 6, 2016 at 16:39:02, uforic<EMAIL_ADDRESS>wrote:

This is due to a check we do to make sure the GOPATH exists, "ls $GOPATH".
When GOPATH is multiple directories, we are throwing an error. We need to
stop assuming GOPATH is one directory.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sourcegraph/sourcegraph-sublime/issues/20#issuecomment-224096661,
or mute the thread
https://github.com/notifications/unsubscribe/ARfebQfMT3oKyJDuRLO4UpL8fk_0HxM8ks5qJJN2gaJpZM4InHAI
.

This is due to a check we do to make sure the GOPATH exists, "ls $GOPATH". When GOPATH is multiple directories, we are throwing an error. We need to stop assuming GOPATH is one directory.

Makes sense.
In case it's helpful, here's a definition of GOPATH env var from Go website:

The GOPATH environment variable lists places to look for Go code. On Unix, the value is a colon-separated string. On Windows, the value is a semicolon-separated string. On Plan 9, the value is a list.

This has been resolved via #25.


[Feature Request] Add CancellationToken parameter to TemporalClient.ConnectAsync and friends

Is your feature request related to a problem? Please describe.
It's standard practice in .NET APIs that perform I/O to include a CancellationToken parameter so that callers can abort I/O requests that take too long.  TemporalClient.ConnectAsync(...) doesn't accept a cancellation token.
Describe the solution you'd like
Add an optional CancellationToken to TemporalClient.ConnectAsync(...), like so:
public static async Task<TemporalClient> ConnectAsync(
    TemporalClientConnectOptions options,
    CancellationToken cancellationToken = default) { ... }

This feedback applies to other APIs as well, such as TemporalConnection.ConnectAsync(...).

On every async call that supports cancellation we do accept a cancellation token, though we intentionally deviate from .NET here and include it in the options to keep the overload count. This includes every call on a collected client.
But we intentionally did not include a cancellation token on collect because we don't have that weird up with Rust. It's not as easy as just cancelling a .NET task, I have to weave the token through Tokio in Rust. I put in this effort for RPC calls but not yet the connect process itself. I will look into putting this time in.


Use laser eyes if key provided in playground

Detect laser eyes key from Playground config and use if provided.

Super minor, just started playing with this repo and thought this might be helpful for others picking this up.

Hi,
Thanks for contributing. I disagree about your jsonl to json fixes. OpenAI is expecting a jsonl file instead of
a Json file. Regarding their [website](https://jsonlines.org/ jsonl), files should have a .jsonl file extension.
But also I realized I made some mistakes,  some of the files have a .json extension. I would rather the fix them.
Laser Cat Eyes would not report any data If the developer doesn't provide an appkey. So I think we don't need to check if the appkey exists or not, for the sake of simplicity. It may have a small effect on performance but we don't need to worry about it in the playground.

All good, reading comprehension fail on my part, thanks for the review 👍


PEAR-2247 - Cohort Builder, endless spinners in some custom filters cards

Description
Checklist

[ ] Added proper unit tests
[ ] Left proper TODO messages for any remaining tasks
[ ] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

Verified there aren't endless spinners for:

family_histories.relationship_age_at_diagnosis
follow_ups.other_clinical_attributes.undescended_testis_corrected_age_range
diagnoses.pathology_details.epithelioid_cell_percent_range

Just have a qn about the min and max removal.

All good here. made a note in jira about better fix for all the date logic. 👍


There is no tap event for full-day events

Hello,
When I tapped on the cells for full-day events in WeekView and DayView, the events did not work.
I tried onEventTap, onDateLongPress, and onDateTap.
Is there any other way to make the events work?

For anyone having this issue, you can just use a GestureDetector to detect the full-day event tap.
Here's an example:
WeekView(
  fullDayEventBuilder: (events, date) {
    return GestureDetector(
      onTap: () => doSomething(events[0]),
      child: ConstrainedBox(
        constraints: BoxConstraints(maxHeight: 200),
        child: ListView.builder(
          itemCount: events.length,
          padding: EdgeInsets.zero,
          shrinkWrap: true,
          itemBuilder: (context, index) => InkWell(
            child: Container(
              margin: const EdgeInsets.all(5.0),
              padding: const EdgeInsets.all(1.0),
              height: 24,
              child: Text(
                events[index].title,
                style: TextStyle(
                  fontSize: 16,
                  color: events[index].color.accent,
                ),
                maxLines: 1,
              ),
              decoration: BoxDecoration(
                borderRadius: BorderRadius.circular(5),
                color: events[index].color,
              ),
              alignment: Alignment.centerLeft,
            ),
          ),
        ),
      ),
    );
  },
)


Adds import statement to front page of docs for clarity and quicker start up

I'm down to try this — but I may remove it later.

Current example is very intentional.


[Bug]

Describe the Bug
On linux (I use popOS), when I want to unfold multiple choice selector, nothing appears
To Reproduce

go to Plugins in parametters
go to the settings of a plugins that contains a multiple choice selector (example : betterformattingredux of betteranimation)
find a selector
nothing happens

Expected Behavior

see the choices

Screenshots
fold

unfold

Discord Version
Stable

This issue tracker is for issues with BetterDiscord only. Plugin settings are provided by the plugin itself.


Fix for the iOS15 CoreBluetooth changes

Some properties in CoreBluetooth have changed to optional. This changes addresses that issue.
Also, some warnings were removed

I believe it needs to be merged quickly. Current version is not compiling in ios 15 (beta also)

Yes lease, we would appreciate a merge soon. We're starting to test with Xcode 13/iOS 15 Betas and we can't compile right now. Can we help in any way? Thx!!

Anyone found a workaround before this will be merged?

Anyone found a workaround before this will be merged?

We will use my branch as a workaround, using npx patch-package on  react-native-ble-plx

Anyone found a workaround before this will be merged?

We will use my branch as a workaround, using npx patch-package on react-native-ble-plx

Never used npx patch-package - can you help me a little bit?  Thanks in advance

@georgeburduhos I will post full instructions once I get it working

@georgeburduhos I will post full instructions once I get it working

Super. thanks a lot. cause ios 15 is on us :)

Since its merged now i guess we need to wait the releases to be made?

@below Any chance to get the release soon ? we are stuck with this :(
I no release is planned yet, could you please tell us how to correct manually ?
Thanks !

Would be better to ping @srgtuszy for that I guess, a release would be much appreciated

We would also appreciate a quick release!

how do I manually fix this for react-native app using the react-native-ble-plx ? I see some instructions above but not sure how to use them @below thanks!


CRIMAPP-758: Apply trust fund screen does not match current design

Description of change
Update text for:

Capital assessment > partner_benefit_from_trust_fund
Capital assessment > client_benefit_from_trust_fund

Link to relevant ticket
https://dsdmoj.atlassian.net/browse/CRIMAPP-758
Notes for reviewer
Screenshots of changes (if applicable)
Before changes:
Client:

Partner:

After changes:
Client:

Partner:

How to manually test the feature

Waiting for Chris Purvis confirmation, whether we need this change or not?


DRKey: representation of first order messages

Mapping of drkey_mgmt.capnp to go/lib.
Update of drkey_mgmt.capnp to reflect the changes in book
Remove signature and timestamp as they are abstracted in SignedPld.

This change is

Review status: 2 of 5 files reviewed at latest revision, all discussions resolved.

go/lib/ctrl/drkey_mgmt/drkey_mgmt.go, line 64 at r1 (raw file):

}

// NewPld creates a new cert mgmt payload, containing the supplied Cerealizable instance.

s/cert/drkey

go/lib/ctrl/drkey_mgmt/drkey_mgmt.go, line 75 at r1 (raw file):

func (p *Pld) ProtoId() proto.ProtoIdType {
	return proto.CertMgmt_TypeID

s/CertMgmt_TypeID/DRKeyMgmt_TypeID

go/lib/ctrl/drkey_mgmt/drkey_rep.go, line 15 at r1 (raw file):

// limitations under the License.

// This file contains the Go representation of Certificate Chain requests.

comment does not match file

go/lib/ctrl/drkey_mgmt/drkey_rep.go, line 46 at r1 (raw file):

func (c *DRKeyRep) String() string {
	return fmt.Sprintf("Src ISD-AS: %s ExpTime: %v CertVerSig: %v CertVerEnc: %v",

Field names do not match string.
Use %d for ExpTime, CertVerSrc and CertVerDst.
Also, use util.TimeToString to print the expiration time human readable.

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 15 at r1 (raw file):

// limitations under the License.

// This file contains the Go representation of Certificate Chain requests.

s/Certificate Chain/DRKey

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 42 at r1 (raw file):

func (c *DRKeyReq) String() string {
	return fmt.Sprintf("Src ISD-AS: %s ValTime: %v",

I would rename Src ISD-AS to SrcIA.
Also, pretty print ValTime.

Comments from Reviewable

Review status: 2 of 5 files reviewed at latest revision, 6 unresolved discussions.

go/lib/ctrl/drkey_mgmt/drkey_mgmt.go, line 64 at r1 (raw file):
Previously, Oncilla wrote…
s/cert/drkey

Done.

go/lib/ctrl/drkey_mgmt/drkey_mgmt.go, line 75 at r1 (raw file):
Previously, Oncilla wrote…
s/CertMgmt_TypeID/DRKeyMgmt_TypeID

Done.

go/lib/ctrl/drkey_mgmt/drkey_rep.go, line 15 at r1 (raw file):
Previously, Oncilla wrote…
comment does not match file

Done.

go/lib/ctrl/drkey_mgmt/drkey_rep.go, line 46 at r1 (raw file):
Previously, Oncilla wrote…
Field names do not match string.
Use %d for ExpTime, CertVerSrc and CertVerDst.
Also, use util.TimeToString to print the expiration time human readable.

Done.

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 15 at r1 (raw file):
Previously, Oncilla wrote…
s/Certificate Chain/DRKey

Done.

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 42 at r1 (raw file):
Previously, Oncilla wrote…
I would rename Src ISD-AS to SrcIA.
Also, pretty print ValTime.

Done.

Comments from Reviewable

Review status: 2 of 5 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

go/lib/ctrl/drkey_mgmt/drkey_rep.go, line 46 at r1 (raw file):
Previously, brothen wrote…
Done.

I would add the following function.:
// Time returns the expiration time.
func (c *DRKeyRep) Time() time.Time {
return util.USecsToTime(uint64(c.ExpTime))
}

(same forDRKeyReq )

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 42 at r1 (raw file):
Previously, brothen wrote…
Done.

same comment as above

Comments from Reviewable

Review status: 2 of 5 files reviewed at latest revision, 2 unresolved discussions.

go/lib/ctrl/drkey_mgmt/drkey_rep.go, line 46 at r1 (raw file):
Previously, Oncilla wrote…
I would add the following function.:
// Time returns the expiration time.
func (c *DRKeyRep) Time() time.Time {
return util.USecsToTime(uint64(c.ExpTime))
}

(same forDRKeyReq )

Done.

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 42 at r1 (raw file):
Previously, Oncilla wrote…
same comment as above

Done.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 6 of 7 files at r4.
Review status: 7 of 8 files reviewed, 2 unresolved discussions (waiting on @Oncilla and @brothen)

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 28 at r4 (raw file):

)

var _ proto.Cerealizable = (*DRKeyLvl1Rep)(nil)

s/Rep/Req

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 49 at r4 (raw file):

func (c *DRKeyLvl1Req) String() string {
	return fmt.Sprintf("SrcIA: %s ValTime: %v",

fits on one line

Comments from Reviewable

Review status: 7 of 8 files reviewed, 2 unresolved discussions (waiting on @Oncilla)

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 28 at r4 (raw file):
Previously, Oncilla wrote…
s/Rep/Req

Done.

go/lib/ctrl/drkey_mgmt/drkey_req.go, line 49 at r4 (raw file):
Previously, Oncilla wrote…
fits on one line

Done.

Comments from Reviewable

Review status: 7 of 8 files reviewed, all discussions resolved (waiting on @Oncilla)

Comments from Reviewable


Add fastly as adopters

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


Cannot cross-compile minimal tflite example

Issue type
Build/Install
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.14
Custom code
Yes
OS platform and distribution
Rocky Linux 8.1
Mobile device
No response
Python version
3.11
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
This is the cmake toolchain file used for cross-compilation:
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR rv64g)
set(CMAKE_C_COMPILER /local/data0/chipyard/.conda-env/riscv-tools/bin/riscv64-unknown-linux-gnu-gcc)
set(CMAKE_CXX_COMPILER /local/data0/chipyard/.conda-env/riscv-tools/bin/riscv64-unknown-linux-gnu-g++)
set(CMAKE_FIND_ROOT_PATH /local/data0/chipyard/.conda-env/riscv-tools/sysroot)
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
include_directories(BEFORE /local/data0/chipyard/.conda-env/riscv-tools/riscv64-unknown-linux-gnu/include)
Standalone code to reproduce the issue
git clone https://github.com/tensorflow/tensorflow.git tensorflow_src

mkdir minimal_build
cd minimal_build

cmake -DCMAKE_TOOLCHAIN_FILE=../riscv.cmake -DTFLITE_ENABLE_XNNPACK=OFF -DTFLITE_ENABLE_RUY=OFF -DTFLITE_ENABLE_MMAP=OFF ../tensorflow/lite/examples/minimal

cmake --build . -j 8

Relevant log output
[ 50%] Built target absl_flags
[ 98%] Built target tensorflow-lite
[ 98%] Linking CXX executable minimal
riscv64-unknown-linux-gnu/12.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: _deps/cpuinfo-build/libcpuinfo.a(init.c.o): in function `.L0 ':
init.c:(.text+0x2): undefined reference to `cpuinfo_riscv_linux_init'
riscv64-unknown-linux-gnu/12.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: minimal: hidden symbol `cpuinfo_riscv_linux_init' isn't defined
riscv64-unknown-linux-gnu/12.2.0/../../../../riscv64-unknown-linux-gnu/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
gmake[2]: *** [CMakeFiles/minimal.dir/build.make:183: minimal] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1229: CMakeFiles/minimal.dir/all] Error 2
gmake: *** [Makefile:136: all] Error 2

@abeyene Could you please verify that all source files related to cpuinfo are being compiled and included in the build. The missing cpuinfo_riscv_linux_init function should be implemented in one of the source files. Kindly upgrade to the latest TF version and let us know? Thank you!

@sushreebarsa I am cloning the tensorflow repository and using the master branch. Is that not the latest TF version by default?

@abeyene If you are using the master branch then it would be latest as you mentioned of using TF 2.14 I asked for an upgrade. Thank you for the update!

Hi @pkgoogle ,
I tried to replicate this issue on ubuntu 20 and tensorflow 2.16 but i keep running into the below error , can you please take a look
/mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:62:26: note: 'std::mutex' is defined in header '<mutex>'; did you forget to '#include <mutex>'? /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:62:31: error: template argument 1 is invalid    62 |     std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                               ^ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:62:38: error: 'TimeZoneMutex' was not declared in this scope    62 |     std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                                      ^~~~~~~~~~~~~ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:62:33: warning: unused variable 'lock' [-Wunused-variable]    62 |     std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                                 ^~~~ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:76:24: error: 'mutex' is not a member of 'std'    76 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                        ^~~~~ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:76:24: note: 'std::mutex' is defined in header '<mutex>'; did you forget to '#include <mutex>'? /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:76:29: error: template argument 1 is invalid    76 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                             ^ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:76:36: error: 'TimeZoneMutex' was not declared in this scope    76 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                                    ^~~~~~~~~~~~~ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:76:31: warning: unused variable 'lock' [-Wunused-variable]    76 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                               ^~~~ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc: In static member function 'static void absl::lts_20230802::time_internal::cctz::time_zone::Impl::ClearTimeZoneMapTestOnly()': /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:87:24: error: 'mutex' is not a member of 'std'    87 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                        ^~~~~ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:87:24: note: 'std::mutex' is defined in header '<mutex>'; did you forget to '#include <mutex>'? /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:87:29: error: template argument 1 is invalid    87 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                             ^ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:87:36: error: 'TimeZoneMutex' was not declared in this scope    87 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                                    ^~~~~~~~~~~~~ /mnt/disks/my-disk/minimal_build/abseil-cpp/absl/time/internal/cctz/src/time_zone_impl.cc:87:31: warning: unused variable 'lock' [-Wunused-variable]    87 |   std::lock_guard<std::mutex> lock(TimeZoneMutex());       |                               ^~~~ make[2]: *** [_deps/abseil-cpp-build/absl/time/CMakeFiles/time_zone.dir/build.make:102: _deps/abseil-cpp-build/absl/time/CMakeFiles/time_zone.dir/internal/cctz/src/time_zone_impl.cc.obj] Error 1 make[1]: *** [CMakeFiles/Makefile2:5567: _deps/abseil-cpp-build/absl/time/CMakeFiles/time_zone.dir/all] Error 2 make: *** [Makefile:130: all] Error 2

Hi @abeyene, can you please provide instructions on how to replicate your conda environment? Also for clarification... is riscv.cmake exactly this?:
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR rv64g)

set(CMAKE_C_COMPILER /local/data0/chipyard/.conda-env/riscv-tools/bin/riscv64-unknown-linux-gnu-gcc)
set(CMAKE_CXX_COMPILER /local/data0/chipyard/.conda-env/riscv-tools/bin/riscv64-unknown-linux-gnu-g++)

set(CMAKE_FIND_ROOT_PATH /local/data0/chipyard/.conda-env/riscv-tools/sysroot)

set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)

set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
include_directories(BEFORE /local/data0/chipyard/.conda-env/riscv-tools/riscv64-unknown-linux-gnu/include)

One thing you can try is using a previous release branch or nightly. Generally speaking master is very dynamic and depending the exact commit you hit, it may be unstable.

Hi @pkgoogle,
Yes, it seems like moving to a different release branch solved the problem. I'm able to build the minimal tflite example using release branch v2.15.0. Note that release branch v.2.17.0-rc1 did NOT work however.
Also, I've switched to a new RISC-V compiler. While the above riscv.cmake file you posted was my indeed my old one, the new configuration looks like this:
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR rv64g)

# which compilers to use for C and C++

set(CMAKE_C_COMPILER /local/data0/AB/riscv-linux/buildroot-2023.02.3/output/host/bin/riscv64-buildroot-linux-musl-gcc)
set(CMAKE_CXX_COMPILER /local/data0/AB/riscv-linux/buildroot-2023.02.3/output/host/bin/riscv64-buildroot-linux-musl-g++)

# where is the target environment located
set(CMAKE_FIND_ROOT_PATH /local/data0/AB/riscv-linux/buildroot-2023.02.3/output/host/riscv64-buildroot-linux-musl)

# adjust the default behavior of the FIND_XXX() commands:

# search programs in the host environment
set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)

# search headers and libraries in the target environment
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
include_directories(BEFORE /local/data0/AB/riscv-linux/buildroot-2023.02.3/output/host/include)

set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -DFLATBUFFERS_LOCALE_INDEPENDENT=0 -DCPUINFO_SUPPORTED_PLATFORM=0")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DFLATBUFFERS_LOCALE_INDEPENDENT=0 -DCPUINFO_SUPPORTED_PLATFORM=0")

set(CMAKE_VERBOSE_MAKEFILE ON)

So there is no longer any conda environment. Simply an existing RISC-V toolchain installation.
And yes, I created the minimal_build directory within the tensorflow repository:
git clone https://github.com/tensorflow/tensorflow.git tensorflow_src
cd tensorflow_src
mkdir minimal_build

Yes I would say the issue is resolved.
Thank you.

Sure thing, if you have no more open items please feel free to close.


Refactor rustls features so workspace can be checked.

Description
Clean up our tls options so that we can run cargo test at the top level again.
Also fixed clippy warnings that had accumulated.
Related Issue(s)

closes #985

Documentation

Thank you @wjones127 for taking a stab at this!

Well I've figured out most of the issues, but the Windows build I haven't figured out 😢

@wjones127 have you tried kicking off the windows build without loading the previous build cache?

@houqp Thanks, clearing the cache worked!


feat(#minor); compound-v2-forks; add usage on tx signers

Deployments:

https://okgraph.xyz/?q=dhruv-chauhan%2Faurigami-aurora
https://okgraph.xyz/?q=dhruv-chauhan%2Fbanker-joe-avalanche
https://okgraph.xyz/?q=dhruv-chauhan%2Fbastion-protocol-aurora
https://okgraph.xyz/?q=dhruv-chauhan%2Fbenqi-avalanche
https://okgraph.xyz/?q=dhruv-chauhan%2Fcompound-v2-ethereum
https://okgraph.xyz/?q=dhruv-chauhan%2Fcream-finance-ethereum
https://okgraph.xyz/?q=dhruv-chauhan%2Fdforce-ethereum
https://okgraph.xyz/?q=dhruv-chauhan%2Firon-bank-ethereum
https://okgraph.xyz/?q=dhruv-chauhan%2Fmoonwell-moonbeam
https://okgraph.xyz/?q=dhruv-chauhan%2Frari-fuse-ethereum
https://okgraph.xyz/?q=dhruv-chauhan%2Fscream-fantom
https://okgraph.xyz/?q=dhruv-chauhan%2Fsonne-finance-optimism
https://okgraph.xyz/?q=dhruv-chauhan%2Fvenus-protocol-bsc

Formatting:

prettier --check subgraphs/compound-forks/protocols/aurigami/src/mapping.ts subgraphs/compound-forks/protocols/banker-joe/src/mapping.ts subgraphs/compound-forks/protocols/bastion-protocol/src/mapping.ts subgraphs/compound-forks/protocols/benqi/src/mapping.ts subgraphs/compound-forks/protocols/compound-v2/src/mapping.ts subgraphs/compound-forks/protocols/cream-finance/src/mapping.ts subgraphs/compound-forks/protocols/dforce/src/mapping.ts subgraphs/compound-forks/protocols/iron-bank/src/mapping.ts subgraphs/compound-forks/protocols/moonwell/src/mapping.ts subgraphs/compound-forks/protocols/rari-fuse/src/mappings.ts subgraphs/compound-forks/protocols/scream/src/mapping.ts subgraphs/compound-forks/protocols/sonne-finance/src/mapping.ts subgraphs/compound-forks/protocols/tectonic/src/mapping.ts subgraphs/compound-forks/protocols/venus/src/mapping.ts subgraphs/compound-forks/src/mapping.ts
Checking formatting...
All matched files use Prettier code style!

tx signers can be greater than unique users, for example:
Following transactions account for 1 unique user but 2 tx signers,

https://etherscan.io/tx/0xb55fbd0875d6dbdd2361f68c45136adc3e4995bd6306e6b29521bd98f6ac3d31
https://etherscan.io/tx/0xd5d0e35ac4f65a42779f31697431772e3d0c79b42badd09933c2352dd2b7f43e

We're using RepayBorrow event, the subgraph account id takes the payer value which is common for the two txns, but the transaction.from is different.


fix travis configuration

After the repo transfer from cirulls/xspec to xspec/xspec, the travis configuration needs to be updated as it is still trying to trigger from the previous repository. Amend configuration in the .travis.yml and README. Plus, move the Saxon processing to its own directory.

As I wrote in 7303f0d moving saxon caused all existing travis build pipelines to fail!
You may probably consider reverting this change!

Also, the example bash script described on the Travis Wiki page
for xspectest in *.xspec;
    do ../bin/xspec.sh $xspectest &> result.log;
    if grep -q ".*failed:\s[1-9]" result.log || grep -q "*\sError\srunning\sthe\stest\ssuite" result.log;
        then echo "$xspectest failed" && exit 1;
        else echo "ok $xspectest";
    fi
done

did not properly detect compiling issues (e.g. when Saxon is not available at the given path).
I updated the wiki entry with better detection:
for xspectest in *.xspec;
    do ../bin/xspec.sh $xspectest &> result.log;
    if grep -q ".*failed:\s[1-9]" result.log || grep -q -E "\*+\sError\s(running|compiling)\sthe\stest\ssuite" result.log;
        then echo "FAILED: $xspectest" && exit 1;
        else echo "OK: $xspectest";
    fi
done

I answered about the location of the Saxon processor in https://github.com/xspec/xspec/commit/7303f0dce788fd8d0e091705b261d4aa284e75d2.
Thanks for updating the documentation, I will add the extra bit to run-xspec-tests.sh.

Thanks for updating the documentation, I will add the extra bit to run-xspec-tests.sh.

Great! I didn't see that it's also part of the repository...

I created #20 and #21 and I close this ticket.


JAX argsort has different behavior on ties compared to {np,tf}.argsort

import numpy as onp
import jax.numpy as jnp
import tensorflow as tf

x = onp.array([0., -0.])
onp.argsort(x)   # array([0, 1])
tf.argsort(x)       # <tf.Tensor: shape=(2,), dtype=int32, numpy=array([0, 1], dtype=int32)>
jnp.argsort(x)    #  DeviceArray([1, 0], dtype=int32)

We caught this when testing the TFP jax backend. Presumably, it won't make that much difference in practice but worth documenting.

TF2XLA will sort -0 < 0, because it uses the following comparator:
https://github.com/tensorflow/tensorflow/blob/97f3666d8c10d317a050d786c645d181cbb4d0bb/tensorflow/compiler/xla/client/lib/comparators.cc#L70
We can easily do the same in JAX.

Although on reflection I note that both NumPy and TF classic treat them as equal:
In [9]: np.argsort([-0., 0.])
Out[9]: array([0, 1])

In [10]: np.argsort([0., -0.])
Out[10]: array([0, 1])

In [15]: tf.argsort(np.array([0., -0.]))
Out[15]: <tf.Tensor: id=32, shape=(2,), dtype=int32, numpy=array([0, 1], dtype=int32)>

In [16]: tf.argsort(np.array([-0., 0.]))
Out[16]: <tf.Tensor: id=43, shape=(2,), dtype=int32, numpy=array([0, 1], dtype=int32)>

@srvasude Can you say more about what behavior you expected? It seems that neither TF or NumPy guarantee anything about the relative ordering of -0. and 0.; the sort is neither stable nor ordered in any particular way.

I don't actually have a preference here, just wanted to point this out when we were running some coherence tests in TFPs backend. I hope nothing in practice should/will depend on this. For our purposes, we can just do a sanity check that x indexed by it's argsort, is sorted.

FWIW, I think the GPU in TF classic will treat -0 as less than 0 because it does a radix sort using a conversion similar to the one linked to by @hawkinsp  (to make things even less defined).  The CPU probably treats them as equal because it uses a comparison sort and -0 should compare equal to 0 according to IEEE.
To make matters even worse, the implementation of top_k on the GPU in TF-classic switches from one that uses comparisons for small k, to one based on radix sorts for large k.

Closing because I don't think there's an action for us to take here. I agree this might perhaps be the wrong behavior for a stable sort, but that's not what we implement at the moment. So the operator is obeying its contract. Feel free to reopen if you think differently!

Closing because I don't think there's an action for us to take here. I agree this might perhaps be the wrong behavior for a stable sort, but that's not what we implement at the moment. So the operator is obeying its contract. Feel free to reopen if you think differently!


cmake: set up build-script support for swift-build-sdk-interfaces

@swift-ci please test

@artemcm do we have CI coverage for changes like this in the swift-driver repo?

@artemcm do we have CI coverage for changes like this in the swift-driver repo?

Alas, we do not (they are coming!).
For now, I'd suggest opening a draft PR against https://github.com/apple/swift and running a cross-repository test.

@artemcm do we have CI coverage for changes like this in the swift-driver repo?

Alas, we do not (they are coming!).
For now, I'd suggest opening a draft PR against https://github.com/apple/swift and running a cross-repository test.

Will do!

This seems to have regressed the Windows build: https://dev.azure.com/compnerd/3133d6ab-80a8-4996-ac4f-03df25cd3224/_apis/build/builds/49662/logs/44


Add support for calling JS

Not too bad!  Now event handlers can produce messages that will call javascript functions.
component count = div
  [ class' "counter-display" $ div [ text (show count) ]
  , div [ onClick "increment" $ id' "increment" $ button [ text "increment" ] ]
  , id' "messages" $ div []
  ]

countHandler = handler' [] (0 :: Int) reducer
  where
    reducer "increment" state =
      let newState = state + 1
      in (newState, [Browser "addMessage" (show newState)])

render = countHandler component

jsMessageAdder = [r|
  const addMessage = (value) => {
    const messagesBlock = document.querySelector("#messages");
    messagesBlock.innerHTML = value;
  }
  window.addMessage = addMessage;
|]

getTest = (defaultConfiguration { eventListeners=[jsMessageAdder] }, render)

Needs some refactoring but I can work on that tomorrow

#26


A11y_PowershellEditorServices_Terminal_Keyboard : Tooltip is not visible for the keyboard only users.

Environment Details:
VSCode Version : 1.25.1
OS Version : Win10
NVDA 2018.2.1
Additional Details:
Keyboard ,MAS1.1.1 ,MAS1.3.1
Repro Steps:
1.Launch Visual Studio code desktop application.
2.Navigate to "View" item of menu bar and select "Integrated Terminal"->Navigate to "Terminal" tab and select "PowerShell Integrated Console" from combo box.
3.Navigate to "Terminal",  "PowerShell Integrated Console" ,"New terminal" etc controls.
4.Navigate using keyboard & see whether tooltip is visible or not.
Actual:
Using mouse tooltip is visible for all the control present in the terminal tab , But for the keyboard only user it is not visible.
Expected:
For the keyboard only users tooltip should be visible.
Same issue is observed with NVDA
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
User will not able to get all the information about the control.
MAS Reference:
MAS1.3.1
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}
Does this issue occur when all extensions are disabled?: Yes
A11y_PowershellEditorServices_Terminal_Keyboard1.pptx

@isidorn the panel buttons don't seem to have content or aria-labels?

This is a duplicate of https://github.com/Microsoft/vscode/issues/52016


Can it go with the room？

Can it go with the room？

Could you clarify your question? If you're asking if AppSearch and Room databases can work together ---
AppSearch and Room are different databases. Room focuses on wrapping SQLite with improved APIs, whereas AppSearch ships a custom search implementation with a focus on full-text search and data sharing.
If you want to use the same Document object for both AppSearch and Room, you can do so. You should apply both AppSearch and Room annotations onto the same document. Note that you will have to separately index these documents into the two separate databases.


Implement Shunting Yard Algorithm

Implement the Shunting Yard Algorithm to parse statements, replacing the current recursive algorithm found in Tree.cpp. More info about the algorithm can be found on the wiki page.

No idea if this will help you guys at all or not, but Aris from Bram-Hub contains deprecated code for converting expressions to Polish notation. https://github.com/rpi-alpaca/logic/wiki/Aris

Hello Everyone.
Currently, the Shunting Yard Algorithm has been merged into Master Branch.
Thank you.


EnumEntryNameCase cannot be suppressed on (enum) class or declaration level

Expected Behavior
I should be able to suppress EnumEntryNameCase via
@Suppress("EnumEntryNameCase")
enum class SpdxLicense(
    val id: String,
    val fullName: String,
    val deprecated: Boolean = false
) {
    _0BSD("0BSD", "BSD Zero Clause License");
}

or
enum class SpdxLicense(
    val id: String,
    val fullName: String,
    val deprecated: Boolean = false
) {
    @Suppress("EnumEntryNameCase")
    _0BSD("0BSD", "BSD Zero Clause License");
}

Observed Behavior
Suppressing this way has no effect, the inspection hint is already being reporter. However, suppressing on the file-level works:
@file:Suppress("EnumEntryNameCase")

enum class SpdxLicense(
    val id: String,
    val fullName: String,
    val deprecated: Boolean = false
) {
    _0BSD("0BSD", "BSD Zero Clause License");
}

Steps to Reproduce
See code examples above.
Context
I ran into this while upgrading to Detekt 1.22 in https://github.com/oss-review-toolkit/ort/pull/6096.
Your Environment

Version of detekt used: 1.22
Version of Gradle used (if applicable): 7.5.1
Gradle scan link (add --scan option when running the gradle task): n/a
Operating System and version: Windows 11
Link to your project (if it's a public repository): https://github.com/oss-review-toolkit/ort

Having the same issue. For some reason even @file:Suppress("EnumEntryNameCase") is not working for me

This is a formatting rule. I think that we can't fix this. I'm going to keep this open if someone has an idea to fix it or can confirm that this is a "won't fix".

This is a formatting rule. I think that we can't fix this. I'm going to keep this open if someone has an idea to fix it or can confirm that this is a "won't fix".

I started to investigate this as it's a sort of recurrent issue, but couldn't find a decent solution that would allow us to support both @file:Suppress("EnumEntryNameCase") and local @Suppress("EnumEntryNameCase"). I need to get back to it.


Tips on how to use RevGrad

This question is for users experienced with RevGrad. What is recommend approach to using RevGrad?

Do we first train without RevGrad and then fine-tune with it?
Do we ramp-up the Lambda parameter? Leave it as a learnable parameter?

@janfreyberg Sorry for the late response. I am attempting to produce a network which is invariant to domain identity. I think Alpha can be backprop'ed if it is set to be a learnable parameter. Although I am not sure if that is a good idea. I can imagine the network completely corrupting the feature space. I find that RevGrad tends to destroy the primary objective if the weight of the loss is not properly balanced. I intend on exploring the effect with a ramp up.

Cool. I'm still unclear if backpropping the parameter will be possible, but maybe you could try it? If you fork the repo and set it to be a learnable parameter, let me know how it goes and I can merge it if it works well.
And yes, fully agree that the balance has to be done pretty carefully because it can have a detrimental effect on performance. It would be great to see how the performance on the domain label changes, too, as you'd ideally want it to be at chance by the time you finish training, so some experiments on charting primary metrics, domain metrics, and gradient scaling over time would be very interesting.

https://github.com/janfreyberg/pytorch-revgrad/issues/6#issuecomment-845889281
Hello, I've been using GRL recently. If I set lambda larger, the main task loss will increase greatly. If I set lambda smaller, the test results will not change much (or even decrease). So, how to balance loss, can you give me some suggestions? thank you

Hi @dingtao1,
my recommendation would be to sweep over the parameter, between 0 and 1, and to track the accuracy (or MSE, or whatever metric is appropriate) for the label you are using RevGrad for, and your main label of interest. Ideally, you'd find a point somewhere that reduces the accuracy on the RevGrad label, while keeping the performance on your main label as high (or nearly as high) as if you had no RevGrad at all (this should be your baseline).
Lastly, one recommendation is to scale the losses so they roughly match. For example, if you are using RevGrad on a regression target, and your main target is classification, I would look at the losses of both and roughly scale the losses to match. This is independent of the lambda parameter in RevGrad.
Hope that helps

若铭

Hi, I have a question related to training the model for domain adaptation, are both the loss functions trained simultaneously or I train task loss first on source domain and then again train the model on domain tasks?


Prepare 1.1.0-rc.2

This RC has a few more changes than the last but closes out the 1.1 related milestones

CRI doesn't need nsenter https://github.com/containerd/cri/releases/tag/v1.0.0-rc.2
GRPC update
Client updates
GC support for container referencing multiple snapshots

Note the release notes have no changed since the last RC with the exception of the support time frame moving along with the release train.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2292   +/-   ##
=======================================
  Coverage   45.52%   45.52%
=======================================
  Files          83       83
  Lines        9190     9190
=======================================
  Hits         4184     4184
  Misses       4330     4330
  Partials      676      676

Flag
Coverage Δ

#linux
50.05% <ø> (ø)
:arrow_up:

#windows
41.23% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


AMD Driver Timeout

It seems that the overlay causes driver timeouts on my end.
i5-10600k and ASUS RX 5700 XT
Latest drivers are installed (24.1.1)
I'm a bit scared that it's just me since I don't see an issue here yet.

same for me with nvidia (4070 Ti Super), but not always. Sometimes it works, sometimes its fatal error, sometimes this one.

Happens without overlay active too, likely an AMD issue rather than a mod issue.

Same issue. On Nvidia 3080.

Rolling back to driver version 23.12.1 looks like it has solved the issue! For Nvidia GPUs you might try looking at the "-sm5" fix which isn't mod-related: https://twitter.com/nkt_dreamer/status/1763938665557008871


Replace wildcards in dependencies with a lower bound

Fixes #37

Cherry-picked to tags setup_rust and printing_to_screen.


error: 0xe3

Hey,
I'm trying to connect a wind speed sensor using the code provided, I changed the address to match the sensor factory default but getting error: 0xe3, what does it mean and how can I resolve it?
By the way, I've tested the sensor using USB and modbus software and it works well.
Wind speed 485 transmitter instructions.pdf
`#include <Arduino.h>
#include <esp32ModbusRTU.h>
#include   // for std::reverse
esp32ModbusRTU modbus(&Serial1, 15);  // use Serial1 and pin 16 as RTS
void setup() {
Serial.begin(4800);  // Serial output
Serial1.begin(4800, SERIAL_8N1, 4, 2, true);  // Modbus connection
modbus.onData([](uint8_t serverAddress, esp32Modbus::FunctionCode fc, uint16_t address, uint8_t* data, size_t length) {
Serial.printf("id 0x%02x fc 0x%02x len %u: 0x", serverAddress, fc, length);
for (size_t i = 0; i < length; ++i) {
Serial.printf("%02x", data[i]);
}
std::reverse(data, data + 4);  // fix endianness
Serial.printf("\nval: %.2f", reinterpret_cast<float>(data));
Serial.print("\n\n");
});
modbus.onError([](esp32Modbus::Error error) {
Serial.printf("error: 0x%02x\n\n", static_cast<uint8_t>(error));
});
modbus.begin();
}
void loop() {
static uint32_t lastMillis = 0;
if (millis() - lastMillis > 5000) {
lastMillis = millis();
Serial.print("sending Modbus request...\n");
modbus.readInputRegisters(0x01, 0, 1);
}
}`
Thanks!

0xE3 is a CRC Error.
Both of your Serials run on baud rate 4800.
Change Serial.begin(4800) to Serial.begin(9600)
and try
Serial1.begin(4800, SERIAL_8N1, 4, 2, false);

Ok, did as you said and now I get this:
18:13:57.062 -> ⸮⸮⸮⤤⸮⸮⸮⸮⸮g⸮⸮儦esending Modbus request...
18:14:02.112 -> error: 0xe3
18:14:02.145 ->
18:14:07.066 -> sending Modbus request...
18:14:07.307 -> error: 0x57
18:14:07.307 ->
18:14:12.077 -> sending Modbus request...
18:14:12.247 -> error: 0xe3
18:14:12.281 ->
18:14:17.055 -> sending Modbus request...
18:14:17.191 -> error: 0xe3
18:14:17.191 ->
18:14:22.081 -> sending Modbus request...
18:14:22.149 -> id 0x00 fc 0xfe len 0: 0x
18:14:22.183 -> val: -2678576141896654202868169793836417024.00
18:14:22.217 ->
18:14:27.056 -> sending Modbus request...
18:14:27.156 -> id 0x00 fc 0xff len 0: 0x
18:14:27.192 -> val: -2679062919727141842958344527867281408.00
18:14:27.225 ->
18:14:32.086 -> sending Modbus request...
18:14:32.154 -> id 0x00 fc 0xff len 0: 0x
18:14:32.188 -> val: -10716576197462225798560161267489701888.00
18:14:32.223 ->
18:14:37.063 -> sending Modbus request...
18:14:37.131 -> id 0x00 fc 0xff len 0: 0x
18:14:37.165 -> val: -42535295865117307932921825928971026432.00
18:14:37.232 ->
18:14:42.085 -> sending Modbus request...
18:14:42.154 -> id 0x00 fc 0xff len 0: 0x
18:14:42.188 -> val: -171449642268820008294076988790847569920.00
18:14:42.256 ->
18:14:47.058 -> sending Modbus request...
18:14:47.159 -> error: 0xe3
18:14:47.159 ->
18:14:52.073 -> sending Modbus request...
18:14:52.140 -> id 0x00 fc 0xff len 0: 0x
18:14:52.174 -> val: 0.00
18:14:52.174 ->
18:14:57.058 -> sending Modbus request...
18:14:57.161 -> id 0x00 fc 0xff len 0: 0x
18:14:57.194 -> val: -42865006715634269487333512445876502528.00
18:14:57.228 ->
18:15:02.073 -> sending Modbus request...
18:15:02.174 -> id 0x00 fc 0xff len 0: 0x
18:15:02.208 -> val: -10465406442834204881406407487782912.00
18:15:02.241 ->
18:15:07.088 -> sending Modbus request...
18:15:07.156 -> id 0x00 fc 0xff len 0: 0x
18:15:07.191 -> val: -171460026862537077949334049783506010112.00
18:15:07.259 ->
18:15:12.072 -> sending Modbus request...
18:15:12.173 -> id 0x00 fc 0xfe len 0: 0x
18:15:12.207 -> val: -42866304789848903194240645069958807552.00
18:15:12.240 ->
18:15:17.084 -> sending Modbus request...
18:15:17.185 -> id 0x00 fc 0xfd len 0: 0x
18:15:17.218 -> val: -42865006715634269487333512445876502528.00
18:15:17.252 ->
18:15:22.069 -> sending Modbus request...
18:15:22.172 -> id 0x00 fc 0xff len 0: 0x
18:15:22.207 -> val: -42862410567205002073519247197711892480.00
18:15:22.241 ->
18:15:27.090 -> sending Modbus request...
18:15:27.159 -> error: 0xe3
18:15:27.159 ->
18:15:32.081 -> sending Modbus request...
18:15:32.183 -> id 0x00 fc 0xfd len 0: 0x
18:15:32.183 -> val: -10716576197462225798560161267489701888.00
18:15:32.252 ->
18:15:37.086 -> sending Modbus request...
18:15:37.188 -> id 0x00 fc 0xff len 0: 0x
18:15:37.188 -> val: -171460026862537077949334049783506010112.00
18:15:37.257 ->
18:15:42.098 -> sending Modbus request...
18:15:42.166 -> id 0x00 fc 0xff len 0: 0x
18:15:42.201 -> val: -167446503085347278102502519804526592.00
18:15:42.236 ->
18:15:47.090 -> sending Modbus request...
18:15:47.191 -> id 0x00 fc 0xfe len 0: 0x
18:15:47.225 -> val: -171449642268820008294076988790847569920.00
18:15:47.259 ->

You are using readInputRegisters which has function code 0x02.
You Wind Speed thingy accepts 0x03, which is
modbus.readHoldingRegisters(slaveaddress, address, data)

Ok, changed it, still get the same issue:
18:32:30.692 -> sending Modbus request...
18:32:30.759 -> error: 0xe3
18:32:30.793 ->
18:32:35.672 -> sending Modbus request...
18:32:35.773 -> id 0x00 fc 0xff len 0: 0x
18:32:35.807 -> val: -2679062919727141842958344527867281408.00
18:32:35.842 ->
18:32:40.667 -> sending Modbus request...
18:32:40.768 -> id 0x00 fc 0xfa len 0: 0x
18:32:40.802 -> val: -42866304789848903194240645069958807552.00
18:32:40.871 ->
18:32:45.674 -> sending Modbus request...
18:32:45.776 -> id 0x00 fc 0xfe len 0: 0x
18:32:45.810 -> val: -2679144049365556449640040316872425472.00
18:32:45.845 ->
18:32:50.698 -> sending Modbus request...
18:32:50.767 -> error: 0xe3
18:32:50.767 ->
18:32:55.688 -> sending Modbus request...
18:32:55.755 -> id 0x00 fc 0xfe len 0: 0x
18:32:55.789 -> val: -10715927160354908945106594955448549376.00
18:32:55.857 ->
18:33:00.688 -> sending Modbus request...
18:33:00.790 -> id 0x00 fc 0xff len 0: 0x
18:33:00.790 -> val: -2679062919727141842958344527867281408.00
18:33:00.857 ->

Try this, I took it straight from your manual.
If it doesn't work, also try swapping the A and B wires.
The sample code assumes returned data is 4 bytes and you only get 2 bytes.
#include <Arduino.h>
#include <esp32ModbusRTU.h>

esp32ModbusRTU modbus(&Serial1, 15);  // use Serial1 and pin 16 as RTS

void setup() {
  Serial.begin(4800);  // Serial output
  Serial1.begin(4800, SERIAL_8N1, 4, 2, true);  // <-- change this to your settings!!!!

  modbus.onData([](uint8_t serverAddress, esp32Modbus::FunctionCode fc, uint16_t address, uint8_t* data, size_t length) {
    Serial.printf("id 0x%02x fc 0x%02x len %u: 0x", serverAddress, fc, length);
    for (size_t i = 0; i < length; ++i) {
      Serial.printf("%02x", data[i]);
    }
    uint16_t temp = 0;
    memcpy(&temp, data, 2);
    float windSpeed = temp / 10.0;
    Serial.printf("\nwind speed: %.2f", windSpeed);
    Serial.print("\n\n");
  });
  modbus.onError([](esp32Modbus::Error error) {
    Serial.printf("error: 0x%02x\n\n", static_cast<uint8_t>(error));
  });
  modbus.begin();

}

void loop() {
  static uint32_t lastMillis = 0;
  if (millis() - lastMillis > 5000) {
    lastMillis = millis();
    Serial.print("sending Modbus request...\n");
    modbus.readHoldingRegisters(0x01, 0, 1);  // FC03, id 1, address 0, 1 register
  }
}

Ok so when trying with the code you provided this is what I got:
`13:56:13.452 -> sending Modbus request...
13:56:13.554 -> error: 0xe3
13:56:13.588 ->
13:56:18.432 -> sending Modbus request...
13:56:18.534 -> error: 0xe3
13:56:18.568 ->
13:56:23.430 -> sending Modbus request...
13:56:23.498 -> error: 0xe3
13:56:23.531 ->
13:56:28.451 -> sending Modbus request...
13:56:28.552 -> error: 0xe3
13:56:28.586 ->
13:56:33.460 -> sending Modbus request...
13:56:33.563 -> error: 0x32
13:56:33.563 ->
13:56:38.451 -> sending Modbus request...
13:56:38.553 -> error: 0xe3
13:56:38.587 ->
13:56:43.446 -> sending Modbus request...
13:56:43.547 -> error: 0xe3
13:56:43.580 ->
13:56:48.435 -> sending Modbus request...
13:56:48.502 -> error: 0x01
13:56:48.535 ->
13:56:53.448 -> sending Modbus request...
13:56:53.550 -> error: 0x5a
13:56:53.583 ->
13:56:58.447 -> sending Modbus request...
13:56:58.516 -> error: 0xe3
13:56:58.516 ->
13:57:03.451 -> sending Modbus request...
13:57:03.520 -> error: 0x29
13:57:03.520 ->
13:57:08.437 -> sending Modbus request...
13:57:08.541 -> error: 0xe3
13:57:08.575 ->
13:57:13.459 -> sending Modbus request...
13:57:13.561 -> error: 0xe3
13:57:13.596 ->
13:57:18.450 -> sending Modbus request...
13:57:18.555 -> error: 0x26
13:57:18.589 ->
13:57:23.440 -> sending Modbus request...
13:57:23.575 -> error: 0x7a
13:57:23.575 ->
13:57:28.449 -> sending Modbus request...
13:57:28.552 -> error: 0xe3
13:57:28.585 ->
13:57:33.446 -> sending Modbus request...
13:57:33.548 -> error: 0xe3
13:57:33.582 ->
13:57:38.445 -> sending Modbus request...
13:57:38.547 -> error: 0xe3
13:57:38.580 ->
13:57:43.462 -> sending Modbus request...
13:57:43.496 -> error: 0xe3
13:57:43.529 ->
13:57:48.456 -> sending Modbus request...
13:57:48.556 -> error: 0xe3
13:57:48.589 ->
13:57:53.464 -> sending Modbus request...
13:57:53.565 -> error: 0xe3
13:57:53.599 ->
13:57:58.473 -> sending Modbus request...
13:57:58.574 -> error: 0xe3
13:57:58.574 ->
13:58:03.450 -> sending Modbus request...
13:58:03.551 -> error: 0xe3
13:58:03.586 ->
13:58:08.471 -> sending Modbus request...
13:58:08.505 -> error: 0x01
13:58:08.539 ->
13:58:13.445 -> sending Modbus request...
13:58:13.580 -> id 0x00 fc 0x95 len 0: 0x
13:58:13.614 -> wind speed: 4456.00
13:58:13.648 ->
13:58:18.449 -> sending Modbus request...
13:58:18.552 -> error: 0xe3
13:58:18.586 ->
13:58:23.458 -> sending Modbus request...
13:58:23.560 -> error: 0xe3
13:58:23.594 ->
13:58:28.460 -> sending Modbus request...
13:58:28.563 -> error: 0xe3
13:58:28.597 ->
13:58:33.447 -> sending Modbus request...
13:58:33.583 -> error: 0xe3
13:58:33.583 ->
13:58:38.455 -> sending Modbus request...
13:58:38.559 -> error: 0xe3
13:58:38.594 ->
13:58:43.465 -> sending Modbus request...
13:58:43.567 -> error: 0xe3
13:58:43.601 ->
`
I also tried with changing the  "true" to "false" and this is what I get, only the "error: 0xe3":
13:59:31.091 -> sending Modbus request... 13:59:31.261 -> error: 0xe3 13:59:31.261 ->  13:59:36.123 -> sending Modbus request... 13:59:36.262 -> error: 0xe3 13:59:36.297 ->  13:59:41.111 -> sending Modbus request... 13:59:41.282 -> error: 0xe3 13:59:41.282 ->  13:59:46.125 -> sending Modbus request... 13:59:46.260 -> error: 0xe3 13:59:46.294 ->  13:59:51.116 -> sending Modbus request... 13:59:51.253 -> error: 0xe3 13:59:51.287 ->  13:59:56.114 -> sending Modbus request... 13:59:56.282 -> error: 0xe3 13:59:56.282 ->  14:00:01.109 -> sending Modbus request... 14:00:01.279 -> error: 0xe3 14:00:01.279 ->  14:00:06.099 -> sending Modbus request... 14:00:06.268 -> error: 0xe3 14:00:06.302 ->  14:00:11.118 -> sending Modbus request... 14:00:11.255 -> error: 0xe3 14:00:11.255 ->  14:00:16.098 -> sending Modbus request... 14:00:16.234 -> error: 0xe3 14:00:16.269 ->  14:00:21.115 -> sending Modbus request... 14:00:21.252 -> error: 0xe3 14:00:21.286 ->
Tried swapping A and B, didn't work either.. any other ideas?

What components do you use? Does your level converter support 3.3V? How does your circuit looks like?

Sparkfun RS485 Breakout:
https://www.sparkfun.com/products/10124
ESP32S:
https://cdn.instructables.com/ORIG/FOL/YWLI/JEOILQ5U/FOLYWLIJEOILQ5U.png?fit=bounds&frame=1&width=1024
I connected an external 12V power supply for the sensor, the breakout I'm feeding 3.3v with the esp32. I attached a zip with pics of the setup.
I highly appreciate the help!
Pics.zip

Is your Arduino framework up-to-date? Are you using Arduino IDE or Platformio?
Regarding hardware: did you add the 120Ohms terminating resistor at the device side?
I'm not sure if the Sparkfun board has it or not.

I ve noticed two things with your setup:
#1 In your code you use the following Pins:
RTS = Pin 15
Rx = Pin 4
Tx = Pin 2
In the photo you wired your Hardware as followed:
RTS = Pin 34
Rx = Pin 32
Tx = Pin 35
Those should match.
#2 You Sensor is not Grounded to the ESP32.

bertmelis:
No actually I do get a message I need to update my Arduino IDE, however, I'm afraid of doing so as I have much in stake now and  I don't want a software update to mess up with all my other sensor..
Regarding the resistor, I didn't use any and I'm not sure if the Sparkfun has one either, but I can say that for another RS485 sensor everything is working fine with the Sparkfun breakout board.
Hasenburg:
Yes I changed the pins and updated everything, also tried other pins and no success either..
It's grounded using the 12V adapter, you can see in the picture.
I'm at loss here.. if you have any more ideas I'd love to hear, in any case, I highly appreciate both of your help!

Ok, but I guess is the 12V adapter is not grounded to the ESP32?
The ESP32 and the Sensor, need to have the same GND!!
You need to add a wire between the Sensor's GND (or 12V adapter GND) and the 'G' Pin of the RS485 board(next to A Pin).
If they don't have the same GND, they have different logic levels hence they don't acknowledge them as message, which leads to timeout errors.

Ohhh... I'm an electronics newbie :) now it works... I still get "error: 0xe3" every now and then, but it's good enough, most of the time its good.. thanks!!
The values I get are weird though, much much higher (about 100 times) than they should be, I checked the hex output and it doesn't correlate with the decimal output, the hex values seem ok but something is going bad in the transition to decimal, any idea?
This is the output:
16:22:56.923 -> sending Modbus request...
16:22:56.958 -> id 0x01 fc 0x03 len 2: 0x0010
16:22:56.993 -> wind speed: 409.60
From what I see 0x0010 is 16 and not 409.
This is the code that is working:
`#include <Arduino.h>
#include <esp32ModbusRTU.h>
#define RS485_RX_PIN 14
#define RS485_TX_PIN 13
#define RS485_DERE_PIN 15
esp32ModbusRTU modbus(&Serial1, RS485_DERE_PIN);  // use Serial1 and pin 34 as RTS
void setup() {
Serial.begin(9600);  // Serial output
Serial1.begin(4800, SERIAL_8N1, RS485_RX_PIN, RS485_TX_PIN, false);  // <-- change this to your settings!!!!
modbus.onData([](uint8_t serverAddress, esp32Modbus::FunctionCode fc, uint16_t address, uint8_t* data, size_t length) {
Serial.printf("id 0x%02x fc 0x%02x len %u: 0x", serverAddress, fc, length);
for (size_t i = 0; i < length; ++i) {
Serial.printf("%02x", data[i]);
}
uint16_t temp = 0;
memcpy(&temp, data, 2);
float windSpeed = temp / 10.0;
Serial.printf("\nwind speed: %.2f", windSpeed);
Serial.print("\n\n");
});
modbus.onError([](esp32Modbus::Error error) {
Serial.printf("error: 0x%02x\n\n", static_cast<uint8_t>(error));
});
modbus.begin();
}
void loop() {
static uint32_t lastMillis = 0;
if (millis() - lastMillis > 5000) {
lastMillis = millis();
Serial.print("sending Modbus request...\n");
modbus.readHoldingRegisters(0x01, 0, 1);  // FC03, id 1, address 0, 1 register
}
}`

Ok a friend helped me out, we changed:
memcpy(&temp, data, 2);
To:
uint16_t temp = (data[0] << 8) | data[1];
and now it's working perfect, thanks! you guys are they best.

Regarding the terminating resistor: the manual you attached does mention this but it refers to another document. It depends on whether you have more then one modbus device on your wire.
Side note: if you're connecting grounds, you may want to do it via a resistor to limit the current if there are any large differences.


java.lang.OutOfMemoryError in generateRandomArray()

Exception in thread "pool-12981-thread-1" java.lang.OutOfMemoryError: Java heap space
at fr.bmartel.speedtest.utils.RandomGen.generateRandomArray(RandomGen.java:59)
at fr.bmartel.speedtest.SpeedTestTask$1.run(SpeedTestTask.java:253)
at fr.bmartel.speedtest.SpeedTestTask$3.run(SpeedTestTask.java:425)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Running on a Raspberry Pi 2

@bertrandmartel seems to occur at line 59: final byte[] buffer = new byte[length];

Hello, this is the same as #27 I will fix this asap

Brilliant, thank you!

We waiting for a new version!

I noticed that it would be more convenient to use file storage rather than doing that dynamically, can you test with :
speedTestSocket.setUploadStorageType(UploadStorageType.FILE_STORAGE);

before launching upload, it will store the data to upload in a file and pick to it rather than using UploadStorageType.RAM_STORAGE which is the default

@DimaDDM upgraded commons-net to 3.6, thanks

@bertrandmartel fantastic! Let us know when you have locked the next update version :)

1.26 is now available on Jcenter & Maven Central


Please check CHEBI:189552

Hi Adnan,
could you maybe check CHEBI:189552? Would be highly appreciated!
Thanks!

Now checked. Thanks


Refactoring parts of the NIC executor code, detection

The changes look great. We need to test them out with a few systems with front NICs since the logic for nearest NIC has slightly changed. I will check if I still have access to the dual port system

Changes merged into rdma_exec_integration


WithdrawReasons should be u8 not i8

The bitflag used for WithdrawReasons is typed i8. Is there are reason for this? In my opinion it should be u8
https://github.com/paritytech/substrate/blob/787ea591eaf9cd2e8b0d638c87d9745762047aa3/frame/support/src/traits/tokens/misc.rs#L129

Using type i8 would produce a literal overflow error for values such as 0b10000000.
The error can be reproduced by attempting to compile with a test value:
bitflags::bitflags! {
	/// Reasons for moving funds out of an account.
	#[derive(Encode, Decode)]
	pub struct WithdrawReasons: u8 {
		/// In order to pay for (system) transaction costs.
		const TRANSACTION_PAYMENT = 0b00000001;
		/// In order to transfer ownership.
		const TRANSFER = 0b00000010;
		/// In order to reserve some funds for a later return or repatriation.
		const RESERVE = 0b00000100;
		/// In order to pay some other (higher-level) fees.
		const FEE = 0b00001000;
		/// In order to tip a validator for transaction inclusion.
		const TIP 	= 0b00010000;
		const TEST = 0b10000000;
	}
}

This would produce the following error:
error: literal out of range for `i8`
   --> frame/support/src/traits/tokens/misc.rs:144:17
    |
144 |         const TEST3 = 0b10000000;
    |                       ^^^^^^^^^^
    |
    = note: `#[deny(overflowing_literals)]` on by default
    = note: the literal `0b10000000` (decimal `128`) does not fit into the type `i8` and will become `-128i8`
    = help: consider using the type `u8` instead

The error is not produced when the type is u8.
Justification
Whilst additional values may not be foreseen in Substrate, future values can be added by teams implementing a workaround as we do in Totem Accounting (Substrate v3 Frame2 migration): totem-lego/-/blob/master/frame/support/src/traits/tokens/misc/
There does not appear to be a good reason to use type i8 as it would prevent other teams from building more complex enhancements to the WithdrawReasons struct.


Add pack jsons for The Ebb and Flow and Elements Unbound

I didn't submit any of the cards, just went ahead and filled in the pack data while I was in that part, since it was missing for The Ebb and Flow


CollectionExists

When we have an basic interface #13 we should check if certain collection of document type exists when creating a collection.
Also should be a functionality the user can use to check it whenever.

Decide in which project this should exist.


[BEAM-1470] A quite logger for testing.

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @staslev

Consider this one, where we set the default to ERROR (so that only errors are printed out) but specifically set the TestSparkRunner to INFO so that test related stuff still show.
log4j.rootLogger=ERROR, testlogger

# A1 is set to be a ConsoleAppender.
log4j.appender.testlogger=org.apache.log4j.ConsoleAppender
log4j.appender.testlogger.target = System.err
log4j.appender.testlogger.layout=org.apache.log4j.PatternLayout
log4j.appender.testlogger.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n

log4j.logger.org.apache.beam.runners.spark.TestSparkRunner=INFO

please retest this

Coverage remained the same at 69.704% when pulling ab06451e01f7b1c2ba0b9c23137ddb1beb30f726 on amitsela:BEAM-1470 into 93ae666bea01d4b90e2d6748b6139f34baee5111 on apache:master.

LGTM.

Sorry for the delay: LGTM too


Feedback for "Terminal" - a suggestion

https://help.sap.com/webcomponents/products/SAP Business Application Studio/9d1db9835307451daa8c930fbd9ab264/c8b4ae95701942a5a21be4e84749f97f.html
i would add that the quickest way to arrive at the directory in the terminal is to right-click on the folder in the explorer and then select 'Open in Terminal'.
Thank you,
gm

Hi @greg2git 👋
Thank you for helping us improve our product.
I will update the guide accordingly. You will be able to see the updated document within a couple of days.


Zabbix Problems Empty

Describe the bug
When trying to display zabbix problems, the panel is empty showing "no problems found".
But when looking in the "data" tab of query inspector we can see there is data.
Expected behavior
A clear and concise description of what you expected to happen.
Grafana zabbix problems showing all zabix problems.
Screenshots
Problem:

Data is here:

Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

7.2.1
3.4.15
4.0.1

Same experience here.

Hi! I've found similar bug - when Problem field set to empty, then problems are not displayed. This bug caused by null value which is the filter set to. The workaround is using /.*/ regex as a Problem filter. Could you confirm this workaround is fixing your issue? If yes, then you can use it and wait for the next release, where bug is fixed (6c20b07c69c7e5ef611aaa6b69f8eb678f77bb2e).

Using /.*/ in the problems section worked for me.

Ok, so closing this - fix will be available in 4.0.2 release.

Hi,
I have exactly the same problem ReiNolkari has been reporting with this issue. So, the actual problems list remains empty although I can see quite a few data returned by the query. I understand the issue was supposed to be fixed in 4.0.2 but I seem to face it even now with latest plugin version 4.1.4, Grafana 7.3.0 and Zabbix server version v3.4.1. I do not seem to work around this even by putting the /.*/ regex in all the possible fields. I have actually tried many combinations of Grafana versions between 7.0.1 to latest 7.4.3 and plugin versions between 4.0.1 to the latest and the problem persists in all cases. Very weird. Could there be any explanation for this @alexanderzobnin?
Thanks,
Elton


app_setting and system_setting packages not working

Hi there i am facing trouble while navigating to android wifi setting screen and i dont know how to solve this issue the screenshot will show u the exception below

Hi I see you've filed already the issue in the app_settings plugin repository https://github.com/spencerccf/app_settings/issues/48
Closing, as this isn't an issue with the 3rd party plugin,
if you disagree or it turns out the issue is not plugin specific write in the comments and I will reopen it
Thank you

hi there bro actually in the app setting repo there are number of issues not solved yet thats why i came here and open issued here bcoz i know they  they will take alot of time to solved all that issues .


Adds a more flexibility to BlockchainElementGenerator

Adds a few helper functions to BlockchainElementGenerator

Coverage remained the same at 91.209% when pulling 11a1e87aab5e9863e8d01eca18653484ebef8209 on Christewart:master into 0727b417f9f89e18bb0a3eea95eca489deb0b814 on bitcoin-s:master.

Coverage increased (+0.2%) to 91.414% when pulling 1853698b334ec6fb8e4e160a38e8775d8b4c3eea on Christewart:master into 0727b417f9f89e18bb0a3eea95eca489deb0b814 on bitcoin-s:master.

ACK.


RuntimeError: grpc cannot be used before and after forking

I am using the following config in my deployed environments -
Rails.application.configure do      config.cache_classes = true      config.eager_load = true   end
If I call Temporal.start_worflow with above configuration, I get  -
RuntimeError: grpc cannot be used before and after forking from /bundle/ruby/2.6.0/gems/grpc-1.50.0-x86_64-linux/src/ruby/lib/grpc/generic/client_stub.rb:493:in create_call'`
However if both cache_classes and eager_load is set to false, it works.
Any suggestions on how I can resolve this?

RuntimeError: grpc cannot be used before and after forking
Description:
When using the Puma server with multiple workers, I encountered the grpc that cannot be used before and after forking error. This issue occurs when there is more than one worker in Puma. The error arises because the grpc library is not designed to be safely used before and after the forking process, which happens in a multi-process environment.
Cause:
Puma uses the fork mechanism to create multiple worker processes for handling concurrent requests. However, the grpc library may encounter conflicts if it is initialized before and after forking, leading to the mentioned error.
Solution:
To address this issue, move the initialization of grpc inside the on_worker_boot block in the Puma configuration (config/puma.rb). The on_worker_boot block ensures that the grpc library is initialized in each worker process separately, avoiding conflicts and enabling smooth functioning in a multi-worker environment.
# config/puma.rb

on_worker_boot do
  Temporal.configure do |config|
    config.host = 'localhost'
    config.port = 7233
    config.namespace = 'ruby-samples'
    config.task_queue = 'hello-world'
    config.credentials = GRPC::Core::ChannelCredentials.new # :this_channel_is_insecure does not work for me
  end
end

By moving the grpc initialization inside on_worker_boot, each worker process will have its own isolated instance of grpc, resolving the grpc cannot be used before and after forking error and ensuring proper functioning in a multi-worker environment.
or just waiting for this PR with solution