There is an error(<class 'AttributeError'>) happened during optimizing on the converted model!

I'm trying to convert keras model from https://github.com/fizyr/keras-retinanet to onnx, and this error show up. Anyone have the same problem in convert keras models to onnx?
Thanks!
Instructions for updating: Use tf.compat.v1.graph_util.tensor_shape_from_node_def_name`
node bn3d_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4f_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5b_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5c_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3c_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4e_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5a_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5a_branch1/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3d_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4f_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5b_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3b_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4d_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3c_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4e_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5c_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5a_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3a_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3a_branch1/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4c_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3d_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3b_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4f_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4d_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5b_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4b_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3c_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3a_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4e_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4c_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn5a_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2c_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4a_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4a_branch1/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3b_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4d_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4b_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2b_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn3a_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2c_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4c_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4a_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2a_branch2c/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2a_branch1/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2b_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4b_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2c_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2a_branch2b/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn4a_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn_conv1/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2b_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
node bn2a_branch2a/FusedBatchNorm of type FusedBatchNorm cannot be converted, fall back to tf2onnx
WARNING:tensorflow:From /root/venv/keras-onnx/lib/python3.6/site-packages/keras2onnx/_builtin.py:59: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.
There is an error(<class 'AttributeError'>) happened during optimizing on the converted model!`

Which version of keras2onnx you use? Can you pull the latest master and try?

Which version of keras2onnx you use? Can you pull the latest master and try?

I used the latest master of keras2onnx, and the problem come out

Which version of tensorflow? Can you specify the pretrained model so that we can debug?

Which version of keras2onnx you use? Can you pull the latest master and try?

I used the latest master of keras2onnx, and the problem come out

In that case, you need manually pip install git+https://github.com/microsoft/onnxconverter-common.git

Which version of tensorflow? Can you specify the pretrained model so that we can debug?

keras2onnx: latest version
tensorflow (I tried both cpu and gpu version): 1.14.0
keras: latest version
keras model I download from here: https://github.com/fizyr/keras-retinanet/releases/download/0.5.1/resnet50_coco_best_v2.1.0.h5
thanks!

Which version of tensorflow? Can you specify the pretrained model so that we can debug?

even I run the script from example in readme, same problem occur! (keras2onnx latest, tensorflow cpu 1.14.0, keras latest)
`import numpy as np
from keras.preprocessing import image
from keras.applications.resnet50 import preprocess_input
import keras2onnx
import onnxruntime
image preprocessing
img_path = 'street.jpg'   # make sure the image is in img_path
img_size = 224
img = image.load_img(img_path, target_size=(img_size, img_size))
x = image.img_to_array(img)
x = np.expand_dims(x, axis=0)
x = preprocess_input(x)
load keras model
from keras.applications.resnet50 import ResNet50
model = ResNet50(include_top=True, weights='imagenet')
convert to onnx model
onnx_model = keras2onnx.convert_keras(model, model.name)`

Resnet50 is in our nightly build and it works, see test_ResNet50 in test_keras_applications.py
you need manually pip install git+https://github.com/microsoft/onnxconverter-common.git

I just tried retina net and find ValueError: get tensor value: TFNodes/filtered_detections/map/while/PadV2_2/paddings_Concat__14245 must be Const, I will look into it later.

I got the same error, but it seems that the resulting converted model works fine.

I got the same error, but it seems that the resulting converted model works fine.

This error is optimization error, we will skip optimization if the error happens, so it works fine. Will take a look later.

I just tried retina net and find ValueError: get tensor value: TFNodes/filtered_detections/map/while/PadV2_2/paddings_Concat__14245 must be Const, this error looks different from what you provided here. I will look into it later.

this problem could be solve by using opset target 10. Anyway the error as I stated in the issue title still remain, when I use the onnx runtime to load, it's said the model is bad and can not load

With the latest keras2onnx master (I add a convertor of FusedBatchNorm at keras side), I find that the inside tf2onnx converter lead to an invalid graph for TensorArrayGatherV3 conversion. It may take sometime to fix.

I stumbled upon the same problem (about TensorArrayGatherV3 conversion) and I wonder if there is any news about a fix or a workaround.
I'm using the latest version of keras2onnx and onnxconverter-common (1.6.5).


e2e, etcdserver: fix wrong usages of ordinal

They must be "ordinary".

@heyitsanthony could you take a look? Sorry for the silly mistakes...

LGTM


Not working in material angular

Can any one suggest me how to use this in material angular.
Thank you in advance..

Hi, I'm developing a project based on Angular Material so, you may wait a few days until I implement it on my project. I believe there is any complex issue to use it with Angular Material

cool, please keep us posted @betorobson

Hi @kaloudis, After I read about this project is not maintained anymore, I decided replace it to http://www.idangero.us/swiper/. I strongly suggest you to do the same I'm sorry for this bad news.

hey guys, yes, unless someone with good expertise can take the relay, because i'm not much into angular anymore, and lack time for maintenance... good luck


Make the page-view remembering logic actually work.

It wasn't tested, which is why it didn't work before.


⚠ ESPN has degraded performance

In c52606f, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 605 ms

Resolved: ESPN performance has improved in 2a0def6.


Manager#reenqueue(job_uuid : String)

Re-uses the same Redis Job instance

There is no use-case for this method. Failed jobs should be reenqueued via background-control or the CLI.


Differences in behaviour of sync and install -r when ignoring dependencies due to environment mismatch

Issue description
There are differences in behaviour when it comes to the dependencies which are ignored or installed whenever sync or install -r are used.
Assume a scenario where a user wishes to update a project written originally for an earlier Python version, 3.9, together with all its dependencies but the original Pipfile doesn't contain the exact versions pinned or is missing altogether. However, assume either the requirements.txt or the Pipfile.lock files are available.
Expected result
One would expect that the results of pipenv sync and pipenv install -r requirements.txt, in the later Python environment, are equivalent, but this is not the case.
In the case of a migration, say from Python 3.9 to 3.11, and when using pipenv sync, dependencies for which  python_version marker mismatches are observed will be ignored.
However, in the same scenario, when using pipenv install -r the same dependencies will still be installed.
Actual result
requirements.txt
-i https://pypi.org/simple
tomli==2.0.1; python_version < '3.11'
typing-extensions==4.7.1; python_version < '3.10'
zipp==3.16.0; python_version < '3.10'

...
Installing collected packages: zipp, typing-extensions, tomli

Successfully installed tomli-2.0.1 typing-extensions-4.7.1 zipp-3.16.0
...

sync
{
    "_meta": {
        "hash": {
            "sha256": "6d18433f07ef40ac8e479c1972d2fd8a96f2fca453118ddd0e2c516642307a6f"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.9"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "tomli": {
            "hashes": [
                "sha256:939de3e7a6161af0c887ef91b7d41a53e7c5a1ca976325f429cb46ea9bc30ecc",
                "sha256:de526c12914f0c550d15924c62d72abc48d6fe7364aa87328337a31007fe8a4f"
            ],
            "markers": "python_version < '3.11'",
            "version": "==2.0.1"
        },
        "typing-extensions": {
            "hashes": [
                "sha256:440d5dd3af93b060174bf433bccd69b0babc3b15b1a8dca43789fd7f61514b36",
                "sha256:b75ddc264f0ba5615db7ba217daeb99701ad295353c45f9e95963337ceeeffb2"
            ],
            "markers": "python_version < '3.10'",
            "version": "==4.7.1"
        },
        "zipp": {
            "hashes": [
                "sha256:1876cb065531855bbe83b6c489dcf69ecc28f1068d8e95959fe8bbc77774c941",
                "sha256:5dadc3ad0a1f825fe42ce1bce0f2fc5a13af2e6b2d386af5b0ff295bc0a287d3"
            ],
            "markers": "python_version < '3.10'",
            "version": "==3.16.0"
        }
    },
    "develop": {}
}

...

Steps to replicate
The Pipfile.lock and requirement.txt files together with pipenv installation logs discussed here can be found in this repository: https://gitlab.com/jdsalaro-group/public/pipenv-sync-install-requirements-differences

$ pipenv --support
Pipenv version: '2023.11.15'
Pipenv location: '/Users/user/.asdf/installs/python/3.11.0/lib/python3.11/site-packages/pipenv'
Python location: '/Users/user/.asdf/installs/python/3.11.0/bin/python3.11'
OS Name: 'posix'
User pip version: '23.3.1'
user Python installations found:
PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.11.0',
 'os_name': 'posix',
 'platform_machine': 'arm64',
 'platform_python_implementation': 'CPython',
 'platform_release': '23.3.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST '
                     '2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000',
 'python_full_version': '3.11.0',
 'python_version': '3.11',
 'sys_platform': 'darwin'}

