QG 4 checks (Release 24.05)

QG checks
Please keep this issue open until QG is concluded and will be managed by the Issue Creator!
We will inform you about finding and proposals in separated issues, this issue here is for the Overview of the Checks!
Please keep this issue open until QG is concluded!
Product Owner:
Dev SPOC:
Helm Chart Version:
App Version:
Release Managemnet Reference Issue:
Check of Tractus-X Release Guidelines

Currently implemented automatic checks can be found under your product on our Release Guidelines Checks Board
This QG Check is depending on the mandatory information from our current Release Guidelines

TRG 1 Documentation

[ ] TRG 1.01 appropriate README.md
[ ] TRG 1.02 appropriate install instructions either INSTALL.md or in README.md
[ ] TRG 1.03 appropriate CHANGELOG.md
[ ] TRG 1.04 editable static files

TRG 2 Git

[ ] TRG 2.01 default branch is named main
[ ] TRG 2.03 repository structure
[ ] TRG 2.04 leading product repository
[ ] TRG 2.05 .tractusx metafile in a proper format

TRG 3 Kubernetes

[ ] TRG 3.02 persistent volume and persistent volume claim is used when needed

TRG 4 Container

[ ] TRG 4.01 semantic versioning and tagging
[ ] TRG 4.02 base image is agreed
[ ] TRG 4.03 image has USER command and Non Root Container
[ ] TRG 4.05 released image must be placed in DockerHub, remove GHCR references
[ ] TRG 4.06 separate notice file for DockerHub has all necessary information

TRG 5 Helm

[ ] TRG 5.01 Helm chart requirements
[ ] TRG 5.02 Helm chart location in /charts directory and correct structure
[ ] TRG 5.03 proper version strategy
[ ] TRG 5.04 CPU / MEM resource requests and limits and are properly set
[ ] TRG 5.06 Application must be configurable through the Helm chart
[ ] TRG 5.07 Dependencies are present and properly configured in the Chart.yaml
[ ] TRG 5.08 Product has a single deployable helm chart that contains all components
[ ] TRG 5.09 Helm Test running properly
[ ] TRG 5.10 Products need to support 3 versions at a time
[ ] TRG 5.11 Upgradeability

TRG 6 Released Helm Chart

[ ] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[ ] TRG 7.01 Legal Documentation
[ ] TRG 7.02 License and copyright header
[ ] TRG 7.03 IP checks for project content
[ ] TRG 7.04 IP checks for 3rd party content
[ ] TRG 7.05 Legal information for distributions
[ ] TRG 7.06 Legal information for end user content
[ ] TRG 7.07 Legal notice for documentation
[ ] TRG 7.08 Legal notice for KIT documentation

TRG 8 Security

[ ] TRG 8.01 Mitigate high and above findings in CodeQL
[ ] TRG 8.02 Mitigate high and above findings in KICS
[ ] TRG 8.03 Mitigate high and above findings in GitGuardian
[ ] TRG 8.04 Mitigate high and above findings in Trivy

Hints
Information Sharing

Hey @ciprianherciu. Please fill the following info:
Product Owner:
Dev SPOC:
Helm Chart Version:
App Version:

Also I need a volunteer committer who does the checks with me, can you name someone please?

I approve the QG, all issues are resolved. Final versions are:
Helm Chart Version: 0.1.8
App Version: v2.4.0
Thanks @RoKrish14 for the help with the checks!

Hey all, a patch has been released, so the new versions approved by me in terms of TRGs are the following:
Helm Chart Version: 0.1.9
App Version: v2.4.1


"invalid input text length" for a long customer password?

One of our customers is getting "invalid input text length" when trying to auth their First Republic account. Is this a real limitation of Plaid Link?
They claim their password is 24 characters long—seems like a perfectly reasonable length to me!

going through old tickets -- i can't reproduce this and don't see any other reports of this, so closing it out as no longer relevant.

I was able to reproduce this today

@mckapur @thomasmost OK, I dug into this a little bit more and here's what I found:

This only applies to First Republic Corporate (not first republic personal, or most other institutions)
If you go to the first republic corporate online banking login page at https://corponline.firstrepublic.com/wcmfd/wcmpw/CustomerLogin you will find that the login screen does in fact have a 20-character limit on the password input field

Therefore, as far as I can tell, Plaid is correctly reflecting a password length limitation set by First Republic. IF customers are seeing this and have a password longer than 20 characters, they are probably trying to log into First Republic Corporate when their account is actually with First Republic Personal.

