Add Global Try Except Function in INDEX.JS

Description
The program will be stopped when errors occurs.
We can fix it and make it long running without stop.
Full steps to reproduce the issue
Add the code at the bottle of the      index.js .
process.on('uncaughtException', function (err) {
    console.log('No worries,still working on~~~');
});
Issue Type
Bug
Operating System
Windows 10, Linux, Mac OS, Other
Do you use Docker?
None

感谢


added initial .travis.yml

Closing, as this is currently under discussion<EMAIL_ADDRESS>


Create Laxmi-pr2

this pr is pending
https://github.com/ajay-dhangar/algo/pull/2006
can you view this
@sanjay-kv @MastanSayyad @AKSHITHA-CHILUKA

@sanjay-kv can you look at this pending pr?

@laxmikandivalasa program ended yesterday at 7 PM no PR after that will be considered


Aurora: Xdg-open broken because kde-open: undefined symbol

Describe the bug
xdg-open is broken in Aurora because kde-open is missing a symbol:
➜ xdg-open https://kde.org
kde-open: symbol lookup error: kde-open: undefined symbol: _ZN3KIOeqERKNS_8UDSEntryES2_

See also:
https://discuss.kde.org/t/xdg-open-broken-because-kde-open-undefined-symbol/26332/4
What did you expect to happen?
I expected that https://kde.org opens in my browser. It worked before on last week's image and in the past.
Output of bootc status
No staged image present
Current booted image: ghcr.io/ublue-os/aurora-dx:stable
    Image version: 41.20241201 (2024-12-01 06:03:49 UTC)
    Image digest: sha256:c7ff06788ace6c1ad1eab39a0973ed8d024d73704f30f9bb4f9b8e6b2eced0a5
Current rollback image: ghcr.io/ublue-os/aurora-dx:stable
    Image version: 41.20241124.5 (2024-11-24 20:39:02 UTC)
    Image digest: sha256:36b157a6c68b6ce4aedb70f7cec5efc43372157f1f20658182c7bce2a52ac580

Output of groups
goekhan wheel incus-admin lxd docker libvirt

Extra information or context
No response

Some further digging to try to find out where this symbol is supposed to come from for kde-open. On the Kinoite image:
$ ldd $(which kde-open) | awk '{print $3}' | xargs -I{} nm -D -A {} 2>/dev/null | grep _ZN3KIOeq
/lib64/libKF6KIOCore.so.6:0000000000098720 T _ZN3KIOeqERKNS_8UDSEntryES2_

It looks like the library /lib64/libKF6KIOCore.so is supposed to have this symbol. On the Aurora image, this symbol does not appear in the same library:
> nm -D -A /lib64/libKF6KIOCore.so.6 | grep _ZN3KIOeq
>

So somehow, the libKF6KIOCore.so library is missing symbols that should be there according to the base image. Not sure how that can happen.

Did some more digging to see where Kinoite and Aurora differ here. Ran the following script to check the different layers of ublue-os/aurora-dx:41-20241130 compared to ublue-os/kinoite-main:41-20241130
img=aurora-dx

for layer in $(crane manifest ghcr.io/ublue-os/${img}:41-20241130 | jq '.layers[] | .digest'); do
  sha=$(echo $layer | tr -d '"')
  echo "Searching layer $sha"
  crane blob ghcr.io/ublue-os/${img}@${sha} | tar -tvz usr/lib64 | grep libKF6KIOCore.so.6
done

ublue-os/aurora-dx:41-20241130
Searching layer sha256:dd5bce6e307d81404b73e62540c42fe7453c3e4a9a879f6de64aa46d2858e425
hrwxrwxrwx 0/0               0 1969-12-31 18:00 usr/lib64/libKF6KIOCore.so.6 link to sysroot/ostree/repo/objects/99/602c29e5c5b9dae591c9401328274b26fa390e070e44b6439e2b4a1799f138.file
hrwxr-xr-x 0/0               0 1969-12-31 18:00 usr/lib64/libKF6KIOCore.so.6.7.0 link to sysroot/ostree/repo/objects/f7/36c82b2ba1e7ff387b66be743164f8dc43e0cee25961bae0d530045342d21e.file

ublue-os/kinoite-main:41-20241130
Searching layer sha256:bca34c9e9cd27a78e2a0ba27128771cca970589f735ac4db26d85c8c906e4716
hrwxr-xr-x 0/0               0 1969-12-31 18:00 usr/lib64/libKF6KIOCore.so.6.8.0 link to sysroot/ostree/repo/objects/2d/0b395fcd2de13be3d50773b10dc25300d86403cfe33787d1c0bf0b0999f7a5.file
hrwxrwxrwx 0/0               0 1969-12-31 18:00 usr/lib64/libKF6KIOCore.so.6 link to sysroot/ostree/repo/objects/57/e890195df164457633db4588ab8e32a36caef992784dda3922def0310057f8.file

Based on this, it seems that Kinoite has updated to KDE Frameworks 6.8 but Aurora still has 6.7 for some reason. And kde-open is relying on KDE Frameworks 6.8.
I'm not familiar with how these images are built, but it seems like somehow Aurora is picking up an old version of KDE Frameworks but some of the KDE utils need a newer version.

I think I understand what's happening now. There is an override when building the images that is downgrading KIO from 6.8 to 6.7:
https://github.com/ublue-os/bluefin/blob/4b7abfb5edfc140eaa772d80d8e90d577261a8df/build_files/base/05-override-install.sh#L12-L21
If we look at the logs at https://github.com/ublue-os/bluefin/actions/runs/12133739629/job/33829758132, we see this happening:
2024-12-03T05:53:02.0604446Z Downloading from 'copr:copr.fedorainfracloud.org:ublue-os:staging'...done
2024-12-03T05:53:02.0605166Z Installing 7 packages:
2024-12-03T05:53:02.0605916Z   kf6-kio-core-6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069.x86_64 (copr:copr.fedorainfracloud.org:ublue-os:staging)
2024-12-03T05:53:02.0607226Z   kf6-kio-core-libs-6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069.x86_64 (copr:copr.fedorainfracloud.org:ublue-os:staging)
2024-12-03T05:53:02.0608644Z   kf6-kio-doc-6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069.noarch (copr:copr.fedorainfracloud.org:ublue-os:staging)
2024-12-03T05:53:02.0610420Z   kf6-kio-file-widgets-6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069.x86_64 (copr:copr.fedorainfracloud.org:ublue-os:staging)
2024-12-03T05:53:02.0611841Z   kf6-kio-gui-6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069.x86_64 (copr:copr.fedorainfracloud.org:ublue-os:staging)
2024-12-03T05:53:02.0613234Z   kf6-kio-widgets-6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069.x86_64 (copr:copr.fedorainfracloud.org:ublue-os:staging)
2024-12-03T05:53:02.0614747Z   kf6-kio-widgets-libs-6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069.x86_64 (copr:copr.fedorainfracloud.org:ublue-os:staging)
2024-12-03T05:53:02.5977384Z Downgrading: kf6-kio-core-libs;6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069;x86_64;copr:copr.fedorainfracloud.org:ublue-os:staging
2024-12-03T05:53:02.6057652Z Downgrading: kf6-kio-doc;6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069;noarch;copr:copr.fedorainfracloud.org:ublue-os:staging
2024-12-03T05:53:02.7276349Z Downgrading: kf6-kio-gui;6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069;x86_64;copr:copr.fedorainfracloud.org:ublue-os:staging
2024-12-03T05:53:02.7324366Z Downgrading: kf6-kio-core;6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069;x86_64;copr:copr.fedorainfracloud.org:ublue-os:staging
2024-12-03T05:53:02.7699286Z Downgrading: kf6-kio-widgets;6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069;x86_64;copr:copr.fedorainfracloud.org:ublue-os:staging
2024-12-03T05:53:02.7761240Z Downgrading: kf6-kio-widgets-libs;6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069;x86_64;copr:copr.fedorainfracloud.org:ublue-os:staging
2024-12-03T05:53:02.7828801Z Downgrading: kf6-kio-file-widgets;6.7.0-2.fc41.switcheroo.0.0.git.177.aecb2069;x86_64;copr:copr.fedorainfracloud.org:ublue-os:staging

This is because there is apparently a custom build of kf6-kio in ublue's COPR. I have created a PR https://github.com/ublue-os/packages/pull/52 to upgrade this package from 6.7 to 6.8. Hopefully, that will be merged, kf6-kio will be repackaged and deployed to COPR and the next build of Aurora should pick it up.

OK, merged the update, rebuilt it in copr, and rebuilding the images:
https://github.com/ublue-os/bluefin/actions/runs/12149226599
https://github.com/ublue-os/bluefin/actions/runs/12149252804
When these go green someone test and confirm and I'll refresh the isos.

With aurora-dx:latest, xdg-open no longer crashes and the correct KIO libraries are in /lib64.

Thank you very much  @ledif for you time and effort!


[Cosmos] Stargate support

swagger: https://cosmos.network/rpc/master
migration guide: https://docs.cosmos.network/master/migrations/rest.html

This was partially done in pr: https://github.com/trustwallet/blockatlas/pull/1420, new grpc rest api isn't finalized (v1beta1 in route), we will reopen this issue one new api is stable


Added leader functions

Description
This branch adds several functions to XMonad.Hooks.ManageHelpers that allows windows to be shifted to the workspace of the leader window. This leader will either be the original window that spawned that window, or another window that the original window spawned. It identifies the leader using the WM_CLIENT_LEADER property.
This is meant to have a similar purpose as the transience hook. However, very few applications set the transience property (in fact, none that I have examined on my system). On the other hand, the WM_CLIENT_LEADER property is set more frequently (in firefox, for example).
The following discussion is relevant: https://xmonad.haskell.narkive.com/xZPtl1AH/managehook-and-child-windows
Checklist

[x] I've read CONTRIBUTING.md

n/a I tested my changes with xmonad-testing

[x] I updated the CHANGES.md file

n/a I updated the XMonad.Doc.Extending file (if appropriate)

@liskin it works on my system and the new code looks good. I think generalizing it so that it works with PID adds a lot of functionality.
I just committed a small change to the documentation.
Thanks for your help with this.


style(test/which): make test/which.js conform to the style guidelines

This is an example PR for how to make PRs against #317.

@nfischer: Ready for review.

LGTM