System environment variables:

PATH
MANPATH
TERM_PROGRAM
SHELL
TERM
ASDF_DIR
TMPDIR
HOMEBREW_REPOSITORY
TERM_PROGRAM_VERSION
ASDF_DEFAULT_TOOL_VERSIONS_FILENAME
TERM_SESSION_ID
USER
COMMAND_MODE
SSH_AUTH_SOCK
__CF_USER_TEXT_ENCODING
LaunchInstanceID
__CFBundleIdentifier
PWD
ASDF_CONFIG_FILE
ITERM_PROFILE
XPC_FLAGS
XPC_SERVICE_NAME
COLORFGBG
HOME
SHLVL
LC_TERMINAL_VERSION
HOMEBREW_PREFIX
ASDF_DATA_DIR
ITERM_SESSION_ID
LOGNAME
LC_CTYPE
HOMEBREW_CELLAR
INFOPATH
LC_TERMINAL
SECURITYSESSIONID
COLORTERM
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /Users/user/.asdf/installs/python/3.11.0/bin:/Users/user/.asdf/installs/python/3.12.0/bin:/Users/user/.asdf/installs/python/3.9.18/bin:/Users/user/.asdf/installs/python/-h/bin:/Users/user/.asdf/installs/python/3.9.1/bin:/Users/user/.asdf/installs/python/3.10.0/bin:/Users/user/.asdf/plugins/python/shims:/Users/user/.asdf/installs/python/3.11.0/bin:/Users/user/.rd/bin:/Users/user/.asdf/shims:/opt/homebrew/opt/asdf/libexec/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Library/TeX/texbin
SHELL: /bin/zsh
PWD: /tmp/pipenv-sync-install-requirements-differences

Could this be re-checked against https://github.com/pypa/pipenv/pull/6282

I wonder if this is related as well to:  https://github.com/pypa/pipenv/issues/6101


go: Minor funTest improvements

@fviernau I'd be fine with merging this and to resolve the unrelated CI issues later.


omiting "io.flutter.embedding.android.SplashScreenDrawable" because i…

Description
omiting "io.flutter.embedding.android.SplashScreenDrawable" because it is deprecated – in Flutter 2.5 and later.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Hey @tahamv, do you mind linking to the documentation which states deprecation? Also -please sign the CLA before we can review. Thank you.

Hey @russellwheatley, you can find the documentaion in this link


Caesar multi language support

Coverage increased (+0.01%) to 99.561% when pulling 1edb0cf29638614b3590fd94986d248904e24d59 on caesar_multi_language into 748cfef98287c36e3c1f3226bdf88161db7442bf on master.


Desktop rendering exception causes click events to stop working

Steps to Reproduce

Run the counter app on macOS:

flutter channel dev
flutter config --enable-macos-desktop
flutter upgrade
flutter create counter_app
cd counter_app
flutter run -d macos

Click the FAB and observe that the counter increments correctly.
Make the window small so that a rendering exception is thrown:

For more information see https://dart.dev/null-safety/unsound-null-safety
flutter: ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
flutter: The following assertion was thrown during layout:
flutter: A RenderFlex overflowed by 3.0 pixels on the bottom.

Make the window larger again and click the counter a few times, and observe that not every click increments the counter.

Logs
flutter doctor -v
[✓] Flutter (Channel dev, 1.25.0-4.0.pre, on macOS 11.0.1 20B29 darwin-x64, locale en-US)
    • Flutter version 1.25.0-4.0.pre at /Users/john/code/sdks/flutter
    • Framework revision a7f5fd5360 (7 days ago), 2020-11-30 13:14:13 +0100
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Xcode - develop for iOS and macOS (Xcode 12.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2020.2.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 51.0.3
    • Dart plugin version 202.8070

[✓] Connected device (3 available)
    • macOS (desktop)  • macos      • darwin-x64     • macOS 11.0.1 20B29 darwin-x64
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 87.0.4280.88

! Doctor found issues in 2 categories.

CC: @dkwingsmt @gspencergoog

Which version of macOS was this on?

Oh, NM: macOS 11.0.1

This is almost certainly a duplicate of https://github.com/flutter/flutter/issues/70529

Yeah this is a dupe of #70529

Web issue is here: https://github.com/flutter/flutter/issues/64961


feat(reporter): be able to display the date and time at which the JSON-files were generated

The purpose of this PR is to be able to display the date and time at which the JSON-files were generated.
A new option called displayReportTime has been created for this purpose.
When this option is set to true, a new column called Date will be added in the Features Overview, just beside the Duration column.
This column will display the creation date of the corresponding JSON-file.
The date is formatted like this: YYYY/MM/DD HH:mm:ss, so that the user can sort the report by dates ascending or descending.

Coverage increased (+0.04%) to 98.758% when pulling 199136edb076902b71ac8b2766dc493f32315b92 on hdorgeval:master into 4e98313d4b3463fa5ff295d09a804481768fa080 on wswebcreation:master.

@hdorgeval
I've released a new version, thanks for your help https://github.com/wswebcreation/multiple-cucumber-html-reporter/releases/tag/v1.18.0

Hi @wswebcreation , thanks for the release :)


Bump to Maven 3.8.8

Maven 3.8.7 is not available for download anymore, so the previous URL would return a 404

Why not 3.9.5?

Why not 3.9.5?
It's a patch version bump, figured it would be easiest. But we should be able to do 3.9.5 indeed.


make cargo-dist opt-in for binaries

Hi, we're looking to adopt cargo-dist for releasing Turborepo. However, we share a repository with other projects, and therefore have multiple binaries in the workspace. I noticed that you can opt-out for a binary by setting publish = false or dist = false.  I was wondering if there's a way to instead make cargo dist opt-in by default, so you have to explicitly annotate publish = true. That way if someone adds a new binary but forgets to annotate it, we won't publish it by accident.

Indeed, you can! If you set
[workspace.metadata.dist]
dist = false

Then that setting gets inherited by every package, so they have to manually override it with
[package.metadata.dist]
dist = true

Awesome, thanks!


PR: Add new test for unnamed first cell and debugcell

Description of Changes
Add more test and uses spyder-kernels #134

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #10048
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

Hello @impact27! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/ipythonconsole/comms/tests/test_runcell.py:

Line 46:80: E501 line too long (83 > 79 characters)

In the file spyder/utils/icon_manager.py:

Line 148:80: E501 line too long (95 > 79 characters)
Line 149:80: E501 line too long (117 > 79 characters)

Could you retrigger the failing test?

@impact27, this is ready. Please don't add more commits here.


[utils] Configurable SSL cipher list

Allows working around the weak ciphers by setting to DEFAULT@SECLEVEL=1
Needed for ceskatelevize.cz with recent Linux distros.
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[x] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
In latest Debian Linux (unstable), SSL library does not accept small Diffie-Hellman keys by default. Because of this, downloading from ceskatelevize.cz fails with the following error:
ERROR: Unable to download webpage: <urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)> (caused by URLError(SSLError(1, '[SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)')))
This patch allows to work around this by specifying the cipher list manually, eg. youtube-dl --no-check-certificate --ciphers DEFAULT@SECLEVEL=1 https://www.ceskatelevize.cz/porady/11784224641-king-skate/

Any hope that the developers could merge this?
Implementation wise, I think it would be better if the user didn't need to know how to specify --ciphers. Just using --no-check-certificate or --prefer-insecure should do the right thing and allow insecure ciphers. It should be easy for a user to download videos from websites using old certificates, not difficult.

Parameter --legacy-server-connect was enough to resolve my issue (urlopen error [SSL: DH_KEY_TOO_SMALL] dh key too small) when downloading from weak host.

Parameter --legacy-server-connect ...

... of yt-dlp, not yet implemented here.


Connecting to a server without password is impossible

The confirm button is deactivated unless a password is typed.

This affects the port dialog too. Empty should equate to the default (7777), but the Confirm button is disabled until something is typed into the field.

There's a method in the text input popup class (forget the exact name) that marks the input as invalid when it's empty. Should be an easy fix if someone would like to make a PR.

I was looking into it the other day out of curiosity. I'll be unavailable for about a week, but if there's no rush I can take another look when I return.

#46 has this resolved


how does fly.babel.js

dove into fly source code and cannot get who fly can use babel for Flyfile.babel.js. can you help me?

That function is here

okay, got it.
fine, fly is already using interpret. have you seen liftoff, which is usually used coupled with interpret?