Hi @phoenixy1, I ran into this issue recently as well. While The First Republic Corporate site (https://corponline.firstrepublic.com/wcmfd/wcmpw/CustomerLogin) appears to limit the number of characters in the password to 20 chars, we were able to prove that if you keep typing additional characters (or use 1password to auto-fill a password of length > 20 chars), the form on the webpage accepts additional characters and the login will work for passwords longer than 20 chars, even though the browser visually does not show any characters typed beyond the first 20. Said another way, the truncation of the password is a visual truncation only. For this reason, it is possible to log into the First Republic corporate account with a password of at least 24 characters (this is the length we were able to verify), which then makes it impossible to connect that same account via Plaid due to the 20 character restriction imposed by Plaid.

@amacrae2 thanks for digging into this! I have got to admit that this seems both very edge casey and at least partially First Republic's fault, but I think you're right that Link shouldn't act this way.
This doesn't seem specific to react, though, so I'll raise it to the overall link team

This is now fixed!


Rolling file writer by date does not write in the original file

Hello !
Given the following configuration:
<seelog type="sync" >
    <outputs formatid="main">
            <rollingfile type="date" datepattern="2006-02-02" filename="/var/log/logByDate.log" />
            <rollingfile type="size" maxsize="5000" filename="/var/log/logBySize.log" />
    </outputs>
    <formats>
        <format id="main" format="%Date(2006 Jan 02/3:04:05.000000000 PM MST) [%Level] %Msg%n"/>
    </formats>
</seelog>

Seelog will write current logs in logBySize.log as expected, but not in logByDate.log. Instead, it will write in the rolling file of the day: logByDate.log.2016-04-04. I suppose this is a bug, right ?

Hey!
No, that works as intended: rolling receiver
Check the 'filename' param description.

Ok, thank you for your answer.
So, having log files matching filename.DATE_PATTERN pattern, wouldn't it be better if the logs of the current period were always written in filename and just create the filename.period when seelog rolls the file ? It would be easier to access the log file of the current period (usually daily rotation) to make research, more recent logs always being in filename.log. Also, if I am not wrong, with the size type, seelog writes in filename.log, then in filename.log.1, filename.log.2, etc.... So the size type could also benefit from this feature.

Yeah, probably it could be easier this way, I'll think about implementation possibility. Currently it doesn't check the file modification date and only checks the filename, thus we need to store the time in the filename to be able to know when to roll.

Can we get the last modified time from the stat'ing the file and format that timestamp before diffing?

Yeah, we can do that.

Ah, this only works for rollingIntervalAny. I see that nothing sets custom rolling intervals at the moment except for tests. Are there plans to support this in the future?
If so, I think we'll need to write this information to disk. We can touch a .seelog_last_roll file on file creation during log roll and parse that to get tprev (previous roll time).

The rollingIntervalDaily and related code is deprecated. It was used in earlier seelog versions and now it's just left there, I forgot to delete it. But it's basically unused, not mentioned in the reference and basically unusable, because the rollingIntervalTypeFromString func is not used anywhere. So it shouldn't affect anything and should be deleted. I'll go delete it now.
And yes, your initial solution works fine as far as I see, so maybe we should modify this pull to implement the stat'n'diff solution, it should be easier than .seelog_rolling_tracker approach.
Basically, the rolling writer approach is pretty simple: we take the last modification time, format it using the datepattern parameter, then we take time.LocalTime(), format it using the datepattern parameter, then we compare and if results are different, we roll. Currently we store the already formatted modification time in the file. I think we could just use stat info and follow the same logic without changing the concept. This works fine.

Ok, I removed the deprecated rollingIntervalDaily.

Perfect, I'm on the same page here. Thanks for the quick response and cleanup. I'll go ahead and cleanup my end too.

Fixed in latest revision. Thanks to @jonsyu1 for this PR


Update widget labels on battery widget

I didn't find the battery widget labels to be very intuitive - here are my suggestions for new ones. If those don't work, maybe a tooltip with the full text and a short explanation of what each status might mean?

You should change the labels in the en.json file.

Oh, duh, sorry! Closing this one and will submit a PR against that.


Update docstrings and docs

Coverage decreased (-0.5%) to 99.465% when pulling 1c06cfe9779b76b1a7bc736fce14f1e8cd030d82 on improve_docs into 2a4706d639e6a6e5f95db26cce16c6ed7e401686 on master.

we need to find a way to link classes and methods in the text to the proper docs section

since we are dealing with docs here,

I just noticed that we have the documentation of the util module that is called utils (which is not correct),
and we are hardcoding the functions we want the documentation for and therefore we are missing some (we should do as we are doing with the other modules and let all the functions/methods have docs)

since we are dealing with docs here,
1. I just noticed that we have the documentation of the `util` module that is called `utils` (which is not correct),

Considering that the module name is util i would say util

2. and we are hardcoding the functions we want the documentation for and therefore we are missing some (we should do as we are doing with the other modules and let all the functions/methods have docs)

No objections, but TBH i don't understand the point XD

Considering that the module name is util i would say util

yes yes this is what I was saying

No objections, but TBH i don't understand the point XD

I'm saying that we should stop hardcoding functions there because otherwise every time we add a new thing we should remember to add that there as well

@nicolebussola everything is good, I will approve it as soon as the LocalOtsuThreshold example is here


No need for a Panku.gd and Panku_impl.gd, currently Panku.gd does not contain any implementation

I suggest that it contains only a file called panku.gd with the implementation that is in the panku_impl.gd file

In my option it will be clearer to only expose the interface functions, or is it a convention to put everything into a single file in Godot singletons?

I don't believe there is a pattern with autoloads, but following a SOLID principle, I can't see what purpose the panku.gd class has
Do you have an example in godot of a structure that uses subclass as an interface?

This pointless script will be removed later when the docs is finished.


[ApiView] Swagger paths should NOT have a trailing colon

When creating an ApiView listing for a swagger file with an action, the trailing colon on the path makes it look like we're sandwiching the action name in colons.

We should remove the trailing colon on paths just like we do for verbs already.  It should instead look like:

PR created https://github.com/Azure/azure-sdk-tools/pull/4740

@tg-msft done

@tg-msft FYI that you won't see this fix until next APIView deployment which is scheduled for 11/28


Kgudel

Removes erroneous files
Adds more documentation to the check files
Updates readme to reflect changes to files and list dependencies of running the code

:+1:


Upstream v1.58.0 with Chargify modifications

This brings us up to v1.58.0 of activemerchant/active_merchant upstream,

bfdb60b - (tag: v1.58.0) release version 1.58.0 (9 weeks ago)

plus the following additions:
3a35be4 650b16f  PayPal
2a75799 0be2c13 d912f42 Fusebox
e84bbcc 95c5865 Eway Rapid 3.1
40b43fc Paymill
See: https://chargify.hackpad.com/ActiveMerchant-Upgrade-Notes-hXUnBe8NRim

This wasn't "merged" -- master was reset to the v1.58.0-custom-1 tag and force pushed.


how to do？'nopython'

The 'nopython' keyword argument was not supplied to the 'numba.jit' decorator. The implicit default value for this argument is currently False, but it will be changed to True in Numba 0.59.0. See https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-object-mode-fall-back-behaviour-when-using-jit for details.
'(MaxRetryError("HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: /charactr/vocos-encodec-24khz/resolve/main/config.yaml (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x0000021D9CE155D0>, 'Connection to huggingface.co timed out. (connect timeout=10)'))"), '(Request ID: 3d32e4dc-962d-4787-8d95-f2ec026dcfae)')' thrown while requesting HEAD https://huggingface.co/charactr/vocos-encodec-24khz/resolve/main/config.yaml
huggingface_hub.utils._errors.LocalEntryNotFoundError: Connection error, and we cannot find the requested files in the disk cache. Please try again or make sure your Internet connection is on.

Download this file.
https://pan.baidu.com/s/123sbEQRvbWJrx728JwgqSg?pwd=h2gi
If you're on Linux, run this:
tar zxvf vocos.tar.gz -C ~/.cache/huggingface/hub
If you're on Windows, please unzip the file to this directory:
C:\Users%username%.cache\huggingface\hub\models--charactr--vocos-encodec-24khz\


update and delete products

add bdd test for updating products
add bdd test for deleting products

Codecov Report

Merging #98 (832864b) into main (fa780ec) will increase coverage by 0.19%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #98      +/-   ##
==========================================
+ Coverage   97.58%   97.77%   +0.19%
==========================================
  Files           7        7
  Lines         538      540       +2
==========================================
+ Hits          525      528       +3
+ Misses         13       12       -1

Impacted Files
Coverage Δ

service/models/product.py
99.22% <100.00%> (+0.05%)
:arrow_up:

service/routes.py
98.18% <100.00%> (+0.52%)
: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 fa780ec...832864b. Read the comment docs.


Use sensible defaults for widths on tablets.

This implements some sensible widths for dialogs on tablets. Before, they often went nearly edge-to-edge with some minor padding on the sides, and the material design spec doesn't provide much help here. We had a long discussion about how best to go about this, with the ideal solution being to automagically create the best experience based on preferred line length. Handling every possible case of that is going to be a lot of tedious work though.
This is a simpler approach, where we basically say up front what we believe a good width is.  Toyed with them in our BottomSheet library, and it turns out they look pretty good here. This is by far the simplest approach, and covers probably 98% of all the use cases.
Resolves #552
Screens:
Landscape

Before
After

Portrait

Before
After

Before
After

Before
After

Before
After

Before
After

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>


Add options interface for AGC options

The AGC feature within the extension has a set of options to control its behavior. This is how the options show up in the WikiTree AGC extension:

I would like to add these options into the WBE options user interface. This will require some design work and probably some redesign of the current options code. So I'm opening this issue to discuss the design before starting on the coding.
I can try to design it such that each feature can register a set of options and the common code handles saving and restoring the options and building the user interface (HTML page) for the options. This is how the wikitree-sourcer  extension works and it is very modular. To add options for a new site in Sourcer the only change needed in shared code is to add one import line.
A few UI design choices have been mentioned.

A style like WikiTree Sourcer where there could be a tab for each category and within each tab a dropdown for each feature. (See screenshot below)
Like this existing design with all the categories and features in a flat scrollable page but with the ability to expand/collapse on a feature to reveal/hide its options.
To not use the options page at all for an individual feature but have some feature specific way of getting to its options.

Here is a screen shot of the Sourcer options page:

Any thoughts?

I can try to design it such that each feature can register a set of options and the common code handles saving and restoring the options and building the user interface (HTML page) for the options. This is how the wikitree-sourcer extension works and it is very modular. To add options for a new site in Sourcer the only change needed in shared code is to add one import line.

This is how I was hoping things would go, where very little has to change in the shared code to add extra options. I just wasn't sure how to implement something like that.
For the UI, I slightly prefer option 2.

I prefer option 2, too.

I have an implementation of option 2. The AGC options are pretty complicated but I have made it work. I'm still cleanng up the code but this is what it looks like.
If a feature has options the "Show Options" button will be displayed:

When you show the options they are displayed within the feature:

Thats nice Rob

Yeah, that's really nice, thanks for working on this!

This is now implemented


Update request: freeimage unstable-2021-11-01 → unstable-2023-05-20

Package name: freeimage
Latest released version: unstable-2023-05-20 (r1909)

Current version on the unstable channel: 2021-11-01
Current version on the stable/release channel: 2021-11-01

[x] Checked the nixpkgs pull requests

Notify maintainers
@viric
@L-as

Note for maintainers: Please tag this issue in your PR.

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

freeimage is probably full of many more security holes that are yet to be found, agree with above, but updating it probably isn't too hard if upstream hasn't changed much

Our position is that freeimage is unmaintainable.
The upstream updates since the version in nixpkgs are basically updates of the bundled libs, which we ~make~ made serious efforts to de-vendor and replace with nixpkgs-versions anyway, so probably wouldn't make any difference to the resulting package.
The vulnerabilities listed in knownVulnerabilities are largely in freeimage code and I don't see any signs of them having been addressed or even acknowledged by upstream.
From what I can tell, there is no way of providing any package that depends on freeimage in a secure way. Packages that depend on freeimage need to have their upstreams made aware of this so they can stop using it.

Just want to chime in with this repo https://github.com/danoli3/FreeImage, claiming that it has fixed all of the security issues.

We could add a new package under a new name and deprecate the old one.


[tool_crash] FileSystemException: Cannot delete file, OS Error: Accès refusé., errno = 5

Command
flutter --quiet assemble --depfile C:\Users\ASUS\Desktop\PFE\visitme\build\app\intermediates\flutter\debug/flutter_build.d --output C:\Users\ASUS\Desktop\PFE\visitme\build\app\intermediates\flutter\debug -dTargetFile=C:\Users\ASUS\Desktop\PFE\visitme\lib\main.dart -dTargetPlatform=android -dBuildMode=debug -dTrackWidgetCreation=true --DartDefines=flutter.inspector.structuredErrors%3Dtrue debug_android_application

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot delete file, OS Error: Accès refusé.
, errno = 5
#0      _File.throwIfError (dart:io/file_impl.dart:635:7)
#1      _File._deleteSync (dart:io/file_impl.dart:298:5)
#2      FileSystemEntity.deleteSync (dart:io/file_system_entity.dart:408:7)
#3      ForwardingFileSystemEntity.deleteSync (package:file/src/forwarding/forwarding_file_system_entity.dart:70:16)
#4      ForwardingFileSystemEntity.deleteSync (package:file/src/forwarding/forwarding_file_system_entity.dart:70:16)
#5      ErrorHandlingFileSystem.deleteIfExists (package:flutter_tools/src/base/error_handling_io.dart:79:12)
#6      FlutterBuildSystem.trackSharedBuildDirectory (package:flutter_tools/src/build_system/build_system.dart:699:33)
#7      FlutterBuildSystem.build (package:flutter_tools/src/build_system/build_system.dart:587:5)
<asynchronous suspension>
#8      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:220:32)
<asynchronous suspension>
#9      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1157:12)
<asynchronous suspension>
#10     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1009:27)
<asynchronous suspension>
#11     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#12     AppContext.run (package:flutter_tools/src/base/context.dart:149:12)
<asynchronous suspension>
#13     CommandRunner.runCommand (package:args/command_runner.dart:197:13)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:278:9)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>

[✓] Flutter (Channel stable, 2.0.5, on Microsoft Windows [version 10.0.19042.928], locale fr-FR)
    • Flutter version 2.0.5 at C:\src\flutter
    • Framework revision adc687823a (4 weeks ago), 2021-04-16 09:40:20 -0700
    • Engine revision b09f014e96
    • Dart version 2.12.3

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\ASUS\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 4.1.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] VS Code (version 1.53.2)
    • VS Code at C:\Users\ASUS\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.19.0

[✓] VS Code, 64-bit edition
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.19.0

[✓] Connected device (3 available)
    • SM G532F (mobile) • 4200b257b27f1499 • android-arm    • Android 6.0.1 (API 23)
    • Chrome (web)      • chrome           • web-javascript • Google Chrome 90.0.4430.212
    • Edge (web)        • edge             • web-javascript • Microsoft Edge 90.0.818.56

• No issues found!

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 9b2d32b605630f28625709ebd9d78ab3016b2bf6
Plugins
connectivity-3.0.3
connectivity_for_web-0.4.0
connectivity_macos-0.2.0
flutter_plugin_android_lifecycle-2.0.1
image_cropper-1.4.0
image_picker-0.7.4
image_picker_for_web-2.0.0
libphonenumber-2.0.0
libphonenumber_plugin-0.2.3
libphonenumber_web-0.2.0+1
package_info_plus-1.0.1
package_info_plus_macos-1.1.1
package_info_plus_web-1.0.1
qr_code_scanner-0.4.0
url_launcher-6.0.3
url_launcher_linux-2.0.0
url_launcher_macos-2.0.0
url_launcher_web-2.0.0
url_launcher_windows-2.0.0

possible duplicate of https://github.com/flutter/flutter/issues/69116
@zneti-sourour
please try this possible solution

Closing this as duplicate of https://github.com/flutter/flutter/issues/69116


A11y_AzureDataStudio_Welcome_AzureDataStudio-Insiders_ScreenReader : No proper name is announced for "Close" control for screen reader users.

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”

If Welcome screen is not shown on application launch, then navigate to Help --> Welcome.
Navigate to the "Close" (X) control present besides "Start Tour" control.
Start screen reader, listen if proper name is announced for the "Close" control or not.

Actual:
When screen reader user navigate to the "Close" (X) control only the role of the control i.e. "button" is announced for the screen reader user, but no proper name as "Close" is announced so that the user is able to identify the control.
Expected:
The "Close" (X) control should be announced with a meaningful name as "close" for screen reader users.
User Impact:
If the proper name of the interactive element is not announced for screen reader users then the user will have difficulty in understanding the control and interacting with the control.
Attachment link for Reference:
11528_A11y_AzureDataStudio_Welcome_AzureDataStudio-Insiders_ScreenReader No proper name is announced for "Close" control for screen reader users.mov.zip

Closing this bug , as the scenario itself is not present in UI.
GitHubTags:#Closed;


chore(brand-components): filled out knobs for other Brand stories

Filled out knobs for other Brand stories
Marketing was looking to take screenshots of custom values, so this'll help them out a little.

🚀 Styleguide deploy preview ready!https://5e90932817210f455f13c75f--codecademy-styleguide.netlify.comDeploy Logs

🚀 Styleguide deploy preview ready!https://5e9095aa8d19e8616c56f36e--codecademy-styleguide.netlify.comDeploy Logs

🚀 Styleguide deploy preview ready!https://5e90988211596c57f7dca8ae--codecademy-styleguide.netlify.comDeploy Logs

I'll follow up with a standardized decoratedStories/decoratedStory pair of functions we can wrap all of them with.


Unable to reproduce Slayer NMNIST Test Accuracy

When running the train.ipynb for NMNIST I am unable to reproduce the test accuracy. I only reach sub 30% accuracy rates. The model is clearly overfitting based on the fact that I reach higher train accuracies faster than the existing numbers. The first epoch I get 90% train vs 80% expected. Similar story when it comes to train loss loss, which is lower significantly faster 0.26 after first epoch compared to 0.4 expected. Test loss is always much higher, 1.0 compared to <0.2.  To be clear I trained the models far longer than a single epoch, this just better shows the discrepancy I am seeing. Messing about with hyper parameters also gave no success.
I tried loading the existing trained model in nmnist/Trained and this gave the expected test accuracy numbers. When further training the pretrained model the accuracy degrades quickly.
I downloaded the NMNIST data manually and the only change I made was to an assert statement in the NMNISTDataset because it was incorrect:
assert len(glob.glob(f'{data_path}/')) == 0 -> assert len(glob.glob(f'{data_path}/')) != 0
To reproduce current behavior
Run train.ipynb.
Expected behavior
Expected to get accuracy values in the high 90s as shown in the notebook and on the website.
Environment (please complete the following information):

OS: Linux
lava-dl                  0.4.0
lava-nc                  0.8.0
torch                    1.13.1+cu117
Using CUDA 11.7.

This is resolved. It turns out the train data was not fully downloaded. I downloaded it from the google drive link, so if anyone else is having this issue double check that the download from drive was actually correct.


Allow use of tables

I want to use this module with Bootstrap 3.3.7 and use tables but in the source code it is harcoded to use a un-ordered list (ul). If this could be customizable that would be awesome

Does using a function for the template option not allow you to customize that?

I posted an example of using a template over here


⚠ Bofrost.at has degraded performance

In 88a45f0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2127 ms

Resolved: Bofrost.at performance has improved in 55195a5.


[WIP] datafile datatypes

This feature breanch is intended to partly implement #981:

add models and views for viewing, creating, and updating DataTypes
add views for managing a project's registered DataTypes
handle specified DataTypes in the API for file uploads
some default behavior if DataTypes weren't specified during upload
records DataType edit history
adds public API endpoint for DataTypes
adds public API endpoint for projects

Close in favor of updated PR


Create Guide “installation-for-beginners”

Automatically generated by Netlify CMS

👷 Deploy Preview for hotplate-docs processing.

Name
Link

🔨 Latest commit
f6b7b79a1461f4e486c404a525b180b89ad422d2

🔍 Latest deploy log
https://app.netlify.com/sites/hotplate-docs/deploys/62be46fb9a7f1b000a0f9924


TimersManager: Start timer post launch hook

Brief description
Currently only post launch hook starting timer is in Ftrack but it can be triggered using TimersManager.
Changes

added new post launch hook using webserver to start timer for passed context
ftrack post launch hook does not start timer
removed need of "hierarchy" in rest api call to start timer
replaced not used change_timer_from_host with static method start_timer_with_webserver

Task linked: OP-1172 Start timer post launch hook

Is there any use case where context could be empty or would I add validation for context whenever I would like to use the start_timer_with_webserver ?

I don't think that there is a use case when client side could handle that in any way. I mean if you find out that context you want to use is invalid what will you do with that? But it does make sense to return "success" in response. And add validate context method but I would not call it automatically in start_timer_with_webserver.


Update api key param name, update edge-api-utils version

Purpose
Update edge-api-utils dependency version to fetch changes with updated api key param name - https://github.com/folio-org/edge-api-utils/pull/4
Approach
Update edge-api-utils version to 1.1.0-SNAPSHOT
Fix unit tests
Handle AuthorizationExceptio as 401 error
Pre-Merge Checklist:
Before merging this PR, please go through the following list and take appropriate actions.

Does this PR meet or exceed the expected quality standards?

[ ] Code coverage on new code is 80% or greater
[ ] Duplications on new code is 3% or less
[ ] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] Were any API paths or methods changed, added or removed?
[ ] Were there any schema changes?
[ ] Did any of the interface versions change?
[ ] Were permissions changed, added, or removed?
[ ] Are there new interface dependencies?
[ ] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

 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.Illia Borysenko seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

it would be great if the param name wasn't case-sensitive.


(question) double unwrapping query_selector

I have a question, what is a point of wrapping result of the query_selector into both result and option? I think it would be much nicer to have just one Result.

The outer Result is because the string you use for the selector might have a syntax error (because it's invalid).
The inner Option is because the element might not exist.
Because you usually use a string literal, you can guarantee that it doesn't have invalid syntax, so you can safely use .unwrap() for the outer Result. Though you have to be careful: new CSS syntax might work in a modern browser but fail in an older browser.
On the other hand, the inner Option usually needs to be handled, because in many cases you can't guarantee that the element will exist.

In general the pattern we use is Result<T, E> where T is the returned type as defined in the specs, and E is the exception the method can throw. And since the method can return null it returns Option<U> as T.

Ok i get it now, thanks.
I didn't see the explanation in the docs and the error is TODO.


Added solution param to convert

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

Comparison is base (ddea397) 23.61% compared to head (b5b2dc1) 0.00%.

:exclamation: Current head b5b2dc1 differs from pull request most recent head 1265a0d. Consider uploading reports for the commit 1265a0d to get more accurate results

Files
Patch %
Lines

urnc/convert.py
0.00%
84 Missing :warning:

urnc/util.py
0.00%
60 Missing :warning:

urnc/ci.py
0.00%
26 Missing :warning:

urnc/preprocessor/add_tags.py
0.00%
6 Missing :warning:

urnc/main.py
0.00%
4 Missing :warning:

urnc/version.py
0.00%
2 Missing :warning:

urnc/edit.py
0.00%
1 Missing :warning:

urnc/preprocessor/util.py
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #26       +/-   ##
==========================================
- Coverage   23.61%   0.00%   -23.62%
==========================================
  Files          14      14
  Lines         864     938       +74
==========================================
- Hits          204       0      -204
- Misses        660     938      +278

Flag
Coverage Δ

unittests
0.00% <0.00%> (-23.62%)
: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.


Support BelongsToMany in HasRelationship

Support BelongsToMany relationships
(I had an error in a MultiSelectFilter, adding support for BelongsToMany fixed it)

Thanks


Abnormal memory consumption with 2.2.x and IBM WebSphere 8.5

OrientDB Version, operating system, or hardware.

v2.2.5

Operating System

[ ] Linux
[ ] MacOSX
[x] Windows
[ ] Other Unix
[ ] Other, name?

Expected behavior and actual behavior
I am using OrientDB in embedded distributed mode with only one node. Currently, the reason for using the distributed mode is to connect with plocal and remote concurrently.
In the Hazelcast config, I am using tcp/ip instead of multicast. All other config parameters are basically the default distributed config.
I am using a document database primarily through the Java Object API.
After upgrading from 2.1.6 to 2.2.5, I noticed that the memory usage of Java process corresponding to the WAS server containing my embedded app kept growing (which typically signifies a memory leak).
I generated a heap dump and analyzed it. The results looked "normal" but the heap size was just a fraction of the memory used by the Java process. I see that 2.2.x uses "direct memory" which, by deduction, must relate to the issue.
Have you done any testing with WebSphere? Do you have any idea of what might be causing the behavior?
For now, I downgraded to 2.1.20 which seems to cure the side-effects observed following the upgrade, including abnormal memory consumption.

I don't know how WebSphere counts the RAM, but I think this is not a problem as far as it's not heap. Did you experience any problem with 2.2?

@fredfortier, first of all, let's check that there is a  memory leak. What RAM size do you have, what is  your DB size and what was memory consumption when you noticed that memory was consumed more than you expected ?

I do not have experience with other Java EE applications using native memory instead of heap. I am only aware of memory analysis tools for heap dumps, not for the native memory.  Unfortunately, even if the observer behavior were considered normal, WebSphere administrators would take issue with an application using several times the memory figure allocated to heap.
I could see the memory grow on the Java process corresponding to the JVM in the Windows Task Manager, not using some WebSphere tools. I let the memory grow to 5GB before pulling the plug. The db usage volume was minimal although the few records affected were relatively large (~1MB). The database size was small (~2MB). I was basically adding, reading and deleting a single record. The heap size was 1024MB. The physical memory available on the server was approximately 5GB.
Now, I did open issue #6493 which could well be related. Since deleting a record results in error, I suppose that it could factor in that record being preserved in memory.

@fredfortier and that is completely reproducible, is not it ? I mean if I will install WebSphere and your app I will see the same result. Is it correct ?

No unfortunately, my app is not easily portable in that it is an extension to an "evolved" (aka bloated) IBM framework. You won't be able to use it as-is in isolation. I did attach my exact configuration to issue #6493.

Do not think that configuration will help. But may we create debug session to fix your issue when all participants will have free time slots ?

Yes, that could work. Please let me know when you guys are available. I am working during business hours on Eastern Standard Time.

Hi @fredfortier! We have time zone difference of 12 hours, so debugging session will be our last resort :)
Let's confirm the problem with the direct memory first. Could you please inspect the direct memory usage stats in VisualVM's JMX console as described here https://blogs.oracle.com/alanb/entry/monitoring_direct_buffers. You may need to install VisualVM's JMX plugin before that.
Also, if you don't mind, I may create a customised 2.2.x version with a detailed logging about direct memory allocations.

@fredfortier, do you have any updates? Could you please also inspect the com.orientechnologies.common.directmemory.OByteBufferPoolMXBean JMX bean? It provides information about OrienDB's direct memory allocations.

Leak detection was pushed to the 2.2.x branch, it will emit an error message to the log, if a leak is detected, the message is prefixed with the DIRECT-TRACK: string. You may build it from the 2.2.x branch or wait for 2.2.7 release, it will be there.

@fredfortier in order to switch on leak detection you need to provide follwoing system property -Dmemory.directMemory.trackMode=true

@taburet and @laa , I will try this as soon as I can.

Closing because no answer after a while. In case please reopen/comment this.


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
9766e6272d0acac2f2f35abb4b6b1c93a2994e3d
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Add movie Micro Men

[x ] I have carefully read and comply with the Contributing Guidelines of this repo.

[x ] I have searched the PRs of this repo and believe that this is not a duplicate.

Title: Micro Men

Link: https://www.imdb.com/title/tt1459467/

Genre: Biography, Drama

Rating: 7.6

Description: In 1979 Clive Sinclair, British inventor of the pocket calculator, frustrated by the lack of home investment in his project,the electric car, also opposes former assistant Chris Curry's belief that he can successfully market a micro-chip for a home computer. A parting of the ways sees Curry, in partnership with the Austrian Hermann Hauser and using whizz kid Cambridge students, set up his own, rival firm to Sinclair Radionics, Acorn. Acorn beat Sinclair to a lucrative contract supplying the BBC with machines for a computer series. From here on it is a battle for supremacy to gain the upper hand in the domestic market.

This sounds like a Pirates of Silicon Valley but for the British home computer market, I'd say it belongs here.


Link rot in RTL2832U tutorial page (2)

Affected page: GNSS-SDR operation with a Realtek RTL2832U USB dongle DVB-T receiver

Code: 2016-06-23-rtl2832U.md#L249

Description:

The RTL-SDR V3 datasheet is no longer available under the url:
https://www.rtl-sdr.com/wp-content/uploads/2017/06/RTL-SDR-Blog-V3-Datasheet.pdf
The resource can now be found at:
https://www.rtl-sdr.com/wp-content/uploads/2018/02/RTL-SDR-Blog-V3-Datasheet.pdf

Fixed, thanks


typeText do not work no android on react native 0.72.5

What happened?
When call typeText method, the app do not apply on input the provided text, however on iOS it works fine.
What was the expected behaviour?
text been prompt on input.
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 20.12.1
React Native version: 0.72.5
Has Fabric (React Native's new rendering system) enabled: no
Node version:  v16.18.1
Device model:  Pixel_3a_API_33_arm64-v8a
Android version: 33
Test-runner (select one): jest
Detox logs
Detox logs
13:17:01.436 detox[2255] B lifecycle node_modules/.bin/detox test --configuration android.emu.release --loglevel trace
  data: {
    "id": "20365f17-2028-eb11-f635-d13a7dded485",
    "detoxConfig": {
      "configurationName": "android.emu.release",
      "apps": {
        "default": {
          "type": "android.apk",
          "binaryPath": "android/app/build/outputs/apk/release/app-release.apk",
          "build": "cd android && ./gradlew assembleRelease assembleAndroidTest -DtestBuildType=release"
        }
      },
      "artifacts": {
        "rootDir": "artifacts/android.emu.release.2023-10-03 16-17-01Z",
        "plugins": {
          "log": {
            "enabled": false,
            "keepOnlyFailedTestsArtifacts": false
          },
          "screenshot": {
            "enabled": true,
            "shouldTakeAutomaticSnapshots": false,
            "keepOnlyFailedTestsArtifacts": false
          },
          "video": {
            "enabled": false,
            "keepOnlyFailedTestsArtifacts": false
          },
          "instruments": {
            "enabled": false,
            "keepOnlyFailedTestsArtifacts": false
          },
          "uiHierarchy": {
            "enabled": false,
            "keepOnlyFailedTestsArtifacts": false
          }
        }
      },
      "behavior": {
        "init": {
          "keepLockFile": false,
          "reinstallApp": true,
          "exposeGlobals": true
        },
        "cleanup": {
          "shutdownDevice": false
        },
        "launchApp": "auto"
      },
      "cli": {
        "configuration": "android.emu.release",
        "loglevel": "trace",
        "start": true
      },
      "device": {
        "type": "android.emulator",
        "device": {
          "avdName": "Pixel_3a_API_33_arm64-v8a"
        }
      },
      "logger": {
        "level": "trace",
        "overrideConsole": true,
        "options": {
          "showLoggerName": true,
          "showPid": true,
          "showLevel": false,
          "showMetadata": false,
          "basepath": "/Users/breno.gomes/Desktop/git-novo/adv-mobile-app/node_modules/detox/src",
          "prefixers": {},
          "stringifiers": {}
        }
      },
      "testRunner": {
        "retries": 0,
        "forwardEnv": false,
        "bail": false,
        "jest": {
          "setupTimeout": 120000,
          "teardownTimeout": 30000,
          "retryAfterCircusRetries": false,
          "reportWorkerAssign": true
        },
        "args": {
          "$0": "jest",
          "_": [],
          "config": "e2e/jest.config.js",
          "--": []
        }
      },
      "session": {
        "autoStart": true,
        "debugSynchronization": 10000
      }
    },
    "detoxIPCServer": "primary-2255",
    "testResults": [],
    "testSessionIndex": 0,
    "workersCount": 0
  }
13:17:01.440 detox[2255] i ipc Server path not specified, so defaulting to ipc.config.socketRoot + ipc.config.appspace + ipc.config.id /tmp/detox.primary-2255
13:17:01.441 detox[2255] i ipc starting server on  /tmp/detox.primary-2255
13:17:01.441 detox[2255] i ipc starting TLS server false
13:17:01.441 detox[2255] i ipc starting server as Unix || Windows Socket
13:17:01.444 detox[2255] i ws-server Detox server listening on localhost:58441...
13:17:01.447 detox[2255] i lifecycle Serialized the session state at: /private/var/folders/jk/r6mqvhr13dj1f6f5rjyg73jw0000gp/T/20365f17-2028-eb11-f635-d13a7dded485.detox.json
13:17:01.448 detox[2255] B lifecycle jest --config e2e/jest.config.js
watchman warning:  Recrawled this watch 77 times, most recently because:
MustScanSubDirs UserDroppedTo resolve, please review the information on
https://facebook.github.io/watchman/docs/troubleshooting.html#recrawl
To clear this warning, run:
`watchman watch-del '/Users/breno.gomes/Desktop/git-novo/adv-mobile-app' ; watchman watch-project '/Users/breno.gomes/Desktop/git-novo/adv-mobile-app'`

Determining test suites to run...13:17:01.858 detox[2256] i ipc Service path not specified, so defaulting to ipc.config.socketRoot + ipc.config.appspace + id
13:17:01.859 detox[2256] i ipc requested connection to  primary-2255 /tmp/detox.primary-2255
13:17:01.859 detox[2256] i ipc Connecting client on Unix Socket : /tmp/detox.primary-2255
13:17:01.860 detox[2255] i ipc ## socket connection to server detected ##
13:17:01.861 detox[2256] i ipc retrying reset
13:17:01.862 detox[2256] i ipc dispatching event to  primary-2255 /tmp/detox.primary-2255  :  registerContext , { id: 'secondary-2256' }
13:17:01.863 detox[2255] i ipc received event of :  registerContext { id: 'secondary-2256' }
13:17:01.864 detox[2255] i ipc dispatching event to socket  :  registerContextDone { testResults: [], testSessionIndex: 0 }
13:17:01.864 detox[2256] i ipc ## received events ##
13:17:01.864 detox[2256] i ipc detected event registerContextDone { testResults: [], testSessionIndex: 0 }
13:17:01.895 detox[2256] B lifecycle e2e/E2E.test.js
13:17:01.903 detox[2256] B lifecycle set up environment
13:17:01.904 detox[2256] i ipc dispatching event to  primary-2255 /tmp/detox.primary-2255  :  registerWorker , { workerId: 'w1' }

 RUNS  e2e/E2E.test.js
13:17:50.477 detox[2255] i ws-server@58519 send
  data: {
    "type": "invoke",
    "params": {
      "target": {
        "type": "Class",
        "value": "com.wix.detox.espresso.DetoxAssertion"
      },
      "method": "assertMatcher",
      "args": [
        {
          "type": "Invocation",
          "value": {
            "target": {
              "type": "Class",
              "value": "androidx.test.espresso.Espresso"
            },
            "method": "onView",
            "args": [
              {
                "type": "Invocation",
                "value": {
                  "target": {
                    "type": "Class",
                    "value": "com.wix.detox.espresso.DetoxMatcher"
                  },
                  "method": "matcherForText",
                  "args": [
                    "Calendário",
                    {
                      "type": "boolean",
                      "value": false
                    }
                  ]
                }
              }
            ]
          }
        },
        {
          "type": "Invocation",
          "value": {
            "target": {
              "type": "Class",
              "value": "com.wix.detox.espresso.DetoxMatcher"
            },
            "method": "matcherForSufficientlyVisible",
            "args": [
              {
                "type": "Integer",
                "value": 75
              }
            ]
          }
        }
      ]
    },
    "messageId": 14
  }
13:17:50.494 detox[2255] i ws-server@58519 get
  data: {"messageId":14,"type":"testFailed","params":{"details":"'(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.\nExpected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)\n     Got: was null\n"}}
13:17:50.495 detox[2255] i ws-server@58442 send
  data: {
    "messageId": 14,
    "type": "testFailed",
    "params": {
      "details": "'(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.\nExpected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)\n     Got: was null\n"
13:17:50.495 detox[2256] i ws-client get message
  data: {"messageId":14,"type":"testFailed","params":{"details":"'(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.\nExpected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)\n     Got: was null\n"}}

13:17:50.495 detox[2256] E ws-client expect element to be visible
  error: Test Failed: '(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.
  Expected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)
       Got: was null

13:17:50.496 detox[2256] B artifacts-manager onTestFnFailure
  args: ({"error":{"name":"DetoxRuntimeError"}})
13:17:50.496 detox[2256] E artifacts-manager onTestFnFailure
13:17:50.496 detox[2256] E lifecycle test_fn
  error: Test Failed: '(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.
  Expected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)
       Got: was null

13:17:50.497 detox[2256] B artifacts-manager onTestDone
  args: ({"title":"Abre o app na home, logado com as credenciais","fullName":"Home Abre o app na home, logado com as credenciais","status":"failed","invocations":1,"timedOut":false})
13:17:50.497 detox[2256] E artifacts-manager onTestDone
13:17:50.497 detox[2256] E lifecycle Abre o app na home, logado com as credenciais
13:17:50.497 detox[2256] i lifecycle Home: Abre o app na home, logado com as credenciais [FAIL]
13:17:50.497 detox[2256] B artifacts-manager onRunDescribeFinish
  args: ({"name":"Home"})
13:17:50.498 detox[2256] E artifacts-manager onRunDescribeFinish
13:17:50.498 detox[2256] E lifecycle Home

13:17:50.498 detox[2256] B artifacts-manager onRunDescribeFinish
  args: ({"name":"ROOT_DESCRIBE_BLOCK"})
13:17:50.498 detox[2256] E artifacts-manager onRunDescribeFinish
13:17:50.498 detox[2256] E lifecycle run the tests
13:17:50.520 detox[2256] B lifecycle tear down environment
13:17:50.520 detox[2256] B artifacts-manager onBeforeCleanup
  args: ()
13:17:50.520 detox[2256] E artifacts-manager onBeforeCleanup
13:17:50.521 detox[2256] i ws-client send message
  data: {"type":"cleanup","params":{"stopRunner":false},"messageId":-49642}

 RUNS  e2e/E2E.test.js
13:17:50.521 detox[2255] i ws-server@58442 get
  data: {"type":"cleanup","params":{"stopRunner":false},"messageId":-49642}
13:17:50.522 detox[2255] i ws-server@58519 send
  data: {
    "type": "cleanup",
    "params": {
      "stopRunner": false
    },
    "messageId": -49642
  }
13:17:50.523 detox[2255] i ws-server@58519 get
  data: {"messageId":-49642,"type":"cleanupDone","params":{}}
13:17:50.523 detox[2255] i ws-server@58442 send
  data: {
    "messageId": -49642,
    "type": "cleanupDone",
13:17:50.523 detox[2256] i ws-client get message
  data: {"messageId":-49642,"type":"cleanupDone","params":{}}

 RUNS  e2e/E2E.test.js
13:17:50.525 detox[2255] i ws-server tester exited session 1d713e11-daa1-f111-5b8d-2431dee5b19f
13:17:50.525 detox[2255] i ws-server@58519 send
  data: {
    "type": "testerDisconnected",
    "messageId": -1
13:17:50.526 detox[2256] i child-process:SPAWN_KILL sending SIGINT to: /Users/breno.gomes/Library/Android/sdk/platform-tools/adb -s emulator-12270 shell am instrument -w -r -e detoxServer ws://localhost:58441 -e detoxSessionId 1d713e11-daa1-f111-5b8d-2431dee5b19f -e debug false br.com.softplan.sajadv.test/androidx.test.runner.AndroidJUnitRunner
13:17:50.527 detox[2256] i child-process:SPAWN_END /Users/breno.gomes/Library/Android/sdk/platform-tools/adb -s emulator-12270 shell am instrument -w -r -e detoxServer ws://localhost:58441 -e detoxSessionId 1d713e11-daa1-f111-5b8d-2431dee5b19f -e debug false br.com.softplan.sajadv.test/androidx.test.runner.AndroidJUnitRunner terminated with SIGINT
13:17:50.527 detox[2256] i child-process:EXEC_CMD "/Users/breno.gomes/Library/Android/sdk/platform-tools/adb" -s emulator-12270 reverse --remove tcp:58441
13:17:50.532 detox[2256] B device free
  args: ({"adbName":"emulator-12270"}, {"shutdown":false})
13:17:50.533 detox[2256] E device free
13:17:50.534 detox[2256] E lifecycle tear down environment
13:17:50.534 detox[2256] E lifecycle e2e/E2E.test.js
 FAIL  e2e/E2E.test.js (48.623 s)
  Autenticação
    ✓ Inicia na tela de login (24819 ms)
    ✕ Realiza o login com multiplos domínios (6221 ms)
    ✕ Apresenta o formuário de satisfação (8104 ms)
  Home
    ✕ Abre o app na home, logado com as credenciais (4026 ms)

  ● Autenticação › Realiza o login com multiplos domínios

    Test Failed: '(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.
    Expected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)
         Got: was null

      41 |     // espera buscar os domínios
      42 |     await new Promise(r => setTimeout(r, 3000));
    > 43 |     await expect(element(by.id('domain.1'))).toBeVisible();
         |                                              ^
      44 |
      45 |     await element(by.id('domain.1')).tap();
      46 |     await expect(element(by.id('dialog-login-button'))).toBeVisible();

      at Object.toBeVisible (e2e/E2E.test.js:43:46)
      at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
      at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)

  ● Autenticação › Apresenta o formuário de satisfação

    Test Failed: '(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.
    Expected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)
         Got: was null

      54 |     await device.reloadReactNative();
      55 |     await new Promise(r => setTimeout(r, 8000));
    > 56 |     await expect(element(by.id('respond-later-button'))).toBeVisible();
         |                                                          ^
      57 |     await element(by.id('respond-later-button')).tap();
      58 |     await expect(element(by.text('Calendário'))).toBeVisible();
      59 |   });

      at Object.toBeVisible (e2e/E2E.test.js:56:58)
      at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
      at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)

  ● Home › Abre o app na home, logado com as credenciais

    Test Failed: '(view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)' doesn't match the selected view.
    Expected: (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() covers at least <75> percent of the view's area)
         Got: was null

      68 |     // await device.enableSynchronization();
      69 |     await new Promise(r => setTimeout(r, 4000));
    > 70 |     await expect(element(by.text('Calendário'))).toBeVisible();
         |                                                  ^
      71 |   });
      72 | });
      73 |

      at Object.toBeVisible (e2e/E2E.test.js:70:50)
      at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
      at _next (node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)

