PR: Update minimal required version of pylint to >=2.5.0,<3.1

Description of Changes

[ ] 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)

Pylint 3 removed long deprecated find_pylintrc() which was only a wrapper to find_default_config_files().
https://github.com/pylint-dev/pylint/issues/9105
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:
bnavigator

Note: If we decide to include this on 5.5.0, this will need to be rebased into the 5.x branch

Agreed.
@bnavigator, to include this in our next release, please run the following commands locally:
git checkout 5.x
git checkout pylint3
git rebase --onto 5.x master pylint3
git push -f origin pylint3

Note: This requires to merge first PR https://github.com/python-lsp/python-lsp-server/pull/475 and then sync our subrepo here so that our tests actually run with Pylint 3 and catch any possible regression.

@bnavigator, I'm going to take care of finishing this one so we can be sure to include it in 5.5.

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

In the file external-deps/python-lsp-server/pylsp/plugins/definition.py:

Line 31:80: E501 line too long (80 > 79 characters)
Line 55:80: E501 line too long (80 > 79 characters)
Line 58:80: E501 line too long (85 > 79 characters)

In the file external-deps/python-lsp-server/pylsp/plugins/rope_autoimport.py:

Line 167:80: E501 line too long (170 > 79 characters)
Line 213:80: E501 line too long (84 > 79 characters)
Line 297:80: E501 line too long (82 > 79 characters)
Line 298:80: E501 line too long (84 > 79 characters)
Line 363:80: E501 line too long (80 > 79 characters)

In the file external-deps/python-lsp-server/pylsp/python_lsp.py:

Line 402:80: E501 line too long (83 > 79 characters)
Line 405:80: E501 line too long (88 > 79 characters)

In the file external-deps/python-lsp-server/pylsp/workspace.py:

Line 62:80: E501 line too long (85 > 79 characters)
Line 64:80: E501 line too long (92 > 79 characters)
Line 67:80: E501 line too long (106 > 79 characters)
Line 83:80: E501 line too long (80 > 79 characters)
Line 663:80: E501 line too long (87 > 79 characters)

In the file external-deps/python-lsp-server/test/plugins/test_autoimport.py:

Line 30:80: E501 line too long (80 > 79 characters)
Line 233:80: E501 line too long (85 > 79 characters)
Line 235:80: E501 line too long (88 > 79 characters)
Line 251:80: E501 line too long (89 > 79 characters)
Line 252:80: E501 line too long (82 > 79 characters)
Line 253:80: E501 line too long (115 > 79 characters)
Line 263:80: E501 line too long (85 > 79 characters)
Line 265:80: E501 line too long (97 > 79 characters)
Line 267:80: E501 line too long (96 > 79 characters)
Line 269:80: E501 line too long (94 > 79 characters)
Line 288:80: E501 line too long (90 > 79 characters)
Line 292:80: E501 line too long (86 > 79 characters)
Line 302:80: E501 line too long (86 > 79 characters)
Line 312:80: E501 line too long (86 > 79 characters)
Line 322:80: E501 line too long (86 > 79 characters)

In the file external-deps/python-lsp-server/test/plugins/test_definitions.py:

Line 24:1: W293 blank line contains whitespace
Line 25:1: W293 blank line contains whitespace

In the file external-deps/python-lsp-server/test/plugins/test_jedi_rename.py:

Line 86:80: E501 line too long (87 > 79 characters)

In the file external-deps/python-lsp-server/test/plugins/test_rope_rename.py:

Line 56:80: E501 line too long (87 > 79 characters)

In the file external-deps/python-lsp-server/test/test_configuration.py:

Line 35:80: E501 line too long (81 > 79 characters)
Line 39:80: E501 line too long (87 > 79 characters)
Line 51:80: E501 line too long (83 > 79 characters)

In the file external-deps/python-lsp-server/test/test_notebook_document.py:

Line 33:80: E501 line too long (83 > 79 characters)
Line 39:80: E501 line too long (87 > 79 characters)

In the file external-deps/python-lsp-server/test/test_utils.py:

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


modify some files for release 2.3.0 version

link to https://github.com/alibaba/tengine/issues/1196


[tests-only] [full-ci] Test get personal space id for user

WIP

enough of this - I have a solution coming. I will make a new PR for that.


Bridge - Upgrade to Angular 12 or 13

Upgrade to Angular 12 or 13 (based on the barista components support) to resolve old dependencies like Barista and make use of HttpContextToken as proposed in:
https://github.com/keptn/keptn/issues/6702
https://update.angular.io/?l=3&v=11.0-12.0
https://update.angular.io/?l=3&v=12.0-13.0

I would suggest to also look at the blocked/on-hold renovate PRs here regarding updates in the bridge for NodeJS, Prettier, TypeScript etc.
Many of them are blocked by an upgrade of Angular and could probably be bumped together with this ticket.


Replace usages of Blueprint decorators

We currently re-export and use two Blueprint decorators: ContextMenuTarget and HotKeysTarget. Both expect to be passed a class-based Component, which they will extend.
This is incompatible with our increasingly important functional component pattern. It also prevents us from shipping our code with ES6 classes in place, as the BP decorator code is itself transpiled to ES5 and expects to call the class constructor as a function (without new).
The react-hotkeys library appears to be a leading contender for general hotkey support, although I have not researched it at all yet to determine if it meets our needs.

Reopening - we took the great steps of getting this support bundled up in a Hoist component / accessible via Panel, but the use of the Blueprint class wrapper functions to implement the features still requires us to transpile our code down to ES5.
You can test this / see the error by setting the (undocumented/internal) transpileWithTargetBrowsers: true flag within Toolbox's webpack.config.js. This removes the internal workaround to push IE11 onto the target browser list, causing Babel to ship ES6 code.
The app will compile and you can login OK, but once you hit one of the new hosts it will throw with an attempt to call the component ctor without new.


Fix Injector

Currently injectors do nothing if the target isn't a mob.
There's also a appearance/visual bug, where AddSolution was passing the wrong entity leading to the wrong entity getting the appearance data updated.
:cl:

fix: Fixed syringes not working.

Relates to #5236 not sure if total fix.


gftools builder: [WinError 193] error

