global_sdk_config.is_enabled() is ignored for async

When disabling the XRay API using global_sdk_config. I'm still getting errors when using the Async pattern.
I've created the following script to demonstrate the bug:
import asyncio
import sys

from aws_xray_sdk import global_sdk_config
from aws_xray_sdk.core import xray_recorder

# Enable SDK based on argument
if 'enable' in sys.argv:
    print('Enabling XRay')
    global_sdk_config.set_sdk_enabled(True)
else:
    print('Disbling XRay')
    global_sdk_config.set_sdk_enabled(False)

@xray_recorder.capture('normal')
def test_normal():
    print('IN NORMAL')

@xray_recorder.capture_async('async')
async def test_async():
    print('IN ASYNC')

if 'normal' in sys.argv:
    print('EXECUTE NORMAL')
    test_normal()

if 'async' in sys.argv:
    print('EXECUTE ASYNC')
    asyncio.get_event_loop().run_until_complete(test_async())

[PASS] Enable XRay, execute sync call
If I call this script:
python test.py enable normal

The output is:
Enabling XRay
EXECUTE NORMAL
cannot find the current segment/subsegment, please make sure you have a segment open
Traceback (most recent call last):
  File "test.py", line 27, in <module>
    test_normal()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/models/subsegment.py", line 58, in __call__
    meta_processor=None,
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 417, in record_subsegment
    subsegment = self.begin_subsegment(name, namespace)
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 284, in begin_subsegment
    segment = self.current_segment()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 267, in current_segment
    entity = self.get_trace_entity()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 369, in get_trace_entity
    return self.context.get_trace_entity()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/context.py", line 93, in get_trace_entity
    return self.handle_context_missing()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/context.py", line 118, in handle_context_missing
    raise SegmentNotFoundException(MISSING_SEGMENT_MSG)
aws_xray_sdk.core.exceptions.exceptions.SegmentNotFoundException: cannot find the current segment/subsegment, please make sure you have a segment open

Which is what I would expect. I never created a segment, so it is perfectly correct to raise exception.
[PASS] Disable XRay, execute sync call
When I call the script again:
python test.py disable normal

The output is:
Disbling XRay
EXECUTE NORMAL
cannot find the current segment/subsegment, please make sure you have a segment open
IN NORMAL

Again correct. (I'm not entirely sure if the "cannot find the current segment/subsegment, please make sure you have a segment open" message is justified, as I've disabled the SDK, I actually am not expecting it to report me anything. But I'll let that one slide for this report.
[PASS] Enable XRay, execute async call
I execute the script:
python test.py enable async

And output:
Enabling XRay
EXECUTE ASYNC
cannot find the current segment/subsegment, please make sure you have a segment open
Traceback (most recent call last):
  File "test.py", line 31, in <module>
    asyncio.get_event_loop().run_until_complete(test_async())
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete
    return future.result()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/async_recorder.py", line 33, in __call__
    meta_processor=None,
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/async_recorder.py", line 75, in record_subsegment_async
    subsegment = self.begin_subsegment(name, namespace)
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 284, in begin_subsegment
    segment = self.current_segment()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 267, in current_segment
    entity = self.get_trace_entity()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 369, in get_trace_entity
    return self.context.get_trace_entity()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/context.py", line 93, in get_trace_entity
    return self.handle_context_missing()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/context.py", line 118, in handle_context_missing
    raise SegmentNotFoundException(MISSING_SEGMENT_MSG)
aws_xray_sdk.core.exceptions.exceptions.SegmentNotFoundException: cannot find the current segment/subsegment, please make sure you have a segment open

Just like the synchronous call. I was expecting this.
[FAIL] Disable XRay, execute async call
I execute the script again:
python test.py disable async

And now the fun begins:
Disbling XRay
EXECUTE ASYNC
cannot find the current segment/subsegment, please make sure you have a segment open
Traceback (most recent call last):
  File "test.py", line 31, in <module>
    asyncio.get_event_loop().run_until_complete(test_async())
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete
    return future.result()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/async_recorder.py", line 33, in __call__
    meta_processor=None,
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/async_recorder.py", line 75, in record_subsegment_async
    subsegment = self.begin_subsegment(name, namespace)
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 284, in begin_subsegment
    segment = self.current_segment()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 267, in current_segment
    entity = self.get_trace_entity()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/recorder.py", line 369, in get_trace_entity
    return self.context.get_trace_entity()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/context.py", line 93, in get_trace_entity
    return self.handle_context_missing()
  File "/home/idoorn/anaconda2/envs/bazelenv36/lib/python3.6/site-packages/aws_xray_sdk/core/context.py", line 118, in handle_context_missing
    raise SegmentNotFoundException(MISSING_SEGMENT_MSG)
aws_xray_sdk.core.exceptions.exceptions.SegmentNotFoundException: cannot find the current segment/subsegment, please make sure you have a segment open

And it fails.. The XRay SDK is disabled, but still it complains that I have to open the segment.
I guess somewhere there is a check missing for the global_sdk_config.is_enabled() state.

Additionally, if I tweak the script to:
import asyncio
import sys

from aws_xray_sdk import global_sdk_config
from aws_xray_sdk.core import xray_recorder

# Enable SDK based on argument
if 'enable' in sys.argv:
    print('Enabling XRay')
    global_sdk_config.set_sdk_enabled(True)
else:
    print('Disbling XRay')
    global_sdk_config.set_sdk_enabled(False)

def test_normal():
    with xray_recorder.capture('normal'):
        print('IN NORMAL')

async def test_async():
    with xray_recorder.capture_async('async'):
        print('IN ASYNC')

if 'normal' in sys.argv:
    print('EXECUTE NORMAL')
    test_normal()

if 'async' in sys.argv:
    print('EXECUTE ASYNC')
    asyncio.get_event_loop().run_until_complete(test_async())

Note that I replaced the: @xray_recorder.capture{_async} sections with: with xray_recorder.capture{_async}
In this case, all 4 variants of calling the function are failing with the same error. So even for the normal synchronous method the Python doesn't adhere to the fact that the SDK is disabled.

Hi IvDoorn,
Thanks for the detailed bug report. I think it's safe to assume we're missing a disabled check (and a test along with it). We'll dive into this and verify as soon as we can. We are also happy to take PRs from the community.
Thanks,
Sandra

@awssandra "I think it's safe to assume we're missing a disabled check" as in disabling does not work completely?


[GSSOC'23] Created an Indian Sign Language Detection

Indian Sign Language Detection Model #1606

Close #1606

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

Kindly review this PR , Waiting for response.

@Saurabh-kumar09 , Kindly review this PR

Kindly, can anyone review this PR, Waiting for response.

@pranjay-poddar, @Saurabh-kumar09 , @MohitGupta121
Kindly review this PR . Waiting for response


[Rust]: Implement nist256p1 curve

Description
This PR implements signing, verifying, working with private and public keys using nist256p1 curve.
How to test
Run Rust and C++ tests. Run fuzz testing via:
cd rust/tw_keypair
cargo fuzz list
# Run each fuzz target:
cargo fuzz run tw_private_sign --jobs=10
cargo fuzz run tw_private_to_public --jobs=10
cargo fuzz run tw_public_verify --jobs=10

Types of changes
The curves implemented:

TWCurveNIST256p1 - link

The public key types implemented:

TWPublicKeyTypeNIST256p1 - link
TWPublicKeyTypeNIST256p1Extended - link

IMPORTANT
In this PR I've used RustCrypto::p256 to work with nist256p1 elliptic curve.
Unlike trezor-crypto, p256 generates different signatures half the time, so I had to change some signatures in CPP, Android and iOS tests.
I've also added multiple tests with random inputs in order to make sure if the signatures given by p256 crate are valid.

No, will do

have you tried sending ontology / neo tx to network

Yes, pushed the implementation:

another question is can we do recovery for secp256k1 and nist256p1?

https://github.com/trustwallet/wallet-core/blob/45db78e47dfbf8d0404fac7852e9d531bc100202/rust/tw_keypair/src/ecdsa/nist256p1/public.rs#L28-L33


Cow: Watch theindustreebar.com.au

Cow requests the watch of the watch_keyword theindustreebar\.com\.au. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

theindustreebar\.com\.au has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Improve validation checks for the topic directive

Changes within this PR resolve issue #20.
I added some tests that make sure that a conversion fails if specific conditions are not met.
I also had to adjust some existing .graphql files so that they comply with the new rules.

Ah, ok, the check failed because I forgot to update the message string

I created a separate method for the keyArg check and the logic there is a little bit superfluous there because we could just return additionalKeyArgCheckResult immediately but then when there is a check for the key field, this should not be a problem


build: add a vercel.json

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I should add a vercel.json for security header purpose.
Describe alternatives you've considered
None.
Additional context
I have already a draft file in other repo.

not any vercel.json ever since i've migrated to gh pages


add version argument to integ test shell

Signed-off-by: Tianle Huang<EMAIL_ADDRESS>Description
Add the support for version argument.
During https://github.com/opensearch-project/opensearch-build/issues/604 I noticed the integ test command failed with Invalid option: -v
Executing "/tmp/tmpz2xuwc_d/functionalTestDashboards/integtest.sh -b localhost -p 5601 -s false -v 1.2.0" in /tmp/tmpz2xuwc_d/functionalTestDashboards
2021-11-30 02:14:32 INFO     status,  is 1
2021-11-30 02:14:32 INFO     stdout is Invalid option: -v

After checking this repo, I realized that this option is not available.
Issues Resolved
Resolves https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/39
Test
The previous -v error is gone.
./integtest.sh -b localhost -p 5601 -s false -v 1.2.0
./integtest.sh: line 80: npm: command not found

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

discard this due to broken commit message. Created a new one


Bug : Canada is not recognized correctly

Hi,
First of all, thanks for this great piece of software.
I may have encountered a bug while working on some partial OSM data set.
I am using geofabrik.de which provides the OSM data per country
http://download.geofabrik.de/
Cosmogony is working well for France, Belgium and Germany.
But for Canada it is not working properly.
http://download.geofabrik.de/north-america/canada-latest.osm.pbf
The shape (the geometry if you prefer) of Canada  is not computed correctly.
Displaying this shape shows only the Haïda Gwaïi archipelago and not the main land !
As a direct consequence the hierarchy is not computed correctly
For example, It computes
Mount Royal, Montreal (06), Quebec
But it should compute
Mount Royal, Montreal (06), Quebec, Canada
Any idea how to fix it ?
Best regards,

It's strange the country seems correctly displayed on cosmogony.world (don't know when the data have been generated though)
I think it's due to the fact that you used a partial osm export that does not contain the whole geometry of the country. I had a similar problem once when using a geofabrik export (I can't remember if it was for france or europe) when their bounding box was filtering some points of the country geometry.
If you can find the right bounding box, you can send geofabrik an email, they are usually very quick to respond.

