TMOP - option to specify target positions for some nodes

Does node fitting to given physical positions (instead of discrete zero level set).
Adds a small example tmop-fit-position. I decided to keep it focused and separate from the heavier TMOP miniapps. We can think of separating other capabilities into their own TMOP examples (like untangling). Where do you think it should go in the folders?

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3682
@vladotomov
@tzanio
@kmittal2 + @tzanio
6/4/23
⌛due 6/18/23
⌛due 6/25/23

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@vladotomov, can you resolve the conflict please?

@vladotomov, can you please resolve the conflicts when you get a chance?

Merged in next for testing...


.dockerignore file will not open in PHPStorm and icon has ?

Issue:
.dockerignore files created using the .ignore plugin show in the tree but the icon firstly shows a file with a overlaying question mark (?), each time i try to open the .dockerignore file generated i just get a flashing loading icon with no result.
Screen grab of issue: https://youtu.be/Sd2RVIfr2Bc
Platform:
Edition: Windows 10 Pro
Version: 1607
OS Build: 14393.1358
IDE:
PhpStorm 2016.3.3
Build #PS-163.13906.21, built on March 8, 2017
Steps taken:

Checked .ignore plugin for updates (up to date)
Checked IDE for updates (up to date)
Manually updated .ignore plugin to Version: 2.0.0-rc.1 (Same issues)
Checked for windows updates (up to date)
Restarted machine & all applications fully.

How to replicate

Install .ignore plugin
Right click on project tree root directory > New > .ignore file > select ".dockerignorefile (Docker)"
Check icon of newly created .dockerignore file to see if you get file icon with a question mark (?) or correct docker icon.
Try to open .dockerignore file in PHPStorm IDE without a flashing loading icon.
Confirm if file opens in the IDE (Mine do not ever open in PHP Storm) (I can open in another IDE i.e. Brackets, so ruling out corrupt file in my eyes.)

@StevenWillett Thank you for this report. As we can see in the Project View - .dockerignore file has a default IDE iconf for not recognized types (file icon with question mark).
Can you please check if in settings: Settings > Editor > File Types you have .dockerignore entry under the Docker group (the one with gray icon - I bet you have two Docker groups because of its plugin installed):

@hsz See attached, I cannot see .dockerignore in my recognised file types list which would explain the icon issue.

It should be fixed with #375 in the newest release.


Getting 403 while running examples

Scenario/Intent
[What are you trying to achieve but can't?]
Trying to run the examples like:

go run server_hardware.go
It returns:

Failed to fetch server List :  Error in response: Forbidden
Response Status: 403 Forbidden
Response Details: You are not allowed to access the requested resource.
exit status 1
Environment Details

Golang binding for HPE OneView Version: [Version of this module for which you are encountering the issue]
OneView SDK Version: [Version of the Oneview SDK for which you are encountering the issue]
OneView Appliance Version: [Version of the OneView appliance you're interacting with]
OneView Client API Version: [API version of your client object]
Golang Version: [Version of Golang in your environment]
Platform: [OS distribution and release version]

Using master code
OneView API Version: 1400
Platform: Ubuntu 18.04
Go version: go version go1.14.2 linux/amd64
Steps to Reproduce
[What are the complete steps needed to do in order to reproduce your problem?]
export env variables
run any sample example program
Expected Result
[What do you expect to happen after taking the steps above?]
If I run server_hardware.go, I would expect server list object
Actual Result
[What actually happens after the steps above? Include error output or a link to a gist.]
See above failure message

BTW - same username and credentials which I am using in env are working in UI as expected.

It was url value issue while setting the env variables. Sample code is working now. I will close this issue. Thanks.


new netgraph major release

Hi,
I saw on the github dashboard that you are using my package netgraph.
This is a heads up that I just released a new major version. I tried to maintain backwards compatibility as much as possible but I did break it in a few cases. Especially if your code uses either the Graph or InteractiveGraph classes, expect a few changes. Also, I have removed some InteractiveGraph derived variants for the time being, as they seem to be used very little but are a pain to maintain. If that affects you, please let me know, so we can work something out.
Hopefully, you will find that the improvements that I have made are worth any pains that might arise from upgrading. ;-)
Best,
Paul
PS: Feel free to close the issue any time.

Thanks so much for the heads up @paulbrodersen !


VMQ-Diversity: Passwords are logged in connection error message

Environment

VerneMQ Version: using docker image vernemq/vernemq:latest
OS: Debian 9
Erlang/OTP version (if building from source):
Cluster size/standalone: standalone
VerneMQ configuration (vernemq.conf) or the changes from the default

accept_eula=yes
allow_anonymous=off
log.console=console
log.console.level=debug
plugins.vmq_acl=off
plugins.vmq_diversity=on
plugins.vmq_passwd=off
vmq_diversity.postgres.user=dbuser
vmq_diversity.postgres.password=dbpassword
vmq_diversity.postgres.port=5432
vmq_diversity.postgres.host=db_ip
vmq_diversity.postgres.password_hash_method=crypt
vmq_diversity.postgres.database=test
vmq_diversity.auth_postgres.enabled=on

Expected behaviour
When a database connection error occurs, the log message detailing the error should not contain any user-supplied details that were used to set up the connection.
Actual behaviour
Whenever the following error occurs due to an issue we're resolving internally, the user-supplied details are logged in plain text, like the username and password.

[error] can't call function auth_on_register with args [{addr,<<"<IP_ADDRESS>">>},{port,58896},{mountpoint,<<>>},{client_id,<<"foo-client">>},{username,<<"foo">>},{password,<<"bar">>},{clean_session,true}] in "./share/lua/auth/postgres.lua" due to {throw,{error,not_connected}}

Since our logs are collected in a centralised storage I'd like to prevent this from happen to prevent leaking security-critical details.
I've looked in several places to see if this is perhaps something that can be configured, but I couldn't find anything indicating as such.

@Goost91 thanks, I agree this needs to be adressed. We either try to sanitize stuff in the logs, or take out those logs manually if this is possible.
This is currently not configurable as you have found already.

This circles back to https://github.com/vernemq/vernemq/issues/1017


No sound or vibration onto new notifications in Iphone XS

Hello all!
I have setup the package, following all instructions. I am coming here from react-native-push-notifcation (everything was working perfectly but had to update and use this package for iOS), and just started using this module for iOS notifications
I can receive notifications in every app state (foreground, background, app closed) and act on them perfectly.
The only thing that does not happen is vibration or sound when the notification comes in device...
I double checked that I followed every instruction. I am referring to remote notifications from Firebase.
Please help!

+1

+1

+1  @Naturalclar

I am using firebase_admin in python3. Here is an example of how to send an ios notification with a sound
from firebase_admin import credentials, messaging
firebase_admin.initialize_app(credential=cred, name=app)
message = messaging.Message(
notification=messaging.Notification(
title=title,
body=message,
),
android=messaging.AndroidConfig(
notification=messaging.AndroidNotification(
channel_id=CHANEL_ID.get(service)
)
),
apns=messaging.APNSConfig(
payload=messaging.APNSPayload(
aps=messaging.Aps(
sound=messaging.CriticalSound(
name='default'
)
)
)
),
data=data,
token=token,
)
firebase_response = messaging.send(message, app=firebase_admin.get_app(app))


COMP: Require only CMake Python3 components that are used in build

Updates to Python3 and relaxes CMake Python requirements so that only the component used in the build (interpreter) is required. Cherry-picks changes from https://github.com/clEsperanto/CLIc_prototype/pull/94 limited to CMake Python requirement.
Resolves ITKCLEsperanto build issue described at https://github.com/InsightSoftwareConsortium/ITKCLEsperanto/issues/30 where CLIc_prototype dependency fails to build in the absence of the Python development library. ITKCLEsperanto Linux Python builds successfully against this development branch: https://github.com/InsightSoftwareConsortium/ITKCLEsperanto/runs/8261050209?check_suite_focus=true.

Codecov Report
Base: 87.55% // Head: 87.55% // No change to project coverage :thumbsup:

Coverage data is based on head (0f82b9f) compared to base (19d5e18).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #100   +/-   ##
=======================================
  Coverage   87.55%   87.55%
=======================================
  Files         150      150
  Lines        7747     7747
=======================================
  Hits         6783     6783
  Misses        964      964

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

I think this was a relicate of the python wrapper build I was testing. Indeed, not needed here anymore.
My CMake structure is not the best made. If you see any way to improve it, do not hesitate!
Thanks again!


Done adding tags

Awesome work finishing session 1's assignment :partying_face:
See if you can finish session 0 as well

Awesome work finishing session 1's assignment :partying_face:
See if you can finish session 0 as well


docs: add link to source code & docs page in util page for easier access to see how the util is implemented and where the doc is located

@eneajaho is that still open?

@va-stefanek Yes of course. Feel free to take it!


Model for Stain4

To test the generalization of the model trained on Stain3 (and tested on Stain2), I will now evaluate it on Stain4. Based on the results, further advancements will be made by training on plates of Stain4 (and then evaluating on Stain2 and Stain3 in turn).
Stain 4 consists of 30 plates which were divided into 5 batches, each with different staining conditions.

Baseline staining conditions used in Stain3 (Stain2)
Baseline staining conditions used in Stain3 with 2-fold dilution of all dyes (Stain2_2)
Baseline staining conditions used in Stain3 with 2-fold dilution of Phalloidin (Stain2_Phalloidin_2)
Baseline staining conditions used in Stain3 with 2-fold dilution of Phalloidin and ConA (Stain2_Phalloidin_ConA_2)
Bray et al. staining conditions (Bray)

Apart from that, standard exposure vs. high exposure and Binning 1 vs. Binning 2 comparisons were also made.
To analyze the relations between the different plates in Stain4, I calculated the correlation between the PC1 loadings of the mean aggregated profiles of every plate. I only included the plates that were similar enough to form a large cluster.

Click here for clusters!

Click here for cells per well per plate! Only the plates I have downloaded so far are available, but will still give a good indication of this dataset

Benchmark Stain4

**  plate **
**  Training mAP BM **
**  Validation mAP BM **
**  PR BM **

BR00116630
0.31155545300649600
0.3137015194497950
53.3

BR00116625
0.3111799693928640
0.2868879397993790
58.9

BR00116631
0.29685278694807900
0.27565518819831600
57.8

BR00116627
0.30212568482745600
0.2931409543407390
56.7

BR00116630highexp
0.29234375449172200
0.30268598644488400
58.9

BR00116629highexp
0.29473182614969600
0.28881984493909600
52.2

BR00116627highexp
0.30536049808241300
0.26915793936424000
56.7

BR00116628highexp
0.3237434573920360
0.3069044968386820
57.8

BR00116625highexp
0.3174989239826670
0.2784561030266570
61.1

BR00116631highexp
0.2807715222921220
0.298022792943548
53.3

BR00116628
0.32245585156612100
0.29058423438922300
58.9

BR00116629
0.30300645187662600
0.285884661508691
52.2

First model trained on Stain4
Using the same setup as found in Stain3 (https://github.com/broadinstitute/FeatureAggregation_single_cell/issues/6#issuecomment-1095241531) I trained on plates BR00116625highexp, BR00116628highexp_FS, and BR00116629highexp. I only have 2 validation plates now, but will have more next week.
Results

TableTime!

plate
Training mAP model
Training mAP BM
Validation mAP model
Validation mAP BM
PR model
PR BM

Training plates

BR00116625highexp
0.62
0.32
0.33
0.28
97.8
61.1

BR00116628highexp
0.62
0.32
0.26
0.31
97.8
57.8

BR00116629highexp
0.58
0.29
0.34
0.29
97.8
52.2

Validation plates

BR00116630highexp
0.44
0.29
0.27
0.3
90
58.9

BR00116631highexp
0.38
0.28
0.21
0.3
85.6
53.3

Second model trained on Stain4
With slightly updated parameters according to https://github.com/broadinstitute/FeatureAggregation_single_cell/issues/6#issuecomment-1109028644 I now train on the same plates as before, but evaluate on all plates in the cluster.
Main takeaways

The model is able to generalize to most plates, although there are still 3 for which it does not beat the baseline validation mAP.
Although the 3 outliers are closely linked, they do not especially stand out when comparing them to the training plates using the PC1 loadings correlation plot. One possible improvement could now be to find a method that more accurately describes which plates are close to the training plates and which ones aren't.

plate
Training mAP model
Training mAP BM
Validation mAP model
Validation mAP BM
PR model
PR BM

Training plates

BR00116625highexp
0.75
0.32
0.36
0.28
98.9
61.1

BR00116628highexp
0.76
0.32
0.34
0.31
96.7
57.8

BR00116629highexp
0.75
0.29
0.32
0.29
98.9
52.2

Validation plates

BR00116631highexp
0.42
0.28
0.22
0.3
88.9
53.3

BR00116625
0.55
0.31
0.31
0.29
98.9
58.9

BR00116630highexp
0.47
0.29
0.27
0.3
91.1
58.9

BR00116631
0.42
0.3
0.21
0.28
94.4
57.8

BR00116627highexp
0.5
0.31
0.36
0.27
92.2
56.7

BR00116627
0.48
0.3
0.32
0.29
92.2
56.7

BR00116629
0.55
0.3
0.3
0.29
97.8
52.2

BR00116628
0.56
0.32
0.29
0.29
97.8
58.9

Using a rank based loss function
As described in Deep Metric Learning to Rank , I use the FastAP loss function which optimizes the rank-based Average Precision measure, using an approximation derived from distance quantization.
Hypothesis: by directly optimizing the mean Average Precision, instead of the Percent Replicating with the Supervised Contrastive Loss function, the model should generalize better to the ranking task (mAP).
Main takeaways

By optimizing for mean average precision we lose some performance on the Percent Replicating score, as expected. The distribution of the Percent Replicating histograms looks different as well.
I observe no significant increase in performance by training the model with the rank loss function.

Results

Table Results

plate
Training mAP model
Training mAP BM
Validation mAP model
Validation mAP BM
PR model
PR BM

Training plates

BR00116625highexp
0.66
0.32
0.36
0.28
95.6
61.1

BR00116628highexp
0.67
0.32
0.33
0.31
92.2
57.8

BR00116629highexp
0.68
0.29
0.3
0.29
86.7
52.2

Validation plates

BR00116631highexp
0.39
0.28
0.26
0.3
71.1
53.3

BR00116625
0.51
0.31
0.3
0.29
86.7
58.9

BR00116630highexp
0.44
0.29
0.29
0.3
76.7
58.9

BR00116631
0.41
0.3
0.25
0.28
77.8
57.8

BR00116627highexp
0.48
0.31
0.35
0.27
81.1
56.7

BR00116627
0.46
0.3
0.3
0.29
73.3
56.7

BR00116629
0.51
0.3
0.31
0.29
87.8
52.2

BR00116628
0.48
0.32
0.24
0.29
83.3
58.9

Percent Replicating graphs
Percent Replicating with rank based loss function

Percent Replicating with supervised contrastive loss function


json match throws error due to source attribute mismatch on windows terminal

/kind bug

What versions of software are you using?

Ran make test-cmd-cmp on windows.
Actual behavior
SSSSSCreated dir: C:\Users\Admin\AppData\Local\Temp\209745756
Creating a new project: xgvocbsngm
Running odo.exe with args [odo project create xgvocbsngm -w -v4]
[odo]  -  Waiting for project to come up  ...
[odo] I0615 05:53:34.877438    8988 occlient.go:543] Status of creation of project xgvocbsngm is Active
[odo] I0615 05:53:34.923391    8988 occlient.go:548] Project xgvocbsngm now exists
[odo] I0615 05:53:34.953368    8988 occlient.go:583] Status of creation of service account &ServiceAccount{ObjectMeta:{default  xgvocbsngm /api/v1/namespaces/xgvocbsngm/serviceaccounts/default 493ec3a9-5db9-4eae-ab6f-794c313ad5ed 42582 0 2020-06-15 05:53:35 +0000 GMT <nil> <nil> map[] map[] [] []  []},Secrets:[]ObjectReference{ObjectReference{Kind:,Namespace:,Name:default-token-mv29v,UID:,APIVersion:,ResourceVersion:,FieldPath:,},ObjectReference{Kind:,Namespace:,Name:default-dockercfg-dddjj,UID:,APIVersion:,ResourceVersion:,FieldPath:,},},ImagePullSecrets:[]LocalObjectReference{LocalObjectReference{Name:default-dockercfg-dddjj,},},AutomountServiceAccountToken:nil,} is ready
 V  Waiting for project to come up [1s]
[odo]  V  Project 'xgvocbsngm' is ready for use
[odo]  V  New project created and now using project: xgvocbsngm
[odo] I0615 05:53:34.974973    8988 odo.go:72] Could not get the latest release information in time. Never mind, exiting gracefully :)
Current working dir: C:\Users\Admin\go\src\github.com\openshift\odo\tests\integration
Setting current dir to: C:\Users\Admin\AppData\Local\Temp\209745756
Running odo.exe with args [odo component create nodejs cmp-git --project xgvocbsngm --context C:\Users\Admin\AppData\Local\Temp\209745756 --app testing -o json]
[odo] {
[odo]     "kind": "Component",
[odo]     "apiVersion": "odo.dev/v1alpha1",
[odo]     "metadata": {
[odo]         "name": "cmp-git",
[odo]         "namespace": "xgvocbsngm",
[odo]         "creationTimestamp": null
[odo]     },
[odo]     "spec": {
[odo]         "app": "testing",
[odo]         "type": "nodejs",
[odo]         "source": "file:///./",
[odo]         "sourceType": "local",
[odo]         "ports": [
[odo]             "8080/TCP"
[odo]         ]
[odo]     },
[odo]     "status": {
[odo]         "state": "Not Pushed"
[odo]     }
[odo] }
Deleting project: xgvocbsngm
Running odo.exe with args [odo project delete xgvocbsngm -f]
[odo]  V  Deleted project : xgvocbsngm
[odo]  !  Warning! Projects are deleted from the cluster asynchronously. Odo does its best to delete the project. Due to multi-tenant clusters, the project
may still exist on a different node.
Setting current dir to: C:\Users\Admin\go\src\github.com\openshift\odo\tests\integration
Deleting dir: C:\Users\Admin\AppData\Local\Temp\209745756

------------------------------
+ Failure [2.093 seconds]
odo sub component command tests
C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_sub_test.go:13
  Creating component
  C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/component.go:52
    should describe not pushed component when it is created with json output [It]
    C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/component.go:262

    Expected
        <string>: "...le:///./","..."
    to equal               |
        <string>: "...le://./","s..."

    C:/Users/Admin/go/src/github.com/openshift/odo/tests/integration/component.go:268

Expected behavior
json output should match all the attribute
Any logs, error output, etc?
Manually verified on windows.

I have gone through the official Microsoft documentation [1] and Wikipedia doc [2] on file URI.
As per Wikipedia doc [2] on file URI :
Over a network the file URI will be like file://localhost/ on both unix and windows setup and if the file is local then the URI will be file:/// on both platform
As per Microsoft documentation [1] on file URI :
File URI will be like - file:///sDrives[|sFile]. whereas sDrives Specifies the local or network drive.
BTW, In our case we are dealing with the local component dir which reflects file URI in the json output against the source key. May be we need to revisit the backend code regarding how the json output prints file URI differently for the same local component on different platform
Lets not add bandage through test script fix. So i am closing the pr until we get a proper fix. ping @girishramnani
[1] https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/jj710207(v=vs.85)
[2] https://en.wikipedia.org/wiki/File_URI_scheme
Slack discussion - https://openshiftdo.slack.com/archives/CQK6HE78S/p1592466401238200

I have changes the priority to high because we have already set up our periodic job on PSI for fedora, windows and macOS. However the platform specific issues are acting as hindrance for the test run, so IMO its high time we fix these bugs or test script issues.

@amitkrout @girishramnani  I have gone through the backend code and observed we are intentionally changing the source file uri on windows to get it work in url. AFAIU for not pushed component with local sourcetype, we get the source file uri from https://github.com/openshift/odo/blob/2e8304e3df88f4e2525863d082ba2f9b02634eeb/pkg/util/util.go#L203-L215 and this function intentionally converts the file uri for windows https://github.com/openshift/odo/blob/2e8304e3df88f4e2525863d082ba2f9b02634eeb/pkg/util/util.go#L212 by adding one more / . So its obvious to get "source": "file:///./" on windows. So I don't think we should look more into the code, this seems a fix from test side.

by adding one more / . So its obvious to get "source": "file:///./" on windows. So I don't think we should look more into the code, this seems a fix from test side.

odo code is not correct. It needs to be fixed there. file://./ is not a valid URI. Correct format is file:///./ no matter what OS is being used.

by adding one more / . So its obvious to get "source": "file:///./" on windows. So I don't think we should look more into the code, this seems a fix from test side.

odo code is not correct. It needs to be fixed there. file://./ is not a valid URI. Correct format is file:///./ no matter what OS is being used.

@kadel Yes, true but file:///./ URI make sense iff we have absolute source path refer [1] for more info. However AFAIU when we execute odo component create <cmp-name> -o json the generated source field takes relative location with dot-segment . ex "source": "file:///./" . Even the doc we were referring earlier [2] [3] only states about absolute path.
I have observed some conflicting backend code where we are using relative source path https://github.com/openshift/odo/blob/2e8304e3df88f4e2525863d082ba2f9b02634eeb/pkg/util/util.go#L203-L215 and writing unit test for absolute path https://github.com/openshift/odo/blob/master/pkg/util/util_test.go#L165 which means we need to handle both properly.
[1] https://stackoverflow.com/questions/7857416/file-uri-scheme-and-relative-files
[2] https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/jj710207(v=vs.85)
[3] https://en.wikipedia.org/wiki/File_URI_scheme


Deep Sleep Enable GPIO Wakeup() won't enable on S3 (IDFGH-12427)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
5.2
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
What is the expected behavior?
I'm following the IDF example in how to work with Deep Sleep.   I am not able to use this function:
esp_deep_sleep_enable_gpio_wakeup(BIT(DEFAULT_WAKEUP_PIN), DEFAULT_WAKEUP_LEVEL)
The include/source files require a definition of SOC_GPIO_SUPPORT_DEEPSLEEP_WAKEUP = 1
Compiler can't find this SOC_GPIO_SUPPORT_DEEPSLEEP_WAKEUP definition for some reason.
I have looked in header files, sdkconfig, Kconfig -- I just don't know where else to look to enable this setting.
Sometimes intellisense can see this setting in esp32p4\include\soc and sometimes it sees it in esp32c2\include\soc -- but this not correct because I'm setup for s3.
The setting and the functions are related to the component esp_hw_support and I have added that to my Requires CMakeLists file and this doesn't help at all.   There is a good chance that esp_hw_support is already a component in my project.
What is the actual behavior?
C:/Users//Desktop/ESP_Projects/v.5.2/project-name/main/main_sleep.cpp:24:5: error: 'esp_deep_sleep_enable_gpio_wakeup' was not declared in this scope; did you mean 'esp_sleep_enable_gpio_wakeup'?
Steps to reproduce.
Just try to use the function:
esp_deep_sleep_enable_gpio_wakeup(BIT(DEFAULT_WAKEUP_PIN), DEFAULT_WAKEUP_LEVEL)
Build or installation Logs.
No response
More Information.
No response

Hi, @SolidStateLEDLighting
The hardware of esp32s3 does not support waking up deepsleep through GPIO. The corresponding function can be replaced by ext0/ext1 wake-up source.     No wonder it didn't make sense to me.    Sorry to bother you on this... and I appreciate the guidance.
I just don't know why I didn't get this understanding from the documentation.

Give me a day, I'll close out this ticket.

Confirmed, the correct method for using GPIO (RTC pin) to wake from a deep sleep is to configure that input as an ext0 wakeup.


Add a reference to Cassandre trading bot

Hello, I developed a trading bot that uses XChange, maybe it would be a good idea to add list of tools that uses XChange on your readme ?
Sources
Guide

Thanks, I added it to the Wiki.


User should be able to connect account by deep linking

Child of #327

Needs investigation by Denis before estimation.

Could possibly be a blocker on Airgap side.... Denis to contact them in need


Remove constructor detect instanceof video

I am trying to fake a video object to use.
Because look like Browser play plugin don't use <video/>
For example: https://github.com/Kagami/mpv.js

ASS.js requires <video> to bind events, control playback, and so on. Faking a video object seems not easy.
#11 wants to use ASS.js without <video> too, I don't find out a general way to support those situation yet.

I am simulating an event on
ass.js need property and event
/**
* HTMLVideoElement
*
* HTMLElement -> HTMLMediaElement -> HTMLVideoElement
*
* https://developer.mozilla.org/en-US/docs/Web/API/HTMLVideoElement
* HTMLVideoElement.videoHeight :only
* HTMLVideoElement.videoWidth :only
*
* HTMLMediaElement.paused :only
* HTMLMediaElement.currentTime
*
* https://developer.mozilla.org/en-US/docs/Web/API/Element
* Element.clientWidth
* Element.clientHeight
*
*
* Events -> Media_events
* https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events
* play, pause, seeking
*/

But HTMLVideoElement.videoHeight And HTMLVideoElement.videoWidth only read
So can't use HTMLMediaElement
About event. My current solution is:
let video = document.createElement('div');
let event = document.createEvent('Event');
event.initEvent('pause', true, true);

video.dispatchEvent(event);


run standard library specs in release mode on travis

This should catch codegen bugs that only appear after LLVM optimizations.

Looks like it actually exposes a bug: https://travis-ci.org/crystal-lang/crystal/jobs/151792684

On my machine digest/sha1 specs fail with --release, I have no idea why

Actually, they fail with the current compiler, but not in the next one. I'll later try to see if it's an LLVM bug or there's a bug in the codegen.

When I discovered this on 0.18.7, digest/sha1 and one process spec were failing. The sha1 spec failing is quite concerning to me...

Bump on this, sha1 specs still fail in release mode on master which is super concerning to me.
Some of the bytes still get corrupted, for example:
  4) Digest::SHA1 does digest for "The quick brown fox jumps over the lazy dog"
     Failure/Error: bytes.to_slice.hexstring.should eq(hexdigest)

       expected: "2fd4e1c67a2d28fced849ee1bb76e7391b93eb12"
            got: "2fd480c67a2d28fced842be1bb76e7391b931212"

#triage
@jhass Is it worth rebasing this against master and having Travis try again? I tried today with Crystal 0.23.0+35 [890ab45bf] (2017-08-04) LLVM 4.0.1 - and it passed locally.

Sure why not, I hope memory consumption is low enough still.

Release mode doesn't pass for me, i'm trying to work out why right now. First guess from gdb is codegen is somehow passing uninitialized memory as the closure to a proc.

If this is rebased on master it should pass travis.


Prevent page reload when clicking menu item

Fixes #189

Can we test this?

I am failing to replicate the behaviour with Jest, using these approaches:
- check url after clicking anchor
- mocking history.push and expect(history.push).toHaveBeenCalledWith("/#")
- mocking window.location.reload and checking if this has been called
there it simply doesn't seem to be present, i.e. the test passes either way.
I would still like to merge this one since it's such a small QoL fix that shouldn't affect anything else.


[Bug][iOS] Clarity SDK Crash: NSInvalidArgumentException

Clarity Bug Report

Describe the Bug
The app crashes with an NSInvalidArgumentException, as reported in Firebase. This crash seems is related to the Clarity SDK and has been present since our app version 1.2.4. in this version, we only released Clarity

Repro Steps
Unable to reproduce the crash reliably. It appears to occur in some user environments without a consistent pattern.

Expected Behavior
The application should function normally without crashing, with the Clarity SDK integrated.

Screenshots
Not applicable as the issue occurs as a crash with no specific UI interaction.

Project Info
If required, the Project ID will be shared with<EMAIL_ADDRESS>along with the issue number in the subject line.

Platform/Framework Info

Device: Various, including iPhone models
OS: iOS SDK > 15
Application Framework: Native UIKit-based
Clarity Version: Unknown, likely the version included in app version 1.2.4

Additional Context
The crash stack trace indicates the issue occurs during animation handling, specifically related to the CA_interpolateValue method in QuartzCore and a missing UUID in the Clarity SDK.
Firebase Crash Report
    Fatal Exception: NSInvalidArgumentException
0  CoreFoundation                 0x83f20 __exceptionPreprocess
1  libobjc.A.dylib                0x172b8 objc_exception_throw
2  CoreFoundation                 0x18d480 +[NSObject(NSObject) _copyDescription]
3  CoreFoundation                 0x20fb4 ___forwarding___
4  CoreFoundation                 0x208d0 _CF_forwarding_prep_0
5  QuartzCore                     0xb4264 -[NSNumber(CAAnimatableValue) CA_interpolateValue:byFraction:]
6  QuartzCore                     0xb0b50 -[CABasicAnimation applyForTime:presentationObject:modelObject:]
7  QuartzCore                     0xc3878 CA::Layer::presentation_layer(CA::Transaction*)
8  Clarity                        0xc9524 (Missing UUID 0370cc1d---
9  Clarity                        0xc9e3c (Missing UUID 0370cc1d
10 Clarity                        0xc9e3c (Missing UUID 0370cc1d
11 Clarity                        0xc9e3c (Missing UUID 0370cc1d
12 Clarity                        0xc9e3c (Missing UUID 0370cc1d7
13 Clarity                        0xc9e3c (Missing UUID 0370cc1d777
14 Clarity                        0xc8ee4 (Missing UUID 0370cc1d7770379aa5a1d8e
15 Clarity                        0xc8b24 (Missing UUID 0370cc1d7770379aa5a1d8
16 Clarity                        0xf44d8 (Missing UUID 0370cc1d7770379aa5a1d8e
17 Clarity                        0xf3f98 (Missing UUID 0370cc1d7770379aa5a1d8eb
18 Clarity                        0xa1b18 (Missing UUID 0370cc1d7770379aa5a1d8eb
19 libdispatch.dylib              0x3dd4 _dispatch_client_callout
20 libdispatch.dylib              0x72d8 _dispatch_continuation_pop
21 libdispatch.dylib              0x1b1c8 _dispatch_source_latch_and_call
22 libdispatch.dylib              0x19d8c _dispatch_source_invoke
23 libdispatch.dylib              0x124b4 _dispatch_main_queue_drain
24 libdispatch.dylib              0x121b8 _dispatch_main_queue_callback_4CF
25 CoreFoundation                 0x56710 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
26 CoreFoundation                 0x53914 __CFRunLoopRun
27 CoreFoundation                 0x52cd8 CFRunLoopRunSpecific
28 GraphicsServices               0x11a8 GSEventRunModal
29 UIKitCore                      0x40aae8 -[UIApplication _run]
30 UIKitCore                      0x4bed98 UIApplicationMain
31 Fedshi                         0x80a4 main + 21 (main.swift:21)
32 ???                            0x1c1eef154 (Missing)

...

Labels: Crash, NSInvalidArgumentException, Clarity SDK, UIKit

Let me know if you need further details or clarification.

Hi @hamed-ice,
This issue should have been resolved in iOS SDK version 2.2.2. Please upgrade and let us know if you have any feedback.

Hi @hamed-ice,
This issue should have been resolved in iOS SDK version 2.2.2. Please upgrade and let us know if you have any feedback.

Hi @ibradwan , I'll update it and let you know the results after the new release.


Text color white in Template Library SearchBar.

Describe the bug
The text color is white inside the Template Library Search bar.
To Reproduce
Steps to reproduce the behavior:

Go to demo
Click on Template Library Component.
Type in search bar.

Expected behavior
The text color should be black so that it clearly differentiates it from the background color.
Screenshots

Additional context
I would like to work on this.

This has been fixed.


Update the Core Components Documentation

Can someone PLEASE update this documentation page?
There are 55 flows documented here, and there 98 flows in the Sept 2023 Core Components.

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

ID: e70f7e68-a58d-f9a1-1f2a-3f2bec8e58e2
Version Independent ID: 119292c3-9155-226c-8f26-9b92a86c0aa5
Content: Use core components - Power Platform
Content Source: power-platform/guidance/coe/core-components.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Thanks for your comment, @robertcaretta. This issue has been assigned to the doc author for review.


Bumping version to v11 in preparation for release

@AlexBulankou,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


should be converted to hooks, but for now fix for development environ…

…ment

This logic should be refactored into a hook that utilizes react-query

This does the trick!


Disable options

It would be convenient to be able to selectively disable options via a property of IMultiSelectOption.  It should be fairly easy to implement with a small change to setSelected and preventCheckboxCheck
Any chance of this getting implemented?

+1

I am also looking for this feature to be implemented.  Thanks in advance.

I am also looking for this feature to be implemented.  Thanks in advance.

+1

I would love to see this as a feature.

Hopefully they like it, test it and we can get it merged sooner rather than later.  In the mean time i left instructions on how you can use my own take on it via the pull request.


Unequal sequence length in MSA

Hi,
I was wondering why some MSAs, e.g. 102L_1_A consist of sequences of unequal length.
If I run the following code:
from Bio import SeqIO

for index, record in enumerate(SeqIO.parse("ProteinNet/raw/102L_1_A.a2m", "fasta")):
    if index > 4: break
    print("index %i, ID = %s, length %i"
          % (index, record.id, len(record.seq)))

I get the following output:
index 0, ID = XXXX_UPI00066315A6/35-154, length 165
index 1, ID = XXXX_UPI00066315A6/175-292, length 165
index 2, ID = TB_PC08_66DRAFT_100509362|3300000228|metagenome/9-106, length 165
index 3, ID = TB_PC08_66DRAFT_100509362|3300000228|metagenome/113-206, length 165
index 4, ID = JGI25909J50240_10726711|3300003393|metagenome/24-165, length 166

Index 4 has length 166, the others 165.
Can I pad the shorter sequences with '-' in the end?
Best
Christoph

The unequal length is due to an insertion in the fifth sequence (insertions are denoted by lowercase letters). The first sequence is the reference to which all other sequences are aligned. Dashes indicate gaps and lowercase letters insertions. I would not pad with -. If you want to get a standard alignment simply remove all lowercase letters.

Thanks for the clarification!


xdebug port

Hi.
You cannot use port 9000 for xdebug.remote_port since is already been used by PHP-FPM service.
It is a well know problem: https://www.theaveragedev.com/xdebug-and-php-fpm-configuration/
I suggest to you change the xdebug.remote_port to something like 9100 and add the note into the readme.
Regards.

@agarzon I didn't face any problem using it, did you face any problem?

@agarzon I  rechecked and tested the debug, and I cant seems to face any problem. as you can see in the image I didn't change the port and phpstorm is connecting to xdebug on port 9000 as normal.


chore(examples): compile & use scss in examples

Closes #72
This PR removes the custom stylesheets for each example and instead compiles the SASS locally to CSS, passes that to docs framework to be used in the examples, and then copies the compiled CSS to the dist directory.
Note: this will require design review - the shipped styles have not changed but the examples now differ in substantial ways such as blue borders at the top of Catalog Tiles.

Preview: https://react-catalog-view-pr-catalog-view-73.surge.sh

The preview loses the hover treatment background. Is this intentional that the vertical tabs don't get this treatment?


Added information about accessing host directory on Windows.

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-2" git@github.com:jaycode/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

@jaycode let us know if you're not available we can carry the PR

Please carry on with the PR for me, thank you,
Jay
On Wed, Apr 1, 2015 at 3:25 AM, Tibor Vass<EMAIL_ADDRESS>wrote:

@jaycode https://github.com/jaycode let us know if you're not available
we can carry the PR
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/11926#issuecomment-88233118.

Thanks for your contribution @jaycode ! I carried it at #11997


Cannot define static property with default value: array [$10]

Getting following error when compiling:
Cannot define static property with default value: array
Zephir version: 0.4.1a
Example:
class Foo
{
    const OP_TYPE_CREATE = "create";
    const OP_TYPE_INDEX  = "index";
    const OP_TYPE_DELETE = "delete";
    const OP_TYPE_UPDATE = "update";

    /**
     * @var array
     */
    public static opTypes = [
        self::OP_TYPE_CREATE,
        self::OP_TYPE_INDEX,
        self::OP_TYPE_DELETE,
        self::OP_TYPE_UPDATE
    ];

    /**
     * @param string opType
     * @return bool
     */
    public static function isValidOpType(string opType) -> boolean
    {
        return in_array(opType, self::opTypes);
    }
}
``

<bountysource-plugin>
---
There is a **[$10 open bounty](https://www.bountysource.com/issues/1946202-cannot-define-static-property-with-default-value-array?utm_campaign=plugin&utm_content=tracker%2F280146&utm_medium=issues&utm_source=github)** on this issue. Add to the bounty at [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F280146&utm_medium=issues&utm_source=github).
</bountysource-plugin>

@ovr @andresgutierrez
This and the other issue now indeed should be closed :)
(dont quite get why the merged commit didn't...)


💅 Change Modal styling

Current Stylings

Acceptance criteria

[ ] Work on styling modal
[ ] It should be responsive
[ ] Should use colors on basis of a theme change
[ ] Update the modal scroll bar
[ ] Add proper styling for list of PRs and PRs Status

GO, GIVE IT A TRY. 🚀

Don't forget to ⭐ this repo. This will help us in reaching a wider audience. Also, do share it with your friends and colleagues,

Thanks 😄

I will try this (Y)

I want to work on this, Please assign to me

@Emalsha & @Johnisaig You both can give it a try and will select the one which covers every criterion mentioned in the issue description 👍

#150

I did something like this ...


OpenAPI 3.0 securitySchemes fix for oauth2

Fix for securitySchemes validations in OpenAPI 3.0 for type "oauth2"
Ref: https://swagger.io/docs/specification/authentication/oauth2/
For OAS:
"securitySchemes": {
"oauth2": {
"type": "oauth2",
"flows": { }
}
}
This causes the code to fail at:
"authScheme = secDefinition.scheme.toLowerCase();" as scheme doesn't exist for type oauth2.
Thereby, causing 'Cannot call method 'toLowerCase' of undefined'.

When can this be merged?

@ErikWittern any change to merge some of the open PR's? Otherwise I will need to use my own fork, which I rather not do.

@niteshhegde Thanks for the PR!
@RolphH Very sorry for the late reply, and thanks for reminding me again. I merged also your other PR https://github.com/ErikWittern/openapi-snippet/pull/45 and published a new version 0.9.0


fix(readme.md): Add ./provision/kubeconfig to sops/flux setup.

Description of the change
Add --kubeconfig=./provision/kubeconfig option to sops/flux integration command.
Benefits
Return code 0!
Possible drawbacks
None that I know.
Applicable issues

Good find!


Live2D Android build issue

axmol version: https://github.com/axmolengine/axmol/commit/05e3ddd1a1cec564d65cda826d1ff150f23fdbc3
devices test on:
developing environments

NDK version: r23c
Xcode version: 14.2
Visual Studio:

VS version: 2019 (16.11), 2022 (17.6+)
MSVC version: 1929, 1934, 19.35, 19.36, 19.37
Windows SDK version: 10.0.22621.0

cmake version:
Steps to Reproduce:

Live2d has the following in Live2D/CMakeLists.txt:
if (ANDROID)
    target_link_libraries(${LIB_NAME} INTERFACE Live2DCubismCore)
else()
    target_link_libraries(${LIB_NAME} Live2DCubismCore)
endif()

Then when it calls setup_ax_extension_config(${LIB_NAME}), it links with Axmol:
function(setup_ax_extension_config target_name)
  set(options DNTLINK opt_DNTLINK)
  cmake_parse_arguments(opt "" "${options}" ""
                          "" ${ARGN} )

  target_link_libraries(${target_name} ${_AX_CORE_LIB})
...

It results in the following error when running cmake for the Android build:
CMake Error at G:/game_engines/axmol/extensions/CMakeLists.txt:14 (target_link_libraries):
The keyword signature for target_link_libraries has already been used with
the target "Live2D".  All uses of target_link_libraries with a target must
be either all-keyword or all-plain.

Is the "INTERFACE" scope required for Android in this line?
target_link_libraries(${LIB_NAME} INTERFACE Live2DCubismCore)
If it is required, then a suggested fix:
Adjust setup_ax_extension_config to allow for optional link scope argument, for example:
function(setup_ax_extension_config target_name)
  set(options DNTLINK opt_DNTLINK)
  set(options LINK_SCOPE opt_LINK_SCOPE)
  cmake_parse_arguments(opt "" "${options}" ""
                          "" ${ARGN} )

  target_link_libraries(${target_name} ${opt_LINK_SCOPE} ${_AX_CORE_LIB})

Which would be called like this:
setup_ax_extension_config(${LIB_NAME} LINK_SCOPE PRIVATE)
The above modification to setup_ax_extension_config has been tested, and it works, without affecting any other extensions.

lgtm, I think you can post a PR to fix it?

Sure, I'll post a PR up soon.


[FIXED JENKINS-28706] - Hide Docker Traceability Root Action by default

On the top of #11
@reviewbybees

:+1:

:+1: we must be using github wrong if we can't separate PRs built on top of PRs correctly... (or the tooling sucks)

if we can't separate PRs built on top of PRs correctly

A PR on top of another PR will show the cumulative diff: what you will actually get in master if you ask to merge it.
Generally you should review the upstream PR first, so it can get merged. Then if the author of the downstream PR does a git merge master && git push the cumulative diff will correctly show only that PR’s changes.


chore: remove unnecessary canvas dependency

PR Checklist

[x] Addresses an existing open issue: fixes #5059
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
canvas was only being used in code to load image sizes from OpenCollective sponsors. That was done to place precise widths on the homepage. This PR switches the images to instead use CSS to position their background image once in their center without repetition. Now there are no more image overflows at all.

Before
After

canvas was also a nested dependency via assetgraph-builder -> assetgraph-sprite -> canvas... but assetgraph-builder was also unused. 🔪

coverage: 94.337%. remained the same
when pulling dbf46ec263b35f82481bfe8a89471ae114f1d3b5 on JoshuaKGoldberg:remove-unnecessary-canvas-dependency
into 645469e1920e2e86458ff068e74eef2e2915083e on mochajs:master.


[Table] Single row edit mode

Internal repo 350
Summary
This allows users to quickly, and relatively simply edit individual records in a table, without needing to flip the whole thing into a bulk edit mode. Its mostly a nice UX affordance to reduce errors, but also likely helps performance where entire tables cannot be flipped into edit, then submitted.
Additional context
Add any other context or screenshots about the feature request here.

:tada: This issue has been resolved in version 2.80.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Backport WCT fix for editing DataGrid

There were two issues:

When Popup was taking a focus from DataGrid, editing cell was resetting, as popup doesn't have a VisualParent (only a logical Parent).
Same goes to the editing template column.

Both fixes were ported from WCT https://github.com/CommunityToolkit/WindowsCommunityToolkit/blob/main/Microsoft.Toolkit.Uwp.UI.Controls.DataGrid/DataGrid/DataGrid.cs#L5739-L5780

You can test this PR using the following package version. 11.0.999-cibuild0033246-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


RangeError: invalid array length when using step prop

When using step={0.1} or any number, the component fails to mount with error RangeError: invalid array length
<Slider
            minimumValue={sliderMin}
            maximumValue={sliderMax}
            progress={sliderValue}
            onSlidingComplete={handleSliderChange}
            containerStyle={{ height: 20, borderRadius: 100 }}
            hapticMode="both"
            step={0.1}
            onHapticFeedback={() => {
              Haptics.impactAsync(Haptics.ImpactFeedbackStyle.Light);
            }}
            theme={{
              minimumTrackTintColor: colors.blue[500],
              maximumTrackTintColor: colors.blue[100],
              bubbleBackgroundColor: "#666",
            }}
          />

I have encountered this issue as well, but turns out it is mostly a 'step' prop naming problem.
I expected this prop to be a dilution of a single slider move, but it is rather changing the amount of available slider "positions". Since positions count should be integer, the code should be something like this:
    <Slider
          progress={progress}
          minimumValue={min}
          maximumValue={max}
          step={Math.ceil((maximumValue - minimumValue) / step)} // Positions count, not a single step size
          onSlidingComplete={onValueChange}
      />

This way the slider positions count is calculated from the total slider range divided by some step size.
@alantoa, I think this prop should be renamed accordingly. The documentation also does not explain that it should be used that way.

I just ran into this same problem and in manifested in two separate points of confusion:

If you have too many steps, the bar looks like it "fills" with white, or whatever your mark style is set to. This was really confusing as the theme doesn't change anything and I couldn't reason about why the bar was filled in
Step is typically "by how much should each tick increase", at least on any other slider. I was setting this to a huge number and it makes the component lock up.

My use case is a real estate purchase price, so the slider is listing price +- 30% For a $500k home that's
$350,000 - $650,000
I wanted the step to be increments of $1k, so when I set step to 1000, it instead made one thousand marks.
Instead, I have to find the diff between my min max and then divide by the step I want
(max - min) / desiredStep = sliderStepTickCount
which then I have to round because step breaks on uneven numbers, and I need to limit it to something like 100 so it doesn't render too many marks.

Good call, I'll try to improve it.


Release 0.1

Prepare

[ ] Go through branches together: keep/ create PR/ delete

Do

[ ] Issues
[ ] PRs
[ ] Testing

Finalize

[ ] Check Readme @j-ti
[ ] Release 0.1.0 by changing setup.py, doc/source/conf.py and adding a tag to commit
[ ] Check all requirements
[ ] Fix flake8 warnings
[ ] Update Changelog ?
[ ] merge to master
[ ] :robot: :tada:

https://github.com/rl-institut/super-repo/blob/feature-11-release-procedure/RELEASE_PROCEDURE.md


Fix remove node from PublishedNodesCollection list

@dacolgit,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


meta data in nav.liquid

header already declared

Good catch, thank you! I'll have to fix the generation script, but this looks good.


PR for code review.

Comments from first round of review - if possible address before second route:
remove the manual list counters:
self._tasks = list()
self._ntasks = len(list)

# could be

self._tasks =list
@property
def ntasks(self):
    return len(self._tasks)

That can be applied to all counters you have.  The property can be public.
focus on one strand of API calls
Instead of supporting pipeline.add_stages() and pipeline._stages = [a, b, c], only support the former, ie. the one which does not rely on knowledge of the type and semantics of private members.
initial state is NEW
This does not make sense: self._state     = states.INITIAL - you assign a list of states here.  Always use NEW.  The purpose of initial would be something like this:
if task.state in re.INITIAL: print 'fresh'
if task.state in re.FINAL: print 'buried'

ie. it allows the user to do check for those states without knowing/caring what exact states are initial or final.
why a state history?
What is the use case for this?  The state models are linear, so if you find a task in state F, you know it had A, B, C, D, E before, in that order.  Where is this used?
efficiency:
            for task in self._tasks:

                for task_name in task_names:

                    if task.name ==  task_name:

                       copy_of_existing_tasks.remove(task)
                       copy_task_names.remove(task_name)

First, there is a break missing after the last line - otherwise you keep searching even after the match.  But also, this can be written as:
            task_map = {t.name : t for t in self._tasks}
            for task_name in task_names:
                if task_name in task_map:
                    self._tasks.remove(task_map[task_name])

No list copies, no nested loops, no breaks.  In fact, the above is the reason why RP keeps many information in dicts, like in self._pilots, because then this becomes:
   for pid in pilot_ids:
      if pid in self._pilots:
        self._pilots[pid].cancel()

etc.  You still can easily extract a set of instances, like:
pilot_ids = self._pilots.keys()
pilots_objects = self._pilots.values()

I understand your reason for set - but you some data structures are better matches for certain operations than others.
less type checking
       if 'uid' in d:
            if isinstance(d['uid'], str) or isinstance(d['uid'], unicode):
                self._uid   = d['uid']
            else:
                raise TypeError(entity='uid', expected_type=str, actual_type=type(d['uid']))

How often did it happen that a user stumbled over one of those errors, and it prevented something worse?  At least this should be:
self._uid = str(d['uid'])

which will barf if that conversion does not work.
check for empty list/sets
Instead of if self._tasks is None, use if not self._tasks
reconsider checks, or document them
        try:
            for task in self._tasks:
                if task.state not in [states.DONE, states.FAILED]:
                    return False
            return True

        except Exception, ex:
            print 'Task state evaluation failed'
            raise Error(text=ex)

Why can the try clause cause an exception?  Can task.state raise anything?  This is not immediately clear - so either comment why you try/except, or remove.
maybe use asserts?
As I said, I conceptually kinda like that you do many type checks and value checks - but they do clutter your code a lot, and distract from what it actually does.  Consider some of the above - and for things you must ensure, consider assert():
def _validate_tasks(self, tasks):

        """
        Purpose: Validate whether the 'tasks' is of type set. Validate the description of each Task.
        Details: This method is to be called before the resource request is placed. Currently, this method is called
        when tasks are added to the stage.
        """

        if not isinstance(tasks, set):

            if not isinstance(tasks, list):
                tasks = set([tasks])
            else:
                tasks = set(tasks)

        for t in tasks:

            if not isinstance(t, Task):
                raise TypeError(expected_type=Task, actual_type=type(t))

            t._validate()

        return tasks

could be:
def _validate_tasks(self, tasks):
    if isinstance(tasks, (set, list)):
        tasks = set(tasks)
  else:
        tasks = set([tasks]

    for t in tasks:
         assert(isinstance(t, Task))
         t._validate()

    return tasks

(although I would not assert this specific type, instead just call _validate...
ok, enough for now - take care :)


Beautify the projects popup

The popup which comes when you click on the coding image looks bland, can add css to beautify it. Can i start working on it? @kingsmen732 , if yes please add hacktoberfest label to this issue, thanks!

yes please
@Anurag519Narula


IPv6 support needed for failover of EIP's in Azure

Do you already have an issue opened with F5 support?
F5 ticket opened C3534813. F5 engineer had asked to open github issue.
Description

We are using both IPv4 and IPv6 addresses today ion-prem on our F5 devices which are HA pair, and are required to migrate the application and F5 services to Azure.
We have a requirement to continue to support both IPv4 and IPv6 in Azure, and we would like to use CFE for high availability because we need fast failover times to meet our strict uptime SLA.
We have compliance enforced by a 3rd party so changing these requirements may be complex.
With an internet-facing deployment of F5 VE in Azure that supports IPv6 VIPs, we need the CFE to support failover of these VIPs. Can you suggest any workaround or timelines so we can plan for this? Many thanks.

Note:  from https://clouddocs.f5.com/cloud/public/v1/azure_index.html
Currently, IPv6 does NOT support failover.
Environment information
For bugs, enter the following information:

Cloud Failover Extension Version:  Not validated
BIG-IP version: <IP_ADDRESS>
Cloud provider: Azure

Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 2
Severity level definitions:

Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
Severity 2 (High) : Defect is causing major obstruction of system operations.
Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.

Thanks reporting this enhancement request. This is a known issue and we are currently tracking it with internal ID AUTOSDK-46.


Node.js Impala client TapplicationException error

Hi ,
I am trying to connect to impala using the package and i'm getting the TapplicationExcpetion  error.
In server.js
var impala=require('node-impala');
app.post('/submit_dsp_block',function(req,res){
var day=req.body.day;
var limit=req.body.limit;
console.log(day);
console.log(limit);
console.log(impala);
var client = impala.createClient();
console.log(client);
console.log("trying to connect");
client.connect(
{
host:'<IP_ADDRESS>',
port: 21050,
resultType: 'json-array'
});
console.log("client connected");
client.query('select * from rpt.rptdaily limit 100')
.then(result => console.log(result))
.catch(err => console.error(err));
.done(() => client.close().catch(err => console.error(err)));
});
This is the console result in git bash:
node server.js
Example app listening on port 3000!
2016-08-15
100
{ createClient: [Function: createClient] }
ImpalaClient {}
trying to connect
client connected
{ [TApplicationException: Invalid method name: 'query']
name: 'TApplicationException',
message: 'Invalid method name: 'query'',
type: 1 }
Guess my client is getting connected, but there is problem with the query. Also how do i execute prepared query using node-impala , for example something like this
var day=req.body.day;
var limit=req.body.limit;
client.execute('select* from portal.pubdomainstats where day=? limit ?',[day,limit], function (err, result) {
if (err) {
return console.error('There was while trying to retrieve data from system.local', err);
}
I'm pretty new to node.js and would be helpful if I can get a layman's answer to my problem
Thanks

I changed the port to 21000 and I was able to execute the query and get the result set. Can anyone explain why..In our system Impala's port is 21050. Also how do I query and receive a large result set say ten thousand records using node-impala package. Once more thing, it would be great if someone helps me with the prepared query, i'm using a form to receive input parameters for my query.
Thanks

@nandakumar8 It needs the improvement that I've mentioned in the issue #4 to surmount result limit, and I'm not planning to do this in the near future. But of course you're free to contribute...
By the way port is 21000 in Cloudera check this link. 21050 is belongs to something else I don't remember right now.


Switch to a futures-compatible API

Implements #20
What does this do?
Instead of polling and waiting for events on the window directly, you first have to register your window on an events loop.
This events loop can then be polled (with poll_events()) or waited upon (with run_forever()), just like in the current API.
See the new window example for an example usage.
There are several advantages to this approach:

We can use the events loop to signal system-wide events that are not specific to a given window (eg. a new monitor was connected). The current Event enum has been renamed to WindowEvent, and a new enum named Event contains all the possible "global" events.
Creating multiple windows no longer requires creating one thread per window. This was especially problematic on Mac OS where it is forbidden to have windows in a non-primary thread. (EDIT: it may still be necessary to spawn an additional thread in winit's internals, but it's no longer necessary from the API point of view).
The fact that we pass a callback to the events loop (as opposed to an iterator) means that we can finally correctly handle resize events on OS X. The resize callback has therefore been removed.
The WindowProxy system has been removed.
The fact that was pass a callback also means that we can add a lifetime parameter to the Event struct if necessary (eg. to pass strings as &str instead of String).

Implementation strategy
In order to make the transition smoother and avoid having to rewrite all the implementation, I created a macro named gen_api_transition! which creates types that expose the new API, and internally uses the old API.
For the moment each backend invokes this macro in order to make itself compatible with the new API.
In the future, each backend should be rewritten to directly implement the new API without going through this macro. Once everything has been transferred, the macro should be removed.
The macro doesn't attempt to register a resize callback, because it was too complex. However it should be easy to pass callback events to the events loop if we modify the OS X backend.
A necessary change was that the frontend now uses a type named Window2 instead of Window. This should also be reverted once possible.
Close #20

Ping @glennw @jdm @ozkriff @mitchmindtree @kvark @retep998 @vberger (hopefully not forgetting someone)

Note: do not forget to test the Android build before merging.

I like this new API. 👍
As it matches pretty well the wayland event flow, it'll allow me to remove a large part of the current runtime overhead of the wayland backend.
Just, to make sure I got it correctly. From the point of view of the backends, doing the proper migration means implementing an EventLoop struct with this API:
impl EventLoop {
    pub fn new() -> EventLoop { ... }
    pub fn poll_events<F>(&self, cb: F) where F: FnMut(::Event) { ... }
    pub fn run_forever<F>(&self, cb: F) where F: FnMut(::Event) { ... }
}

and update the window internals to dispatch the events through the event loop. Is it correct?
Secondary question: is it supposed to be valid for an user to have more than one EventLoop, and manage them independently (possibly from different threads)?

Is it correct?

Yes, the backends are supposed to be exactly like the public API.

Secondary question: is it supposed to be valid for an user to have more than one EventLoop, and manage them independently (possibly from different threads)?

Yes, is it a problem?

Not at all, but this has consequences on the implementation, so I wanted to be sure we are on the same page.

It seems weird to me to provide a  run_forever instead of something like this:
pub fn wait_event<F>(&self, cb: F) where F: FnOnce(::Event) { ... }

..or just return the Event directly:
pub fn wait_event(&self) -> Event { ... }

Does it have to include the loop?
The run_forever version could be implemented on top of those as a convenience.

@darkstalker There's the problem of OS X which interrupts your main thread while your window is being resized, which means that the only way to do something is through the callback handler.

Let's do that final comment period thing for this design.
I'm probably a bit overprecocious here, but I don't want to change an "important" library's design on a whim.

@tomaka thanks for inviting the FCP. Is the expectation with this implementation that drawing should happen on a secondary thread?

@jwilm No. Today you usually do something like this:
loop {
    for ev in window.poll_events() {
        match ev { ... }
    }

    draw();
}

With the new API it would be something like this:
loop {
    events_loop.poll_events(|ev| {
        match ev { ... }
    });

    draw();
}

@tomaka oops, I missed the poll_events() mention at the top of the post. Thanks for the clarification there.
My other concern regards removal of the WindowProxy system. Is there another way to wakeup the run_forever loop? I currently depend on that functionality to multiplex window events with reading from a file descriptor on another thread.

Is there another way to wakeup the run_forever loop?

Yes, events_loop.interrupt() can be called from a separate thread and will wake up one instance of run_forever (similar to a condvar for example).

@tomaka perfect. This all sounds good!

It seems like the Window's poll_events and wait_events methods and their associated Iterators should also be removed as a part of this PR?

There's no poll_events and wait_events anymore in the public API, so I'm not sure what you mean.

It looks like they are still exposed here and here, unless I am mistaken?

There's a window_proxy_send.rs module in the tests directory that could probably be removed.

@tomaka should it be possible for a user to call poll_events or run_forever inside another call to poll_events or run_forever? E.g.
events_loop.run_forever(|event| {
    events_loop.poll_events(|event| {
        // ..etc
    })
})

The API as it is allows it, however this has some implications for the macOS implementation, as the macOS implementation must be able to share the user-given callback to each of the window delegate's callbacks (for resize, etc). I think I can allow this by keeping the user-given callbacks in a stack (there might still be other issues), but just thought I'd check that allowing this is intentional first.

A minor point: the following might be more ergonomic and suitable method names:

events_loop.poll_events(...) -> events_loop.poll(...)
events_loop.run_forever(...) -> events_loop.wait(...)

I think these are more concise while still making it obvious that we are polling or waiting for events. I think using wait is more suitable than run_forever as:

It is consistent with the old wait_events iterator and will make it more obvious to people switching over from the old wait_events API that this is method achieves the same behaviour.
The loop doesn't really run "forever" if it is interrupted.

Sorry for the late bike-shedding! Only just getting time to properly look over all this over the past couple days.

@tomaka should it be possible for a user to call poll_events or run_forever inside another call to poll_events or run_forever? E.g.

Maybe it's best to simply panic if the user does so.

I think using wait is more suitable than run_forever as:

The reason why I don't really like wait is that it makes you think that it will wait for an event or a set of events, and will automatically stop waiting afterwards.
Just run would be appropriate though I guess.

About the nesting, my wayland lib has a similar pattern, but the methods require &mut self on the event-loop. If there a reason this is not the case here?
With the wayland backend, nesting run_forever and/or poll_events calls will result in a deadlock.

About the nesting, my wayland lib has a similar pattern, but the methods require &mut self on the event-loop. If there a reason this is not the case here?

If it required &mut self you couldn't call interrupt anymore.

Oh, right., forgot about that.
I've solved this issue in wayland-client using an EventLoopHandle struct, which is given as a reference argument to the closure by the event loop. This handle providing limited control to the event loop, allowing only operations that are safe to do from within a callback. Might be an option here?

Well, the other reason is that ideally the events loop should be sharable amongst threads (even if that means that a mutex is used internally) unless there's a good reason not to.
I suggest that the code just panics if run_forever or poll_events is called while inside a callback.
This check could even be performed in the public code so that the behavior is the same amongst backends.

Ok, let's merge this.
The next steps are to write a PR that panics if we call a callback from within a callback, and to update the backends.


Trait 'Illuminate\Foundation\Auth\Access\AuthorizesResources' not found

On new laravel that the "Trait 'Illuminate\Foundation\Auth\Access\AuthorizesResources' not found" error is thrown since the AuthorizesResources trait has been merged with the AuthorizesRequests trait. Should remove the AuthorizesResources trait from file.

I believe I have fixed this in a pull request that I have merged a while back
Sent from my iPhone

On 3 Nov 2017, at 13:30, Erick Mabusi<EMAIL_ADDRESS>wrote:
On new laravel that the "Trait 'Illuminate\Foundation\Auth\Access\AuthorizesResources' not found" error is thrown since the AuthorizesResources trait has been merged with the AuthorizesRequests trait. Should remove the AuthorizesResources trait from file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Got the same problem here, would be nice to get fixed.

@ied3vil i think the pull is still open https://github.com/ied3vil/LanguageSwitcher/pull/12

#12 was just readme.md fixes!
https://github.com/ied3vil/LanguageSwitcher/pull/2

Please create a tag/release for this merge request. We now have to depend on the master. @ied3vil

@herrwalter added tagged version 1.1.1 that includes the fix. If you need anything else let me know


Using a default Field will crash when the type annotation references a class of the same name as the field

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Traceback (most recent call last):
  File "/home/louis/lab/tubeulator/pascalify/Journey.py", line 10, in <module>
    class X(BaseModel):
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 178, in __new__
    set_model_fields(cls, bases, config_wrapper, types_namespace)
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 452, in set_model_fields
    fields, class_vars = collect_model_fields(cls, bases, config_wrapper, types_namespace, typevars_map=typevars_map)
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic/_internal/_fields.py", line 122, in collect_model_fields
    type_hints = get_cls_type_hints_lenient(cls, types_namespace)
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic/_internal/_typing_extra.py", line 212, in get_cls_type_hints_lenient
    hints[name] = eval_type_lenient(value, globalns, localns)
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic/_internal/_typing_extra.py", line 224, in eval_type_lenient
    return eval_type_backport(value, globalns, localns)
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic/_internal/_typing_extra.py", line 240, in eval_type_backport
    return typing._eval_type(  # type: ignore
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/typing.py", line 327, in _eval_type
    return t._evaluate(globalns, localns, recursive_guard)
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/typing.py", line 693, in _evaluate
    type_ = _type_check(
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/typing.py", line 176, in _type_check
    raise TypeError(f"{msg} Got {arg!r:.100}.")
TypeError: Forward references must evaluate to types. Got FieldInfo(annotation=NoneType, required=False).

This is a very odd and specific bug, I've tried changing aspects of it and have whittled it down to the reproducible essence, as in this issue's title.

It only occurs when you use Field, even when equivalent to not using Field (i.e. = Field(None) rather than = None)
It only occurs when the field name matches the [forward referenced] field type name
It is not affected by stringifying the type

This isn't some contrived example, it came up when trying to codegen for the TfL API.
I think I can work around this, it's a shame that I can't use aliases in this way though.
Example Code
from __future__ import annotations

from pydantic import BaseModel, Field

class Aaa(BaseModel):
    b: str = None

class X(BaseModel):
    Aaa: Aaa = Field(None)  # This crashes
    # Aaa: "Aaa" = Field(None)  # Likewise
    # Aaa: Aaa = None  # This is fine

Python, Pydantic & OS Version
pydantic version: 2.6.4
        pydantic-core version: 2.16.3
          pydantic-core build: profile=release pgo=true
                 install path: /home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic
               python version: 3.10.14 (main, Mar 21 2024, 16:24:04) [GCC 11.2.0]
                     platform: Linux-5.15.0-91-generic-x86_64-with-glibc2.35
             related packages: typing_extensions-4.10.0
                       commit: unknown

@lmmx,
Thanks for the detailed bug report. I know that @Viicos worked on a PR recently to disallow / warn for cases similar to yours above. @Viicos, any idea why that wouldn't take effect for this case (when running on main, where your change is active).

Aaa: Aaa = Field(None) should have been caught by https://github.com/pydantic/pydantic/pull/8243, however I don't think it works with the __future__ import. I'll try to take a look at it and see if it can be handled as well.
Aaa: Aaa = None seems to be the same as https://github.com/pydantic/pydantic/pull/8243#issuecomment-1831900199, and can be very misleading as the Aaa annotation will take the value of None.
@lmmx My suggestion is to follow the alternatives mentioned here. I know this isn't perfect but Pydantic is limited by the annotation evaluation of Python (assignments are evaluated before annotations, meaning when Python tries to evaluate Aaa, it uses the assigned value in the class as it is in the same class scope). I'll also note that type checkers won't support the annotation as well (see this screenshot).
To catch this kind of issues, I wrote a Flake8 plugin (rule can be found here). This detection could be implemented in Pydantic but it would require parsing the AST which isn't an ideal solution considering it would slow down model creation.

Thanks for the prompt triage @sydney-runkle and explanation @Viicos ! Best team :muscle:
Due to the specific [imposed] requirements I have in this project:

The code is codegen'd, some keys in the JSON it parses are reserved words in Python so would be illegal [in the AST] to leave as model field names, hence must be aliased from camelCase to PascalCase
There are cyclic inter-model references (so forward refs must be stringified with the future annotations import)

mean that I can't use the alternatives but good to know!
I've opted to go with an AliasGenerator for now which seems to do the trick for my needs, still wanted to report it back to base :-) Plugin looks great too, I use flake8 all the time (even though my pre-commit is in ruff now so cool to see the plans for that!)
I went back and checked your warning that a stringified annotation - one example is the Identifier model I generated here which includes such a field:
class Identifier(BaseModel):
    Crowding: Crowding = None

Indeed you were right :face_exhaling:
>>> from tubeulator.generated.Journey import Identifier
>>> Identifier.model_validate({})
Identifier(Id=None, Name=None, Uri=None, FullName=None, Type=None, Crowding=None, RouteType=None, Status=None)
>>> Identifier.model_validate({"crowding": {}})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/louis/miniconda3/envs/tubeulator/lib/python3.10/site-packages/pydantic/main.py", line 509, in model_validate
    return cls.__pydantic_validator__.validate_python(
pydantic_core._pydantic_core.ValidationError: 1 validation error for Identifier
crowding
  Input should be None [type=none_required, input_value={}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.6/v/none_required

Thanks for the specific warning there, I thought I was good to go ahead !

I use flake8 all the time (even though my pre-commit is in ruff now so cool to see the plans for that!)

My plan is to implement these rules at Ruff at some point (but still need to a bit more familiar with Rust first). But yeah aliases seems like a good option

@Viicos, do you think this still fits within the scope of v2.10?

I'd say we should close it given we can't really do much here as said in the previous comments


Map<String,List can't save to mongodb

public class UserData{
@id
String id;
public Map < String, List < String >>  data=new HashMap < String, ArrayList < String>>();
}
when I save a UserDate to mongodb ,I catched the exception
org.mongodb.morphia.mapping.MappingException: Error mapping field:*******************
at org.mongodb.morphia.mapping.Mapper.toDBObject(Mapper.java:578)
at org.mongodb.morphia.mapping.Mapper.toDBObject(Mapper.java:558)
......
Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to com.mongodb.DBObject
at org.mongodb.morphia.mapping.EmbeddedMapper.writeMap(EmbeddedMapper.java:118)
at org.mongodb.morphia.mapping.EmbeddedMapper.toDBObject(EmbeddedMapper.java:28)
at org.mongodb.morphia.mapping.Mapper.writeMappedField(Mapper.java:668)
at org.mongodb.morphia.mapping.Mapper.toDBObject(Mapper.java:576)
... 29 more

Can you please post a test case to the mailing list and we'll try our best to get you sorted out.  Thanks.

I found the tests that I thought was covering this use case but they were testing something almost the same but not.  I have it fixed in master.


adding support for mouse events to IconMenu

I believe it was intended for this to work with mouse events as well as
touch events. In my project the mouse events were not working correctly
until I added this bit of code. I tested it when nested in a AppBar’s
iconElementRight and when on it’s own.

The onTouchTap is also supposed to be triggered  by a mouse event.

In my project the mouse events were not working correctly

Can you be more specific?

Sure - this is my usage:
https://github.com/chrisgervang/pickoleon/blob/master/app/src/components/PickleBrowser.jsx#L34-L37
Hmm. What I am curious about is that it seems to work in the hosted docs, but not on my machine. I don't think I'm using it differently than the docs though.
If it means anything, I'm on OSX using latest Chrome release.

Are you starting the React-tap-event-plugin?
http://material-ui.com/#/get-started/installation

I am not. Seems weird to me that I'd need that if I'm not using touch in my app.

Yes, that's required. The main benefit of it is to remove the 300ms delay of Safari iOS.
I agree, would be better to not be required. Another solution would be to use onClick and to emulate the onClick on Safari iOS

Hmm is that trivial to do?
After including following the instructions IconMenu does appear to actually work. I'm going to close this PR because it doesn't seem necessary to fix right now.

It's not trivial but we could suggest to use https://github.com/ftlabs/fastclick instead.


[FEATURE] Desktop: Default "VIAME_DATA" storage dir has aggressive title

Recommend changing to "VIAME Data" or "viame data" or just "VIAME" to match the case of most linux systems, not sure what's best here but by default it stands out and doesn't match any default cases for the folders in user home dirs

Should probably make it Dive_Data instead, since this isn't something we can customize per-user and the data in that directory has nothing to do with VIAME.  We don't want to confuse users about where their VIAME install is.


API endpoint for car image

Is there an API endpoint to get the car image?

There doesn't seem to be, but that would be amazing.


Components such as Slider and Carousel is not compatible with App router.

Which package has an issue?
@yamada-ui/react
Package Version
1.2.6
Description
When using Slider or Carousel components on App Router, they do not display or display incorrectly. This applies to components that use fineChildren or pickChildren internally.
Target components

AccordionItem
Carousel
FormControl
Dialog
Drawer
Modal
PopoverContent
RangeSlide
Slider
Stat
Tabs

Link to Reproduction
No response
Steps to Reproduce

Use Slider and Carousel components within the App router.
See display.

Browser
Chrome
Operating System

[X] macOS
[X] Windows
[X] Linux

Do you know how to fix the issue?
None
Are you willing to participate in fixing this issue and create a pull request with the fix?
None
Additional Information
No response

The solution is to "use client".


Improve typehints of xr.Dataset.getitem

To resolve some common type-related errors, this PR adds some overload type hints to Dataset.__getitem__. Now mypy can correctly infer that hashable inputs return DataArrays.

[x] Closes #4125
[ ] Tests added
[x] Passes isort -rc . && black . && mypy . && flake8
[ ] Fully documented, including whats-new.rst for all changes and api.rst for new API

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

In the file xarray/core/dataset.py:

Line 1244:1: W293 blank line contains whitespace
Line 1246:5: E303 too many blank lines (2)
Line 1247:5: E704 multiple statements on one line (def)
Line 1250:5: E704 multiple statements on one line (def)
Line 1250:40: F821 undefined name 'Dataset'

The mypy check throws an error: xarray/core/dataset.py:1250: error: Overloaded function signature 2 will never be matched: signature 1's parameter type(s) are the same I think you can ignore the other failures. Should that be:
    @overload
    def __getitem__(self, key: Hashable) -> DataArray:
        ...

    @overload
    def __getitem__(self, key: Iterable[Hashable]) -> "Dataset":
        ...

? Only guessing, though - it was Any so there may be more options. @crusaderky

@mathause On further consideration, I think it might not be possible to get this to work. This method has three behaviors:

Mapping -> Dataset
Hashable -> DataArray
else (List): -> Dataset

With my limited understanding of mypy, I think that any two of these is supported by overload, but I'm not sure it's possible to support all 3 with overload. I tried several different options.

Okay. Assuming the tests pass, I think this is ready for review. I tried adding a test, but mypy didn't seem to find problems even with code that I know doesn't work (e.g. 'a'+ 1). Is there some strategy for testing tricky type hints like this?
In any case, this code does work:
$ cat test_mypy.py                                                                                (fv3net)
import xarray as xr
ds = xr.Dataset({"a": ()})

arr = ds['a']
union_obj = ds[['a']]

reveal_locals()
$ mypy test_mypy.py                                                                                (fv3net)
test_mypy.py:8: note: Revealed local types are:
test_mypy.py:8: note:     arr: xarray.core.dataarray.DataArray
test_mypy.py:8: note:     ds: xarray.core.dataset.Dataset
test_mypy.py:8: note:     union_obj: Union[xarray.core.dataarray.DataArray, xarray.core.dataset.Dataset]

Seems this was already discussed in GH3210 (comment) and see also the TODO:
https://github.com/pydata/xarray/blob/8f688ea92ae8416ecc3e18f6e060dad16960e9ac/xarray/core/dataset.py#L1244-L1250
(although it is not entirely clear to me whether this is actually fixed or not)

Nice find @mathause ; I remember that discussion now.
As @nbren12 said, this doesn't go all the way given mypy's restrictions, but seems like a dominant improvement.
Test failures are unrelated.
Thanks @nbren12 !

No problem! I think I am done with this one unless you think its important that I document or test this somehow. Can someone review it?

I took the liberty to rework it, please have a look
Test script:
from typing import Hashable, Mapping
import xarray
ds: xarray.Dataset

class D(Hashable, Mapping):
    def __hash__(self): ...
    def __getitem__(self, item): ...
    def __iter__(self): ...
    def __len__(self): ...

reveal_type(ds["foo"])
reveal_type(ds[["foo", "bar"]])
reveal_type(ds[{}])
reveal_type(ds[D()])

mypy output:
t1.py:12: note: Revealed type is 'xarray.core.dataarray.DataArray'
t1.py:13: note: Revealed type is 'xarray.core.dataset.Dataset'
t1.py:14: note: Revealed type is 'xarray.core.dataset.Dataset'
t1.py:15: note: Revealed type is 'xarray.core.dataset.Dataset'

@crusaderky Thanks for the re-work. For my own benefit, could you explain why that code worked? I remember writing something very similar, and running into mypy errors. <y understanding of how mypy intreprets overload seems incomplete.

@nbren12 it seems to me that mypy is being overly aggressive when parsing the hinted code (hence why I had to put # type: ignore on it) but it is being more lax when the same code is invoked somewhere else like in my test script. Overall I suspect it may be fragile and break in future mypy versions...


Test cases are failing and code coverage is not working

Right now I believe the first test case is failing, which is breaking the whole pipeline.
We'll look into it and update

The issue seems to be intermittent when the bots are run at very short interval over and over again.
Wll not be fixing as of now.


[webview_flutter] Add a getTitle method to WebViewController

Description
Allows inspecting the title of the currently loaded page.
Related Issues
https://github.com/flutter/flutter/issues/37177
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

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

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Could this possibly be a Stream<String> as the title may whenever the web view loads the next page?

Could this possibly be a Stream<String> as the title may change whenever the web view loads the next page?

Actually no need, there's a page listener that's called when a (or any further) page is loaded, so developers could use that. :-) Ignore my original comment.

Could this possibly be a Stream<String> as the title may change whenever the web view loads the next page?

Good point, thanks!
I think a broadcast stream makes sense for this case, though I think we would still need this getter for the "current" value (as broadcast streams drop values if there are no listeners).
WDYT?

Could this possibly be a Stream<String> as the title may change whenever the web view loads the next page?

Actually no need, there's a page listener that's called when a (or any further) page is loaded, so developers could use that. :-) Ignore my original comment.

Your comment is still valid as the title might change without a new page being loaded (e.g javascript code can change the title).
I do think it still makes sense to to have this getter as I commented above though.

If JS code can change the title, we'd need to fiddle with the html to get it, unless WebView has some sort of listener we can hook into.
From my point of view, the current PR (to get the title) provides enough of a building block to build a stream of titles later when combining this with the page listener and perhaps other methods (even a Timer.periodic..).
Thx @amirh.

If JS code can change the title, we'd need to fiddle with the html to get it, unless WebView has some sort of listener we can hook into.
From my point of view, the current PR (to get the title) provides enough of a building block to build a stream of titles later when combining this with the page listener and perhaps other methods (even a Timer.periodic..).
Thx @amirh.

Yes such listeners are available on Android and iOS.
Anyway going to land this PR as-is it seems that we all agree this getter makes sense.


example_nav2 on web. Navigator.onGenerateRoute was null

I have downloaded and run your example_nav2 application on Chrome. So trying it for web.

Switched to Profile or Products page on Bottom nav bar.
Refreshed the page (or copy and paste the url to another window) and got below error.
Refreshing on Home page it is not giving the error.

How to solve this problem? Thanks.

One more issue about same example

App started on Home page on Chrome
Go to Profile (click on bottom nav)
Go to Products (click on bottom nav)
Back to Profile by clicking browser's Back button (Profile page is empty, error1)
Back to Home by clicking browser's Back button (Home page is filled)
Click to browser's forward button (Profile page is still empty)
Click to browser's forward button (Products page has error, error2)
Click to browser's back button (Profile page has error, error2)

error1:

error2:

error3:

Clone this repo instead of the current one https://github.com/Bdaya-Dev/getx

Clone this repo instead of the current one https://github.com/Bdaya-Dev/getx

Thank you. I have noticed your pr after opening this issue. Im checking it right now.

@ahmednfwela
Seems that browser navigation problem solved. Thank you.
Home or Settings own views not loaded when I select one of them on drawer. Page not changed, only route url updated on AppBar.title.
if I refresh the page, it lost AppBar.title also.

All of these problems are fixed now in the new PR

All of these problems are fixed now in the new PR

Thank you for your help. It looks very nice.


Extract vector representation of molecules

Is it possible to use the program just to encode a set of molecules in an sdf file to the vector representation? I would like to use this representation as feature vectors in my code for binding affinity prediction.

Did you ever figure out if that's possible? I have a similar task right now, and would also require the vector representation.

I attempted to modify the code to work with the latest Python version and upgrade all the dependencies to the current versions but I had to correct too many exceptions, thus I stopped at some point cause it wasn't worth the time.

I did not try but this should be possible.
If the code is still working, the output of the encoder should be the latent-space encoding.


Sane and documented defaults

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment
Same as https://github.com/quantopian/zipline/issues/2195
Description of Issue
I started my backtests and got interrupted by a ValueError: 'Time Period' is not in list. I tracked it down to the Federal Reserve's data download website not working; as a result, all of my backtests are blocked, and I don't even use a benchmark in these specific backtests.
As an addendum, I discovered that Zipline automatically inserts a default commission model whereas I would have expected there to be none -- and couldn't find anywhere in the documentation what this default model was or how to recover it from the module.
Both of those are design decisions which make Zipline of course more "batteries included", but one relies on hardcoding the URL of an external service which can't be controlled, and the other makes silent assumptions on the analyst's needs. I appreciate an "opinionated defaults" approach may be intended by the team (and is in fact the same approach I found in every other backtest software, most of which go all the way through defining proprietary languages), but it greatly hinders flexibility for those who need it. I would suggest to set sane defaults (no benchmark required/lazy benchmark downloading, no commission model, ...) and document in a detailed manner how to configure each of those aspects.
Thanks again for your patience!
Andrea

@ssanderson, you definitely have a good point. I guess it depends on the analyst's modus operandi. I, for example, tend to backtest with zero commissions and slippage first in order to test the theoretical effect of a given market anomaly, and only later work on a good execution model (i.e. filtering the number of trades and whatnot). That's why I think having a zero-fee commission model is reasonable, besides the fact that any default non-zero-fee model is going to end up different from actual brokers' fee schedules. But this is far from an exact science and, as long as all the influences that come into play are correctly taken into account, my approach is as good as any.
With that being said, I don't think it's that big of an issue and, whatever choice ends up to be taken on the matter, it can simply be solved by thoroughly documenting what the default model is, what are the reasons it is like that and so on, so that the user can make an informed choice.