Slow results

I have recoded my program from multiprocessing to mpire however the program seems very slow when compared to multiprocessing.
Mpire Code
chunk_size_db = 1000000
        input_table_chunks = read_psql_as_chunks.read_psql_chunks(input_engine, input_table_name, master_id,
                                                                  master_phone_1_column, master_phone_2_column,
                                                                  master_phone_3_column, chunk_size_db)
        # Process each chunk
        for input_df_chunk in input_table_chunks:
            print(f"Now working with the db {master_tb}")
            # Divide the emails into batches (e.g., batches of 10)
            batch_size = 100000
            email_batches = [
                (input_df_chunk['id'][i:i + batch_size], input_df_chunk[input_column_name][i:i + batch_size]) for i in
                range(0, len(input_df_chunk[input_column_name]), batch_size)]
            # Process the emails in batches
            for input_id_batch, email_batch in email_batches:
                finder_args = [{
                    'input_email': email,
                    'input_id_val': input_id_val,
                    'df_master': df_master.columns,
                    'db_host': db_host,
                    'db_user': db_user,
                    'db_password': db_password,
                    'database_name_output': output_database_name,
                    'input_table_name': input_table_name,
                    'input_column_name': input_column_name,
                    'master_id': master_id,
                    'master_tb': master_tb,
                    'master_database': master_databse,
                    'input_database_name': input_database_name,
                    'row_master': row_master,
                    'output_table_name': output_table_name,
                    'master_email_column': master_email_column,
                    'row': row,
                    'phone_columns': phone_columns,
                    'search_type': search_type,
                } for input_id_val, email in zip(input_id_batch, email_batch)]
                list_df = make_single_arguments(finder_args, generator=False)
                with WorkerPool(
                        n_jobs=16, start_method="threading", use_worker_state=True, keep_alive=True
                ) as pool:
                    results = pool.map(
                        main_logic.finder, list_df,
                        worker_init=init_db_conn,
                        worker_exit=close_db_conn, n_splits=10, chunk_size=10000
                    )

Multiprocessing code:

chunk_size = 10
        input_table_chunks = read_psql_as_chunks.read_psql_chunks(input_engine, input_table_name, master_id, master_phone_1_column, master_phone_2_column, master_phone_3_column, chunk_size)
        # Process each chunk
        for input_df_chunk in input_table_chunks:
            print(f"Now working with the db {master_tb}")
            # Use the pool to process rows in parallel
            pool = Pool(processes=1)  # You can adjust the number of processes as needed

            # Divide the emails into batches (e.g., batches of 10)
            batch_size =1
            email_batches = [(input_df_chunk['id'][i:i + batch_size], input_df_chunk[input_column_name][i:i + batch_size]) for i in
                range(0, len(input_df_chunk[input_column_name]), batch_size)]
            # Process the emails in batches
            for input_id_batch, email_batch in email_batches:
                arg_tuples = [(email, input_id_val, df_master.columns, db_host, db_user, db_password,
                               output_database_name, input_table_name,
                               input_column_name,
                               master_id,
                               master_tb, master_databse, input_database_name,
                               row_master,
                               output_table_name, master_email_column, row, phone_columns, search_type) for
                              input_id_val, email in zip(input_id_batch, email_batch)]

                results = pool.map(main_logic.finder, arg_tuples)

In multiprocessing to execute my program it takes 0.04 avg in Mpire it takes 0.6 am I missing something?
My finder function is doing database operationgs simple select and update.

Hey thanks, I found the issue. I have used gc.collect() in my main logic its taking time to do the job. Now its faster 0.001 sec.. Tx


Update to latest Openshift Rest Client

starting the move to the new openshift rest client
connects to #290

Pull Request Test Coverage Report for Build 761

71 of 83 (85.54%)  changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 96.76%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/helpers.js
3
6
50.0%

lib/build-watcher.js
0
9
0.0%

Totals

Change from base Build 24:
-0.06%

Covered Lines:
637

Relevant Lines:
661

💛  - Coveralls


Change server updates to ignore missing attributes

The majority of the change is converting the simple:
this._data = jsonApiResource.attributes to a whole _mergeUpdates function, which considers each key.
We need the function, because simple assignment (ala this._data = attributes) will overwrite everything and Object.assign(this._data, attributes) will overwrite nested models (which we want to actually delegate).

Added the handling of different type and ids for a nested model. It is a separate commit for easier review.


ImportError: cannot import name 'force_fp32' from 'mmcv.runner'