13:17:50.538 detox[2256] i ipc dispatching event to  primary-2255 /tmp/detox.primary-2255  :  reportTestResults , {
  testResults: [
    {
      success: false,
      testFilePath: '/Users/breno.gomes/Desktop/git-novo/adv-mobile-app/e2e/E2E.test.js',
      testExecError: undefined,
      isPermanentFailure: false
    }
  ]
}
13:17:50.538 detox[2255] i ipc received event of :  reportTestResults {
  testResults: [
    {
      success: false,
      testFilePath: '/Users/breno.gomes/Desktop/git-novo/adv-mobile-app/e2e/E2E.test.js',
      isPermanentFailure: false
    }
  ]
}
13:17:50.539 detox[2255] i ipc dispatching event to socket  :  reportTestResultsDone {
  testResults: [
    {
      success: false,
      testFilePath: '/Users/breno.gomes/Desktop/git-novo/adv-mobile-app/e2e/E2E.test.js',
      isPermanentFailure: false
    }
  ]
}
13:17:50.539 detox[2255] i ipc broadcasting event to all known sockets listening to  /tmp/detox.primary-2255  :   sessionStateUpdate {
  testResults: [
    {
      success: false,
      testFilePath: '/Users/breno.gomes/Desktop/git-novo/adv-mobile-app/e2e/E2E.test.js',
      isPermanentFailure: false
    }
  ]
}
13:17:50.539 detox[2256] i ipc ## received events ##
13:17:50.539 detox[2256] i ipc detected event reportTestResultsDone {
  testResults: [
    {
      success: false,
      testFilePath: '/Users/breno.gomes/Desktop/git-novo/adv-mobile-app/e2e/E2E.test.js',
      isPermanentFailure: false
    }
  ]
}
13:17:50.540 detox[2256] i ipc connection closed primary-2255 /tmp/detox.primary-2255 0 tries remaining of 0
13:17:50.540 detox[2256] i ipc secondary-2256 exceeded connection rety amount of  or stopRetrying flag set.
13:17:50.541 detox[2255] i ipc socket disconnected secondary-2256
13:17:50.546 detox[2256] i child-process:EXEC_SUCCESS
13:17:50.641 detox[2255] E lifecycle Command failed with exit code = 1:
jest --config e2e/jest.config.js
13:17:50.642 detox[2255] i ws-server Detox server has been closed gracefully
13:17:50.643 detox[2255] i ws-server app exited session 1d713e11-daa1-f111-5b8d-2431dee5b19f
13:17:50.643 detox[2255] E ws-server@58519 connection :58441<->:58519
13:17:50.643 detox[2255] E lifecycle node_modules/.bin/detox test --configuration android.emu.release --loglevel trace
breno.gomes@SOFT009051 adv-mobile-app %

Device logs
Device logs
paste your device.log here!

More data, please!
No response

Hi @gomesbreno, this is most likely linked to https://github.com/wix/Detox/issues/3762.

I can confirm this happens for me on API 33 & 34. Even with the latest patch for<EMAIL_ADDRESS>My only option has been to downgrade to API 32, which also has an issue of really slow keyboard entry.
Is anyone else experiencing this?

typeText is really slow on Android. Once done, I also see s_glBindAttribLocation: bind attrib 0 name position which I have no idea how to resolve. Also, once typing is done, the test doesn't proceed and shows The app is busy with the following tasks: • 1 network requests with URLs in the log.

I also get this in a test: s_glBindAttribLocation: bind attrib 0 name position
s_glBindAttribLocation: bind attrib 1 name color
s_glBindAttribLocation: bind attrib 2 name localCoor

same to me
RN : 0.72.3
detox : 20.21.0

Also experiencing this
RN: 0.74.5
Detox: 20.25.2

typeText is really slow on Android. Once done, I also see s_glBindAttribLocation: bind attrib 0 name position which I have no idea how to resolve. Also, once typing is done, the test doesn't proceed and shows The app is busy with the following tasks: • 1 network requests with URLs in the log.

Probably because Android is doing all kinds of AI/ML stuff for every text input typing.


Update Dismiss screen

Added a sentence in the Dismiss alert screen.
Should be merged only when approved by partners.
Reference in Figma
Trello card

@timarney updated the PR based on HC's comments; this can be reviewed + merged now please!

Great thanks I'll run the scripts tp generate the translation file now.


RSDK-7749: Add SetRPM to flutter SDK

blocked by API changes that should be merged later today
all tests passing with local API changes

api changes are merged, ran make format, analyze, and test locally everything passes, so I just changed the comparison branch to the automatic workflows one

api changes are merged...

although it doesn't seem to be recognizing the new api changes... unsure why


Movie Search Not Case-Insensitive

Currently, the movie search functionality is case-sensitive, which impacts search accuracy and user experience. For example, searching for "star wars", "Star Wars", and "STAR WARS" produces different results.
Expected Behavior:

Search should be case-insensitive
"Star Wars", "star wars", and "STAR WARS" should all return the same results

Closing issue with this commit bfaeab3.


build: simplify handling for static variants (NFC)

There is no need to special case the products for the static build.
This handles libdispatch_static and foundation_static more
generically.

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

Resolves SR-NNNN.

CC: @spevans

@swift-ci please test

@swift-ci please build toolchain