As @antoine-de pointed out perfectly well, this issue is very probably caused by the polygon used by Geofabrik (visible on this page) not quite covering the whole Canada relation boundary.
Here is a corrected polygon that I've just sent to Geofabrik:
canada_updated.poly.zip
In the meantime it's possible to use the (significantly larger) North America file or to build your own extract using osmium for example.

You are right. I have tried with the North America file and everything works well.
Thanks a lot for your fast answers.

FYI Geofabrik has updated the polygon used to generate the Canada extract.
It should now work correctly with canada-latest.osm.pbf


Feature/issue 14/open in system tray

Implementation of SystemTrayManager class. The class purpose is to bind to a main window of a program and manage tray icon of that window.
I have a question implementation wise. Do you see your app using multiple tray icons? Because I can implement the class in different ways. I was thinking of a singleton pattern in case you will ever need only one tray icon or I can do it the way it will be able to create multiple tray icons for different windows (I will probably have to make a more general class then). So let me know which of those you see more fit for your app, thanks.

Oh, and about the multiple tray icons, I am not 100%  sure if my idea will work, so don't take it for granted.

hello @ioki9, I am not able to compile your code. What command do you use for compilation?
I use: g++ -std=c++17 src/main.cpp
getting the following error while compiling your code:
err.txt

hello @ioki9, I am not able to compile your code. What command do you use for compilation?
I use: g++ -std=c++17 src/main.cpp
getting the following error while compiling your code: err.txt

Sorry, I forgot to mention you need to link Gdi32 library for some functions to work. ( -lGdi32)

Okay, thanks.

Oh, you have std mutex/thread errors. May I ask what compiler are you using? If you use mingw then I think you need a version with POSIX threads for std mutex/threads to work. I can rewrite that with winapi threads instead of std if you want, although I never used them before,

Actually i am AFK currently, will check the posix version once i get back. Until then, i just wanted to convey the plan that i have already made an issue to start with the GUI interface of this software - so it's already on the roadmap. Now, I believe, with whatever lightweight GUI library we use, we will get some API to make the program run in background - either accessible in the tray or in the task manager. Due to which I think, we can focus on GUI part first, and incorporate this change with that.

@ioki9, first of all, thank you so much for your contribution. I couldn't test it previously as my version of MinGW g++ didn't support threads and mutex, which is why I migrated my project from g++-based compilation to cl (MSVC)-based compilation locally. By doing so, I was able to compile your source code correctly, after making some amendments, of course.
While testing, I noticed that your implementation minimizes the window automatically when it loses focus, which is a clever solution. However, it can still be annoying for the user who may see the program running in the taskbar. Taking these factors into consideration, I won't be able to merge this pull request. Please let me know your thoughts.

@hetulbhatt Behavior of window minimization on focus loss (when you click somewhere else) is a default Windows behavior.  If so then I haven't written the code for such behavior and I don't get it this behavior on my machine. Can you explain in more details what do you mean?

Focus on your app.
I pressed on vscode, focus is on vscode, your window is not minimized.

Closing this pull request due to merge conflicts. Thanks @ioki9 for your efforts. If you are still interested in this project, you can check this spike: https://github.com/hetulbhatt/KeyFlow/issues/18


Fixes issue #36

To Do: calculate SNR_single slice-wise

@jcohenadad SNR_single is now computed slice-wise


MSID: 89656 Version: 1 DOI: 2<IP_ADDRESS>7802

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=89656)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/89656/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[ ] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>7802)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/89656/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/89656)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/89656

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/89656

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/89656/v1/89656-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/89656)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Full text not yet available at bioRxiv

Getting a 500 internal server error from https://prod--epp.elifesciences.org/preview/89656/v1. Suspect this one still needs loading.


feat: Add config to allow surpressing notification on launch (flag cache load)

Description
This pull request introduces a new feature to disable notifications on initialization and refactors the caching mechanism to support this feature. It also includes updates to the test suite to ensure the new functionality works as expected.
Problem

go-feature-flag always sent notification of diff to all Notifierson ffClient initialization because it detects the difference between the initial cache (= always empty) and the flags retrieved.

Resolution

introduce DisableNotificationOnInit configuration key. If set to true, avoid sending the notification on cache initialization (it will still send notification when the change is detected AFTER initialization)

Since the behavior (should) stays the same if the new config is NOT set, it should not introduce any breaking change.

How to test

I've added some tests to make sure the behavior stays the same when the new config is not explicitly set. You can run go test ./...
Or, simply initialize ffClient should do the trick too.

Closes issue(s)

Resolve #2532
Checklist

[x] I have tested this code
[x] I have added unit test to cover this code
[x] I have updated the documentation (README.md and /website/docs)
[x] I have followed the contributing guide

Sorry about the repeated commits. I think I've fixed the issue, and hopefully it works now.

@thomaspoignant Thank you for reviewing and giving me suggestions! 🚀


retryable integration cancellation/crediting  tests

added the integration tests. I get the following error when attempting to cancel a retryable:
Error: cannot estimate gas; transaction may fail or may require manual gas limit (error={"reason":"cannot estimate gas; transaction may fail or may require manual gas limit","code":"UNPREDICTABLE_GAS_LIMIT","error":{"reason":"processing response error","code":"SERVER_ERROR","body":"{"jsonrpc":"2.0","id":447,"error":{"code":-32000,"message":"execution reverted"}}\n","error":{"code":-32000},"requestBody":"{"method":"eth_estimateGas","params":[{"gasPrice":"0x11fa3932","from":"0x5ca71680c74a8c15de4be49a32c460e0de633091","to":"0x000000000000000000000000000000000000006e","data":"0xc4d252f583a1f53a0aac87211a566187a7007fbaebe9afa09562893a11cc07fcb54b9fd4"}],"id":447,"jsonrpc":"2.0"}","requestMethod":"POST","url":"https://rinkeby.arbitrum.io/rpc"},"method":"estimateGas","transaction":{"from":"0x5cA71680c74a8C15De4be49A32C460E0DE633091","gasPrice":{"type":"BigNumber","hex":"0x11fa3932"},"to":"0x000000000000000000000000000000000000006E","data":"0xc4d252f583a1f53a0aac87211a566187a7007fbaebe9afa09562893a11cc07fcb54b9fd4"}}, tx={"data":"0xc4d252f583a1f53a0aac87211a566187a7007fbaebe9afa09562893a11cc07fcb54b9fd4","to":{},"from":"0x5cA71680c74a8C15De4be49A32C460E0DE633091","gasPrice":{},"nonce":{},"gasLimit":{},"chainId":{}}, code=UNPREDICTABLE_GAS_LIMIT, version=abstract-signer/5.0.14)

This surfaced a few things which I added to the PR here https://github.com/OffchainLabs/arbitrum/pull/1346 ; you should merge those changes onto this branch (/they should be on master soon).
I'll explain each by commit:

https://github.com/OffchainLabs/arbitrum/pull/1346/commits/1fe5c5d3efc700ef18b5dddeb847cb4fce34c16b Only the beneficiary is allowed to cancel a retryable. The deposit method by default uses the caller of (on L1) for the benficiary; the tests as is aren't using the same address for the L1 and L2 wallets. This fixes that.
https://github.com/OffchainLabs/arbitrum/pull/1346/commits/aa6c3eb6a8b1950d568edf3a821f60d75cb2a129 the maxGas override option wasn't actually being used in deposit, thus the retryable was actually getting autoredeemed
https://github.com/OffchainLabs/arbitrum/pull/1346/commits/427f916a5c15580cdc20c614414f786cbe7ad422 ... but wait! (I hear you say), cancelRetryableTicket already sanity checks that the transaction hasn't been redeemed yet, so why weren't we getting the nice error message?? (Because we were checking against the wrong provider)

3 things caught by one test, not bad 👌.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: RahulMaganti47:x: DZGoldmanYou have signed the CLA already but the status is still pending? Let us recheck it.


Failed to open TCP connection to sns (getaddrinfo: No address associated with hostname)

Hello,
Friday at nearly same time, on of my sensu-client and my sensu-server crashed with this stacktrace
/opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:882:in `rescue in block in connect': Failed to open TCP connection to sns.eu-west-1.amazonaws.com:443 (getaddrinfo: No address associated with hostname) (Seahorse::Client::NetworkingError)
    from /opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:879:in `block in connect'
    from /opt/sensu/embedded/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
    from /opt/sensu/embedded/lib/ruby/2.3.0/timeout.rb:101:in `timeout'
    from /opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:878:in `connect'
    from /opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:863:in `do_start'
    from /opt/sensu/embedded/lib/ruby/2.3.0/net/http.rb:858:in `start'
    from /opt/sensu/embedded/lib/ruby/2.3.0/delegate.rb:83:in `method_missing'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/net_http/connection_pool.rb:281:in `start_session'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/net_http/connection_pool.rb:93:in `session_for'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/net_http/handler.rb:116:in `session'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/net_http/handler.rb:68:in `transmit'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/net_http/handler.rb:42:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/plugins/content_length.rb:12:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/xml/error_handler.rb:8:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/request_signer.rb:84:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/helpful_socket_errors.rb:10:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:87:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:118:in `retry_request'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:101:in `retry_if_possible'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:89:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:118:in `retry_request'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:101:in `retry_if_possible'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:89:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:118:in `retry_request'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:101:in `retry_if_possible'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/retry_errors.rb:89:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/query/handler.rb:27:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/user_agent.rb:12:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/plugins/endpoint.rb:41:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/param_validator.rb:21:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/plugins/raise_response_errors.rb:14:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/aws-sdk-core/plugins/param_converter.rb:20:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/plugins/response_target.rb:21:in `call'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/request.rb:70:in `send_request'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.7/lib/seahorse/client/base.rb:207:in `block (2 levels) in define_operation_methods'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-snssqs-2.0.4/lib/sensu/transport/snssqs.rb:155:in `send_message'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-snssqs-2.0.4/lib/sensu/transport/snssqs.rb:138:in `block in publish'
    from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:1076:in `block in spawn_threadpool'

Maybe this was due to the Dyn DDos, I don't know but, I think it have to retry connecting continuously instead of crashing. Is there a solution available or do I have to monitor my monitoring agents processes? Maybe this is a sensu-core question too.
Thanks

Is it working now? This seemed like an issue with your DNS system, not sensu-transport-snssqs.