(open-mmlab) fsr@titanxp:~/FoveaBox-01$ python tools/train.py configs/foveabox/fovea_r50_fpn_gfl.py
Traceback (most recent call last):
File "tools/train.py", line 9, in
from mmdet.apis import (get_root_logger, init_dist, set_random_seed,
File "/home/fsr/FoveaBox-01/mmdet/apis/init.py", line 2, in
from .inference import (inference_detector, init_detector, show_result,
File "/home/fsr/FoveaBox-01/mmdet/apis/inference.py", line 13, in
from mmdet.models import build_detector
File "/home/fsr/FoveaBox-01/mmdet/models/init.py", line 1, in
from .anchor_heads import *  # noqa: F401,F403
File "/home/fsr/FoveaBox-01/mmdet/models/anchor_heads/init.py", line 10, in
from .gfl_head import Integral, GFLHead
File "/home/fsr/FoveaBox-01/mmdet/models/anchor_heads/gfl_head.py", line 5, in
ImportError: cannot import name 'force_fp32' from 'mmcv.runner' (/home/fsr/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/runner/init.py)

我也遇到了相同的问题，请问您解决了吗？

I have same question,
My envs is mmcv 2.0.0+cu11.8+torch2.1
I think this is a version problem, but I cannot solve it

我已收到，。

I use the "from mmcv.runner.fp16_utils import force_fp32" to replace "from mmcv.runner import force_fp32", and the problem solved.


kinit fix, remove click

There is a chance that no kerberos ticket exists before this function is called
click is installed from doozer

Tested in dev, merging.

Test Message


ROS2 crashed after CMAKE upgrade

Nvblox requires CMAKE version > 3.22. Jetpack5.1.3 came with 3.16. May need to upgrade cmake the first thing after Jetpack flashing. Check this post for upgrade cmake.

This answer infers I may need to use cmake 3.22.6


Implement the other cursorBoxes

I think this is referring to the blue boxes that show up on connected entities:

Blue for electrically connected entities,
2, White boxes that show up on inserter connected entities (and the yellow triangles indicating inserter direction)
Green boxes on corresponding underground entities.

Is this correct?
If so, I think a precursor would be a system to record those connections. I think it would make sense to keep track of those connections separate from the display of the cursors. That way the connection information could also be used for the throughput/bottleneck detector, displaying the "unplugged" warning sign etc.
Maybe this connection recording system is already in place, but given how the underground highlighting code is written my guess is that it's not storring that connection information anywhere.

I have just implemented nr3 in 01123339e5fc49a6b806c5fc728efe3eadc37ad6 and I'm currently getting the copy/paste of entity settings (green cursorBox around source entity).
I don't think we would need to keep track of those connections. The needed position data is in G.bp.entityPositionGrid. I guess it would be helpful in the future for the "unplugged" warning sign but haven't thought how that would work yet.
I feel like there is logic code everywhere - as the project progressed, it got out of hand and I'm looking into refactoring it using an ECS (Entity Component System). Not sure when or if I will do it but ECS looks quite interesting. This is not really related to this issue but it's just something that is bothering me. :)

A few cursor boxes were missing from your comment so I made a check list in the issue body that you can refer to.


Removed === compare, changed to ==

Compare by value and type (===) does not work for this algorithm, as both cd and cdv can be either types at the same time. By comparing by value only (==) cd and cdv can be either integer or string, as a string number will be converted to a number reqardless of type.
Relates to BUG: https://github.com/jquery-validation/jquery-validation/issues/2459

I've rewritten the for loop, and removed the nested loop, different commit on my branch.
Will create a test.

Code is better now, removed nested for loop with an array index lookup.
Created test cases, added to the test/index file, and created a separate additional vinUS.js test file.

Thanks :heart:


feat: add support for dry run/check command arg

First time submitting to an open-source project as a maintainer, so happy to learn and read the manual if I missed anything.

[x] bump to .travis.yml to run latest version of Node
[x] updated documentation
[x] tests passed successfully
[ ] tested locally with `npm-link´

@macobo not sure if you are still involved/want to be involved. do let me know if you're not!
... if you are, would appreciate a sanity check.
tested this feature locally with npm linkwith this tiny test repo: https://github.com/minademian/test-repos/tree/master/node-ansible/dryrun
output looks good:
$ node index.js
Exit code:  0
[DEPRECATION WARNING]: DEFAULT_SUDO_FLAGS option, In favor of Ansible Become,
which is a generic framework. See become_flags. , use become instead. This
feature will be removed in version 2.8. Deprecation warnings can be disabled by
 setting deprecation_warnings=False in ansible.cfg.

PLAY [localhost] ***************************************************************

TASK [Gathering Facts] *********************************************************
ok: [localhost]

TASK [Ensure project directory exists.] ****************************************
skipping: [localhost]

TASK [Ensure main directory exists.] *******************************************
skipping: [localhost]

TASK [create directory] ********************************************************
skipping: [localhost]

PLAY RECAP *********************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=0


Dependent child handling missing from links

Need to do dependent child link and satellite, but it seems to impossible to add link unhashed keys that are not described as hub's.
It should be possible to add for example invoice line numbers in link that has only invoice hub. Line number should be unhashed but should be included to link hashkey. Invoice line satellite should be linked to link and not hub.
I tried to add the line number as hashed key in link, but it seems that it requires always hub.

Hi! Thanks for this request. This should already be supported. A Link's src_fk field can be provided whatever column names you like as long as they are in the staging table your are sourcing from. Can i ask if you're getting any errors or if there's any further information to help us understand the issue please? Thanks

It could be beneficial if in documentation there should be some word about this dependent child structure handling in automateDV because is quite essential feature to get the DataVault model to work together with different source systems.


chore(net): support multiple eth protocol versions.

Closes #1101
Motivation

we're announcing support for eth66/67 by default in Hello but only check for a single version in the eth Status handshake

Direction

we add a list of versions as a separate parameter to the handshake function

Alternative idea to direction

overwrite SharedCapability::Eth.version to Status.version

Note

geth negotiates eth protocol and it selects highest version.
https://github.com/ethereum/go-ethereum/blob/d0a4989a8def7e6bad182d1513e8d4a093c1672d/cmd/devp2p/internal/ethtest/helpers.go#L130-L132
We also already have the same logic at
https://github.com/paradigmxyz/reth/blob/a55e7fd9b5b40acce3030a9366285947455138be/crates/net/eth-wire/src/p2pstream.rs#L562-L567
With this simple change, I'm success to handshake w/ Eth66.
I expect it might mitigate the MismatchedProtocolVersion issue before #791 is completed.

please add a test for this, agree with the fix, testing the PR now

follow it up w/ b4d688081dee7352f3154147275302b506fab20f

Codecov Report

Merging #1152 (b4d6880) into main (a55e7fd) will increase coverage by 0.51%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1152      +/-   ##
==========================================
+ Coverage   74.75%   75.27%   +0.51%
==========================================
  Files         333      335       +2
  Lines       35442    36373     +931
==========================================
+ Hits        26495    27380     +885
- Misses       8947     8993      +46

Flag
Coverage Δ

unit-tests
75.27% <100.00%> (+0.51%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/net/network/src/session/mod.rs
68.75% <ø> (+0.06%)
:arrow_up:

crates/net/network/src/test_utils/testnet.rs
88.20% <100.00%> (+0.92%)
:arrow_up:

crates/transaction-pool/src/test_utils/mock.rs
51.77% <0.00%> (-6.74%)
:arrow_down:

crates/executor/src/revm_wrap.rs
38.21% <0.00%> (-1.79%)
:arrow_down:

crates/net/network/src/session/active.rs
85.90% <0.00%> (-1.00%)
:arrow_down:

crates/primitives/src/transaction/mod.rs
89.29% <0.00%> (-0.54%)
:arrow_down:

crates/transaction-pool/src/pool/txpool.rs
58.82% <0.00%> (-0.51%)
:arrow_down:

crates/stages/src/stages/bodies.rs
92.68% <0.00%> (-0.45%)
:arrow_down:

crates/stages/src/stages/execution.rs
92.04% <0.00%> (-0.14%)
:arrow_down:

crates/executor/src/executor.rs
93.76% <0.00%> (-0.13%)
:arrow_down:

... and 27 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Unused branches

There are 8 branches in this repository, 1 of which is actually being used. All the others are 500 - 1100 commits behind and 2 of them contain 1 'new' commit.
Is there a reason these branches are being kept? To me they just seem like unnecessary clutter.

Yep, they were completely unused and merged. I've deleted them.

newspritebatch was pretty cool. I copied the api for FlexBatch. It solves the problem of all the crazy draw overload by using a builder pattern.

Do you think we should restore it? I doubt anyone will have much benefit from it, especially if you've taken over the ideas in an extension for everyone to use.

Oh, no, sorry, I was just commenting. It's not something we would ever consider merging because it would be such a major API change.


SampleApp Discoball Endpoint example can be controlled by Alexa App but not by voice commands.

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
After following this tutorial, compilation succeeds, "Discoball" is aknowledged by my other devices and appears in Android Alexa App.
I can interact with the device states (on, off, change color, set speed) successfully using the App, and the corresponding onDirective and debug logs appear at SampleApp's console .
However, the only voice command that work is the turn on/off command. If I say for example (exactly as the tutorial video at 5min45s) "Alexa, set Discoball to red", the answer is "Discoball doesn't support that". Same for speed command.
Since I can control all Discoball's features (Power/Mode/Range) using the Android Alexa App (and console prints the command being executed), I assume Endpoints are set and exposed correctly, but I cannot figure out why only Power interface voice command is accepted.
Tried on Raspberry Pi and MacOS with the same result (compiled natively on both devices).
What is the expected behavior?
Power/Mode/Range/Toggle voice commands should work according to the tutorial.
What behavior are you observing?
Only Power (turn on/off, activate...) voice commands are being recognized.
Provide the steps to reproduce the issue, if applicable:
Followed the tutorial from Device Makers Amazon Blog, also linked at this issue's summary.
After unsuccessful results, in a second try I've added PT_BR  friendly names along with the default EN_US for all resources that had a friendly name (I live in Brazil), and tried setting my device language to English first and then Portuguese. Both tests had the same result with commands in English and Portuguese.
Tell us about your environment:
CMake command:
cmake /Users/marloschida/MacLexa/1.17/source/avs-device-sdk
-DGSTREAMER_MEDIA_PLAYER=ON
-DCURL_LIBRARY=/usr/local/opt/curl-openssl/lib/libcurl.dylib
-DCURL_INCLUDE_DIR=/usr/local/opt/curl-openssl/include
-DPORTAUDIO=ON
-DPORTAUDIO_LIB_PATH=/Users/marloschida/MacLexa/third-party/portaudio/lib/.libs/libportaudio.a \
-DPORTAUDIO_INCLUDE_DIR=/Users/marloschida/MacLexa/third-party/portaudio/include
-DCMAKE_BUILD_TYPE=DEBUG
-DKITTAI_KEY_WORD_DETECTOR=ON
-DKITTAI_KEY_WORD_DETECTOR_LIB_PATH=/Users/marloschida/MacLexa/third-party/snowboy/lib/osx/libsnowboy-detect.a
-DKITTAI_KEY_WORD_DETECTOR_INCLUDE_DIR=/Users/marloschida/MacLexa/third-party/snowboy/include
-DENABLE_ALL_ENDPOINT_CONTROLLERS=ON
Discovery JSON snippet (second try with pt-BR):
{                         "endpointId"\: "amzn1.application-oa2-client._REDACTED_\:\:PiLexa\:\:000003\:\:Discoball"\,                         "friendlyName"\: "Discoball"\,                         "description"\: "Sample Discoball Description"\,                         "manufacturerName"\: "Sample Manufacturer"\,                         "displayCategories"\: ["OTHER"]\,                         "additionalAttributes"\: {                             "manufacturer"\: "Sample Manufacturer"\,                             "model"\: "Model1"\,                             "serialNumber"\: "123456789"\,                             "firmwareVersion"\: "1.0"\,                             "softwareVersion"\: "1.0"\,                             "customIdentifier"\: "SampleApp"                         }\,                         "capabilities"\: [{                                     "type"\: "AlexaInterface"\,                                     "interface"\: "Alexa.ModeController"\,                                     "version"\: "3"\,                                     "instance"\: "Discoball.Mode"\,                                     "properties"\: {                                         "supported"\: [{                                             "name"\: "mode"                                         }]\,                                         "proactivelyReported"\: true\,                                         "retrievable"\: true\,                                         "nonControllable"\: false                                     }\,                                     "capabilityResources"\: {                                         "friendlyNames"\: [{                                             "@type"\: "text"\,                                             "value"\: {                                                 "text"\: "Light"\,                                                 "locale"\: "en-US"                                             }                                         }\, {                                             "@type"\: "text"\,                                             "value"\: {                                                 "text"\: "Luz"\,                                                 "locale"\: "pt-BR"                                             }                                         }\, {                                             "@type"\: "asset"\,                                             "value"\: {                                                 "assetId"\: "Alexa.Setting.Mode"                                             }                                         }]                                     }\,                                     "configuration"\: {                                         "ordered"\: true\,                                         "supportedModes"\: [{                                             "value"\: "Red"\,                                             "modeResources"\: {                                                 "friendlyNames"\: [{                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "Red"\,                                                         "locale"\: "en-US"                                                     }                                                 }\, {                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "Vermelho"\,                                                         "locale"\: "pt-BR"                                                     }                                                 }]                                             }                                         }\, {                                             "value"\: "Green"\,                                             "modeResources"\: {                                                 "friendlyNames"\: [{                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "Green"\,                                                         "locale"\: "en-US"                                                     }                                                 }\, {                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "Verde"\,                                                         "locale"\: "pt-BR"                                                     }                                                 }]                                             }                                         }\, {                                             "value"\: "Blue"\,                                             "modeResources"\: {                                                 "friendlyNames"\: [{                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "Blue"\,                                                         "locale"\: "en-US"                                                     }                                                 }\, {                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "Azul"\,                                                         "locale"\: "pt-BR"                                                     }                                                 }]                                             }                                         }]                                     }                                 }\, {                                     "type"\: "AlexaInterface"\,                                     "interface"\: "Alexa.RangeController"\,                                     "version"\: "3"\,                                     "instance"\: "Discoball.Speed"\,                                     "properties"\: {                                         "supported"\: [{                                             "name"\: "rangeValue"                                         }]\,                                         "proactivelyReported"\: true\,                                         "retrievable"\: true\,                                         "nonControllable"\: false                                     }\,                                     "capabilityResources"\: {                                         "friendlyNames"\: [{                                             "@type"\: "text"\,                                             "value"\: {                                                 "text"\: "Speed"\,                                                 "locale"\: "en-US"                                             }                                         }\, {                                             "@type"\: "text"\,                                             "value"\: {                                                 "text"\: "Velocidade"\,                                                 "locale"\: "pt-BR"                                             }                                         }]                                     }\,                                     "configuration"\: {                                         "supportedRange"\: {                                             "maximumValue"\: 10.0\,                                             "minimumValue"\: 1.0\,                                             "precision"\: 1.0                                         }\,                                         "presets"\: [{                                             "rangeValue"\: 10.0\,                                             "presetResources"\: {                                                 "friendlyNames"\: [{                                                     "@type"\: "asset"\,                                                     "value"\: {                                                         "assetId"\: "Alexa.Value.Maximum"                                                     }                                                 }\, {                                                     "@type"\: "asset"\,                                                     "value"\: {                                                         "assetId"\: "Alexa.Value.High"                                                     }                                                 }]                                             }                                         }\, {                                             "rangeValue"\: 5.0\,                                             "presetResources"\: {                                                 "friendlyNames"\: [{                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "mid"\,                                                         "locale"\: "en-US"                                                     }                                                 }\, {                                                     "@type"\: "text"\,                                                     "value"\: {                                                         "text"\: "meio"\,                                                         "locale"\: "pt-BR"                                                     }                                                 }\, {                                                     "@type"\: "asset"\,                                                     "value"\: {                                                         "assetId"\: "Alexa.Value.Medium"                                                     }                                                 }]                                             }                                         }\, {                                             "rangeValue"\: 1.0\,                                             "presetResources"\: {                                                 "friendlyNames"\: [{                                                     "@type"\: "asset"\,                                                     "value"\: {                                                         "assetId"\: "Alexa.Value.Minimum"                                                     }                                                 }\, {                                                     "@type"\: "asset"\,                                                     "value"\: {                                                         "assetId"\: "Alexa.Value.Low"                                                     }                                                 }]                                             }                                         }]                                     }                                 }\, {                                     "type"\: "AlexaInterface"\,                                     "interface"\: "Alexa.PowerController"\,                                     "version"\: "3"\,                                     "properties"\: {                                         "supported"\: [{                                             "name"\: "powerState"                                         }]\,                                         "proactivelyReported"\: true\,                                         "retrievable"\: true                                     }                                 }\, {                                     "type"\: "AlexaInterface"\,                                     "interface"\: "Alexa.ToggleController"\,                                     "version"\: "3"\,                                     "instance"\: "Discoball.Light"\,                                     "properties"\: {                                         "supported"\: [{                                             "name"\: "toggleState"                                         }]\,                                         "proactivelyReported"\: true\,                                         "retrievable"\: true\,                                         "nonControllable"\: false                                     }\,                                     "capabilityResources"\: {                                         "friendlyNames"\: [{                                             "@type"\: "text"\,                                             "value"\: {                                                 "text"\: "Light"\,                                                 "locale"\: "en-US"                                             }                                         }\, {                                             "@type"\: "text"\,                                             "value"\: {                                                 "text"\: "Luz"\,                                                 "locale"\: "pt-BR"                                             }                                         }]                                     }                                 }
What version of the AVS Device SDK are you using?
  <1.19.1>
  <1.17.0>

Tell us what hardware you're using:

[x] Desktop / Laptop
[x] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[x] MacOS
[x] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @MarlosChida,
Can you attach DEBUG9 logs so we can investigate further?

Hi,
I can attach DEBUG9 files.
Before doing this I would like to know if there is something that should be removed/redacted from the debug logs in order to hide personal info or anything that could compromise security of my account/ids/credentials/tokens.

Hi @MarlosChida, as long as you don't reveal the content of your AlexaClientSDKConfig.json file, DEBUG9 logs is safe.  Also, could you also check your voice history with instructions here here to ensure your utterance is being understood by Alexa correctly?  Thanks!

The DEBUG9 log is attached.
I checked my voice history and the utterances are ok, as follows:
"turn on discoball" -> Answer "OK"
"set discoball to red" -> Answer "Discoball doesn't support that"
"turn off discoball" -> Answer "OK"
Discoball_Voice_Interaction.log

Hi @kclchan , same result.
Utterance history:
"turn on discoball" -> Answer "OK"
"change discoball mode to red" -> Answer  "Discoball doesn't support that"

With the release of version 1.20 of the SDK, I rebuilt everything from scratch. Fresh Raspbian Buster install, SDK v1.20. Same results.

Hi @MarlosChida, we have filed a ticket to track this issue internally and will let you know if we have further questions or updates for you.

Hi @MarlosChida we need more info. Can you do the following?
Discover the device, and do a new test, and do not remove the device until we are able to investigate. Please attach all the logs and utterance history from the new investigation.

The DEBUG9 log is attached.
Discoball_Voice_Interaction_2020-jul_16.log
Utterance history:
"turn on discoball" -> Answer "OK"
"change discoball mode to red" -> Answer "Discoball doesn't support that"
"set discoball to red" -> Answer "Discoball doesn't support that"
"turn off discoball" -> Answer "OK"

Hi @MarlosChida
We couldn't root cause the issue yet, can you please redo the same test? Please do not remove the device.

I am closing this issue due to inactivity.  If you have further questions, please open a new ticket and refer to this closed one.


How to integrate angular2-google-chart with angular-cli?

Please kindly guild me how i can integrate it with angular-cli as i am trying but its not working . So please give me the proper steps how i can integrate it with angular cli

I would like to know this as well. It will be helpful for greater adoption.

@devrockzz @manish153 I've made a tutorial here on how you guys can achieve this.
https://github.com/RicardoVaranda/Angular2-Google-Charts

Thank you for this tutorial. I figured out that your are loading that chart api each time in the diretive. It makes the chart display very slow. Maybe we can upgrade this script.

Hi guys and thanks for the tutorial !  Yes. I noticed the poor performance and it was a no-go for me, but the chart supports 2 graphics that I needed so I had no choice to try to make it work better.
I simply did this:

I just called this.drawGraph() on the chart component (i especially skipped loading the package)
On the index page, right after including the chart script, I only called once the following line google.charts.load('current', { 'packages': ['line'] });

I only needed to draw a couple of line charts, so I grabbed the minimum and it works blazing fast now.
I hope this helps someone, cheers !

@RicardoVaranda: Thanks a lot.

thing i want to ask, that how to show location on hover of grey section.

@sup99 could you please allaborate on step 1. in your answer.
you call "this.drawGraph() on the chart component" ? -in angular component.ts file
where is  "loading the package" that you skip?
I really need this fix, but I just do not understand what to do


Update Composer dependencies (2020-03-02-00-11)

Visual regression test passed!
View the visual regression test report


Compiler bug when shadowing

ceylon version 1.2.2:
I get this "due to a bug in the compiler" message a lot.
In this particular case I had a top-level variable shadowing a class member variable. I wonder if all the errors I get has the same root cause. At least the stack traces seem similar.
ceylon compile: Fatal error: The compiler exited abnormally (4) due to a bug in
the compiler.
Please report it:
 https://github.com/ceylon/ceylon-compiler/issues/new
Please include:

* the stacktrace printed below
* a description of what you were trying to compile.

Thank you!
com.redhat.ceylon.compiler.CompilerBugException: Bug
	at com.redhat.ceylon.compiler.CeylonCompileTool.handleExitCode(CeylonCompileTool.java:569)
	at com.redhat.ceylon.compiler.CeylonCompileTool.run(CeylonCompileTool.java:551)
	at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:520)
	at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:405)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:115)
	at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:41)
	at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:34)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at com.redhat.ceylon.launcher.Bootstrap.run(Bootstrap.java:126)
	at com.redhat.ceylon.launcher.Bootstrap.main(Bootstrap.java:76)
Caused by: java.lang.NullPointerException
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.retype(TransTypes.java:159)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.visitApply(TransTypes.java:604)
	at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1323)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.translate(TransTypes.java:428)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.visitReturn(TransTypes.java:572)
	at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCReturn.accept(JCTree.java:1242)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:70)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.visitBlock(TreeTranslator.java:160)
	at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:783)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.translate(TransTypes.java:428)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.visitMethodDef(TransTypes.java:462)
	at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:671)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:70)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.visitClassDef(TreeTranslator.java:134)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.translateClass(TransTypes.java:889)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.visitClassDef(TransTypes.java:449)
	at com.redhat.ceylon.langtools.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:593)
	at com.redhat.ceylon.langtools.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.translate(TransTypes.java:428)
	at com.redhat.ceylon.langtools.tools.javac.comp.TransTypes.translateTopLevelClass(TransTypes.java:916)
	at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.desugar(JavaCompiler.java:1374)
	at com.redhat.ceylon.compiler.java.tools.LanguageCompiler.desugar(LanguageCompiler.java:823)
	at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.desugar(JavaCompiler.java:1270)
	at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.compile2(JavaCompiler.java:869)
	at com.redhat.ceylon.langtools.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:827)
	at com.redhat.ceylon.compiler.java.tools.LanguageCompiler.compile(LanguageCompiler.java:256)
	at com.redhat.ceylon.compiler.java.launcher.Main.compile(Main.java:663)
	at com.redhat.ceylon.compiler.java.launcher.Main.compile(Main.java:579)
	at com.redhat.ceylon.compiler.java.launcher.Main.compile(Main.java:569)
	at com.redhat.ceylon.compiler.CeylonCompileTool.run(CeylonCompileTool.java:550)
	... 15 more

We will need some example source code which reproduces this problem in order to be able to investigate it.

@realms50 we really need example code to reproduce this. Stacktraces like this one just tell me that our code generator produced something which made the javac backend break, but provide no information about what it was we produced.

Sorry, Ceylon ended up being too buggy at this point so I forgot about my submitted issues.
I'll write up a test case tomorrow.

@realms50 Do you have the test case yet? Thanks.

Closing. We can reopen if a test case materializes.

@gavinking Completely forgot about it... again. Test case below, feel free to reopen.
This ends up with the compiler bug exception on 1.2.2:
variable Integer count=0;

class Counter()
{
    shared Integer currentValue
    {
        return count;
    }

    shared void increment()
    {
        count++;
    }

    variable Integer count;
}

That was fast 👍

@tombentley but... your fix seems to imply the shadowing I tried is not allowed? I  assumed normal shadowing rules applied here, i.e. I should be allowed to use the internal count variable regardless of the top-level one.

The problem that the typechecker is complaining about is that you're trying to use the member count before you're declared it (read up about the "declaration section" if you've not heard the phrase before: http://ceylon-lang.org/documentation/1.2/tour/initialization/#class_bodies). In short if your declare the count member before you use it, like this:
variable Integer count=0;

class Counter()
{
    shared Integer currentValue
    variable Integer count;
    {
        return count;
    }

    shared void increment()
    {
        count++;
    }
}

then it will behave more like you're expecting.
You will then need to qualify the package-level count within the class like this: package.count

Sorry, I screwed up the example code, now fixed.

Thanks, so it was actually unrelated to shadowing.

FTR: the real problem was a bug in the 1.2.2 IDE where backend errors were getting ridiculous huge error spans, making it very difficult to notice the actual meaningful typechecker error (that was there, and correctly displayed). This was already fixed in https://github.com/ceylon/ceylon-ide-eclipse/commit/41cf819e4a0f597487cf8daaa63b1333e3717ff3.

This was from the command line

Well then, if you would have scrolled up, you would have seen the typechecker error.

Well, in my original code, there was a large amount of "symbol: method getValue$priv$()" error cannot find symbol" which didn't make much sense to me (still doesn't), and with the crash report, I assumed that was the problem. I'll redirect to a file and submit the entire trace next time.

This created the impression for some users that the Ceylon compiler had a lot of backend bugs in 1.2.2.

Good to know. I don't use the IDE due to frequent lockups, but I will use the IDEA plugin when available.


1807: Resolve dictionary query bug

CHANGELOG:

Resolved bug for state_get_dictionary_item RPC method that would incorrectly query for the seed_uref in the case of a Contract hash
Fixed bug by retrieving seed_uref by looking up the named keys for both Account and Contract cases

Closes: 1807

bors r+

Build failed:

continuous-integration/drone/push

I canceled this do to CI issue. Restarting.

bors r+


If MFMT not supported but MDTM available...

See issue #914
If MFMT is not supported (re. FEAT list), but MDTM is supported, attempt setting the file time with MDTM. This is not universally supported at all, but worth a try.

Wow, great feature!! Well done.

Simple and universal implementation, nice.


AttributeError: type object 'Qt' has no attribute 'Alignment'

I used pip install git+https://github.com/haiiliin/pyqtribbon.git@main to install it.
This is my code:
import sys
import os
os.environ['QT_API'] = 'pyside2'

from qtpy import QtGui
from qtpy.QtWidgets import QApplication, QMainWindow
from qtpy.QtGui import QIcon

from pyqtribbon import RibbonBar, RibbonCategoryStyle
from pyqtribbon.screenshotwindow import RibbonScreenShotWindow

However, I get the following error:
File "/home/tim/mambaforge/lib/python3.10/site-packages/pyqtribbon/menu.py", line 93, in RibbonMenu
    def addLabel(self, text: str = "", alignment: QtCore.Qt.Alignment = QtCore.Qt.AlignLeft):
AttributeError: type object 'Qt' has no attribute 'Alignment'

What should I do?

Which PyQt/PySide version are you using?

Maybe, The problem is my environment setting.Thanks for your help.Please delete this issues :smiley:

It seems that for different PyQt/PySide distributions, the API for QtCore.Qt.Alignment is different, the current code only works on PyQt5 and PySide2, but does not work on PyQt6 and PySide6

Maybe, The problem is my environment setting.Thanks for your help.Please delete this issues 😃

This is actually a bug, I will fix it in #50 and publish a patch version.

It seems that for different PyQt/PySide distributions, the API for QtCore.Qt.Alignment is different, the current code only works on PyQt5 and PySide2, but does not work on PyQt6 and PySide6

Actually only it only occurs in PyQt6.

pyqtribbon version 0.6.2 has been released


ActionBar - NoSuchMethodError

Hello there.
When i used this library in native android, downloaded directly from market the samples run without problems.
When i used it with xamarin, everything worked but the ActionBar accesses in BaseActivity Line 44:             ActionBar.SetDisplayHomeAsUpEnabled(true);
throw this exception: "Java.Lang.NoSuchMethodError: getActionBar" on a device with API  2.3.7.
Can you help?

This happens because you don't have the Actionbar on 2.3.7... It was introduced on Honeycomb.
And... if you are using some kind of compat library or ABS you should change the part "ActionBar" to "SupportActionBar"
Hope it helps! ^^

yes. i know that. but i tested the native android library with the same device and the action bar worked.

Step 1. Download Support Library v7
Step 2. Follow instructions on how to use it
Step 3. Make a new SlidingActivity inheriting from ActionBarActivity instead of Activity
Step 4. ??
Step 5. Profit
Follow these simple steps and you should be golden. Even better just use NavigationDrawer from Support v4 instead, makes for a more consistent UI compared to other apps.


[BUG] Sprint shootout results loading broken after 3.0.2

Describe the issue:
I haven't narrowed down the issue yet, but something has broken sprint shoot results loading after 3.0.2. It still works correctly with version 3.0.2.
Reproduce the code example:
import fastf1

event = fastf1.get_event(2023, 9)
ss = event.get_sprint_shootout()
ss.load()

print(ss.results) # all quali columns are null (should have times)

Error message:
No response

Caused by 2402ba0f956bf3a41b4dcc27b9f2232ce8fcfac5
I haven't yet analysed what the actual problem is. I'll try  to fix it soon.


feat(external-router): add route inserter injection token

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Fixes: #1383
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
I chose to make it a multi token because I don't think the app dev can always know where to insert each route at root. Each child routing module may need to decide that behavior for themselves.

lgtm


added stage1 babelrc settings

According to https://babeljs.io/docs/plugins/preset-stage-1/, which is included in dev-dependencies, you need to specify stage1 in .babelrc to work. I assume, you only forgot this, since it is already included.
After adding, features like {var1, var2, ...other} started to work.

Coverage decreased (-0.4%) to 98.501% when pulling 01f5ad67c3e10fe234d146d8df542c8ee59ece27 on ArcanisCz:master into 7666f9fcf364bc88615e4c4c91b4bbc39bcee9b0 on coryhouse:master.

Coverage decreased (-0.4%) to 98.501% when pulling 01f5ad67c3e10fe234d146d8df542c8ee59ece27 on ArcanisCz:master into 7666f9fcf364bc88615e4c4c91b4bbc39bcee9b0 on coryhouse:master.

Interesting - I had intended to remove stage 1 support because I didn't think ESLint could handle stage 1-3 features, but object spread is the most relevant feature and is already enabled in .eslintrc, so I went ahead and accepted. The one caveat with this change is some other stage 1-3 features may cause ESLint warnings. But I figure those who experience that can either disable eslint on that line, or pull in babel-eslint to have full stage 1-3 support.
Thanks for the PR!

If you want only object spread without other stage 1-3 features, why not include only object spread instead of stage 1-3 bundle? (http://babeljs.io/docs/plugins/transform-object-rest-spread/ - this one is responsible for it)
then, you will add only {   "plugins": ["transform-object-rest-spread"] }

Yeah, I considered it, but figure supporting all of stage-1 is more inclusive and only downside is potential linting issues which people can easily address.


Update GCP-Cost-Dashboard.yaml

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

done here -> https://github.com/awslabs/cid-gcp-cost-dashboard/commit/fbc9b9acf5687bcc0a4abc0c3e00c688aa8eebba


Create Example Documentation

@rakurame96 I am making this ticket as we discussed through email. I will provide some examples of demonstration code in this thread. I think it will be good to have examples for the specific usage case of each cryptographic algorithm from a file.
So for instance I would read a file from disk and get the bytes and perform the necessary operation.
Hashers would compare two hashes of different files and show a true / false example. I can some code examples in this thread for a hash and aes_gcm.

[ ] Asymmetric
[ ] Compression
[ ] Digital Signature
[ ] ecdsa
[ ] hashers
[ ] hybrid
[ ] key_exchange
[ ] message
[x] password_hashers
[ ] signatures
[ ] sponges
[ ] symmetric

I made an example for AES 256 encrypting and decrypting a docx and writing it disk after each round. This way the user can see its encrypted but when the bytes decrypted its the same file that is written to disk as the original.
use std::{fs::{File}, io::Write, path::Path};

use cas_lib::symmetric::{aes::CASAES256, cas_symmetric_encryption::CASAESEncryption};

fn main() {
    let path = Path::new("MikeMulchrone_Resume2024.docx");
    let file_bytes: Vec<u8> = std::fs::read(path).unwrap();
    let aes_nonce = <CASAES256 as CASAESEncryption>::generate_nonce();
    let aes_key = <CASAES256 as CASAESEncryption>::generate_key();
    let encrypted_bytes = <CASAES256 as CASAESEncryption>::encrypt_plaintext(aes_key.clone(), aes_nonce.clone(), file_bytes);
    let mut file =  File::create("encrypted.docx").unwrap();
    file.write_all(&encrypted_bytes);

    let path = Path::new("encrypted.docx");
    let file_bytes: Vec<u8> = std::fs::read(path).unwrap();
    let decrypted_bytes = <CASAES256 as CASAESEncryption>::decrypt_ciphertext(aes_key, aes_nonce, file_bytes);
    let mut file =  File::create("decrypted.docx").unwrap();
    file.write_all(&decrypted_bytes);
}

I created a .md file at this location, https://github.com/Cryptographic-API-Services/cas-lib/blob/main/docs/EXAMPLES.md

Hello Michael,
Thank you for providing the markdown file. I will begin working on these examples next week and assign this ticket to myself.

Hi @WingZer0o,
I just created a PR (#15) with the above example, placed inside tests/ folder. Created binary crate with name symmetric and added the code. Do you have any other ideas, or continue the current approach?

Hello,
I took a quick glance at the code this would be great to incorporate a test
suite. I made a separate issue for that but we can combine them.
If you could get this to run with a cargo test that would be fantastic and
I think it would be a good way to continue approaching examples.
I will be out of town for a few days before I merged anything into main.
On Tue, Nov 26, 2024 at 1:10 PM Rakuram @.***> wrote:

Hi @WingZer0o https://github.com/WingZer0o,
I just created a PR (#15
https://github.com/Cryptographic-API-Services/cas-lib/pull/15) with the
above example, placed inside tests/ folder. Created binary crate with name
symmetric and added the code. Do you have any other ideas, or continue the
current approach?
—
Reply to this email directly, view it on GitHub
https://github.com/Cryptographic-API-Services/cas-lib/issues/7#issuecomment-2501621663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEG2SNGFDO2F3OF62ODUENL2CS2RXAVCNFSM6AAAAABSIAOSKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGYZDCNRWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@rakurame96 I started working on the hasher test cases here. I still have to create example but this fail and success comparison will be a good addition to the test suite.
https://github.com/Cryptographic-API-Services/cas-lib/blob/main/tests/hashers.rs

Thanks for the info. For next tests, which one should I consider?
So far, hashers & symmetric has been in good shape with more scenarios can be added in future.

I thinking wrapping up the threadpool methods for the SHA3 hashes would be best and moving onto the blake2 hash. If you wanna take those up lemme know.
आपकी सहायता के लिए धन्यवाद

Sure, but would require some assistance from you in this regard.

Honestly the best way to go about this would be to mimic the existing test cases for the SHA256 and SHA512 test cases that I already created, the threadpool methods just have the characters _threadpool appended on it. Here is an example for SHA256 threadpool.
fn test_sha_256_threadpool_compare_fail() {
        let path = Path::new("tests/test.docx");
        let file_bytes: Vec<u8> = std::fs::read(path).unwrap();
        let hash = <CASSHA as CASHasher>::hash_256_threadpool(file_bytes);

        let path_2 = Path::new("tests/test2.docx");
        let file_bytes_2: Vec<u8> = std::fs::read(path_2).unwrap();
        let hash_2 = <CASSHA as CASHasher>::hash_256_threadpool(file_bytes_2);

        assert_ne!(hash, hash_2);
    }

Got it. I have created PR for this.
During build, I have noticed many Clippy warnings. Should we add an appropriate command to suppress them or look for permanent fix? Most of them were related to unused variables warnings.

Probably a fix would be more appropriate but I wouldn’t worry about it in
this PR. I’ll have a closer look after the holidays.
On Thu, Dec 26, 2024 at 4:25 AM Rakuram @.***> wrote:

Got it. I have created PR for this.
During build, I have noticed many Clippy warnings. Should we add an
appropriate command to suppress them or look for permanent fix? Most of
them were related to unused variables warnings.
—
Reply to this email directly, view it on GitHub
https://github.com/Cryptographic-API-Services/cas-lib/issues/7#issuecomment-2562359304,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEG2SNB6MHIA2P2WP7CS55D2HPDPHAVCNFSM6AAAAABSIAOSKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSGM2TSMZQGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


refactor: Widget Selection

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

Add a TL;DR when description is extra long (helps content team)

Fixes #19570

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Manual
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=89ec05f

/ok-to-test sha=40e8591

/ok-to-test sha=eb6a91f

/ok-to-test sha=f507d24

/ok-to-test sha=4cf78b5

/ok-to-test sha=c8b87b0

/ok-to-test sha=e047ff7

/ok-to-test sha=02f5b9e

/ok-to-test sha=e01bf4c

/ok-to-test sha=6aa8f03

[ ] Modal widget property pane is still displayed on the canvas when the user clicks outside the modal. Please refer the attached video:- https://jIju8JbmWA.vmaker.com/record/sZpXijZ47Ds34SUB
[ ] Error is displayed on the canvas whenever the user switches between pages. Please refer the attached video:- https://jiju8jbmwa.vmaker.com/record/1mP5si09TY6HhpIW
[ ]  STATS BOX container widget is selected when the user is selecting the Multiple widgets inside the STATS box widget. Please refer to the attached video:- https://jiju8jbmwa.vmaker.com/record/KI6dMVnVJzYf0FP5

@hetunandu

[ ] 2 scenarios in the video.
a) When there is a container(c1) in container(c2) and there are multiple widgets in c2, now when you select all the widgets in c2 + c2 itself it shows up as multi select along with c2 also selected.
b) When in tabs widget when you place another widget, both tab and other other widget is getting selected.
-

@hetunandu

[ ] Charts widget text is overlapping with each other. Please refer to the attached SS:-

/ok-to-test sha=aff193d

/ok-to-test sha=8d567a1

/ok-to-test sha=235f068

/ok-to-test sha=3378beb

/ok-to-test sha=32aa3d9

/ok-to-test sha=7388b42

/ok-to-test sha=e1855f3

/ok-to-test sha=208d1c0

/ok-to-test sha=ea35423


Improve ResourceLogsTable actions cell (#3072)

Pull request opened by the merge tool on behalf of #3072

Merged in fca361c4b0c45aab84607dac3c9537bb423c01c3


[Snyk] Fix for 1 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

backend-lambda/package.json
backend-lambda/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

658/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

Already fixed.


feat(editors/publisher): add code-editor-dialog

@danyill I was thinking to add a code editor to the publisher on every element as you suggested. That would be a very fast way to allow editing of the elements and would make the editor already quite usable.
The tricky part here was to re-render properly. There is no clean way to distinguish between doc change on open project or doc change due to an editor action at the moment because in both cases we exchange the doc. So I had to do an assumption:

When the new doc has an element at the same location in the file, I assume there was a change due an editor action. That means also that when you load an older version of a file that has also the same element (same identity string) then the element stays selected, and the values are updated.

I would love to have your review for this PR a code review as well. Maybe there is a smarter way to implement the pure code editor.
Tests are still missing. I would do those as soon as I know the principal solution is good enough

With some feedback from @ca-d I will close the PR as is. We need something a bit more general here I think than this web component that can be reused in other cases.


First attempt with Atom S3 - Arduino - M5AtomS3.h "no file or directory"

Describe the bug
I have been using the M5StickC and M5StickC-PLUS with Arduino for over a year with a lot of success.
I thought I would like to try the Atom S3 as a smaller device for the same MQTT and I2C tasks,
I have selected M5Stack-AtomS3 from the M5Stack Arduino board manager (after adding the URL for the library)
Pasting your example Button code into Arduino and trying to flash to Com3
All I get is an error message saying -
Arduino: 1.8.13 (Windows 10), Board: "M5Stack-ATOM, Default, 1500000, None"

RepeatTimer:15:22: fatal error: M5AtomS3.h: No such file or directory

compilation terminated.

exit status 1

M5AtomS3.h: No such file or directory

To reproduce

On a Windows 10 with Arduino 1.8.13
Using the sample Button.ino code

/*
*******************************************************************************
* Copyright (c) 2022 by M5Stack
*                  Equipped with M5AtomS3 sample source code
*                          配套  M5AtomS3 示例源代码
* Visit for more information: https://docs.m5stack.com/en/core/AtomS3
* 获取更多资料请访问: https://docs.m5stack.com/zh_CN/core/AtomS3
*
* Describe: Button example.  按键示例
* Date: 2022/12/18
*******************************************************************************
Press button to display the corresponding output on the screen and
USBserial. 按下按键，在屏幕和串口上显示相应输出
*/
#include <M5AtomS3.h>
/* After M5AtomS3 is started or reset
  the program in the setUp () function will be run, and this part will only be
  run once. 在 M5AtomS3
  启动或者复位后，即会开始执行setup()函数中的程序，该部分只会执行一次。 */
void setup() {
    M5.begin(true, true, false, false);  // Init M5AtomS3.  初始化 M5AtomS3
    M5.Lcd.println("Pls Press Btn");
}

/* After the program in setup() runs, it runs the program in loop()
The loop() function is an infinite loop in which the program runs repeatedly
在setup()函数中的程序执行完后，会接着执行loop()函数中的程序
loop()函数是一个死循环，其中的程序会不断的重复运行 */
void loop() {
    M5.update();  // Read the press state of the key.  读取按键 A, B, C 的状态
    if (M5.Btn.wasReleased() || M5.Btn.pressedFor(1000)) {
        USBSerial.print('A');
        M5.Lcd.print("A");
    }
}

Expected behavior
I was kind of hoping it would just work
Screenshots
No response
Environment

OS: Windows 10
IDE & IDE Version: Arduino 1.8.13
Repository Version: https://github.com/m5stack/M5AtomS3/blob/main/examples/Basics/Button/Button.ino

Additional context
No response
Issue checklist

[X] I searched for previous reports in the issue tracker
[X] My report contains all necessary details

What you downloaded was the RISC chip compiler for the ESP32 chip, and M5Stacks's core libraries - like the "USBSerial" object the examples use.
You're missing the M5AtomS3 software library! (It's the built that codes for the TFT LCD screen, inertial unit, buttons, pin names, and alllllll that).. which is exactly what this GitHub contains. YAY!
On the main Github page here, https://github.com/m5stack/M5AtomS3/  , near the top... Click the blue button that says "<> Code",  in the menu that appears click "Download ZIP".
In your browsers download folder, unzip the "M5AtomsS3-main.zip" file to you Libraries file - it's in your documents folder......
Close and reopen Arduino IDE.
The examples will now work, because the "Include AtomS3.h" will now work - that and the CPP and other files are what's in this library.
ALSO - putting the Library in this folder, you get all the examples BUILT IN! Yay!
From "File..... Examples....." scroll down........ and down..... until you reach "M5AtomS3" and all the examples in this github are there, for you to open and run!

I have now submitted the AtomS3 library to the Arduino library and it will be searchable in a few hours.

@Sarah-C
@Tinyu-Zhao
Thank you both for your help.
I'm really looking forward to seeing what I can do with this little device.

I have now submitted the AtomS3 library to the Arduino library and it will be searchable in a few hours.

@Tinyu-Zhao AtomS3 library is not yet searchable.

I'm working on it.

I have now submitted the AtomS3 library to the Arduino library and it will be searchable in a few hours.

@Tinyu-Zhao AtomS3 library is not yet searchable.

Fixed.

Thank you @Tinyu-Zhao
I'm looking forward to seeing what I can do with it.


Redesigning how builds are retrieved on the Zuul source.

Adding a new API to perform queries related to jobs. This allows for easier filtering of desired builds. This redesign was meant to implement the '--last-build- query, but I will wait for how https://github.com/rhos-infra/cibyl/pull/101 resolves first.

No, this pull request is just before I start working on the --last-build option. I expected that beforehand.


Pretty printed logs and events in cast run

Motivation
Recently I got quite big events in cast, so made them a bit more pretty printed, also fixed padding of topics in logs
Solution
Before:

After:

P.S. I don't remember any log bigger than 4 topics, so removed number 13 for string formating.

If we accept this, we should also do this for calls too.

looking at the failing tests, I think we want to this for topics > 1

Added calls + fixed calls with no params

Hi @ioterw, since the last update we've entirely moved to use the revm-inspectors  crate to render the traces. Any proposed changes should be added there.
Given that there is no actionable item left here I think it makes sense to close this ticket in favor of a future one to be opened by @ioterw in https://github.com/paradigmxyz/revm-inspectors


decision: implement a simple decision maker

With that a user can do:
 bot: go to the beach or go to the mountains?
 go to the beach, of course!
Signed-off-by: Leandro Dorileo<EMAIL_ADDRESS>

LGTM

Implementation already exists in ai.go :-)


UI stuff (?!)

e x p e r i m e n t a l

After over an hour of debugging, I have unfortunately not yet been able make window resizing function properly. someone pls help

After over an hour of debugging, I have unfortunately not yet been able
make window resizing function properly. someone pls help

—
Reply to this email directly, view it on GitHub
https://github.com/Sceleratis/Adonis_2.0/pull/13#issuecomment-1068766897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARPWXKXOPOXRNLEQQMJ7KT3VAF2NXANCNFSM5QX5CCLQ
.
You are receiving this because you commented.Message ID:
@.***>

No

After over an hour of debugging, I have unfortunately not yet been able
make window resizing function properly. someone pls help

—
Reply to this email directly, view it on GitHub
https://github.com/Sceleratis/Adonis_2.0/pull/13#issuecomment-1068766897,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARPWXKXOPOXRNLEQQMJ7KT3VAF2NXANCNFSM5QX5CCLQ
.
You are receiving this because you commented.Message ID:
@.***>

No

Thanks for volunteering! Looking forward to your contributions.
*proceeds to do major trolling with maintainer perms by editing your message to "yes"

You might be able to draw inspiration from how the current window stuff deals with resizing

Didn't work.


Register version v0.2.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/44962
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.2 -m "<description of version>" 6052c4ab77d7813a4047561eb9adcab9cdf7f0f6
git push origin v0.2.2


bug: visualisation, run steps and labware position check refer to old protocol after update to 7.0.1

[Edit by @SyntaxColoring: this is tracked internally as RESC-162.]
Overview
We updated the Opentrons app and the robot servers to 7.0.1 on 26/10/23.
Our current workflow is:

create a new protocol using a config generator and a standardised Python protocol which reads the config file
upload the config and the standardised protocol to the robot via the HTTP API
for a subset of our protocols, run a labware position check via the Opentrons app

The problem after the update: The run steps, labware visualisation and position check refer to an old version of the protocol. However, when the protocol is run, it runs the new version.
What we've tried:

Deleting the old protocol
Turning the app and the robots on and off again

[NB: we appreciate this probably isn't a common workflow - it is temporary whilst we create a version of the labware position check in our own interface.]
Steps to reproduce

Upload a protocol
Update the app and robots to 7.0.1
Upload a new version of the protocol with the same name to the robot via the HTTP API
Run a labware position check via the Opentrons app
Run the protocol via the Opentrons app

Current behavior
The run steps, labware visualisation and position check refer to an old version of the protocol. However, when the protocol is run, it runs the new version.
Expected behavior
The run steps, labware visualisation and position check refer to the latest version of the protocol and match the protocol that is run.
Operating system
Windows
System and robot setup or anything else?
Versions:

Opentrons app and robot server versions: 7.0.1
All our protocols are at least 2.0 (mostly 2.13+)
The HTTP API:  3
Python package: 6.2.1
The app is run from Windows and Mac computers
The HTTP request is sent from Mac computers when testing locally and then from a Fargate instance (Linux) when in production

Accessing the robot via wifi, sending an HTTP request to post the protocol and scp-ing a configuration file to the robot. Then running the labware check through the Opentrons app.
Not sure whether this issue is related: https://github.com/Opentrons/opentrons/issues/13839

👋 Hey, thanks for the detailed report.

The run steps, labware visualisation and position check refer to an old version of the protocol.

Does it seem like it could be referring to the latest .py file, but an old config file?
We have a couple things that might be interacting here in a confusing way.
First: The robot analyzes a protocol only when you first upload it via POST /protocols. If, after that, you scp over some stuff that affects the protocol's behavior, those changes in behavior won't be reflected in the protocol's analysis. The analysis will be stale.
Second: When you upload a protocol via POST /protocols, the robot no-ops if it's a protocol it's already storing, as an optimization. The comparison is made by comparing the files in the POST requests. This means if you repeatedly upload the exact same Python file, the robot will only analyze it the first time. It mistakenly skips re-analysis because it doesn't know about any externally-scp'd files that have changed its behavior since it was first uploaded.
So my theory at the moment is that you're running into some combination of those.
You want to guarantee that you're looking at a fresh analysis, representing, as closely as possible, what a new run would actually do. I think these are your options today:

The easiest is probably to make the file different every time you upload it, so it always looks like a new protocol that needs to be analyzed. Appending a timestamp to the filename should be sufficient for this, like my_protocol_1698624000.py.
Alternatively, you could fully delete and recreate the protocol every time you upload it. Delete the protocol with an HTTP DELETE /protocols/{id}. You may need to also delete the runs that were created from that protocol, with HTTP DELETE /runs/{id}.

Also, if your protocol has dependencies that it's expecting to be externally scp'd, make sure you scp them before doing POST /protocols. Otherwise, the protocol analysis will start without waiting for those dependencies to be present on the system.
Let me know if that helps!

We've renamed the file each time we upload it and this seems to have solved the issue. Will close. Thanks for your detailed suggestions!

We're tracking this as #14598, moving forward.


[Feature Request] Show average total time

While it's great to see the percent breakdown of each event, it would also be useful to display the (average, for multiple tries) total startup time at the top of the startuptime buffer.

The functionality you've requested is available.
:StartupTime takes an optional argument, --tries, for specifying how many runs to conduct. The results are averaged.
E.g.,
:StartupTime --tries 20

Additionally, pressing <space> with the cursor on the header row will show additional information, including the total time (an averaged total if --tries was used).
Possibly Relevant Additional Information
The numbers reported by the vim-startuptime plugin are obtained by calling Vim with the --startuptime option, which reports both self times and self+sourced times. As far as I can tell, based on the information in :help profd (assuming the info applies generally to timings reported by --startuptime), the self times exclude time spent performing various actions (e.g., sourcing other files), whereas the self+sourced times include these various other actions.
The vim-startuptime plugin uses the self+sourced times by default (e.g., for individual times, total times, and percent calculations). The optional --no-self option can be specified so that only self timings are reported and used for calculations.

Ah, I did not realize that using <space> on the header line would show the total time. That's the part I was missing. Thanks!


Sections Subnav does not work.

Sections Subnav link entries do not function. The href populates on both the element and the link in the subnav, but it does not jump to the heading.

Whoops. Technical error. We were on an older version. Working now, thanks!

Okay! Glad to hear. It's moved a few times due to P&T making some adjustments to the main CP templates.


Slowness observed in obtaining connection using neo4j java jdbc driver

Hi All,
I have my java application deployed in websphere application server. I am successfully able to connect to neo4j from my java application using jdbc driver. But there are some performance issues with the approach i have followed. Currently neo4j server is running on Xms - 8G and Xmx-16GB. I have only less amount of data that is aprox 40mb with 3100 nodes. When we test the performance over http with cypher, the performance is outstanding. But with the java application we are using the jdbc driver in the to connect to neo4j via bolt. Every connection creation is taking around 100ms which is adding up delay. We are able to achieve only 160 hits/sec with this approach. With 500 concurrent calls, the requests are queuing up and the response time is shooting to 3 seconds. Any pointers of improvement would be helpful. (Application server and neo4j servers are on different boxes under the same VLAN).
Below is the snippet of connection creation.
Class.forName("org.neo4j.jdbc.Driver").newInstance();
Connection conn = DriverManager.getConnection("jdbc:neo4j:bolt://localhost:port") ;

Which version do you use?
What happens if you reuse the same driver or connection?

@jexp Im using neo4j version 3.3.9 with neo4j driver 3.3.1.
As of now it looks like i the issue is due to the connection pool not being set.
Im trying to create data source for neo4j in websphere application server but its failing to connect. Any pointers on this would be helpful.
JDBC Driver Created with the following parameters:
Name : neo4j Driver
Class path : path of the neo4j jdbc jar/neo4j-jdbc-driver-3.3.1.jar
Implementation class name : org.neo4j.jdbc.Driver
Data source created with the following :
jndi Name: jdbc/neo4j
Custom Properties:
auth : container
type: javax.sql.DataSource
username: neo4j
password: password
url:jdbc:neo4j:bolt://localhost:port
removeAbandonedOnBorrow : true
closeMethod : close
The properties are added based on the pointers provided in https://github.com/neo4j-contrib/neo4j-jdbc
Here is the error from logs:
java.lang.Exception: DSRA8101E: DataSource class cannot be used as one-phase: ClassCastException: org.neo4j.jdbc.bolt.BoltDriver incompatible with javax.sql.ConnectionPoolDataSource
[5/27/19 13:12:41:533 UTC] 00000111 SystemErr R at com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:441)
[5/27/19 13:12:41:533 UTC] 00000111 SystemErr R at com.ibm.ws.rsadapter.DSConfigHelper.getPooledConnection(DSConfigHelper.java:1340)

@jexp Got to know from the other forum that Websphere doesnt support to create datasource for neo4j.
https://stackoverflow.com/questions/56336920/error-when-creation-data-source-for-neo4j-in-websphere-application-server
Can you please help me on how we can achieve connection pooling ?

The Neo4j Driver that the JDBC driver wraps pools connections internally.
There should be no need to created individual connections.
Can you see if this build helps you, it includes a change that reuses driver objects by settings/url.
https://www.dropbox.com/s/7w8ad2ln5dz41od/neo4j-jdbc-driver-3.4.0.jar?dl=0

Closing this as we have not heard back.


Add a license to the project

I haven't been able to find a license for this repository. Is there a way for us to add one? That would facilitate people legally being able to use this project.
More information here: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

Exactly. A license is important for any open-source project. But we haven't had any discussions about the license yet. Probably, it will be added after the hacktoberfest. So, until then, I'm closing this issue.


Feature: setup/unset multilang

Option to setup multilang: Rename all content files with specified lang locale.
Option to unset multilang: Rename content files of a specified language by removing the locale, delete all other language's content files.

Yes please! That would be totally awesome.


jpegexiforient: init at 2002-02-17

Motivation for this change
This allows feh --edit to work properly, whereas previously it would give
feh WARNING: lossless rotate: Failed to exec jpegexiforient: No such file or directory
feh WARNING: lossless rotate: Failed to update EXIF orientation tag: jpegexiforient returned 1

Things done

[x] Built and tested on linux

Yeah, done that

feh's build failure on darwin isn't related: https://hydra.nixos.org/job/nixpkgs/trunk/feh.x86_64-darwin


Still unable to slide/grapple/mantle and vault

I reinstalled Beatrun to the newest version, not replacing any files completely from scratch and I did the same for Vmaniprework, I'm running on Chromium/64-bit version of Gmod on the map Catalyst Blockout, above 60 FPS, the most consistent way I have found to replicate this bug was my either coiling into a slide or kicking while sliding, as previously mentioned I followed the new instructions for the installation 1:1, I tried fiddling around with the new kick glitch settings also to no avail, if video proof or something alike is needed I will provide it if requested.
Edit: Forgot to mention that I uninstalled the Workshop version of Vmanip, so that isn't causing the issue

Try latest release, should be good now (i hope)

Yup, works perfectly


MessageReactionsScreen: Set scrollEnabled to true.

Currently in MessageReactionsScreen when we have a bunch of emojis then
the emoji tabs are overlapping with each other making it hard for any user
to view emojis & it's reaction count.
So add a scrolling effect by setting scrollEnabled to true in Tab.Navigator.
Screenshots/Media:
https://user-images.githubusercontent.com/42652941/109989091-2ead2980-7d2e-11eb-9e15-dbc52016c9e2.mp4
Fixes : #4508
Signed-off-by: rajprakash00<EMAIL_ADDRESS>

Hi! Before reviewing an approach like this, I'd like to hear more thoughts on some alternative designs; there's been some discussion on an existing issue around https://github.com/zulip/zulip-mobile/issues/3798#issuecomment-574370290.

Hi, @rajprakash00! You mentioned at https://github.com/zulip/zulip-mobile/issues/3798#issuecomment-813921147 that you'd like to try a different approach than the one here; I think that makes sense. 🙂 Quoting that comment:

If we go the vertical list way (see my previous comment here, and still I think my preference), the shuffling would still affect tap attempts, but it would be noticeably less annoying because there's less of a demand to tap to see who the users are, because you can already see avatars. It's also a much larger area than the row of tabs.

@chrisbobbe I'm thinking the design path to be more or less like this 🙂
Also in this way we don't have to deal with tediuos amount of scrolling for unique reactions(if tab view design is kept) and another good thing is we are also keeping the design in sync with other SectionLists used in zulip mobile)(e.g: UserList screen)

Should we close this PR, then, or are you thinking you'll update it with that new approach? Either is fine.

I think #3798  goes for the whole MessageReactionsScreen UI change, so better to have a separate PR for that 🤔


Running on CPU instead of GPU

Hello,
Thanks for making this work publicly available.
I'm currently running ./scripts/long_term_forecast/ETT_script/TimesNet_ETTh1.sh on Google Colab. But it is always running on CPU, instead of GPU. I'm wondering if there's something in the code I should set as True in order to make it run on GPU.
I set the default of the functions below as True in the run.py file:
parser.add_argument('--use_gpu', type=bool, default=True, help='use gpu')
parser.add_argument('--use_multi_gpu', action='store_true', help='use multiple gpus', default=True)

Thank you!

Hello!
We have retested our code and executing ./scripts/long_term_forecast/ETT_script/TimesNet_ETTh1.sh will not cause any issues with CPU operation. You can consider the following solutions:

Check the export CUDA_VISIBLE_DEVICES=xxx statement in the script, which selects your GPU number
Check if your GPU has sufficient graphics memory


fix(Datagrid): expander title / aria-label updates

Contributes to #3561
Properly assigns a more logical value to the row expander title and aria-label attributes, as opposed to using the default value that react-table provides via {...row.getToggleRowExpandedProps()}.
This change has been applied to both expanded and nested rows.
What did you change?
packages/ibm-products/src/components/Datagrid/Datagrid/DatagridExpandedRow.js
packages/ibm-products/src/components/Datagrid/Extensions/ExpandableRow/ExpandableRow.docs-page.js
packages/ibm-products/src/components/Datagrid/Extensions/ExpandableRow/ExpandableRow.stories.js
packages/ibm-products/src/components/Datagrid/Extensions/NestedRows/NestedRows.stories.js
packages/ibm-products/src/components/Datagrid/styles/_useExpandedRow.scss
packages/ibm-products/src/components/Datagrid/useNestedRowExpander.js
packages/ibm-products/src/components/Datagrid/useRowExpander.js
packages/ibm-products/src/components/Datagrid/utils/getArgTypes.js

How did you test and verify your work?
Storybook

😅 Yes, plenty more to do but at least it's a start


train cifar using multigpu

accuracy drops to 93.47% if the eval batches are split across multiple gpus. Drops to 93.76% if just evaling on a single gpu.
trains about 2.2x faster than on a single gpu. it seems pretty host memory bandwidth limited.

The accuracy would drop even when I attempted to optimize one single kernel. Either add another trick to make it stay above 94% more consistently or just to do one more sweep after to find a better set of hyper-parameters.

Hmm, how did the accuracy drop from optimizing a kernel? Is there a bug, or it is just numerical instability?

I'm assuming it is a numerical instability but haven't given it much more thought, here's an example from the current master, and I used a hack to only optimize the slowest kernel.
***  146 r_16_2_16_3_512_32_32_3_4         arg   3 sz [2, 16]            [3, 16]      OPs  19327M/ 452.04G  mem  0.66 GB tm  24122.77us/   112.97ms (  801.21 GFLOPS,    8.35 GB/s)
999   87.43 ms run,    3.90 ms python,   83.54 ms CL,  469.10 loss, 0.000070 LR, 5.99 GB used,   7712.73 GFLOPS
eval 9403/10000 94.03%,    0.40 val_loss STEP=1000

After that kernel was optimized
***  146 r_4_3_3_32_8_512_16_16_2_2_2      arg   3 sz [3, 3, 4]          [8, 32]      OPs  19327M/ 452.04G  mem  0.66 GB tm  18760.47us/   106.96ms ( 1030.22 GFLOPS,   10.74 GB/s)
999   82.74 ms run,    2.61 ms python,   80.13 ms CL,  470.44 loss, 0.000070 LR, 5.99 GB used,   8150.66 GFLOPS
eval 9407/10000 94.07%,    0.40 val_loss STEP=1000

Re: eval, how is eval getting a different answer? Training can sometimes be affected by the norms, but eval shouldn't be.
But if the training is being affected, the weights could differ slightly which eventually causes eval to be different.

I don't understand why splitting the eval across multiple gpus would change the score, because if I run the full eval on all the gpus, they all eval to the same score, but sharding the eval makes it eval to a lower score.

Yea this has to be some sort of bug.

Oh a 0.04% difference after 1000 steps of training is very possibly numeric. A 0.28% difference on eval is a bug.

It's at 93.88% now with eval sharded, 93.95% with eval on a single gpu.

ok, this autodetects gpu count now, and just throws assertions if bs and eval_bs aren't divisible.

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/runtime/ops_gpu.py                7               4
------------------------------------------------------------
lines added in the tinygrad folder: 3


add intent: quote

Resolves #10 .

Should I update test.py and commit??

@srishti-nema Yes, you have to update.

Thanks @srishti-nema! 👍
Here's a good issue for you to work on next: https://github.com/the-vision/jarvis-telegram/issues/10


chore: release v0.2.0

:robot: I have created a release beep boop
vue: 0.2.0
0.2.0 (2022-08-15)
Features

input component (#2) (ca2cde0)

svelte: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)

use: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)

usevue: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)
input component (#2) (ca2cde0)

theme: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)
input component (#2) (ca2cde0)

config: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)
input component (#2) (ca2cde0)

metadata: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)
input component (#2) (ca2cde0)

transform: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)
input component (#2) (ca2cde0)

monorepo: 0.2.0
0.2.0 (2022-08-15)
Features

button alert alertError (23b1361)
input component (#2) (ca2cde0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/agufaui/agufaui/releases/tag/vue-v0.2.0 :sunflower:


test: add dragonfly docker latest

Closed in favour of https://github.com/soluble-io/cache-interop/pull/890


Backport 3.9 typehints to 3.8 so tests can run under Pyston (faster p…

Backport typehints to 3.8, which allows Pyston to run.
It turns out there wasn't much to do to port this, and we didn't even need strip-hints :)
This also adds info to the readme about running tests in parallel.

Codecov Report

Merging #339 (57149e3) into master (3bc4205) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 57149e3 differs from pull request most recent head 8d7e529. Consider uploading reports for the commit 8d7e529 to get more accurate results

@@           Coverage Diff           @@
##           master     #339   +/-   ##
=======================================
  Coverage   89.77%   89.77%
=======================================
  Files         275      275
  Lines       14029    14031    +2
  Branches     1025     1025
=======================================
+ Hits        12594    12597    +3
  Misses       1219     1219
+ Partials      216      215    -1

Impacted Files
Coverage Δ

common/business_rules.py
98.49% <100.00%> (+<0.01%)
:arrow_up:

measures/views.py
73.07% <100.00%> (+0.52%)
:arrow_up:

quotas/business_rules.py
97.63% <0.00%> (+0.78%)
:arrow_up:

Continue to review full report at Codecov.

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

You will need to force merge this and go and update the settings in Github to not be expecting a 3.9 build anymore.


[BUG] Payload Too Large when uploading images through Rancher

Describe the bug
When adding an image via the web UI, when the UI is accessed via a Rancher UI and the Virtualization Management page, the image upload fails with 413 Payload Too Large. Additionally, the upload fails immediately, but the upload status and progress bar persist and do not reflect an errored state.
When uploading the same image via the Harvester UI directly, the image upload succeeds.
To Reproduce
Steps to reproduce the behavior:

Access Harvester through a connected Rancher Management Server UI
Create an Image
Select Upload
Select File
Click Create

Expected behavior
An image should begin uploading
Support bundle
(this may not need a support bundle)
Environment

Harvester ISO version: 1.3.0
Rancher UI Version: 2.8.3
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Bare metal mini PCs, 32gb, 16cpu

Additional context
I recognize this may moreso be a Rancher UI issue, but wanted to first share this in context of Harvester.

Hi @krumware are you able to please try this?
https://docs.harvesterhci.io/v1.3/upload-image/#http-413-error-in-rancher-multi-cluster-management

I confirmed that the above suggestion did resolve the issue, and was very simple. Thank you!
Steps to resolve: Update the nginx ingress manually, test resolution. Apply the configuration change to the helm deployment values of the Rancher management server, and perform an upgrade. Check for persistence of the configuration. Re-tested and confirmed.

complete


VersionEye Status

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change

Gives up-to-date status on the status and security of libraries used by uPortal.

Goal
See version status of all dependencies, and subproject dependencies in this repository.
Technical Solution
Because of the large number of subprojects, we added an aggregation script to send the dependency information as a single bundle.
https://github.com/Jasig/uPortal/blob/051d2037573ab8c755fdc86e56132455f0268f4e/build.gradle#L43-L46
For that upload to work it needs an API token to give it access
script: ./gradlew versioneye-update -Pversioneye.api_key=$VERSION_EYE_TOKEN

Because that is an access token we don't want it kept in plain text so it is encrypted.
secure: aJtucm9bUlpbBOxkDulRJ+4Y7XLCDgNbfn2TGcDieQrklAEMf1YgV8cYjKxe/Ddno7Ifc3RsSle8aAU7GNmd59ed8YGhgdzJ1Ozla8YiClh9X/XiMzBMCyYfrHeMHmpnRcO4BX7tZ98SGUOrln3rpf3CbIix5m8gdiFeMpuE+M=

Flow

Travis CI build is started
If the the current branch is master continue
Version eye gradle plugin will scan dependencies of all projects in the uPortal repo
Version eye gradle plugin aggregates dependencies into a single bundle
API token is decrypted and used to upload results to versioneye


Explicitly require hypervisor beaker gems, for non-CI contexts

These are no longer built into beaker 4

Appveyor failure is unrelated

CLA signed by all contributors.


The game is not letting me past backwoods standoff, because even though it is a core level, It keeps saying that I need codecombat premium.

I really love this game and I want to continue, but I don't think I can without help.

+1 I try this game but it seems broken on begining. Cannot start Cell Commentary (red) level in dangeon


Several downloads at the same time

Scenario

The user clicks on a volume to download. The download begins.
During the download, he can click on another volume to download it.

Solution

Disable the mouse click as long as the current download is not finished, so as not to download several volumes at the same time

Solution :

Monitor the thread that starts the download, as long as it isAlive no action is possible.


support oss log

Codecov Report

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

@@           Coverage Diff           @@
##           master     #250   +/-   ##
=======================================
  Coverage   86.63%   86.63%
=======================================
  Files          50       50
  Lines        3076     3076
=======================================
  Hits         2665     2665
  Misses        284      284
  Partials      127      127

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 f364241...9725ad9. Read the comment docs.


fix(sortAllTxs): Renaming Electrumx.sort0ConfTxs to sortAllTxs

:tada: This PR is included in version 4.7.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.7.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: