HIP XX Crowdspot Modifications

HIP XX: Crowdspot Modification

Author: Tony12times
Start date: 2023-05-17
Category: Meta
Original HIP PR:
Tracking Issue
Voting Requirements: veIOT

Summary:
There will always be gamers, therefore there will always be a need for policing those bad actors.  The proposals of this HIP aim to reinforce the impact of the denylist as a whole.  Penalties for POC gaming under this proposal are more harsh than the current process.
Incidentally, there will occasionally be falsely accused hotspots.  This HIP seeks to identify and clear those falsely accused in a timely manner.
The two main goals are reducing bad actors on the network and returning false positive cases to active status in a timely manner. These goals will be accomplished by two innovative steps.   First, a Staking Bond will be required to request any removal submission on Crowdspot.  Secondly, a "two & banned" process is established on Crowdspot to end the revolving door of appeals of the denylist.
Motivation:
The current process and flow of the Crowdspot submissions is 4 months backlogged and in desperate need of attention.  The requests to Crowdspot will continue to grow if the process isn't improved. This has resulted in thousands of potentially false positive cases that can not get a fair review for months at a time.
January 12th's algorithmic detection shutdown almost 20,000 gamers in one sweep! It was initially hailed as a success with a greater than 99% accuracy rate. Within days, it was announced that hundreds of hotspots were denied incorrectly by the algorithm.  Within the first month it was announced that 1589 of those 20K had been removed from the deny list. Another month later on March 10th, it was announced that 784 of 2616 submissions reviewed had been declined vs. 1832 of those 2616 had been rolled back, an accuracy rate of 30% among the 2616 reviews conducted.  Since March 10th, there have been no further official updates regarding the more than 4100 hotspots requesting reviews.  Furthermore on March 10th it was announced that April's Solana migration would temporarily slow down the rate of reviews.  Instead, the migration has nearly halted all review progress for the past 60 days.

This is simply a "get out of jail free" card for cheaters.

This is simply a "get out of jail free" card for cheaters.

This HIP establishes harsher penalties than the current system.   In the current system gamers can place an unlimited number of submissions, clogging the system.   Also there is no monetary fine for being a gamer.

This is simply a "get out of jail free" card for cheaters.

This HIP establishes harsher penalties than the current system. In the current system gamers can place an unlimited number of submissions, clogging the system. Also there is no monetary fine for being a gamer.

Gamers cannot place unlimited submissions. That was corrected early on.
Sending their rewards to 0 sure sounds like a fine.

"get out of jail free card"  I see it as more like "put your money where you mouth is"

This is simply a "get out of jail free" card for cheaters.

This HIP establishes harsher penalties than the current system. In the current system gamers can place an unlimited number of submissions, clogging the system. Also there is no monetary fine for being a gamer.

Gamers cannot place unlimited submissions.
Where and how?  I didn't find that in any documents.  Where are the rules written for how Crowdspot is administered?   I certainly don't want to write rules that already exist.

It's in the announcements and the crowdspot channel.

This is simply a "get out of jail free" card for cheaters.

This HIP establishes harsher penalties than the current system. In the current system gamers can place an unlimited number of submissions, clogging the system. Also there is no monetary fine for being a gamer.

Gamers cannot place unlimited submissions.
Where and how?  I didn't find that in any documents.  Where are the rules written for how Crowdspot is administered?   I certainly don't want to write rules that already exist.

It's in the announcements and the crowdspot channel.

You are right.  In announcements on Jan 17th karishma wrote that checks will be in place to stop duplicates.  I will correct this HIP to remove language referring to duplicate submissions.

Hi @Tony12times - looks like you're finding info the right way by going through the Discord announcements and other related channels. I wanted to provide you with this overview and explanation of the current review process based on publicly available information. Hopefully, it can serve as a reference for you and anyone else working on this HIP:
The Helium community requested Nova Labs (formerly Helium, Inc.) to maintain a temporary Hotspot Denylist through an on-chain vote around block 1,180,295 (approximately 2022-01-14 04:57 UTC).

Nova Labs built Crowdspot, a self-service tool for the community that allows anyone to explore Helium Network Hotspot data to understand atypical Hotspot behavior and identify anomalies.

Anyone with a Helium Black Wallet account can submit Denylist requests directly to Crowdspot, where requests are reviewed using publicly available Hotspot data. Applicable Denylist updates are then sent and verified on https://github.com/helium/denylist through a multi-signature process.

Review Process
Independent and trusted community members complete the review process. Each submission is reviewed by utilizing tools built by Nova Labs that detect anomalies and uses machine learning to provide further insight, Hotspot data that is publicly available, and community-submitted evidence. The tools that are used to review Hotspot legitimacy assess a Hotspot’s signal strength, asserted location, historical data, and surrounding witnesses. These tools can be found on Crowdspot.io.

Reviewed Denylist updates are published as frequently as possible while striving to maintain the highest level of accuracy through meticulous review. These lists continue to be verified by a multi-signature group of community members independent of the initial review process.

We may or may not choose to publish the methodology used to generate these new lists, as that would allow suspicious Hotspot deployers to identify the analysis approaches we utilize.

I like this HIP but think it needs to go further.

Where does the HNT go that is forfeited by people who submit denied requests?  I propose it goes to a Subdao with the funds set aside for compensation of those who have waited moths for a review already. Should a removal request be validated it should be easy to see the date the hotpot was put on the deny list and how many days have passed to a successful review. a compensation could be fixed at 0.05 HNT a day for example. This can be in conjunction with the HIP entitled : Hold_Rewards_for_Denylist_Hotspots.  This is a show of good faith in Innocent hotspot owners and restores trust in the network.

I feel this HIP should go further and limit the carte blanche given to Nova Labs by previous HIP's to solve the problem of gaming by any means. They have shown themselves unable to do this with the algorithm in thoughtful a way that does not impact badly on the Innocent as well as the guilty.  I propose adding to this HIP the following:   In any given month no more than X hotspots can be added to the deny list by algorithmic means.  X = 200 % of the number of hotspots which can be reviewed in the man hours offered in advance by the volunteer reviewers. So, for example if on average 3 reviews can be done an hour and in a given month 100 man hours of reviewing is offered then the maximum number of hotspots algorythmicaly  added to the deny list is 600. this means barring disasters there is time allocated to review at least 50% of all deny listed hotspots even if every single one has a submission made which is unlikely. On current evidence less than 30% of hotspots in the last algorithmic sweep have had a review request submitted.

A further compensation idea along side the above.
As the HNT from forfeited bonds may not be enough and taking IOT or HNT from emissions does not seem to be an option how about this:
Should a hotspot be found to be wrongly added to the deny list the wallet is sent a code which can be redeemed for a staking bonus similar to the land rush bonus. The code allows a one time stalking of the bond amount of 5 HNT at 1 + X the standard rate.
X =  months on the deny list.  So if a hotspot was wrongly denied for 4 months the staking bonus is X 5.

This compensates the hotspot owner if the HNT is delegated to a Sub Dao with more IOT/Mobile tokens by way of compensation.

Benefits

The hotspot owner can choose to use this bonus or not.
It does not impact on current emissions.
It encourages staking and the locking up of HNT which shows the hotspot owner is part of the network in good faith.
It reduces HNT circulating supply.

Above when I say 'a month' I should qualify that as any consecutive period of 30 days or part thereof.  scenario number 1:  a hotspot is denied for 27 days.  bonus to staking of bond HT is  1+1 = X 2 multiplier.  Scenario number 2 : A hotspot is denied for 63 days.  Staking bonus multiplier is : 1+3 = x 4 multiplier.

The process of this Bond reward staking could be kept simple or automated. All staking positions are in our black wallets as an NFT. It cant be hard for those programmers in the know to create these.  Hopefully the team of volunteer reviewers includes such people or the team at at least those Nova Labs certainly will.
The entire process can be automated with a crowd spot removal submission.
On the submission form there is a tick box saying.
If you tick this box pending a successful removal request your HNT Bond will automatically be delegated to the IOT staking pool for fixed for 1 year with a staking multiplier bonus to compensate you for the time your hotspot has not received rewards. the Staking NFT will be sent to your black Helium wallet.
Should you not wish to have your HNT Bond staked and do not tick this box should your removal request be approved, your HNT Bond will be returned to your black helium wallet with no further compensation for loss of hotspot rewards.
As part of the removal from deny list verification process the appropriate NFT is created and sent to the hotspot owners wallet.

This compensates the hotspot owner if the HNT is delegated to a Sub Dao with more IOT/Mobile tokens by way of compensation.

Benefits

The hotspot owner can choose to use this bonus or not.
It does not impact on current emissions.
It encourages staking and the locking up of HNT which shows the hotspot owner is part of the network in good faith.
It reduces HNT circulating supply.

These are really good ideas.  I will see about writing them into the HIP.   With due credit Screwtape7

Further addition to the above Bond Staking compensation idea.
This bond staking bonus would be for hotspots wrongly placed on the deny list in future.  forfeited bonds being kept in an a wallet or Subdao to compensate those in the past affected by long periods on the deny list. This may mean not enough HNT is available to start with to compensate the thousands of wrongly added hotspots and owners may have to wait some time for compensation. This could be done either on a first added/first compensated basis or compensation could be given to those who have been on the deny list list the longest first.   If the compensation per day is nominally set at 0.05 HNT a day then one forfeited bond is equal to 100 days of compensation time. This is roughly just over 3 months, so most compensation payouts would be on a 1:1  basis per forfeited bond.

Staggler comment from @Tony12times here - https://github.com/helium/HIP/issues/669#issue-1718296214

This is simply a "get out of jail free" card for cheaters.

I changed some stuff on deadlines.  It really tightened the noose for gamers, provided some relief for the review team, and set a higher threshold for "getting out of jail".   There are much stiffer penalties for gamers that want to stick around after getting caught.

Be sure that you have proper coax and connections. No attenuators, amplifiers, and no use of shared or multiple antennas.
This may need to be edited. Amplifiers ARE permitted in certain limited circumstances i.e on long antenna cable runs or on setups with large amounts of attrition loss. Provided that 1. the overall Dbi is not more than the antenna would usually output and 2. No local Dbi maximum output laws are broken. As far as I know this is more specifically accurate.
It was far simpler for Mods on the Crowdspot forum to say 'no amps' but actually when I dug deeper and asked some of the more helpful approachable ones this proved not to be completely accurate.