Hi,
I think the issue is not the temporary connectivity error but the sensu-server crashing instead of retrying.
Here an other error from yesterday:
/opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.5/lib/seahorse/client/plugins/raise_response_errors.rb:15:in `call': We encountered an internal error.
 Please try again. (Aws::SQS::Errors::InternalError)
        from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.5/lib/aws-sdk-core/plugins/param_converter.rb:20:in `call'
        from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.5/lib/seahorse/client/plugins/response_target.rb:21:in `call'
        from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.5/lib/seahorse/client/request.rb:70:in `send_request'
        from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/aws-sdk-core-2.6.5/lib/seahorse/client/base.rb:207:in `block (2 levels) in define_operation_methods'
        from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/sensu-transport-snssqs-2.0.4/lib/sensu/transport/snssqs.rb:117:in `block in acknowledge'
        from /opt/sensu/embedded/lib/ruby/gems/2.3.0/gems/eventmachine-<IP_ADDRESS>/lib/eventmachine.rb:1076:in `block in spawn_threadpool'

Do I have to post this issue in sensu-core repo?

This transport should do a similar reconnect procedure like the rabbitmq transport. I am not sure if this is implemented in the transport or core? @cwj or @portertech can you advice?


Disable memcpy() overflow warnings in C compilation

Fixes #18
This PR eliminates the warnings mentioned in #18. It uses a similar technique as was applied for other C compiler warnings in earlier commits.

Thanks for the contribution!


Can we have lottie integrated with nativescript (lottie-nativescript)

@NathanWalker

@mohammedzamakhan I'm not very familiar with exposing native views/libraries to NativeScript, but it sounds very possible. You may want to reach out specifically on the lottie-ios and lottie-android repos, but I'm happy to help in any way that I can.

Looks like someone beat you to it? :)
https://github.com/bradmartin/nativescript-lottie


Fix lab computers bug

This change is

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

Comments from Reviewable


R Host process stop: unexpected host response, Escape key after browse(), no debugger

x<-1:10
browser()
 (maybe several times...)
Trace.Fail in ProtocolError() is called.

The problem is that when CancelAllAsync is called, it immediately terminates the ongoing RunLoop via cancellation token. But if that loop was an eval loop, the eval response can already be on the way. When that happens, the eval response gets received by the top-level (non-eval) loop, which doesn't know what to do with it.
Support for async evals, which I'm implementing as part of #541, should take care of this scenario, since that change requires servicing eval responses asynchronously without tying them to any specific loop.


模型下载？

您好，能否提供 vgg16_faster_rcnn_iter_5000 的下载地址？

would you like to tell us how can we contact with you.
or please add my wechat as a friend : kiwa-tech

would you like to tell us how can we contact with you.
or please add my wechat as a friend : kiwa-tech

收费模型下载地址：https://item.taobao.com/item.htm?id=584772614657

您好，能否提供 vgg16_faster_rcnn_iter_5000 的下载地址？ @Hale-Lee

Hello, can you please offer the download address of vgg16_faster_rcnn_iter_5000?


Land Water Storage contribution to Sea Level Rise is modified to include the population

LWS is modified by fitting the data from BRICK to population

This pull request is missing any changes to the Sea Level rise module -- make sure to check the FRIDA_Modules folder for changes.
Also the model is currently using Stella v3.5.1, this commit was done with 3.4.1, please resubmit using Stella 3.5.1
When complete I expect to see that FRIDA.isdb is changes, as well as Sea_Level.itmx inside of the FRIDA_Modules folder.  I expect that there may be minimal changes in FRIDA.stmx as well.
Finally I assume you've reviewed this change with Lennart?


QUESTION: Can gitsigns and LSP diagnostic marks co-exist?

RIght now, if I have gitsigns and the default nvim-lsp, one overwrites the other if both SHOULD be on a line. Looks like the LSP overwrites the git sign for me.
Attached is a picture of it happening.

Do you know of a way where both can exist in the signcolumn for the same line?

Checkout :help 'signcolumn'

@hahuang65, how did you fix this? I tried set signcolumn=auto:4, but I still have the following:

@Shatur95 I've set the sign_priority:
require('gitsigns').setup {
  sign_priority=100
}

Which I'm not sure is actually needed for this,
and I set signcolumn=auto:4, same as you.
It could be that your signs (if you're using different plugins than me) are coded different so the auto:4 didn't do anything for you.

and I set signcolumn=auto:4, same as you.

It was a mistake on my side, it worked, thanks!

How do you make gitsign's signs align in the same column?

You can't. It's a current limitation of multi signs in Neovim. Best you can do is adjust the priorities so Gitsigns marks always appear on the left.

@lewis6991 I set it's priority to 100 (highest), but it does not change, it still appears in the rightmost

Try 0 then

@lewis6991 that might work, but depends on how many diagnostic signs, otherwise it will be overlapped.
Take an example, if :set signcolumn=auto:2, and there are two diagnostic signs, only diagnostics signs will be shown, gitsign's sign will be covered. if there is only one diagnostic sign, then gitsign's sign can be shown on the leftmost side(therefore align).

Looks like there isn't a decent solution.

Like I said, no. This is a limitation with neovim. Any solution is going to have issues.


Plugin Initialization Issue: Shutdown After First Data Transmission and Configuration Handling Problems

Describe the bug
I am encountering an issue with the initialization of the IEC104North plugin. The primary problem is that the plugin shuts down after the first data transmission. However, after a restart—or if the restart occurs before any data is sent—the plugin operates correctly.
To Reproduce
Here is the sequence of actions I followed:

Start Fledge and enable the IEC104North plugin in the script importModules.sh:

# Create service north
curl -sX POST http://localhost:8081/fledge/service -d '{"name":"'$n1_north_service_name'","type":"north","plugin":"iec104","enabled":true}'

With Fledge running, I update the plugin configuration (specifically, exchanged_data), which is recognized and processed by Fledge
I then run a test script that sends data to the south plugins. (Note: The assets do not exist before this operation.)
Upon running the test, the following error occurs for each asset:

Fledge iec104north[1493]: ERROR: iec104 - IEC104Server::send - Data point 1:6 not found or type M_ME_NC_1 (13) not expected

followed by the log message:
Fledge iec104north[1493]: INFO: iec104 - plugin_shutdown - Shutting down the plugin...

Upon deeper investigation, I found that logs from the plugin initialization, such as:
plugin.cpp
std::string beforeLog = Iec104PivotUtility::PluginName + " - plugin_init -";
Iec104PivotUtility::log_info("%s Initializing the plugin", beforeLog.c_str());

are missing. This absence of initialization logs suggests that the plugin initialization may not have been performed correctly.
The complete log is attached as a Word document, with my comments and important logs highlighted in color. Note that two filters are enabled in the IEC104North plugin pipeline: to_pivot and the standard iec104_pivot_filter - that's not a mistake.
Expected behavior
A plugin should handle its configuration properly and be ready to send data afterward.
System
Fledge 2.5.0 dockerized under Ubuntu 20.04
Fledge rsyslogd- iec104north plugin init.docx

@fledge-power/dev-equans can you take a look at this issue. Maybe the init process have been overlooked, and we might run into this bug if we send data too early ?

@Aeredren We did not experience this in out automated tests so far, but maybe this state is not reachable for us as the importModules.sh we use enforce a Fledge restart as it is mandatory for newly created control pipelines to work.
A few points of interest here :

About some logs not being displayed, this is a known behavior due to the fact that plugins will start at WARN log level by default: even if you can enable lower log levels in the plugin options, some logs that happen very early in the plugin launch process will never be displayed because the plugin configuration has not yet been read at this point. I suggested a solution to ensure that all logs can be seen even at startup for debug purposes, but it was never implemented: https://github.com/fledge-power/fledge-north-iec104/issues/56
About the issue you encountered, after the north plugin did shutdown, are you able to start it again, and is Fledge operating correctly afterward? Having something that does not work as intended, but does after a restart reminds me if this issue we raised a long time ago but was never totally solved that caused a complete hang of Fledge where it was still running but would not answer to any API call (can't seem to find back the ticket related to it sadly).

@FlorentP42 @Aeredren
I repeated my test with a simple MQTT South plugin and an IEC104 North plugin, considering two scenarios:
Scenario 1

Start Fledge 2.5.0.
Set the log level to DEBUG and enable the plugin via the UI.
Configure the North plugin and the exchanged_data and protocol_stack filters using the REST API.
Send data to the South plugin for the first time—this creates a new asset that should be forwarded to IEC104.
Wait 1 minute and trigger a data change.

Upon analyzing the logs, I noticed that after the configuration was changed via the REST API, the plugin_shutdown function was not triggered. Instead, it was only triggered when the South plugin received the first set of data.
Scenario 1 logs.docx
Scenario 2

Start Fledge 2.5.0.
Send data to the South plugin for the first time—this creates a new asset.
Set the log level to DEBUG and enable the plugin via the UI.
Configure the North plugin and the exchanged_data and protocol_stack filters using the REST API.
Wait 1 minute and trigger a data change.

In this scenario, after the configuration change in step 4, the plugin_shutdown function was triggered, and the data received in step 5 was forwarded correctly.
Scenario 2 logs.docx
Key Observations

The only difference between Scenario 1 and Scenario 2 is that, in Scenario 2, the South plugin had already received data and created an asset before configuring the North plugin.
In Scenario 2, after enabling the plugin from the UI, the North plugin attempted to forward previously received data stored in the asset. However, before the exchanged_data was configured, the following error was logged:
'...Asset 'dev00000' not found in exchangedData'.

Final Conclusion
If the IEC104 North plugin is configured before any data is received by Fledge, the plugin is not restarted, which causes issues with forwarding the first data set. The root cause of this behavior is currently unknown.
Workaround
To avoid this issue, ensure that data has already been received by Fledge before configuring the North plugin, or trigger a Fledge restart via the REST API after configuration.


Removing the tests.

We have training site now which is more appropriate than this.
Signed-off-by: Mary Anthony<EMAIL_ADDRESS>

ping @docker/docs-owners

@moxiegirl the test scared me to death :scream_cat: :stuck_out_tongue_closed_eyes:
Anyway, I do agree (even though I'm no docs-owners :cat:).

@vdemeester see we were scaring people! Not good.

ping @thaJeztah @SvenDowideit

LGTM
@moxiegirl If we still want interactive tutorials, perhaps this is nice; http://www.katacoda.com (docker tutorials here: http://www.katacoda.com/courses/docker), created by one of our contributors, @BenHall


Add missing update field to onStoreDocumentPayload

Noticed that update was missing from the onStoreDocumentPayload interface.
The documentation regarding the payload states that the update should be a part of the payload:
https://github.com/ueberdosis/hocuspocus/blob/main/docs/api/hooks/on-store-document.md
We can also see that the update is included in the payload from handleDocumentUpdate
https://github.com/ueberdosis/hocuspocus/blob/main/packages/server/src/Hocuspocus.ts#L530-L555

hey @daniel-johnsson, thanks for this!
This is a bit dangerous, as the onStoreDocument hook actually can be triggered once for multiple updates because it's denounced, so I actually was already thinking to remove it completely from the payload.
Need to think about this..

Hi @janthurau , I thought this was the solution to my problem, however as you say the update will trick you. I think it should be removed completely from the onStoreDocument, would be cool though if it would be possible to pass to merge all debounced updates or pass all in an array. This looks tricky to achieve tough.
Some context why I wanted the update:
I noticed that onStoreDocument where triggered if all connections to a document were closed. I have not found the root of this, but I figure (correct me if I am wrong) it's some safe keep to store the debounced changes. This would also trigger even if no changes to the document had been made. To prevent unnecessary stores I started to check if the update was defined. This ended up not working since per the issue you point out, this onStoreDocument call when all disconnect would always have an undefined update. Ended up scarping the idea of using the update and just added the last change time to document.meta that I compare to the db. This works but feels like it could be some race condition issues in the future.


drivers: adc: stm32: dma support

The STM32 ADC already supports sampling multiple channels in one sequence. This nwo PR allows those channels to be read in one go using the DMA.
Support for multiple channel sampling for the STM32 was originally part of this PR, but split off in #53534.
Currently dependent on #54156 for a final check
Notes:

Currently only tested with STM32H743zi. With only this PR only ADC1 is supported. This PR #53184 enables the bdma which will add support for running ADC3 through DMA as well.
This PR is porting ADC DMA support from a Zephyr 2.6 fork, which has been running on many devices for combined hundreds of hours with the MCUs under heavy load.
Does not support DMA driven continious sampling, and is considered out-of-scope for this PR because it can already be mimicked with ADC_ACTION_REPEAT. Adding continous sampling will require changes to adc_context, which has an open discussion here: https://github.com/zephyrproject-rtos/zephyr/discussions/48478

@heinwessels Thanks for your work on this feature which has been requested since a long time by numerous users.
In order to help the review process, please split this PR in few commits, at least:

One commit dedicated to the sample changes
One commit dedicated to the changes that impacts the driver when CONFIG_ADC_STM32_DMA is not enabled
One commit for the pure driver DMA related changes

Also, one general comment the solution:
Generally, on other DMA enabled STM32 devices, DMA is enabled based on the presence of DMA properties on the node (coupled to an FOO_ASYNC Kconfig driver symbol if provided by the API). For consistency, it would be great to add that as well.
This is not blocking though, it can be added later on.

@erwango

In order to help the review process, please split this PR in few commits, at least:

Done. Please let me know if you had something different in mind.

Also, one general comment the solution: Generally, on other DMA enabled STM32 devices, DMA is enabled based on the presence of DMA properties on the node (coupled to an FOO_ASYNC Kconfig driver symbol if provided by the API). For consistency, it would be great to add that as well. This is not blocking though, it can be added later on.

I would prefer to keep it as-is for now, but if it's really required I can work it in.

@erwango  @FRASTM
This PR is ready for review again now that multiple-channel-sampling is supported.
I also added unit tests for the ADC DMA driver.

Adding NXP maintainers for the NXP boards related change

did you also check for stm32 mcu without dmamux ?

No, but from the ADC drivers point of view there should be no difference between using a DMA and DMAMUX. I will remove accidental  dependency of ADC_STM32_DMA on DT_HAS_ST_STM32_DMAMUX_ENABLED. It should depend on STM32_DMA.
That said, I haven't tested running the ADC driver through dma1 (and not dmamux1) because it doesn't compile IIRC, even on main.

@heinwessels Could you please rebase this PR? There is a conflict now that #54038 has been merged.

Rebased with the recent driver changes.

could you detail the reason for adding the section .ld ? else LGTM

I initially thought that dma1 only had access to SRAM1, but realized that this is not the case. So I removed this change.

Not explicitly, but from the ADC drivers point of view there should be no difference between using a DMA and DMAMUX. I will remove accidental dependency of ADC_STM32_DMA on DT_HAS_ST_STM32_DMAMUX_ENABLED. It should depend on STM32_DMA.

I removed these dependencies because enabling ADC_STM32_DMA should do a select DMA. It cannot be dependent on DMA as well.
Finally, the check to see if the buffer is correctly aligned was also broken. It was checking for alignment for uint32_t (32 bits) and not 32 bytes. I fixed this, but this is now dependent on a split-off PR #54156. Depending on the outcome of that PR I will re-enable this check or remove it.

Finally, the check to see if the buffer is correctly aligned was also broken. It was checking for alignment for uint32_t (32 bits) and not 32 bytes. I fixed this, but this is now dependent on a split-off PR #54156. Depending on the outcome of that PR I will re-enable this check or remove it.

Updated the code because the mentioned PR was merged.

I added a commit to fix the adc_dma tests because it didn't verify that the sampled buffer is actually correct. It does this by placing a known value in the buffer beforehand, and then afterwards verifies the expected slots were overwritten.
This also led to a fix in the stm32 driver where the cache needs to be be clean before a read sequence to ensure that when the cache is invalidated in the callback no data is lost.

I added an addtional commit to remove CONFIG_TEST_USERSPACE from the adc_dma tests, because I don't think it's compatible with having buffers in memory which is not defined by ZTEST_BMEM. And it doesn't seem required either.

DNM until @FRASTM could have a chance to review (probably today)


.gitconfig is owned by root

The created .gitconfig is owned by root when it should be owned by the local user.

I cannot reproduce this issue here with puppet-git 2.7.6:
$ ls -al ~/.gitconfig
-rw-r--r--  1 sebroeder  staff  231 Apr  3 23:42 .gitconfig

Thanks @sebroeder, going to close this one.


Define audio / DSP algorithms

Check out CSound documentation ... it may be as simple as copying their UGENs

Candidates in no particular order:

multi-operator FM
additive
wavetable / samples
physical model
virtual analog: "virtual east coast" or "virtual west coast"
granular / other miscellaneous
"errant"

I'm learning towards a collection of physical modeling / additive and errant. Additive is the simplest for spectral music.

Probably need to code and profile wavetable first.

Overview is done - will define details on a composition-by-composition basis


Bump base python image

Description
Changes proposed in this pull request:

Bump base python image to alpine 3.19

Related issue(s)

/etest

/retest

/retest


updates baza.rb to intorduce decompression feature for pull.

fixes #84
Just update as the majority of work was done within https://github.com/zerocracy/baza.rb/issues/12

@yegor256, please take a look

@rultor release, tag is 0.26.0

@rultor release, tag is 0.26.0

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.26.0

@yegor256 Done! FYI, the full log is here (took me 23min)

@tank-bohr Thank you for your contribution! We appreciate your effort, but there are areas for improvement. You've earned +4 points: +16 base, -16 for no code review, -4 for insufficient comments (1), and -8 for low hits-of-code (2). We encourage you to focus on quality and engage in code reviews for future contributions. Your current balance is +116. Keep up the good work and aim for more comprehensive submissions!


Add persistent volumes, PV claims and storage classes to tree view

First cut of an update for storage-related resource types - it just adds them to the tree view with the same set of verbs as other resources.  Should there be other/different operations, and are any other resource types required?
Fixes #338.

cc @nbarnum (trusting you're the same person who left the review asking for these, and that you don't mind being tagged in on this)


devsite 3 content | Review Flutter SDK documentation

lead: @XavierChanth

[ ] Review the present codelab
[ ] Evaluate the content for gaps

[ ] ensure full at_commons coverage
[ ] Notify content
[ ] Best practices / tips & tricks (at_utils content)
[ ] Tyler & Xavier's "pizza mental model"

[ ] Create missing content

PR39: Begin organizing & reviewing content with the dev team in some working sessions.

@XavierChanth is this still an active ticket or do you have others opened now?  Unsure if this is a placeholder for future work or already underway.  TY!

This is a placeholder for future work


Rotated map jumps when dragging around

When a map is rotated (this happens especially with angles like 45°) the dragging movement isn't smooth but map jumps around.
Currently testing with rotation in MapController.

closing because https://github.com/johnpryan/flutter_map/issues/361 has been reopened


-h flag

display readme.md

better to create and display man page

#11 added man page

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
JaimeeNye, @mb8z, @Buanderie, @blakemccawe, @krmadala, @yyt0702, @maxclchen, @pari, @zhems, @bcbwatt, @garvingit, @hirawatt, @jo-ym, @Jack-FinancialMarket, @GivyBoy, @ZnO314, @BenmoussaZakaria, @surjitr, @sheamunny, @uysalibov

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
riggaroo, @moldabekov, @zhengyangfeng00, @popra, @gurgelff, @rkirmizi, @nbontempo, @kensai7, @gato-n0ir, @pkmr06, @inphomercial, @jakubzitny, @zackzackzackzack, @kaifeichen, @hyl910401, @amitport, @randxie, @thunderdrum, @kyofight, @mprince


Request: remove warning log of EncryptedSharedPreferences :"keyset not found, will generate a new one"

I was told to create a request about this here:
https://issuetracker.google.com/issues/185219606

Yes I also facing the same issue
You can check logs here.
2022-08-02 10:52:12.016 25975-25975/com.akaita.encryptedsharedpreferences I/AndroidKeysetManager: keyset not found, will generate a new one
    java.io.FileNotFoundException: can't read keyset; the pref value __androidx_security_crypto_encrypted_prefs_value_keyset__ does not exist
        at com.google.crypto.tink.integration.android.SharedPrefKeysetReader.readPref(SharedPrefKeysetReader.java:71)
        at com.google.crypto.tink.integration.android.SharedPrefKeysetReader.readEncrypted(SharedPrefKeysetReader.java:89)
        at com.google.crypto.tink.KeysetHandle.read(KeysetHandle.java:116)
        at com.google.crypto.tink.integration.android.AndroidKeysetManager$Builder.read(AndroidKeysetManager.java:311)
        at com.google.crypto.tink.integration.android.AndroidKeysetManager$Builder.readOrGenerateNewKeyset(AndroidKeysetManager.java:287)
        at com.google.crypto.tink.integration.android.AndroidKeysetManager$Builder.build(AndroidKeysetManager.java:238)
        at androidx.security.crypto.EncryptedSharedPreferences.create(EncryptedSharedPreferences.java:160)
        at androidx.security.crypto.EncryptedSharedPreferences.create(EncryptedSharedPreferences.java:120)

Yes it was removed recently.
Sadly not sure about the rare exceptions , though

I changed my mind. I think this log message is more confusing than helpful. Let's remove it completely.

@juergw Wasn't it removed? Please check.

I think it will still log by default, according to what https://developer.android.com/reference/android/util/Log.html#isLoggable(java.lang.String, int) says. So I will change it to "verbose", so the logging is turned off by default, and the user can still turn it on if they want to.

@juergw Please check on latest version.

Yes, the lastest version of jetpack (https://developer.android.com/jetpack/androidx/releases/security#1.1.0-alpha04) says that the log message was removed, and references b/185219606. Which is marked as fixed. But I don't see what was changed.

I've now changed the logging to only log in verbose mode, https://github.com/google/tink/commit/cb67a3a9e3acce588cb00f7b2da384be1d48290a.


blobs: add script and update repository

@uLipe @glaubermaroto PTAL again. This PR is the same as before but now to be merged to hal_v4.4.1.


Use Ember-idx-tree in Ember 2.9.0

Hi, Im trying to use the addon in lastest Ember. It wont render any children and doesnt give me any Errors. Do anybody have a solution? Thank you

Maybe try https://github.com/systembugtj/ember-tree-view this version seems abandoned.

@knownasilya done, awesome :)


Add zero vpmem (no gpu) test case

Add a non gpu zero vpmem test case to test lcow scsi layer additions.

Signed-off-by: Daniel Canter<EMAIL_ADDRESS>

In relation to the bug that this pr (https://github.com/microsoft/hcsshim/pull/793) fixes which was introduced with the resource cleanup changes.


duplicate data_names for every data source

I'm having an issue in my environment where every data source is duplicated in the "Data Sources Availability Tracking" page. I was originally running 1.1.11 and now I'm running 1.1.16 which is having the same issue.
What appears to be happening is that when I run the reset collection mechanism, it will compile the list correctly once, and then after a few minutes it will append and update the second data_name.
I haven't tried uninstalling and reinstalling the app, or clearing the collections manually. I was wondering if there was a simpler fix or if this was a known issue. I'm happy to provide screenshots and more troubleshooting I have done over Slack.
Below is a snippet for just one index/sourcetype filter. That date of 6/24 14:44 on the bottom row is around when I reset the collection.

Hi @ankitjain-splunk
Right this technically should not be happening anymore since Version 1.2.x but I will double check if there is something to be improved and better protected when one resets the collection.
Since version 1.2.x records are managed by their internal _key via insert / update rather than full flush like it used to be.
To fix your immediate issue you can do:
| inputlookup trackme_data_source_monitoring | eval _time=data_tracker_runtime  | stats latest(*) as "*" by data_name | outputlookup trackme_data_source_monitoring
And the same can be done for hosts too if same issue happened:
| inputlookup trackme_host_monitoring | eval _time=data_tracker_runtime  | stats latest(*) as "*" by data_host | outputlookup trackme_host_monitoring
Let me know if this fixes your issue.
Guilhem

Thank you for the quick reply. That search was able to repair the issue and I'm going to let it sit to see if it's resilient overnight. Interestingly, this issue didn't seem to happen for hosts.
I haven't updated to 1.2.x yet because I'm a little hesitant to use summary indexing in our environment in the near-term. Right now I'm trying to demonstrate to my customer that this solution will meet their goals, which I'm sure it will :)
Great work on this app. I appreciate all the hard work that went into it.

Thanks @ankitjain-splunk ;-)
Good, if an issue would happen it would happen quite quickly between the short term tracker execution (every 5 min) and the long term (once per hour) but this shouldn't be the case.
No problem, the version 1.2.x is behaving better than 1.0.x and faster, with shorter run time of the trackers and of course many things improved and fixed obviously.
Efforts have been achieved to support better very high scale environment but it's up to you no problem, I would suggest to create now the indexes required for the 1.2.x such that you can update smoothly when you wish to so do.
Gulhem

I assume we can close this issue @ankitjain-splunk
Let me know otherwise.
Guilhem


SIL: support non-clang compilers again

The toolchain has traditionally been buildable with clang, cl (MSVC),
and gcc.  __has_feature is a clang-specific directive, ensure that we
are portable to other compilers by providing a definition of the macro
incase it is not available (which also includes older clang releases).

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @eeckstein

@swift-ci please test


FlareSystemsFirework: create 1.0.0 solution

Remove empty variables in Connector_REST_API_FlareSystemsFirework.json which caused solution validation errors
Create the first 1.0.0 solution and add it to the Package folder

cc @elforb
This creates the first version of our solution!

@elforb
I think that most of your comments were fixed by switching to Powershell 7.1+ to generate the solution.

Remove Unused Parameters formattedTimeNow

Looks like its now used in the workbook display name

Remove Unused Variables workbook-source _workbook-source

Looks like its now used by the workbook.

Add location property to data connector resource "location": "[parameters('workspace-location')]",

I had to add that one manually. Maybe the solution creation script should have done it?

Remove Workbook Tab, since no workbook is included

This was a bug, the workbook is now included.

@aviau Thanks for fixing, the solution is passing validation and deployable now.
Could you also provide the Publisher ID for your solution? You can find it on your Marketplace offering, under the "Usage Information + Support" tab.
Ex.

@elforb
Here you go: flaresystmesinc1617114736428.
We tried updating the zip of our sumissions with the fixes that you have recommended but we got the following message:

You have an in-progress submission. You can't publish until the in-progress submission has been published.

Not sure what to do here. Should this be 1.0.1? Or can you just replace the content of whatever we uploaded on the store to the 1.0.0 that is now in this PR?

@aviau
Regarding the issue with in-progress submission, did you happen to click go-live already? Either way you should be able to click "Cancel Publish" and the offer will shortly allow you to update as necessary and publish.

@elforb
Ahhhh, got it! Thanks! I canceled the publish, edited the zip, and published again!
The package is back to the "Certification" step:


Workspace - Inviting a member to the workspace, when re-entering the email of the previous member, pressing "Enter" will delete the previously invited members

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any workspace -> go to invite members
Input email -> select many members to invite
After selecting some member's email account -> re-entering the previously selected email
The previously selected email will appear highlight -> Pressing the "Enter" key

Expected Result:
Invite members to be normal, if delete the character and retype, Enter again, it will not be deleted
Actual Result:
It will delete previously selected members
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.66-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/92b3cdf2-82f2-444d-b385-cd49cb4f49c1
https://github.com/Expensify/App/assets/115492554/e82245ab-1836-4c0a-91ea-8013fd63cc2b
Expensify/Expensify Issue URL:
Issue reported by: @Le Thi Thu Thuy
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693316843292169
View all open jobs on GitHub

Asked for clarification in the Slack thread.

Proposal
Please re-state the problem that we are trying to solve in this issue.
When we press enter while searching, it sometimes remove already selected users
What is the root cause of that problem?
Actually the problem happens whenever we have already selected user that are focused in the list, that happens whenever the search don't find any unselected user that match the search.
In WorkspaceInvitePage we are toggling the option when the row is selected here:
https://github.com/Expensify/App/blob/95c9e4743f44ca42ece2c6ac56259b911d5feafc/src/pages/workspace/WorkspaceInvitePage.js#L227
The row is selected when we press enter so we toggle the option, for our case it means we remove them from the selected users
What changes do you think we should make in order to solve the problem?
There is many ways to resolve this but I think one of the best way is to not focus automatically the selected options. Right now the focused index is changed to 0 in ArrowKeyFocusManager here when the focused index is superior to the length of the list.
I propose that in WorkspaceInvitePage here: https://github.com/Expensify/App/blob/95c9e4743f44ca42ece2c6ac56259b911d5feafc/src/pages/workspace/WorkspaceInvitePage.js#L220-L231 we pass a new parameter selectedOptionsAtTheTop (the number of selected options) to SelectionList that will pass it to ArrowKeyFocusManager, , instead of setting the focusedIndex to 0 it will put it to selectedOptionsAtTheTop.
We can also use that parameter here instead of testing the number of sections that can change when we filter
https://github.com/Expensify/App/blob/95c9e4743f44ca42ece2c6ac56259b911d5feafc/src/components/SelectionList/BaseSelectionList.js#L173-L186
What alternative solutions did you explore? (Optional)

Clarified in the Slack post, I think this is expected behavior.

I think that's expected behavior that we would select the member that you searched for. I'm going to close the issue for now.

Currently we are not highlighting the member that the user searched, we are highlighting the first selected member even if it has nothing to do with what the user is searching. When we are not searching we avoid highlighting the already selected users, I think we should do the same when we are searching


[CHALLENGE SUBMISSION]

Please provide the following information for your submission:
What is your name? (First, Last)
Giorgio Lasala
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/salem84/AzureEats-Website
Public site URL is https://azchallenge-1-app-service.azurewebsites.net
What Challenge is this for? (Challenge number between 1 and 5)
1
(Optional) Anything else we should know? e.g., language used, location, blog post?
I have created a simple Terraform script that creates app-service-plan and app-service (free tier hasn't enough space). In this version remote state is not handled (not requested), so pipeline fails the second time
Moreover I have created a CI/CD pipeline GitHub Actions composed of two jobs:

terraform
build and deploy (from existing pipeline with some fix)

I have always used Terraform with CLI or Azure DevOps (with custom tasks) so I have played this video https://www.youtube.com/watch?v=UEXq5qtM3_I for some suggestion, but it use obsolete actions.
Location: Rome, Italy 🇮🇹

Thanks for participating in the #TerraformOnAzure coding challenges!
We have attached your very special Astronaut Badger background, for you to use in all your upcoming video calls!
And to recognize you for your learning, you can collect your digital Azure Heroes badge on your mobile (you may need to install the Enjin wallet to collect it). Make sure to collect it today!
https://beam.enjin.io/claim/d32599695c8c28cfc24820492080fac0
Keep on learning and sharing!
Greetings from the #TerraformOnAzure team,
Suzanne, Floor, Erik & Nick


feat(sql): support third party parameters in url

Hi,
I'm using the Spring Cloud GCP SQL to configure my app with a CloudSQL Postgresql database. But, I need to use a specific schema.
This need is linked to a limitation of Spring-Batch which will create its metadata-table inside the public schema by default and can't be overridden.
So, one solution is to add a parameter in the JDBC url to add currentSchema=mycustomschema. This leads to a string like this in case of CloudSQL for PostgreSQL:
url:url: jdbc:postgresql://google/dbname?cloudSqlInstance=my-project-id:zone:instance-name&socketFactory=com.google.cloud.sql.postgres.SocketFactory&currentSchema=mycustomschema

I've looked into the source code of the autoconfigure part and I think, for now, this can't be done with Spring Cloud GCP => https://github.com/spring-cloud/spring-cloud-gcp/blob/master/spring-cloud-gcp-autoconfigure/src/main/java/org/springframework/cloud/gcp/autoconfigure/sql/DefaultCloudSqlJdbcInfoProvider.java
For now, I choose to use the url of the datasource and not relying on the autoconfiguration, but I would like to fit best into Spring Cloud GCP logic. What is your opinion about this ?
Then, I would like to do a PR about this to allow custom parameters. Is it a good idea from your point of view?

I like the idea of supporting configurable properties; this will likely need to be done in DatabaseType.
For your immediate problem of reusing database URL creation logic while still passing the extra schema parameter, you could provide a CloudSqlJdbcInfoProvider bean in your own configuration as an extension of DefaultCloudSqlJdbcInfoProvider that calls super.getJdbcUrl() to get the base and then appends the extra parameter. This will suppress the autoconfigured plain DefaultCloudSqlJdbcInfoProvider  and use your composite URL when autoconfiguring DataSourceProperties.

Re-open if the answer is not satisfactory.


Copy functionality not working properly in chrome.

Describe the bug
Copy functionality of GlycoCT sequence does not propelry in all browsers, specifically chrome.
/GlycoGlyphPublic/src/modules/copyTextFromElement.js
/GlycoGlyphPublic/public/js/glycoglyph.js
copyText() function should return promise object and copyTextFromElement should wait on the object. I have added modified code below,
//If you want to copyText from Element
function copyTextFromElement(elementID) {
let element = document.getElementById(elementID); //select the element
let elementText = element.innerText; //get the text content from the element

if (element.tagName == 'INPUT' ) {
  elementText = element.value;
}

elementText = elementText.trim();

if (elementText != '') {
  //use the copyText function below
  copyText(elementText).then(() => {
    alert('Copied: \n' + elementText);
  })
  .catch(() => {
    alert('Could not copy text.');
  });
}else {
  alert('Nothing to copy.');
}

}
//If you only want to put some Text in the Clipboard just use this function
// and pass the string to copied as the argument.
function copyText(text) {
return navigator.clipboard.writeText(text);
}

Hi @sujeetvkulkarni. I cannot reproduce the error in chrome.
Example: https://glycotoolkit.com/Tools/GlycoGlyph/

Hi @akulmehta copy pop-up comes but if you try to paste the copied GlycoCT string on text editor it was not working.

Sorry - can't reproduce yet. It copies it fine for me. I wonder if this is OS related - I am on Windows 10.

Maybe I am on macOS Monterey Version 12.1 and Chrome Version 100.0.4896.75
(Official Build) (x86_64).
On Thu, Apr 7, 2022 at 1:36 PM Akul Mehta @.***> wrote:

Sorry - can't reproduce yet. It copies it fine for me. I wonder if this is
OS related - I am on Windows 10.
—
Reply to this email directly, view it on GitHub
https://github.com/akulmehta/GlycoGlyphPublic/issues/35#issuecomment-1092015842,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJ7PGXZRAMH27E5VTZCMNTVD4MKHANCNFSM5R3TT6UA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Does the code you proposed fix this for you?

Yes, navigator.clipboard.writeText(text); function returns a promise object
and we should handle it with then construct before proceeding. That's what
the proposed code does.
On Thu, Apr 7, 2022 at 1:45 PM Akul Mehta @.***> wrote:

Does the code you proposed fix this for you?
—
Reply to this email directly, view it on GitHub
https://github.com/akulmehta/GlycoGlyphPublic/issues/35#issuecomment-1092023293,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJ7PGWHQ5OVDKHYQADGBMDVD4NLDANCNFSM5R3TT6UA
.
You are receiving this because you were mentioned.Message ID:
@.***>


using custom dashboard doesn't work

I get the following error when I try to change the dashboard
{ SyntaxError: Octal literal in strict mode (2:54) in C:\Users\Pavilian i5\Documents\1.Freelancer\Fiver Projects React\fork\testing\quora\backend.adminbro.entry.js
...
pos: 83,
  loc:
   { file:
      'C:\\Users\\Pavilian i5\\Documents\\1.Freelancer\\Fiver Projects React\\fork\\testing\\quora\\backend\\.adminbro\\.entry.js',
     line: 2,
     column: 54 },
  raisedAt: 85,
  frame:
   '1: AdminBro.UserComponents = {}\n2: import Component1 from \'C:\\Users\\Pavilian i5\\Documents\\1.Freelancer\\Fiver Projects React\\fork\\testing\\quora\\backend\\config\\adminDashboard\'\n                                                         ^\n3: AdminBro.UserComponents.Component1 = Component1',
  id:
   'C:\\Users\\Pavilian i5\\Documents\\1.Freelancer\\Fiver Projects React\\fork\\testing\\quora\\backend\\.adminbro\\.entry.js',
  hook: 'transform',
  code: 'PLUGIN_ERROR',
  plugin: 'commonjs' }

It is probably related to windows issue we have with custom components #136. Can you paste the content of your .adminbro\.entry.js file?

AdminBro.UserComponents = {}
import Component1 from 'C:\\Users\\Pavilian i5\Documents\1.work\Projects React\fork\testing\questions\backend\config\adminDashboard'
AdminBro.UserComponents.Component1 = Component1

yes - that is related to windows. I will try to fix this by passing relative paths instead of absolute. Hopefully, it will help. But this will happen end of next week.

Have you resolved this yet I think it's past a week

yes - that is related to windows. I will try to fix this by passing relative paths instead of absolute. Hopefully, it will help. But this will happen end of next week.

I've just changed paths to relative - can you try out the 1.1.5-beta.2 version and let me know if that helped

it duplicates #136

it duplicates #136

This is the output of my hidden adminbro file
AdminBro.UserComponents = {} import Component1 from '..\routes\my-dashboard-component' AdminBro.UserComponents.Component1 = Component1
This is the error that I'm getting or rather output
outesmy-dashboard-component' is imported by .adminbro\.entry.js, but could not be resolved – treating it as an external dependency outesmy-dashboard-component' in output.globals – guessing 'Component1'
This is how I'm importing the component
 dashboard: {         component: AdminBro.require('./my-dashboard-component')     }
what I'm i doing wrong?

This is the output of my hidden adminbro file
AdminBro.UserComponents = {} import Component1 from '..\routes\my-dashboard-component' AdminBro.UserComponents.Component1 = Component1
This is the error that I'm getting or rather output
outesmy-dashboard-component' is imported by .adminbro.entry.js, but could not be resolved – treating it as an external dependency outesmy-dashboard-component' in output.globals – guessing 'Component1'
This is how I'm importing the component
dashboard: { component: AdminBro.require('./my-dashboard-component') }
what I'm i doing wrong?

same error ;
Is there any known solution?


Peak connection in mysql logs incorrect

Rather strange issue!
I have about 20 connections online according to the API, but according to the mysql logs I have 180 peak connections!
Any ideas?
Thanks in advance and for the great package.

The MySQL peak connections have nothing to do with the peak connections that this package store.

@lovetoast The package version you're using? We have fixed some memory leaks in 2.x (beta for now): https://github.com/beyondcode/laravel-websockets/pull/475

Ah right, I'll check this and revert back, it could also be a quick in how window.load works but I'll let you know as it may help others :)

@rennokki
Hi, as promised, I've been monitoring, using version 1.4.1. We use laravel websockets in document.ready, and there does seem to be an issue with multiple connections made from the same client. I don't think this is a memory leak, but I can see one person, with just 1 browser and 1 tab open and they have 54 connections, as mentioned, using pusher.js.
I'm not sure if an upgrade would fix this?


Add date format to support offset in nuget analyser

Description
Nuget Analyzer has list of two supported SimpleDateFormat which are allowed for parsing the dates being received from the repository, based on limited test data.
Now, as seen in logs, below date format is also received from the nugget repo. This date has offset dateTime and needs to be added to the list of supported formats in order to avoid the ParseException.
Date example: 1900-01-01T00:00:00+00:00
Format needed: yyyy-MM-dd'T'HH:mm:ss
Addressed Issue
Closes https://github.com/DependencyTrack/hyades/issues/1263
Checklist

[x] I have read and understand the contributing guidelines
[x] This PR fixes a defect, and I have provided tests to verify that the fix is effective
[ ] This PR implements an enhancement, and I have provided tests to verify that it works as intended
[ ] This PR introduces changes to the database model, and I have updated the migration changelog accordingly
[ ] This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

Thanks @sahibamittal!
It seems that DT v4.x has the same issue. Would you be interested in submitting a PR for that, too?

Yes, I'll raise it 👍🏼


413 Payload size too large

Summary
I'm using Kong helm chart. It's working well except when I try to upload a file of size greater than 8.5 MB. I tried increasing the client body size in Nginx config to client_max_body_size 300m;, but the problem doesn't go away. Tried even disabling it with client_max_body_size 0;, but the isssue still there. Any upload of large file from 8.5 MB fails with the 413 payload size too large

Are you using a custom Nginx template?

@bungle I'm not using a custom Nginx template. I only injected nginx some nginx settings e.g client_max_body_size. I think it's Kong because when I hit the upload endpoint directly without proxying via Kong, I can upload even 50 MB. Via Kong I can't upload even just 8.5mb. I can upload anything less.

I just tried on my machine, and could not reproduce.
$ cat a.conf
client_max_body_size=50m
$ ./bin/kong start -c a.conf
Kong started
$ du -h keycloak-8.0.2.zip
228M	keycloak-8.0.2.zip
$ http :8000<EMAIL_ADDRESS>-f
HTTP/1.1 413 Request Entity Too Large
Connection: close
Content-Length: 18
Content-Type: text/plain; charset=utf-8
Date: Thu, 27 Feb 2020 15:27:02 GMT
Server: kong/2.0.0
X-Kong-Response-Latency: 0

Payload too large
$ echo client_max_body_size=500m > a.conf
$ cat a.conf
client_max_body_size=500m
$ ./bin/kong stop
Kong stopped
$ ./bin/kong start -c a.conf
Kong started
$ http :8000<EMAIL_ADDRESS>-f
HTTP/1.1 404 Not Found
Connection: keep-alive
Content-Length: 48
Content-Type: application/json; charset=utf-8
Date: Thu, 27 Feb 2020 15:28:53 GMT
Server: kong/2.0.0
X-Kong-Response-Latency: 0

{
    "message": "no Route matched with those values"
}
´´´

What version are you running?

Also can you show us full example with all the headers visible?

Is there another Nginx proxy that's sitting in-front of Kong or are you hitting Kong directly?

I'm not using a custom Nginx template. The current Nginx config is as shown below:
charset UTF-8;

error_log syslog:server=kong-hf.konghq.com:61828 error;

error_log /dev/stderr notice;

client_max_body_size 0;
proxy_ssl_server_name on;
underscores_in_headers on;

lua_package_path '/opt/?.lua;;;;';
lua_package_cpath ';;';
lua_socket_pool_size 30;
lua_max_running_timers 4096;
lua_max_pending_timers 16384;
lua_shared_dict kong                5m;
lua_shared_dict kong_db_cache       128m;
lua_shared_dict kong_db_cache_miss   12m;
lua_shared_dict kong_locks          8m;
lua_shared_dict kong_process_events 5m;
lua_shared_dict kong_cluster_events 5m;
lua_shared_dict kong_healthchecks   5m;
lua_shared_dict kong_rate_limiting_counters 12m;
lua_socket_log_errors off;
lua_ssl_verify_depth 1;

# injected nginx_http_* directives
ssl_protocols TLSv1.1 TLSv1.2 TLSv1.3;
include /kong/servers.conf;
lua_shared_dict prometheus_metrics 5m;

init_by_lua_block {
    Kong = require 'kong'
    Kong.init()
}

init_worker_by_lua_block {
    Kong.init_worker()
}

upstream kong_upstream {
    server <IP_ADDRESS>;
    balancer_by_lua_block {
        Kong.balancer()
    }

# injected nginx_http_upstream_* directives
    keepalive_timeout 60s;
    keepalive_requests 100;
    keepalive 60;
}

server {
    server_name kong;
    listen <IP_ADDRESS>:8000;
    listen <IP_ADDRESS>:8443 ssl;
    error_page 400 404 408 411 412 413 414 417 494 /kong_error_handler;
    error_page 500 502 503 504 /kong_error_handler;

    access_log /dev/stdout;
    error_log /dev/stderr notice;

    client_body_buffer_size 300m;

    ssl_certificate /usr/local/kong/ssl/kong-default.crt;
    ssl_certificate_key /usr/local/kong/ssl/kong-default.key;
    ssl_certificate_by_lua_block {
        Kong.ssl_certificate()
    }

    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;
    ssl_prefer_server_ciphers on;
    real_ip_header     X-Real-IP;
    real_ip_recursive  off;

    # injected nginx_proxy_* directives
    client_max_body_size 0;
    send_timeout 600s;

    rewrite_by_lua_block {
        Kong.rewrite()
    }

    access_by_lua_block {
        Kong.access()
    }

    header_filter_by_lua_block {
        Kong.header_filter()
    }

    body_filter_by_lua_block {
        Kong.body_filter()
    }

    log_by_lua_block {
        Kong.log()
    }

    location / {
        default_type                     '';

        set $ctx_ref                     '';
        set $upstream_te                 '';
        set $upstream_host               '';
        set $upstream_upgrade            '';
        set $upstream_connection         '';
        set $upstream_scheme             '';
        set $upstream_uri                '';
        set $upstream_x_forwarded_for    '';
        set $upstream_x_forwarded_proto  '';
        set $upstream_x_forwarded_host   '';
        set $upstream_x_forwarded_port   '';
        set $kong_proxy_mode             'http';

        proxy_http_version 1.1;
        proxy_set_header   TE                $upstream_te;
        proxy_set_header   Host              $upstream_host;
        proxy_set_header   Upgrade           $upstream_upgrade;
        proxy_set_header   Connection        $upstream_connection;
        proxy_set_header   X-Forwarded-For   $upstream_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto $upstream_x_forwarded_proto;
        proxy_set_header   X-Forwarded-Host  $upstream_x_forwarded_host;
        proxy_set_header   X-Forwarded-Port  $upstream_x_forwarded_port;
        proxy_set_header   X-Real-IP         $remote_addr;
        proxy_pass_header  Server;
        proxy_pass_header  Date;
        proxy_ssl_name     $upstream_host;
        proxy_pass         $upstream_scheme://kong_upstream$upstream_uri;
    }

    location @grpc {
        internal;

        set $kong_proxy_mode       'grpc';
        grpc_pass grpc://kong_upstream;
    }

    location @grpcs {
        internal;

        set $kong_proxy_mode       'grpcs';
        grpc_pass grpcs://kong_upstream;
    }

    location = /kong_error_handler {
        internal;
        uninitialized_variable_warn off;

        rewrite_by_lua_block {;}

        access_by_lua_block {;}

        content_by_lua_block {
            Kong.handle_error()
        }
    }
}

server {
    server_name kong_admin;
    listen <IP_ADDRESS>:8444 ssl;

    access_log /dev/stdout;
    error_log /dev/stderr notice;

    client_max_body_size 10m;
    client_body_buffer_size 10m;

    ssl_certificate /usr/local/kong/ssl/admin-kong-default.crt;
    ssl_certificate_key /usr/local/kong/ssl/admin-kong-default.key;

    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;
    ssl_prefer_server_ciphers on;

    location / {
        default_type application/json;
        content_by_lua_block {
            Kong.serve_admin_api()
        }
    }

    location /nginx_status {
        internal;
        access_log off;
        stub_status;
    }

    location /robots.txt {
        return 200 'User-agent: *\nDisallow: /';
    }
}

Kong version - 1.4
I'm not hitting Kong directly. I'm hitting it via AWS Application load balancer.

Is there another Nginx proxy that's sitting in-front of Kong or are you hitting Kong directly?

I'm not hitting Kong directly. I'm hitting it via AWS Application load balancer. When I remove Kong, I can actually proxy to the application via AWS ALB successfully without the 413 error.

Hi everyone. I have the same issue reported by @collins-b. There´s any workaround?

Dear contributor,
We're closing this issue as there hasn't been any update to it for a long time. If the issue is still relevant in the latest version, please feel free to reopen it. We're more than happy to revisit it again.
Please have a look at our pledge to the community for more information.
Sincerely,
Kong Gateway Team


feat: liveness endpoint

Adding liveness  endpoint.  Related the issue https://github.com/aquasecurity/postee/issues/100

@afdesk please review this PR


Document adding CocoaPods dependency when developing plugins

https://flutter.io/developing-packages/
Describe what to do when adding a CocoaPod dependency to the plugin's CocoaPod itself

@xster, is this documented anywhere?

I'm closing this bug. I suspect newer documentations were added since I opened this issue. https://flutter.io/developing-packages/#dependencies was the info I was looking for.


Revise instruction on running local Typesense instance

We switch to Docker Compose for local Typesense setup and improves the documentation structure and clarity.

@jaeyson Perhaps we should remove the TODO, move to GitHub issues, and add link to readme instead?

@jaeyson Perhaps we should remove the TODO, move to GitHub issues, and add link to readme instead?

Good idea! :+1:

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Fix path to 'wasm-opt'

Fixes #1263
Fix typo of path to 'wasm-opt'
30f2b0a26232b54c8ab7e2e09751170f52856eab
Make sure these boxes are checked! 📦✅

[x] You have the latest version of rustfmt installed

$ rustup component add rustfmt

[x] You ran cargo fmt on the code base before submitting
[x] You reference which issue is being closed in the PR text

✨✨ 😄 Thanks so much for contributing to wasm-pack! 😄 ✨✨

Sorry, the code does not pass the test.
I close it once.


After share a folder coreos ask me a password

im have to share a folser from host to guest, but when i share it in file, when i try to ssh to coreos machine it ask me for a password.

the only password i use is from my host when i bring up the virtual machine (vagrant up)

If i remove the shared folder then i can ssh into my coreos machine without password.
this is my configuration for shared-folder
$shared_folders = {'.' => '/home/core/'}

$shared_folders.each_with_index do |(host_folder, guest_folder), index|
        config.vm.synced_folder host_folder.to_s, guest_folder.to_s, id: "core-share%02d" % index, nfs: true, mount_options: ['nolock,vers=3,udp']
      end

Moved to https://github.com/coreos/bugs/issues/1330


Added french locale

I edited the UserInputManager to add the french locale.
It was not proposed on building.

Hello Superdrac,
Thank you for the pull request. Our process is to make changes internally and run all test before pushing the change to github in the form of a new release. I have added this to our internal tracking system to be assessed and prioritized.
Thank you,
-SWH