[#1447] feat(client): Introduce configurations to control default behavior of RPC client

What changes were proposed in this pull request?
Introduce two configurations to control the default behavior of the RPC client:

Property Name
Default
Description

<client_type>.rss.client.rpc.timeout.ms
60000
Timeout in milliseconds for RPC calls.

<client_type>.rss.client.rpc.maxAttempts
3
When we fail to send RPC calls, we will retry for maxAttempts times.

Why are the changes needed?
For #1447
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually.

PTAL @jerqi @zuston

Codecov Report
Attention: 18 lines in your changes are missing coverage. Please review.

Comparison is base (b43bbd8) 54.15% compared to head (8553f12) 54.68%.

Files
Patch %
Lines

...ffle/client/impl/grpc/ShuffleServerGrpcClient.java
0.00%
9 Missing :warning:

...client/impl/grpc/ShuffleServerGrpcNettyClient.java
0.00%
8 Missing :warning:

...fle/client/factory/ShuffleServerClientFactory.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1448      +/-   ##
============================================
+ Coverage     54.15%   54.68%   +0.52%
+ Complexity     2773     2240     -533
============================================
  Files           423      346      -77
  Lines         24178    15595    -8583
  Branches       2057     1427     -630
============================================
- Hits          13094     8528    -4566
+ Misses        10275     6594    -3681
+ Partials        809      473     -336

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Merged. Thanks @rickyma


Adapt button/text input sizes to screen resolution

Because of fixed-size labels, on smaller resolutions, the text is not shown fully - it doesn't fit into the  provided space.

Possible solution: change sizes to sp or dp?


A little advice from a foreign friend

You can check out the translation model of this plugin, it would be simply awesome if the officials would collaborate with them or make a similar plugin
His translation is based on the original with annotations
https://twitter.com/immersivetran
https://microsoftedge.microsoft.com/addons/detail/沉浸式翻译/amkbmndfnliijdhojkpoglbnaaahippg

This translation model is great for students who are learning a foreign language!

Hi, this plugin looks interesting but we don't own it (and it doesn't look like it's open source? It has a GitHub but it looks like it's already transpiled TypeScript. So the developer who made it would need to integrate our API.

Yes, it's possible to use your API on his plugin, I'm struggling with the fact that our country doesn't support the opening of deeply API pro, this is great. I'm using Mastercard and Express and it doesn't work, it looks like it only supports a few countries that are written on the website, hope,fully it will come to the Chinese market soon.
---Original---
From: @.>
Date: Tue, Sep 5, 2023 15:58 PM
To: @.>;
Cc: "Evan<EMAIL_ADDRESS>Subject: Re: [DeepLcom/openapi] A little advice from a foreign friend (Issue#5)
Hi, this plugin looks interesting but we don't own it (and it doesn't look like it's open source? It has a GitHub but it looks like it's already transpiled TypeScript. So the developer who made it would need to integrate our API.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Show user transaction history

We would like to show the user their transaction history so they can track the status of the bridge transactions.

Closing because now using Jira


Fix decoder only generation

What does this PR do?
Fixes issues with decoder-only generation. Multiple issues were found and corrected.
root@idc705326-7:/optimum-habana# GAUDI2_CI=1  RUN_SLOW=1 python -m pytest tests/transformers/tests/models/ -k test_generate_from_inputs_embeds_decoder_only
============================================================================================================== test session starts ==============================================================================================================
platform linux -- Python 3.10.12, pytest-7.4.4, pluggy-1.4.0
rootdir: /optimum-habana
configfile: setup.cfg
collected 1218 items / 1210 deselected / 8 selected

tests/transformers/tests/models/bert/test_modeling_bert.py .                                                                                [ 12%]
tests/transformers/tests/models/falcon/test_modeling_falcon.py .                                                                                [ 25%]
tests/transformers/tests/models/gpt2/test_modeling_gpt2.py .                                                                                [ 37%]
tests/transformers/tests/models/gpt_neox/test_modeling_gpt_neox.py .                                                                                [ 50%]
tests/transformers/tests/models/gptj/test_modeling_gptj.py .                                                                                [ 62%]
tests/transformers/tests/models/llama/test_modeling_llama.py .                                                                                [ 75%]
tests/transformers/tests/models/roberta/test_modeling_roberta.py .                                                                                [ 87%]
tests/transformers/tests/models/t5/test_modeling_t5.py .                                                                                [100%]

=============================================================================================================== warnings summary ================================================================================================================
../usr/local/lib/python3.10/dist-packages/transformers/utils/generic.py:462
  /usr/local/lib/python3.10/dist-packages/transformers/utils/generic.py:462: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
    _torch_pytree._register_pytree_node(

../usr/local/lib/python3.10/dist-packages/transformers/utils/generic.py:319
../usr/local/lib/python3.10/dist-packages/transformers/utils/generic.py:319
  /usr/local/lib/python3.10/dist-packages/transformers/utils/generic.py:319: UserWarning: torch.utils._pytree._register_pytree_node is deprecated. Please use torch.utils._pytree.register_pytree_node instead.
    _torch_pytree._register_pytree_node(

tests/transformers/tests/test_modeling_common.py:2044
  /optimum-habana/tests/transformers/tests/test_modeling_common.py:2044: PytestUnknownMarkWarning: Unknown pytest.mark.accelerate_tests - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
    @mark.accelerate_tests

tests/transformers/tests/test_modeling_common.py:2082
  /optimum-habana/tests/transformers/tests/test_modeling_common.py:2082: PytestUnknownMarkWarning: Unknown pytest.mark.accelerate_tests - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
    @mark.accelerate_tests

tests/transformers/tests/test_modeling_common.py:2118
  /optimum-habana/tests/transformers/tests/test_modeling_common.py:2118: PytestUnknownMarkWarning: Unknown pytest.mark.accelerate_tests - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
    @mark.accelerate_tests

tests/transformers/tests/models/gpt2/test_modeling_gpt2.py::GPT2ModelTest::test_generate_from_inputs_embeds_decoder_only
tests/transformers/tests/models/gpt_neox/test_modeling_gpt_neox.py::GPTNeoXModelTest::test_generate_from_inputs_embeds_decoder_only
tests/transformers/tests/models/gptj/test_modeling_gptj.py::GPTJModelTest::test_generate_from_inputs_embeds_decoder_only
tests/transformers/tests/models/llama/test_modeling_llama.py::LlamaModelTest::test_generate_from_inputs_embeds_decoder_only
  /usr/local/lib/python3.10/dist-packages/transformers/generation/utils.py:1178: UserWarning: Using the model-agnostic default `max_length` (=20) to control the generation length. We recommend setting `max_new_tokens` to control the maximum length of the generation.
    warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=============================================================================================== 8 passed, 1210 deselected, 10 warnings in 11.21s ================================================================================================

Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

@regisss I think too many reviewers were tagged and this got lost in the weeds. Can I please have this PR reviewed?

Please sync your PR with main/upstream and fix any merge conflicts. Thank you.

@ssarkar2 @regisss Please review this fix for inputs_embeds with static shapes.

Thanks @yafshar. It is ready for review. I'll run the tests to confirm no regressions

@yafshar  Here are the test results:
GAUDI2_CI=1 RUN_SLOW=true python -m pytest tests/transformers/tests/models/ -s -v
main: 26 failed, 873 passed, 326 skipped, 1 xpassed, 58 warnings in 1639.18s (0:27:19) =
this pr:  21 failed, 878 passed, 326 skipped, 1 xpassed, 58 warnings in 1330.34s (0:22:10) =

@yafshar Here are the results of additional tests
make slow_tests_text_generation_example
Main: 1 failed, 25 passed, 4 skipped
This pr: 1 failed, 25 passed, 4 skipped
Perf test to check that text generation with input_ids is not impacted by fix.
python run_generation.py --model_name_or_path openai-community/gpt2 --use_kv_cache --max_new_tokens 128 --max_input_tokens=128 --batch_size 4 --use_hpu_graph --bf16 --no-ignore_eos
Tokens/sec for 3 runs
Main:  2186.605, 2222.230,  2201.932
This PR: 2222.338 2240.891  2237.272

@skavulya please ignore my last comments if you do not like it. It is a personal style, I do not like the extra conditional check

Thanks @yafshar. I'll update the code. Your suggestions make it cleaner.

@skavulya thanks, everything sounds good to me. Would you please add a final test to make sure we do not miss anything. please run GAUDI2_CI=1 RUN_SLOW=true python -m pytest tests/transformers/tests/models/ -s -v before and after changes and make sure there is no new one is introduced.

Thanks @yafshar. I rebased and re-ran the tests.
Main: 25 failed, 874 passed, 326 skipped, 1 xpassed, 59 warnings in 1351.61s (0:22:31) =
This PR 20 failed, 879 passed, 326 skipped, 1 xpassed, 59 warnings in 1474.58s (0:24:34) =

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Supervisor Meeting - Wed Sep 25

Date and Time
Wed Sep 25, 3:00-4:00pm
Attendance

[ ] Adam Podolak
[ ] Austin Bennett
[ ] Christian Petricca
[ ] Evan Sturmey
[ ] Jacob Kish

Agenda

Start with a set of suggested (ChatGPT) requirements to iterate off of
Communicate plans for POC, as well as next steps for gaining dev access to MES infrastructure

Questions to Ask

Financial Reporting Platform Requirements (ChatGPT generated, starting point for actual discussion)
Functional Requirements
1. User Roles and Permissions

The platform must support two user roles: User and Admin.

User: Can submit financial report requests, view reports, and receive notifications.
Admin: Can view all user-submitted requests, manage reports, and perform user management (add, remove, update users).

2. Authentication and Security

User Authentication: Users must sign in with a unique username and password, utilizing a secure authentication mechanism (OAuth 2.0 or similar).
Role-based Access Control: Ensure that users and admins only have access to the features and data permitted by their role.
Two-factor Authentication (2FA): Optionally enable two-factor authentication for additional security.

3. Financial Report Request Submission

Users must be able to submit requests for financial reports through a form.
The form should capture the following information:

User details (auto-filled based on login).
Type of report (e.g., balance sheet, income statement).
Date range for the report.
Customizable filters (e.g., by department, by account).

Provide the ability to upload supporting documents or additional data for the request.

4. Notifications

User Notifications:

Notify users via email or in-platform notifications when their financial report request has been submitted, is in progress, or has been completed.
Allow users to configure their notification preferences (e.g., email, SMS).

Admin Notifications:

Notify admins when a new report request is submitted.
Alert admins of failed report generations or overdue requests.

5. Financial Report Generation

The platform must be able to generate financial reports based on user input and provided data.
Support exporting reports in multiple formats (e.g., PDF, Excel, CSV).
Reports should be archived and accessible to the user after generation.

6. Dashboard and Report Management

User Dashboard:

Display all submitted report requests with statuses (pending, in progress, completed).
Provide quick access to download previously requested reports.

Admin Dashboard:

View all submitted reports from all users.
Provide controls to assign report requests to team members, mark requests as completed, or reject requests with reasons.

7. User and Admin Management

Admin:

Manage users: Add, edit, or deactivate user accounts.
Assign or revoke admin privileges to specific users.

User Profile: Allow users to update their personal information (e.g., email, phone number) and configure notification preferences.

8. Audit Trail

Record all user and admin activities (e.g., report request submissions, login attempts, report downloads) for security and compliance purposes.
Provide admin access to audit logs with filters for date range, activity type, or user.

Non-Functional Requirements
1. Scalability

The platform must be able to handle multiple simultaneous report requests and high traffic during peak usage periods.

2. Performance

Ensure that report generation times are optimized, with feedback mechanisms in place for the user if processing takes longer than expected.
Dashboard loading times should be under 2 seconds.

3. Security

Ensure the platform uses encryption for all sensitive data (e.g., passwords, financial data).
Implement regular security updates and patches.
Support secure API integration with other financial systems.

4. Data Privacy and Compliance

Ensure compliance with relevant data privacy laws (e.g., GDPR, CCPA).
Provide users with clear options to delete their data or request a copy of all their stored data.

5. Usability

Design the platform with an intuitive user interface that requires minimal training.
Provide user-friendly error messages and tooltips to guide users through the submission and report retrieval processes.

Optional Features

Report Scheduling: Allow users to schedule recurring financial report requests (e.g., monthly or quarterly).
Data Visualization: Provide basic visualization tools (e.g., charts, graphs) for users to analyze report data within the platform.
API Access: Offer API endpoints for power users to submit report requests or retrieve completed reports programmatically.

Summarized meeting notes (Chat GPT generated):
Meeting Summary: Streamlining Financial Processes
Objective: Enhance and automate the organization's financial workflows, including reimbursement requests, disbursements, payment processing, intramural funding, invoice generation, and bank transaction tracking.

Key Areas of Focus:

Reimbursement Requests:

Implement a streamlined submission process that captures budget lines, receipts, and payment information.
Introduce a review stage where the financial team evaluates requests before escalating them to Luke for final approval.
Provide the ability for requestors to edit submissions to correct issues, reducing the need for email correspondence or resubmissions.
Establish a two-step approval process to enhance oversight.

Disbursement Tracking:

Utilize the bank platform to handle disbursements.
Track the status of each request through defined stages:

Submitted
Reviewed
Approved

Entered into the bank system
Requires second-person approval for bank transactions

Disbursed
Delivered

Payment Requests:

Manage outgoing payments to vendors, including e-transfers and invoice settlements.
Collect detailed payment information and link each payment to the appropriate budget line.

Intramural Funding Requests:

Develop an intramural funding dashboard for streamlined applications and approvals.
Allow applicants to apply for funding on the backend system.
Enable sports coordinators to monitor the disbursement of funds.

Data Management and Compliance:

Save repetitive information to improve efficiency.
Implement audit tracking to ensure compliance by matching expenditures to budget categories.
Automate ledger tracking for accurate financial records.
Set up SMS notifications and automated emails for communication.

Invoice Generation:

Create a custom, organization-wide invoice generation system that incorporates GST/HST numbers.
Design pre-built PDF templates featuring the organization's logo for consistent branding.
Customize invoice templates for approximately 60 different clubs.
Maintain accurate tracking of past invoices.

Bank Transaction Integration:

Import bank account data via CSV files.
Link each bank transaction to corresponding reimbursements, funding allocations, and invoices.
Keep a comprehensive record of all incoming and outgoing transactions.


Moore Vote Algorithm

would like to add moore vote algorithm along with an example particularly a question from leetcode based on this (majority element #169) and proper explanation.
Please assign this to me and add gssoc tag including other relevant tags

present at #392


Wallet creation is taking a long time.

Wallet creation taking such a long time even after Savings Account is not being created here.

Verified this issue on dev app v2.0(345)


Change mouse cursor based on the current selected brush mode

Currently, the user cannot know which brush they selected.
It would be great if we could change the mouse cursor based on the selected brush mode.
Plus, since people could have their own brush modes, we could create a function that allows people to change the mouse cursors to the icon of their choice

I will close this issue since it was implemented.


Add error message when configuration loading fails

When the configuration path for the lixXnDevicesSensorV2.dylib isn't found loading the modules fails withouth showing a message or error. It keeps "waiting" on something. You can reproduce this easily by changing the configDir inthe modules.xml file to a  non-exsting path.

This was fixed in sensor 5.1 and above.
Ziv.


docs: clarify auto_patch as per #108

Issue #, if available: #108
Description of changes:

Clarifies auto_patch=False feature when reusing Tracer across multiple modules, or in Lambda Layers, where import order creates a side effect where no modules end up being patched.
Checklist

[ ] Meet tenets criteria
[ ] Update tests
[x] Update docs
[ ] PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #109 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop      #109   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           17        17
  Lines          499       492    -7
  Branches        46        46
=========================================
- Hits           499       492    -7

Impacted Files
Coverage Δ

aws_lambda_powertools/logging/logger.py
100.00% <0.00%> (ø)

aws_lambda_powertools/tracing/tracer.py
100.00% <0.00%> (ø)

aws_lambda_powertools/metrics/metrics.py
100.00% <0.00%> (ø)

...ws_lambda_powertools/middleware_factory/factory.py
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Adopt-a-Drain SF (AAD-SF) uses an email address ( info@sfwater.org). Replace or remove?

Steps:

Updated<EMAIL_ADDRESS>to<EMAIL_ADDRESS>Tests: OK
In heroic staging:

Is this a tech support email or a general program information email? If it's for people's questions about the adopt a drain program, it should come to LGROW. We are getting our tech guys to set up an email for the program - hoping it will be<EMAIL_ADDRESS>


Get the transmission rate of the video

hello, Is there a way to monitor the real-time transmission rate of live video?

Now zlmediakit support whip/whep, you can also use other client.

you can custom  develop the player reference https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/getStats


etcd.conf not used

I am running ubuntu trusty
Linux beehive 3.16.0-33-generic #44~14.04.1-Ubuntu SMP Fri Mar 13 10:33:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

made the .deb package and installed it.  local testing works fine
⟫ etcdctl set /message "Bonjour monde"
Bonjour monde
⟫ etcdctl get /message "Bonjour monde"
Bonjour monde
⟫ curl -L -X PUT http://<IP_ADDRESS>:4001/v2/keys/message -d value="Hello World"
{"action":"set","node":{"key":"/message","value":"Hello World","modifiedIndex":23,"createdIndex":23},"prevNode":{"key":"/message","value":"Bonjour monde","modifiedIndex":22,"createdIndex":22}}
⟫ curl -L -X GET http://<IP_ADDRESS>:4001/v2/keys/message
{"action":"get","node":{"key":"/message","value":"Hello World","modifiedIndex":23,"createdIndex":23}}

I proceed to edit /etc/etcd.conf file, restart the service and it doesn't give error or use the values (I wanted to listen on the LAN, not <IP_ADDRESS>)

etcd.conf

This file will be sourced after the /etc/default/etcd system
config file.  You can configure etcd via environment variables
from this file.

See the documentation in /usr/share/doc/etcd/ for details.
sample etcd cluster config
export ETCD_INITIAL_CLUSTER_TOKEN="cluster1"

sudo service etcd restart

Stopping etcd:
stopped
Starting etcd:
started

2015/04/02 09:37:01 no data-dir provided, using default data-dir ./default.etcd
2015/04/02 09:37:01 etcd: listening for peers on http://localhost:2380
2015/04/02 09:37:01 etcd: listening for peers on http://localhost:7001
2015/04/02 09:37:01 etcd: listening for client requests on http://localhost:2379
2015/04/02 09:37:01 etcd: listening for client requests on http://localhost:4001
2015/04/02 09:37:01 datadir is valid for the 2.0.1 format
2015/04/02 09:37:01 etcdserver: name = default
2015/04/02 09:37:01 etcdserver: data dir = default.etcd
2015/04/02 09:37:01 etcdserver: member dir = default.etcd/member
2015/04/02 09:37:01 etcdserver: heartbeat = 100ms
2015/04/02 09:37:01 etcdserver: election = 1000ms
2015/04/02 09:37:01 etcdserver: snapshot count = 10000
2015/04/02 09:37:01 etcdserver: advertise client URLs = http://localhost:2379,http://localhost:4001
2015/04/02 09:37:01 etcdserver: restart member ce2a822cea30bfca in cluster 7e27652122e8b2ae at commit index 8589
2015/04/02 09:37:01 raft: ce2a822cea30bfca became follower at term 16
2015/04/02 09:37:01 raft: newRaft ce2a822cea30bfca [peers: [], term: 16, commit: 8589, applied: 0, lastindex: 8589, lastterm: 16]
2015/04/02 09:37:01 etcdserver: added local member ce2a822cea30bfca [http://localhost:2380 http://localhost:7001] to cluster 7e2765$
2015/04/02 09:37:02 raft: ce2a822cea30bfca is starting a new election at term 16
2015/04/02 09:37:02 raft: ce2a822cea30bfca became candidate at term 17
2015/04/02 09:37:02 raft: ce2a822cea30bfca received vote from ce2a822cea30bfca at term 17
2015/04/02 09:37:02 raft: ce2a822cea30bfca became leader at term 17
2015/04/02 09:37:02 raft.node: ce2a822cea30bfca elected leader ce2a822cea30bfca at term 17
2015/04/02 09:37:02 etcdserver: published {Name:default ClientURLs:[http://localhost:2379 http://localhost:4001]} to cluster 7e2765$

That is surprising. Can you dig a little deeper into why? Maybe a set -vx on the init script might reveal it?

Tried a bunch of different settings in the conf file and finally got it working, maybe you can use this as a starting conf?
OLD (not working, the duplicate lines probably cause issues)
#
# etcd.conf
#
# This file will be sourced after the /etc/default/etcd system
# config file.  You can configure etcd via environment variables
# from this file.
#
# See the documentation in /usr/share/doc/etcd/ for details.

# sample etcd cluster config
#export ETCD_INITIAL_CLUSTER_TOKEN="cluster1"
#export ETCD_INITIAL_CLUSTER="infra1=http://<IP_ADDRESS>:2380,infra2=http://<IP_ADDRESS>:2380,infra3=http://<IP_ADDRESS>:2380"
#export ETCD_INITIAL_CLUSTER_TOKEN="cluster1"
#export ETCD_INITIAL_ADVERTISE_PEER_URLS="http://<IP_ADDRESS>:2380"
#export ETCD_LISTEN_PEER_URLS="http://<IP_ADDRESS>:2380"

NEW (working)
#
# etcd.conf
#
# This file will be sourced after the /etc/default/etcd system
# config file.  You can configure etcd via environment variables
# from this file.
#
# See the documentation in /usr/share/doc/etcd/ for details.

export ETCD_NAME="testlab"
export ETCD_LISTEN_PEER_URLS="http://<IP_ADDRESS>:7001"
export ETCD_LISTEN_CLIENT_URLS="http://<IP_ADDRESS>:4001"
export ETCD_INITIAL_ADVERTISE_PEER_URLS="http://<IP_ADDRESS>:7001"
export ETCD_INITIAL_CLUSTER="testlab=http://<IP_ADDRESS>:7001"
export ETCD_INITIAL_CLUSTER_STATE="new"
export ETCD_ADVERTISE_CLIENT_URLS="http://<IP_ADDRESS>:4001"

now listening on my eth0 :+1:
2015/04/02 11:29:14 no data-dir provided, using default data-dir ./testlab.etcd
2015/04/02 11:29:14 etcd: listening for peers on http://<IP_ADDRESS>:7001
2015/04/02 11:29:14 etcd: listening for client requests on http://<IP_ADDRESS>:4001
2015/04/02 11:29:14 etcdserver: name = testlab
2015/04/02 11:29:14 etcdserver: data dir = testlab.etcd
2015/04/02 11:29:14 etcdserver: member dir = testlab.etcd/member
2015/04/02 11:29:14 etcdserver: heartbeat = 100ms
2015/04/02 11:29:14 etcdserver: election = 1000ms
2015/04/02 11:29:14 etcdserver: snapshot count = 10000
2015/04/02 11:29:14 etcdserver: advertise client URLs = http://<IP_ADDRESS>:4001
2015/04/02 11:29:14 etcdserver: initial advertise peer URLs = http://<IP_ADDRESS>:7001
2015/04/02 11:29:14 etcdserver: initial cluster = testlab=http://<IP_ADDRESS>:7001
2015/04/02 11:29:14 etcdserver: start member ceb5e9e76eb97be4 in cluster 65a9292a43de52c8
2015/04/02 11:29:14 raft: ceb5e9e76eb97be4 became follower at term 0
2015/04/02 11:29:14 raft: newRaft ceb5e9e76eb97be4 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2015/04/02 11:29:14 raft: ceb5e9e76eb97be4 became follower at term 1
2015/04/02 11:29:14 etcdserver: added local member ceb5e9e76eb97be4 [http://<IP_ADDRESS>:7001] to cluster 65a9292a43de52c8
2015/04/02 11:29:16 raft: ceb5e9e76eb97be4 is starting a new election at term 1
2015/04/02 11:29:16 raft: ceb5e9e76eb97be4 became candidate at term 2
2015/04/02 11:29:16 raft: ceb5e9e76eb97be4 received vote from ceb5e9e76eb97be4 at term 2
2015/04/02 11:29:16 raft: ceb5e9e76eb97be4 became leader at term 2
2015/04/02 11:29:16 raft.node: ceb5e9e76eb97be4 elected leader ceb5e9e76eb97be4 at term 2
2015/04/02 11:29:16 etcdserver: published {Name:testlab ClientURLs:[http://<IP_ADDRESS>:4001]} to cluster 65a9292a43de52c8

in the make file, I had problem with this line:
wget -nv --show-progress -c -O $(TARBALL) $(DOWNLOAD)

on trusty 14.04 (GNU Wget 1.15 built on linux-gnu)
wget: unrecognized option '--show-progress'
i changed it to
wget -nv --progress=dot -c -O $(TARBALL) $(DOWNLOAD)

@jtktam nice finds.
Ideally I didn't want to set any config that would cause a fresh install to deviate from the etcd defaults.  I'd prefer to leave it so.
Can you provide more info about how you were setting the config that wasn't getting picked up?  Did you find a bug in that part?
I have some other improvements to the init script that I'll push in the next couple of days, though none of that changes how the config is applied, so would be interested in more info from you.

@jinnko please review my two suggestions above.  one of them is the makefile doesn't work on trusty wget install, the --show-progress is not supported
the other is the fact that the config file contains duplicate lines, i think that is the cause of why it didn't work out of the box
once i remove the duplicate lines and added the correct line, it works for me.  if you want to make a config file with the defaults, that would be ideal for a starting point as well.

Please PR with any improvements to help other people who encounter the same things!

I will do that. thanks.  working on it this weekend.

PR sent, closing issue since it's running great for me now.


docs: List GitLab Suggestion as Implemented

The GitLab merge request discussion reporter definitely supports the suggestion feature.
Looks like it was added in https://github.com/reviewdog/reviewdog/pull/1012
No need to update the change log since this is just a docs change.

Probably needs to merge changes from master so that status checks are run

Probably needs to merge changes from master so that status checks are run

Done, but I don't know if that's the hold up. On my end it says that the workflows need approval to run.

@shogo82148 @kepten do either of you know who needs to approve the workflows so that they will run?

Hi, @JamesMConroy! We merged your PR to reviewdog! 🐶
Thank you for your contribution! ✨
We just invited you to join the @reviewdog organization on GitHub.
Accept the invite by visiting https://github.com/orgs/reviewdog/invitation.
By joining the team, you'll be a part of reviewdog community and can help the maintenance of reviewdog.
Thanks again!


[Marker.io] (Mobile) av integration page is distorted

Steps to reproduce:

slide on screen, from right to left

Actual result: it is distorted
Expected result: should be shown properly

Reported by: Vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://proav-stg.webflow.io/av-integration
Issue details: Open in Marker.io
Device typemobileBrowserSafari 17.6Screen Size375 x 812OSiOS 17.6.1Viewport Size375 x 710Pixel Ratio@3x

🤖 Marker.io bot - This issue was marked as ✅ Resolved in Marker.io


Update to v2.9.0

2.9.0 (08/06/2020)

Drop support for iOS 7, 8 & 9

2.8.5 (07/21/2020)

Improved Swift interface

2.8.1 (07/01/2020)

Convert private static C functions (that take self as an argument) to Objective-C direct methods

Same low overhead, better calling syntax

2.8.0 (06/08/2020)

Update initWithOutError: to initAndReturnError: for TLSRollingFileOutputStream

More idiomatic

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


clean up the ml dev experience sig and add harshad16 as chair

Description

clean up the ml dev experience sig and add harshad16 as chair
New Open Data Hub Member Requirements

[ ] New members have reviewed and acknowledged the Open Data Hub:

Code of Conduct
Contribution Guide
Community Membership Guidelines

[ ] Enabled 2FA on their GitHub account

Pull Request Requirements

[x] New members are added in alphabetical order
[ ] Only one new member change per commit (if you add two members separate it in two commits
[ ] For individual user changes: Commit message format Add <USERNAME> to <opendatahub-io, mlops-sig, ...>.
[ ] For new team requests: Commit message format Create <TEAMNAME>. If the new team consists solely of existing members, you may
[x] New GitHub team requests are from an existing opendatahub-io member who will function as the maintainer of the team. Each additional member will follow the same requirements for adding new members

I think the multiple commits requirement is... not super valuable... so have no qualms approving this in that state.


fixed issue #1358,#1529,#1566,#1562,#1568 - [closed]

In GitLab by @liyanq528 on Jul 19, 2018, 02:25
Merges 20180628 -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
The test coverage for backend is FAIL  ,The test coverage for frontend is 38.11   , check  consolse log

In GitLab by @wknet123 on Nov 13, 2019, 11:16
closed


plan cache

Peloton's query plan, or even plan executor, can be cached. There is no need to create a new plan instance for each transaction. Meanwhile, the executor_context of each transaction can also be reused.

We are now caching the query plan. I am not sure if caching the executor tree is a good idea.


Write log messages from SourceKit-LSP’s index log to a separate output view

https://github.com/apple/sourcekit-lsp/pull/1398 adds an LSP extension to set a logName in the window/logMessage notifications. It would be great if the VS Code extension could write log messages that have logName set to an output view with that name. This would ensure that the index log does not get interleaved with other logs from SourceKit-LSP such as stderr messages or the message trace if verbose logging is enabled in the Swift extension.

The logging of LSP output is internal to the VSCode language client. We don't have control over this. I checked to see if we could catch log messages via a middleware but that doesn't seem possible either.

I think @award999 had some ideas of how to capture the log output.

Ya we can't hook into the middleware but should be able to set an notification handler, I'll take a look next week and make sure works as I expect it to

For verification need to enable background indexing https://github.com/apple/sourcekit-lsp/blob/main/Documentation/Enable Experimental Background Indexing.md

Verified with e8308d6


Package request: nucleo

A fast and convenient fuzzy matcher library for rust
Fuzzy matcher that is used in helix editor
Metadata

homepage URL: https://github.com/helix-editor/nucleo
source URL: https://github.com/helix-editor/nucleo
license: MPL 2.0
platforms: all

Add a :+1: reaction to issues you find important.

AFAICT at the moment they haven't implemented a standalone cli.

oh, my problem


segmentation fault when using 1080p res (imx327)

Hi,
I am getting Segmentation fault when setting --width 1920 --height 1080 when using the imx327, with my pi 3b+.
The preview window will appear only for a moment, and segmentation fault appears.
It does not happen when width and height is not set.
[0:13:54.413228670] [1334]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+2390-e32d33b1
[0:13:54.430912021] [1338]  WARN CameraSensor camera_sensor.cpp:306 'imx290 10-001a': Recommended V4L2 control 0x009a0922 not supported
[0:13:54.431568269] [1338]  WARN CameraSensor camera_sensor.cpp:358 'imx290 10-001a': The sensor kernel driver needs to be fixed
[0:13:54.431746446] [1338]  WARN CameraSensor camera_sensor.cpp:360 'imx290 10-001a': See Documentation/sensor_driver_requirements.rst in the libcamera sources for more information
[0:13:54.442069238] [1338]  WARN CameraSensor camera_sensor.cpp:472 'imx290 10-001a': Failed to retrieve the camera location, setting to External
[0:13:54.616388274] [1334]  WARN V4L2 v4l2_pixelformat.cpp:180 Unsupported V4L2 pixel format XB24
[0:13:54.617047491] [1334] ERROR Controls controls.cpp:990 Control 0x00000002 not found
[0:13:54.617675563] [1334] ERROR Controls controls.cpp:990 Control 0x00000002 not found
[0:13:54.618043583] [1334] ERROR Controls controls.cpp:990 Control 0x00000002 not found
[0:13:54.618370770] [1334]  INFO Camera camera.cpp:890 configuring streams: (0) 1920x1080-YUV420
[0:13:54.619355247] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 1500 (best 1500)
[0:13:54.619602434] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt RG10 Score: 3500 (best 1500)
[0:13:54.619725298] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG12 Score: 500 (best 500)
[0:13:54.619825455] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt RG12 Score: 2500 (best 500)
[0:13:54.619929673] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1000 (best 500)
[0:13:54.620076392] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt pRAA Score: 3000 (best 500)
[0:13:54.620186600] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRCC Score: 0 (best 0)
[0:13:54.620286339] [1338]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt pRCC Score: 2000 (best 0)
[0:13:54.620433214] [1338]  INFO RPI raspberrypi.cpp:611 Sensor: /base/soc/i2c0mux/i2c@1/imx290@1a - Selected mode: 1920x1080-pRCC
[0:13:54.738936733] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: Sharpness = 1.000000
[0:13:54.739254232] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: Saturation = 1.000000
[0:13:54.739365274] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: Brightness = 0.000000
[0:13:54.739455221] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: FrameDurations = [ 33333, 33333 ]
[0:13:54.739593554] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: AeMeteringMode = 0
[0:13:54.739834856] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: Contrast = 1.000000
[0:13:54.739911002] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: NoiseReductionMode = 1
[0:13:54.740162408] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: ExposureValue = 0.000000
[0:13:54.740270584] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: AwbMode = 0
[0:13:54.740348345] [1341]  INFO IPARPI raspberrypi.cpp:612 Request ctrl: AeExposureMode = 0
[0:13:54.743313495] [1338]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:13:54.743495526] [1338]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:13:54.743582453] [1338]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:13:55.019033479] [1338]  INFO RPI raspberrypi.cpp:1621 Dropping frame at the request of the IPA (6 left)
[0:13:55.068152081] [1338]  INFO RPI raspberrypi.cpp:1621 Dropping frame at the request of the IPA (5 left)
[0:13:55.132388570] [1338]  INFO RPI raspberrypi.cpp:1621 Dropping frame at the request of the IPA (4 left)
[0:13:55.192103193] [1338]  INFO RPI raspberrypi.cpp:1621 Dropping frame at the request of the IPA (3 left)
[0:13:55.241578305] [1338]  INFO RPI raspberrypi.cpp:1621 Dropping frame at the request of the IPA (2 left)
[0:13:55.295289607] [1338]  INFO RPI raspberrypi.cpp:1621 Dropping frame at the request of the IPA (1 left)
[0:13:55.334941300] [1338]  INFO RPI raspberrypi.cpp:1621 Dropping frame at the request of the IPA (0 left)
Segmentation fault

Hi, sorry - I didn't see this issue come in.
I've tried this running on a Pi 3 with the imx327 module that I have  (an Innomaker one) as follows:
./libcamera-vid -o test.h264 --width 1920 --height 1080
but don't see a problem.
Can you say which application you're running and the exact command line? Is everything up to date? Is there anything unusual about your setup or how you're driving it? Failing that we may need to get a backtrace and see what that tells us.

Hi,
I am using a pi 3+, with the imx327 (innomaker).
The command that I was using was ./libcamera-vid --width 1920 --height 1080. Having -o or not makes no difference in this issue.
I remembered running rpi-update before trying and experiencing this issue. libcamera-apps, libcamera was also newly compiled from source. (as of time of first post)
uname -a
Linux raspberrypi 5.10.20-v7+ #1404 SMP Thu Mar 4 19:40:23 GMT 2021 armv7l GNU/Linux

First run always results in Segmentation fault, but second run will result in:
./libcamera-vid --width 1920 --height 1080
[0:01:49.201691257] [1355]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+2390-e32d33b1
[0:01:49.227770858] [1359]  WARN CameraSensor camera_sensor.cpp:306 'imx290 10-001a': Recommended V4L2 control 0x009a0922 not supported
[0:01:49.227989922] [1359]  WARN CameraSensor camera_sensor.cpp:358 'imx290 10-001a': The sensor kernel driver needs to be fixed
[0:01:49.228051694] [1359]  WARN CameraSensor camera_sensor.cpp:360 'imx290 10-001a': See Documentation/sensor_driver_requirements.rst in the libcamera sources for more information
[0:01:49.237700873] [1359]  WARN CameraSensor camera_sensor.cpp:472 'imx290 10-001a': Failed to retrieve the camera location, setting to External
[0:01:49.410258019] [1355]  WARN V4L2 v4l2_pixelformat.cpp:180 Unsupported V4L2 pixel format XB24
[0:01:49.410964586] [1355] ERROR Controls controls.cpp:990 Control 0x00000002 not found
[0:01:49.411726362] [1355] ERROR Controls controls.cpp:990 Control 0x00000002 not found
[0:01:49.412142667] [1355] ERROR Controls controls.cpp:990 Control 0x00000002 not found
[0:01:49.412485325] [1355]  INFO Camera camera.cpp:890 configuring streams: (0) 1920x1080-YUV420
[0:01:49.413498978] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 1500 (best 1500)
[0:01:49.413698146] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt RG10 Score: 3500 (best 1500)
[0:01:49.413783772] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG12 Score: 500 (best 500)
[0:01:49.413851585] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt RG12 Score: 2500 (best 500)
[0:01:49.413923981] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1000 (best 500)
[0:01:49.413991169] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt pRAA Score: 3000 (best 500)
[0:01:49.414068149] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRCC Score: 0 (best 0)
[0:01:49.414136014] [1359]  INFO RPI raspberrypi.cpp:122 Mode: 1280x720 fmt pRCC Score: 2000 (best 0)
[0:01:49.414240181] [1359]  INFO RPI raspberrypi.cpp:611 Sensor: /base/soc/i2c0mux/i2c@1/imx290@1a - Selected mode: 1920x1080-pRCC
[0:01:49.527162188] [1359] ERROR V4L2 v4l2_videodevice.cpp:1133 /dev/video14[17:cap]: Not enough buffers provided by V4L2VideoDevice
[0:01:49.529292410] [1359] ERROR RPI raspberrypi.cpp:788 Failed to allocate buffers
ERROR: *** failed to start camera ***

My /boot/config.txt:
dtoverlay=vc4-fkms-v3d,cma=512
max_framebuffers=2
framebuffer_priority=2
dtparam=i2cz_vc=on
dtoverlay=imx290,clock-frequency=74250000

GPU Memory set at 380
Thank you.

Hi, thanks for the extra information. I've had a go at reproducing the problem with those parameters but haven't so far been successful, the module - same or very similar to yours by the sound of it - just won't "not work". A couple of suggestions:

This morning I've been through a completely fresh install with the latest Pi OS and the raspberrypi/libcamera-apps instructions. uname -a reports Mar 15, and vcgencmd version reports Mar 19. The only changes to the default config.txt are to add the following to the [all] section:

dtoverlay=vc4-fkms-v3d
dtoverlay=imx290,clock-frequency=74250000

and it runs fine. Are you able to try this experiment and see if it works for you? You'd then be able to make your other alterations one at a time and hopefully spot when it goes wrong.

Can you get a stack trace for the segmentation fault? The fact that it then fails to allocate buffers after that also seems suspicious, I wonder if the kernel is getting unhappy. It might be worth checking dmesg, perhaps.

(Slightly unrelated: I think your cma syntax may be wrong, it should be cma-512 not cma=512. Having said that, 512MB sounds huge for a platform with only 1GB; it may even be harmful. Also 380MB sounds large for the gpu_mem. I realise of course that you may be running other software that needs this!)

Hi,
Will test out the experiment when free in the coming days.
I set the gpu_mem to 380MB because previously, it was at a lower value that made even the hello app not run at all. I simply randomly chose a memory value, and it just happened to work.
I also tried no cma previously. With or without, same results.

Can you get a stack trace for the segmentation fault? The fact that it then fails to allocate buffers after that also seems suspicious, I wonder if the kernel is getting unhappy. It might be worth checking dmesg, perhaps.

How do I get the stack trace? in dmesg?
Thanks for taking the time to look into this!

So to get a user space stack trace you'll have to run under gdb. Enter the following commands:
gdb libcamera-vid
run --width 1920 --height 1080
bt

(each command will take a while). The final one should print out a backtrace which you can post here.
In dmesg, just look for anything that contains contains lots of hex and looks really scary, especially anything that says "call trace" or something like that. But there may well be nothing, which would be worth knowing in itself.

Closing this since we have not heard back in a while.


sporadic travis failures

I just modified README.md, which triggered a build.  The build failed.
The issue is:
  1) server with a confirmable message should retry sending the response if it does not receive an ack four times before 45s:
      Uncaught AssertionError: expected 4 to deeply equal 5
      + expected - actual
      +5
      -4

      at /home/travis/build/mcollina/node-coap/test/server.js:624:29
      at Object.sinon.clock.callTimer (/home/travis/build/mcollina/node-coap/node_modules/sinon/lib/sinon/util/fake_timers.js:200:32)
      at Object.tick (/home/travis/build/mcollina/node-coap/node_modules/sinon/lib/sinon/util/fake_timers.js:145:28)
      at fastForward (/home/travis/build/mcollina/node-coap/test/server.js:51:11)
      at processImmediate [as _immediateCallback] (timers.js:363:15)
1``

I imagine this is just a timing issue, but I'm wondering if it's indicative of a code problem or simply a test problem.

I have been seeing this for quite some time, but had no time to
investigate. It's a time related test, which for their nature tend to have
false positives. I fear the latter case, anyway.
Il giorno dom 2 ago 2015 alle 21:09 Christopher Hiller <
<EMAIL_ADDRESS>ha scritto:

I just modified README.md, which triggered a build. The build failed
https://travis-ci.org/mcollina/node-coap/jobs/73797017#L403.
The issue is:

server with a confirmable message should retry sending the response if it does not receive an ack four times before 45s:
Uncaught AssertionError: expected 4 to deeply equal 5

expected - actual
+5
-4

at /home/travis/build/mcollina/node-coap/test/server.js:624:29
at Object.sinon.clock.callTimer (/home/travis/build/mcollina/node-coap/node_modules/sinon/lib/sinon/util/fake_timers.js:200:32)
at Object.tick (/home/travis/build/mcollina/node-coap/node_modules/sinon/lib/sinon/util/fake_timers.js:145:28)
at fastForward (/home/travis/build/mcollina/node-coap/test/server.js:51:11)
at processImmediate [as _immediateCallback] (timers.js:363:15)
1``

I imagine this is just a timing issue, but I'm wondering if it's indicative of a code problem or simply a test problem.
—
Reply to this email directly or view it on GitHub
https://github.com/mcollina/node-coap/issues/77.

just a wild guess: the tests use increasing udp ports - depending on the travis machine such a port could be in use, this the test fail? maybe use a fixed port?

it may be worth trying get-port.  if that doesn't work, there's always the retry option in .travis.yml

I think the cleanest solution would be mocking for all udp requests, when we wouldn't have any issues anymore. Adding more logic to the test setup is a waste of time in my eyes. What's your view on this issue?

get-port works for tcp.
The actual solution should be to use https://nodejs.org/api/dgram.html#dgram_socket_bind_port_address_callback without a fixed port (maybe 0 will do), and rewrite the tests to use that auto-discovered port instead.

can be closed, fixed with issue #104


Move .env to template.env

This is a convenience for developers. When developing and switching between branches it becomes easy to accidentally check in .env since there is a template .env file checked in.
Here we ignore .env and instead check in a file called template.env.
We do this for the docker-compose .env and for the web-ui.

This work was done by the Dae.mn Team. http://dae.mn/ml
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

template.env is now .env.template. In retrospect perhaps this would have been better as .template.env so that editors can pick the file type from the file extension. Happy to make that change if requested.


How to test it, i use the Usage  test code

yhzhao@X550JD:~/blockChain/btfxwss/tests$ ./mytest.py
from: can't read /var/mail/btfxwss
./mytest.py: line 7: syntax error near unexpected token `('
./mytest.py: line 7: `log = logging.getLogger(__name__)'

yhzhao@X550JD:~/blockChain/btfxwss/tests$ pip install btfxwss
Requirement already satisfied (use --upgrade to upgrade): btfxwss in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): websocket-client in /usr/local/lib/python2.7/dist-packages (from btfxwss)
Cleaning up...
yhzhao@X550JD:~/blockChain/btfxwss/tests$ python
Python 3.6.0 (default, Jan 13 2017, 00:00:00)
[GCC 4.8.4] on linux
Type "help", "copyright", "credits" or "license" for more information.

You have a syntax error in your code. Could you post it ? Running the code from the README.md works for me without issues.

yhzhao@X550JD:~/blockChain/btfxwss/tests$ ls
client_tests.py  logging  mytest.py  sys  test.py  time  unittest
yhzhao@X550JD:~/blockChain/btfxwss/tests$ chmod 777 test.py
yhzhao@X550JD:~/blockChain/btfxwss/tests$ ./test.py
from: can't read /var/mail/btfxwss
./test.py: line 7: syntax error near unexpected token (' ./test.py: line 7: log = logging.getLogger(name)'
`import logging
import time
import sys
from btfxwss import BtfxWss
log = logging.getLogger(name)
fh = logging.FileHandler('test.log')
fh.setLevel(logging.DEBUG)
sh = logging.StreamHandler(sys.stdout)
sh.setLevel(logging.DEBUG)
log.addHandler(sh)
log.addHandler(fh)
logging.basicConfig(level=logging.DEBUG, handlers=[fh, sh])
wss = BtfxWss()
wss.start()
while not wss.conn.connected.is_set():
time.sleep(1)
Subscribe to some channels
wss.subscribe_to_ticker('BTCUSD')
wss.subscribe_to_order_book('BTCUSD')
Do something else
t = time.time()
while time.time() - t < 10:
pass
Accessing data stored in BtfxWss:
ticker_q = wss.tickers('BTCUSD')  # returns a Queue object for the pair.
while not ticker_q.empty():
print(ticker_q.get())
Unsubscribing from channels:
wss.unsubscribe_from_ticker('BTCUSD')
wss.unsubscribe_from_order_book('BTCUSD')
Shutting down the client:
wss.stop()`

I installed  btfxwss  by pip3.
kint@ubuntu:~/blockCoin/btfxwss/tests$ python test.py
Traceback (most recent call last):
File "test.py", line 5, in
from btfxwss import BtfxWss
File "/usr/local/lib/python3.4/dist-packages/btfxwss/init.py", line 1, in
from btfxwss.client import BtfxWss
File "/usr/local/lib/python3.4/dist-packages/btfxwss/client.py", line 6, in
from btfxwss.connection import WebSocketConnection
File "/usr/local/lib/python3.4/dist-packages/btfxwss/connection.py", line 470
self.send(**q, auth=True)
^
SyntaxError: invalid syntax

This library requires python 3.5 or later. Earlier versions won't work.


Trailing "/" inconsistency for dat URLs

When indexing DBs, if you do:
async () = {
    await webdb.indexArchive('dat://232ac2ce8ad4ed80bd1b6de4cbea7d7b0cad1441fa62312c57a6088394717e41/');
console.log(await webdb.listSources());
}

You will see ["dat://232ac2ce8ad4ed80bd1b6de4cbea7d7b0cad1441fa62312c57a6088394717e41"] in your console (note, no trailing /).
If you do this:
...
console.log(webdb.isSource('dat://232ac2ce8ad4ed80bd1b6de4cbea7d7b0cad1441fa62312c57a6088394717e41/');
...

You will see false, because the / at the end is missing. It seems like isSource does an exact string match, when the thing that's important is the dat hash.
A little thing, but it was throwing me off for a bit :)
Any thoughts? It's simple enough, I might make another PR for this unless you have any objections...

Yeah that's not right. We should "normalize" the URLs as they get stored/passed into WebDB so that the trailing slash is consistent.


boards: Add Intel Raptor Lake P board

Add Intel Raptor Lake P board.

As discussed, please optimize Intel dtsi files. You can provide as another PR once this PR get merged.


Unexpected graduation year

In education background section:

Ph.D. in Computer Science, 2022(expected)
Duke University

While the expectation is by all means 2020, or earlier. 2022 is too self-deprecating.  It is inaccurate, and unacceptable.

Basically, 2020 is the expectation, 2022 is a loose upper bound, and hopefully 2019 is the reality.


Add aoc_2024

Repository URL
https://github.com/drdozer
Crate name
No response
Toolchain version
No response

Hey @drdozer, the workflow failed because the name of the repo is missing from the url.
You can close this issue and recreate one with the correct link:  https://github.com/drdozer/aoc_2024


Support writing the logs to stderr

Fixes #85.
Please review, cc @krazylek

@jsumners can you have a look here?

@mcollina I don't think this is affected by the extreme mode buffer flushing. _writableState doesn't track whether or not the backing file descriptor is blockable. Indeed, I pulled this patch into my feature branch and ran the tests. Everything is checking out just fine.

@jsumners the problem is that stderr do not have a _writableState, because it inherits directly from Stream.

It looks to have one to me:
> process.stderr
WriteStream {
  // *snip*
  _writableState:
   WritableState {
     objectMode: false,
     highWaterMark: 16384,
     needDrain: false,
     ending: false,
     ended: false,
     finished: false,
     decodeStrings: false,
     defaultEncoding: 'utf8',
     length: 0,
     writing: false,
     corked: 0,
     sync: true,
     bufferProcessing: false,
     onwrite: [Function],
     writecb: null,
     writelen: 0,
     bufferedRequest: null,
     lastBufferedRequest: null,
     pendingcb: 0,
     prefinished: false,
     errorEmitted: false,
     bufferedRequestCount: 0,
     corkedRequestsFree: CorkedRequest { next: null, entry: null, finish: [Function] } },
  writable: true,
  allowHalfOpen: false,
  destroyed: false,
  _bytesDispatched: 0,
  _sockname: null,
  _writev: null,
  _pendingData: null,
  _pendingEncoding: '',
  server: null,
  _server: null,
  columns: 130,
  rows: 50,
  _type: 'tty',
  fd: 2,
  _isStdio: true,
  destroySoon: [Function],
  destroy: [Function] }

I'm not clear what you want me to investigate here.

The original issue:
$ node a.js 2> out
SyncWriteStream {
  domain: null,
  _events: {},
  _eventsCount: 0,
  _maxListeners: undefined,
  fd: 2,
  writable: true,
  readable: false,
  autoClose: false,
  _type: 'fs',
  _isStdio: true,
  destroySoon: [Function],
  destroy: [Function] }

The content of a.js:
console.log(process.stderr)

As you see, it's our old friend SyncWriteStream.

I see. I'll dig into it soon and see what I can figure out.

@jsumners this is already passing, just check if it's ok for you.

Yep. The tests pass and the following does what you'd expect:
var pino = require('./')
var log = pino(process.stderr)
log.info(process.stderr)


user_data is not working in provisioning ec2 server

I trying to pass userdata while provisioning the ec2 server as per the below script. But user_data is not getting set to the machine .
my_dbag = data_bag_item('test','test-dbagitem')
cluster_array = my_dbag['cluster_name']
cluster_array.each {|cluster|
machine cluster do
  add_machine_options bootstrap_options: {
    subnet: my_dbag['subnet-id'],
    image_id: my_dbag['ami-id'],
    security_group_ids: my_dbag['security-group-ids'],
    key_name: my_dbag['security-keypair'],
    instance_type: my_dbag['instance-type'],
    user_data: "testcluster001"
   }
  tag cluster
  ohai_hints 'ec2' => '{}'
end
}

@manjukdvg What happens if you change add_machine_options to machine_options?

machine_options worked . Thanks a lot.

@manjukdvg Great!  I'm going to close this since we resolved the issue


feat(issue#793): Standalone PLT service module

Address https://github.com/platformatic/platformatic/issues/793

Thanks! I've left a couple of notes.

Thank you Matteo 🙏🏼 done


refactor(deps): Restructure into checks/

Addresses: https://github.com/aquasecurity/trivy/issues/5609

TODO: This will require relocation of the following

LGTM, but:
I think document-related commands can be deleted:
.PHONY: id
id:
	@go run ./cmd/id

.PHONY: docs
docs:
	go run ./cmd/avd_generator

.PHONY: docs-test
docs-test:
	go test -v ./cmd/avd_generator/...

LGTM, but:
I think document-related commands can be deleted:
.PHONY: id
id:
	@go run ./cmd/id

.PHONY: docs
docs:
	go run ./cmd/avd_generator

.PHONY: docs-test
docs-test:
	go test -v ./cmd/avd_generator/...

Yes I've moved them here https://github.com/aquasecurity/avd-generator/pull/79 - I will remove the targets from here.

TODO: This will require relocation of the following

As for the tests:

bundle_test.go was brought back https://github.com/aquasecurity/trivy-policies/pull/41/commits/be424204ba52d5cb7aab59e468a9dc41d60bd272
rules_test.go was moved here https://github.com/aquasecurity/avd-generator/pull/79/commits/143b1038a90b035a5e4c562e53a62a4c0408d2ba
I think we can scrap docker_test.go as I don't see much value in keeping it.


Raised actions from external components are not reaching the parent

I'm not sure if I'm doing something wrong, but I can't manage to thread messages from external components to the parent. I get no errors, but just silent fails so I'm having a hard time figuring out what's wrong.
I'm using version 0.2.0
Edit to add that if I build the examples they work correctly. There has to be something that I'm failing to see here (but that should give me an error :( )
I've reduced my code to a pretty simple case:
data Query a
  = HandleFormless (F.Message Query Form FormState) a
  | Typeahead TAMessage a

data TAQuery a = HandleSelect a

data TAMessage = SelectionsChanged

type ChildQuery = F.Query Query TAQuery Unit Form FormState Aff
type ChildSlot = Unit

component :: H.Component HH.HTML Query Input Void Aff
component =
  H.parentComponent
    { initialState: identity
    , render
    , eval
    , receiver: const Nothing
    }

   render :: State -> H.ParentHTML Query ChildQuery ChildSlot Aff
   render s = HH.div_
                    [ HH.slot unit F.Component { inputs, validators, submitter, render }
                      (HE.input HandleFormless)
                    ]

  eval :: Query ~> H.ParentDSL State Query ChildQuery ChildSlot Void Aff
  eval (Typeahead SelectionsChanged next) = next <$
    logShow "msg" -- <--- this is never called.

inputs ...
validators ...
submitter ...

render :: F.State Form FormState Aff -> F.HTML Query TAQuery Unit Form FormState Aff
render state = HH.div_ [ HH.slot unit tacomp unit
                                    (HE.input $ F.Raise <<< H.action <<< Typeahead)
                                  ]

tacomp :: H.Component HH.HTML TAQuery Unit TAMessage Aff
tacomp =
  H.component
    { initialState: identity
    , render
    , eval
    , receiver: const Nothing
    }

    where
      render :: Unit -> H.ComponentHTML TAQuery
      render st = HH.button [ HE.onClick $ HE.input_ HandleSelect
                            , HP.type_ HP.ButtonButton
                            ] [ HH.text "CLICK" ]

      eval :: TAQuery ~> H.ComponentDSL Unit TAQuery TAMessage Aff
      eval (HandleSelect next) = next <$ do
        logShow "Check" -- <-- gets logged
        H.raise $ SelectionsChanged

Hi @dariooddenino! I'm sorry for the late reply; I've been on vacation in Japan for the past two days and will be here for another week before I'm back on a normal working schedule. I have an inkling of what might be wrong, but I haven't recreated your example. If my comments below don't help, let me know and I'll dig a little deeper tomorrow on the train.

The short version: I believe you need to handle the Formless outputs, and specifically the Emit message with the top-level component query inside.
The longer version (forgive me if this is not your issue!):
In your render function for the typeahead, you're triggering HandleSelect when the "CLICK" button is clicked. Next, your eval function for the typeahead kicks in, logging "Check" and then raising the message SelectionsChanged.
What happens next? Well, messages are the outputs of a component which get handled by their parent, and the parent in this case is Formless.
Formless, unfortunately, has no idea what to do with a SelectionsChanged message. But you know how to handle it, because you have a query written for exactly that: your top-level component's Typeahead query. And Formless does know what to do with top-level component queries: it has the Raise query and related Emit message. You can take your top-level component's query type, wrap it up in Raise (to make it a Formless query), and then Formless will send that query back to you via the Emit message whenever it gets triggered.
You've done that in your code: your handler for the typeahead component inside Formless is (HE.input $ F.Raise <<< H.action <<< Typeahead). You wrap up the message in Typeahead (your top-level component's query type), then wrap that up in Raise (a Formless query type). Finally, this handler gets called.
The eval function in Formless handles this new Raise message. It unwraps it to get the top-level component query inside, then sends an Emit message containing the query to your top-level component. So we repeat the pattern!
Now we're in your top-level component. It should handle the Emit message from the Formless component by unwrapping it and evaluating the query inside (after all, the query inside is a top-level component query):
eval (HandleFormless (F.Emit query) a) = eval query *> pure a)

So we've unwrapped the query, which is Typeahead message a, and called eval on it. Now, finally, your eval function in the top-level component will evaluate the Typeahead query and logged out the message and the process is complete.

To learn more about how renderless components work, see this commented file from purescript-halogen-renderless (I promise to write about the topic soon!):
https://github.com/thomashoneyman/purescript-halogen-renderless/blob/master/example/Child.purs

Ugh, it's that for sure.
I spent 3 hours analyzing carefully all the examples, and I missed it all the time :(
I'm gonna kill myself.
Thanks!

Don't worry, it's not an obvious thing! Renderless components are a fairly new idea in Halogen and nothing has been written about them, though I gave a talk at LambdaConf this year that explains the concept. With only two examples of embedded parent queries and no real documentation it's an easy thing to miss. Rule of thumb: any time you use a renderless component like Select or Formless, go ahead and write your eval case for Emit first, handling the outputs recursively:
eval = case _ of
  HandleFormless message a -> case message of
    Emit query -> a <$ eval query

I'll add this to documentation soon :)

Is there a vod of the talk by any chance? :)

While it was recorded, the LambdaConf 2018 videos haven't been released yet. Sorry about that! They should be coming out at any moment now.


Various changes in the U.S. English translation file

As in the title, in this commit I made various changes in the U.S. English translation file. If you are wondering whether I did a reorganization or not, the answer is: no, I didn't :)
If you don't like some of my changes, please, let me know. I'm marking this PR as a draft, so we can freely discuss the changes. Furthermore, I can always update this PR via a force push to preserve a clean commit history.
Also, this PR is either blocked by CF#204 or some of the new button labels must be shortened.

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

Oh, make sure you open the file (link) because it doesn't show the comments I replied to here, which sucks.

Thank you. I really like and appreciate your work, so I try to help as I can.
And I said bye bye to the merge conflicts, but it doesn't really matter, as this PR is still not ready to be merged.

Thank you for going through the review!
I replied to some stuff.
The conflicts should be minimal I think, so no big worries there.

For me, you can do breaking changes at any time. Sometimes the GitHub web interface is not very helpful, but I use Git Bash for resolving merge conflicts anyway.

I answered your other questions as well, so if you would like to reply to them, please scroll up and don't go to the "Files changed" tab, as this time GitHub hides some threads there.

I answered your other questions as well, so if you would like to reply to them, please scroll up and don't go to the "Files changed" tab, as this time GitHub hides some threads there.

Thank you very much and sorry for not replying sooner!
I have replied to your comments (hopefully all).

No problem. It's rather a parallel project I work on when I have enough free time and you can freely do so as well.

I would like to ask you to review the changes in the latest commit, and tell me what you think about them.

Overall the changes seem great! Thank you very much.
I added a couple of comments to the last 2 commits.

Could you please answer my questions that haven't been answered yet? Only a few of them remain.

Could you please answer my questions that haven't been answered yet? Only a few of them remain.

Yeah, sorry for taking so long! I think that should be all of them.

Turns out I have missed some conversations. I think now it should be all of them!

Thanks. That's good news.

So, what do you think?
Seems pretty much perfect to me. Only two unfinished lines here.

Well, the work is almost done.
Unfortunately two people have already done translations based on the old U.S. English one. Oh, and I have also this project, which now needs to be rebased on top of the current master. But no problems other than these three.

Don't worry about people translating the old file. It's not 2 people, it's every translation file. You're not changing the meaning of things, so it shouldn't be a problem. It's never a word by word translation anyway.

As we are near the end, what commit message would you like to have in the Git commit history?

Just put something that makes sense. I'm pretty sure I can change it anyway.

I think this pull request is now ready for a final review(s).

Looks great! Thank you very much for your contribution. I really appreciate it. Sorry for taking so long. Went through it all again and couldn't really find anything I was unhappy with. So, if you are also happy with it, then let me know and I'll merge it :)

Thank you for your help and your time. It was a long journey. I have no additional comments, so if you think it's ready to be merged, feel free to do so.

Awesome, thank you!


Add waiting time before applying manual remediation

Applying remediation right after Pool is ready might cause some issues, hence let's add some wait before it applies the remediation.
And also keep the IdP no matter the test's state, so we can have the log.
Change the Idp test-route termination to passthrough, as we need to provide cert for re-encrypt termination

/retest

/test all

/test all

/retest

Just one question (but the tests pass, so ack), did we end up patching the vendor/ files manually?

Oops, just saw that, should I patch the route in e2e_test.go instead?

Just one question (but the tests pass, so ack), did we end up patching the vendor/ files manually?

Oops, just saw that, should I patch the route in e2e_test.go instead?

I think patching vendor can be fine, but it would be nice to mention in the commit message.I normally skip reading patches to anything under vendor/ but I was surprised to see a PR touching vendor/ but neither go.mod or go.sum. Is there a reason to actually not bump the dep instead?

If the vendor changes are a patch from upstream, we should bump the dependencies -- if it's a custom patch then we can carry it but normally the convention would be to have the patch as a diff in our repo, and then it gets applied during build (similar to patches carried for a RPM spec)

If the vendor changes are a patch from upstream, we should bump the dependencies -- if it's a custom patch then we can carry it but normally the convention would be to have the patch as a diff in our repo, and then it gets applied during build (similar to patches carried for a RPM spec)

Thanks for the advice on using the git patch, I just converted the commit to a patch instead.

/retest


Add 4.x branch

I believe I have the shader converted for version 4.x. I still need to do some testing to make sure I didn't break anything.
I'd like to merge this in, but I think you might have to add a 4.x branch first? I'm not sure how to merge in an entire new branch from a PR, if it's possible at all.
Up to you whether to call the new branch 4.x, 4.3, or main/master. Once the branch is up I can PR against it sometime today or tomorrow, and if you want to review the exact changes you're welcome to

Works in Forward+, Compatibility, and Mobile.

Adjusted shader to work in 4.x. I have only tested in 4.3, but it looks like reverse-z doesn't actually affect this, so it might work in 4.2 as well. If it's all the same to you, 4.3 can be the minimum version. If not, I can try testing in 4.2 (and maybe 4.1?).

Cleaned up the shader, removing unneeded matrix varyings.

Fixed the rotation behavior at certain angles. At least, it looks better to my eyes? Some of your original matrix math is a little beyond me.

Fixed at least one precision bug, causing pixelated caustics due to mediump. There is a lot of mediump left, and the caustics still maybe have some banding/precision issues if you zoom in, but it looks generally fine. If I tackle that it should be in a followup commit.

Added some sliders for the caustics parameters. Changed the shader default values to match the look of the existing tweaked values. Sliders are set to powers of two where possible, and the range is set as what looks nice artistically + one more power of two in either direction:

I did not rename variables much. My preferred naming convention for shaders that get shared is more verbose, but I didn't want to change too much for no reason.

Still working out some edge cases, actually. The lighting function in 4.x seemed to change, so I can't use the same setup of ALBEDO and render_mode as in 3.x, and I haven't found the right setup in 4.x. I keep getting a dim outline of the bounding box.
Also: OmniLights? It looks like the original unity shader supports a single directional light, passed in. Your 3.5 version supports multiple directional lights, by using LIGHT in the light() function. Was your original version ever meant to work with omni lights? The shader doesn't check to see if the LIGHT is directional, which produces funny results with point lights.

I imagine this could be dealt with in userspace just by using a specific cull mask for the caustics lights. But I can also use LIGHT_IS_DIRECTIONAL to only apply the shader to directional lights.
Thanks for any guidance, I also understand if you don't want to think too much about a two year old codebase

Hey @tetrapod00! Thank you so much for doing this :D now regarding the branch: I have created a 4.3+ branch now you can make a PR against. I definitely appreciate it that you took the time for this. Regarding your changes: They look really great and I would be happy to review it. About the OmniLight support: There was never any support planned. Not really sure if it is even possible to make it look nice.

Yeah, happy to help update this. I thought about doing it when I converted the shader the first time, but once I had to do it twice it should just be done as a PR.

Closing as of #2 being merged now. Thanks again for your work on this!


Add the Cinny client.

Sorry about my awful code -- I'm very new to JavaScript.

I am so sorry; didn't expect this to take so long on my end.

can this be merged?

For some reason all the image files have been updated.
/src/open/clients/index.js should be updated too, so Cinny is added to the list of clients

I guess I'll just do my own PR unless OP, who seems to be inactive, fixes the files before me (@FieryMewtwo)

Duplicate of #286


Add go get to Readme

You definitely know more about golang than me, so this might not be the correct thing to do. On my machine, I just needed to go get before the installation took place.

I think that is necessary for fresh installs. Good catch... thanks!


Allow inserting text presets by drag and drop (Moveable)

Feature Description
Currently, other elements can all be added to the page by dragging and dropping in addition to just clicking on the element.
Text presets, however, can only be added by clicking. For consistency, we should also allow dragging presets onto the page.

Alternatives Considered

Additional Context
Note that this will influence the smart text color feature since the color calculation needs to be done once dropped.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

cc @barklund For prioritisation.

Verified in QA


tutorial doesn't work @microsoft/microsoft-graph-sdk

Trying to follow this tutorial, however two issues arise:

One of the dependencies does not appear to exist in the registry, so cannot download, and get error message.
@microsoft/microsoft-graph-sdk

While it is common to need to sign up for a developer account to get an app registration to be able to follow a tutorial, it is not common for that account to require credit card details. You should provide a test/trial account for people who are not using the app registration for commercial purposes. And no, the student option doesn't help - many people who are learning don't meet your criteria for student accounts.

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

ID: 513e58c2-8752-9286-415e-b3dc1e5fba54
Version Independent ID: b9a6ea0d-8eac-42b7-0a48-387ca491e6ea
Content: Tutorial: Sign in users and call the Microsoft Graph API in an Electron desktop app - Microsoft Entra
Content Source: articles/active-directory/develop/tutorial-v2-nodejs-desktop.md
Service: active-directory
Sub-service: develop
GitHub Login: @cilwerner
Microsoft Alias: cwerner

@lucitemple
Thanks for your feedback! We will investigate and update as appropriate.

@lucitemple
I'm going to assign this to the document author so they can take a look at it accordingly.
@cilwerner
Can you please check and add your comments on this doc update request as applicable.

Hi @SaibabaBalapur-MSFT, sure thing. I've recently attained ownership of this article, so will set aside some time to get it working.

@lucitemple, I've checked with the software team and the package you should use is @microsoft/microsoft-graph-client, I've tested the npm install and it works, so I will correct that in a pull request which I will link in the next comment.
There's a couple of additional items that need fixing which I will also address, however that's the main hurdle solved for you!
I'll keep the issue open for the moment to make sure you can get it working.


License

Hi, I would like to implement your library into a project of mine. Would you mind adding a license to this project? I can do it if you like, just let me know which one you want and I'll do a PR.

MIT license or similar would do.
BTW recently I found a way to do ECDSA in CL, at least the math is there. But getting it all together would take considerably time, and I'm not that interested anymore...

Ok ill add it when soon when I have time. For the ecc I have contributed to cl-ecc (https://github.com/krkhan/cl-ecc https://github.com/krkhan/cl-ecc) and added  the secp256k1 curve. It should be able to do bitcoin ecc - not secure or anything but it works. Im currently working on som bitcoin tools for cl and will put it on github when I feel there is something to show.

On 08 Mar 2016, at 10:16, killerstorm<EMAIL_ADDRESS>wrote:
MIT license or similar would do.
BTW recently I found a way to do ECDSA in CL, at least the math is there. But getting it all together would take considerably time, and I'm not that interested anymore...
—
Reply to this email directly or view it on GitHub https://github.com/killerstorm/cl-coin/issues/1#issuecomment-193682976.


question about onRendered vs rendered: chapter 9.5

I was curious is there a difference when creating the errors package in the original helpers/errors.js file Template.errors.onRendered is used and then in the package code /errors_list.js  Template.meteorErrors.rendered is used.
I couldn't find anything in the meteor documentation regarding "rendered" but read on stackoverflow that from version 1.04 rendered has been renamed to onRendered.
Sorry trying to figure out what the difference is, it seems like they both work but that onRendered is the preferred name going forward.

rendered was the old way, and onRendered() is the new way; but I have found that some packages expect rendered and some expect onRendered(). For me at least, they are not interchangeable, despite what others may say.

okay cool, thanks.. Do you think expectation is due to what meteor version is being used? So if it's Meteor 0.9 then  .rendered is expected, but if that package was written after 1.04 then .onRendered.
Thanks just trying to wrap my brain around it.


VPN Cannot Connect Client to Telegram

Issue Report: VPN Cannot Connect Client to Telegram
Repository: bepass-org/warp-plus
Issue Title: VPN Cannot Connect Client to Telegram
Description:
I am experiencing an issue with the warp-plus VPN service where it fails to connect the client to Telegram. Despite successfully establishing a VPN connection, Telegram remains inaccessible. Below are the details of the problem:
Steps to Reproduce:

Install and set up warp-plus VPN following the instructions provided in the repository.
Connect to the VPN.
Attempt to access Telegram.

Expected Behavior:
Telegram should be accessible once the VPN connection is established.
Actual Behavior:
Telegram fails to connect, displaying a network error.
Additional Information:

**VPN Version:**v1.2.3
Operating System: Ubuntu 22.04 LTS
Telegram Version: 5.2.3

Potential Cause:
It is possible that the VPN is not routing traffic correctly for Telegram or there may be an issue with the VPN server's ability to handle Telegram's network requirements.
Request for Assistance:
Could you please investigate this issue and provide guidance on how to resolve it? Any suggestions or fixes would be greatly appreciated.
Thank you for your attention to this matter. I look forward to your response.

If you need any further information or assistance in reproducing this issue, please let me know.
Best regards,
Farokh

Duplicate of #65


Bias synonym creation towards id usage in the current function

There is little point creating a synonym of an id %x at a particular program point if there are no uses of %x dominated by that program point, because the synonym will not be usable in a replacement.
Find a way to bias the synonym creator in this respect.

@Vasniktel This is a fairly vague issue, but it's one example of something that could be approached using the kind of DecisionMaker class we have been talking about.


feat(pixels): add my new pixel (36, 0)

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

wrong branch, sorry, requesting a new pr correctly


bannertool and makerom are not compatible with Windows

The binaries for bannertool and makerom that are included do not work on Windows. Please include Windows binaries.
EDIT: Also, first. :trollface:

Working out some other issues right now, but I'll make sure to include some Windows binaries when I can get around to it.

Okay, thanks. I can't get bannertool to compile though, so can you please post a Windows binary? (To clarify, I can get it to compile, but it gives me this error message whenever I try to use it with your template makefile:

The procedure entry point __gxx_personality_v0 could not be located in the dynamic link library d:\Users\Flarn\Desktop\3DS_stuff\WorldOf3DSand\tools\bannertool.exe.

I added Windows binaries, and the Makefile should automatically detect that you're on Windows and use them. Let me know if it works or not.

Okay, first off: the makefile doesn't work properly on Windows. I see you're trying to add ".exe" to the end of the variables when it detects you're running Windows, but for some reason it adds a space first, so what it actually does is attempt to load the Linux versions with ".exe" as its first parameter. This code works fine on Windows, and should on Linux as well:
ifeq ($(OS),Windows_NT)
	MAKEROM    = $(TOPDIR)/tools/makerom.exe
	BANNERTOOL = $(TOPDIR)/tools/bannertool.exe
else
	MAKEROM    = $(TOPDIR)/tools/makerom
	BANNERTOOL = $(TOPDIR)/tools/bannertool
endif

The CIA version works fine, if it's supposed to display a black screen when you run it. (Which usually wouldn't be the case, but given that this is only a template, I wouldn't be at all surprised.) However, when you go to "unwrap" the icon, and also when it's suspended, its name shows up like this:

The .3DS version doesn't work, however. It shows up properly in the Gateway menu (though the ".3ds" extension is visible), and selecting it does cause it to appear as if it is inserted as a cartridge. However, when I attempt to load it, it gives me a black screen saying the game card was removed, and sends me back to sysnand.
Also, why is bannertool.exe 7 megabytes? It just doesn't seem like it would need to be that big.

The Makefile variable problem is now fixed in the repo.
You are correct in assuming that the black screen is because its a template. I'll add a hello world message in now just to make it clear that it works.
bannertool.exe is probably 7 megabytes because I statically linked the required libraries into it to avoid errors like the one you were having when compiling it.
I have to go out for a bit now, so I'll look into why the .3DS version isn't working and why the text shows up wrong when I get back.

Actually, the text issue was fairly simple, so it should be fixed now.

Yep, it was fixed. But I'm still getting the problem where the .3DS doesn't load.

Can you try this 3DS file and see if it works: https://www.dropbox.com/s/fwl86wyyzw5q5lc/Worldof3DSand.3ds?dl=0
(I don't have a Gateway or anything of that sort to test it with.)

That works!

Should be all fixed in the source repo then. Let me know if compiling it yourself works and I'll close the issue.

It gives me that same error with the broken text when I use the .3DS version and suspend it with Home.

That's strange... there should be a file named "icon.icn" in the build folder of the project after running make, can you upload and link it here?

http://www.filedropper.com/showdownload.php/icon_5
Also, I just deleted the folder and redownloaded the ZIP file, so make clean wouldn't have been necessary, right?

Yeah, it shouldn't be a problem then. I just headed off to bed, so I'll make sure to take a look and figure it out as soon as I can tomorrow.

Hmm... not to sure why that would happen. The icon file looks alright.
For what its worth, I've updated things a bit, so you can try building again and see what happens.

It's still giving me the same problem with the .3DS file.

Can you post a screenshot or something of the problem, specifically when using the 3DS version?

Also, notice that "◙Y: 67" in the corner. That's a bug in the screen_draw_string function where \n isn't handled properly. Should I create a separate issue for that or is that enough information?

Does the title show correctly when the icon is selected in the home menu? (If you set the layout to 1 row of icons, it shows a title and author above the selected icon.)
Also, I'll go ahead and fix that newline issue.

Nope, shows up the same. Also, I edited icon.png, which shows up fine in the Gateway menu, but not on the cartridge image.

Oh, one more thing you might want to be aware of: I edited AppInfo to say the following:
APP_TITLE = Bouncing Square
APP_DESCRIPTION = Title says it all.
APP_AUTHOR = flarn2006
APP_PRODUCT_CODE = BouncingSquare
APP_UNIQUE_ID = 0xF1337

Then when I built and installed the CIA, it didn't show up as an icon in the Home Menu, or in the dev menu. Though if I try to install it again, it says it's already installed.

There was an issue not too long ago with the icon generation that caused that... is that with the latest commit?

Well latest as of about a half an hour ago; I see you fixed the newline issue I mentioned but I haven't tested it with that yet.

Does the CIA version show the title properly?

Yes, and the icon as well.

Actually I don't know what I did differently, but I just built a different .3ds and the text worked fine.
Here's the icon.icn.

So... everything is good then? Titles and icons are showing up fine on both 3DS and CIA files?

Well it seems with .3DS it only happens sometimes. It didn't work before, but then it did later.

Since it seems to be working for you now and it's working fine in my testing, I'll go ahead and close this issue.


[Feature]: global tool registration

Description of the new feature / enhancement
Add a command that registers npm  -g i <package>  commands to run after installing a new version of  node so that yarn and such are installed globally again for that version.
Scenario when this would be used?
nvm instal lts
nvm use lts -reinstall-globals

Or even by default and add a switch to not do it.  If use detects switching between different versions it runs the registered global installs.  This way I don't have to keep reinstalling my global packages each version change.  I will know yarn and gulp and whatnot are installed.
Supporting information
No response

Could also just do a global list from nom and reinstall from the current version before a use does the switching.

This will not be coming to NVM4W due to the feature freeze. There is a hook system in Runtime that supports the ability to install/link packages and respond to other events (like install). I'm not marking this as consider for rt because  the purpose of tagging issues that way is to make sure we don't lose them while building Runtime. Since we're already building this feature into Runtime, it'd be redundant.

Thanks for the update.


mac os build broken

Hi @conda-forge/core,
Please move the mac os build of my package osx-64/healpy-1.12.2-py36h7127e17_0.tar.bz2
from main to broken on the conda-forge channel on anaconda.org
because:
It doesn't even import, not sure how circleci uploaded it to anaconda.org as it failed the unit tests.

Yep! Definitely broken 😄

Sorry for the delay -- which versions do you want removed? Just that specific build for mac or all builds for mac that are 1.12.x or something else?

just that one, it is the only one that was built for 1.12.x

Done!


"Edit Title" of card in the list view and "Edit Description" of card's tasks - clicking sometimes does not work

Clicking on "Edit Title" to edit the title of the card on the list view:

And "Edit Description" of card's tasks:

Sometimes requires to click multiple times to open the edit popup.
Known cases:
Clicking either edits while having simultaneously opened Edit List field seems one of the causes of the issue
its probable that the error is coming from useClossableForm

@wilkobyl Please test the fix

fixed