Can you site the source?   I pulled these banned items from https://docs.helium.com/iot/denylist/
"What is the denylist? " Examples include, but are not limited to: Cluster Packet Forwarders, Misasserted Locations, Misasserted Antennas, Multiple or Shared Antennas, Attenuators, Amplifiers and Data Credit Farming

GK covers it in this Youtube video. Also I asked some of the Mods/admin.
https://www.youtube.com/watch?v=hA8xqGyTdfM&t=2122s

GK covers it in this Youtube video. Also I asked some of the Mods/admin. https://www.youtube.com/watch?v=hA8xqGyTdfM&t=2122s

I watched the GK video.  There are use cases for amplifiers given in this video for towers and long coax runs.  That probably only pertains to a small percentage of hotspots, and the Helium Docs is a more solid reference to quote in my HIP.  Because of this,  I think I'll keep this as is in this HIP.

Fair enough.

User Starteck2002 wrote:     Just done a quick skim of that HIP and as someone caught in the algorithmic sweep of Jan 2023 I feel that me having to pay a bond is not only unfair, if my request is denied (even though I have a 100% legit hotspot) I will have lost (so far) 6 months worth of earnings, bonuses from the solana migration, value in what was at the time an expensive bit of hardware and also the bond I would have paid for the removal submission.  On the plus side, if my submission is that I get removed from the deny list, I have a working hotspot and get my bond back.... but still incur losses through no fault of my own.

You certainly raise valid points here. Communication with hotspot owners from Crowdspot/Nova re being black listed is non-existent. As a result, it can be weeks if not months before some owners are aware it’s been put on the deny list. however inaccurate it may be Hotspots are sold as 'passive' reward sources. Most owners clearly do not check them often.
This lack of communication has led to:

The continuous ongoing trickle of Deny List removal requests still incoming now months after the algorithm sweep. The new requests are still coming in in at a faster rate than old ones are being reviewed. As a result, the denialist review backlog simply gets bigger and bigger.

Anger and resentment from hotspot owners who could if they had known applied for a removal request sooner.

Additional loss of rewards to said owners.

Confusion and the flooding of the Crowdspot Discord channel with owners looking for answers. had they been notified what was going on the volume of messages would be more manageable.

Unnecessary loss of coverage for longer by legitimate hotspots on the deny list.

Loss of confidence and trust in Helium.

wrongly banned owners feeling ‘jailed' without even being told they are even being 'jailed' or 'charged.'

Unnecessary pressure and workload to discord forum moderators whose talents (paid or free) could be better employed elsewhere improving the Helium Network.

Nova can and do send any or all hotstpot owners notifications to the black wallet app. Implementing a notification of deny list status can't be a challenging thing to do.
This Allows:

Hotspot owners to be notified as soon as the hotspot is placed on the deny list.

The Review Team to be able to better control the flow of denialist removal requests. i.e. If 100 hotspots are deny listed in any given day and their owners notified at once they can reasonably expect up to 1000 removal requests in the next few days/weeks Rather than unknown volume in fits and starts.

Clarity trust and understanding between Nova and hotspot owners.

Less downtime of legitimate hotspots providing necessary coverage.

The lessening of time any one hotspot is on the denialist meaning less potential compensation needing to be paid to wrongly deny listed hotspot owners from forfeited bonds.

Easing of pressure on the Crowdspot Discord Forum.

The restoring of or the maintaining of trust in the Helium Network by hotspot owners.

I  definitely agree with the idea that Nova Labs should communicate with hotspot owners when their hotspot is put on the deny list for the above reasons.
However, the idea that the hotspot remains operational on payment of only a 5 HNT bond will only work in my opinion if there is no deny list review backlog or a very small one.
Otherwise, 5 HNT is a relatively small amount for a gamer to pay to continue gaming the system for perhaps months more, potentially earning far more than the 5 HNT that they would eventually forfeit when the hotspot is actually reviewed and found to be gaming.  We could increase the bond amount but this creates affordability issues.
Also, while I really like the idea of giving hotspot owners the chance to correct possible problems with the hotspot that have caused it to be flagged up and put on the deny list, the fact remains that most hotspot owners would probably not have any idea why or what could be wrong.
Information would have to be communicated with ALL hotspot owners in advance, in a way that they could not miss outlining definitively what counts as gaming: Atenuators, packet forwarders etc.
We need to deviate away from this idea of ‘the information is already out there’ or ‘do your own research' which seems to prevail the mentality of many of the powers-that-be in the Nova team or among moderators.
Providing knowledge and information to hotspot owners on this topic and any other via notifications seems to me to be obvious to help grow the Helium Network. However, when I suggested this in the past on Discord it was shot down or met with considerable resistance from Nova/foundation/moderators.
If the Helium Network is to grow and flourish Nova needs to provide hotspot owners with information and knowledge that is in an easily accessible format that they can't miss via black wallet app. These Deny list notifications could be the start.

The algorithmic detection sweep on January 12th, 2023 shut down almost 20,000 hotspots in one day! It was initially hailed as a success with a greater than 99% accuracy rate.  Within days, it was announced that hundreds of hotspots were denied incorrectly by the algorithm.  Within a month it was announced that 1589 hotspots had been identified incorrectly and had been removed from the denylist. Another month later, on March 10th, it was announced that 2616 hotspots had been reviewed.  784 of 2616 submissions reviewed had been declined vs. 1832 of 2616 that had been removed from the denylist.  This was the last official count and announcement of the false positive hotspots.  Unofficially the count is more than 2100 false positives, and an accuracy rate around 90%.

Closed due to inactivity.  See PR 721


🐛 [cloud_firestore_platform_interface] Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference

Bug report
Describe the bug
Have been receiving Attempt to invoke virtual method 'long java.lang.Long.longValue()' on a null object reference error today on cloud_firestore get calls. On looking at the stacktrace, it's coming from cloud_firestore_platform_interface.

Steps to reproduce
Steps to reproduce the behavior:

Call the get method on any DocumentReference

Expected behavior
The get call should return the DocumentSnapshot
Sample project
final ref = FirebaseFirestore.instance;
final documentRef = ref.collection('some_col').doc('some_doc');
final documentSnap = await documentRef.get();

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel stable, 3.13.0, on macOS 14.0 23A344 darwin-arm64, locale en-NP)
    ! Warning: `flutter` on your path resolves to /Users/shrijanregmi/Projects/Flutter/sdk/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/shrijanregmi/fvm/versions/3.13.0. Consider adding /Users/shrijanregmi/fvm/versions/3.13.0/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/2.19.6/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/shrijanregmi/fvm/versions/3.13.0. Consider adding /Users/shrijanregmi/fvm/versions/3.13.0/bin to the front of your path.
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.83.1)
[✓] Connected device (3 available)
[✓] Network resources

! Doctor found issues in 1 category.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.1.0
Flutter SDK 3.13.0
alp 2.1.4+340

dependencies:
- adapty_flutter 2.7.0 [flutter meta]
- after_layout 1.2.0 [flutter]
- cached_network_image 3.3.0 [cached_network_image_platform_interface cached_network_image_web flutter flutter_cache_manager octo_image]
- carousel_slider 4.2.1 [flutter]
- circular_profile_avatar 2.0.5 [flutter cached_network_image]
- clipboard 0.1.3 [flutter]
- cloud_firestore 4.11.0 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cloud_firestore_web 3.8.1 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- copy_with_extension 5.0.4 [meta]
- country_code_picker 3.0.0 [flutter collection]
- country_codes 2.2.0 [flutter]
- detectable_text_field 2.1.0 [flutter]
- dio 5.3.3 [async http_parser meta path]
- dotted_border 2.1.0 [flutter path_drawing]
- easy_debounce 2.0.3
- easy_localization 3.0.3 [flutter shared_preferences intl args path easy_logger flutter_localizations]
- emoji_picker_flutter 1.6.2 [flutter flutter_web_plugins plugin_platform_interface shared_preferences]
- enum_to_string 2.0.1
- expandable_text 2.3.0 [flutter]
- firebase_analytics 10.6.1 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_analytics_web 0.5.5+3 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth 4.11.1 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_auth_web 5.8.4 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
- firebase_core 2.19.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_core_web 2.8.1 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics 3.4.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_dynamic_links 5.4.1 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_messaging 14.7.1 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_messaging_web 3.5.10 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_performance 0.9.3+1 [firebase_core firebase_core_platform_interface firebase_performance_platform_interface firebase_performance_web flutter]
- firebase_performance_web 0.1.4+9 [_flutterfire_internals firebase_core firebase_core_web firebase_performance_platform_interface flutter flutter_web_plugins js]
- firebase_storage 11.3.1 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- firebase_storage_web 3.6.10 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- flex_color_picker 3.3.0 [flex_seed_scheme flutter]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math web sky_engine]
- flutter_isolate 2.0.4 [flutter uuid]
- flutter_map 6.0.0-dev.3 [async collection flutter http latlong2 meta polylabel proj4dart vector_math]
- flutter_map_animations 0.5.0-dev.1 [flutter flutter_map latlong2]
- flutter_map_cancellable_tile_provider 1.0.0-preview [dio flutter flutter_map]
- flutter_map_line_editor 5.0.0 [flutter latlong2 flutter_map_dragmarker]
- flutter_map_location_marker 7.0.5 [flutter flutter_compass flutter_map geolocator latlong2]
- flutter_map_marker_cluster 1.2.0 [flutter flutter_map flutter_map_marker_popup latlong2]
- flutter_native_splash 2.3.4 [args flutter flutter_web_plugins js html image meta path universal_io xml yaml]
- flutter_screenutil 5.9.0 [flutter]
- flutter_slidable 3.0.0 [flutter]
- flutter_speed_dial 7.0.0 [flutter]
- flutter_styled_toast 2.2.1 [flutter flutter_localizations]
- flutter_svg 2.0.7 [flutter vector_graphics vector_graphics_codec vector_graphics_compiler]
- flutter_uxcam 2.4.6 [flutter visibility_detector]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math web]
- fluttertoast 8.2.2 [flutter flutter_web_plugins]
- freezed_annotation 2.4.1 [collection json_annotation meta]
- geolocator 10.1.0 [flutter geolocator_platform_interface geolocator_android geolocator_apple geolocator_web geolocator_windows]
- google_fonts 6.1.0 [flutter http path_provider crypto]
- group_radio_button 1.3.0 [flutter]
- hashtagable 2.3.0+1 [flutter]
- hooks_riverpod 2.4.4 [collection flutter flutter_hooks flutter_riverpod riverpod state_notifier]
- image_cropper 5.0.0 [flutter image_cropper_platform_interface image_cropper_for_web]
- image_picker 1.0.4 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]
- image_picker_for_web 3.0.1 [flutter flutter_web_plugins image_picker_platform_interface mime]
- intl 0.18.1 [clock meta path]
- isar 3.1.0+1 [ffi js meta]
- isar_flutter_libs 3.1.0+1 [flutter isar]
- jiffy 6.2.1 [intl]
- json_annotation 4.8.1 [meta]
- json_serializable 6.7.1 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- map_launcher 3.0.1 [flutter]
- maps_toolkit 3.0.0
- package_info_plus 4.2.0 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface win32]
- path_provider 2.1.1 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- percent_indicator 4.2.3 [flutter]
- provider 6.0.5 [collection flutter nested]
- reorderables 0.6.0 [flutter]
- responsive_framework 1.1.1 [flutter collection]
- retrofit 4.0.3 [dio meta]
- share_plus 7.2.1 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- shared_preferences 2.2.2 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- showcaseview 2.0.3 [flutter]
- stomp_dart_client 1.0.0 [web_socket_channel]
- string_validator 1.0.2
- system_settings 2.1.0 [flutter]
- url_launcher 6.1.14 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 3.0.7 [crypto]
- vector_map_tiles 6.0.0 [flutter flutter_map http latlong2 path_provider vector_tile_renderer async executor_lib]
- vector_tile_renderer 5.0.1 [flutter vector_tile fixnum collection]
- version 3.0.2
- wiredash 1.7.5 [clock collection file flutter flutter_localizations http http_parser intl material_color_utilities path_provider shared_preferences]

dev dependencies:
- build_runner 2.4.6 [analyzer args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- copy_with_extension_gen 5.0.4 [analyzer build source_gen copy_with_extension meta]
- flutter_oss_licenses 2.0.1 [path meta yaml dart_pubspec_licenses args]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math async boolean_selector characters collection material_color_utilities meta source_span stream_channel string_scanner term_glyph web]
- freezed 2.4.5 [analyzer build build_config collection meta source_gen freezed_annotation json_annotation]
- isar_generator 3.1.0+1 [analyzer build dart_style dartx glob isar path source_gen xxh3]
- mockito 5.4.2 [analyzer build code_builder collection dart_style matcher meta path source_gen test_api]
- retrofit_generator 7.0.8 [analyzer build built_collection code_builder dart_style dio retrofit source_gen tuple]

transitive dependencies:
- _fe_analyzer_shared 61.0.0 [meta]
- _flutterfire_internals 1.3.9 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 5.13.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- animated_stack_widget 0.0.4 [flutter]
- archive 3.4.6 [crypto path pointycastle]
- args 2.4.2
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- build 2.4.1 [analyzer async convert crypto glob logging meta package_config path]
- build_config 1.1.1 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 4.0.0 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.4.1 [analyzer async build collection convert crypto graphs logging package_config path pool pub_semver stream_transform yaml]
- build_runner_core 7.2.11 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta package_config path pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.6.3 [built_collection collection fixnum meta]
- cached_network_image_platform_interface 3.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.1.0 [cached_network_image_platform_interface flutter flutter_cache_manager]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- clock 1.1.1
- cloud_firestore_platform_interface 6.0.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- code_builder 4.7.0 [built_collection built_value collection matcher meta]
- collection 1.17.2
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+6 [js meta]
- crypto 3.0.3 [typed_data]
- csslib 1.0.0 [source_span]
- dart_pubspec_licenses 2.0.2 [yaml path json_annotation]
- dart_style 2.3.2 [analyzer args path pub_semver source_span]
- dartx 1.2.0 [characters collection crypto meta path time]
- easy_logger 0.0.2 [flutter]
- executor_lib 1.1.1 [flutter async]
- fake_async 1.3.1 [clock collection]
- ffi 2.1.0
- file 7.0.0 [meta path]
- file_selector_linux 0.9.2+1 [cross_file file_selector_platform_interface flutter]
- file_selector_macos 0.9.3+3 [cross_file file_selector_platform_interface flutter]
- file_selector_platform_interface 2.6.1 [cross_file flutter http plugin_platform_interface]
- file_selector_windows 0.9.3+1 [cross_file file_selector_platform_interface flutter]
- firebase_analytics_platform_interface 3.7.3 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_auth_platform_interface 7.0.1 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_crashlytics_platform_interface 3.6.9 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.6+9 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.5.10 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_performance_platform_interface 0.1.4+9 [_flutterfire_internals firebase_core flutter plugin_platform_interface]
- firebase_storage_platform_interface 4.4.9 [collection firebase_core flutter meta plugin_platform_interface]
- fixnum 1.1.0
- flex_seed_scheme 1.4.0 [collection flutter meta]
- flutter_cache_manager 3.3.1 [clock collection file flutter http path path_provider rxdart sqflite uuid]
- flutter_compass 0.8.0 [flutter]
- flutter_hooks 0.20.3 [flutter]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math web]
- flutter_map_dragmarker 5.0.0 [flutter flutter_map latlong2]
- flutter_map_marker_popup 5.3.0-dev.1 [flutter animated_stack_widget flutter_map latlong2 provider]
- flutter_plugin_android_lifecycle 2.0.16 [flutter]
- flutter_riverpod 2.4.4 [collection flutter meta riverpod state_notifier]
- frontend_server_client 3.2.0 [async path]
- geolocator_android 4.3.1 [flutter geolocator_platform_interface uuid]
- geolocator_apple 2.3.2 [flutter geolocator_platform_interface]
- geolocator_platform_interface 4.1.1 [flutter plugin_platform_interface vector_math meta]
- geolocator_web 2.2.0 [flutter flutter_web_plugins geolocator_platform_interface]
- geolocator_windows 0.2.1 [flutter geolocator_platform_interface]
- glob 2.1.2 [async collection file path string_scanner]
- graphs 2.3.1 [collection]
- html 0.15.4 [csslib source_span]
- http 1.1.0 [async http_parser meta]
- http_multi_server 3.2.1 [async]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image 4.1.3 [archive meta xml]
- image_cropper_for_web 3.0.0 [flutter flutter_web_plugins image_cropper_platform_interface js]
- image_cropper_platform_interface 5.0.0 [flutter plugin_platform_interface http]
- image_picker_android 0.8.8+1 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_ios 0.8.8+2 [flutter image_picker_platform_interface]
- image_picker_linux 0.2.1+1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_macos 0.2.1+1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_platform_interface 2.9.1 [cross_file flutter http plugin_platform_interface]
- image_picker_windows 0.2.1+1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
- io 1.0.4 [meta path string_scanner]
- js 0.6.7 [meta]
- latlong2 0.9.0 [intl]
- lists 1.0.1 [meta]
- logging 1.2.0
- matcher 0.12.16 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.5.0 [collection]
- meta 1.9.1
- mgrs_dart 2.0.0 [unicode]
- mime 1.0.4
- nested 1.0.0 [flutter]
- octo_image 2.0.0 [flutter]
- package_config 2.1.0 [path]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path 1.8.3
- path_drawing 1.0.1 [vector_math meta path_parsing flutter]
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.2.0 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.1 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.1 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.1 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.1 [ffi flutter path path_provider_platform_interface win32]
- petitparser 5.4.0 [meta]
- platform 3.1.3
- plugin_platform_interface 2.1.6 [meta]
- pointycastle 3.7.3 [collection convert js]
- polylabel 1.0.1 [collection]
- pool 1.5.1 [async stack_trace]
- proj4dart 2.1.0 [mgrs_dart wkt_parser meta]
- protobuf 2.1.0 [fixnum collection meta]
- pub_semver 2.1.4 [collection meta]
- pubspec_parse 1.2.3 [checked_yaml collection json_annotation pub_semver yaml]
- riverpod 2.4.4 [meta stack_trace state_notifier]
- rxdart 0.27.7
- share_plus_platform_interface 3.3.1 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shared_preferences_android 2.2.1 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.3.4 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.3.2 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.1 [flutter plugin_platform_interface]
- shared_preferences_web 2.2.1 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.3.2 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- shelf 1.4.1 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.4 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 1.4.0 [analyzer async build dart_style glob path source_span yaml]
- source_helper 1.3.4 [analyzer collection source_gen]
- source_span 1.10.0 [collection path term_glyph]
- sqflite 2.3.0 [flutter sqflite_common path]
- sqflite_common 2.5.0 [synchronized path meta]
- stack_trace 1.11.0 [path]
- state_notifier 1.0.0 [meta]
- stream_channel 2.1.1 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- synchronized 3.1.0
- term_glyph 1.2.1
- test_api 0.6.0 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- time 2.1.3 [clock]
- timing 1.0.1 [json_annotation]
- tuple 2.0.2
- typed_data 1.3.2 [collection]
- unicode 0.3.1 [lists]
- universal_io 2.2.2 [collection meta typed_data]
- url_launcher_android 6.1.0 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.5 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.6 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.7 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.5 [flutter plugin_platform_interface]
- url_launcher_web 2.0.20 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.8 [flutter url_launcher_platform_interface]
- vector_graphics 1.1.9 [flutter vector_graphics_codec]
- vector_graphics_codec 1.1.9
- vector_graphics_compiler 1.1.9 [args meta path_parsing xml vector_graphics_codec path]
- vector_math 2.1.4
- vector_tile 1.0.0 [fixnum protobuf]
- visibility_detector 0.4.0+2 [flutter]
- watcher 1.1.0 [async path]
- web 0.1.4-beta
- web_socket_channel 2.4.0 [async crypto stream_channel]
- win32 5.0.9 [ffi]
- wkt_parser 2.0.0
- xdg_directories 1.0.3 [meta path]
- xml 6.3.0 [collection meta petitparser]
- xxh3 1.0.1
- yaml 3.1.2 [collection source_span string_scanner]

Thanks for the report @shrijanRegmi
I am unable to replicate the reported error using the plugin example and after adding the code snippet you shared that I added in the example as below:
Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);

  if (shouldUseFirestoreEmulator) {
    FirebaseFirestore.instance.useFirestoreEmulator('localhost', 8080);
  }

  final ref = FirebaseFirestore.instance;
  final documentRef = ref.collection('firestore-example-app').doc('Tenet');
  final documentSnap = await documentRef.get();
  print(documentSnap);

  runApp(FirestoreExampleApp());
}

My pubspec.yaml:
environment:
  sdk: '>=3.1.0 <4.0.0'

dependencies:
  cloud_firestore: ^4.11.0
  firebase_core: ^2.19.0
  flutter:
    sdk: flutter
  http: ^0.13.3

Can you narrow down the error by providing only bare minimal code sample only using flutterfire plugins that shows the reported error ?

Hey @darshankawar,
Looks like there is an issue with the latest plugin (but not sure which one). Downgrading all of the firebase plugins solved my problem. I'll look into this problem more carefully in the weekend and leave a comment here.
I downgraded from the below:
firebase_core: ^2.19.0
firebase_core_web: ^2.8.1
firebase_analytics: ^10.6.1
firebase_analytics_web: ^0.5.5+3
firebase_auth: ^4.11.1
firebase_auth_web: ^5.8.4
firebase_storage: ^11.3.1
firebase_storage_web: ^3.6.10
firebase_crashlytics: ^3.4.1
firebase_performance: ^0.9.3+1
firebase_performance_web: ^0.1.4+9
firebase_messaging: ^14.7.1
firebase_messaging_web: ^3.5.10
firebase_dynamic_links: ^5.4.1
cloud_firestore: ^4.11.0
cloud_firestore_web: ^3.8.1

to the below:
firebase_core: ^2.17.0
firebase_core_web: ^2.8.0
firebase_analytics: ^10.5.1
firebase_analytics_web: ^0.5.5+1
firebase_auth: ^4.10.1
firebase_auth_web: ^5.8.2
firebase_storage: ^11.2.8
firebase_storage_web: ^3.6.8
firebase_crashlytics: ^3.3.7
firebase_performance: ^0.9.2+7
firebase_performance_web: ^0.1.4+7
firebase_messaging: ^14.6.9
firebase_messaging_web: ^3.5.8
firebase_dynamic_links: ^5.3.7
cloud_firestore: ^4.9.3
cloud_firestore_web: ^3.7.2

I've just updated to firebase_core: ^2.19.0 & cloud_firestore: ^4.11.1 and got same problem. It works again after downgrading to older versions as @shrijanRegmi said

Same issue here with same fix as @meomap  and @shrijanRegmi.
For me, the issue only seemed to show up on Android. iOS and web continued to work with the newer dependencies.

It might help if you share the document for reproduction. change any sensitive data (e.g. email address), it is important you keep the types within the document the same however.

I've been running into the same issue with one of my firebase projects. Still looking for a permanent fix but removing this line temporarily fixed it for me
FirebaseFirestore.instance.settings = const Settings(persistenceEnabled: true);

I've been running into the same issue with one of my firebase projects. Removing this line fixed it for me
FirebaseFirestore.instance.settings = const Settings(persistenceEnabled: true);
It's enabled by default anyway according to the docs

For Android and Apple platforms, offline persistence is enabled by default. To disable persistence, set the PersistenceEnabled option to false.

I hope this helps

@AlexFeldmeier  you are awesome. I had the same line and if you have not provided this commented i would be still struggling. Thanks a lot 👍

@AlexFeldmeier - Which platform produces this behaviour?

@russellwheatley Sorry for the late reply. It happens in Android and iOS. Web you still need this if you want persistence
  if (kIsWeb) {     await FirebaseFirestore.instance.enablePersistence(const PersistenceSettings(synchronizeTabs: true));   }


Add a flag dry_run flag to lane generated by init beta

This allows users to try fastlane beta<EMAIL_ADDRESS>after running fastlane init beta to test it before sending out a build to all their testers/groups
Also makes emails an optional param when groups are passed

👍


Update custom-theme.mdx (en version)

Summary

copilot:summary
Details

copilot:walkthrough
Related Issue

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

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


Move multi-select from canary to core package

Summary
Move the multi-select component from the canary package to the core packages
💬 Description
When first implemented as a canary component,
To bring the component into the core package, the 2 code bases need to be merged back into a single select component
This should be done sooner rather than later, as this will become a more complex task as more changes are made to ic-select. there are already changes (for example adding an icon into the ic-select), which are not in the select-with-multi code base
A decision needs to be made at what point we are happy to do this - after reaching out for feedback?
Before releasing we should ensure that there is sufficient test coverage in the unit tests
##Additional info
Doing this work will remove the need to complete #2095
#1700 should also be completed before release

As part of v3


⚠ PrivateHD has degraded performance

In 83c0e9d, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1481 ms

Resolved: PrivateHD performance has improved in c31221f.


Provide better support for WSL

Currently the only WSL specific support we provide is specifying the specific distribution you wish to use as a default shell. We should provide the ability to define how to connect to said distro as well. Things such as the user to use, the command to run on startup, etc. Basically try to mimic how Microsoft Terminal handles its WSL support

Completed with commit e47d93f


Boot2Docker for Windows\start.sh requires bash.exe

After installation (skipping VirtualBox installation as it was already installed) when I double click the Boot2Docker Start icon on the desktop my Notepad++ opens up showing me the contents of the start.sh. I expect this script to be executed by bash.
First line of the script shows #!/bin/bash.exe but this is not installed nor associated with the .sh extension on my system.
I tried guessing that MinGW is a prerequisite, but simply installing it and starting the start.sh in the bash shell fails on complaints on missing clear and ssh-keygen commands.
It seems that the installation instructions at http://docs.docker.com/installation/windows/ are missing a prerequisite?
Platform used is Windows 7 64 bits.

"bash is installed by the installer..."
Where to ?
It's not in my "Program Files/Boot to Docker for Windows" directory.

@SteveJM "bash" is part of the MSys Git distribution - look in C:\Program Files (x86)\Git or thereabouts.

Thanks for your response, znmeb.
I don't really think that "bash" should be considered part of git. Nonetheless, yes, I've found it, set it as the "default" executable for files of type "sh". It now "flashes" a window that appears to fail (given nothing else happens), I'll have to debug this tomorrow. Weirdly, the install script offered to put boot2docker in my PATH, but I can't simply execute that from a command prompt, so it hasn't actually done that.

Sorry that I wasn't clear enough to state in my initial comment that I have a workaround. These are step-by-step instructions that I used as workaround:

Install MinGW
Use the MinGW Installation Manager to install the packages for clear and ssh-keygen
Start the bash shell from the MinGW installation by clicking in Windows Explorer on c:\MinGW\msys\1.0\msys.bat
In the bash window type cd /c/Program\ Files/Boot2Docker\ For\ Windows/
In the bash window type ./start.sh

Regarding solving this ticket: most user friendly may be to have the installer offer to download MinGW if its not yet installed and set the proper file association.

@waltervdb The boot2docker install offers to install MSys Git, this contains bash.
@SvenDowideit Wouldn't it make more sense to use .bat files instead of bash scripts? See also this question @ the Docker forums https://forums.docker.com/t/docker-on-windows-its-overkill-to-require-msys-git/1119

Make sure that you point to the 'start.sh' file (example: "C:\Program Files\Docker Toolbox\start.sh").
If it cannot recognize the file, can it be that Git isn't installed on the machine. Remember to let Docker install Git, during the installation.


Clarifying intended use of the secondary menu (fixes #875)

This fixes #875 by clarifying that the secondary menu doesn't have any special behavior by itself, it's just good for formatting sections on a page.

@it's Rajpoot:🤍:: :إِنا لِلّهِ وَإِنَـا إِلَيْهِ رَاجِعون
😭اللهﷻ مغفرت فرمائیں۔آمین😭


Update index.php

I mean, I'd always consider an easter egg...

In fact, we already have one. Visit /index.php.
I would always love more!

? Wouldn't that add my IP to the list.. y'know?


could not create a descriptor for a dilated convolution forward propagation primitive

my code is as follows:
import jittor as jt
from jittor import nn, Module
import numpy as np
import sys, os
import random
import math
from jittor import init
from jittor.dataset.mnist import MNIST
from jittor.dataset.cifar import CIFAR10
import jittor.transform as trans
import pylab as pl

jt.flags.use_cuda = 0 # if jt.flags.use_cuda = 1 will use gpu

class Model (Module):
    def __init__ (self):
        super (Model, self).__init__()
        self.conv1 = nn.Conv (3, 32, 3, 1) # no padding
        self.conv2 = nn.Conv (32, 64, 3, 1)
        self.bn = nn.BatchNorm(64)

        self.max_pool = nn.Pool (2, 2)
        self.relu = nn.Relu()
        self.fc1 = nn.Linear (64 * 12 * 12, 256)
        self.fc2 = nn.Linear (256, 10)
    def execute (self, x) :
        x=jt.transpose(x,0,3,1,2)
        x = self.conv1 (x)
        x = self.relu (x)
        x = self.conv2 (x)
        x = self.bn (x)
        x = self.relu (x)

        x = self.max_pool (x)
        x = jt.reshape (x, [x.shape[0], -1])
        x = self.fc1 (x)
        x = self.relu(x)
        x = self.fc2 (x)
        return x

def train(model, train_loader, optimizer, epoch, losses, losses_idx):
    model.train()
    lens = len(train_loader)
    for batch_idx, (inputs, targets) in enumerate(train_loader):
        outputs = model(inputs)
        loss = nn.cross_entropy_loss(outputs, targets)
        optimizer.step (loss)
        losses.append(loss)
        losses_idx.append(epoch * lens + batch_idx)
        if batch_idx % 10 == 0:
            print('Train Epoch: {} [{}/{} ({:.0f}%)]\tLoss: {:.6f}'.format(
                    epoch, batch_idx, len(train_loader),
                    100. * batch_idx / len(train_loader), loss.data[0]))

def test(model, val_loader, epoch):
    model.eval()
    test_loss = 0
    correct = 0
    total_acc = 0
    total_num = 0
    for batch_idx, (inputs, targets) in enumerate(val_loader):
        batch_size = inputs.shape[0]
        outputs = model(inputs)
        pred = np.argmax(outputs.data, axis=1)
        acc = np.sum(targets.data==pred)
        total_acc += acc
        total_num += batch_size
        acc = acc / batch_size
        print('Test Epoch: {} [{}/{} ({:.0f}%)]\tAcc: {:.6f}'.format(epoch, \
                    batch_idx, len(val_loader),100. * float(batch_idx) / len(val_loader), acc))
    print ('Total test acc =', total_acc / total_num)

def main ():
    batch_size = 16
    learning_rate = 0.1
    momentum = 0.9
    weight_decay = 1e-4
    epochs = 5
    losses = []
    losses_idx = []
    train_loader = CIFAR10(train=True, transform=trans.Resize(28)).set_attrs(batch_size=batch_size, shuffle=True)
    val_loader = CIFAR10(train=False, transform=trans.Resize(28)) .set_attrs(batch_size=1, shuffle=False)
    model = Model ()
    optimizer = nn.SGD(model.parameters(), learning_rate, momentum, weight_decay)
    for epoch in range(epochs):
        train(model, train_loader, optimizer, epoch, losses, losses_idx)
        test(model, val_loader, epoch)

    pl.plot(losses_idx, losses)
    pl.xlabel('Iterations')
    pl.ylabel('Train_loss')
    pl.show()

    # model_path = '/home/root/Python_Demo/JittorMNISTImageClassification/mnist_model.pkl'
    # model.save(model_path)

if __name__ == '__main__':
    main()

It is a code that works well on another computer (a mac), but can't run well on my computer (windows).

Hi there,
It seems that the input data or labels of cifar-10 are initially in uint8 format, which is not directly compatible with operations expecting float32 data types.
I solved this problem by converting both the input data and the labels to jt.float32 before passing them to the convolution layers.


Dapr produces high cardinality span names on creating/deleting reminders

In what area(s)?

/area runtime/actor

/area operator

/area placement

/area docs

/area test-and-release

What version of Dapr?

1.7.4

Expected Behavior

Dapr produces trace spans with certain static names, like 'DeleteReminder/{ActorType}/{ReminderName}'
Actual Behavior

Dapr produces spans with bad names like '/v1.0/actors/{ActorType}/c5ab0479-a6c3-4ae6-a724-028bfc4d1b9e/reminders/{ReminderName}'
High cardinality span names can be highly likely to break tracing infrastructure since span names are often used for indexing in storage and grouping in queries.
See https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#span for span naming.
Steps to Reproduce the Problem

Enable tracing feature
Register/Remove reminders
Check span names

Release Note

RELEASE NOTE:

I checked related code in dapr, seems it will fall back to use request path as span name if there's no span name set in spanAttr[daprAPISpanNameInternal]
Can this behavior change to using route pattern as default span name? like "{http_method} actors/{actorType}/{actorId}/reminders/{name}", it would be much safer.

In the example above, do you mean to strip the actorType, actorId and name values by placeholders?

In the example above, do you mean to strip the actorType, actorId and name values by placeholders?

Thanks for your response.
For reminders creation/deletion:
It's better to give it a readable name, like "DeleteReminder/OrderActor/CancelOrderReminder", actor id needs to be omitted since it has unbounded values.
just as same as span names for actor invocation
https://github.com/dapr/dapr/blob/1d69ce63c9c92a9087034aac2729d5b475121008/pkg/diagnostics/http_tracing.go#L295
Also, I propose to not use request path as the default common span name. It's just for safety, to make sure dapr will never produce unbounded span names for any requests. For example, use fmt.Sprintf("HTTP %s %s", httpMethod, endpoint.Route) as the default span name


Provide way for user to indicate agreement to a data usage agreement

Is there an existing issue for this?

[x] I have searched the existing issues

New feature

This should be either node or dataset specific
Should ideally work in both curl requests (i.e., the query tool or a direct API user can handle the agreement info) and in the interactive docs

Unclear documentation
No response

Hi @alyssadai, 😋  I'm interested in working on this issue if it's still available. could you also provide the reference file for this task? Thank you!

Hi @samadpls, thanks for your interest on this! Unfortunately, this issue is not currently suitable or ready for an external contribution as the exact specification still needs to be discussed with data owners before we can work on it. In other words, input is needed from our collaborators before we can implement the feature.
If you have specific ideas for this issue however, we welcome you to leave relevant links or resources here!


Mod selection GUI does not close

Mod selection gui does not close after pressing Download button. Caused by the mod scroll window added in last update.

Fixed in version <IP_ADDRESS>


Can you provide a Linux version of jaxlib 0.3.14 for download

Please:Can you provide version 0.3.14 of jaxlib
ERROR: Ignored the following yanked versions: 0.1.63, 0.4.0, 0.4.15
ERROR: Could not find a version that satisfies the requirement jaxlib==0.3.14 (from tensorflow-federated) (from versions: 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.4.6, 0.4.7, 0.4.9, 0.4.10, 0.4.11, 0.4.12, 0.4.13, 0.4.14, 0.4.16, 0.4.17, 0.4.18, 0.4.19, 0.4.20)
ERROR: No matching distribution found for jaxlib==0.3.14

It's not on pypi because of storage issues.
You can install it via this command:
pip install -U jaxlib==0.3.14 -f https://storage.googleapis.com/jax-releases/jaxlib_releases.html

@yashk2810
Excuse me, is this the Linux version? I am using a remote server to execute pip install - U jaxlib=0.3.14- f https://storage.googleapis.com/jax-releases/jaxlib_releases.htmlPost error

Looking in links: https://storage.googleapis.com/jax-releases/jaxlib_releases.html

Error: Ignored the following yang versions: 0.1.63, 0.4.0, 0.4.15

Error: Could not find a version that satisfies the requirement jaxlib=0.3.14 (from versions: 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.4.6, 0.4.7, 0.4.9, 0.4.10, 0.4.11, 0.4.12, 0.4.13, 0.4.14, 0.4.16, 0.4.17, 0.4.18, 0.4.19, 0.4.20)

Error: No matching distribution found for jaxlib==0.3.14

Ohh, sorry this is the right command: pip install -U jaxlib==0.3.14 -f https://storage.googleapis.com/jax-releases/jax_releases.html

This is also mentioned in the docs here: https://jax.readthedocs.io/en/latest/installation.html#installing-older-jaxlib-wheels


portalicious: another approach to forms

This is an alternative approach to what I had tried in #5658
I prefer this approach better now that I've fleshed it out. I think it's the right balance between reducing duplication, and flexibility.
More details in the comments.
Checklist before requesting a review

[ ] I have performed a self-review of my code
[ ] I have added tests wherever relevant
[ ] I have made sure that all automated checks pass before requesting a review
[ ] I do not need any deviation from our PR guidelines

@arsforza this isn't ready to be merged because it still needs some tweaking here and there, but it could still use a review for sure - especially on the new form components.


Signing typedData?

EIP712 signing?

You can use this package, https://github.com/wakumo/eth-sig-util
Took me a while to figure out how to use it but here's a closed issue where I documented my final code.


[stable/prometheus-operator] Consider making AdditionalPrometheusRules a map

I think additionalPrometheusRules would be better as a map, instead of a list of maps with name:groups[] pairs. Aside from removing a layer of indirection, it allows for finer-grained overrides in parent charts, multiple values files, --set, etc. The key would be the PrometheusRule name, and the value would be the value of groups: in the current schema.

if only there were some way to annotate lists with their desired merge behavior (replace the list, append, prepend, replace non-null elements, etc) instead of treating them like opaque leaf nodes! until then it seems like we should shy away from lists in our values files whenever possible.

This is a significant breaking change for others from this chart and can be avoided by creating a separate chart for deploying rules into the cluster yourself


feat: WFT-335 Add Keys CRUD API

Summary
Update the Whispir Platform API openapi documentation to include the Keys CRUD API specifications.
Changes

feat: Added Keys tag
feat: Added Key and KeyCollection schema
feat: Added Key and Keys response object
feat: Add /keys GET and POST endpoint
feat: Add /keys/{keyId} GET, PUT, and DELETE endpoint
feat: Mark all updates as internal

Notes

The API response is based on the standard used by existing endpoints. I used the Contact crud endpoints as basis. This means the response is not following jsonapi standard.
Following the other endpoints, I also prefixed the keys endpoint with the workspaces route. Will need to verify if we are going to support workspaces.

Output

{
  "id": "7f6a3d23-11f3-406c-9d72-8e8a80c248e4",
  "type": "basic",
  "userId": "d7d429e0-7e1e-4b03-ba34-e486483e76f2",
  "clientId": "ead5ac28-47df-4d52-9d4f-de4b5e3d31a8",
  "accountId": "30ab9bb0-373c-4f6c-b24d-1e4160af98b4",
  "enabled": true,
  "description": "Key used by Engineering for testing",
  "createdTime": "2023-01-25T02:25:33+0000",
  "lastModifiedTime": "2022-03-29T16:30:18+11:00"
}

Great work Errol! Good to see the Spectral rules in action for a new resource


Prompt not updated when switching tabs

When I have multiple tabs open and all of them are in different directory, the starship prompt is not being updated after tab is changed. This issue does not exist if the plugin is disabled, e.g. yazi, by default, updates path in top left corner every time the tab is switched.
Also, is there a way to have custom starship config only for yazi? I know one can choose specific starship config by exporting STARSHIP_CONFIG env var.

I don't use tabs and never noticed, so thanks for opening this. I'll have a look at that and also possibly allowing a config file to be specified.

I opened an issue over at Yazi itself to see if I can get something for subscribing to tab changing events, so we'll see how that goes.
As for the configuration file, could you check out if the changes over on this branch work well for you? Should be something like the following command to just grab that branch:
git clone -b configuration-file https://github.com/Rolv-Apneseth/starship.yazi.git ~/.config/yazi/plugins/starship.yazi

I've just reviewed the changes and it works like a charm. Will you be merging it to main branch?
Let's see how it goes with the tab switching.
Thank you very much!

I'll merge it into the main branch yeah, was just waiting to see if it worked for you.

Thank you very much!

No problem and yeah I'll comment here again when there's an update about the tabs

Yazi got a new event for switching tabs and I made the changes required for this plugin in #10. That should work with the latest changes of both, let me know if there are any issues

Works nicely, thanks for the fix 🙂

It works for me as well. Thank you very much!

Works nicely, thanks for the fix 🙂

Thanks for creating the new event in Yazi


How to upload an entire directory structure in Codiad?

I am looking for a browser to server uploading feature for codiad.
The Codetransfer Plugin works well but only from server to server.
Do you see any reliable alternatives to upload an entire directory structure in Codiad?

Best would be to use FTP as initial upload

Yes. I am thinking using the Codetransfer Plugin for that purpose. Making the left part pointing to C: instead of the workspace directory and connecting the Codiad Server via FTP. What do you think?

Another alternative would be to upload and unzip an archive.

To solve the problem I finally developed a plugin to unpack archives
It works only with .zip for the moment.
https://github.com/rafasashi/Codiad-Archives

Which variables are you collecting here? Just asking because you unset them
https://github.com/rafasashi/Codiad-Archives/blob/master/controller.php#L14

I published the wrong piece of script :) it comes from a script reviewer I use to wrap external php modules into my environment.