macOS Toolchain
Download Toolchain
Git Sha -<PHONE_NUMBER>6ce5b8b86db976879b519fecf68b2a
Install command
tar -zxf  swift-PR-28960-458-osx.tar.gz --directory ~/

Build failed
Swift Test Linux Platform
Git Sha -<PHONE_NUMBER>6ce5b8b86db976879b519fecf68b2a


Check barcodes

Even though many of the samples are already separated by barcode we should validate that all samples have a valid barcode within a certain margin of error (1 nt difference).

Implemented in split_samples now.


Improve project type detection

This removes the type selection dropdown, and shows the correct layout when the page is refreshed.
closes #1331

cc: @galeyang


Add mention badge to the sidebar and configure it to change color depending on theme.

Add the mention badge to the SideBar.js component and ensure it receives the proper props to change color in relation to the current theme.

@yutingcxiang Hey can I take this issue?

Of course, thanks for handling this!

@r4zorgeek Do you still want to work on this?


[FEAT]: Send email when the contact us form is submitted

@abhay-raj19  I'm going to implement a feature to send an email whenever a user submits the contact us form. I'll be using Nodemailer to handle the email functionality. Please assign me under gssoc so I can start working on it.

//Duplicate issue


Develop

Coverage remained the same at 86.581% when pulling 685c41ea20d597a5391840d2cc96f4a48cd9e628 on develop into b3cb5d2d70ed1c9441e56c263d5d05db5e6184b5 on qa.


Inner code option?

Is there any options to only apply higlighting to inner  blocks inside the string, instead of entire string?

not totally sure what you mean, can you explain more?

i don't think that's something this library will support, it would be possible to build a library on top of this that does this but will unlikely be part of the core lib. Thanks!


"Exception: type_prior contains negative values!" when running tc.tl.annotate()

Hello,
I tried to run tc.tl.annotate() and encountered this error:
`

tc.tl.annotate(puck,reference,'subtype',result_key='subtype',)                                                                     Starting preprocessing
Annotation profiles were not found in reference.varm["subtype"]. Constructing reference profiles with tacco.preprocessing.construct_reference_profiles and default arguments...
Finished preprocessing in 118.54 seconds.
Starting annotation of data with shape (173055, 2841) and a reference of shape (56131, 2841) using the following wrapped method:
+- platform normalization: platform_iterations=0, gene_keys=subtype, normalize_to=adata
+- multi center: multi_center=None multi_center_amplitudes=True
+- bisection boost: bisections=4, bisection_divisor=3
+- core: method=OT annotation_prior=None
mean,std( rescaling(gene) )  29.675947315286834<PHONE_NUMBER>199611
bisection run on 1
/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/utils/_dist.py:393: RuntimeWarning: invalid value encountered in sqrt
A = np.sqrt(A)
Traceback (most recent call last):
File "", line 1, in
File "/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/tools/_annotate.py", line 802, in annotate
cell_type = _method(tdata, reference, annotation_key, annotation_prior, verbose)
File "/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/tools/_annotate.py", line 328, in _method
cell_type = annotation_method(adata, reference, annotation_key, annotation_prior, verbose)
File "/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/tools/_annotate.py", line 381, in _method
cell_type = annotation_method(adata, reference, annotation_key, annotation_prior, verbose)
File "/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/tools/_annotate.py", line 208, in _method
cell_type = annotation_method(adata, reference, annotation_key, annotation_prior, verbose)
File "/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/tools/_annotate.py", line 115, in _method
cell_type = annotate(adata, reference, annotation_key, annotation_prior=_annotation_prior, **verbose_arg, **kw_args)
File "/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/tools/_OT.py", line 75, in _annotate_OT
cell_type = _run_OT(type_cell_dist, annotation_prior, cell_prior=cell_prior, epsilon=epsilon, lamb=lamb)
File "/USER/lizeyu/00.software/Miniconda3/envs/TACCO_env/lib/python3.10/site-packages/tacco/utils/_utils.py", line 247, in _run_OT
raise Exception('type_prior contains negative values!')
Exception: type_prior contains negative values!
`
Since i couldn't find an example data format. Could you give me a hint about was that because of and where my data format is wrong?

The puck and reference i used were like:

Hello,
by default tc.tl.annotate assumes to find counts (i.e. non-negative integer values) in .X of both reference and adata.
So my guess would be that the .X at least in reference contains negative values due to some preprocessing.
If the bare counts are still somewhere in reference (and adata) but not in .X, you can use the counts_location parameter of tc.tl.annotate to specify where to find them. https://simonwm.github.io/tacco/_autosummary/tacco.tools.annotate.html#tacco.tools.annotate
Hope this helps!

Great, thanks you!


A6000 XAVC 60p issue - Possible workaround, assistance requested

Problem: When using OpenMemories Tweak and recording at 60p in XAVC-S, the recording consistently fails at 3:28:33 (tested with two separate A6000 cameras). Resulting in a corrupted, unrecoverable video file.
Possible Workaround: The code in VideoActivity.java sets the maximum time limit at 13H 1M 00S (at least in V 0.10, I don't understand how V 0.11 works). If this could be changed to 3H 28M 30S the video would stop recording three seconds before the failure point, preserving the recorded video.
I could use some help, if anyone has the knowledge and a few minutes it would be extremely helpful and appreciated if one could provide a custom APK version of OpenMemories Tweak with the shorter time limit.
I installed Android Studio and attempted to make the change myself but something just isn't working and I can't figure out how to compile the APK file.

As a work around; the time limit is "just" stored as values within the config database, these can be change individually either by:
1). Enable WiFi and Telnet with 'tweak', telnet to the device and use the 'bk.elf' command.
2). Using https://github.com/ma1co/Sony-PMCA-RE, which now supports the 'bk r and bk w' commands directly in updatershell.
Unfortunately I don't remember which keys need to be changed, and a quick search failed me...

Try this in updatershell:
bk w 003c0373 03
bk w 003c0374 1c
bk w 003c0375 1e

You can then check inside the tweak app if the limit was set correctly.

