DX - Vue/React - Add prettier plugin for tailwind class standard ordering

What this does
Add a prettier plugin to both React and Vue so that tailwind class names are sorted in a standard way.
Based on this: Automatic Class Sorting with Prettier
How to test

Create a project with cookiecutter and this branch with either React or Vue as web clients
Go to web client folder
Install dependencies
Try changing the className / class of a html element. A good class to test is: text-white px-4 sm:px-8 py-2 sm:py-3 bg-sky-700 hover:bg-sky-800
Hit save (or trigger format the way you're used to)
The class should get re-ordered

Okay not sure what is wrong with eslint vue... don't even know why would it care about prettier...

Okay not sure what is wrong with eslint vue... don't even know why would it care about prettier...

Seems like vue has a  tough time with eslint 8+. Ended up just leaving the current version of things, wanted to do some upgrades but found these issues


V2 - Contributor is redirected to github app installation to UI to install the EasyCLA bot

Not sure if this is an issue logging it for tracking purpose
Prerequisite

Create a CLA group with only ICLA enabled
Add github repository for the CLA group
Generate template

Steps to Follow

Login to Github as individual contributor

Navigate to the repository used in prerequisite

Create PR

CLA check fails

Click on CLA NOT SIGNED

Contributor is redirected to Contributor Console

Click on Proceed as a Individual Contributor

Click on SIGN CLA when the button is enabled

Complete the docusign process

Contributor is redirected to github PR and CLA checks passed

Click on CommunityBridge logo or on dev-communitybridge-easycla link that is shown in below screenshot

Observed that contributor is redirected to github app installation and allows contributor to install EasyCLA bot (As per my understanding only Project Manager should be able to install the EasyCLA bot. Not sure if my understanding is correct)

Observed same issue when clicked in below links

Need to double-check that we have control over this or not. I think this is a GitHub link that points to the App which everyone can click on. However, only users of their own Org/Repos are able to install.


[Bug]: ConstantVariable not hidden

version
11.3.x
language

[ ] Go
[ ] Java
[ ] PHP
[x] Python
[ ] Typescript

Describe your bug
If you create a constant template variable with the builder dashboard.ConstantVariable, it is not hidden (the hide field is not generated). There is no hide method on this class - which makes sense as all constants should be hidden. If you upload the generated json - the template variable is displayed as a box with a name in it. If you go into edit mode and then save with no changes, the hide field is added to the json.
I have currently worked round this by patching the _internal.hide value of the ConstantVariable builder object as the underlying variable model does have the hide field.
def patched_contsant_variable(name: str) -> dashboard.ConstantVariable:
    constant_variable = dashboard.ConstantVariable(name)
    constant_variable._internal.hide = VariableHide.HIDE_VARIABLE
    return constant_variable

What did you expect to happen?
ConstantVariables should always have the hide field set to HIDE_VARIABLE and generate json with that setting

Fixed with the latest release - thanks
grafana-foundation-sdk = "1732830272!11.3.0"

My pleasure :)


Fixes Layer.isPopupOpen when no popup is bound

This fixes uncaught exception when checking whether a popup isOpen(), when the layer has no popup bound to it.

Oooh, I like this. Could it be possible to add a unit test, which makes sure that a call to isPopupOpen() does not throw an error?

Sure, but I wasn't able to find other unit tests for the L.Layer popup functions.
Do they exists?

No, maybe you should add them to https://github.com/Leaflet/Leaflet/blob/master/spec/suites/layer/PopupSpec.js . If you look at that file, you'll see it has tests for both L.Popup and the popup methods/options for L.Map. Having tests for the popup methods/options for L.Layer in the same place makes sense.

Alright, I'll have a look tonight!

@IvanSanchez this is my initial pass at the test cases, I kept 1 separate since I'm unsure whether this is actually expected behavior.

This looks quite good :+1: . One thing, though: As the current undesired behaviour is that a method call throws an error, the tests should explicitly check that the method call does indeed not throw an error (and check that, without your fix, the unit tests fail).
For reference, see https://github.com/Leaflet/Leaflet/blob/88d107ca969be9d7a5e7b17fafc4aadab466e18f/spec/suites/control/Control.LayersSpec.js#L104

Tooltip has the same issue https://github.com/Leaflet/Leaflet/blob/master/src/layer/Tooltip.js#L371

@medpr Feel free to write a fix and some tests, then.

@IvanSanchez changed the commits to first add the tests and only then change the behavior

@gvangool could you rebase this on master? Other than that, I think we're good to merge


[simd] Bump to 6.1.139

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Bump to 6.1.139, #39811
Fix cmake config
Fix build shared library

I tried to build this with cmake on windows but failed.
The upstream support for cmake+windows is very poor.

1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Test.vcxproj" (2) on node 1 (Simd target(s)).
     2>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Test.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     2>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Test.vcxproj" (Simd target(s)) -- FAILED.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.vcxproj" (3) on node 4 (Simd target(s)).
     3>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     3>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.vcxproj" (Simd target(s)) -- FAILED.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Use.vcxproj" (5) on node 5 (Simd target(s)).
     5>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Use.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\AmxBf16.vcxproj" (4) on node 7 (Simd target(s)).
     4>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\AmxBf16.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     5>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Use.vcxproj" (Simd target(s)) -- FAILED.
     4>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\AmxBf16.vcxproj" (Simd target(s)) -- FAILED.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx512vnni.vcxproj" (6) on node 2 (Simd target(s)).
     6>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx512vnni.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     6>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx512vnni.vcxproj" (Simd target(s)) -- FAILED.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Neon.vcxproj" (7) on node 9 (Simd target(s)).
     7>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Neon.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     7>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Neon.vcxproj" (Simd target(s)) -- FAILED.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Base.vcxproj" (8) on node 6 (Simd target(s)).
     8>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Base.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     8>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Base.vcxproj" (Simd target(s)) -- FAILED.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx512bw.vcxproj" (10) on node 8 (Simd target(s)).
    10>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx512bw.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx2.vcxproj" (9) on node 3 (Simd target(s)).
     9>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx2.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
    10>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx512bw.vcxproj" (Simd target(s)) -- FAILED.
     9>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Avx2.vcxproj" (Simd target(s)) -- FAILED.
     1>Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (1) is building "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Sse41.vcxproj" (11) on node 10 (Simd target(s)).
    11>D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Sse41.vcxproj : error MSB4057: The target "Simd" does not exist in the project.
    11>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Sse41.vcxproj" (Simd target(s)) -- FAILED.
     1>Done Building Project "D:\b\simd\x64-windows-rel\v6.1.139-db7544246e.clean\prj\vs2022\Simd.sln" (Simd target(s)) -- FAILED.

The error log on windows is odd.

To repro it, in the Simd project dir exec this
msbuild /m /p:Configuration=Release /p:Platform=x64 /t:Simd prj/vs2022/Simd.sln


WIP: [stable/mongodb-replicaset]: allow changing dbPath

WIP DO NOT MERGE

What this PR does / why we need it:
If you want to use storage.directoryPerDb this will crash because the mongo user does not and should not have permission to modify the lost+found directory that is added to /data/db when the volume mounts.
This change maintains the default of /data/db for existing users, but allows us to change the path. I would like feedback on a few items:
Special notes for your reviewer:

Should we allow total freedom or would it be better to restrict this to a sub-directory of /data/db.
Is mkdir -p $DB_PATH on line 82 problematic? There is an existence check on line 86 that this nullifies. Why does that existence check exist?

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md

Should we allow total freedom or would it be better to restrict this to a sub-directory of /data/db.

I would prefer to not even expose it all and just hardcode it to /data/db/something, then just migrate them to the new format if old format detected in the on-start.sh, if that's possible.

Is mkdir -p $DB_PATH on line 82 problematic? There is an existence check on line 86 that this nullifies. Why does that existence check exist?

I would hope mongodb should create the directories if they don't exist. If it doesn't, I'd say the mkdir is fine. The check on line 86 I added is just to detect an empty directory to determine if this is the initial install or not. This is because the mongod standalone feature (that I didn't add) doesn't support initial install.


Add Euler problem 27

Great! but can you remove those  ? to look like this

Updated. Should look the same as your screenshot now 😄


wiki/Directives defaults incorrect

The Directives wiki page still mentions that LE staging environment is the default whereas an unmodified 0.9.1 install uses the production environment.

Just went over it and fixed, thanks! If you find more of my mistakes, don't hesitate to rub it in! :-D


OpenLayers v6

Have you tested this with v6? I'll do so as soon as I can.

@tomchadwin I've updated a couple of apps that depend on ol-popup to v6 and haven't had any issues. I'm hoping to update the examples to v6 over the next few days just to be sure.

I've updated the examples to use ol v6.1.1 and also built the parcel and webpack examples using the same and no changes were required to ol-popup :tada:

Splendid! Many thanks.


Debian не удаётся запустить плагин

# Logfile created on 2018-10-18 10:15:07 +0700 by logger.rb/v1.2.7
E, [2018-10-18T10:15:07.861992 #30323] ERROR -- : Validation failed: Taggings is invalid
E, [2018-10-18T10:15:07.862099 #30323] ERROR -- : /var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/validations.rb:79:in `rais
e_record_invalid'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/validations.rb:43:in `save!'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/attribute_methods/dirty.rb:29:in `save!'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:291:in `block in save!'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transac
tion'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:220:in `transaction'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
/var/lib/gems/2.3.0/gems/activerecord-4.2.8/lib/active_record/transactions.rb:291:in `save!'
/var/www/redmine/plugins/redmine_recurring_tasks/app/models/recurring_task.rb:120:in `tap'
/var/www/redmine/plugins/redmine_recurring_tasks/app/models/recurring_task.rb:120:in `copy_issue'
/var/www/redmine/plugins/redmine_recurring_tasks/app/models/recurring_task.rb:126:in `execute'
/var/www/redmine/plugins/redmine_recurring_tasks/lib/redmine_recurring_tasks/issue_checker.rb:16:in `block in call'
/var/www/redmine/plugins/redmine_recurring_tasks/lib/redmine_recurring_tasks/issue_checker.rb:14:in `each'
/var/www/redmine/plugins/redmine_recurring_tasks/lib/redmine_recurring_tasks/issue_checker.rb:14:in `call'
/var/www/redmine/plugins/redmine_recurring_tasks/lib/tasks/process.rake:5:in `block (2 levels) in <top (required)>'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/task.rb:251:in `block in execute'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/task.rb:251:in `each'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/task.rb:251:in `execute'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/task.rb:195:in `block in invoke_with_call_chain'
/usr/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/task.rb:188:in `invoke_with_call_chain'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/task.rb:181:in `invoke'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:160:in `invoke_task'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:116:in `each'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:116:in `block in top_level'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:125:in `run_with_threads'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:110:in `top_level'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:83:in `block in run'
/var/lib/gems/2.3.0/gems/rake-12.3.0/lib/rake/application.rb:186:in `standard_exception_handling'

Всё перепробовали, не знаем куда копать :(

Пожалуйста, покажите вывод команды
ls -laF plugins
Переоткройте задачу, если готовы работать по ней.


Remove dependency on libpcre++

C++ has had support for simple regex matching since C++11.  This PR removes the dependencies on both libpcre and libpcre++ by using the standard library implementation.

That is crazy, but yeah, that's a very old version of gcc.  I'm sure it's possible to add some sort of compile-time check, but I'm not sure how to go about that.  Also the check is only actually needed when compiling for Windows, but the current configuration enforces the dependency on all systems.
I bet you can just throw an error during config if compiling with mingw with gcc version < 4.9.
Since all of this effort is for this single check, I wonder if regex is overkill here.  Maybe a simpler check can just be used?

Can you check if your change makes a working windows binary? I wonder if the mingw dependency in the docker file works. If the docker file works out the box then I vote to just go with it - we can just say the docker file is the supported build env and not worry too much about checking for old tools.

It makes a working windows binary with mingw-64 with gcc version 8.2.0, but I haven't tried the docker version.
I'm all in favor for not supporting ancient compilers.

Awesome! We can always up the version in docker if we need to (although I think it is already current).


Add IBM resource group flag in hiveutil

Among the pre-requirement steps to create an IBM Cloud, we get redirected to CCOTL (GH) which suggests to use resource-groups when creating Service IDs
Note: --resource-group-name option is optional, but it is recommended to use to have finer grained access to the resources.
However, hiveutil doesn't have a flag for resource group, so if we use resource group in the ccotl cmd, then our cluster creation will fail because would not be using the same resource group.

Closing in favor of https://issues.redhat.com/browse/HIVE-2480.

Another thing to be aware of: If you use hive's MachinePools, there's currently going to be no way to feed that ResourceGroup to them. You'll either need to constrain your use of MachinePools to the default RG, or avoid them altogether (--skip-machine-pools in hiveutil) and manage your MachineSets directly on the spoke cluster.

Hello @2uasimojo ! thanks for your reply and for opening the Jira.
I was using hiveutils for starting building our automated script about cluster provisioning, but I moved to applying config YAML.

I should warn you: with our current workload, we are unlikely to get around to this any time soon. However, we welcome external contributions! And we'll be happy to guide you along the way.

I'd really like to contribute, although my workload won't let me pull myself into this right now, IBM Cloud and ocp installer are new to me so I'd need some time to dig into, try and error etc. But I'll watch the Jira ticket and if I find any time in the next months to look into it, I will.


please add pixel style round icon support

We are working on everything!

Did you like this??

That looks pretty!


Update v2 schemas to include “#/definitions/“ …

…as a $ref prefix so Phil’s parse works

@philerooski
I've updated the schema mappings where applicable. There are still a few references to v1 schemas b/c those are related to older assessments that have not been validated against the v2 schemas.
WRT "taskResult.json" - that file is marked as deprecated and was only ever included on iOS. Same with "answers.json" and "info.json" (as far as I know - @nategbrown9 is this correct?) It is included in the archives b/c Northwestern is still doing internal testing on iOS using those files which are required by Exporter 2.0 and Bridge 1.0
WRT build numbers, I am not sure I understand what you are referring to.


Optionally disable gossip block forwarding

This commit adds a new configuration option to the peer which makes peers
not forward blocks that they pull from the ordering service.
If all peers in an organization explictly set "peer.deliveryclient.blockGossipEnabled" to false,
no peer in the organization gossips blocks to any other peer in that organization.
Change-Id: I5d9b278ae72f239129827c044fa78179f6ba87ab
Signed-off-by: Yacov Manevich<EMAIL_ADDRESS>

@Mergifyio backport release-2.3

@Mergifyio backport release-2.2


Modbus is missing in docker image Espressif/idf:latest (IDFGH-7287)

Hi,
the Espressif/idf:latest image (773b66c28144) provided on dockerhub.com does no longer contain the component "freemodbus".
Is this by accident or intention?
Best regards
Andreas

Hi Andreas,
This is intended behavior. The freemodbus component is no longer part of esp-idf and its image but will be supported as a separate component in the component manager registry.
The component can be used with esp-idf v4.1 - v5.0.

Thank you, that link solves my issue.

Just for reference in case someone else finds this issue, the docs related to IDF 5.0 migration can be found here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/migration-guides/removed-components.html


Form explainer: fix image positioning after expandable animation

Fixes occasional issue where, when the form explainer image is fixed & the window is scrolled almost to the footer, expanding or collapsing an expandable will cause the image to be positioned over the footer.
Additions

adds an expandable click handler that sets up a timeout to check the image position after expandable animation is estimated to be complete

Review

@cfarm @amymok

Screenshots
Before

After

Testing

Open loan-estimate
Click on the Definitions tab on the first page, and open the first term (Monthly Principal & Interest)
Scroll down almost to the footer
Click on second to last expandable (Estimated Closing Costs)
Check whether the footer is partially covered by the form explainer image.

Notes

This is working for me locally in Safari & Chrome, but it's hard to verify in Saucelabs given the streaming lag. I think it's working on the iPad & IE9+ and Chrome on Windows, but I can't really tell with IE8.

Checklist

[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the front end playbook
[ ] Visually tested in supported browsers and devices

Windows 7

[ ] IE 11
[x] IE 10
[x] IE 9
[x] IE 8
[x] latest Chrome
[ ] latest Firefox

Mac

[x] latest Chrome
[ ] latest Firefox
[x] latest Safari

Mobile

[ ] latest iPhone
[x] latest iPad
[ ] latest Android
[ ] latest BlackBerry

I can test the remaining browsers on the checklist

I guess this doesn't exist as a problem on small screens, but I checked IE on Windows and they seem to be working.

:+1:


add test to Validator

This PR adds more tests in order to cover core validation functionality.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Demo in source form

Hi, do you have this demo in source code from?
https://codesandbox.io/s/dice-box-threejs-j79h35?file=/src/index.js
I've setup a vite project (first time using it)  , put the vite.config.js from your dice the folder, and I'm getting an error with import "'./styles.css" error
Syntax error: Cannot use import statement outside a module
I wanted to setup with source code version.

I solved it, it seems you need to load the specify index.js to load as a module.
However, I build a distribution version, and  when I uploaded it a webserver, it has error loading (minified files)

fixed. Had to update blob storage to v2 and use static website


The automatic Imports of vscode behaves differently in different folders

I have disabled all the vscode extensions.
This is my jsconfig configuration:
{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/gulp/*": ["script/gulp/*"],
      "@/script/*": ["script/*"],
      "@/src/*": ["src/*"]
    }
  },
  "exclude": ["node_modules", "dist"]
}

This is my project directory structure
├── script
│   ├── gulp
│   │   ├── task
│   │   │   ├── components
│   │   │   │   └── index.js
│   │   │   └── ...
│   │   └── ...
│   │
│   ├── utils
│   │   ├── yaml.js <-- I expect the automatic import behavior in this file
│   │   └── ...
│   └── ...
│
├── src
│   ├── app.js <-- I don't expect the automatic import behavior in this file
│   └── ...
│
├── jsconfig.json
├── gulpfile.babel.js
└── ...

When I use the automatic import in the script directory(The behavior I want)

When I use the automatic import in the src directory(Behavior I don't want)

I don’t know what I have configured wrong or other errors
anybody can help me?

The difference is because you have a file with imports vs an empty file
In empty files, VS Code tries to use the import style that best matches what is configured in your jsconfig (the default is module). If you set something like "module": "es2020",, import should be used
In a file with existing imports, we try to match the style of existing imports


calibre: 2.64.0 -> 2.66.0

Motivation for this change

Update to 2.64.0 to 2.66.0
Get rid of embedded python modules in favour of upstream
Privacy settings (based on patches from Debian)

I understand item 3 could be controversial, so I'm open to moving that to a separate PR.
NOTE: calibre segfaults on exit (for 2.64, 2.66 and 2.66 with patches) for me, but it doesn't seem to cause any bad behaviour.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Thanks @fpletz, we now use fetchpatch as requested. I also bumped QT from 5.5 to 5.6 in the process. Seems to work here.
Segfault on exit is still present, but that was always the case it seems.

 and verified the segfault existed before.

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks broke.

Comments from Reviewable


Removed -d flag from 'invoke'

The -d flag seems to be interpreted by SLS as the payload and not "deployed function" anymore.

This will fix https://github.com/Nordstrom/serverless-artillery/issues/61

This does the trick.  Thanks @gwsii!


refactor: remove unnecessary allocations and apply clippy fixes

The following pull request removes lots of instances of unnecessary heap allocations through either .clone(), .collect(), or .to_string() by using references or utilizing Display instead of ToString.
Other than that, this pull request also refactors many parts of the code to be a lot cleaner! :D

Pull request will be redone with verified commits, one sec!


Upgrade deprecated runtime nodejs8.10

CloudFormation templates in aws-appsync-calorie-tracker-workshop have been found to include a deprecated Lambda function runtime (nodejs8.10). The affected templates have been updated to a supported runtime (nodejs10.x).
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

thank you Chris


Add basic snapshot testing with insta

This is now fixed to work with the values given by the current stable. The debug representation gains trailing commas on the next stable so we will need to update the snapshots then.
I've included two simple testcases here to show the system working. We'll obviously want to add more later. File name format is <production>.<test-identifier>.input.

Alright, that's complete functionality and tuned to behave decently.
r? @qmx
This basically has to be serial until https://github.com/mitsuhiko/insta/issues/31. We can probably parallelize the parsing, actually, so long as we serialize the snapshot testing. I'll do that in another PR, though.

I added a note to the README about the snapshot tests. This will require changing which productions are initially tested here to keep the promises I posited there (though of course the exact promise can be debated/reworded), which I'll look at tomorrow. I want to have at least two basic but nontrivial tests present here in the initial PR to show the harness working.

Rebase wrt. changes in other PR?

Done.


Repaint gantt control

Hi, is it possible to repaint gantt control? I'd like to implement 'fit to screen' feature by specifying columnWidth, but unfortunately after setting the new width it's not changes in UI.
Upd: workaround - hide and display component to cause repaint using ngIf

Sorry, this is a defect that we will address in the future. Now I can provide you with a solution.
    @ViewChild(NgxGanttComponent) ganttComponent: NgxGanttComponent;

changeWidth(){
    this.columnWidth=300;
    Promise.resolve().then(()=>{
        ganttComponent.detectChanges();
   })
}


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter vis-timeandweather for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.vis-timeandweather
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E162] js-controller dependency missing. js-controller 4.0.24 is required as minimum, 5.0.19 is recommended. Please add to dependencies at io-package.json.
[ ] :heavy_exclamation_mark: [E162] onlyWWW should have common.mode "none" in io-package.json

WARNINGS:

[ ] :eyes: [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W145] Missing suggested translation into uk,pt,nl,fr,it,es,pl,zh-cn of some "common.news" in io-package.json.
[ ] :eyes: [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.noConfig" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI.config":"none".
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W523] "package-lock.json" not found in repo! Please remove from .gitignore!

SUGGESTIONS:

[ ] :pushpin: [S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 06 Sep 2024 11:28:17 GMT

Issue outdated due to RECREATE request. Follow up issue #52 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Rename Flags EventFlag and MemFdCreateFlag

relates to #317
What does this PR do
Rename Flags
Checklist:

[x] I have read CONTRIBUTING.md
[ ] I have written necessary tests and rustdoc comments
[x] A change log has been added if this PR modifies nix's API

Also, a changelog entry is needed, see this on how to add one.

thank you too

Let's merge this first.


Force miui launcher recents task in 3rd party launcher a10

Please add support to force use of miui launcher recents task in 3rd party launcher a10, system ui recents doesn't work fine in miui 12.5 A10.
If you can and want

I don't have miui12.5 or A10 MIUI devices, you can try using quick switch to set lawnchair as recent provider.

Hello. How to ur use module?


cannot run demo scenarios and error message is displayed

Description
I cannot run demo scenarios. Instead, a message is displayed on the console.
It looks like there is a mismatch in the argument types of the PythonAPI.
To Reproduce
Executed around 15:00 on 2020-02-04.

Download CARLA_<IP_ADDRESS>.tar.gz (compiled version) and extract it.
Clone "carla-simulator/scenario_runner".
Follow the instractions on 'Docs/getting_started.md'.

Install prerequisites(For Python 3.x)
Include CARLA Python API to the PYTHONPATH

Start the CARLA server: ./CarlaUE4.sh
Open another tarminal and execute: python scenario_runner.py --openscenario srunner/examples/FollowLeadingVehicle.xosc --reloadWorld
See the following message:

...
Boost.Python.ArgumentError: Python argument types in
WeatherParameters.init(WeatherParameters)
did not match C++ signature:
init(_object, float cloudiness=0.0, float precipitation=0.0, float precipitation_deposits=0.0, float wind_intensity=0.0, float sun_azimuth_angle=0.0, float sun_altitude_angle=0.0, float fog_density=0.0, float fog_distance=0.0, float wetness=0.0)
init(_object)
...

Desktop:

OS: Ubuntu 18.04.1
CARLA Version 0.9.7 (compiled version)
Python version 3.6.9
master branch

The problem is an API change introduced after 0.9.7. Cloudyness became cloudiness. Can you for the moment change this locally at your end?

**Error :- ** AttributeError: 'Namespace' object has no attribute 'config_file'
python3 scenario_runner.py --scenario FollowLeadingVehicle_1 --reloadWorld
Traceback (most recent call last):
File "scenario_runner.py", line 620, in
sys.exit(main())
File "scenario_runner.py", line 610, in main
result = scenario_runner.run()
File "scenario_runner.py", line 530, in run
result = self._run_scenarios()
File "scenario_runner.py", line 423, in _run_scenarios
self._args.config_file)
AttributeError: 'Namespace' object has no attribute 'config_file'


Attributes: <%- replaced with <!-

Recently discovered using ejs with tailwind is pretty handy. Unfortunately, prettier breaks upon the following scenario (using ejs inside element attribute):

  <% "lorem ipsum dorem jazz".split(" ").forEach((word, idx) => { %>

  <span class="animation-delay-[<%- 50 * idx %>ms]"> <%= word %>
  <% }) %>

Using prettier 3.1.1 and plugin v0.0.19

upon x'th inspection and utter disappointment, it appears my vscode was not using the local config file with the plugin for some odd reason


Still want support for both <- and ~ nodes in a model

Still desire for support of nodes the follow both a stochastic and a deterministic declaration in the model:

<- deterministic declaration defines the node value
~ stochastic declaration determines the logProb evaluation

I've needed this once before for a project, and did a workaround using a custom distribution.  I now find myself needing it again, and once again have to explain the only way to do this is via a custom distribution, to accomplish both the deterministic calculations and the likelihood evaluations.
Note that WinBUGS does support this.
e.g.,
a ~ dnorm(0, 1)
b ~ dnorm(0, 1)
c <- a+b
c ~ dwhatever(...)

Is there a case where this is not an artificial construction?  If a and b each have a density, their sum can't have a separate density.  IIRC, JAGS does not support this.  I've also had users ask about such a need, but it has usually reflected incorrect thinking about their problem.

Yes, certainly.  In an earlier project I was working on (about 2 years ago now) they were modelling manatee deaths.  Some deaths due to different causes were known, and we could count them.  Some deaths were due to unknown causes, but those were modelled stochastically.  The sum of the unknown and unknown numbers of deaths, then was assigned to follow some other distribution (again one component of that sum was observed counts, and the other part of that sum was being modelled) as a function of the entire population size and the death rate (that is, the total number of deaths, those we saw, and those we didn't see, is some stochastic function of the total population size and the death rate).
In this case, the total number of individuals in each particular area is a derived quantity based on limited observations.  Then, again, this total number of individuals is also modelled as a stochastic function, being a function of the environmental factors, habitat, etc, at each location.

I did a little thinking about how I think it should work:
deterministic nodes

simulate fills in the value via a deterministic calculation
calculate (calls simulate) to fill in the value

stochastic nodes

simulate fills in the value via a random draw
calculate calculates the logProb

deterministic and stochastic nodes

simulate fills in the value via a deterministic calculation (like a deterministic node)
calculate acts like both: calls simulate (like a deterministic node) to fill in the value via deterministic calculation, then also (like a stochastic node) calculates the logProb.

Of course, there would have to be special processing to allow for 2 definitions of such a node.
And I'm not sure the right handling of things like isStoch, but my initial thought is that it should be handled mostly like a stochastic node.  isStoch = TRUE, and getDependencies stops there, unless downstream = TRUE.
Just some thoughts.  But I really would like to see this supported.
I know JAGS did not support this, but that WinBUGS does.

Adding this comment from defunct 'core feature ideas' wiki:
This would permit combinations of model nodes to be specified as following a particular distribution.  For example, perhaps we wish to say the sum of two model components follows a normal distribution.  One of these components is observed data, and the other is a latent model variable.  Yes, this simple example is otherwise tractable because of the normal distributions, but hopefully it makes the point:
code <- nimbleCode({
x ~ dnorm(b0 + b1*c1 + b2*c2, sd = sigma_x)
y <- x + observedData
y ~ dnorm(mu, sd = sigma_y)
})


Update Papers to 3.4.0-386

Thank you for the contribution. It was merged directly as b21cb639d925237263533ea1986497be3a8a1909 to keep commit history cleaner. Your contribution is still credited to you.


Change BackstackAccessor.isInBackStackAndroidX() implementation

FragmentManager.toString() occurs NPE when mHost is null since androidx.fragment:fragment:1.2.0-beta01.
        java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference
        at androidx.fragment.app.FragmentManager.toString(FragmentManager.java:1022)
        at java.lang.String.valueOf(String.java:2896)
        at java.lang.StringBuilder.append(StringBuilder.java:132)
        at androidx.fragment.app.Fragment.dump(Fragment.java:2640)
        at androidx.core.app.BackstackAccessor.isInBackStackAndroidX(BackstackAccessor.java:57)
        at androidx.core.app.BackstackAccessor.isFragmentOnBackStack(BackstackAccessor.java:46)
        at com.hannesdorfmann.mosby3.mvp.delegate.FragmentMvpDelegateImpl.retainPresenterInstance(FragmentMvpDelegateImpl.java:163)
        at com.hannesdorfmann.mosby3.mvp.delegate.FragmentMvpDelegateImpl.onDestroy(FragmentMvpDelegateImpl.java:285)
        at com.hannesdorfmann.mosby3.mvp.MvpFragment.onDestroy(MvpFragment.java:103)

So this PR uses reflection instead of Fragment.dump().

@sockeqwe Please merge & release it

Thanks for your PR, however, I don't think that this will work:
 if (clazz != null && clazz.getName().startsWith("androidx")) {
                Method method = clazz.getDeclaredMethod("isInBackStack");
                method.setAccessible(true);
                return (boolean) method.invoke(fragment);
            }

as android has some internal white / black listing and would at runtime not allow  to use reflection on androidx classes (usually)...
Did that work for you? Can you provide a working unit test?

I knew that but do the support libraries also have grey or blacklist APIs?
Our app is working on Pie device without any problem. And I can run BackstackActivityWithChildFragmentsTest.fragmentsOnBackstack() test in utils-fragment-integration-test module successfully on Pie emulator.
Testing started at 12:21 ...

12/09 12:21:08: Launching 'fragmentsOnBackstack()' on Pixel 2 API 29.
Running tests

$ adb shell am instrument -w -r   -e debug false -e class 'com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragmentsTest#fragmentsOnBackstack' com.hannesdorfmann.mosby3.utils.fragment.integrationtest.test/android.support.test.runner.AndroidJUnitRunner
Waiting for process to come online...

Started running tests
Connected to process 25251 on device 'emulator-5554'.
Capturing and displaying logcat messages from application. This behavior can be disabled in the "Logcat output" section of the "Debugger" settings page.
I/integrationtes: The ClassLoaderContext is a special shared library.
I/chatty: uid=10137(com.hannesdorfmann.mosby3.utils.fragment.integrationtest) identical 2 lines
I/integrationtes: The ClassLoaderContext is a special shared library.
I/integrationtes: The ClassLoaderContext is a special shared library.
I/chatty: uid=10137(com.hannesdorfmann.mosby3.utils.fragment.integrationtest) identical 1 line
I/integrationtes: The ClassLoaderContext is a special shared library.
W/integrationtes: Accessing hidden method Landroid/app/Instrumentation;->execStartActivity(Landroid/content/Context;Landroid/os/IBinder;Landroid/os/IBinder;Landroid/app/Activity;Landroid/content/Intent;ILandroid/os/Bundle;)Landroid/app/Instrumentation$ActivityResult; (greylist, linking, allowed)
I/MonitoringInstrumentation: Instrumentation Started!
I/MonitoringInstrumentation: Setting context classloader to 'dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/android.test.runner.jar", zip file "/system/framework/org.apache.http.legacy.jar", zip file "/system/framework/android.test.mock.jar", zip file "/data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest.test-W6-Ji71aHW6AfyYNlBDu8Q==/base.apk", zip file "/data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest-wGjh1IUHICnXmCwhtzmqcQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest.test-W6-Ji71aHW6AfyYNlBDu8Q==/lib/x86, /data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest-wGjh1IUHICnXmCwhtzmqcQ==/lib/x86, /system/lib, /system/product/lib]]]', Original: 'dalvik.system.PathClassLoader[DexPathList[[zip file "/system/framework/android.test.runner.jar", zip file "/system/framework/org.apache.http.legacy.jar", zip file "/system/framework/android.test.mock.jar", zip file "/data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest.test-W6-Ji71aHW6AfyYNlBDu8Q==/base.apk", zip file "/data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest-wGjh1IUHICnXmCwhtzmqcQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest.test-W6-Ji71aHW6AfyYNlBDu8Q==/lib/x86, /data/app/com.hannesdorfmann.mosby3.utils.fragment.integrationtest-wGjh1IUHICnXmCwhtzmqcQ==/lib/x86, /system/lib, /system/product/lib]]]'
I/MonitoringInstrumentation: No JSBridge.
D/InfraTrack: Tracking disabled due to lack of internet permissions
I/UsageTrackerFacilitator: Usage tracking disabled
D/TestExecutor: Adding listener android.support.test.internal.runner.listener.LogRunListener
    Adding listener android.support.test.internal.runner.listener.InstrumentationResultPrinter
D/TestExecutor: Adding listener android.support.test.internal.runner.listener.ActivityFinisherRunListener
I/TestRunner: run started: 1 tests
I/TestRunner: started: fragmentsOnBackstack(com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragmentsTest)
I/MonitoringInstrumentation: Activities that are still in CREATED to STOPPED: 0
D/ActivityTestRule: Launching activity com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments
D/MonitoringInstrumentation: execStartActivity(context, ibinder, ibinder, activity, intent, int, bundle
W/ActivityThread: handleWindowVisibility: no activity for token android.os.BinderProxy@a1e3304
D/libEGL: Emulator has host GPU support, qemu.gles is set to 1.
W/libc: Unable to set property "qemu.gles" to "1": connection failed; errno=13 (Permission denied)
W/RenderThread: type=1400 audit(0.0:261): avc: denied { write } for name="property_service" dev="tmpfs" ino=8906 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:property_socket:s0 tclass=sock_file permissive=0
D/libEGL: loaded /vendor/lib/egl/libEGL_emulation.so
D/libEGL: loaded /vendor/lib/egl/libGLESv1_CM_emulation.so
D/libEGL: loaded /vendor/lib/egl/libGLESv2_emulation.so
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@7cd7b70 in: PRE_ON_CREATE
W/integrationtes: Accessing hidden method Landroid/view/View;->computeFitSystemWindows(Landroid/graphics/Rect;Landroid/graphics/Rect;)Z (greylist, reflection, allowed)
W/integrationtes: Accessing hidden method Landroid/view/ViewGroup;->makeOptionalFitsSystemWindows()V (greylist, reflection, allowed)
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@7cd7b70 in: CREATED
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@7cd7b70 in: STARTED
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@7cd7b70 in: RESUMED
D/HostConnection: HostConnection::get() New Host Connection established 0xe0a722d0, tid 25285
D/HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_gles_max_version_3_0
W/OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 0 0
D/EGL_emulation: eglCreateContext: 0xe0a1a300: maj 3 min 0 rcv 3
D/EGL_emulation: eglMakeCurrent: 0xe0a1a300: ver 3 0 (tinfo 0xe0a0f270)
W/Gralloc3: mapper 3.x is not supported
D/HostConnection: createUnique: call
D/HostConnection: HostConnection::get() New Host Connection established 0xe0a72410, tid 25285
D/HostConnection: HostComposition ext ANDROID_EMU_CHECKSUM_HELPER_v1 ANDROID_EMU_native_sync_v2 ANDROID_EMU_native_sync_v3 ANDROID_EMU_dma_v1 ANDROID_EMU_direct_mem ANDROID_EMU_host_composition_v1 ANDROID_EMU_host_composition_v2 ANDROID_EMU_YUV420_888_to_NV21 ANDROID_EMU_YUV_Cache GL_OES_EGL_image_external_essl3 GL_OES_vertex_array_object GL_KHR_texture_compression_astc_ldr ANDROID_EMU_gles_max_version_3_0
D/eglCodecCommon: allocate: Ask for block of size 0x1000
    allocate: ioctl allocate returned offset 0x3ff807000 size 0x2000
D/EGL_emulation: eglMakeCurrent: 0xe0a1a300: ver 3 0 (tinfo 0xe0a0f270)
D/eglCodecCommon: setVertexArrayObject: set vao to 0 (0) 1 0
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@7cd7b70 in: PAUSED
D/EGL_emulation: eglMakeCurrent: 0xe0a1a300: ver 3 0 (tinfo 0xe0a0f270)
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@7cd7b70 in: STOPPED
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@7cd7b70 in: DESTROYED
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@ce73585 in: PRE_ON_CREATE
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@ce73585 in: CREATED
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@ce73585 in: STARTED
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@ce73585 in: RESUMED
D/EGL_emulation: eglMakeCurrent: 0xe0a1a300: ver 3 0 (tinfo 0xe0a0f270)
I/TestRunner: finished: fragmentsOnBackstack(com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragmentsTest)
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@ce73585 in: PAUSED
I/MonitoringInstrumentation: Activities that are still in CREATED to STOPPED: 1
I/TestRunner: run finished: 1 tests, 0 failed, 0 ignored
I/MonitoringInstrumentation: Unstopped activity count: 1
I/MonitoringInstrumentation: Unstopped activity count: 1
I/MonitoringInstrumentation: Activities that are still in CREATED to STOPPED: 1
D/EGL_emulation: eglMakeCurrent: 0xe0a1a300: ver 3 0 (tinfo 0xe0a0f270)
D/LifecycleMonitor: Lifecycle status change: com.hannesdorfmann.mosby3.utils.fragment.integrationtest.backstack.BackstackActivityWithChildFragments@ce73585 in: STOPPED
I/MonitoringInstrumentation: waitForActivitiesToComplete() took: 102ms

Tests ran to completion.

I added utils-fragment-androidx-integration-test module. To use jetifier, I had to create new module and copy 'utils-fragment.aar' to its libs directory not use 'utils-fragment' module directly.
I think you can check whether reflection works or not.

Any update on this?

I thought a bit more about it  @uOOOO and have written down my thoughts in #339
Your feedback would be highly appreciated

@sockeqwe Could you please release any temporary workaround version? It seems reall, really critical in current circumstances. To be honest I don't really care how it works (if it works at least a bit better), I just badly need to buy myself some time to find a new solution.

I guess it's not needed anymore since fragment-1.2.1 returned toString in it's previous form

Yep, Google fixed it.

Calling toString() on a FragmentManager instance no longer throws a NullPointerException when the Activity is already destroyed. (b/148189412)
https://developer.android.com/jetpack/androidx/releases/fragment

Confirm that this issue was fixed by google by add these lines to build.gradle in app as Document :
implementation 'androidx.appcompat:appcompat:1.3.0-alpha01'
implementation "androidx.fragment:fragment-ktx:1.3.0-alpha07"
https://developer.android.com/jetpack/androidx/releases/fragment


chore: Local installation

Installation steps for local
Parameterise secret values
Resolves #98

@awellnitz-materna : Please approve

Hi @adkumar1, what do the new values have to do with the installation docs?

Hi @adkumar1, what do the new values have to do with the installation docs?

Hi @SebastianBezold : These are not new values, these are old only. We have just moved it from secret file to values file so that it can be configurable for any user directly into values file.

@adkumar1 Thank you for your changes. It would still be important for me to know which of the values from the secret are important for a local deployment. There are a lot of standard values and we don't need all of them.

@adkumar1 Thank you for your changes. It would still be important for me to know which of the values from the secret are important for a local deployment. There are a lot of standard values and we don't need all of them.

Hi @awellnitz-materna :
To Run a pod successfully,  it needs database information , other than that all secrets can be just default.
postgresql.auth.username ,postgresql.auth.password ,postgresql.auth.postgresPassword ,postgresql.auth.database
To run e2e successfully it needs Kubeapps, Vault secrets in place.

@adkumar1 That's good that you tell me, but everyone who wants to install the project locally faces the same issue. Which values are important and which are not.


Large percentage of cpu time in memset when reading with a larger buffer

Reproduced using a slightly modified version of examples/client.rs to allow specifying a path, and reading into a user-provided buffer. The problem was originally noticed via rusoto s3 client, which has a configuration for a read buffer size, which gets mapped to hyper http1_read_buf_exact_size. Since aws s3 recommends fetching large ranges, using a larger buffer seemed like a good idea and was not expected to cause any cpu overhead.

use std::fs::File;
use std::io;
use std::io::BufReader;
use std::net::ToSocketAddrs;
use std::path::PathBuf;
use std::sync::Arc;

use argh::FromArgs;
use tokio::io::{split, AsyncReadExt, AsyncWriteExt};
use tokio::net::TcpStream;
use tokio_rustls::TlsConnector;

/// Tokio Rustls client example
#[derive(FromArgs)]
struct Options {
    /// host
    #[argh(positional)]
    host: String,

    /// path
    #[argh(positional)]
    path: Option<String>,

    /// port
    #[argh(option, short = 'p', default = "443")]
    port: u16,

    /// domain
    #[argh(option, short = 'd')]
    domain: Option<String>,

    /// cafile
    #[argh(option, short = 'c')]
    cafile: Option<PathBuf>,
}

#[tokio::main]
async fn main() -> io::Result<()> {
    let options: Options = argh::from_env();

    let addr = (options.host.as_str(), options.port)
        .to_socket_addrs()?
        .next()
        .ok_or_else(|| io::Error::from(io::ErrorKind::NotFound))?;
    let domain = options.domain.unwrap_or(options.host);
    let path = options.path.as_ref().map(|p| p.as_str()).unwrap_or("/");
    let content = format!(
        "GET {} HTTP/1.0\r\nConnection: close\r\nHost: {}\r\n\r\n",
        path, domain
    );

    let mut root_cert_store = rustls::RootCertStore::empty();
    if let Some(cafile) = &options.cafile {
        let mut pem = BufReader::new(File::open(cafile)?);
        for cert in rustls_pemfile::certs(&mut pem) {
            root_cert_store.add(cert?).unwrap();
        }
    } else {
        root_cert_store.extend(webpki_roots::TLS_SERVER_ROOTS.iter().cloned());
    }

    let config = rustls::ClientConfig::builder()
        .with_root_certificates(root_cert_store)
        .with_no_client_auth(); // i guess this was previously the default?
    let connector = TlsConnector::from(Arc::new(config));

    let stream = TcpStream::connect(&addr).await?;

    let domain = pki_types::ServerName::try_from(domain.as_str())
        .map_err(|_| io::Error::new(io::ErrorKind::InvalidInput, "invalid dnsname"))?
        .to_owned();

    let mut stream = connector.connect(domain, stream).await?;
    stream.write_all(content.as_bytes()).await?;

    let (mut reader, _writer) = split(stream);

    let mut buffer = Vec::with_capacity(4 * 1024 * 1024);
    let mut total_len = 0_usize;

    loop {
        match reader.read_buf(&mut buffer).await {
            Ok(len) => {
                total_len += len;
                buffer.clear();
                if len == 0 {
                    break;
                }
            }
            Err(e) => {
                eprintln!("{:?}", e);
                break;
            }
        }
    }

    println!("Size: {}", total_len);

    Ok(())
}

I believe this is because the poll_read call is passing in a large uninitialized ReadBuf, causing the stream to zeroing the ReadBuf unnecessarily.
https://github.com/rustls/tokio-rustls/blob/main/src/common/mod.rs#L218
We can do some optimizations on read_buf cfg. https://github.com/rustls/rustls/blob/main/rustls/src/conn.rs#L230

This problem can also be fixed if you change Vec::with_capacity(4 * 1024 * 1024) to vec![0; 4 * 1024 * 1024].

I believe this is because the poll_read call is passing in a large uninitialized ReadBuf, causing the stream to zeroing the ReadBuf unnecessarily.
https://github.com/rustls/tokio-rustls/blob/main/src/common/mod.rs#L218
We can do some optimizations on read_buf cfg. https://github.com/rustls/rustls/blob/main/rustls/src/conn.rs#L230

We could limit zero-initialization to the maximum TLS record size. On modern CPUs, a 16KB memset should not have a noticeable impact.

A possible solution could be the following. I think this is sound, since Reader is a concrete type whose behavior we know, and not a trait where adversarial implementations would be possible. But it seems a bit hacky.
I'm profiling this on an aws m6in.8xlarge instance, downloading from s3. In the flamegraph the memset with default buffer sizes was taking about 5% of time. The throughput is varying too much quantify the benefit.
The call stack is coming from hyper h1 poll_read_from_io, which seems  to create a new ReadBuf on every call, so maybe there is also potential improvement on that side.
diff --git a/src/common/mod.rs b/src/common/mod.rs
index fde34c0..a9e3115 100644
--- a/src/common/mod.rs
+++ b/src/common/mod.rs
@@ -248,6 +248,10 @@ where
             }
         }

+        // Safety: We trust `read` to only write initialized bytes to the slice and never read from it.
+        unsafe {
+            buf.assume_init(buf.remaining());
+        }
         match self.session.reader().read(buf.initialize_unfilled()) {
             // If Rustls returns `Ok(0)` (while `buf` is non-empty), the peer closed the
             // connection with a `CloseNotify` message and no more data will be forthcoming.

@seanmonstar do you think it's feasible to avoid recreating the ReadBuf on every call?

I suppose theoretically, but realistically at the moment, that ReadBuf is backed by the unfilled part of a BytesMut, which doesn't expose a way to know how much of it is initialized.

I think best way for now, apart from stabilize read_buf feature in std, is for rustls to provide a ReadBuf of own (or a trait to avoid unsafe in rustls).
like
pub trait ReadBuf {
    fn append(&mut self, buf: &[u8]);
}

pub fn read_buf(&mut self, buf: &mut dyn ReadBuf) {
    //
}

rustls can be asked how much data it would write into an infinite size buffer provided to reader().read() -- self.session.process_new_packets().unwrap().plaintext_bytes_to_read[^1] -- and I think it would be reasonable to expose that quantity as a new method on reader(). I think that would resolve the immediate issue (clearing an 4MB buffer to use the first 4 bytes).
[^1]: unwrap() is for brevity only!

I am considering using unbuffered api refactor, which would also solve the problem.


⚠ tradingpost.kiondaga.org has degraded performance

In 95e00c0, tradingpost.kiondaga.org (https://tradingpost.kiondaga.org) experienced degraded performance:

HTTP code: 200
Response time: 311 ms

Resolved: tradingpost.kiondaga.org performance has improved in f0fe96a after 1 minute.


Ability to use multiple apiKey entries in requests

As per issue #88

Please ignore this for the moment - forgot to branch and it's brought in other merges


Document is not clear

[Enter feedback here]
I was referring to assign subscription role for SPN, steps really confuses specially example tenant and billing id. reference screenshots also doesnt have correct reference.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 18b4787e-1e2f-dd28-b33b-0a220ad0819d
Version Independent ID: c663cfb2-3ea6-4a6e-9d88-f146526ead59
Content: Assign roles to Azure Enterprise Agreement service principal names - Microsoft Cost Management
Content Source: articles/cost-management-billing/manage/assign-roles-azure-service-principals.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@l-koppuravuri-BL
Thanks for your feedback! We will investigate and update as appropriate.

@l-koppuravuri-BL Thanks for your feedback.
Assigning to content author @bandersmsft   for review.

@l-koppuravuri-BL Thanks for your feedback.
Can you please explain more about what you mean about "assign subscription role"?
Are you referring to the SubscriptionCreator role? If so, the Cost Management + Billing engineering team has tested the procedure at https://learn.microsoft.com/azure/cost-management-billing/manage/assign-roles-azure-service-principals#assign-the-subscription-creator-role-to-the-spn, including the screenshots. Which screenshots do you think are incorrect?

#please-close


support sample count in prompt_viewer

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Add support to print multi samples from dataset
Modification
Add a for loop to extract multiple prompts
Checklist
Before PR:

[x] Pre-commit or other linting tools are used to fix the potential lint issues.
[x] Bug fixes are fully covered by unit tests, the case that causes the bug should be added in the unit tests.
[x] The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[x] The documentation has been modified accordingly, like docstring or example tutorials.

After PR:

[ ] If the modification has potential influence on downstream or other related projects, this PR should be tested with those projects.
[ ] CLA has been signed and all committers have signed the CLA in this PR.

Also, I'd like to add a subcommand to dump prompts to unified dataset format (jsonl, for example).

Also, I'd like to add a subcommand to dump prompts to unified dataset format (jsonl, for example).

Sounds cool!


Conversation Grouping

Like Chrome Group Tabs - read & experiment how that works and duplicate for whatsapp conversations

Already exists in Labels

(in whatsapp business)


tflite 2.0 gpu delegate error when inputs resized

Hi,
For gpu delegate if resizeInput is called and then runForMultipleInputsOutputs, there is an exception.

Mobile Samsung S9
Mali G72 GPU
Tensorflow lite installed from binary version 2.0
Development env, android studio on fedora 29

Example code:
fun resizeInput() {
            val options: Interpreter.Options = Interpreter.Options()
            val del = GpuDelegate()
            //options.addDelegate(del)
            val inter = Interpreter(AssetLoader.loadMappedBytes("best_model_shape_4x416x224_float32.tflite"), options)
            val sh = inter.getInputTensor(0).shape()
            inter.resizeInput(0, intArrayOf(1, 224, 416, 4))
            var inNumBytes = inter.getInputTensor(0).numBytes()
            var inputs = Array<ByteBuffer>(1) {
                ByteBuffer.allocateDirect(inNumBytes).order(ByteOrder.nativeOrder())
            }
            val outputs1 = Array<ByteBuffer>(inter.outputTensorCount) {
                val tensor = inter.getOutputTensor(it)
                ByteBuffer.allocateDirect(tensor.numBytes()).order(ByteOrder.nativeOrder())
            }
            val outputBuffers = outputs1.mapIndexed { index, byteBuffer -> index to byteBuffer }.toMap()

            inter.modifyGraphWithDelegate(del)
            inter.runForMultipleInputsOutputs(inputs, outputBuffers)
            DefaultLogger.verbose { "TfLite inference: ${inter.lastNativeInferenceDurationNanoseconds} ns" }

            inter.resetVariableTensors()
            inter.resizeInput(0, intArrayOf(1, 416, 224, 4))
            inNumBytes = inter.getInputTensor(0).numBytes()
            inputs = Array<ByteBuffer>(1) {
                ByteBuffer.allocateDirect(inNumBytes).order(ByteOrder.nativeOrder())
            }
            inter.runForMultipleInputsOutputs(inputs, outputBuffers)
            DefaultLogger.verbose { "After resize TfLite inference: ${inter.lastNativeInferenceDurationNanoseconds} ns" }
    }

TfLiteGpuDelegate Prepare: delegate is not initialized
Node number 70 (TfLiteGpuDelegateV2) failed to prepare.

Restored previous execution plan after delegate application failure.
at org.tensorflow.lite.NativeInterpreterWrapper.allocateTensors(Native Method)

Is this a bug or this sequence of operations is not supported for gpu delegate? I am using the Java API.
Regards,
Naveen

@karopawil I see two resizeInput.  Can you elaborate which of those are giving you the problem?

The second one. Basically once you have set GpuDelegate and then you call resizeInput, it leads to the exception.
Naveen

The problem is not directly due to resize, but with allocate Tensor call afterwards.

Hi, is there any update on this? Regards.

Sorry for the late reply; I was out on a conference & business trip.
resizeInput must be called before modifyGraphWithDelegate.  Tensor dimensions must be known upfront for GPU delegates, and the failure is expected.  For this to work (unless we make some bigger changes around the delegate), you would have to re-create an interpreter object.

Thanks for the clarification.


[Issue]: Entra ID based authentication support.

Describe the issue
Is there a way to use Entra ID based authentication for Azure Open AI resource instead of token based auth?
Steps to reproduce
No response
GraphRAG Config Used
No response
Logs and screenshots
No response
Additional Information

GraphRAG Version:
Operating System:
Python Version:
Related Issues:

Checking the code, I realized that leaving the api_key empty in settings.yaml file seems to do the job. Would be great to have this in the documentation.

Will make sure to put this in the docs! Thanks


Backpack Preview Bug

Describe the bug
On a regular backpack, it would show a preview of what's in the backpack. For example:

However, this backpack does not have a preview, picture is in the screenshot section.
Profile/Location
https://sky.shiiyu.moe/stats/Pigicial/Lemon
Check the ender chest on the 14th column and the 8 and 9th row.
Additional Info
None
Screenshots

Desktop (please complete the following information):
Windows 10 on chrome browser. Not sure on what version
Additional context
It could be a bugged backpack ingame, Im not sure though.

https://sky.shiiyu.moe/stats/Pigicial/Lemon
The large backpack is still broken

It most likely has nothing in it, which is why it is not displayed


[FLINK-8429] Implement stream-stream non-window right outer join

What is the purpose of the change
Implement stream-stream non-window right outer join. Most of the work has been done by FLINK-8428, this pr mainly adds tests for right join.
Brief change log

Add right join support during translateToPlan.
Add right join tests.
Update docs.

Verifying this change
This change added tests and can be verified as follows:

Added IT/UT/harness tests for right join

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

Thank you @hequn8128 for the good test coverage. The changes look good to me. I will merge this...


[$500] IOU - Repeatedly pressing same number shows a mark nearby

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to https://staging.new.expensify.com/
Tap Fab
Tap request money
Press the same number multiple times like 1 or 2 or 3

Expected Result:
When user presses same number multiple times also, number alone must be displayed
Actual Result:
When user presses the same number multiple times , nearby "1" number apostrophe like shown, similarly for "2", above and below a small line and while typing 3rd " 3" also we can note the apostrophe like
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.62-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/71a31eca-a587-4e77-a12a-99fbb985f30e
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011af9157d69c084d8
Upwork Job ID:<PHONE_NUMBER>756721664
Last Price Increase: 2023-09-11

That's pretty subtle, but I see it too through Browserstack

I see the problem in Chrome (mobile emulator). The possible issue in the viewport resizing — the number appears before the width resizes and because of that the apostrophe shows. Basically, if you take a look you will see that it's not an apostrophe but the front part of a number just appears before the width changes.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01006d6855461586ee

Proposal
Please re-state the problem that we are trying to solve in this issue.
When changing the text field on the request money screen, the next digit is partially shown for a brief moment.
What is the root cause of that problem?
The change made from issue #8158 added an additional width of 2 pixels to the Text component used to autoGrow the RNTextInput in BaseTextInput. The value of RNTextInput is changed prior to the Text component resizing, which shows a partial number.

Here is the same issue with a width of 8 pixels added, to emphasize the issue:
https://github.com/Expensify/App/assets/1709513/2788c426-2de2-4d80-b219-ea09d547ea0e
The change introduced in #9102 no longer seems to be necessary, as removing the extra width does not show any rendering issues on mWeb on either the request money or split bill screens.
https://github.com/Expensify/App/assets/1709513/18f84e37-a6bd-4e89-a3aa-a0f3058114b1
What changes do you think we should make in order to solve the problem?
Simply remove the extra added width in BaseTextInput makes the text render correctly.

What alternative solutions did you explore? (Optional)
None

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~016b88d5b00db11c11

I'm on parental leave; re-assigning! This has been triaged and is waiting for proposals.

@neg-0 Could you provide more details regarding suggested changes in your proposal?

@ArekChr Sure,
The proposed change is to remove the extra 2 pixels applied to the Text component that's being used to implement autoGrow in the BaseInputText component. The original intent of this padding was to fix issue #8158 but it seems that the root cause has been resolved and the extra padding is no longer necessary.
The code causing this issue is on line 396 of BaseTextInput.
https://github.com/Expensify/App/blob/3f61f61843a91dc2c4f0c3205b35b70dceb38eb7/src/components/TextInput/BaseTextInput.js#L385-L403
Removing the 2 pixels of padding on line 396 will prevent the portion of text from being displayed when the text value changes.

https://github.com/Expensify/App/assets/1709513/18f84e37-a6bd-4e89-a3aa-a0f3058114b1
Note: To dive deeper into this issue, there is actually a delay between when the text value of RNTextInput changes and when the size of the autoGrow Text component is computed. It's almost imperceptible and shouldn't be noticed by a user on a daily basis, so I'll divert to the Expensify team whether or not I should dive into finding a solution to synchronize these components.

Thanks for details @neg-0!

Note: To dive deeper into this issue, there is actually a delay between when the text value of RNTextInput changes and when the size of the autoGrow Text component is computed. It's almost imperceptible and shouldn't be noticed by a user on a daily basis, so I'll defer to the Expensify team whether or not I should dive into finding a solution to synchronize these components.

I didn't notice that issue after applying your changes, On which device did you notice that? Could you send a video that shows that sync issue?

@ArekChr Check out the video below. Like I said, very hard to notice at full speed. I turned on device throttling in Chrome to make it much more obvious. This is done on Windows Chrome but I can also notice it on Android native.
https://github.com/Expensify/App/assets/1709513/cf01266f-04ab-4981-a7dc-53cc8203818f

@neg-0 I think this might be done as a separate issue. It requires refactoring of baseTextInput and more changes in PR.
Your proposal looks good to me.
:ribbon: :eyes: :ribbon: C+ reviewed

In my opinion, a small UI tweak does not warrant a regression test. @ArekChr and I have discussed the need to eventually refactor this component to more elegantly render the text. A complete component refactor would involve much more work.

[x] Link to the PR: This component has had performance issues for a long time. It's hard to determine which PR introduced the regression.
[x] Link to comment: n/a
[x] Link to discussion: n/a
[x] Determine if we should create a regression test for this bug: I don’t think we need to add a regression test here.

Payment summary:
@neg-0 = $500 (no bonus)

@neg-0 I just sent you an offer in UW.

Everyone has now been paid so closing this.


Setup readthedocs and sphinx for the package.

[x] sphinx docs
[x] readthedocs

http://resonance.readthedocs.io


Mac OS X, watchOS, tvOS Support

I tried installing SwiftDate with Carthage, but only the framework for iOS was built.
This was pretty easy to fix by adding an OS X target, and a shared scheme for it as well. However, I also had to comment out everything in SwiftDate.h because it was importing UIKit. Is this necessary? It seems like other Swift-only libraries don't have one.
I could pretty easily add some targets and schemes to get it to build for other OSs as well, but what are your thoughts on SwiftDate.h?

When I was doing this yesterday, I realized I had a super old version of Carthage installed. I'll have to try this again with the new version and see if I still have the same problems. :sweat_smile:

@malcommac Can you answer this one pls?

Just added TvOS, OSX and WatchOS shared scheme frameworks: commit https://github.com/malcommac/SwiftDate/commit/430813365b877a26b12fe2c3067e661736c25feb.
@cjwirth can you confirm if it works fine for you?

@malcommac I can't seem to get it to work for the Mac platform.

@rcdilorenzo  (@malcommac) the source are not added into the OSX target "Build Phase" "Compile Sources"
@malcommac I think to keep same framework names for Carthage "product name" ("Build Settings") must be edited in OSX, TVOS, WatchOS target to replace $(TARGET_NAME) by SwiftDate

I just tried it right now, and this is what I got:
> mkdir test && cd test

> echo 'github "malcommac/SwiftDate"' > Cartfile

> carthage version
0.11.0

> carthage update
*** Cloning SwiftDate
*** Checking out SwiftDate at "2.0.2"
*** xcodebuild output can be found in /var/folders/2b/j65n_shn79v2m2zb93r6gqcc0000gn/T/carthage-xcodebuild.kBibXZ.log
*** Building scheme "SwiftDate" in SwiftDate.xcodeproj
2016-01-06 09:51:50.362 xcodebuild[35941:2131692] ### Failed to load Addressbook class CNContactNameFormatter
2016-01-06 09:52:02.041 xcodebuild[36005:2132008] ### Failed to load Addressbook class CNContactNameFormatter

> ls Carthage/Build
iOS

When I added the extra target/scheme and commented out the UIKit things, it did make multiple directories in my Build directory...

(on develop branch)
Just fixed the issue with compile files in OSX; it should now compile.
However SwiftDate.xcodeproj now uses CocoaPods and Nimble as framework so when I try to compile it I get: ".... ld: framework not found Nimble" (and I can't compile the xcworkspace used by cocoa pods to import Nimble).
I think the solution is to make a single independent xcproj without any reference to CocoaPods, add target to it and make another project with test files and link to nimble and cocoapods.
@Hout: do you agree?

I made some configuration changes so Quick/Nimble aren't included in the main framework, only the test target. I also got rid of some extraneous targets that didn't have to be there. Take a look at #141 and tell me what you think.

The change is quite big and needs investigation. I find the issue it tries to solve real though.
@malcommac we need time to investigate and we are already in the release of v3.0.0. Shall we line this one up for v3.1.0?

Go for 3.0. I'll investigate further this week to release a minor version update (3.0.1?) which enable this and carthage

Just solved in 3.0.1. Thank you for your report.
If you have problems make sure to remove Carthage folder in your project in order to do a clean fetch/clone/build.


Add changelog for release v0.10.0-alpha.2

What this PR does / why we need it:
This PR adds a changelog for the upcoming v0.10.0-alpha.2 release, targeted for today.
Does this PR introduce a user-facing change?:
NONE

/assign @kron4eg

/hold

/retest

/hold cancel


References and Test Interfaces

Hello, what is the main reference for this project? I want to learn it theoretically. I saw that you recently added python code. I tried to test but it failed. Can you add some test interfaces for some beginners to learn? Thank you.

Please have a look to the main website for this project: https://dcoeurjo.github.io/OTColorTransfer/
You'll find all references and basic instructions.


Certificate validation failed

good day, I am using ic-websocket v1.4.1 with frontend and getting error on open:
[certification] Witness != Tree passed in ic-certification utils.ts:55:11
isMessageBodyValid utils.ts:55
_isIncomingMessageValid ic-websocket.ts:510
_processIncomingMessage ic-websocket.ts:326
_processNext queues.ts:84
process queues.ts:69
addAndProcess queues.ts:51
_onWsMessage ic-websocket.ts:233
at the same time another error is printed in console:
[onWsMessage] Error: [onWsMessage] Certificate validation failed
_processIncomingMessage ic-websocket.ts:328
_processNext queues.ts:84
process queues.ts:69
addAndProcess queues.ts:51
_onWsMessage ic-websocket.ts:233
ic-websocket.ts:349:13
_processIncomingMessage ic-websocket.ts:349
_processNext queues.ts:84
process queues.ts:69
addAndProcess queues.ts:51
_onWsMessage ic-websocket.ts:233
on error callback gives me this:
Error:
error { target: null, isTrusted: false, message: "", filename: "", lineno: 0, colno: 0, error: Error, eventPhase: 0, bubbles: false, cancelable: false, … }

bubbles: false

cancelBubble: false

cancelable: false

colno: 0

composed: false

currentTarget: null

defaultPrevented: false

error: Error: Error receiving message: Error: [onWsMessage] Certificate validation failed

eventPhase: 0

explicitOriginalTarget: null

filename: ""

isTrusted: false

lineno: 0

message: ""

originalTarget: null

returnValue: true

srcElement: null

target: null

timeStamp: 6972

type: "error"

<get isTrusted()>: function isTrusted()

: ErrorEventPrototype { message: Getter, filename: Getter, lineno: Getter, … }
Lobby.tsx:97:24
I am using canisterActor created with dfinity Authclient and identity authenticated in local Internet Identity. I also tried using actor and canister id imported from declaration as in example, but it is the same. Env variables are loaded correctly, I checked it in console.
My code at frontend:
const icUrl = process.env.DFX_NETWORK === "local" ? "http://<IP_ADDRESS>:4943" : "https://ic0.app";
const gatewayUrl = process.env.DFX_NETWORK === "local" ? "ws://<IP_ADDRESS>:8080" : "wss://gateway.icws.io";
const wsConfig = createWsConfig({
canisterId: process.env.CANISTER_ID_GATEWAY!,
canisterActor: web3State.Gateway_actor,
identity: web3State.identity,
networkUrl: icUrl,
});
let websocket = new IcWebSocket(gatewayUrl, undefined, wsConfig);
I have no idea what is causing this error: the running local gateway server, my backend motoko canister, ic-websocket-sdk frontend library or maybe my dfx is somehow misbehaving?
Could you please help me pinpoint what is wrong?

Env variables are loaded correctly, I checked it in console.

Does this mean that DFX_NETWORK = local and that CANISTER_ID_GATEWAY = the canister id of the Motoko canister on which the IC WS Motoko CDK is installed and set up?
It looks like the certified data are not looked up correctly from the local replica certificate, and the causes can be many.
Also, have you tried resetting/reinstalling the Motoko canister before opening the frontend?

Good day, thank you for your reply! Here is the Gateway.mo canister that I am using: https://github.com/ktry1/Gateway_test/blob/main/Gateway.mo.
I have restarted pc, and deployed all canisters anew multiple times.
Variables that I am passing into createWsConfig, as gotten from console.log:
process.env.DFX_NETWORK: "local"
process.env.CANISTER_ID_GATEWAY: "be2us-64aaa-aaaaa-qaabq-cai"
canisterActor:
" Object { send_message_to_clients: handler(args), ws_close: handler(args), ws_get_messages: handler(args), ws_message: handler(args), ws_open: handler(args), Symbol("ic-agent-metadata"): {…} }

send_message_to_clients: function handler(args)

ws_close: function handler(args)

ws_get_messages: function handler(args)

ws_message: function handler(args)

ws_open: function handler(args)

Symbol(ic-agent-metadata): Object { config: {…}, service: {…} }

: Object { … }
Lobby.tsx:83:20
"
identity:
"Object { _inner: {…}, _delegation: {…}, _principal: {…} }

_delegation: Object { delegations: (1) […], publicKey: ArrayBuffer }

_inner: Object { _keyPair: {…}, _derKey: ArrayBuffer, _subtleCrypto: SubtleCrypto }

_principal: Object { _arr: Uint8Array(29), _isPrincipal: true }

: Object { … }
Lobby.tsx:84:20
"
networkUrl: "http://<IP_ADDRESS>:4943"

I think I found out what's causing this error. The problem is with the @dfinity/... dependecies. Due to https://github.com/dfinity/agent-js/pull/878, the certificates are handled a bit differently starting from v1.4.0.
My suggestion is to manually install the @dfinity/... packages dependencies with version v1.3.0 manually. Steps (execute them inside the frontend canister folder, if you've bootstrapped the project using the dfx new command):

remove the ic-websocket-js package:npm remove ic-websocket-js

remove the @dfinity/... packages:npm remove @dfinity/agent @dfinity/candid @dfinity/identity-secp256k1 @dfinity/principal

install the @dfinity/... packages with the correct version:npm install<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

install the ic-websocket-js package:npm install ic-websocket-js

build and deploy the canisters again:dfx deploy

I've tested these steps locally, and it seems that the issue is solved.
We'll update the SDKs packages to use the newest dependencies soon, so you won't need this workaround anymore.
I'm sorry for the late reply, feel free to close this issue if this is the solution.

Good day,  I would have never figured it out by myself 😁. Thank you very much for your reply - it worked, the frontend now successfully connects! 😊


Test UNA in Dolphin browser (especially for Android)

https://una.io/page/view-discussion?id=287

UNA works in Dolphin browser the same way as in Chrome.


Fix multilingual plus relativeURL removing the language URL section

Fix #7805
Add an optional param to GetDottedRelativePath to remove language prefix in URL if multilingual is enabled

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

@jmooring @bep this is ready for review.

https://github.com/gohugoio/hugo/issues/7805 is a configuration issue related to a "serverless" multilingual multi-host site. See this forum topic to learn how to craft and configure a “serverless” site.


update glow information

switch lock are working now for glow and onyx
target_temperature_high improve (error between high and low parameter)
heatzy_to_ha_state set to correct mapping
new feature : display 7°C to target temperature when preset mode is away

I don't understand how it was working before ? did someone with glow or onyx devices has something which works correctly ?

i'm glad to know there is a documentation...
You're right about the given values coming from the documentation, i'm wrong about none, comfort_1, comfort2
I didn't see PRESET_COMFORT_1 and PRESET_COMFORT_2 inside the heatzy app, maybe it is used when you use your radiator with a pilot wire.
for derog_mode, unfortunately, that's not what i see when i play with heatzy app and rectrieve data information by calling apis. But maybe i'm wrong, i will do other test now i have the documentation.
Thank you

i'm glad to know there is a documentation... You're right about the given values coming from the documentation, i'm wrong about none, comfort_1, comfort2 I didn't see PRESET_COMFORT_1 and PRESET_COMFORT_2 inside the heatzy app, maybe it is used when you use your radiator with a pilot wire. for derog_mode, unfortunately, that's not what i see when i play with heatzy app and rectrieve data information by calling apis. But maybe i'm wrong, i will do other test now i have the documentation. Thank you

I built version 6.4.1-beta2 which I think is the right configuration. Tell me what you think? Send a PR if it is not good. For info, I fixed the switch.py file because it did not work with other heatzy 's device versions


Make dependencies config generic

What this PR does / why we need it:
I'll work on it later, but removed from the doc to avoid being confusing.
Which issue(s) this PR fixes:
Part of https://github.com/pipe-cd/pipe/issues/979
Does this PR introduce a user-facing change?:

NONE

Thank you.
/approve


SVG for 'eyes' 1f440 is not transparent

The .png version of 1f440 is transparent but the .svg version has an opaque white background.

can i fix it manually? will you accept it?

Sure.