yeah that looks better now :) I will test it later and add it to the marketplace

@daeks @rafasashi and me we update the plugin.
it supports rar und tar now.

i have added it to the marketplace


refactor spagcn graph construct; use dance data object in the example spagcn script

Hi @JiayuanDing100, I have updated the SpaGCN example script with the following changes:

Refactored spatial graph construct to SpaGCNGraph and SpaGCNGraph2D transformation objects
Load raw data objects (adata, spatial, spatial_pixel, etc.) from the dataset object and construct the dance Data object.

Feel free to comment under this thread about any editing suggestions or questions. Otherwise, let me know if it is good to merge. Afterward, please help update stagate, louvain, and stlearn following the changes made in this PR.

I'm merging this in favor of a new data API modification that adds more complex support to label channels for the multi-modality tasks (TBA). Please still feel free to comment under this thread for editing suggestions, and we will open a new PR to address those.


Fix openFile not working on Linux.

Thanks to LeotomasMC for some assistance with this.
I noticed and was quite confused by the fact that certain things in Flixel failed to work on Linux, such as FlxG.openURL, which returned "xdg-open: unexpected argument '&'". This appears to fix that and seems to work quite fine, with that segment of Flixel now working once more.
May be good to have someone more qualified than I check this out before er... merging, as I'm not exactly the best programmer around.

Looks like someone wanted Sys.command() not to block. In a shell, you can do this by adding & after all the arguments, but that's a special message to the shell, outside the argument list. Makes sense that it didn't work here.
We could use Process instead, but I figure xdg-open is quick enough that it's probably fine.

Just checked and we also don't include the ampersand for <prebuild open="file" /> or <postbuild open="file" />. Almost no one uses those, but then again, how many people use this? Lime sure doesn't; Lime only calls it from WindowsPlatform, which obviously uses the Windows-specific command.
Pretty sure it never worked and just never got noticed until now, making this a straightforward bug fix.


usb device status

Obtaining the USB device status currently takes an extremely long time compared to the refresh interval of the NuvlaBox heartbeats. This is causing false alarms concerning the status of the NuvlaBox.
The cause of this problem is the amount of time it takes to run lsof from within a container. The timings for the command:
time for i in {1..10}; do lsof /dev/bus/usb/001/002; done

are shown in the following table.

test
time (s)

bare metal
0.309

ubuntu 18.04 container (non-priv.)
12.474

ubuntu 18.04 container (priv.)
9.084

While the excessive timing of lsof can be investigated, it would be useful to update the heartbeat information from the device information separately to ensure that the heartbeat information is sent at a reliable frequency.
In addition to the timing issue, there is a problem with the deployment of the agent container.  This is done within a non-privileged container, so the device files are not available within the container.  Consequently, lsof always reports an error and the agent interprets this as the device being free. Unless the agent is deployed in privileged mode, it will never report a device as being busy.

The behavior is the same on a RPi as well as a standard Exoscale VM; this is not device related.

investigation
The tardiness of the lsof within a Docker container is most likely related with the way the host filesystem is mounted inside the container. This goes deep into the Docker implementation of the storage driver, but what is observed is that during lsof, the file /proc/filesystems is opened, read and closed. The closing operation however, inside the container, takes hundreds of thousands of attempts before succeeding: -1 EBADF (Bad file descriptor).
solution
There's no clear solution on how to make this run faster. A possible solution would be to simply replace lsof by another command or script which simply looks at the device ID and checks whether there is a process making use of it.
However, the best solution is actually to simply remove this line. This is because lsof will not be able to infer whether a device is being used by another container, even if running on privileged mode. Such information can only be obtainer from the respective container...so it doesn't make sense to have this in the agent as a overview call for all devices in the host.
next steps
create the iot-manager (https://github.com/nuvlabox/iot-manager/issues/1), which will take care of discovering, categorizing and managing all peripherals. Everything related with peripherals, which might disrupt the agent's hearbeat, will be moved into this new component


Updating master with release 0.7.1

Codecov Report

Merging #902 into master will increase coverage by 1.3%.
The diff coverage is 55.33%.

@@             Coverage Diff             @@
##             master     #902     +/-   ##
===========================================
+ Coverage     61.06%   62.36%   +1.3%
- Complexity      826      929    +103
===========================================
  Files           444      465     +21
  Lines         12828    13464    +636
  Branches       1480     1550     +70
===========================================
+ Hits           7833     8397    +564
- Misses         4419     4452     +33
- Partials        576      615     +39

Impacted Files
Coverage Δ
Complexity Δ

...va/uk/gov/gchq/gaffer/store/ValidatedElements.java
75% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../java/uk/gov/gchq/gaffer/data/IsEdgeValidator.java
100% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../java/uk/gov/gchq/gaffer/types/IntegerFreqMap.java
13.33% <ø> (ø)
1 <0> (?)

.../uk/gov/gchq/gaffer/function/FreqMapExtractor.java
0% <ø> (ø)
0 <0> (?)

...ffer/serialisation/TypeSubTypeValueSerialiser.java
66.66% <ø> (ø)
14 <0> (?)

...va/uk/gov/gchq/gaffer/data/IsElementValidator.java
100% <ø> (ø)
0 <0> (ø)
:arrow_down:

...v/gchq/gaffer/serialisation/IntegerSerialiser.java
40% <ø> (ø)
4 <0> (?)

...ava/uk/gov/gchq/gaffer/data/IsEntityValidator.java
100% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ava/uk/gov/gchq/gaffer/types/TypeSubTypeValue.java
52.5% <ø> (ø)
13 <0> (?)

...v/gchq/gaffer/serialisation/FreqMapSerialiser.java
79.16% <ø> (ø)
14 <0> (?)

... and 164 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3042271...6253cdf. Read the comment docs.


Bump djl version to 0.10.0 and pytorch native version to 1.7.1

Bump version of demos to djl bom version - 0.10.0 and pytorch native version to 1.7.1

@aws-samples/djl-committers

Have you tested and verify everything is working?

Have you tested and verify everything is working?

There should be some incompatible between 0.9.0 and 0.10.0,
At least, we should see if the code can compile

yeah sorry my bad, I assumed we might have some tests running if I created a PR. But I will run all the modules and check.

Have you tested and verify everything is working?

There should be some incompatible between 0.9.0 and 0.10.0,
At least, we should see if the code can compile

I have tested the modules. I'm not sure whether we should update djl-ui-demo too. That project looked like it hasn't updated in a while.


AKS and EKS modules

Using AKS and EKS Terraform configuration directly with Epiphany.
Result of Spike #2982

@erzetpe
Regarding validation in AKS:

most of the values are fetched automatically from existing epiphany infrastructure
if user wants to provide another resource group, it already should exist, therefore he cannot provide anything that was not verified by azure api
only prefix could raise some problem as it was used in dns name, therefore I added validation only for it

Validation in EKS:

similar situation -> we can only control prefix name
all other resources should already exist

When it comes to the k8s specific configurations that we are allowing to tweak, users should take full responsibility of values used.


Double Decoder Consistency for Tacotron 2

Hi, I found this interesting post while regularly checking up on erogol's blog. Any chances of having it here? Having a Tacotron 2 that is practically immune to alignment problems sounds very state of the art.
For reference, Mozilla/TTS has it.

@ZDisket training tacotron-2 take too much time for me but i will consider. There are many paper solve alignment problem and training very fast such as glow-tts, flow-tts, aligntts. I don't think we really need tacotron-2 because fastspeech2 can produce comparable results and alignTTS can learn very good alginment with serveral hours. So the problem is, if we can find a model can be inference real-time, training time < 1 day and learn very good alignment with serveral hours, do we need tacotron-2 anymore ?

@dathudeptrai I know that too. If you get any of these working well (or FastSpeech2 without teacher model) then just ignore my suggestion.

Yeah :))) fastspeech2 without anh external aligner is comming :))) be patient

BTW, to: @erogol is "Double Decoder" training slower than original Tacotron-2 ? cc: @ZDisket

@dathudeptrai it makes training only for 5% slower. And it definitely is worth it. It solves to attention problems once for all at least for my runs.
The problem with FastSpeech it requires initial alignments (from an aligner or a teacher model). Therefore to make the whole process easier and more accessible to everyone, I still believe targeting Tacotron like attention models is a worthy effort.
Even you like to train FastSpeech you can use DDC to generate even better attention alignments labels for your FS training.

Yeah :))) fastspeech2 without any external aligner is comming :))) be patient

you mean align-TTS?

@erogol flow-tts :D

@ZDisket i will read erogol's blog then i will consider to implement here but maybe you need training by urself :(. Tell me if it's ok ;v

I can try a PR but I need at least one day being 48 hours :)

@erogol what do you mean :)), one day cann't being 48 hours :))).

not in Mars :)

@erogol decoder (fine) is still 2 LSTM layers as normal and decoder (coarse) is 1 LSTM layers, am i right?

no the architecture is the same bur reduction rate is larger. But its a good idea to use even less layers.

@dathudeptrai I can train it from scratch myself although I estimate it'll take a week.

@dathudeptrai

So the question is, if we can find a model can be inference real-time, training time < 1 day and learn very good alignment with serveral hours, do we need tacotron-2 anymore ?

Does MFA-extracted duration FastSpeech2 now fit that description?


feat: added preliminary SDK support to "rand_data" plugin