Thank you for the information. I have given that a try even though I have limited experience coding and using command prompt. Here's what I did:
In OpenMemories Tweak, I navigated to the Developer tab and enabled WiFi and Telnet.
I connected the camera to my home WiFi.
On my PC I enabled Telnet in Control Panel, I opened command prompt and entered the "telnet" command.
Then I entered the "o" command and connected to the camera using the IP displayed in the OpenMemories app.
Once connected I get this message:
BusyBox v1.13.4 (2012-07-17 15:11:04 JST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ #

I attempted to enter the commands listed above and got this error message:
/ # bk w 003c0373 03
sh: bk: not found

I entered the "help" command and get this message:
Built-in commands:
-------------------
        . : [ alias bg break cd chdir continue echo eval exec exit export
        false fg hash help jobs kill let local pwd read readonly return
        set shift source test times trap true type ulimit umask unalias
        unset wait

I tried a few of the commands listed, the only one I tried that didn't throw an error was "set"
I entered the three commands as:
set bk w 003c0373 03
set bk w 003c0374 1c
set bk w 003c0375 1e

However, the time limit was still displayed in OpenMemories Tweak as 13h 01m 00s. I haven't yet tested the camera to see if it recording limit changed even though the displayed limit hasn't. I'm assuming if I did everything correctly the displayed limit would change. Any further guidance is greatly appreciated.

My instructions were for updatershell (run pmca-console updatershell while your camera is connected over USB). If you want to apply the changes over telnet, replace bk by bk.elf in my instructions.

Thank you very much. I was able to make the change via telnet to both of my A6000 cameras. I have tested one of them so far and the recording stopped at 3:28:30 with no issues, maintaining a fully working video file.
For anyone else who may want to alter the maximum recording time here is a step by step guide based on my experience:
Notes: 003c0373 = Hours, 003c0374 = Minutes, 003c0375 = Seconds. The two characters that follow are Hexadecimal numbers: 03 = 3, 1c = 28, 1e = 30. A decimal to hex converter can be used to find the hex equivalent for any time limit you want under the 13:15:21 theoretical limit described in the source code comments.
There are two ways to alter the maximum recording time; you can connect the camera to a wifi network using telnet or you can connect your camera via USB and use the updatershell function within the command line version of pcma, found here: https://github.com/ma1co/Sony-PMCA-RE/releases/tag/v0.17
If using the updatershell method the commands do not contain ".elf" and are as described by ma1co three comments above.
I used the telnet method, steps are as follows (Windows 10):
Prior to starting this procedure it is recommended you change the following setting on your camera:
Menu > Setup (toolbox icon) > submenu #2 > Pwr Save Start Time > Select: 30 Min
If not done, you may lose the connection after the camera screen dims.

On your PC open Control Panel
Find "Programs and Features"
Select "Turn Windows features on or off" on the top left side of the window
Scroll down to "Telnet Client," select the check box, and click OK (you may have to wait a minute while telnet is enabled)
Open Command Prompt
Type the command "telnet"
Turn on you camera
Navigate to the OpenMemories: Tweak app
Scroll right to the "Developer" tab
Select and turn on "Enable Wifi" and "Enable Telnet"
Scroll down to "Wifi settings"
Select "Access Point Set."
Select your home network (same network your PC is connected to)
Input password if required (press center button in scroll wheel to activate virtual keyboard), and select "OK"
In Command Prompt enter the command "o" (lowercase letter O)
In the Developer tab of OpenMemories: Tweak, under "Enable Wifi" there should be an IP address visible, enter the IP address into Command Prompt and press Enter
Command Prompt should now be connected to the camera.
Enter the each of the following three commands separately (press enter after each command is typed):

bk.elf w 003c0373 03
bk.elf w 003c0374 1c
bk.elf w 003c0375 1e

In OpenMemories: Tweak, navigate to the "Video" tab and check that the time limit under "Disable video recording limit" has changed. The check box will no longer be checked. If you attempt to check the box it will reset the limit to 13:01:00 and subsequently unchecking the box will set it back to 29:50. You will have to repeat the process if you check the box. If left untouched, the limit you set via telnet will be retained even if you turn the camera off, remove the battery, or reformat you SD card.
Once completed, you can close Command Prompt and disable telnet on you PC as well as turn off "Enable Wifi" and "Enable Telnet" in the Developer tab of OpenMemories: Tweak.


Cloudformation Spec vs Documentation

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-distribution-distributionconfig.html#cfn-cloudfront-distribution-distributionconfig-defaultcachebehavior
CloudFormation Spec has this value as not required but the documentation has it as required.  Which one is it and where does the fix go?

I've alerted the service team of the issues with the resource spec.  Reclassified as a big and will leave open until the internal ticket is closed.

This may be a similar issue (I'm not sure how to check the spec):
I have a custom resource
AppServiceDesiredCountRolloverResource:
    Type: "Custom::EcsServiceSizeRollover"
    Version: "1.0"
    Properties:
      ClusterName: !Ref ECSCluster
      .....

Which gets Invalid resource attribute Version for resource AppServiceDesiredCountRolloverResource
The docs for custom resources list a "Version": "1.0" top-level attribute on custom resource definitions.

This one is perhaps a different case. For Lambda functions, the Cfn docs and spec say the memory limit is 1536, but the Lambda docs and reality say the limit is 3008 (CloudFormation accepts templates with a value of 3008).

@farski the Version is on us.  I will work to fix that.  Sorry about that.
What error are you getting for the Lambda one?  We should have updated our check to 3008.
https://github.com/awslabs/cfn-python-lint/blob/master/src/cfnlint/rules/resources/lmbd/FunctionMemorySize.py#L41  Accidentally used the CloudFormation docs the first time as you had mentioned but it should be fixed now.
but the other qualifier is it be a multiple of 64 which we also test for.

@kddejong You must specify a value that is greater than or equal to 128, and it must be a multiple of 64. You cannot specify a size larger than 1536. The default value is 128 MB at 3008
(for  MemorySize: 3008)

Yup, that's definitely an old version of the linter.  You can find that exact message here, with the higher max value, in the code:
https://github.com/awslabs/cfn-python-lint/blob/779ccc8c2430dc9091012255aacd2d74af873380/src/cfnlint/rules/resources/lmbd/FunctionMemorySize.py#L28
You may need to do a pip install cfn-lint --upgrade and make sure you're running v.0.2.0 or 0.2.1.

@farski https://github.com/awsdocs/aws-cloudformation-user-guide/pull/68/ also I have submitted and now need to rebase that pull request.

Ok, just merged the "version" piece.  You can build from code to get both fixes now, or wait until the next version to upgrade via pip.

@cmmeyer Hm, I'll dig into this some more because when I upgrade I get Requirement already up-to-date: cfn-lint in /usr/local/lib/python3.6/site-packages (0.2.1). I only first installed this two days ago.

This is interesting -- that says python3.6, but your error on the VS code side was 2.7.  I wonder if there are some pip shenanigans going on here?
I noticed pip3 was having trouble upgrading me from 0.1.0 to 0.2.1 -- I did a bunch of pip3 uninstall cfn-lint and pip3 install cfn-lint without getting a new version.
I would try to clean up all current versions on your machine (pip2 uninstall cfn-lint and/or pip3 uninstall cfn-lint) then pip3 install cfn-lint --no-cache --upgrade and see if you get a nice, clean install with the higher memory cap.


Do not write empty lines

This PR removes those annoying empty lines that get written into your html src file.
Example:
BEFORE
<!-- injector:cssvendor -->
    <link rel="stylesheet" href="bower_components/font-awesome/css/font-awesome.css">
   ...empty line here...
   ...empty line here...
   ...empty line here...
<!-- endinjector -->

AFTER
<!-- injector:cssvendor -->
    <link rel="stylesheet" href="bower_components/font-awesome/css/font-awesome.css">
<!-- endinjector -->

Thanks for the PR, i'd happily merge it if you provide a unit test :)

@dehru thanks for the PR ! Please update the readme to tell user empty files won't be included. :)

OK.  Memory is coming back to me on this ;-).  What this PR does is fix empty spaces that appear in the links section of the header in my index.html file.  What appears to be happening is wiredep is giving grunt injector a list of bower dependencies.  Usually not all of the dependencies have both css AND javascript.  And it's usually that there are fewer css files.  So what injector was doing was leaving an empty space in the index.html file where a dependency did not have an associated css file.
So you get like 10 lines of javascript injected, and you also get 10 lines of css injected, but 8 of those lines would just be empty lines.  So without this fix my header would look like this:
<!-- injector:cssvendor -->
<link rel="stylesheet" href="bower_components/emc-ui/release/styles/emc-ui-bootstrap.min.css">
<link rel="stylesheet" href="bower_components/angular-loading-bar/build/loading-bar.css">

<!-- endinjector -->

But with this fix my links section looks nice and neat.
<!-- injector:cssvendor -->
<link rel="stylesheet" href="bower_components/emc-ui/release/styles/emc-ui-bootstrap.min.css">
<link rel="stylesheet" href="bower_components/angular-loading-bar/build/loading-bar.css">
<!-- endinjector -->

So I don't think there's a need for a readme comment on this, it's just improving the output that gets injected into index.html.  And helping my OCD related to empty spaces that injector was leaving in my perfectly crafted html ;-)

Woot!  I figured out the testing mechanism and added a test to verify that bower dependencies that do not have css files do not leave empty lines in the html file.  And all other tests are still passing...so I didn't break anything.  BTW, we've been using this fork for a lot of development and haven't seen an issue either.

Great :) Thanks for your feedback and unit test.


Entity has four key properties used in multiple relationships.

I have an Oracle DB and would like to create an entity. The entity is on the 1 side of multiple 1-to-many relationships.
E.g. I would like Relationship A to use 1 and 3 and Relationship B to 2, 3 & 4.
Is this possible?
Daniel

In general, yes. But you'd need to validate your exact scenario.


DropDown using vs-trigger-click need a way to close the dropdown.

I am using a DropDown component and would like to use the vs-trigger-click as it is much more mobile friendly to use clicks over hovers. It works fine for showing the menu but I'm not able to figure out a way to close the menu once it is open if I use that feature.

I fixed this with a pull request https://github.com/lusaxweb/vuesax/pull/128


fix: findings enigma audit

Description
Fix the findings from Enigma Dark audit (see ref in)
Limitations & risks
Introducing new vulnerabilities or missing some existing ones
Check-list

[ ] Tests are covering the new feature
[x] Code is natspec'd
[x] Code is linted and formatted
[x] I have run the test locally (and they pass)
[x] I have rebased to the latest main commit (and tests still pass)

Interactions
These changes will impact the following contracts:

Directly:
Hooki

Indirectly:
/

@drgorillamd can we get this out of draft? should we be trying to get test CI to pass?


Nested resources 404'ing when 3 deep using MySQL.

So, strange issue I’m having with nested resources in 5.1, I have a route defined as groups.feeds.images with route model binding for groups, feeds and images. Now locally, using sqlite and the built in artisan serve, if I hit {url}/groups/1/feeds/1/images/1 I get the resource I am after, but on our production server running ngix and mysql, we get a resource not found. Now this only seems to happen with nested resources that are more than 2 deep, {url}/groups/1/feeds/1 works fine, so does {url}/groups/1/feeds/1/images/.
Both the local and the remote databases share the same data and the id's being used exist in the relative tables.

Please ask on the forums.


Return proper json from /channels resource

damn the contract test are in a very bad shape when it comes to flake8. I've disabled the most annoying checks and fixed everything else I could.
Related: #482

Hmmm, yes - I did not fix what did not bother me at that point. Let me know what I can help with to clean up my mess.


Spring feign-reactor-cloud2 timeout

Hi everyone,
We are using the Spring cloud module through feign-reactor-cloud2 + spring-cloud-starter-circuitbreaker-reactor-resilience4j (Ribbon and Hystrix are disabled) and everything works fine except for the timeout configurations. Could someone provide me with an example with the proper way to override the default 1s read timeout per Feign client?
Thanks

Hi. There are two places for timeout configuration - http client and circuitbreaker:
Regarding Resilience4j:
Global customization
Specific feign client customization

If you want configure feign client manually

Thanh you! @kptfh
Works like a charm!

Thanks, your solution is great.

Thanks so much!! We have been using your library since its early release and now are doing some major refactoring and moving to the newest feign-reactor-cloud2.  Your library should be included as part of the Spring Cloud project.
CC: @spencergibb, @ryanjbaxter

@howardem  https://github.com/spring-cloud/spring-cloud-openfeign/issues/4#issuecomment-585875126


How can we bring the ASKotec to even more use

what do you have in mind?

mobilise refugee youths and instil repair skills in them
these will cut on the cost of hiring experts during community repair cafe.
community repair cafe alone doesn't have much effect on the community, more effect when we have train them and organise community repair cafe's as their interneurship.

That's my thought

Having an established repair Café center would put the #ASKotec to more use since there will be everyday use of it.


Extend git plugin to allow breaking path pre- and post- git repo root

It would be cool if it was possible to display paths like fish does:

Top is pshazz (theme agnoster-alternate), bottom is fish. The git root is in the iTerm2-Color-Schemes folder, and I am currently in the terminal subfolder. You can see that fish shows git info at git root, also treating path before/after repo root differently (in this case abbreviating the path before repo root just to single letters).
I believe this could be achieved by hardcoding git rev-parse --show-toplevel in the theme to get the repo root path (and determine the "rest" from full path), but a cleaner and faster solution would be to get direct support from the git plugin.

Sounds good to me. I've added labels and see if anyone wants to implement it.

On another thought, the split would be better in three parts: path before, repo folder name, and path after. That way themes could easily theme the repo name differently (it has lighter color in my screenshot, for example).

@h404bi I was able to replicate the fish behavior:

...using some really ugly code:
{
    "plugins": [ "git", "ssh", "z" ],
    "prompt": [
        [ "", "", "$($global:g=$git_branch.Length; If($global:g) { $global:path_git_root=((git rev-parse --show-toplevel) -replace '/','\\'); $path_real=($path -replace '^~',$home); $global:path_git_rest=($path_real -replace ('^'+[Regex]::Escape($global:path_git_root)),'') -replace '^\\\\',''; $global:path_git_root_split=($global:path_git_root -replace '\\\\([^\\\\]+)$','|$1').Split('|'); })"],
        [ "darkblue", "gray", " ${user}@${hostname}" ],
        [ "gray", "darkblue", "${rightarrow}" ],
        [ "white", "darkblue", " $( If($global:g) { ($global:path_git_root_split[0] -replace '\\\\([^\\\\])[^\\\\]+','\\$1') + '\\' + $global:path_git_root_split[1] } Else { $path } ) " ],
        [ "darkblue", "black", "$( If(!$global:g) { $rightarrow } )" ],
        [ "darkblue", "darkyellow", "$( If($global:g) { $rightarrow} )" ],
        [ "white", "darkyellow", "$(If($global:g) { ' ' + ([text.encoding]::utf8.getstring((238,130,160)) + ' ' + (($git_branch + ' ') -replace '^master $','') + $git_local_state + $git_remote_state).Trim() + ' ' })" ],
        [ "darkyellow", "black", "$(If($global:g -and !$global:path_git_rest.Length) { $rightarrow })" ],
        [ "darkyellow", "darkblue", "$(If($global:g -and $global:path_git_rest.Length) { $rightarrow })" ],
        [ "white", "darkblue", "$(If($global:g -and $global:path_git_rest.Length) { ' ' + $global:path_git_rest + ' ' })" ],
        [ "darkblue", "black", "$(If($global:g -and $global:path_git_rest.Length) { $rightarrow })" ],
        [ "", "", " `n`" ]
    ],
    "git": {
        "prompt_unstaged": "*",
        "prompt_staged": "~",
        "prompt_stash": "$",
        "prompt_untracked": "…",
        "prompt_remote_push": "+",
        "prompt_remote_pull": "-",
        "prompt_remote_same": " "
    }
}

@h404bi @lukesampson What are your thoughts on this approach? Does it deserve support in the Git plugin? Three variables are needed: path before current repo root, repo root folder name, rest of path after repo root folder. It seems functional so far and mimics the bobthefish behavior quite well.


SArray should have an implementation of median

A approx/exact median is very useful for SArrays
sa.median(approx = False) # default
sa.median(approx = True)  # uses the sketch summary to compute the median

I like this idea. It's pretty simple to do efficiently at the Python layer. As a proof of concept, the following works:
def median(sa, approx = False):
    if not approx:
        temp = tc.SFrame({'x': sa})
        temp['dummy'] = 1
        result = temp.groupby('dummy', {'y': tc.aggregate.QUANTILE('x', 0.5)})
        return result['y'][0][0]
    else:
        sketch_summary = tc.Sketch(sa)
        return sketch_summary.quantile(.5)

@TobyRoseman We should do exactly that in the C++ layer :). I think the code is just as easy and we can also put it in the C-APIs.