Trying to follow the docs, installed latest python and pip, installed gftools.
On attempt to run gftools builder --help getting:
  File "C:\Users\dfcre\AppData\Local\Programs\Python\Python310-32\Scripts\gftools", line 99, in <module>
    p = subprocess.Popen(args, stdout=sys.stdout,
  File "C:\Users\dfcre\AppData\Local\Programs\Python\Python310-32\lib\subprocess.py", line 966, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "C:\Users\dfcre\AppData\Local\Programs\Python\Python310-32\lib\subprocess.py", line 1435, in _execute_child
    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
OSError: [WinError 193] %1 is not a valid Win32 application

Please help.

Fixed by #638.


[image_picker] Updated documentation of getImage() to include information about Andr…

…oid's impossibility to specify camera
Description
Updated the documentation of getImage() in image_picker.dart and image_picker_platform.dart about Android's disability to preference front/rear camera, because this wasn't specified and caused confusion for people wondering why it didn't work.
Related Issues
Issue 55644
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.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[X] All existing and new tests are passing.
[X] I updated/added relevant documentation (doc comments with ///).
[X] The analyzer (flutter analyze) does not report any problems on my PR.
[X] I read and followed the Flutter Style Guide.
[X] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[X] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[X] I updated CHANGELOG.md to add a description of the change.
[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 (please indicate a breaking change in CHANGELOG.md and increment major revision).
[X] No, this is not a breaking change.

@googlebot I signed it!

@googlebot I signed it!
Van: googlebot<EMAIL_ADDRESS>Beantwoorden - Aan: flutter/plugins<EMAIL_ADDRESS>Datum: vrijdag 11 september 2020 om 15:26
Aan: flutter/plugins<EMAIL_ADDRESS>CC: Anniek Valk<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Onderwerp: Re: [flutter/plugins] [image_picker] Updated documentation of getImage() to include information about Andr… (#3021)
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2F&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056358897&sdata=KRvB9HrJaWY%2FdpZo3N7%2F1NpRNgXWRrjou4RMiz4e%2F2s%3D&reserved=0 to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA datahttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2Fclas&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056358897&sdata=7L%2Bon9s5XJquVnsybLSLtOY8e2AdjbmXXSEL7E6gf58%3D&reserved=0 and verify that your email is set on your git commitshttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.github.com%2Farticles%2Fsetting-your-email-in-git%2F&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056358897&sdata=Z9ypYPeW2n12WyW5AwaMsg9aSyDXODqoN7fkv1JTskQ%3D&reserved=0.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoothttp://go/cla#troubleshoot (Public versionhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensource.google%2Fdocs%2Fcla%2F%23troubleshoot&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056368854&sdata=T8IFy8DBffJ4%2BNQlEh14XnMKd3hs6hXnLB8MXnpPva8%3D&reserved=0).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA datahttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2Fclas&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056368854&sdata=q5ST5qjGvDQLBk81ok8ZbWIPeMB4iuGqbovHsWtXll8%3D&reserved=0 and verify that your email is set on your git commitshttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.github.com%2Farticles%2Fsetting-your-email-in-git%2F&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056368854&sdata=gpTnOP7eidGuglK7yUDwi%2B49Dgzc9hu1Wqil9GGFTto%3D&reserved=0.
The email used to register you as an authorized contributor must also be attached to your GitHub accounthttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsettings%2Femails&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056378810&sdata=ZNKGbkFJCdFKeyZEgN41%2BToKx20bK3CXSaVYn9Q%2FG3k%3D&reserved=0.

ℹ Googlers: Go herehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgoto.google.com%2Fprinfo%2Fhttps%253A%252F%252Fgithub.com%252Fflutter%252Fplugins%252Fpull%252F3021&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056378810&sdata=LE0jQ1KF5XNR2FeV4ECAJrdL7BC6HBR4qpzKmdalM9Y%3D&reserved=0 for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fflutter%2Fplugins%2Fpull%2F3021%23issuecomment-691094228&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056378810&sdata=kiDfv0K2iddgP%2BZfAVh1fsFd%2Bs%2BPai%2FyFw%2BQGxXk4DE%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALLVMCQYHOXTJVUI7BZ74F3SFIQRJANCNFSM4RHPPWUQ&data=02|01|449747%40student.saxion.nl|1f6e8400c52a402d015208d85656541f|a77b0754fdc14a62972c8425ffbfcbd2|0|0|637354276056388767&sdata=OeZb5yjcIswexiz%2B122qbMqu9olKWwIGIGPd9idtrTw%3D&reserved=0.


Not working in dataTables v2

Just migrated to datatables v2.0.1 and colResize not working.
It fails at the version check and fails after fixing and passing version check.
There are no error messages in the console after the version check passes.

indeed, would be good if we can get a fix

The version check is super easy to fix. But there are multiple other problems. The CSS has changed so orderable colums cannot be resized as well as the aoColumns API so columns must be selected differently.
If you want the upgrade, I suggest getting to work, I'm not sure I'll have the time to fix everything.


Remove oc alias and update OpenCommit CLI to use 'oco'

oc is a pretty well-known alias for OpenShift CLI

Closes https://github.com/di-sukharev/opencommit/issues/144

Didn't realize that I should have forked from the dev branch. Rebased on dev now

@di-sukharev anything pending?

@Moulick hi, sorry for being late :) was busy,
I see some conflicts are here to be fixed

The branch history got confusing, making a new PR

superseded by https://github.com/di-sukharev/opencommit/pull/178


SSRS Report Viewer: 150.1400.0 Release Notes missing

https://docs.microsoft.com/en-us/sql/reporting-services/application-integration/release-notes-ssrs-application-integration?view=sql-server-ver15
150.1400.0 was published to NuGet 2019-11-07 but there's no indication of what has changed.

@bdenhollander -- thank you for bringing this to our attention.
@RhysSchmidtke -- please look into this issue 3773.
cc @MightyPen as a writer

Following up

The doc update should be live soon.


Revise DataVolumeTemplate API field

The vm.Spec.DataVolumeTemplate api list actually contains DataVolumes rather than a struct that restricts the fields to only the metadata and spec. This gives the user the impression they can set things like the DataVolume group/kind and status when they in fact cannot.
This change aligns our DataVolumeTemplate usage similar to how the PodTemplate works, by creating a new struct that only contains values a user can set.
I discovered this issue while reviewing this pr #3257 which adds the cdr validation schema back to our crd registrations. We're advertising DataVolume fields that users can't actually set.
Release note:

NONE

/cc @xpivarc
This will likely help us handle that strange datavolume exception logic you had to add to your explain pr.

/override pull-kubevirt-e2e-k8s-1.17
Error related to #4264, overriding.
/lgtm
/approve


add support for multiple JWKS

Summary
These changes add support for multiple JWKS. Also, this code changes the behavior of the static jwk endpoint to be the location of the endpoint, not the value of the JWK itself.
Related

https://github.com/pomerium/pomerium/issues/1721

Signed-off-by: Bobby DeSimone<EMAIL_ADDRESS>

\cc @lukegb


LEFT_SIDEBAR: Rewrite activation of narrows

Rewrite how we handle activation of narrows in left_side_navigation_area.js by adjusting the classes for all the buttons when switching narrows. Also changed remove function to removeActiveClasses
Fixes: #26686 issue on Left sidebar navigation area library rewrite.

@ademolaomosanya welcome! I'm closing this as this doesn't look ready for review:

It doesn't follow our commit guidelines.
It doesn't follow our snake_case variable naming conventions.
It doesn't implement the goal of the issue -- you still have several calls in each function.

Please take some time to review our contributing guide and how to write reviewable pull requests.

@timabbott Thank you for the correction will work on that right away


How this can be used with vue-i18n

Will be great to have an example for vue-i18n or even if someone confirms that this library works with it.
Here is the link to vue-i18n.
Thanks

@husayt As described in the README, this is an agnostic locale switcher for Storybook. It's designed to be used as the basis for concrete implementations of various i18n libraries.
I don't use Vue but making a Vue version should be very easy. I assume there's an addon kit for Vue. Since Storybook itself is React and this library simply adds a locale switcher to the header in Storybook, this library should still work in the Vue addon.
Other than the required addon boilerplate, there's just one file that contains the specific implementation of the i18n library.
In this file, you would implement vue-i18n however it works, and listen for the locale global to change using useGlobals() or whatever the Vue addon equivalent is. Again, I don't use Vue so I don't know what that is, but reading globals is a Storybook API and it's explained in their addon documentation.
Here are two React examples of concrete implementations that hopefully should show how simple it is:

storybook-react-i18next
storybook-react-intl

If you need help with writing Vue addons, the Storybook Discord is a great resource!

Hi @stevensacks ,
I finally managed to get it working using decorators. Initially I was trying to use addons.getChannel, but that didn't work, nor I could find a single working example of that.
Now it all works with decorators. Thanks


Restructuring of Maxwells in Homogeneous Media

I have a proposition for improving the current structure of content within Maxwell's equation in homogeneous media. I would like to meet as soon as possible to discuss. It is important because the content in each page must be written in the right context.
Maxwell Homogeneous Media New Structure.docx

@dccowan : I have put this content in a google doc so that we can comment on it: https://docs.google.com/document/d/1WpnpOMhzODEPj-wbs9VnBOh_kH0Px9-ZTaLhUObxyM0/edit?usp=sharing

The google doc is available for comment here: https://docs.google.com/document/d/1qx5cpgXttz0JdHSBTKF3VkdxcgU_MKA9xof6M1G4ZBY/edit?ts=57eef57d


Install generator not functioning on blank install with admin and starter theme.

Subscription generator isn't working out of the box with stock Solidus starter starter frontend.
Solidus Version:
4.3.5
Installed with starter frontend on Ruby 3.3.5 with Rails 7.1.4
To Reproduce

Spin up a new rails app
add solids and solids subscription gem
Run solidus install
run solidus subscription install
add a subscription
Get an error on cart_line_item path: Validation failed: Subscribable must exist, Subscribable can't be blank

Current behavior
Validation failed: Subscribable must exist, Subscribable can't be blank
extracted source:
def handle_subscription_line_items
line_item = @current_order.line_items.find_by(variant_id: params[:variant_id])
create_subscription_line_item(line_item)
end
end
Expected behavior
Installation of fields should appear normal and have options
Move onto Checkout when added to checkout
backend admin also has the 'subscription' option come and go based on other menu item I'm in.
Screenshots

Desktop (please complete the following information):

OS: MacOS Sonomo
Browser: FF
Version: 131

@noltedesign Hey, did you manage to solve this issue?


Declare Geckolib dependency in fabric.mod.json

I may be wrong but I don't think this mod declares Geckolib as a dependency. I also I think the version of Fabric Loom is out of date

Seems that I've missed the part, thanks for bringing it up!

Is Loom up to date?


Test code in pyCaffe/C++

Do anyone have the test code without matconvnet. I tried using python interface and I am not able to get good results. I am able to get good results using matconvnet and the given test code. But not for python interface. Seems like I have done something wrong in the data preprocessing. It would be great if anyone has done it already.

Hi, you can try PIL.Image.LANCZOS instead of BICUBIC to get better resize performance.

And do I have to add padding after output of every convolutional layers or I can take output directly from the last layer? Could you please post the test script if you have it. Thank you so much.

Hi, you can take output directly from the last layer. I am sorry that I don't have the test script in python.

Thank you for your reply. Here is my code :
import numpy as np
import matplotlib.pyplot as plt
import cv2
import caffe
caffe.set_mode_gpu()
net = caffe.Net('model/deploy.prototxt', 'model/vdsr.caffemodel',caffe.TEST)
input = cv2.imread('testImages/temp.jpg')
input = cv2.cvtColor(input, cv2.COLOR_BGR2YCR_CB)
input = input[:, :, 0]
input = input.reshape(1, input.shape[0], input.shape[1])
out = net.forward_all(data = input.astype(float)/255)
mat = out['sum'][0]
output = mat.reshape(mat.shape[1], mat.shape[2])
If I use pyplot to show this image, it does not look nice. But if I convert this caffemodel to mat and test using your code, Its working fine. Could you please guide me to right direction.

In matlab, the Anti-Aliasing is default. And if you use PIL,there is no Anti-Aliasing. So the low resolution picture generated by imresize() in matlab is better. I also troubled by this before.

@sdlpkxd What method of interpolation did you use in python to fix this problem?  I tried INTER_CUBIC and INTER_LANCZOS4 in opencv. The result was terrible.

I use matlab imresize() to do data augmentation instead of opencv. You can use cv2.resize() in opencv2 instead.


🐛 [V3][iOS][CodeScanner] CodeScanner very slow on Android

What's happening?
On a Moto G Stylus 2022 Android device, when codeScanner is used, the displayed view drops to about 5 fps and any codeScanner functionality is slow & delayed.
When codeScanner is disabled (or on iOS at all times), the framerate is excellent.
This is occurring on<EMAIL_ADDRESS>Reproduceable Code
Tested in the Example App, with photo/video/audio/frameProcessor all disabled and this codeScanner function:

  const onCodeScanned = useCallback((codes: Code[]) => {
    console.log(codes.length)
  }, [])

### Relevant log output

```shell
N/A

Camera Device
{
  "sensorOrientation": "landscape-right",
  "hardwareLevel": "full",
  "maxZoom": 8,
  "minZoom": 1,
  "supportsLowLightBoost": false,
  "neutralZoom": 1,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsFocus": true,
  "supportsRawCapture": true,
  "isMultiCam": false,
  "name": "BACK (0)",
  "hasFlash": true,
  "hasTorch": true,
  "position": "back",
  "id": "0"
}

Device
Moto G Stylus 2022
VisionCamera Version
3.3.1
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[ ] I am using Expo
[x] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Same issue on Samsung Galaxy A51

can confirm, same on samsung galaxy s23 ultra

Exact same issue here on a Samsung Galaxy S21 FE.

How about you guys change the title to "[V3][Android]" ?
Putting iOS in the title of an Android-only problem gives me headaches.

Same issue here on a samsung A23

Same Issue OnePlus 9. The first few seconds work fine, then start to drop the fps

FYI there's this frame processor plugin that works with v3:
https://github.com/mgcrea/vision-camera-barcode-scanner
I haven't fully tested myself but it looks pretty promising. Anyone hit by this issue could try using the frame processor plugin above on Android as a workaround.

Yes, that one works nicely. I had to upgrade react native to 0.72.5 though.

same problem, pr fix of https://github.com/mrousavy/react-native-vision-camera/commit/915ef331d3b3f3630f4b8d5a8cdd7f5fcf30c335 didn't fixed it on andoid

Yes, that one works nicely. I had to upgrade react native to 0.72.5 though.

Well I just tried it on Android and it crashed the whole app after ~1 sec of code scanning.
Guess I'll be staying with v2 a little longer.

same problem, pr fix of https://github.com/mrousavy/react-native-vision-camera/commit/915ef331d3b3f3630f4b8d5a8cdd7f5fcf30c335 didn't fixed it on android.
tested on 2 diffrent androids

@celik75 how did you test that?

same problem, pr fix of https://github.com/mrousavy/react-native-vision-camera/commit/915ef331d3b3f3630f4b8d5a8cdd7f5fcf30c335 didn't fixed it on android.
tested on 2 diffrent androids

@celik75 how did you test that?

Also just tested using the latest commit on main and the issue remains
I tested by using gitpkg and setting my dependency to https://gitpkg.now.sh/mrousavy/react-native-vision-camera/package?e8df7148fa50214f47ff1a41dfa40e7255bc3f8d
The behavior I noticed using this commit is that the camera is fluid at first but becomes progressively laggy (during the first ~2 seconds) & it stabilizes with the same level of slowness as v3.3.1. On v3.3.1 however it was slow from the start

I don't get this. I think the Camera2 APIs are just terrible at this.
@sacha-c can you maybe try this change? Idk if that'll work better

@mrousavy Gave it a shot, and with this the lagging is fixed! It works smoothly and remains that way.
However after scanning a QR code the camera goes black, this did not used to occur on v3.3.1.
Looking briefly through the logs I see this after scanning a QR code which may be related
2023-10-16 13:55:17.455  2699-3982  Camera3-OutputStream    cameraserver                         E  returnBufferCheckedLocked: Stream 0: Error queueing buffer to native window: No such device (-19)
2023-10-16 13:55:17.455  2699-3982  Camera3-Device          cameraserver                         E  Can't return buffer to its stream: No such device (-19)

It looks like it may be related to the latest codeScanning changes (not just the diff above, but the diff between v3.3.1..master), but if you would like a separate issue for this let me know if you would like me to create it.

Yea please create a separate issue. Thanks

Fixes this in #2009!

Render performance is much better now, thank you. Still seeing the reads buffer/queue and execute for a while after the reads, but vastly improved!

Running smoothly on Android after the new version update (3.4.0)!

Amazing, great to hear my fix works for you guys.

Still seeing onCodeScanned buffer/queue and execute for a few seconds after the reads, but vastly improved!

Create a separate issue if that's a problem, I don't quite get what this means tbh


feat: Add containerd config

What type of PR is this?

/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

6 of 16 (37.5%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 70.857%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/agent/datamodel/types.go
0
10
0.0%

Totals

Change from base Build<PHONE_NUMBER>7:
-0.1%

Covered Lines:
2570

Relevant Lines:
3627

💛  - Coveralls


fix: change serialization of struct field order to match the user defined order

Related issue(s)

Resolves #1110
Description
Summary of changes
When serializing contracts, struct fields were previously serialized alphabetically. This change will serialize them in the order defined by users when declaring the struct instead.
Dependency additions / changes

Test additions / changes

Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt with default settings.
[x] I have linked this PR to the issue(s) that it resolves.
[x] I have reviewed the changes on GitHub, line by line.
[x] I have ensured all changes are covered in the description.

Documentation needs

[ ] This PR requires documentation updates when merged.

Additional context

Using a fixed serialisation pattern, like the alphabetical order for instance is more reliable and avoids user errors based on field struct ordering. I wonder if we could not find a way to keep a fix ordering?

Reassigning this to @kevaundray for the remaining errors.
Locally the poseidenperm test is failing, and a different test is failing on the CI.

For more context:
I added another example with a simple struct which also fails:
use dep::std;

 struct myStruct {
     foo: u32,
     bar: Field,
 }

 fn main(y : pub myStruct) {
     constrain y.foo == 5;
     constrain y.bar == 7;
 }

But if we re-order the struct to be in alphabetical order, it will pass like so:
 struct myStruct {
    bar: Field,
    foo: u32,
}

There must be a case I missed regarding the ordering. Perhaps during verification

You haven't adjusted the ABI encoding code to use this new ordering logic. This means when constructing the initial witness you're reversing the two fields.
https://github.com/noir-lang/noir/blob/6fe27e782e9be3d6c25a90fcfd472c6b3d280be0/crates/noirc_abi/src/lib.rs#L289-L293

Should be good to go now.

Just noticed the panic in CI. Looking into it now

This may take some larger refactoring. It's pretty gross.

Could you open up an issue re the hack and the larger refactoring needed


Web component: Multi-select - Prod QA testing of the fluid variant

User Story

As a [user role below]:
developer using the carbon web components Library Multi-select fluid variant

I need to:
have a version of the component that has been tested for accessibility compliance as well as on multiple browsers and platforms

so that I can:
be confident that my ibm.com web site users will have a good experience

Additional information

Browser Stack link
Browser Standard
Browser versions to be tested:  Tier 1 browsers will be tested with defects created as Sev 1 or Sev 2.  Tier 2 browser defects will be created as Sev 3 defects.
Platforms to be tested, by priority:  1)  Desktop  2)  Mobile  3)  Tablet
Mobile & Tablet iOS versions: 13.1 and 13.3
Mobile & Tablet Android versions: 9.0 Pie and 8.1 Oreo
Browsers to be tested:  Desktop: Chrome, Firefox, Safari, Edge, Mobile: Chrome, Safari, Samsung Internet, UC Browser, Tablet: Safari, Chrome, Android
Accessibility Checklist
Creating a QA bug
See the Epic for the Design and Functional specs information
Dev issue (#506)
Carbon Web Components Production Instance
Once development is finished the updated code is available in the ** Carbon Web Components test environment**

Acceptance criteria

[ ] Accessibility testing is complete.  Component is compliant.
[ ] All browser versions are tested
[ ] All operating systems are tested
[ ] All devices are tested
[ ] Defects are recorded and retested when fixed

Closing this issue as the Prod QA testing will be automated.


add red background on gruvbox: ediff-current

before:

after:

Looks good to me. Thanks for the PR!


[18.03] Add /proc/acpi to masked paths

The deafult OCI linux spec in oci/defaults{_linux}.go in Docker/Moby
from 1.11 to current upstream master does not block /proc/acpi pathnames
allowing attackers to modify host's hardware like enabling/disabling
bluetooth or turning up/down keyboard brightness. SELinux prevents all
of this if enabled.
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>(cherry picked from commit 569b9702a59804617e1cd3611fbbe953e4247b3e)
Signed-off-by: Sebastiaan van Stijn<EMAIL_ADDRESS>Fix for CVE-2018-10892
cherry-pick of https://github.com/moby/moby/pull/37404 for 18.03 (no conflicts)

Failure on s390x; https://jenkins.dockerproject.org/job/docker-ce-pr-s390x/603/execution/node/476/log/ is a known flaky https://github.com/moby/moby/issues/32673
21:17:21 FAIL: docker_api_swarm_test.go:297: DockerSwarmSuite.TestAPISwarmLeaderElection
21:17:21
21:17:21 [d82fd828ea31f] waiting for daemon to start
21:17:21 [d82fd828ea31f] daemon started
21:17:21
21:17:21 [dd4c7947a7052] waiting for daemon to start
21:17:21 [dd4c7947a7052] daemon started
21:17:21
21:17:21 [df783e432c929] waiting for daemon to start
21:17:21 [df783e432c929] daemon started
21:17:21
21:17:21 [d82fd828ea31f] exiting daemon
21:17:21 assertion failed: error is not nil: Error response from daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded
21:17:21 [dd4c7947a7052] exiting daemon
21:17:21 [df783e432c929] exiting daemon

No idea what's the cause for the PowerPC failures; it's not in the tests themselves (don't know what these steps do)
https://jenkins.dockerproject.org/job/docker-ce-pr-ppc64le/596/execution/node/330/log/
21:18:29 [docker-ce-pr-ppc64le] Running shell script
21:18:29 + pwd
21:18:29 + docker run --rm -v /home/docker/workspace/docker-ce-pr-ppc64le:/v -w /v -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY seemethere/awscli-ppc64le@sha256:1f46b7687cc70bbf4f9bcf67c5e779b65c67088f1a946c9759be470a41da06d7 s3 cp --only-show-errors s3://****/jenkins-docker-ce-pr-ppc64le-596/bundles-binary-daemon.tar.gz .
21:18:29 Unable to find image 'seemethere/awscli-ppc64le@sha256:1f46b7687cc70bbf4f9bcf67c5e779b65c67088f1a946c9759be470a41da06d7' locally
21:18:30 sha256:1f46b7687cc70bbf4f9bcf67c5e779b65c67088f1a946c9759be470a41da06d7: Pulling from seemethere/awscli-ppc64le
21:18:30 1e52418956f7: Pulling fs layer
21:18:30 ed6f332c99ba: Pulling fs layer
21:18:30 59311d198603: Pulling fs layer
21:18:30 ed6f332c99ba: Download complete
21:18:30 1e52418956f7: Verifying Checksum
21:18:30 1e52418956f7: Download complete
21:18:31 1e52418956f7: Pull complete
21:18:31 ed6f332c99ba: Pull complete
21:18:32 59311d198603: Verifying Checksum
21:18:32 59311d198603: Download complete
21:18:38 59311d198603: Pull complete
21:18:38 Digest: sha256:1f46b7687cc70bbf4f9bcf67c5e779b65c67088f1a946c9759be470a41da06d7
21:18:38 Status: Downloaded newer image for seemethere/awscli-ppc64le@sha256:1f46b7687cc70bbf4f9bcf67c5e779b65c67088f1a946c9759be470a41da06d7
21:18:44 fatal error: ('Connection aborted.', error(13, 'Permission denied'))

https://jenkins.dockerproject.org/job/docker-ce-pr-ppc64le/596/execution/node/559/log/
21:19:48 [docker-ce-pr-ppc64le] Running shell script
21:19:48 + pwd
21:19:48 + docker run --rm -v /home/docker/workspace/docker-ce-pr-ppc64le:/v -w /v -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY seemethere/awscli-ppc64le@sha256:1f46b7687cc70bbf4f9bcf67c5e779b65c67088f1a946c9759be470a41da06d7 s3 cp --only-show-errors s3://****/jenkins-docker-ce-pr-ppc64le-596/bundles-binary-daemon.tar.gz .
21:19:59 fatal error: ('Connection aborted.', error(13, 'Permission denied'))

Closing this PR because docker-ce 18.03 is EOL.


Add service_namespace attr to span metrics

The resource attribute service_namespace is missing for span metrics generated
from OTEL such as http_server_request_duration_seconds_count. This PR adds
that attribute to these metrics.
Fixes #975

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 50.38%. Comparing base (b51cc68) to head (df178b8).

Files
Patch %
Lines

pkg/internal/request/span_getters.go
0.00%
2 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (b51cc68) and HEAD (df178b8). Click for more details.
HEAD has 1 upload less than BASE

Flag
BASE (b51cc68)
HEAD (df178b8)

oats-test
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #980       +/-   ##
===========================================
- Coverage   66.05%   50.38%   -15.68%
===========================================
  Files         134      134
  Lines       10648    10650        +2
===========================================
- Hits         7034     5366     -1668
- Misses       3124     4923     +1799
+ Partials      490      361      -129

Flag
Coverage Δ

oats-test
?

unittests
50.38% <0.00%> (-0.01%)
:arrow_down:

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

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


add support to pageable dynamic search on company number and user

filter on used id and company number
JIRA Ticket Number
Type of change

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[ ] I have added unit tests for new code that I have added
[ ] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: No security warnings found


Revert wrangler field lineage

Reverts the changes in these two PRs:
https://github.com/hydrator/wrangler/pull/145
https://github.com/hydrator/wrangler/pull/150
They will be brought back, after some code improvements and further testing.

LGTM


fixes #18 - implement reconnecting and pinging websocket

Creates a new hook that wraps useWebsocket that does two things:

Reconnects automatically with exponential backoff after disconnect
Pings the server every 9 minutes to prevent the server automatically closing

Both to deal with AWS hard limits: https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html

Really great work! No comments on this just a few questions:
* Is the username the only argument that would ever be wanted? Could there ever be a need for others in the future?

* Is the last message the only return value that will be needed?

Thanks for looking at it, appreciate it!

For now, the username is the only filter on the websocket api. In the future, there might be more, but I prefer to keep it simple and adjust later in one go if I need more filters.
I don't think there will be another value needed. The websocket will probably always be passive, so sendMessage will not be needed. I also don't see a reason for the implementing code to close the client, or access the ready state, since the latter can be infered from the lastMessage.

So in short: extensions might be needed in the future, but I'd rather deal with it then and keep it simple for now.
Going to merge :D


Add Scoreboard components

This PR implements scoreboard and team components.

Scoreboard components are attached to Scoreboard instances (accessible from any World) - they are essentially alternatives to level components. They may replace level components at some point, as they are less reliant on a fragile class hierarchy.
Team components are attached to Team instances - they can be used to implement shared data between entities in the same team.

Both component providers support synchronized components. They get attached using the experimental static component system
Closes #34

@haykam821 opinions ?


[bug] Results paging bug for collections with type None items

To reproduce:

go to https://calisphere-stage.cdlib.org/collections/469/
hit the forward arrow button to go to page 2

This results in no items displayed and "1 item found in this collection of 66 items" heading.
url: https://calisphere-stage.cdlib.org/collections/469/?q=&sort=a&type_ss=&start=24
This is because we are currently including records with type_ss=None in our faceting query. The "next page" URL includes the type_ss facet, which defaults to no value, and there is only one record with type None in this collection.

Adding in an example of a collection with date None -- this does not seem to produce the same error.
https://calisphere-stage.cdlib.org/collections/26171/


fix: allow pinpoint category removal after manual deletion

Description of changes
This PR fixes an issue where, if a Pinpoint project is deleted manually via AWS Console, the notifications category could not be removed from the amplify project. It accomplishes this by treating a NotFoundException on deletion as a successful deletion.

Issue #, if available
https://github.com/aws-amplify/amplify-cli/issues/9036

Description of how you validated changes
amplify add notifications && amplify push
delete pinpoint manually
amplify remove notifications && amplify push
# note that everything seems to work on AWS console/amplify status
amplify pull/push no longer recreates the notifications category.

Checklist

[x] PR description included
[x] yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #9691 (9ce67a2) into master (4a87373) will decrease coverage by 0.04%.
The diff coverage is 31.63%.

@@            Coverage Diff             @@
##           master    #9691      +/-   ##
==========================================
- Coverage   52.93%   52.89%   -0.05%
==========================================
  Files         829      830       +1
  Lines       45865    45957      +92
  Branches     9789     9815      +26
==========================================
+ Hits        24279    24308      +29
- Misses      19581    19634      +53
- Partials     2005     2015      +10

Impacted Files
Coverage Δ

...mplify-category-notifications/lib/channel-Email.js
0.00% <0.00%> (ø)

...lify-category-notifications/lib/pinpoint-helper.js
0.00% <0.00%> (ø)

...amplify-cli-core/src/feature-flags/featureFlags.ts
80.83% <ø> (ø)

...c/extensions/amplify-helpers/auth-notifications.ts
34.14% <34.14%> (ø)

...l-auth-transformer/src/graphql-auth-transformer.ts
89.62% <50.00%> (ø)

packages/graphql-transformer-core/src/index.ts
97.29% <100.00%> (+0.07%)
: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 5ff6fe8...9ce67a2. Read the comment docs.


Update ingress.yaml

I am closing the PR due to inactivity. If you have additional information, please add it to the PR and reopen it.


TypeError: undefined is not a function on express.post

Ok, so I have alexa-app-server server.js like so:
var AlexaAppServer = require('alexa-app-server');

var instance = AlexaAppServer.start({
  server_root: __dirname,     // Path to root
  public_html: "public_html", // Static content
  app_dir: "apps",            // Location of alexa-app modules
  app_root: "/alexa/",        // Service root
  port: 8080,                  // Port to use

  httpsPort: 8081,
  httpsEnabled: true,
  privateKey: 'private-key.pem',
  certificate: 'cert.cer',

  debug: true,
  verify: false
});

And then in ./apps/hello_world/index.js, I have:
var alexa = require('alexa-app');

// Allow this module to be reloaded by hotswap when changed
module.change_code = 1;

// Define an alexa-app
var app = new alexa.app('hello_world');
app.launch(function(req, res) {
  res.say("Hello World!!");
});

app.intent('NameIntent', {
  "slots": { "NAME": "LITERAL", "AGE": "NUMBER" },
  "utterances": ["{My name is|my name's} {matt|bob|bill|jake|nancy|mary|jane|NAME} and I am {1-100|AGE}{ years old|}"]
}, function(req, res) {
  res.say('Your name is ' + req.slot('NAME') + ' and you are ' + req.slot('AGE') + ' years old');
});

app.intent('AgeIntent', {
  "slots": { "AGE": "NUMBER" },
  "utterances": ["My age is {1-100|AGE}"]
}, function(req, res) {
  res.say('Your age is ' + req.slot('AGE'));
});

module.exports = app;

But when I start the server I get this stack trace complaining about express.post:
serving static content from: /home/ec2-user/Tinkering/xAlexa/public_html
loading server-side modules from: /home/ec2-user/Tinkering/xAlexa/server
   loaded /home/ec2-user/Tinkering/xAlexa/server/login.js
loading apps from: /home/ec2-user/Tinkering/xAlexa/apps
/home/ec2-user/Tinkering/xAlexa/apps/hello_world/node_modules/alexa-app/index.js:491
    express.post(endpoint, function(req, res) {
            ^
TypeError: undefined is not a function
    at Object.express (/home/ec2-user/Tinkering/xAlexa/apps/hello_world/node_modules/alexa-app/index.js:491:13)
    at /home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:122:11
    at Array.forEach (native)
    at Object.self.load_apps (/home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:82:30)
    at Object.self.start (/home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:188:12)
    at Function.appServer.start (/home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:295:21)
    at Object.<anonymous> (/home/ec2-user/Tinkering/xAlexa/server.js:3:31)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3

I tried installing express then updating ./apps/hello_world/index.js to be:
var express = require( 'express' );
var alexa = require('alexa-app');
var express_app = express();

// Allow this module to be reloaded by hotswap when changed
module.change_code = 1;

// Define an alexa-app
var app = new alexa.app('hello_world');
app.launch(function(req, res) {
  res.say("Hello World!!");
});

app.intent('NameIntent', {
  "slots": { "NAME": "LITERAL", "AGE": "NUMBER" },
  "utterances": ["{My name is|my name's} {matt|bob|bill|jake|nancy|mary|jane|NAME} and I am {1-100|AGE}{ years old|}"]
}, function(req, res) {
  res.say('Your name is ' + req.slot('NAME') + ' and you are ' + req.slot('AGE') + ' years old');
});

app.intent('AgeIntent', {
  "slots": { "AGE": "NUMBER" },
  "utterances": ["My age is {1-100|AGE}"]
}, function(req, res) {
  res.say('Your age is ' + req.slot('AGE'));
});

app.express({ expressApp: express_app });
module.exports = app;

And this starts the server, but the app does not load:
serving static content from: /home/ec2-user/Tinkering/xAlexa/public_html
loading server-side modules from: /home/ec2-user/Tinkering/xAlexa/server
   loaded /home/ec2-user/Tinkering/xAlexa/server/login.js
loading apps from: /home/ec2-user/Tinkering/xAlexa/apps
   error loading app [/home/ec2-user/Tinkering/xAlexa/apps/hello_world/index.js]: TypeError: undefined is not a function
enabling https
listening on https port 8081
listening on http port 8080

Any ideas?

If you're using alexa-app server, remove all references to express in the function/app itself. I think the call to app.express() causes app.express to be redefined or something like that.
Reopen if that doesn't solve it.

hmm, no dice. This is my entire server.js:
var AlexaAppServer = require('alexa-app-server');

var instance = AlexaAppServer.start({
  server_root: __dirname,     // Path to root
  public_html: "public_html", // Static content
  app_dir: "apps",            // Location of alexa-app modules
  app_root: "/alexa/",        // Service root
  port: 8080,                  // Port to use

  httpsPort: 8081,
  httpsEnabled: true,
  privateKey: 'private-key.pem',
  certificate: 'cert.cer',

  debug: true,
  verify: false
});

Your ./apps/hello_world/index.js is what needs to change. Post the whole code if you can't make it work.

Ah, ok, sorry I misunderstood. This is ./apps/hello_world/index.js:
var alexa = require('alexa-app');

// Allow this module to be reloaded by hotswap when changed
module.change_code = 1;

// Define an alexa-app
var app = new alexa.app('hello_world');
app.launch(function(req, res) {
  res.say("Hello World!!");
});

app.intent('NameIntent', {
  "slots": { "NAME": "LITERAL", "AGE": "NUMBER" },
  "utterances": ["{My name is|my name's} {matt|bob|bill|jake|nancy|mary|jane|NAME} and I am {1-100|AGE}{ years old|}"]
}, function(req, res) {
  res.say('Your name is ' + req.slot('NAME') + ' and you are ' + req.slot('AGE') + ' years old');
});

app.intent('AgeIntent', {
  "slots": { "AGE": "NUMBER" },
  "utterances": ["My age is {1-100|AGE}"]
}, function(req, res) {
  res.say('Your age is ' + req.slot('AGE'));
});

module.exports = app;

This results in:
serving static content from: /home/ec2-user/Tinkering/xAlexa/public_html
loading server-side modules from: /home/ec2-user/Tinkering/xAlexa/server
   loaded /home/ec2-user/Tinkering/xAlexa/server/login.js
loading apps from: /home/ec2-user/Tinkering/xAlexa/apps
/home/ec2-user/Tinkering/xAlexa/apps/hello_world/node_modules/alexa-app/index.js:491
    express.post(endpoint, function(req, res) {
            ^
TypeError: undefined is not a function
    at Object.express (/home/ec2-user/Tinkering/xAlexa/apps/hello_world/node_modules/alexa-app/index.js:491:13)
    at /home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:122:11
    at Array.forEach (native)
    at Object.self.load_apps (/home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:82:30)
    at Object.self.start (/home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:188:12)
    at Function.appServer.start (/home/ec2-user/Tinkering/xAlexa/node_modules/alexa-app-server/index.js:295:21)
    at Object.<anonymous> (/home/ec2-user/Tinkering/xAlexa/server.js:3:31)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3

Sorry, I must be missing something else.

Can you put this project on Github pls, I can take a look.

I ended up going with lambda. This is more of a research project, so I can stick with that for now. If I need to I'll pick this back up and put it on github per your request. Thanks for your help!

I had the same problem, and it was because I was symlinking the package.json file in the app folder to the parent alexa-app-server folder (still not sure how to use only one package.json file). At some point, I had ran npm install from the app directory, so the app was trying to use old versions of alexa-app/-server from the node_modules of that directory. To fix, just wipe node_modules from the app directory.


Add AMTRELAY RR

See https://datatracker.ietf.org/doc/html/rfc8777 for the definition.
Also add RFC 8777 to README.md

The IPv4/IPv6 is done in another RR as well, can't remember which one though


Custom field and tmp dir fix

Pull request contains:

Add new type for files (custom-plaintext) to attach plaintext files to archive and display them without any parsing
Fix for tmp_dir function, which was broken if there was two files with the same date.

Hi @emate, thanks for the pull request. Before we can merge it, we need you to sign our Contributor License Agreement. You can do so electronically here: http://opensource.box.com/cla
Once you have signed, just add a comment to this pull request saying, "CLA signed". Thanks!

CLA signed.

Verified that @emate has just signed the CLA. Thanks, and we look forward to your contribution.

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

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


make graphql_ws test less timing-sensitive.

A fix to intermittent test failure in graphql_ws

Description
Due to timing issues on test runners, the exact number of Keepalive messages sent can vary.
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

🎉


Table color

Description
The table color can be removed for reading ease. Or choose single font or background color for high contrast
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
Figures
Internal issue ID
6f247816-4e0e-44bd-b2d4-af3f3cf7838a
Paper URL
https://arxiv.org/html/2410.02073v1
Browser
Chrome/<IP_ADDRESS>
Device Type
Desktop

This is a good example of non-standard colors that can be remapped in dark mode. Thank you for the report.


fix(deploy): use absolute path to load component source

fixes #590

@FrankYang0529  https://spin.fermyon.dev/contributing/

We might also want to absolutize the app dir reference as a follow up.

Do you mean also put app_folder in DeployCommand? If yes, I can help to do the follow up.

Would you mind also signing your commit so we can merge?

I sign it. Thank you.


[BUG] pointer substraction cause compilation error when overflowcheck is enabled

Describe the bug
Pointer substraction cause compilation error when overflowcheck is enabled
To Reproduce
Code to reproduce the behaviour:
# cython: overflowcheck=True

import numpy as np

cpdef run():
    cdef int[::1] v = np.zeros(5)
    cdef const int* p1 = &v[0]
    cdef const int* p2 = &v[1]
    cdef ssize_t t = p2 - p1

This produce compilation error:
build_source/src/run_test.cpp:2364:65: error: invalid conversion from ‘const int*’ to ‘ptrdiff_t’ {aka ‘long int’} [-fpermissive]
 2364 |   __pyx_t_7 = __Pyx_sub_ptrdiff_t_checking_overflow(__pyx_v_p2, __pyx_v_p1, &__pyx_t_6);
      |                                                                 ^~~~~~~~~~
      |                                                                 |
      |                                                                 const int*

Expected behavior
This should success
Environment (please complete the following information):

OS: Ubuntu 20.04.4 LTS
Python version 3.10.4
Cython version 0.29.30

This is simple workaround.
import numpy as np

cdef extern from *:
    """
    template<typename T>
    static inline long my_pointer_diff(T p1, T p2) {
        return p1 - p2;
    }
    """
    long my_pointer_diff[T](T, T)

cpdef run():
    cdef int[::1] v = np.zeros(5)
    cdef const int* p1 = &v[0]
    cdef const int* p2 = &v[1]
    cdef ssize_t t = my_pointer_diff(p2, p1) # type of t doesn't have to be ssize_t


Fixed: Variables should be declared explicitly in Custom JS code (ROL-2157)

Pattern is identified and reported at  sonacloud.io as Blocker
JavaScript variable scope can be particularly difficult to understand and get right. The situation gets even worse when you consider the accidental creation of global variables, which is what happens when you declare a variable inside a function or the for clause of a for-loop without using the let, const or var keywords.

Looks good to me.

Thanks @snoopdave for the review


in docs/forms/select, the default selected option tag should have an aria-hidden="true"

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
hello,
in docs/forms/select, the default selected option tag should have an aria-hidden="true" to avoid a vocalization of the content of the option when an AT is entering the select tag. This content is not really needed and the label of the select is enough to understand his purpose. And this info in thee default option is much more for visual users than AT.
And this has to be made in every select tag of the docs...
Reduced test cases
https://getbootstrap.com/docs/5.2/forms/select/
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome, Firefox, Microsoft Edge
What version of Bootstrap are you using?
v5.0 and down

hello,
you should modify each default option tag with the text content of "Open this select menu" by putting :

Open this select menu
One
Two
Three

To be aware of such a modification, you can see it in the accessibility panel in the devtool of Firefox. When adding the ariâ-hidden="true", the value of the select tag must be null
![image](https://user-images.githubusercontent.com/13222389/206670681-3f930d24-2e03-411a-a680-c691a757dc5e.png)
and in Chrome, you can see the null value in the accessibility subpanel in devtool
![image](https://user-images.githubusercontent.com/13222389/206676310-e0b4f030-c3e9-45d9-8216-fa00853d1eaa.png)
if you need more infos, just tell me !

I have raised the PR #37619 and please find attached the screenshot of the validation that I have done in chrome.


gen_gpio_defaults.py need to be updated for gf180 and the new caravel RTL updates

What needs to be fixed is the gate level verilog netlist for the gpio_defaults_block module.  This needs to be in a very specific format, following what was done with the Sky130 versions of the cells, which is a netlist with all of the components but with pins connections made by a series of assignment statements at the end of the cell.  The script expects to see this format or else the script will not work.

Gate level verilog is fixed by #68 ;  need to check that the scripts work with the modified netlists.

More changes were made with an additional commit to PR #68.
Note that PR #68 changes both the gate level netlist and the script.  Kareem's other pull request (#66) accomplishes the same thing (with automation, which is good) but there will probably be issues with missing decap cells, and the power pins will need to have VNW and VPW added when the PDK is updated.


HIVE-25334: refactor timestamp UDF

What changes were proposed in this pull request?

Refactor cast(<> as timestamp)
Why are the changes needed?

Code and old and repetitive
Does this PR introduce any user-facing change?

No
How was this patch tested?

Yes

@zabetak @mattmccline-microsoft @adesh-rao Could you please review the PR?

@zabetak @sankarh could you guys please review the PR?


Google Drive Batch Request Error: socket.timeout: The read operation timed out

Possibly related to #563
Occasionally when executing a batch request using the Python client library callingdrive.files().copy the operation fails with the error socket.timeout: The read operation timed out
Environment details
Running Python 3.7 on Google Cloud Functions environment
Relevant Code
def copy_files(access_token, file_ids, folder_ids, labels):
    def copy_callback(request_id, response, exception):
        if exception:
            print(exception)
        else:
            print(response)

    creds = AccessTokenCredentials(access_token, 'my-user-agent/1.0')
    drive_service = build('drive', 'v3', credentials=creds)

    move_files = drive_service.new_batch_http_request(callback=copy_callback)

    for label, id in zip(labels, file_ids):
        move_files.add(
            drive_service.files().copy(fileId=id, body={"parents": [folder_ids[label]]})
        )

    move_files.execute()

Error
Traceback (most recent call last):
  File "/env/lib/python3.7/site-packages/google/cloud/functions/worker.py", line 313, in run_http_function
    result = _function_handler.invoke_user_function(flask.request)
  File "/env/lib/python3.7/site-packages/google/cloud/functions/worker.py", line 215, in invoke_user_function
    return call_user_function(request_or_event)
  File "/env/lib/python3.7/site-packages/google/cloud/functions/worker.py", line 208, in call_user_function
    return self._user_function(request_or_event)
  File "/user_code/main.py", line 19, in sort
    request_json['labels'])
  File "/user_code/drive.py", line 51, in copy_files
    move_files.execute()
  File "/env/lib/python3.7/site-packages/google_api_python_client-1.7.8-py3.7.egg/googleapiclient/_helpers.py", line 130, in positional_wrapper
    return wrapped(*args, **kwargs)
  File "/env/lib/python3.7/site-packages/google_api_python_client-1.7.8-py3.7.egg/googleapiclient/http.py", line 1450, in execute
    self._execute(http, self._order, self._requests)
  File "/env/lib/python3.7/site-packages/google_api_python_client-1.7.8-py3.7.egg/googleapiclient/http.py", line 1382, in _execute
    headers=headers)
  File "/env/lib/python3.7/site-packages/oauth2client/transport.py", line 175, in new_request
    redirections, connection_type)
  File "/env/lib/python3.7/site-packages/oauth2client/transport.py", line 282, in request
    connection_type=connection_type)
  File "/env/lib/python3.7/site-packages/httplib2/__init__.py", line 1926, in request
    cachekey,
  File "/env/lib/python3.7/site-packages/httplib2/__init__.py", line 1595, in _request
    conn, request_uri, method, body, headers
  File "/env/lib/python3.7/site-packages/httplib2/__init__.py", line 1533, in _conn_request
    response = conn.getresponse()
  File "/opt/python3.7/lib/python3.7/http/client.py", line 1321, in getresponse
    response.begin()
  File "/opt/python3.7/lib/python3.7/http/client.py", line 296, in begin
    version, status, reason = self._read_status()
  File "/opt/python3.7/lib/python3.7/http/client.py", line 257, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/opt/python3.7/lib/python3.7/socket.py", line 589, in readinto
    return self._sock.recv_into(b)
  File "/opt/python3.7/lib/python3.7/ssl.py", line 1052, in recv_into
    return self.read(nbytes, buffer)
  File "/opt/python3.7/lib/python3.7/ssl.py", line 911, in read
    return self._sslobj.read(len, buffer)
socket.timeout: The read operation timed out

Thanks!

Hi! Thanks for the report. I've seen issues in other client libraries saying that timeouts can be a little weird in the Cloud Functions environmentt. Would you mind showing us what's in your requirements.txt?

@busunkim96
# Function dependencies, for example:
# package>=version
sklearn>=0.0
nltk>=3.4
oauth2client>=0.0
pandas>=0.23.0

Hiya, I have been seeing this error when I run reports for Google Analytics, a lot during 11am to 3pm PDT yesterday & just today again so far at 3am PDT. Is there a solution to this so far? I also updated to the 1.7.9 version on all forms.

I haven't had the chance to dig into this further, unfortunately.
How long are your functions running for, on average? Are you close to the 9 minute max, or does this happen earlier?
If each request invocation takes a while, it may be worth moving the client instantiation out into the global scope. There are other networking best practices for cloud functions here.
drive_service = build('drive', 'v3', credentials=creds)

def copy_files(access_token, file_ids, folder_ids, labels):
    def copy_callback(request_id, response, exception):
        if exception:
            print(exception)
        else:
            print(response)

    creds = AccessTokenCredentials(access_token, 'my-user-agent/1.0')

    move_files = drive_service.new_batch_http_request(callback=copy_callback)

    for label, id in zip(labels, file_ids):
        move_files.add(
            drive_service.files().copy(fileId=id, body={"parents": [folder_ids[label]]})
        )

    move_files.execute()

There are a few other support channels that might be worth reaching out to:
https://cloud.google.com/functions/docs/getting-support

Whoop, I apologize; I am seeing this error not on Google's Cloud platform, but running locally.
Intermittently works, but my function does not run for that long, a minute at most.
Do you recommend increasing the timeout for now?

@ktbernoulli Are you in Cloud Functions or in another environment?

Hello, after some more investigation, it might have been a latency issue with the GA account I am creating reports from; I am not sure why it would cause a read operation issue though ):
Thank you for your responses so far ~

I am getting the very same error when using Batch Request containing requests to the drive_service.files().copy().
After different tests, I've noticed that this depends on the size of the batch: if I run small batches (e.g., five calls at time), I don't get the issue.
For the moment, my work-around is to have a wrapper class around the BatchHttpRequest class that takes care of running the requests in small chunks.

@ilpersi doesn't that defeat the point of a batch request? If the size of the request is related it should be handled on Google's side, or they should list any limitations to the size of batch requests in the docs

@hsyyid I agree with you and in the I came to the same conclusion: my current program is not using batch requests anymore.
The size tip is a nice one as it makes it easier to reproduce this issue.

@ilpersi Are you also experiencing this in the Cloud Functions environment?

@busunkim96 No, I am running the code locally on my Windows laptop.
I saw that this very same issue is also happening, much less frequently, with normal calls (not batch) to the drive.files.copy end point.

Hi everyone!
Have you have any solution for this issue??
Thanks in advanced

Thank you @AlJohri  for linking that issue! :)
The default timeout 60 seconds, which is probably too short for many batch requests. It makes sense that the behavior would go away when batches were made smaller (smaller batches -> faster requests).
https://github.com/googleapis/google-api-python-client/blob/f0b025b95b2fb5fd0369d7233614e35b9c86af30/googleapiclient/http.py#L1777-L1792
import socket
from googleapiclient import discovery

socket.setdefaulttimeout(600)  # set timeout to 10 minutes
client = discovery.build("drive", "v3")

I am closing this issue now, but please do open a new issue if you are still experiencing problems.


implementing cabbage tests that use in_beam_watcher and mix_based_child_chain

elixir-omg  inomurko/ife2 $ grep -r ":mix_based_child_chain" apps/
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_watcher/test/omg_watcher/integration/transaction_submit_test.exs:  @tag fixtures: [:in_beam_watcher, :mix_based_child_chain, :stable_alice, :bob, :stable_alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/invalid_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/invalid_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits, :test_server]
apps//omg_watcher/test/omg_watcher/integration/invalid_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/block_getter_test.exs:  @tag fixtures: [:in_beam_watcher, :mix_based_child_chain, :alice, :bob, :alice_deposits, :token]
apps//omg_watcher/test/omg_watcher/integration/block_getter_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits, :test_server]
elixir-omg  inomurko/ife2 $
elixir-omg  inomurko/ife2 $
elixir-omg  inomurko/ife2 $ grep -r ":mix_based_watcher" apps/
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
apps//omg_performance/test/omg_performance/byzantine_event_test.exs:  @tag fixtures: [:perf_test, :mix_based_child_chain, :mix_based_watcher]
elixir-omg  inomurko/ife2 $ grep -r ":in_beam_watcher" apps/
apps//omg_watcher/test/omg_watcher/integration/transaction_submit_test.exs:  @tag fixtures: [:in_beam_watcher, :mix_based_child_chain, :stable_alice, :bob, :stable_alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/invalid_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/invalid_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits, :test_server]
apps//omg_watcher/test/omg_watcher/integration/invalid_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/status_test.exs:  @tag fixtures: [:in_beam_watcher, :root_chain_contract_config]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/in_flight_exit_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :bob, :mix_based_child_chain, :token, :alice_deposits]
apps//omg_watcher/test/omg_watcher/integration/block_getter_test.exs:  @tag fixtures: [:in_beam_watcher, :mix_based_child_chain, :alice, :bob, :alice_deposits, :token]
apps//omg_watcher/test/omg_watcher/integration/block_getter_test.exs:  @tag fixtures: [:in_beam_watcher, :test_server]
apps//omg_watcher/test/omg_watcher/integration/block_getter_test.exs:  @tag fixtures: [:in_beam_watcher, :alice, :test_server]
apps//omg_watcher/test/omg_watcher/integration/block_getter_test.exs:  @tag fixtures: [:in_beam_watcher, :stable_alice, :mix_based_child_chain, :token, :stable_alice_deposits, :test_server]

Some of the tests above re-occur as they use both in_beam_watcher and mix_based_child_chain

apps//omg_watcher/test/omg_watcher/integration/invalid_exit_test.exs:

some got added to cabbage in #1344.

Shared state between tests. The tests above run in a way where the setup of the test is basically a clean slate.

:+1: A follow-up comment: When doing invalid_exit_test.exs in cabbage in a recent PR https://github.com/omisego/elixir-omg/pull/1344 I stumbled upon this very problem.
Tentatively, I fixed this by making sure that those tests added there (to cabbage, that is) as well as the pre-existing in_flight_exits_test.exs cabbage test left the chain in a "clean" state, at least as far as byzantine_events go.
In in_flight_exits_test.exs this meant for instance piggybacking all inputs/outputs of IFE and challenging them. For invalid_standard_exits_test.exs this meant challenging :unchallenged_exits.
However, this still falls short, when speaking about conditions that invalidate the chain permanently (invalid block, invalidly processed exit (see #1318)).

@pdobacz question: the #1344 added some test both in cabbage and in elixir-omg. are we able to delete any tests that got implemented as cabbage tests now?

@InoMurko

@pdobacz question: the #1344 added some test both in cabbage and in elixir-omg. are we able to delete any tests that got implemented as cabbage tests now?

It didn't really add non-cabbage tests (as in, add new behaviors/features tested; it just tidied them) and I postponed removing non-cabbage tests.
As per PR description there:

does some necessary intro fixes to the "old" integration tests which were not strict enough
separates those tests into two "kinds"

tests requiring an invalid block (not moving to cabbage yet)
tests not requiring an invalid block (this is moving)

turns three of those tests into cabbage tests

and

I'm keeping the tidied up "old" approach tests, as I'd like to first gain more confidence in the cabbage tests added.

ahaaa, okay, I only took a quick peek at the tests. are we able to identify and mark potential tests that are implemented in both "old" way and cabbage? just so that we know what tests have coverage in both implementations... I want to avoid guessing what we can delete and what not.

ahaaa, okay, I only took a quick peek at the tests. are we able to identify and mark potential tests that are implemented in both "old" way and cabbage?

TBH, I think the "old" way and cabbage diverge far enough, in terms of how they test, that there is no 1:1 relationship between them.
For now, I used this issue to comment on work done in #1344 related to the "old" invalid_exit_test.exs :point_up: .
But I think, in the long run, this issue is going to be done more or less like this:

top-down design thinking on how cabbage is going to be structured/phrased (in gherkin)/split/setup-torndown
write comprehensive cabbage tests aligning to the design
carefully go through the "old" way tests and figure out, whether removing the "old" way tests will not leave gaps in coverage (possibly tweak cabbage in this process)

So guessing will be avoided.


GhcMod window auto-scroll to bottom

It would be nice for the GhcMod window to auto-scroll to bottom and/or have an option in settings to toggle that feature.

I agree completely. Having to scroll down all the time is quite inconvenient.


Problem displaying pictures on iOS 11

I have been using this plugin for a while now, but newer pictures cannot be displayed (at least not the full image). Judging by the time, I think only pictures I took after upgrading to iOS 11 are affected. This leads me to believe that it has something to do with the new image format (HEIC). Does anyone else have this problem and maybe even has a fix?

Hi @AndreasGassmann,
I'm having the same problem loading images from the library on an iPhone X, using the native URL methods from your fork (thanks!) and found this issue. I also suspect that the problem comes from HEIC/HEIF/HEVC photos I took with the camera, as the <img> throws an error event.
I'm currently looking for a way to get HEIF photos transformed to JPG, as it seems there are native methods to do this (or transparently handled by iOS).
I will post any findings here.

I failed to notice that the thumbnails using native URL are showing correctly (using getNativeThumbnailUrl()), maybe because of the conversion involved. However, the URLs from getNativePhotoUrl() don't load.

Fixed thanks to the PR by @FdezRomero


Istio-operator chart: parameterize resources

This is a tracker issue as I'm on my phone and it's late.
The operator helm chart defaults to 128mb ram, this should be configurable.
I'll create a PR tomorrow.

Solved in #24578
@shamsher31 yep, we like to densely pack our nodes.


publish-marketplace-app.md and cpp-azure-app-offer.md say nothing about need for "Azure usage tracking resource"

I am helping our partner Oracle publish an azure application aka
solution template offer by following our documentation.  Some relevant
documentation includes

./articles/managed-applications/publish-marketplace-app.md

./articles/marketplace/cloud-partner-portal/azure-applications/cpp-azure-app-offer.md

When I finally clicked "Publish" in the Cloud Partner Portal I learned
about an entirely new requirement that I feel should have been mentioned
on at least one of the above pages.
Azure usage tracking resource missing in one or more ARM
templates. To resolve, add a tracking GUID to the ARM template in
mainTemplate.json packages for the following plan:
20190829-arm-oraclelinux-wls-cluster. For more details, see
https://aka.ms/aboutinfluencedrevenuetracking.
Also, the template should not have passed the tests in
https://github.com/Azure/azure-quickstart-templates/tree/master/test/template-validation-tests
but I will file a separate issue for that.

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

ID: ad011394-e4cf-71fc-fefe-c5e21d91d092
Version Independent ID: 5a8896e7-a65c-499c-d26a-8ad9aac21ca7
Content: Azure managed applications in the Marketplace
Content Source: articles/managed-applications/publish-marketplace-app.md
Service: managed-applications
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

Feel free to assign this to me and I'll make a PR.

@edburns We have gone ahead and assigned the issue to you as requested.

Closing this issue because there hasn't been any activity since September 2019. The document is no longer included in the Managed apps documentation. The link redirects to Create an Azure application offer in the Commerical Marketplace documentation. If this is still a valid issue, open a new GitHub issue in the Marketplace documentation.

#please-close


Inline Code Formatting in Callout Card

Issue Summary
Issue Synopsis
In previous versions of Ghost -- prior to upgrading to 5.74.3 -- inline code was formatted as expected in callout cards. Upon upgrading to the latest version, the inline code formatting still displays as expected in the editor view. However, when reading the published article, the formatting of the inline code is lost, and the inline code appears as plain text. This makes it difficult to emphasize and distinguish code and/or commands in callout cards.
Inline code formatting in callout cards was last known to be working for me in Ghost 5.59.
Screenshots
Callout Card with Code in Ghost 5.74.3 Editor

Callout Card in Ghost 5.74.3 Published Article

Callout Card in Google Cache (Ghost 5.59)

Steps to Reproduce

Create a new post or update an existing one
Add a new callout card or update an existing one
Add some text to the callout card, as well as one or many inline code blocks. Inline code blocks are created by wrapping text between backticks. `inline code example` == inline code example
Note that the inline code appears to be formatted correctly within the callout card
Publish or update the post, then open the published post
Note that the inline code formatting in the callout card does not match what's shown in the editor

Ghost Version
5.74.3
Node.js Version
18.17.1
How did you install Ghost?
Followed self-hosting guidance, Ubuntu 22.04
Database type
MySQL 8
Browser & OS version
Google Chrome 119.0.6045.160
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

Can i work on this issue?

Moving my original comment here;

Kevin and team, thanks for your work on this issue and Ghost overall. Is there a recommended way to re-render all posts that I've modified in the past, such that the inline formatting is displayed as expected? In other words, should I republish posts one-by-one, or is there a batch way to have the content regenerated?

Hello, I'm not sure if this is the proper workflow, or if you'd rather a new issue that references this one. However, this issue still seems to be ongoing. I've updated my Ghost instance to the latest version and still and not able to have inline code elements rendered within a callout card.

The fix hasn't been released yet. It will appear in the release notes when it's included


Change Config to use Preferences

This update moves the config from a json file to Preferences. If there are Preferences, these take precedence. If there are no Preferences, and config file exists, then it will load the json config, and write it to Preferences. This ensures the configuration is automatically migrated.
Note: I haven't tested this with the Wi-Fi Manager yet, but I see no reason for it not to work.

This is superseded by the OTA PR.


using pystablemotifs in spyder via a conda enviroment

Hi,
I have been trying to use pystable motifs from spyder, but I receive an error when using a simple code. Briefly, I created an environment in conda where I followed the Installation steps on the read me file, including clasp and gringo. I believe that the error may be related to gringo, which I installed in my conda environment. However, I am not sure about this. By any chance do you know how to solve the problem or how to install pystablemotifs in spyder?
Below I paste the simple code that I used to test the installation and the error that I reveive:
import pystablemotifs as sm
relative_path_to_model = "./models/simple_model.txt"
rules='''xA*=xB
xB*=xA
xC*=xA or not xD
xD*=xC
xE*=xB and xF
xF*=xE'''
primes = sm.format.create_primes(rules)
print("RULES")
sm.format.pretty_print_prime_rules(primes)
print()
ar = sm.AttractorRepertoire.from_primes(primes)
Everything seems fine, but I receive an error with the last line. The error says:
BrokenPipeError: [Errno 32] Broken pipe
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File ~/opt/anaconda3/envs/zanudo/lib/python3.8/site-packages/spyder_kernels/py3compat.py:356 in compat_exec
exec(code, globals, locals)
File ~/.spyder-py3/temp.py:24
ar = sm.AttractorRepertoire.from_primes(primes)
File ~/opt/anaconda3/envs/zanudo/lib/python3.8/site-packages/pystablemotifs/AttractorRepertoire.py:98 in from_primes
x.analyze_system(primes,max_simulate_size=max_simulate_size,max_simulate_size_vc=max_simulate_size_vc,max_stable_motifs=max_stable_motifs,max_in_degree=max_in_degree,MPBN_update=MPBN_update)
File ~/opt/anaconda3/envs/zanudo/lib/python3.8/site-packages/pystablemotifs/AttractorRepertoire.py:196 in analyze_system
self.succession_diagram = sm_succession.build_succession_diagram(primes,max_simulate_size=max_simulate_size,max_simulate_size_vc=max_simulate_size_vc,max_stable_motifs=max_stable_motifs,max_in_degree=max_in_degree,MPBN_update=MPBN_update)
File ~/opt/anaconda3/envs/zanudo/lib/python3.8/site-packages/pystablemotifs/succession.py:515 in build_succession_diagram
myMotifReduction=sm_reduction.MotifReduction(motif_history,fixed.copy(),primes,max_simulate_size=max_simulate_size,max_simulate_size_vc=max_simulate_size_vc,prioritize_source_motifs=prioritize_source_motifs,max_stable_motifs=max_stable_motifs,MPBN_update=MPBN_update)
File ~/opt/anaconda3/envs/zanudo/lib/python3.8/site-packages/pystablemotifs/reduction.py:413 in init
self.stable_motifs = pyboolnet.trap_spaces.compute_trap_spaces(self.reduced_primes, "max",max_output=max_stable_motifs)
File ~/opt/anaconda3/envs/zanudo/lib/python3.8/site-packages/pyboolnet/trap_spaces.py:245 in compute_trap_spaces
return potassco_handle(primes, type_, bounds=bounds, project=[], max_output=max_output, fname_asp=fname_asp, representation=representation)
File ~/opt/anaconda3/envs/zanudo/lib/python3.8/site-packages/pyboolnet/external/potassco.py:74 in potassco_handle
raise Exception
Exception
Regards,

Let's make sure the required software is properly installed. Can you verify that this script runs (from https://github.com/hklarner/pyboolnet/blob/master/tutorials/09_trap_spaces.py):

from pyboolnet.repository import get_primes
from pyboolnet.trap_spaces import compute_steady_states, compute_trap_spaces

if __name__ == "__main__":
    # compute minimal and maximal trap spaces

    primes = get_primes("remy_tumorigenesis")
    mints = compute_trap_spaces(primes, "min")
    print(len(mints))

    max_trap_spaces = compute_trap_spaces(primes, "max")
    print(len(max_trap_spaces))
    print(max_trap_spaces)

    # compute steady states using the ASP solver

    steady = compute_steady_states(primes)
    print(len(steady))

Closing due to inactivity. Will re-open upon request.


Fixed broken link

Docs Build status updates of commit 753b1c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamicsax2012-technet/creating-exchange-rate-providers-for-microsoft-dynamics-ax-2012.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit d4b9a41:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamicsax2012-technet/apply-updates-and-hotfixes.md
:white_check_mark:Succeeded
View

dynamicsax2012-technet/creating-exchange-rate-providers-for-microsoft-dynamics-ax-2012.md
:white_check_mark:Succeeded
View

dynamicsax2012-technet/demand-forecasting-in-microsoft-dynamics-ax-2012-r3.md
:white_check_mark:Succeeded
View

dynamicsax2012-technet/find-out-which-version-of-microsoft-dynamics-ax-you-are-using.md
:white_check_mark:Succeeded
View

dynamicsax2012-technet/overview-of-the-microsoft-dynamics-ax-intelligent-data-management-framework-idmf.md
:white_check_mark:Succeeded
View

dynamicsax2012-technet/what-s-new-financial-dimensions-framework.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Video Upload

Make tweepy handle MP4 videos upload according to the Twitter API documentation for chunked uploads :
https://dev.twitter.com/rest/public/uploading-media#chunkedupload

I was going to work on this myself, but as it turns out, someone already had. Nice!
This doesn't seem to be usable, though. Sure, this allows for uploading videos, but there's no way to actually tweet them. The update_with_media (or really the update_status method, since update_with_media is deprecated needs to be able to handle video files / filenames for it to actually be usable, right?

Hello @obskyr !
No need to update update_status function. You can send the video link in the media_ids argument and it rocks :+1:
I tried this last week and it works really fine ! Of course you will have to send Twitter-compliant videos (MP4 <= 30sec, 15MB max, 1280x1024max, etc. you can have the list of constraints in the given link). Otherwise, a TweepError is raised.
I did not change anything else and it works fine for me :)
Let me know if something goes wrong ;)

Tip: You cannot send videos and images in a tweet. You can only send 1 video or 4 images max.

Oh, the docs don't mention the media_ids parameter. The docs are out of date in general, in fact. Cool, so there is a way to use it.
Regardless, don't you think it should be easier to tweet videos with the API? It'd be way more dev-friendly if you could just tweet a video with a filename / file object and it'd handle the upload under the hood for you, like what is done with images. All that would be needed would be some checks to see whether a file is a video or an image, which is easy (basically just check the extension).

Yes you're right !
I will create a wrapper function to send directly tweets with medias by handling upload automatically ;)
Thanks!

Thank you for awesome work, @Choko256.
@joshthecoder do you plan to merge it?

Hey, great work. I was just trying to find a solution to a GIF problem and ended up here. One thing that I found (since my code is python3): you're going to run into problems with the urllib import statement and the supported versions of python. Maybe change from:
import urllib

to:
if six.PY2:
    from urllib import urlencode
elif six.PY3:
    from urllib.parse import urlencode

And then change lines 1444 & 1481 to just use urlencode.

Fails sometimes for me with following exception:
TweepError: {"request":"\/1.1\/media\/upload.json","error":"SegmentIndex must be between 0 and 999."}
  File "tweepy/api.py", line 252, in video_upload
    )(*args, **kwargs)
  File "tweepy/binder.py", line 243, in _call
    return method.execute()
  File "tweepy/binder.py", line 227, in execute
    raise TweepError(error_msg, resp)

How large is the file you're trying to upload

Found root cause:
https://github.com/tweepy/tweepy/pull/655/files#diff-ea5dd38a4efd9ff36c96e04ab0597cfbR239
File size = 5219933.
chunk_size = 4096
nloops = 1275

I think the code should raise an exception if nloops > 999 and don't try to upload. Also explain to the method caller, that he/she needs to increase chunk_size or decrease file size.

4k is too small as a default. Should probably be set to something more reasonable like 1MB.
Rather than returning an error, if the user really wants a small chunk size, disallow any value smaller than 16K, so that it always succeeds. (Max size / 16K = 960 chunks)

This is great and I would love to see it in Tweepy asap.
But, what do you think about having a single media_upload function that's agnostic about file type? I think it would just need to have a single mimetypes.guess_type check, and then send the sile to the correct function. This would save trouble of having to check file file for applications that might be upoading video and images.

Hi,
Just getting started with python and the twitter APi for a twitter bot, can anyone help me with where I might be going wrong with the video send:
twitterApi.update_status(filename = 'MP4_SIZE_TEST_2.mp4',status=replyText, in_reply_to_status_id=tweetId, file = 'MP4_SIZE_TEST_2.mp4')
Im simply trying to reply to an @mention tweet with a video and a message (message is created earlier and assigned to the replyText var).
I get the message ok, and works fine if i try with a message and an image, but video never makes it through or throws error

I'd be very happy to see Tweepy support this. Any updates?

Hi guys,
Did someone find a solution ?
Because I've got the same issue, when I post a video I got this answer from twitter : {"media_id":55783223323555,"media_id_string":"555556565465656","size":323161,"expires_after_secs":86400,"video":{"video_type":"video/mp4"}}
Like if everything went fine but there is no video on Twitter.
Do you have any idea ?
Best regards.

My bad everything fine we just need to update status with the media ids.

Superseded by #672 and #929
@jason-hyland-heyhuman API.update_status does not accept filename or file parameters, and those aren't being added by this PR.

Any updates on this?

The video-upload branch / pull request #1486 should be complete now.
Any feedback or review would be appreciated.


⚠ Samsung has degraded performance

In 3929534, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2343 ms

Resolved: Samsung performance has improved in 78ab73c.


[SPARK-39854][SQL] replaceWithAliases should keep the original children for Generate

What changes were proposed in this pull request?

The current implementation of the replaceWithAliases method in NestedColumnAliasing replaces the children of the current plan with mapped aliases. When the current plan is a Generate -- which keeps a set of indices unrequiredChildIndex for unsed child outputs -- and if the replaced child happens to be in this set, because the unrequiredChildIndex is not updated for this Generate plan, the original unrequiredChildIndex will point to the new children, leading to exceptions/errors.
Why are the changes needed?

See the description above.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

A unit test is added to SparkPlanSuite

Can one of the admins verify this patch?

Any comments?

Hi @dongjoon-hyun , is it possible to find someone to view the change (it's a relatively small one :)? Thanks.

I'll take a look today or tomorrow. Thanks @dongjoon-hyun

Thank you!

I removed State tag. Could you rebase this PR to the master branch, @jiaji-wu ?

shall we change unrequiredChildIndex: Seq[Int] to requiredChildren: Seq[Attribute]? then column position is not an issue anymore.

I think we just hit this after upgrading to Spark 3.4. Some change is now triggering the GeneratorNestedColumnAliasing where it wasn't happening before, and as a result we're getting corrupted generators because of the stale unrequiredChildIndex value.

Thank you for reporting, @Kimahriman .

BTW, may I ask what is your previous successful Spark version, @Kimahriman ?

3.3.2

@Kimahriman feel free to pick up this if you have an idea about how to fix it.

I think I'm also hitting another possibly unrelated bug with the GeneratorNestedColumnAliasing that I'm still trying to track down, and I still haven't figured out what changed between 3.3.2 and 3.4.0 that would cause GeneratorNestedColumnAliasing to trigger now for the exact same plan when it wasn't in 3.3.2.


Use tested keyring funcs to load keys

Regarding issue #1

Need to run go mod tidy (according to my env)


idea: Cortex API Playground

Problem Statement

Users don't know the current API
It is hard to craft CURL requests from scratch

Feature Idea

Bring back the API playground at localhost:port/api
Autogenerated (not manual pls)

Added a comment to #1366

swagger to be root url
output semantics

I fixed this issue in this two pr #1397 #1392

Marking as complete, nice work @nguyenhoangthuan99!


Use of HTML5 history API

I was thinking that iD should remember major changes in the url.
Currently iD doesn't keep a record of the part in url after #.
For eg.

The level of zoom.
Major change in the latitudes or longitudes, (jumping across a city).

After discussing on IRC with @bhousel,
A use case for this enhancement.
The user can suddenly find themself somewhere that they didn't expect to be.. whether due to the panning bug, or even just moving the minimal around.

I'm not sure this is a good idea. It's a pretty well established convention with web slippy maps that panning and zooming doesn't add history entries. I find the sites that do add history entries with every pan and zoom to be quite annoying to navigate back from. And adding history entries in some cases, but not others, sounds like it would introduce an unpredictability that would also be a poor user experience.


Take prefix into account in getAll-function

When using lockr with a prefix, getAll() returns all localStorage-values, including those that do not have the specified prefix. This is a simple fix that works with or without a prefix.
Perhaps it should be considered to add a function that returns all keys/value-pairs or just all keys? Considering most other functions in the library depend on keys, the values by them selves aren't very useful.

Thanks a lot for your contribution.


HTML: Navigation Links move page to different areas

WHEN I click one of the links in the navigation
THEN the UI scrolls to the corresponding section

This is complete.  Links are working


Should we optionally display the weekly/monthly budget on the budget bar?

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?

More than one fund has reached out to me recently to ask for this. We've generally discouraged doing Real Budgeting in DARIA (excel is way better and more consistent than we'll ever be) but people are making pretty good arguments that some signals would be helpful.
@lwaldsc as one of the original intellectual architect of the budget bar interested in your thoughts - my recollection is that we didn't do this originally because we thought it would bum out DCAF CMs (one late case and there you go). but wonder if this is similarly a bummer for smaller funds.

What feature or behavior is this required for?

not doing math

How could we solve this issue? (Not knowing is okay!)

if we were to do this, it would look like:

config to toggle display on/off

add some math to the budget bar like (soft pledged: X) + (sent pledged: Y) = X+Y / (weekly budget) (Z%)

Anything else?

nah

okay, let's do this. Specifically:

Config to toggle this on/off called something display_budget_bar_aggregate_data, defaulting to having it off
If it's on, add these calculations to the view. (I don't care how you get there, but not making additional database calls would be a nice bonus if possible!)

@elimbaum you're up!

you got it!! are those the four metrics we want?

hm, great question. Let's start with the dollar figures and cut the percents, and see how close that gets us.

frontend draft, open to comments!

refactoring this a bit to make it easier to add more statistics in the future w/ out a bunch of copy paste.

I agree that the pledging concept is kinda confusing - refers to both setting aside money in the CM's case, and actually sending the promise of money in the clinic's case - but those are the terminology conventions at the moment, so let's leave that as is for the time being.