@MadcapJake Thanks.
@iamstarkov I am completely open to improve fly-util :+1:
Now, I remember I checked out liftoff while I was researching other build systems and this came up while reading gulp's source, but honestly I couldn't readily figure out how to use it and felt frustrated :laughing:
Going over liftoff documentation it appears more complicated than Fly itself. This is still totally open to debate, if you can show me how using liftoff can be implemented or explain how it would help make things better I will absolutely consider it.

If anyone has suggestions to improve fly-util, I'll see you at the other end of the rainbow.


Typo error on class name. Should be .orange-text not .brown-text.

Challenge Override Class Declarations by Styling ID Attributes has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.0) Gecko/20100101 Firefox/52.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

Hello World!

Hi, I noticed that there is a typo error in the instructions for this lesson,  I attached a screenshot showing the typo.

As you can see it is stated as brown-text class where in to complete the lesson you should put a orange-text class and an orange color text.  As seen in this screen shot.

@FaalVedtuz
but that is example code.   it said here's an example of what this look like:
you didn't notice?

@FaalVedtuz thanks for the issue. As @texas2010 has pointed out, this is just an example.  Hope this makes sense. Closing as not a bug. Happy coding!


Get temperature through the IR camera

Hi all,
I'm would like to develop a program able to lively detect faces and to check if it's a real person or just a picture/video  (in particular by liveliness, heat and 3D checking).
To do so, I need to remotely measure the temperature of a body using the IR camera.
What I though about is :

Get RGB image
Detect face and crop the IR arround
Compute the average temperature (+ maybe check on special coordinates)

So far, I'm not able to convert the a4k IR image into a more friendly structure. I don't really know either how to retrieve the temperature.
Is there a way to easily access this information through the SDK ?
I'm using the C# Wrapper, Emgu and Keras (for the Learning part)

@ClementVincent, thank you for your question! This device was not designed to capture body temperature and unfortunately we do not have any plans to do so.

If I may add to this answer to give the asked some information they did not ask for but probably needs to hear. As far as I know, there is not a way to get radiometric information from any thermal image without proper radiometry which in most instances is built into a thermal sensor by means of a flat field shutter with a thermocouple attached. Otherwise you are not able to corollate the data to real world absolute temperatures.


Cannot Read Files using archaius.configurationSource.additionalUrls

I am trying to leverage on Archaius for dynamic loading of property files.
I am trying to access properties defined in the project class path and also on the system class path.
When I try to test the code, the files from the system class path are not getting loaded.
I wanted to specify a list of files that need to be read from the system classpath.
I am trying to test this in my spring project.
@Before
public void setup() {
ConfigurationManager.getConfigInstance().setProperty("archaius.deployment.environment","dev");
ConfigurationManager.getConfigInstance().
setProperty("archaius.configurationSource.additionalUrls","file:///Users/rramakrishnan/innovation/innovation-third.properties");
}

Appreciate any help on this.
Thanks
Raj.

You got a slash too much within your Url.
IMHO you need to configure "file://Users/rramakrishnan/innovation/innovation-third.properties"
I made the same mistake and it took me hours...


Working example with angular2-webpack-starter not working

I've forked your fork of angular2-webpack-starter (to https://github.com/vesteraas/angular2-webpack-starter), and added the following markup to src/app/app.component.ts:
Modal


feat(LICENSE): Relicenses to Apache 2 with LLVM exception

This is in preparation for moving this repo into the Bytecode alliance as indicated in https://github.com/bytecodealliance/governance/issues/88

@calvinrp since you also have a commit to this repo, I'd like to confirm that you're ok with me relicensing those contributions to Apache 2 with LLVM exception

@calvinrp since you also have a commit to this repo, I'd like to confirm that you're ok with me relicensing those contributions to Apache 2 with LLVM exception

Ok with me.

LGTM


1.3.16 is not on Maven Central

see https://search.maven.org/artifact/io.dropwizard/dropwizard-core/1.3.16/bom

@lutzhorn True, I forgot to release the staging repository on Sonatype OSSRH. Should be here with the next synchronisation (1-2 hours).
Thanks for reporting this! 👍


End-to-End Weather App Scenario Part 8

Hi, at step6, the given URL throws the following error.
"HTTP Status 500 - Servlet.init() for servlet CXFServlet threw exception"
I have followed the exactly same steps as described,
I am not sure where to check and how I can fix the issue. Please help.
regards,
Shinichi
Error report.zip

Does this change only happen at Step 8?  Until that point, the web application is working correctly?

Since I haven't heard a response, I am closing this ticket.  Please re-open it if you are still having problems.


Tor address seems to be down (or changed)

This is not strictly a client issue, but, nevertheless, since instructions to access keybase.io via Tor using the http://keybase5wmilwokqirssclfnsqrjdsi7jdir5wy7y7iu3tanwmtp6oid.onion address are on the keybase client (non-GUI) manual page, I was just wondering — is that Onion address still operational?
As far as I can test it, it seems to have disappeared from the Onion-world :-(
Note that this address is still shown on the official webpage for keybase.io ...

Back in 2022, @heronhaye resolved #24477. Maybe they can bring it back again?


GROOVY-11263: Analyze dead code

https://issues.apache.org/jira/browse/GROOVY-11263

Besides the extra class bytecode, is there a strong reason for this?  The issue ticket pops up out of the blue without much explanation.
There are so many possible paths that I think this will be another feature that gets you a quick 80% of the way and then will have issue tickets forever with uncovered scenarios.  Would it be easier to use a bytecode path analyzer?  Something that has been through research and proving phases?
I think ASM does some of this analysis already but does not provide any API to ask if a path is dead -- but it does know internally using path analysis.  It replaces dead code with NOP instructions.  Maybe just a NOP pruning is in order.

@eric-milles
As we all know, source code is meant for developers to read, and the less redundant code there is, the more developer-friendly it becomes.
Admittedly, it's challenging to cover all scenarios of dead code, but at least we can support some common ones and gradually improve, which aligns with the principle of program evolution.
As for ASM's analysis of dead code, at least I haven't seen any relevant API it offers. If you have any new findings, please share them with us. Thanks in advance.

source code is meant for developers to read, and the less redundant code there is, the more developer-friendly it becomes.

So now you have a benefit statement that you can put in the ticket.  It would be nice to have a period of review on the problem statement and cost-benefit analysis before being forced to review code in hand.
If a user does not care about the extra code to read and the extra bytecode generated, is there a way to turn this off?
Have you still left it as a compiler error or did you soften it to a warning?  If analysis mis-identifies some code as dead code and fails compilation, what can a user do to get their previously-working code to compile?
If you do not address such concerns, then why not leave this out as a global transform that you apply to your own code?  Why must it be core code from the very start?
It's a -1 from me unless you can more carefully spell out the problem definition and the solution ramifications.

We can add a option to prevent or warn dead code or disable check totally.
Here is the table to show how mainstream programming language to handle dead code. Most of them prevent or warn the dead code, so I think it's good choice for Groovy to align with most of them.

Language
Allows Consecutive return (Dead Code)
Compiler/Interpreter Behavior

Java
No
Marks as unreachable code, may cause a compile error.

C++
Yes
Might warn but allows compilation.

C#
No
Identifies unreachable code, causes a compile error.

Python
Yes
Does not prevent dead code, allows execution.

Scala
Yes
Might issue a warning but allows compilation.

Kotlin
No
Detects unreachable code, causes a compile error.

JavaScript
Yes
Does not check for dead code at compile time.

dead code analysis, as its name shown, it just traverses AST and does not change the AST, so no tranforming [sic] changes involved.

This was understood.  The point is that if you add a compiler error you may fail code that previously compiled.  A compiler warning allows the user to be notified but continue using code unchanged.  Also, you scan the AST at a specific point in time.  If later AST transformations occur that address the dead code scenarios, you have false positive.
I'm just trying to have you describe your reasoning for when to do the analysis.  Even the class generator does a bit of instruction re-ordering that may or may not introduce dead code paths.  It seems the goal of this change is to identify any dead statements explicitly represented in the source file.  If that is indeed the case, it would be good to state all of this in the original problem description.


metrics should be accessible via API

import the_segmentation_game as tsg
tsg.metrics... ()

Throws an error. We should import .metrics in __inity__.py, I think.

from the_segmentation_game import metric

... works with the 0.2.0 release


[REVIEW] Malicious-Debian-Package-Maker

Project link
https://github.com/padsalatushal/Malicious-Debian-Package-Maker

Some suggestions from my point of view -

Add ISSUE & PULL_REQUEST templates

Happy Learning 💚


[fearure]  generic xmi parser

create a generic xmi parser 2.x

It could be cool but it will unfortunately never happen as some UML editors export their XMI files with some differences:

the header (used to detect the editor without asking the user),
attributes never are the same (for instance, the enums aren't always the same everywhere),
even types differ!

However, I do agree... some editors could be refactored to share the same code.
However, XMI could change overtime (there was a bug in Modelio in v3.4).
Unless UML editors actually respect the XMI spec and export a common XMI file, and JUML's work would be made easy... I don't think there's a chance of seeing it happen =(

;o(


Deprecate useRucio parameter within MicroServices; remove PhEDEx logic from MSOutput/MSMonitor

Fixes #10093
Fixes #10052
Fixes #9996
Status
not-tested
Description
As the title says, no longer verify which Data Management system to be used, Rucio becomes the only option now.
In addition to this, removed all the DDM/PhEDEx base code from the MicroServices (MSCore/MSMonitor/MSOutput).
Is it backward compatible (if not, which system it affects?)
no, in the sense of no longer supporting PhEDEx.
Related PRs
none
External dependencies / deployment changes
Deployment changes: https://github.com/dmwm/deployment/pull/991

I still have to run some basic tests, but I don't expect any bad surprises and it's ready for review.

I'd like to get it deployed in testbed this morning, so I'm getting it merged now.
Todor, feel free to leave any comments/review though.


affected/package: benchmark ReportMetric panic on concurrent call

What version of Go are you using (go version)?

$ go version
go version go1.18.4 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="auto"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/jack/Library/Caches/go-build"
GOENV="/Users/jack/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/jack/.go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/jack/.go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.18.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.18.4/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.18.4"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/zv/mhvsb81s63b7kk08sfhfq8d00000gn/T/go-build1807741596=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

example code: https://go.dev/play/p/ToeyneuJPcT
What did you expect to see?
no panic here

Copy panic log here
fatal error: concurrent map writes
fatal error: concurrent map writes

goroutine 1200 [running]:
runtime.throw({0x4ae646?, 0x0?})
	/usr/local/go-faketime/src/runtime/panic.go:992 +0x71 fp=0xc0001de740 sp=0xc0001de710 pc=0x431e91
runtime.mapassign_faststr(0x4ab755?, 0x2?, {0x4ab755, 0x2})
	/usr/local/go-faketime/src/runtime/map_faststr.go:212 +0x39c fp=0xc0001de7a8 sp=0xc0001de740 pc=0x4114bc
testing.(*B).ReportMetric(...)
	/usr/local/go-faketime/src/testing/benchmark.go:356
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:7 +0x65 fp=0xc0001de7e0 sp=0xc0001de7a8 pc=0x48e665
runtime.goexit()
	/usr/local/go-faketime/src/runtime/asm_amd64.s:1571 +0x1 fp=0xc0001de7e8 sp=0xc0001de7e0 pc=0x45cdc1
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1 [chan receive]:
testing.(*B).doBench(0xc0000c4000)
	/usr/local/go-faketime/src/testing/benchmark.go:285 +0x7f
testing.(*B).run(0xc0000c4000?)
	/usr/local/go-faketime/src/testing/benchmark.go:279 +0x6e
testing.Benchmark(0x4b3f48)
	/usr/local/go-faketime/src/testing/benchmark.go:824 +0xf5
main.main()
	/tmp/sandbox1758758439/prog.go:18 +0x25

goroutine 59 [runnable]:
main.BenchmarkReportMetrics(0xc0000c4000)
	/tmp/sandbox1758758439/prog.go:12 +0x87
testing.(*B).runN(0xc0000c4000, 0x2710)
	/usr/local/go-faketime/src/testing/benchmark.go:193 +0x102
testing.(*B).launch(0xc0000c4000)
	/usr/local/go-faketime/src/testing/benchmark.go:334 +0x1c5
created by testing.(*B).doBench
	/usr/local/go-faketime/src/testing/benchmark.go:284 +0x6c

goroutine 1393 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1391 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1394 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1277 [running]:
	goroutine running on other thread; stack unavailable
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1392 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1396 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1395 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1389 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1388 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1387 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1386 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1390 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1385 [runnable]:
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:6
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

goroutine 1277 [running]:
runtime.throw({0x4ae646?, 0x0?})
	/usr/local/go-faketime/src/runtime/panic.go:992 +0x71 fp=0xc000186f40 sp=0xc000186f10 pc=0x431e91
runtime.mapassign_faststr(0x49a6e0, 0xc000012030, {0x4ab755, 0x2})
	/usr/local/go-faketime/src/runtime/map_faststr.go:295 +0x38b fp=0xc000186fa8 sp=0xc000186f40 pc=0x4114ab
testing.(*B).ReportMetric(...)
	/usr/local/go-faketime/src/testing/benchmark.go:356
main.BenchmarkReportMetrics.func1()
	/tmp/sandbox1758758439/prog.go:7 +0x65 fp=0xc000186fe0 sp=0xc000186fa8 pc=0x48e665
runtime.goexit()
	/usr/local/go-faketime/src/runtime/asm_amd64.s:1571 +0x1 fp=0xc000186fe8 sp=0xc000186fe0 pc=0x45cdc1
created by main.BenchmarkReportMetrics
	/tmp/sandbox1758758439/prog.go:12 +0x87

Program exited.

try aquire lock on benchmark extra map write
https://github.com/golang/go/pull/54038

This looks like an incorrect use of ReportMetric though

This looks like an incorrect use of ReportMetric though

I agree, especially given this sentence in its documentation:

ReportMetric overrides any previously reported value for the same unit.

Without a happens-before relationship between the calls to ReportMetric, the notion of “previously reported” is not well defined.
By convention, Go methods that mutate the state of a data-structure (as ReportMetric does) should be considered unsafe for concurrent use unless the documentation explicitly says otherwise.


Send Tweet Tool fails

⚠ Check for existing issues before proceeding. ⚠

[X] I have searched the existing issues, and there is no existing issue for my problem

Where are you using SuperAGI?
MacOS
Which branch of SuperAGI are you using?
Main
Do you use OpenAI GPT-3.5 or GPT-4?
GPT-4
Which area covers your issue best?
Tools
Describe your issue.
When trying to tweet, the tool returns:
Error1: 'NoneType' object has no attribute 'value', AttributeError, args: {'tweet_text': 'Hello', 'is_media': False, 'media_files': []}
How to replicate your Issue?
Instruct an agent to tweet
Upload Error Log Content
Error1: 'NoneType' object has no attribute 'value', AttributeError, args: {'tweet_text': 'Hello', 'is_media': False, 'media_files': []}

Additional information: When clicking on "Authenticate" in the toolkit - the api returns an undefined OAUTH token:
https://api.twitter.com/oauth/authenticate?oauth_token=undefined

Restarted SuperAGI to fix.


Review/reform toString and tryParse

The difference between toString and (the F# built-in) string may be subtle.
I think toString function can play together with tryParse in order to get a sort of mini-serializer for simple F# values.
A rule can be enforced, for parse / tryParse:  toString >> parse = id.
As a consequence, toString for a string will add the double quotes and tryParse will expect them.
The same way tryParse has a fallback mechanism, toString (or another function can be created) can fallback to the generic string function. The idea behind this is that toString is free of any rule as long as there is no correspondent tryParse defined for that type.
Here are some examples:
toString "abc"
> val it : string = ""abc""

toString ["a"; "b"; "c"]
> val it : string = "[a; b; c]"

toString (set ["a"; "b"; "c"])
> val it : string = "set [a; b; c]"

tryParse<string> "abc"
> val it : string option = None

tryParse<string> ""abc""
> val it : string option = Some "abc"

Here's a relevant discussion in Haskell for their read / show functions
Another thing is to consider renaming these functions: toString might be confused with .NET ToString instance member and parse / tryParse when using any parser library.
Also, if we decide to keep toString, parse (or maybe tryParse) should be fromString. If we think from the point of view of serializer this makes more sense, but the term string doesn't add any information about the format, it should rather be something like toFSharpString and fromFSharpString or shortened as toFsString / fromFsString.
Finally we can consider keeping the parse / tryParse functions and implement a fromFsString that returns a Result type, with a detailed parsing error description .... and possibly keep the parse / tryParse functions aligned with the Parse .NET methods, which means language agnostic (?) and no rules at all.
Many open questions.
Please drop your thoughts, specially @mausch who implemented initially the ToString abstraction. Keep in mind consistency is a high premise of this library.

I like the idea!

It would be nice to have something like edn but for f#. Some deviations might be needed, but you could formalize a standard format as a subset of f#.

I think the main difference is the strong typing. We can't have heterogeneous lists for instance and instead of symbols we'll have some records with custom printer/parser.
But I see a value on having a printer that output values in an F# format. Sometimes I need to execute something that will output a value and I need to hardcode that value for example in a test. Copy-pasting work only with very basic stuff, but if you have a DateTime, it prints the internal structure whereas it would be useful for this scenario to print the DateTime constructor with all the arguments that will produce that value.
This, of course would not be possible to use with every type, some types can't be re-created by simply applying a constructor + arguments.
Another consequence of this is that a separate generic function can be created for parsing, that uses F# language itself to parse the values.


XCode 9.2 / Swift 4 - selector required @objc tag

func pageControlDidTouch() functions needs @objc tag to support latest Xcode version.

Fixed with 14b749e655738551da9c123ba64e8b4f46ae24fe


Added details of new Pipeline Setting

https://harness.atlassian.net/browse/CDS-80322 contains the details.
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://657dd405c7a0a5512993aa31--harness-developer.netlify.app

@SudarshanPurohit Do we have a Jira for release notes?

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://657f9e72738f65567d8108f7--harness-developer.netlify.app


Centralize test indexes for integration tests

Problem
Our integration tests are currently very flakey (meaning they fail in an non-deterministic manner depending largely on fluctuations in latency on backend operations).
Solution
Centralize the creation and deletion of indexes for integration tests; cleanup the tests where I can.
The tests that now use the centralized indexes:
- Control:
- describeIndex.test.ts
- listIndexes.test.ts
- Data:
-  fetch.test.ts
- list.test.ts
- query.test.ts
The tests that still have to create/delete their own indexes because their operations are difficult to undo:
- Control:
- configureIndex.test.ts
- createIndex.test.ts
- Data:
- delete.test.ts
-  upsertAndUpdate.test.ts
New jobs & files

I added a job in testing.yml called setup that calls a file called setup.ts (src/integration/setup.ts)
I added a job in testing.yml called teardown  that calls a file called teardown.ts (src/integration/teardown.ts)
setup.ts sets up (creates and seeds) a shared serverless index (only serverless for now b/c we don't have pod-based data plane tests) called "integration-test-serverless"

I have put a todo in this file to refactor it; right now, it's quite rudimentary in the way it loops and checks conditions; you'll notice other todos in other files that point to where we need more tests, etc. I'd like to keep these in there for now, if that's okay.

teardown.ts deletes this index
I found some tests that were not actually testing what they intended to, so I have marked those as skipped for now (e.g. createIndex.test.ts > test('insufficient quota')`)

Bug fixes

Last week, @austin-denoble and I noticed a bug in waitUntilReady where the status sometimes evaluated to Ready without the index actually being ready. So, this PR includes a fix to that function that also checks for state.ready being true and adds a value (that it also checks for) to the IndexModelStatusStateEnum that accounts for an index's state being Upgrading, which accounted for a lot of flakiness in the configureIndex tests.

Notes

The goal of this PR is to decrease flakiness
I removed one of our Bun versions to try to get the time down a bit; we might want to experiment with upping the max-parallel field too in testing.yml (although I tried removing it altogether and we had failures)
I removed the job in testing.yml that calls utils/cleanupResources.ts, since I replaced it with my Teardown job. This file (cleanupResources) is still called via cron, though, by testing-cleanup.yml
I decided not to use jest's globalSetup and globalTeardown capabilities because they interfered with how our integration tests run in parallel in CI -- the "global"-ness of these jest fixtures would be per option in our matrix, so even though they would be "global" to all test files, they would not be global across all CI runs (node, bun, edge, etc.), so collisions happened.

Type of Change

[x] 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
[x] Infrastructure change (CI configs, etc)
[ ] Non-code change (docs, etc)
[ ] None of the above: (explain here)

Test Plan
CI passes consistently

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1208439494339500
https://app.asana.com/0/0/1207545518662985

(Recent CI failures are due to super flakey upsert-and-update test. Have removed for now. No way to win with that test despite adding a big sleep. Will revisit later.)

(Recent CI failures are due to super flakey upsert-and-update test. Have removed for now. No way to win with that test despite adding a big sleep. Will revisit later.)

Okay. @austin-denoble and I decided that we will assert the client calls the correct endpoint w/the correct params, but not assert things like updates, etc. are actually reflected later. This eliminates a ton of waiting time + works towards separation of concerns, since if updates (e.g.) don't work, that is ultimately a bug with the backend, not the client.

We have had 3 successful* runs in a row. I am declaring the flakiness (that we control) surpassed!
*There is a bug with list where sometimes a pagination token is not included in the response. Not counting this as a 'flake' on our end.

I decided not to use jest's globalSetup and globalTeardown capabilities because they interfered with how our integration tests run in parallel in CI -- the "global"-ness of these jest fixtures would be per option in our matrix, so even though they would be "global" to all test files, they would not be global across all CI runs (node, bun, edge, etc.), so collisions happened.

When I initially was thinking about updating things I was thinking "global" in terms of all files - so a single "test" run would be per option in the matrix.
Instead of having a hard-coded "serverlessIndexName" that gets inherently shared, I'd prefer if each run of integration tests had an index name that was randomized, and then shared across all test files in that run.
I'm not sure what issues you were seeing when using the global setup / teardown in Jest. The other client integration test suites tend to create randomized names for indexes and resources per run, so things are shared globally across integration tests / files, but not all possible integration tests that might be run in CI when factoring in a matrix.

Note: we spoke about this offline. We are sticking w/the current approach of having setup and teardown jobs, since it's more efficient, but we are randomizing the index names to allow simultaneous runs by diff users on the same Pinecone account 🎉


Apple M1 and Atom — will it work?

Can someone confirm that Atom is working on Apple SOCs practically with A14 (if you have a transition kit) and M1 (if you are going to buy it anytime soon) or theoretically? And is Node going to work without issues on this new system?
UPDATE
If your Atom doesn't run on M1, right click the app in finder, open it and when prompted to install Rosetta 2, install it.

Close

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀

this is a valid question!

@darangi can you please re-open this?

@darangi it's hard to fill out the issue properly cause details of it are completely unknown for now. We need a platform to discuss the Atom performance on the new Macs.

Just set up new MacBook Air with M1. Atom will not launch. Googling how to launch. Came across this thread.

Thanks for reporting this, This could be a problem with electron itself.
We will update the issue with our findings

Just set up new MacBook Air with M1. Atom will not launch. Googling how to launch. Came across this thread.

@ash37 do you have Rosetta 2 installed?

Electron has just been updated to support Apple Silicon: https://www.electronjs.org/blog/electron-11-0

Just set up new MacBook Air with M1. Atom will not launch. Googling how to launch. Came across this thread.

@ash37 do you have Rosetta 2 installed?

No, I did not. Had to right click app in finder. Open. Was then prompted to install Rosetta 2.
Launched with Rosetta 2.

@ash37 great! So how fast is Atom with Rosetta 2 compared with the native x86 environment?

Still quick.
https://dropmefiles.com/WU267

@ash37 would you (or anybody else) also try:

https://github.com/platformio/platformio-atom-ide-terminal
https://docs.brew.sh/Installation
https://classic.yarnpkg.com/ru/docs/install/#mac-stable
https://vuejs.org/v2/guide/installation.html
https://gridsome.org/docs/#how-to-install

@ash37 how much RAM do you have in your new MBA M1? Could you also test if Atom becomes sluggish under some load?

13" MacBook Pro, M1.
Atom works mostly, but will hang intermittently with one or more (I've seen three, possibly due to force quit/restart) Atom Helper threads at 95-100% CPU.

@eneroth how much RAM do you have? And what kind of tasks Atom is performing at these moments?

@eneroth how much RAM do you have? And what kind of tasks Atom is performing at these moments? It would be great if you recorded this on video.

OK, I will give it a shot!
16GB of RAM.
I'm using it for Clojure and Rust, so packages are to support development in these two languages.
I downloaded Nightly as well, which turned out to exhibit the same behaviour.

@eneroth thanks! It would be useful to compare the current version of Atom with the current version of VSCode AND with a beta version of ARM VSCode https://code.visualstudio.com/insiders/

Atom is still on electron v6. They have a ways to go if they need to upgrade to v11 one version at a time.

Hope this transition will be surprisingly quick for once, then… 😂

Atom is still on electron v6. They have a ways to go if they need to upgrade to v11 one version at a time.

Does it mean that an optimized version of Atom is not going to be released soon and it's better to switch to VSCode?

@sergeyfilimonov Atom did the thing, and I caught a bit of it on tape. It seems like it is the renderer that gets traumatised by something.

Does it mean that an optimized version of Atom is not going to be released soon and it's better to switch to VSCode?

Atom was updating electron more frequently for a while but I haven't heard anything in a while about a v7 upgrade. I wish Atom was a little more transparent about their roadmaps but that information is either privileged or non-existent.
There is a community run version of atom that will hopefully be ready soon and should be a little faster with development since it doesn't have all of the backwards compatibility to worry about.
https://github.com/atom-ide-community/atom

Thanks for raising this issue! As has been pointed out, Atom is still on Electron 6. We have been working on at plan to get Electron upgraded to at least a supported version and the release of Apple M1 has escalated the urgency of those plans. This is something that is very much on the team's radar and we intend to have a plan in place in the coming weeks.

@jjcaine could you possibly allow that planning to take place in public? I think it would give everyone ease to see the plan progressing instead of not hearing anything for a while and wondering if it was forgotten or put on the back burner.

Same issue — Atom hits 100% of CPU usage. Will switch to VSCode for some time.

Same issue with M1 — Atom hits 100% of CPU usage.

Still not fixed yet, this would put me off upgrading, and I want to, but I spend most of my life in Atom with many tabs open at once, currently using a 2018 15" MacBook Pro, 6 core, but 15" is too big, and want to go 13", the M1 looks perfect, but this is putting me off.
Will Atom be supported?

@ptscopedev I wouldn't though say that this issue is arising absolutely every time after 10 mins of Atom running. I saw this issue only once.

I'm seeing this issue once per session once it has happened it doesn't happen until the relaunch of the app. It mostly occurs for me when i'm trying to save a file.

For me it happens about once per 30 minutes to an hour, on average. Sometimes it happens a lot, sometimes it can go a while before it happens again.

@eneroth @arundaniel-kennedy for about safe mode?

@sergeyfilimonov   Haven't tried that yet

Let's log all cases here. Today a Node (Vue) process launched from a terminal window powered by platformio-ide-terminal package made the CPU work at 98% load which made my M1 pretty warm. I had to close the process and relaunch it.

+1 Atom support is the only thing keeping me from switching to M1

+1 for me too. Please, bring M1 support to Atom asap! Thanks

+1 for me too. Please, bring M1 support to Atom asap! Thanks

+1 m1 support needed asap!

+1 m1 support needed asap!

Atom is holding you back from getting an M1? Amazing. I chose to switch to another editor 🤷

Atom is holding you back from getting an M1? Amazing. I chose to switch to another editor 🤷

Actually atom runs just fine on my m1 mbp too, I usually get around 1-3% cpu usage, I guess that's rossetta or something
Hope they do make it run for atom!

Actually atom runs just fine on my m1 mbp too, I usually get around 1-3% cpu usage, I guess that's rossetta or something
Hope they do make it run for atom!

Is dit the end of the discussion? I want to replace my old macbook for a new one. I is manly used for python development with Atom as IDE. Is atom now running fine?
Chris

Is dit the end of the discussion? I want to replace my old macbook for a new one. I is manly used for python development with Atom as IDE. Is atom now running fine?
Chris

It's fine but I had to switch to VS Code Insiders Edition for M1, it's faster and doesn't overload CPU which Atom does sometimes.

lallqkqkqkqla
On Wed, Feb 24, 2021, 2:53 PM Sergey Filimonov<EMAIL_ADDRESS>wrote:

Is dit the end of the discussion? I want to replace my old macbook for a
new one. I is manly used for python development with Atom as IDE. Is atom
now running fine?
Chris
It's fine but I had to switch to VS Code Insiders Edition for M1, it's
faster and doesn't overload CPU which Atom does sometimes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/21688#issuecomment-785375961, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNRQZC3QPE3OQ26RYKUJJ3TAVRLNANCNFSM4TRYYN2A
.

Is the development of Atom dead ?
All major software now work natively on Apple Silicon, not to mention VS Code, which is also based on Electron.
I remember when Atom was on beta and then got released years ago, it was the most cool editor ever !
Now, I've just got the feeling it has staled and its development is really lagging behind.

Is the development of Atom dead ?
All major software now work natively on Apple Silicon, not to mention VS Code, which is also based on Electron.
I remember when Atom was on beta and then got released years ago, it was the most cool editor ever !
Now, I've just got the feeling it has staled and its development is really lagging behind.
Do you guys need volunteers for testing ?

AFIAK the maintainers are trying to switch to electron 9. Meaning, M1 support is coming soon (I think).
Meanwhile, nobody is forcing you to use Atom and you can give VS Code a try (I personally use both, but I mainly use Atom).

The problem has started again in 1.54.0. For sometime i had no issues, but now it's crashing suddenly.... again.

AFIAK the maintainers are trying to switch to electron 9. Meaning, M1 support is coming soon (I think).

Actually, Apple Silicon (M1) support wasn't added to Electron until v11 (see the blog post):

Electron 11.0.0 has been released! It includes upgrades to Chromium 87, V8 8.7, and Node.js 12.18.3. We've added support for Apple silicon, and general improvements. Read below for more details!

So as long as Atom keeps seeing periodic upgrades to the latest Electron releases, we should get M1 support in Atom soon enough.

Yep. Since Atom's got electron 9 now, M1 support should be soon.

This PR may be on track to get Atom running well on Apple silicon, but it looks like it's gonna take a lot of work until it's ready. There are contributors pushing to delay it until the current bugs in electron 9 are fixed as well.

Need update for Apple Silicone ASAP!

ASAP!

You can speed up the process by contributing.

Atom was no longer a viable option, it just continued eating my battery more and more, and I already have 2 Rosetta apps running (OneDrive and discord); and I really don't want another one eating even more battery and resources than it should.

I've switched to IntelliJ IDEA and VS Code for my development purposes.
Atom was no longer a viable option, it just continued eating my battery more and more, and I already have 2 Rosetta apps running (OneDrive and discord); and I really don't want another one eating even more battery and resources than it should.

Traitor! 😤😜

11 nov 2021, does anyone has news about Apple Silicon version of Atom ?

@IMNotMax Let's face it, Atom is an old peace of software. SublimeText already released a new stable version also for the M1.

For a 99$ licence ... atom is great for small personal projects, playing with config files, updating automatically via SSH. I don't work as a Dev, I'm not de Dev. That's why Atom is great for me. The current version works pretty well, but with native apple silicon binaires, it could be lightweight as far as I understand.
Maybe it's not possible, I'm not able to see all the implications of recompiling on another platform.

I had to switch to VS, and it's been a year since Atom has not been adapted to M1.

I had to switch to VS, and it's been a year since Atom has not been adapted to M1.

Yeah, this update requirement marks that Atom is far away from the current progress of IDEs and is not going to catch up. For me, this is the end of Atom. I had to switch to VS and realized that it's at least as good as Atom.

I really want atom for M1.

Moved to VS Code, and it's even better than Atom.

Atom is genuinely getting old.

Finally given up on Atom, installed VS Code and an Atom default dark theme, its wonderful.
Happy at last, was getting sick of lag in Atom randomly
Time to move on
Rob

On 2 Dec 2021, at 16:07, EvadingEvasions @.***> wrote:
Atom is genuinely getting old.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/atom/atom/issues/21688#issuecomment-984770073, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHNKP2AG562LDYKGXGNGS4LUO6KVLANCNFSM4TRYYN2A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Rob Bradley
CEO
Pharos Provisions Limited
https://pharos.pm
T: 01322 903902
M: 07521 423291

In light of the recent update that the Electron 11 pull request was merged, Atom might be really close to native M1 support!
I'm crossing my fingers because I refuse to use VS Code haha, Atom is almost perfect

I might just ditch VSCode for Atom if native M1 support comes! Super excited.

I use Atom and VScode, different tools for different things, but the fact that Atom is not build for my M1 MacBook Pro drives me crazy, it eats a lot of RAM and CPU doing the same things of VSCode, and it's not as snappy, I think I'm going to choose VScode

Hi guys! Is there any news about the topic? I recently switched to a Silicon Mac and just can't use Atom. Initially it started and I was able to install the first packages, then I closed the app and, after restarting it, it doesn't work anymore: it opens, but doesn't show the screen. I can't wait to start working on my new Mac with Atom, but for now I continue with my old Windows. Let's hold on!

id like to hear about this as well!

It will be very nice to get Atom running natively on Apple Silicon :)

I downloaded atom on m1 pro, but its not stable many times i open it and it doesnt open at all

It's not stable for me either. I noticed that if I try to open a folder/project which is a git repo it crashes from the start.
I think a lot of us are waiting now for a new native version of Atom for m1 macs.
Hopefully it comes soon - I assume it shouldn't be too difficult as the new Electron version will take care of the issue.

It's not stable for me either. I noticed that if I try to open a folder/project which is a git repo it crashes from the start.
I think a lot of us are waiting for new native version of Atom.
Hopefully it comes soon - I assume it shouldn't be too difficult as the new Electron version will take care of the issue.

Let's hope ... but in the meantime, time goes on ...

Curious about this as well

Electron 11 supports M1, so if the Atom team manages to upgrade then there is no issue.

@holmesherlockhs Fortunately, the recently-released Atom v1.61.1-beta0 includes an upgrade to Electron v11.4.7, so hopefully that should imply M1 support, at least at the foundation of the editor.
https://github.com/atom/atom/releases/tag/v1.61.0-beta0
https://github.com/atom/atom/pull/22687
Not sure how long it will take for it to become stable, and I haven't tested the beta myself to confirm any architecture or performance differences. But I believe we're one step closer!

I have an M1 Mac, so I should be able to test it. If any others have a M1 Mac, you can test it and report you results here.

I have an M1 Mac and tested out the 1.61.1 beta build, but unfortunately I don't have the dependencies necessary to build Atom from scratch, and the pre-built version only came with an Intel binary, so I can't report anything on native performance yet

Yes it would be great if the core team can compile the pre-built versions as an ARM binary as well!

I have an M1 Mac, so I should be able to test it. If any others have a M1 Mac, you can test it and report you results here.
Me too, but where can I find an ARM binary ? All downloads are Intel.

It does not have separate binaries, because the version is universal. To check if it's arm, open activity monitor and see architecture of the process.

I did, but it is NOT universal, it is an Intel binary (1.60.0).

I confirm 1.60.0 and 1.61.0 are both compiled for intel macs only in the releases. No Univeral versions 😕
I think I will download the repo and compile it myself at this point.

This is a rather old post (Oct 2020, Electron 11). Now there should be Electron 18.01, but it is unclear what should be downloaed for making Atom to run natively on arm64.

Atom hasn't migrated to the latest version yet. Because version 1.61.0 is still at v11.4.7

It works on mac but its horrible. It eats the battery so fast!! It ate my battery in just a few hours on my macbook air m1.

It works on mac but its horrible. It eats the battery so fast!! It ate my battery in just a few hours on my macbook air m1.

Did you check whether it is 'Apple' (Arm) or 'Intel' in 'Activity Monitor' ?
Probably it is Intel because that lets Rosetta run, eating more CPU.

Atom version 1.61.0 when it gets released with electron v11.4.7 will probably compile for mac m1 not as great as 18.0.1 but would be awesome, probably a lot faster

I confirm 1.60.0 and 1.61.0 are both compiled for intel macs only in the releases. No Univeral versions 😕
I think I will download the repo and compile it myself at this point.

I was wondering if you were able to test out a build compiled for ARM?  After all this time I still haven't been able to find a suitable replacement for Atom on M1, its design is just so perfect

I confirm 1.60.0 and 1.61.0 are both compiled for intel macs only in the releases. No Univeral versions 😕
I think I will download the repo and compile it myself at this point.

I was wondering if you were able to test out a build compiled for ARM? After all this time I still haven't been able to find a suitable replacement for Atom on M1, its design is just so perfect

Branch master and 1.6.1-releases does not compile on M1.
IIRC npm or apm (i dont remember) fails to install a dependency, but I haven't looked further.

Switched to VS Code due to this. Don't think that I will come back to Atom... sigh...

I switched to VS Code, although its still not quite right, need to tweak it a bit, Atom for PHP was fantastic, just a shame it runs like pooh on my M1 Pro.
If Atom eventually gets updated to M1, then I will be back, but for now, I will have to live with all my gripes, VS Code for PHP is rather pants, but at least it's stable and fast, and fully supports M1.

Sad to say, I had to give up waiting.   Loved atom, but now using VSCodium (non-telemetry version of VSCode).

Does it mean there will be no arm native version?

it means not more of anything atom related


Will there be multiple db migrations running if multiple rails servers started?

So the dockerfile has this line
ENTRYPOINT ["/rails/bin/docker-entrypoint"]

It will run migration when rails server being started. My question is, if auto-scaling triggers multiple web instances, will that run multiple db migrations at the same time? I think it would be nice if the migration could only run just once, after deployment, not everytime when a web server starts.

That is correct, and that is how the rails 7.1 dockerfiles are structured, so by default I'm matching that.  If your deployment destination supports a "release" step (many do), you can provide an option to not do the prepare.  Here's the instructions provided for fly.io: https://fly.io/docs/rails/getting-started/dockerfiles/#scaling

Interesting, thank you


Breaks JS highlighting - html highlighting is not really usable

Thanks for the effort on this.... so I got it working. But it does not highlight in the manner where it is useable(as othree html5 does). Also, it breaks my vim-javascript highlighting.
I realize I am at a disadvantage here because I am not using a Microsoft product that Polymer is now geared for, but it would be nice if I could use vim with Polymer 3 as I did with Polymer 1.

Without this plugin with no breakage(as the JS should look):

UPADTE:
I took another swing at this. I got it working correctly when I disabled the pangross/vim-javascript plugin. Is there away to use both of these plugins at the same time? For the JS code, vim-javascript is better. It parses better giving more syntax groups that allow for JS customizations.


Download error: decompression get wrong: no output data

Thank you for this great GitHub Action, I'm currently using it on https://github.com/pbek/QOwnNotes!
I'm currently having issues with the Qt 5.7  installation on Windows (some still are using Windows XP) with win32_mingw53.
Config: https://github.com/pbek/QOwnNotes/blob/48f5b73e1b0a200b88c93d82ef6192f7d80fbe03/.github/workflows/build.yml#L61-L69
Build log: https://github.com/pbek/QOwnNotes/runs/880829548?check_suite_focus=true
I always get the error Download error: decompression get wrong: no output data. for all packages:
2020-07-17 06:56:23,560 - aqt - INFO - Downloading qtsvg...
2020-07-17 06:56:23,560 - aqt - DEBUG - Download URL: http://mirrors.ocf.berkeley.edu/qt//online/qtsdkrepository/windows_x86/desktop/qt5_57/qt.57.win32_mingw53/5.7.1-0qtsvg-Windows-Windows_7-Mingw53-Windows-Windows_7-X86.7z
2020-07-17 06:56:24,064 - aqt - ERROR - Download error: decompression get wrong: no output data.

I tried with and without mirror
Qt 5.14.2 works great, only Qt 5.7 doesn't seem to work
When I download the file on my computer it decompresses fine

Has anyone seen something like that?

Sorry for not replying for a while, I've been pretty busy lately.
I think the issue is with aqtinstall itself, so I'd recommend you post an issue there and report back. The developer produces his own decompression utility for aqtinstall AFAIK.

Thank you for the hint!

It is a big issue for aqtinstall, so could you try  following for Qt5.7 for windows?
       extra: '--external 7z'

Thank you very much for the fix, @miurahr. It now works with
        aqtversion: '==0.9.4'
        py7zrversion: '==0.9.0'

@jurplel  Could you mind to update install-qt-action documentation to guide users to use aqtversion >=0.9.4 an py7zrversion >=0.9.1 for Qt5.7 and before?

Yep, I'll do it first thing in the morning.

Having trouble with my test here on windows (with aqtinstall 0.9.4 and py7zr 0.9.1)
https://github.com/jurplel/install-qt-action/runs/942431516?check_suite_focus=true
@miurahr

@jurplel  Please check a combination Qt5.7 with msvc 2015, not with msvc 2017.

Okay, I've got both of those defaults sorted out now. Thank you for your help.

Thank you to both of you!


Is python websockets client recv() blocked? How to set it to receive only when there is a message?

Is python websockets client recv() blocked? How to set it to receive only when there is a message?
async with websockets.connect(url) as websocket:
  wfile = wave.open(sys.argv[1], "rb")
  await websocket.send(''something'')
  while True:
    data = wfile.readframes(2048)
    if len(data) == 0:
      break
    await websocket.send(data)
    res = await websocket.recv()

when server did not send something，the line "res = await websocket.recv()" is blocking.

No, it is not blocking but async. Please read up on that topic in the Python docs.

Thank you, I solved my problem, and I really don’t understand asyncio well.


Don't parse JSON if we've had no response fixes #70

This would have caused the json to be parsed every time the getter is called.

Fixed in 9d9f7cb


Refactor RxJs usages

Please check if the PR fulfills these requirements

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

What kind of change does this PR introduce? (check one with "x")
[x] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
In EventTargetInterruptSource:

filterEvent() runs after throttleTime()

this means there is a race condition that can have bad results: filtered events can still reset the throttle timer, blocking potentially important events from emitting onInterrupt

eventSrc is an array of Array<Observable> but you should use Observable.merge() instead of doing all that housekeeping yourself

What is the new behavior?

filterEvent() runs before throttleTime() so that filtered events don't reset the throttle timer
eventSrc is now a merged Observable
eventSubscription is a single Subscription that subscribes or unsubscribes all events at once

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
I had to fix the formatting a little bit. Someone isn't using EditorConfig.

Do you have a timeframe for when this PR's changes will be published into a new release? I'm currently having a Webpack compile error:
eventtargetinterruptsource.js:43 Uncaught TypeError: __WEBPACK_IMPORTED_MODULE_2_rxjs_Observable__.Observable.fromEvent is not a function
    at eval (eventtargetinterruptsource.js:43)
    at Array.forEach (<anonymous>)
    at DocumentInterruptSource.EventTargetInterruptSource [as constructor] (eventtargetinterruptsource.js:41)
    at new DocumentInterruptSource (documentinterruptsource.js:21)
    at createDefaultInterruptSources (index.js:16)
    at eval (index.js:19)
    at<EMAIL_ADDRESS>(vendor.bundle.js:719)
    at __webpack_require__ (inline.bundle.js:55)
    at eval (keepalive.js:1)
    at<EMAIL_ADDRESS>(vendor.bundle.js:855)

Angular: 5.2.9
Angular CLI: 1.7.3
ng-idle/core: 2.0.0-beta.13
ng-idle/keepalive: 2.0.0-beta.13


Issue: Can not import the Langchain modules.

Issue you'd like to raise.
I installed "langchain==0.0.27" on a linux machine but i am getting the folowing error when i try to import langchain in a script. Was running this with python 3.7.
/home/s0s06c3/lang/lang_env/bin/python /home/s0s06c3/lang/hugging_lanchain.py Traceback (most recent call last):   File "/home/s0s06c3/lang/hugging_lanchain.py", line 2, in <module>     from langchain import PromptTemplate, HuggingFaceHub, LLMChain   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/__init__.py", line 8, in <module>     from langchain.agents import MRKLChain, ReActChain, SelfAskWithSearchChain   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/agents/__init__.py", line 2, in <module>     from langchain.agents.agent import Agent   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/agents/agent.py", line 10, in <module>     from langchain.chains.base import Chain   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/chains/__init__.py", line 2, in <module>     from langchain.chains.conversation.base import ConversationChain   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/chains/conversation/base.py", line 7, in <module>     from langchain.chains.conversation.memory import ConversationBufferMemory   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/chains/conversation/memory.py", line 7, in <module>     from langchain.chains.conversation.prompt import SUMMARY_PROMPT   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/chains/conversation/prompt.py", line 2, in <module>     from langchain.prompts.prompt import PromptTemplate   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/prompts/__init__.py", line 2, in <module>     from langchain.prompts.base import BasePromptTemplate   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/prompts/base.py", line 35, in <module>     class BasePromptTemplate(BaseModel, ABC):   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/langchain/prompts/base.py", line 41, in BasePromptTemplate     @root_validator()   File "/home/s0s06c3/lang/lang_env/lib/python3.7/site-packages/pydantic/deprecated/class_validators.py", line 231, in root_validator     code='root-validator-pre-skip', pydantic.errors.PydanticUserError: If you use @root_validatorwith pre=False (the default) you MUST specifyskip_on_failure=True. Note that @root_validatoris deprecated and should be replaced with@model_validator.
I tried setting this up on my local machine as well but there also got the same issue.
Suggestion:
No response

@devstein I tried that version and this issue was persisting. For now i upgraded my python version to 3.9 and then installed langchain 0.0.219 . I think the issue is due to some version mismatch in the pydantic module but could not find the exact verson required for langchain.

I had this problem with:
langchain==0.0.229
langchainplus-sdk==0.0.20
pydantic==2.0.2
pydantic-core==2.1.2

I had to downgrade pydantic to:
pydantic==1.10.9

Now it works... Not a solution, but a workaround...

I am experiencing a similar issue, however, I am using Pydantic 2 in my project and I am not inclined to use the downgrading method as a solution.

For what it's worth, saw this as well with a Flask server trying to import anything from langchain. The root cause was pydantic. Adding pydantic to pip with a specific version (pydantic==1.10.9) rather than just letting pip install it as a langchain dependency resolved the issue.
My stack trace had a lot of these
File "/Users/neilmurphy/.pyenv/versions/service/lib/python3.9/site-packages/connexion/utils.py", line 116, in get_function_from_name
    module = importlib.import_module(module_name)
  File "/Users/neilmurphy/.pyenv/versions/3.9.14/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "/Users/neilmurphy/.pyenv/versions/service/lib/python3.9/site-packages/ddtrace/internal/module.py", line 190, in _exec_module
    self.loader.exec_module(module)

Downgrading pydantic is what worked for me too. Closing the issue.

It did not work for me. Please help. Below are snippits of my code.
!pip install pydantic==1.10.9
!pip install langchain
!pip install openai
from langchain.llms import OpenAI

How is downgrading Pydantic acceptable? Pydantic v1 and v2 are very different


[flake8-annotations] Fix parsing of "complex" forward reference type annotations in any-type (ANN401)

Summary
Fixes #14695.

The root cause was tricky to find.
"Complex" forward reference type annotations are handled differently. Forward references are "complex" in this case when the raw contents (without quotes) of the expression with the parsed contents is not contained in the string literal.
https://github.com/astral-sh/ruff/blob/84748be16341b76e073d117329f7f5f4ee2941ad/crates/ruff_python_parser/src/typing.rs#L65
Annotations are recursively parsed, for instance:
"'int'" (complex) => "int" (simple)
The raw contents of the expression "in\x74" is not contained in the string literal int and hence requires multiple complex parsing steps: "'in\x74'" (complex) -> "in\x74" (complex). This is rare, and probably that's why the bug went unnoticed.
Parsed type annotations are cached by their start offset:
https://github.com/astral-sh/ruff/blob/84748be16341b76e073d117329f7f5f4ee2941ad/crates/ruff_linter/src/checkers/ast/mod.rs#L2544
As it turned out, for these complex annotations the starting offset was not properly updated (removing the quotes), as well already do for the simple annotations. This caused an infinite loop, and eventually a stack overflow.
Test Plan

Extended the test suite with regression tests.

Do you think this is an issue that should be solved holistically (https://github.com/astral-sh/ruff/issues/10586) ?

As it turned out, for these complex annotations the starting offset was not properly updated (removing the quotes), as well already do for the simple annotations.

Sorry, I'm a bit confused still. Why are we using the range without quotes for the parsed expression in case of complex annotation? Because for simple annotations, we just use the range without quotes for the original string expression.

I think an ideal solution here would be to fix the relocate_expr to transform the entire parsed tree accordingly and then move the range_exluding_quotes in parse_type_annotation which then passes to both parse_simple_type_annotation and parse_complex_type_annotation.


Add Enforce Runtime Attributes rule

Adds a new rule that ensures runtime attributes classes are set to the allowed values.

cc @keith

cc @keith again. And please merge when you can because I don't have permissions.


Multiple mocoWriter

If an application need to mock different hostname, it would be impossible currently.
Solutions :

Move out hostname from behat config and let people configure it at runtime when using MocoWriter
Configure multiple hostname in behat config, create as many MocoWriter as hostnames, and find a way to allow people injecting the good one in their context

In fact I was totally wrong. hostname is just used for heath check purpose. So we should consider to refactore that part to allow multiple health_check

So we could imagine change MocoWriter to add a collections of hostname:port indexed by name :
default:
    extensions:
        Rezzza\MocoBehatExtension\MocoExtension:
            json_file: features/fixtures.yml
            hosts:
                my_first_mock: { hostname: http://coucou.hibou, port: 2113 }
                my_other_mock: { hostname: http://coucou.filou, port: 2113 }

Then the MocoWriter::mockHttpCall should be changed to receive the name of the hosts targeted by this call. We should continue to enqueue the httpCall but also the hosts.
And add a BeforeStep hook, that will watch for the first When step and automatically call writeForMoco and wait for all mocos we queued
Big BC break, that would lead to v2.0


.button-group list-style

I seem to be having problems with .button-group - I've included all foundation components, but it gives me grouped buttons with bullet points - see attached. Seems like there's missing css definition to remove list-style etc.

You can just use a plain
. You also then don't need
s inside, just nest the buttons directly inside the button group, like so:

  One
  Two
  Three

You could also just add a .no-bullet class to the
.