This pull request is the first pass at using the hipcheck-sdk crate to make a plugin for hipcheck
The goal of the SDK is to make it as easy as possible for plugin authors to write new plugins for hipcheck!
The hidden hc plugin command no accepts another flag --sdk that will use the dummy_rand_data_sdk plugin, rather than the dummy_rand_data plugin
There are some outstanding issues that still need to be addressed, whether in this issue, or in another issue in the future:

How are we handling third-party dependencies that are exposed in public facing types (serde_json::Value, schemars::schema::SchemaObject, ...)
How much documentation should be present in the hipcheck-sdk crate
How do we test the hipcheck-sdk crate to ensure it is producing the desired behaviors and integrates cleanly with what hipcheck is expecting
Does it make sense to add a prelude module so a user would be able to use hipcheck_sdk::prelude::* and have the most common imports?

Thanks @patrickjcasey! I'll take a look tomorrow! :smile:

Re: a prelude crate
As far as I see, excluding the re-exports the only types users need access to is QuerySchema, DynQuery, NamedQuery, Query, Plugin, PluginServer, PluginEngine, plus the error module. And anyone using the SDK to write a plugin will need all of these.
I'd be in favor of adding a prelude crate so that users that want to do so can simply import * as you have shown above.
Leave this and the reexport crate as a separate commit on top for now in case we need to walk it back

As for documentation and testing, those are important, but they can be done after the SDK is merged

I concur on the idea of a prelude module.


Small improvements concurrent map

The hash table underlying unordered_map_concurrent has support for queries using a precomputed hash value.
Since we need to hash once to figure out which bin to use, we may as well re-use that value for the lookup when possible, which avoids an extra hash operation while we are holding the lock.
Benchmarks show a 1-2% speedup in some cases (as part of a whole renderer).
Also swapped the FingerprintMap to  tsl::robin_map while I was in there, there's no good reason to use std:unordered_map.

It's failing the clang-format check. Can you enable the setting that lets me push changes to your submission? I'm happy to pull, clang-format it, and then update.

N/M, I see I already can do so. Hang on, I'll fix it.

I fixed the formatting for you. I will merge when the new CI tests come back. Good fixes.

I have some ideas for what to try next, BTW.

It's failing CI on OSX, but it doesn't have anything to do with you. Looks like just this morning homebrew updated libheif (which we use to read HEIF/HEIC files) and it's changing some of the image hashes for that format. I will deal with that separately. Merging your code...


Boolean not serializing in Refit 4.3

Hello!
Bool type fields  are not serialized in the query.
This problem appeared in Refit version 4.3. All worked in version 4.2.
Example
[Get("/myobject")]
Task<List<MyObject>> GetMyObjectsAsync([AliasAs("admin")] bool? admin);

Is the value you're passing in null or a true/false?

I'm passing any value (null, false, true) but In my query this parameter is missing.

We need that too!


kube-anywhere fails with "unexpected EOF" or "connection shut down" when photon OS template is not within the cluster

When trying to deploy a kubernetes on cluster A and datastore DS1 inside a VC, I observe the following

uploading the photonOS template on "datastore DS2" on a different cluster say "cluster B" altogether is not working.
uploading the photonOS template on "datastore DS3" in the same cluster "clusterA" is working.

The deployment fails with errors "unexpected EOF", "connection shut down". Its because terraform crashes for vsphere plugin. However, I see this errors only after the kubernetes nodes are created sometimes (or) after powering on those kubernetes nodes. So this is not something related to that it couldn't find the template.

+1 I am seeing the same failure. is there a solution?

@datagen24 : Can you upload the photon OS template in the cluster itself?
Currently for terraform we have to give the current context where to search for this template. It is the same place where you deploy kubernetes cluster.

The Photon os template is in the root of the cluster, Kubernets is being deployed into a folder called Kubernets.
Should i put the OVA in the folder?
Steven C. Peterson
Mainstream Technology Group
<EMAIL_ADDRESS>Office:<PHONE_NUMBER> x 2409
Cell/SMS:<PHONE_NUMBER>
Skype: datagen24
OpenPGP KeyID: CC16FE24 Fingerprint: 596A F093 33FF FEC3 7CC3  9E82 7099 D155 CC16 FE2
Digitally Signed CaCERT, more info at cacert.org

On Mar 21, 2017, at 19:29, BaluDontu<EMAIL_ADDRESS>wrote:
@datagen24 https://github.com/datagen24 : Can you upload the photon OS template in the cluster itself?
Currently for terraform we have to give the current context where to search for this template. It is the same place where you deploy kubernetes cluster.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/kubernetes/kubernetes-anywhere/issues/300#issuecomment-288251647, or mute the thread https://github.com/notifications/unsubscribe-auth/AT6Opbdgir1XGpqSYtgnCOn462aKjB6Qks5roF1egaJpZM4LPvUX.

You can deploy the OVA inside a valid Cluster, Host or Resource Pool in which you deploy ur Kubernetes VM's.
For example, if you want to deploy your kubernetes cluster inside a VSAN cluster. Then you need to deploy the OVA on a VSAN cluster.
If you plan to deploy your kubernetes cluster inside a ESX host. Then you need to deploy the OVA on a ESX host.
Also, you might have specified the resource pool while deploying the cluster.
Resource pool/cluster (same as destination for OVA import). (phase1.vSphere.resourcepool) [] (NEW) - xxx
This should be same place where you might want to deploy your resource pool.

I may have figured out the issue on my side,  it appears that the password string is not properly escaped, I use randomly generated passwords with no restrictions on the upper ASCII.
I captured an area where I think this happened.
As a test, I created a new user gave it admin rights with no upper ASCII and it all worked.
I have a section of the screen where it died it includes passwords and other sensitive info so I can not post the log to the github, if someone would reach out to me via private message i will send it along.

So this password is a VC password? U can email me at<EMAIL_ADDRESS>I can take a look.

Sent

If you pass the full template Path, you can deploy a kubernetes cluster successfully even though the template is not in the current cluster.


EBSW indicator

I don't know if this goes anywhere really, I tried using the Even Better Sine Wave indicator and noticed the note in the docs about the logic. So I made the function below based off the code in the two links:

prorealcode
tradingview

import numpy as np
import pandas as pd
def testEBSW(close,length = 40,bars = 10):
    '''Just making the ebsw indicator from pro real code'''
    #Instance Variables
    lastHP = lastClose = 0
    filtHist = np.zeros(3)
    result = [np.nan]*(length-1)+[0]

    #Calculate constants
    angle = 2*np.pi/length
    alpha1 = (1-np.sin(angle))/np.cos(angle)
    ang = 2**.5*np.pi/bars
    a1 = np.exp(-ang)
    c2 = 2*a1*np.cos(ang)
    c3 = -a1**2
    c1 = 1-c2-c3

    for i in range(length,close.size):
        HP = 0.5*(1+alpha1)*(close[i]-lastClose)+alpha1*lastHP

        #Rotate filters to overwrite oldest value
        filtHist = np.roll(filtHist,-1)
        filtHist[-1] = c1*(HP+lastHP)/2+c2*filtHist[1]+c3*filtHist[0]

        #Wave calculation
        wave = np.mean(filtHist)
        rms = np.sqrt(np.mean(filtHist**2))
        wave = wave/rms

        #Update past values
        lastHP = HP
        lastClose = close[i]
        result.append(wave)
    return pd.Series(result, index=close.index)

The outputs are pretty different so this code could be bugged, either way I think the original code could be changed slightly to not calculate the constants on every loop as they don't change. Sorry if this serves no purpose, I just signed up to post this so I don't know how any of this works.

I realized after posting this graph is pretty ambiguous, but it's the result of both indicator types on 100 days of EURUSD data I have saved to my computer. Blue line is the one in this library and the orange one is my test function.

Hello @Squigglez2,
Interesting. I will add it to the list of things. Have you tried exporting data and it's indicator values from TradingView and run a correlation test to see how inline your version is with TradingView? If not, that would help you see if there are bugs in your code.
How to do a TV Correlation Test
Are you using a different data source for Pandas TA and then visually comparing the numbers displayed from TradingView? If so, then that can cause deviations in calculation because they are not the same data source. You can Export Chart Data from TradingView data for comparison by using the hamburger menu in the upper left corner; select the ISO format.

Once you have exported your chart data from TradingView, try the following:
import pandas as pd
import pandas_ta as ta

# Load the TV export data or whatever you saved it as
data = pd.read_csv("path/to/tradingview_data.csv")
data.ta.chop(length=14, append=True) # Example using the choppiness index. Replace with your indicator
# data.drop()   # https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.drop.html
print(data.corr()) # Check their correlation

Also, @rengel8 would you mind taking a look at this Issue when you have a moment?
Kind Regards,
KJ

I'll give it a try. The graph I posted was the version in Pandas_TA and my custom function both run on the same EURUSD data. I just compared the tradingview and prorealcode to make sure I didn't miss any steps since I've never used either of those languages and figured it help prevent mistakes.

@Squigglez2,

EDIT: Sadly, it seems that exporting chart data requires a premium account which I don't have.

Understandable. Thanks for providing links to the TradingView source so I can do it. Unfortunately, I do not have a time frame on the resolution of this Issue.
Kind Regards,
KJ

Understandable, the code I posted should be runnable at least, if anyone else with a premium account has the chance. Of can somehow give me a copy of the close data and indicator output.

@Squigglez2 Thank you very much for providing the function of the EBSW. That made it easy to look into it.
With the data, @twopirllc provided, I made a comparison between TradingView and the updated version, which is now very close (despite some bars 4 to 6 decimal places are identical) to TradingView.
TV offers a very fast pre-roll of only one bar probably with historical data under the hood. That is interesting, but the recent version in Pandas TA is now closely to TV with the advantage of providing the same results each time one bar earlier.
TV offers a very fast pre-roll of only one bar probably with historical data under the hood. That is interesting, but the recent version in Pandas TA is now closely to TV with the advantage of providing the same results each time one bar earlier.

Has the code been updated for this then?

Hello @Squigglez2,
Please test the updated version using by installing the development branch and let us know if it is working better.
$ pip install -U git+https://github.com/twopirllc/pandas-ta.git@development

Kind Regards,
KJ


New package: JackenWu.MSearcher version 1.4.2

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

[!TIP]
The developers of the package put the package installer in a zip file.
The developers of the package provide an introductory video and documentation:

当你相册里有几千张meme图，水群时却找不到那张在你相册角落的图

https://github.com/user-attachments/assets/59360835-d8a6-4dd9-b456-893bba75a2f6

如何使用 MSearcher

Microsoft Reviewers: Open in CodeFlow

Successfully test the installation manually with the following command:
& "D:\Duckhome\CodeDebug\MSearcher Setup 1.4.2.exe" /S /D=D:\Duckhome\CodeDebug\winngetaaa

@stephengillie - Maybe you can take a look at this pull request before the pipeline validation ends.
Pipeline validation always flagged this pull request as https://github.com/microsoft/winget-pkgs/labels/Validation-Unattended-Failed , but everything worked fine when I used winget install -m validation locally.

Automatic Validation ended with:

No errors to post.

(Automated response - build 899.)

Verify:

I couldn't find how to have the application display its version.

@wingetbot waivers Add Validation-Unattended-Failed

I couldn't find how to have the application display its version.

Me too, maybe the developers didn't design this feature...

@stephengillie - It seems waivers were not successfully added...

Manual Validation ended with:

2024-12-06 10:40:28.266 [FAIL] Installer failed security check. Url: https://github.com/Jacken-Wu/MSearcher/releases/download/v1.4.2/MSearcher_Setup_1.4.2_win_x64.zip Result: 0x80004005

(Automated response - build 900.)

Manual Validation ended with:

2024-12-06 10:40:28.266 [FAIL] Installer failed security check. Url: https://github.com/Jacken-Wu/MSearcher/releases/download/v1.4.2/MSearcher_Setup_1.4.2_win_x64.zip Result: 0x80004005

(Automated response - build 900.)

The installer has been submitted to virustotal.
zip: https://www.virustotal.com/gui/file/26d0e2017e4f7dd084d41c3f426156b4852c0e6b8d4e1f0b9fdadfcfbfbcb0db/detection
unzip: https://www.virustotal.com/gui/file/c72fff26543a4cead8f2a0b92d3b4f0a0fc5367bbb52ed637a8ab8e1f917658c
Also submitted to Microsoft Security Intelligence, results pending.

@wingetbot run

https://github.com/microsoft/winget-pkgs/pull/196163#issuecomment-2528305987

Verify:

@ stephengillie - Pipeline validation always flagged this pull request as  Validation-Unattended-Failed During installation testing the installer was blocked on user input and no switches were provided. , but everything worked fine when I used winget install -m validation locally.

Since a recent pipeline change, logs are no longer emitted. To troubleshoot these, I have to install into a VM. But there are too many to install all errors on to a VM.


ionic 2 recommendation for ios-deploy fails

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
ionic --version shows
******************************************************
 Dependency warning - for the CLI to run correctly,
 it is highly recommended to install/upgrade the following:

 Install ios-deploy to deploy iOS applications to devices.  `npm install -g ios-deploy` (may require sudo)

******************************************************

npm install -g ios-deploy fails with ENOENT

Rs-MacBook-Pro:elite-schedule-app-2.0final rebeccaannburton$ sudo npm install -g ios-deploy
npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd %s %s (wd=%s<EMAIL_ADDRESS>./src/scripts/check_reqs.js && xcodebuild /Users/rebeccaannburton/.nvm/versions/node/v7.5.0/lib/node_modules/.staging/ios-deploy-4e4d52dd
npm ERR! Darwin 16.4.0
npm ERR! argv "/Users/rebeccaannburton/.nvm/versions/node/v7.5.0/bin/node" "/Users/rebeccaannburton/.nvm/versions/node/v7.5.0/bin/npm" "install" "-g" "ios-deploy"
npm ERR! node v7.5.0
npm ERR! npm  v4.1.2
npm ERR! path /Users/rebeccaannburton/.nvm/versions/node/v7.5.0/lib/node_modules/ios-deploy/build/Release/ios-deploy
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/rebeccaannburton/.nvm/versions/node/v7.5.0/lib/node_modules/ios-deploy/build/Release/ios-deploy'
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/rebeccaannburton/.nvm/versions/node/v7.5.0/lib/node_modules/ios-deploy/build/Release/ios-deploy'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!
Steps to reproduce:
ionic --version
sudo npm install -g ios-deploy
Related code:
Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Your system information:

Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.1.13
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: 5.0.13
OS: macOS Sierra
Node Version: v7.5.0
Xcode version: Xcode 8.2.1 Build version 8C1002

******************************************************
 Dependency warning - for the CLI to run correctly,
 it is highly recommended to install/upgrade the following:

 Install ios-deploy to deploy iOS applications to devices.  `npm install -g ios-deploy` (may require sudo)

******************************************************

This issue was moved to driftyco/ionic-cli#1910


filer.copy: No resume / checksum to skip work.

Describe the bug
weed filer.copy should only upload new files, and should not restart from the beginning.
System Setup

5.4
unknown command: version | version 30GB 2.85 19555385 linux amd64

Expected behavior
compare file sizes, if they match run adler32 between the files.
Additional context
Bad things can happen during a transfer, starting from scratch is not good behaviour. https://github.com/chrislusf/seaweedfs/pull/2579

consider xxhash3 over adler32 for better collision prevention.

See weed filer.copy -h. Current code has option -check.size to skip copying if size did not change.


broken github actions workflow

Expected Behavior
all tests on the main should pass
Current Behavior
tests for pylint, flake8 und docs are suddenly failing
tox4 has default isolated builds and i think this leads to these errors
Minimum acceptance criteria
make all test workflows pass again

fixed by @SiQube in #77


Release v1.0.0

Major release due to #113

Codecov Report

Merging #114 (6934b20) into master (ab4685d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #114   +/-   ##
=======================================
  Coverage   52.65%   52.65%
=======================================
  Files          16       16
  Lines        1960     1960
=======================================
  Hits         1032     1032
  Misses        827      827
  Partials      101      101

Impacted Files
Coverage Δ

pkg/loadtest/cli.go
7.82% <ø> (ø)


hyperspace-cli: init at 1.5.1

Motivation for this change
Adds the CLI component of Hypercore, previously known as dat https://github.com/hypercore-protocol/cli
Things done

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

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 130063 at 6891ec11 run on aarch64-linux 1

7 packages failed to build:

python39Packages.batchspawner
python39Packages.dockerspawner
python39Packages.jupyterhub
python39Packages.jupyterhub-ldapauthenticator
python39Packages.jupyterhub-systemdspawner
python39Packages.jupyterhub-tmpauthenticator
python39Packages.oauthenticator

1 package skipped due to time constraints:

lumo

11 packages built successfully:

parity-ui
python38Packages.batchspawner
python38Packages.dockerspawner
python38Packages.jupyterhub
python38Packages.jupyterhub-ldapauthenticator
python38Packages.jupyterhub-systemdspawner
python38Packages.jupyterhub-tmpauthenticator
python38Packages.oauthenticator
teleprompter
vscode-extensions.matklad.rust-analyzer
vscode-extensions.vadimcn.vscode-lldb

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

I will fix the Editor Config issues in the next commit when I figure out why this won't build on aarch64

The following error occurs on native aarch64:
[nix-shell:~/nixpkgs/nixpkgs-hypercore-cli]$ nix build github:MatthewCroughan/nixpkgs/hypercore-cli#hyperspace-cli
GC Warning: Couldn't read /proc/stat
[0/1 built, 0.0 MiB DL] GC Warning: Couldn't read /proc/stat
error: builder for '/nix/store/wga4n0xf01y9gzlvz5qmmw93h5lv9zqg-node__at_hyperspace_slash_cli-1.5.1.drv' failed with exit code 1;
       last 10 log lines:
       > npm ERR! errno 1
       > npm ERR<EMAIL_ADDRESS>install: `node-gyp-build "node preinstall.js" "node postinstall.js"`
       > npm ERR! Exit status 1
       > npm ERR!
       > npm ERR! Failed at the<EMAIL_ADDRESS>install script.
       > npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
       >
       > npm ERR! A complete log of this run can be found in:
       > npm ERR!     /tmp/nix-build-node__at_hyperspace_slash_cli-1.5.1.drv-0/.npm/_logs/2021-07-13T18_36_09_195Z-debug.log
       >
       For full logs, run 'nix log /nix/store/wga4n0xf01y9gzlvz5qmmw93h5lv9zqg-node__at_hyperspace_slash_cli-1.5.1.drv'.

hyperspace-cli build on native aarch64(via boot.binfmt.emulatedSystems)

hyperspace-cli build on native aarch64(via binfmt)

I was doing my build via nix-on-droid so it's interesting to consider that it didn't work, maybe something to do with sandboxing?

I'm now re-running generate.sh which will take around 30 minutes, at which point we can merge.

Result of nixpkgs-review pr 130063 run on x86_64-linux 1

4 packages built:

hyperspace-cli
joplin
netlify-cli
vimPlugins.coc-solargraph


JIT user provisioning

Add an issue to track JIT user provisioning for OIDC. Some inspiration:

JIT provisioning could just be a checkbox to enable/disable for this iteration, but the mockup captures all of the feedback we got in Firezone legacy for this feature

See previous discussion
https://github.com/firezone/firezone/issues/830

Chatted with customer about this, what would be better is supporting Actor/Identity/Group manage via REST API and provide example scripts to manage.


Dataset Creation

❓ Questions & Help

I have my data objects in a list in the following form:
x.shape = [819, 14] edge_index.shape = [2, 402000]
x.shape = [701, 14] edge_index.shape = [2, 162000]
The error appears at data, slices = self.collate(data_list)
I get a RuntimeError: invalid argument 0: Sizes of tensors must match except in dimension 0. Got 819 and 701 in dimension 1 at C:\w\1\s\tmp_conda_3.6_160730\conda\conda-bld\pytorch_1570810118016\work\aten\src\TH/generic/THTensor.cpp:689
I have tried transposing my node features to no avail, its exactly the same error.

It seems that your shapes do not align with the ones you reported. The DataLoader tries to concatenate x in dimension 1, but it encounters unequal sizes (819, 701) in dimension 1.

Well, the print for data.num_nodes and data.num_features are correct for the data independently. So I just decided to merge the data first before initializing it as a Data object of pytorch geometric.


Create a service to make our requests

Create a service object that calls the API and sends the response to the JsonToEvents Service.

more or less done