The code I shared previously is not going to work when approx = False. It turns out we can not use tc.aggregate.QUANTILE if we want exact answers.
The docstring for tc.aggregate.QUANTILE contains this surprising information:
The returned quantiles are guaranteed to have 0.5% accuracy. That is to say,
if the requested quantile is 0.50, the resultant quantile value may be
between 0.495 and 0.505 of the true quantile.

Let's use the sketch for getting the exact method by using the bound guarantees of the sketch.  Because it guarantees the value to be within eps * N of the original value, we set eps based on memory (it's pretty conservative, so that can be set small), then get the quantiles of the data at (0.5 - eps) *N and (0.5 + eps) *N.  Call these values a and b.  We then know that the true median lies between a and b.
Then, we do a second pass on the data using an apply:
atomic<size_t> n_below_a = 0;
std::vector<flexible_type> candidates;  // could be replaced with internal lock free stack.
std::mutex candidate_lock;

auto count_median = [&](flexible_type x) {
   if(x < a) { ++n_below_a; }
   else if(x <= b) {
      std::lock_guard<std::mutex> lg(candidate_lock);
      candidates.push_back(x);
   }
});
data.apply(count_median);   // May be reduce_with_lambda or something like that.

Now, what's the 50% mark?
size_t inner_n = (data.size() / 2 - n_below_a);   // do even-vs-odd etc.
// Linear time partition
std::nth_element(candidates.begin(), candidates.begin() + inner_n, candidates.end());
// median is now at inner_n
return candidates[inner_n];


swift: add Foundation import

Xcode 10.3 complains that this file uses @objc without importing Foundation.

Merging, Kotlin flake


Strikethrough on a string with only spaces does not get colored

Strikethrough with only spaces:

Strikethrough with a letter prefix:

Currently impossible to make horizontal bars colored currently unless a non-space character is in the string.

Wrong repo. Also a duplicate of https://github.com/KyoriPowered/adventure-webui/issues/117.


[WIP] feat: welcome page

In this PR
Make the "welcome" page at #/welcome available by clicking the IPFS cube logo in the navbar, and adjust details for continuity.
Done

Make connection icon in top right of screen go to status page (not welcome page) with "Advanced" section expanded, and recolor as red (not orange) if not connected to IPFS API
Update files screen when there are no files:

Remove WelcomeInfo box as it didn't really make sense there and added clutter
As a result, remove info-boxes/welcome-info and add its contents to WelcomePage.js; move welcomeInfo i18n text into welcome.json
Update outdated reference to "Add files" button in no-files state to ready "Import" instead

On welcome page, in both connected and disconnected states:

Rewrite WelcomeInfo and AboutIpfs content for clarity

On welcome page, in connected state:

Replace text that's essentially duplicated in WelcomeInfo with shorter, friendly messaging
Add check-mark icon for continuity with Companion
Remove <ApiAddressForm> box, since it's rarely relevant here (but add to settings page to account for edge cases; see below)

On welcome page, in disconnected state:

Add alert icon for continuity with Companion
Rewrite troubleshooting guidance for clarity and update docs link
For CORS section of troubleshooting guidance, add option to select between OS/flavor in <Shell> header, to streamline and avoid showing user commands they don't need (thanks @rafaelramalho19!)
Move <ApiAddressForm> into the troubleshooting guidance (thanks @rafaelramalho19!)

On status page, upon connection interruption:

Update "Is your daemon running?" guidance to align with edits to welcome page disconnected state

On status page, always:

Add "Edit" link next to API line in "Advanced"; this takes user to <ApiAddressForm> section of settings page (thanks @rafaelramalho19!)

On settings page:

Add box for <ApiAddressForm> above "IPFS Config" box, to account for users who are already connected but want to connect to a different IPFS API
Adjust font size/style for consistency

Update Joyride guidance throughout to account for the above changes, particularly to emphasize entry points for changing API address

Open questions

Does anything need to be modified as a result of https://github.com/ipfs-shipyard/ipfs-webui/pull/1563 ?
This PR involves a number of changes to running copy; will Transifex take care of reconciling differences between locales/en files to remove outdated i18n text, or does anything else need to be done first?

Extra note
These changes will require updating screenshots across a number of locations in our ecosystem. I'll take care of that in separate PR(s) once we know when we'd ship a release.
Screenshots
Welcome page, connected

Welcome page, disconnected

Files page when no files

Status page upon connection interruption

Closes #1463. Also refs #1406 about adding a link to Awesome IPFS somewhere in welcome content.

@lidel and @rafaelramalho19 -- I believe this is ready for your review, thanks for all your help in the meantime 😊
Please note there are two open questions in the description above.
Thanks so much!

Sounds good; see https://github.com/ipfs-shipyard/ipfs-webui/issues/1575 for node shutoff experience tweaks. I'll rebase against latest master and merge if all well. Thanks!


reogrid在显示20多万条的时候就不显示了

!!! Remove this before you submit the issue !!!

Providing code or test projects to reproduce the bug is important.
We may close the issue without resolving it if the issue doesn't include any sample code or reproducing steps.

Thank you for your cooperation!

Description
A clear and concise description of what the bug is.
To Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
Press ctrl+v to paste and upload the snapshot images.

Edition
Which edition of ReoGrid do you using?

Windows Form
WPF

Environment

OS: [e.g. Windows 10]
Language of OS: English

Even if someone wanted to help you, I doubt they could because your description of the problem is not clear and you did not provide a minimized code sample to reproduce the problem.
I don't know Chinese but based on Google translation your subject says 'Reogrid is not displayed when more than 200,000 items are displayed.'
If your problem is with the number of rows, see https://reogrid.net/document/worksheet/row-and-column
The upper limit for number of rows is 1,048,576
The following code works fine, writes data, displays it and sets focus to a cell.
If you have a reproducible error you should provide a minimized code sample.
Me.ReoGridControl1.CurrentWorksheet.RowCount = 1000000
Me.ReoGridControl1.CurrentWorksheet.SetCellData(New CellPosition(999999, 1), "Test")
Me.ReoGridControl1.CurrentWorksheet.FocusPos = New CellPosition(999999, 1)

Best Regards


有没有计划增加像webpack里npm run watch这种模式，有些情况需要这种模式

Clear and concise description of the problem
比如要在微擎里调试vue前端的时候
Suggested solution
期待中
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

You mean this? https://vitejs.dev/guide/build.html#rebuild-on-files-changes
你的意思是这样吗？ https://cn.vitejs.dev/guide/build.html#rebuild-on-files-changs

It's already supported.


incorrect path to sky130 klayout lyp file

Currently open_pdks installs technology file in the current directory layout:
/home/proppy/.volare/sky130A/libs.tech/klayout
/home/proppy/.volare/sky130A/libs.tech/klayout/drc
/home/proppy/.volare/sky130A/libs.tech/klayout/scripts
/home/proppy/.volare/sky130A/libs.tech/klayout/tech
/home/proppy/.volare/sky130A/libs.tech/klayout/tech/sky130A.lyp
/home/proppy/.volare/sky130A/libs.tech/klayout/tech/sky130A.lyt
/home/proppy/.volare/sky130A/libs.tech/klayout/lvs
/home/proppy/.volare/sky130A/libs.tech/klayout/pymacros
/home/proppy/.volare/sky130A/libs.tech/klayout/macros
/home/proppy/.volare/sky130A/libs.tech/klayout/ruby
/home/proppy/.volare/sky130A/libs.tech/klayout/python
/home/proppy/.volare/sky130A/libs.tech/klayout/klayoutrc

which is slightly different from the one in https://github.com/mabrains/sky130_klayout_pdk
This causes reference to the lyp file not be resolved my initializing klayout with technology:
$ KLAYOUT_HOME=$PDK_ROOT/sky130A/libs.tech/klayout klayout -e
...
Warning: Initialization of layers failed: Unable to open file: /home/proppy/.volare/sky130A/libs.tech/klayout/tech/sky130/sky130A.lyp (errno=2)

One can fix the reference to the lyt file to drop the sky130 directory:
https://github.com/mabrains/sky130_klayout_pdk/blob/main/sky130_tech/tech/sky130/sky130.lyt#L7-L9
in order to workaround this issue:
 <base-path>$(appdata_path)/tech</base-path>
 <original-base-path>$(appdata_path)/tech</original-base-path>
 <layer-properties_file>sky130A.lyp</layer-properties_file>

Which one is correct? sky130 and gf180 are definitely different, as evidenced by the fact that klayout doesn't work with gf180: https://github.com/The-OpenROAD-Project/OpenLane/issues/1593

another error related to this is klayout failing to load the lyp file:
Warning: Initialization of layers failed: Unable to open file: /home/proppy/mixed-signal-sky130a-env/share/pdk/sky130A/libs.tech/klayout/tech//sky130.lyp (errno=2)

I think this is due to the installation renaming the file from being named after the TECH (sky130) to being named after the pdk variant sky130A:
https://github.com/RTimothyEdwards/open_pdks/blob/master/sky130/Makefile.in#L1011