Added NestedScrollView in Android (Kotlin)

Description 📜
I have added all the docs related to NestedScrollView in Android (Kotlin) with this I also have formatted the code accordingly and also I have given the user a choice to copy the code direct from the docs.
THANKYOU
Fixes #1409

Type of change 📝

[x] Doc#umentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Android Dev (Kotlin)

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@sitamadex11 I don't think so there is a need for that but still I will merge it right away.😄

Done @sitamadex11 you can review it now

sure

bro, I was talking about the layout design that comes when you split the code and design tab, not about the codes' screenshot. I guess some miss understanding😅


Behaviour with a failed node

I have a 3 node openshift cluster and have installed gluster-kubernetes on it. It works flawlessly unless a node is failing.
I shutdown one of the 3 machines, but openshift / kubernetes does not notice that one of the gluster pods is not reachable anymore. The existing volumes are still mounted on the pods and can be accessed without problems, heketi tries to create a brick on the failed node though after creating a new pvc. This obviously does not work, so heketi cancels the creation of the new volume.
Is this a reasonable behavious of heketi? IMO, since there are still 2 of 3 active gluster pods, it should still be able to create a new volume?

There is on-going discussion on the heketi project about how it behaves when one or more nodes are in a failure state. So yes, you've hit a hot-button issue. :) I'll let one of @raghavendra-talur or @MohamedAshiqrh comment on this one further.

@timbrd Hi, For now all the volume create in pvc creates replica 3 volumes. Now in kube 1.6 and origin 1.6 we have added the volume type option. In which you can specify replica:2 which just needs two nodes to be up and running.


Markup issue: Add min-width: 0 to main#main element

Basically main area right now is able to expand as much as it wants to and if devs for example want to add horizontal-scrollable blocks the main element should have min-width: 0, since it's default value is "auto";
Without min-width: 0

With

https://defensivecss.dev/tip/flexbox-min-content-size/

@callmevladik Any quick way to reproduce this?


[0.2] Feat - Menu layout refactor

This PR looks to introduce a number of tweaks to the side menu in the hub. Currently we have issues such as:

Currently we have duplicate logic for displaying desktop and mobile menu's
Collapsing the menu into icon's which tooltips doesn't save much screen space and also introduces some UX issues when trying to show nested menu items
Item's such link links are a bit duplicated within loops leading to level of maintenance overhead we should avoid
The menu doesn't scroll if the number of menu items is longer than the window height, making it unusable.
When on a sub page the parent menu item was not shown as active and it wasn't as obvious what page you were viewing

What this PR looks to solve...

Moved menu display into one component so we only have to update in one place
Menu will no longer collapse into icons, instead the user can decide to completely hide the menu, freeing up the entire available screen space, this should persist between page loads
The side menu is now scrollable when the items overflow
There is a slight shift in the layout so the top bar that goes across is now fixed, however the padding has been reduced to minimise screen size issues.

Misc updates

Changed font to Poppins

With menu

On a sub page with active highlighting

Menu hidden

@alecritson looks good. All I'd say is the JS open/close could do with a nice transition.
transition-all duration-500 might do it?

@alecritson looks good. All I'd say is the JS open/close could do with a nice transition.
transition-all duration-500 might do it?

Added a small animation

@alecritson looks good. All I'd say is the JS open/close could do with a nice transition.
transition-all duration-500 might do it?

Added a small animation

Can we do the same for the Products sub-menu, so that also has a subtle animation?


Implement support for abstract namespaces in unix domain sockets

Normally unix domain sockets are visible in the file system, though there is a linux-specific extension that allows abstract namespaces. Those names start with a null byte. See here for a brief overview.
This is for internal customer.

Actually this is already implemented, seems like an issue on user side.


Allow the percent character in the userinfo of an authority.

The username and password in an authority are percent-encoded.

Seems fine, mind including a comment next to the code with a link to the relevant RFC/section so Future Us doesn't forget the why?

Do you have any preference between https://tools.ietf.org/html/rfc3986#section-3.2.1 and https://url.spec.whatwg.org/#set-the-username ?

Thanks!


Migrate existing minimal FE implementation

https://github.com/EMBL-EBI-ABC/Pert_Cat_FE

In order to preserve commit history, migrated with a direct merge: https://github.com/EMBL-EBI-ABC/PerturbationCatalogue/commit/23596cd02494ee8f5618d9db17ba810ea575e4a4


Sample on root span level

for spans that have a local parent (i.e., non-root spans/transactions), just inherit the sampling decision from the parent
add support for start_span(parent_sampled=<bool>) -- opinions welcome on whether we still want this (we have it in the SDK atm)

Closes https://github.com/getsentry/sentry-python/issues/3766

@sl0thentr0py Removed parent_sampled and updated the tests a bit more, please recheck


[Proposal]-[M03]-[Lab 07]:[Prevent a new organization from being created]

Often students will accidently create a new organization while completing the Integrating External Source Control with Azure Pipelines lab. This fix adds a step to ensure that the Default Directory is selected, allowing learners to select their existing org instead of creating a new one.
Checklist
Mark completed with "x" between brackets, "[x]", or checking the box once the PR is created:

[x] Has related GitHub Issue 💥 #231
[x] Tested it
[x] Read the PR collaboration guide 👓 Collaboration Guide 📝

Changes proposed in this pull request:
-This adds a simple clarification. Often the GitHub tool will select the student's Microsoft Account directory

Thanks @rob-foulkrod , great proposal ;)


AB#27848  Created pending migration and fix event entity

AB#27848
Describe your changes
Create pending migrations and
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have added tests wherever relevant
[x] I have made sure that all automated checks pass before requesting a review
[x] I have communicated above whether I need any deviation from our PR guidelines (eg. "I don't want the reviewer to merge on my behalf because...")

@aberonni  Thanks for the review. I do not think more additional testing is needed than what I described in the subtask in devops


Grav 1.1.0 rc1 admin left sidebar enlarging again after each page save

Hi, so if i minimize the left sidebar admin menu and i edit a page and save.. the left menu is enlarging itself again.

Yes it's currently only a page-level thing.  There is no memory for it. I'll leave a note for @w00fz as this will require some JS magic to keep track of sidebar status.


Disabled accessing the udev log on systemd based systems

Recent versions of systemd ship a libudev that deprecated udev_set_log_fn and stubbed away the implementation.
This patch removes the code from crosswalk that otherwise breaks the build due to deprecated warnings being errors. With the change, crosswalk runs on Yocto "Fido" with systemd.

Have these changes been submitted to crosswalk-project.org itself?  Also the patch is missing the normal header that has fields like Upstream-status which would answer that :)  Thanks!

I'm currently checking what's necessary for crosswalk upstream

OK cool.  Please keep in mind http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines and then re-submit once you can add the Upstream-Status field, thanks!

Phew, lot of reading…


Possible concurrency issues in storage blobs

valgrind --tool=dr^C./azure-storage-blobs-test &> ~/blobs_thread.txt
blobs_thread.log

duplicate of https://github.com/Azure/azure-sdk-for-cpp/issues/4435


feat: add yayi2-30b example

Yayi2-30b has a score of over 80 MMLU. I performed some fine-tuning on it using qlora, and from my quick test, it appears to be very promising. so, I created the mlx example for this model in case anyone wants to run it via mlx. However, this model has an unusual k,v layer that causes the quantization to fail. Currently, I haven't found any quantization tools that support this model (except for bnb nf4). It would be great if mlx could provide support for its quantization.
FYI:
https://huggingface.co/wenge-research/yayi2-30b
https://huggingface.co/mzbac/yayi2-30b-guanaco
https://github.com/ml-explore/mlx/issues/328

I have added the workaround for the quant as suggested in https://github.com/ml-explore/mlx/issues/328. Now, the example works with 4-bit quantization. Once the PR gets merged, I will upload the 4-bit quantized model.

I have added the workaround for the quant as suggested in https://github.com/ml-explore/mlx/issues/328. Now, the example works with 4-bit quantization. Once the PR gets merged, I will upload the 4-bit quantized model.

HI @mzbac sorry for the delayed review here. Do you still want to merge this? I think given the non-standard size it wouldn't fit easily in our hf_llm example, but wdyt?

I think this should be supported by hf_llm once we fix the quant non-32 dimension. I'm happy to close this one. Meanwhile, if people want to try this model in f16 precision, they should be able to run it via hf_llm.

Sounds good, thank you!


unable to login into account

Hey guys I just wanted to report a weird issue, I am unable to login into my steam account on ChimeraOS but obviously on my PC or on my phone I have no problems but when I login with the correct details it will say it's wrong.
I even did a password reset and changed to a shorter one while also double checking to make sure it was correct.

I can't log in either. I only see a blue screen.

I can't log in either. I only see a blue screen after the last update (31)

This may be a separate issue. See https://github.com/ChimeraOS/chimeraos/wiki/ChimeraOS-Troubleshooting#after-steam-logs-me-in-i-get-a-blank-blue-screen and open a new issue if you still encounter issues.

I can't log in either. I only see a blue screen after the last update (31)

This may be a separate issue. See https://github.com/ChimeraOS/chimeraos/wiki/ChimeraOS-Troubleshooting#after-steam-logs-me-in-i-get-a-blank-blue-screen and open a new issue if you still encounter issues.

 I can login again.

Is this still an issue or was the blue screen issue noted above?

I'd have to check if I still have the issue

I'd have to check if I still have the issue

@coreybruce did you check if it still the case. If it is, feel free to comment and we will reopen the issue.

I'll have to download the latest version and check, I will get back to you

Well I was booting it up after installation but it's failing to boot..

That is a new issue. Could you please report it in a new ticket? We know about it and we are investigating it but we need some more info.
Are you booting from an USB by any chance? That seems to be problematic in some cases with the implementation of external libraries.
Cc @pastaq

Yeah I'll start a new issue for this and yeah I installed it on a portable USB 3 drive but the old version didn't have a issue with it


BlobService.set_container_acl optional param not documented

Description:
signed_identifiers is also optional, but not documented as so.

Original Issue: https://github.com/Azure/azure-sdk-for-python/issues/185
Comments (0):

We have fix the documentation for set_container_acl and will be releasing this with our next major release.
Thanks for the feedback!

Hello @ahmetalpbalkan ,
We have released the 0.30 version (#132) which addressed this feature request. If you have issues with the new version in regards to this issue, please reopen it and continue the discussion.
Thanks!


Host already in use by other container

Fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "errors": [], "module_stderr": "Starting pihole ... \nHost is already in use by another container\n\u001b[1A\u001b[2K\nStarting pihole ... \n\u001b[1B", "module_stdout": "", "msg": "Error starting project Encountered errors while bringing up the project."}

Please refer to the closed issues mentioning "host is already in use".

Thank you


PR is #15914

Hi @eolivelli
Could you tell us why we have to revert it?

@cbornet may add more details.
A few tests on master branch are now failing

Master fails consistently on several tests:
testGetAllPartitions(org.apache.pulsar.broker.namespace.NamespaceOwnershipListenerTests)
producerBacklogQuotaExceededTest(org.apache.pulsar.websocket.proxy.ProxyPublishConsumeTest)
I have the same failure locally on latest master.
Can someone else confirm ?

mvn test -pl pulsar-broker -Dtest=NamespaceOwnershipListenerTests

Message: org.apache.bookkeeper.mledger.ManagedLedgerException$ManagedLedgerFencedException: Can't trim fenced ledger

Stacktrace:

org.apache.pulsar.broker.service.BrokerServiceException$PersistenceException: org.apache.bookkeeper.mledger.ManagedLedgerException$ManagedLedgerFencedException: Can't trim fenced ledger
	at org.apache.pulsar.broker.service.persistent.PersistentTopic$6.deleteLedgerFailed(PersistentTopic.java:1248)
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.lambda$asyncDelete$34(ManagedLedgerImpl.java:2737)
	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
	at java.base/java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:887)
	at java.base/java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2325)
	at org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl.asyncDelete(ManagedLedgerImpl.java:2734)
	at org.apache.pulsar.broker.service.persistent.PersistentTopic.lambda$delete$33(PersistentTopic.java:1220)
	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)

tests are now failing due to https://github.com/apache/pulsar/pull/17736
because "trim" cannot happen if a ManagedLedger is "fenced", and we set "fenced" in "delete".
so there is some code path in which we "delete" and then try to "trim".
we should do the opposite...trim and then delete.


Unexpected child debugging session when starting remote debuggee with RUBYOPT=-rdebug/*

Describe the bug
Some criteria for this issue:

Use RUBYOPT=-rdebug/open to load the debugger in remote mode.
The program runs another Ruby process like system("bundle exec rake")

When the above happens at the same time, it'll trigger double debugging sessions. I recorded a video to demo this:
https://user-images.githubusercontent.com/5079556/175811942-bd585b50-edc0-45a8-9bc6-b666d1e359bf.mov
This is annoying because the second session starts independently and hangs the program, until we connect to and disable it.
And this can happens to Rails apps.
I'm not sure it's at fault of the debugger as that's how ENV vars are passed to child processes. But perhaps we can do something from the debugger to prevent it?
To Reproduce
bar.rb
puts "bar"

target.rb
result = `ruby bar.rb`

puts(result)

terminal1
RUBYOPT=-rdebug/open ruby -Ilib target.rb

terminal2
rdbg -A

Expected behavior
The second process shouldn't start a debugging session.

Okay. Restore RUBYOPT while requiring session.rb.

@ko1 Thanks for the fix. But I just tested the PR but it doesn't solve the example I mentioned here, as it's not passed by the rdbg binary. Do you think there's a way to solve that case too?

Ah, I see. On this case, we can't recognize it should be kept or not.
Another idea is set RUBY_DEBUG_ENABLE=0 at session.rb and child processes can not load debug.rb, but it also prohibits invoking debugger if it is needed.
Another idea is removing -r debug/... but I'm afraid it can be done correctly.

@ko1 I see, thank you.


Server error  503 despite successful upload to TestFlight

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I have successfully uploaded build to TestFlight many times but started getting error 503 today.
I have not made any modification to the lane.
What i have tried

Restarted laptop
Quit terminal and restarted in case iTunes session needs relogin
Apple system status all green

below is stripped down relevant output of lane
  Login to App Store Connect<EMAIL_ADDRESS>    Login successful
    Ready to upload new build to TestFlight (App:<PHONE_NUMBER>)...
    Going to upload updated app to App Store Connect
    This might take a few minutes. Please don't interrupt the script.
    iTunes Transporter successfully finished its job
    ------------------------------------------------------------------------------------------------------------------
    --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
    ------------------------------------------------------------------------------------------------------------------
    Successfully uploaded the new binary to App Store Connect
    If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
    Note that if `skip_waiting_for_build_processing` is used but a `changelog` is supplied, this process will wait for the build to appear on AppStoreConnect, update the changelog and then skip the remaining of the processing steps.
    Waiting for processing on... app_id:<PHONE_NUMBER>, app_version: , build_version:, platform: IOS
    Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997
    Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)
    Waiting for App Store Connect to finish processing the new build () for IOS
    Successfully finished processing the build  for IOS
    Successfully set the changelog for build
    Distributing new build to testers:

fastlane environment
### Captured Output

  Command Used: `--capture_output`
  Output/Log

  ```

  DEBUG [2020-12-25 22:18:12.78]: Checking if there are any plugins that should be loaded...
  DEBUG [2020-12-25 22:18:12.79]: Loading 'fastlane-plugin-versioning' plugin
  INFO [2020-12-25 22:18:12.79]: gem 'fastlane-plugin-versioning' is already installed
  DEBUG [2020-12-25 22:18:12.80]: Loading 'fastlane-plugin-badge' plugin
  INFO [2020-12-25 22:18:12.80]: gem 'fastlane-plugin-badge' is already installed
  DEBUG [2020-12-25 22:18:12.81]: Loading 'fastlane-plugin-firebase_app_distribution' plugin
  INFO [2020-12-25 22:18:12.81]: gem 'fastlane-plugin-firebase_app_distribution' is already installed

  ```

  🚫 fastlane environment 🚫

  ### Stack

  | Key                         | Value                                       |
  | --------------------------- | ------------------------------------------- |
  | OS                          | 11.1                                        |
  | Ruby                        | 2.6.4                                       |
  | Bundler?                    | true                                        |
  | Git                         | git version 2.24.3 (Apple Git-128)          |
  | Installation Source         | ~/.rbenv/versions/2.6.4/bin/fastlane        |
  | Host                        | macOS 11.1 (20C69)                          |
  | Ruby Lib Dir                | ~/.rbenv/versions/2.6.4/lib                 |
  | OpenSSL Version             | OpenSSL 1.1.1d  10 Sep 2019                 |
  | Is contained                | false                                       |
  | Is homebrew                 | false                                       |
  | Is installed via Fabric.app | false                                       |
  | Xcode Path                  | /Applications/Xcode.app/Contents/Developer/ |
  | Xcode Version               | 12.3                                        |

  ### System Locale

  | Error                       |
  | --------------------------- |
  | No Locale with UTF8 found 🚫 |

  ### fastlane files:

  `./fastlane/Fastfile`

  ```ruby

  	lane :bump_version do |options|

  		increment_build_number_in_plist(target:  'app')
  		increment_build_number_in_plist(target:  'aptest')

  		increment_version_number(
  				bump_type: 'minor' # Automatically increment minor version number
  		)

  	end

  	# Lane to upload dsysms file to Crashlysitcs.
  	lane :upload_dsyms do |options|

  		scheme = options[:scheme]
  		if scheme == ""  or scheme == nil
  			UI.important "❌❌❌❌❌ No scheme provided so skipping uploading dsym to Firebase ❌❌❌❌❌"
  		else
  			gspPath = "./Source/Configs/Firebase/GoogleService-Info-#{scheme}.plist"
  			puts "Google services plisy file path - #{gspPath}"

  			upload_symbols_to_crashlytics(gsp_path: gspPath)
  		end
  	end

    lane :testflight_beta do |options|

  	bump_version

  	match(type: "appstore", app_identifier: ["bundle id"])

  	notification(title: "Fastlane TestFlight Lane", message: "Match complete",app_icon: ENV['ICON_PATH'])

  	build_app(

  		export_method: "app-store",
  		configuration: "Test",
  		scheme: "Test",
  		export_options: {
  			signingStyle: "automatic",
  			provisioningProfiles: {
  			"bundle id" => "match AppStore "bundle id"
  			}
      	},
  		export_xcargs: "-allowProvisioningUpdates"
    )

    	notification(title: "Fastlane TestFlight Lane", message: "Build finished",app_icon: ENV['ICON_PATH'])

  	upload_to_testflight(
  		username<EMAIL_ADDRESS>  		beta_app_feedback_email<EMAIL_ADDRESS>  		beta_app_description: "",
  		demo_account_required: true,
  		notify_external_testers: false,
  		changelog: "Some bug fixes and UI improvements.",
  		beta_app_review_info: {
  			contact_email<EMAIL_ADDRESS>  			contact_first_name: "A",
  			contact_last_name: "N",
  			contact_phone: "",
  			demo_account_name<EMAIL_ADDRESS>  			demo_account_password: "dummy",
  			notes:
  "Email based login
  - User Name -<EMAIL_ADDRESS>  		},
  		testers_file_path: "./all_testers_export.csv",
  		groups: "Internal, Family",
  		expire_previous_builds: true,
  		localized_app_info: {
  			"default": {
  				feedback_email<EMAIL_ADDRESS>  				marketing_url: "",
  				privacy_policy_url: "https://....",
  				description: ".....",
  			},
  		}
  	)

  	notification(title: "Fastlane TestFlight Lane", message: "Upload to AppStore done",sound: "Crystal", app_icon: ENV['ICON_PATH'])

  	# Upload dSYS file to Crashlysitcs
  	upload_dsyms(scheme:"Test")

  	notification(title: "Fastlane TestFlight Lane", message: "Upload to Crashlytics done",sound: "Magic Bell",app_icon: ENV['ICON_PATH'])
    end

  end

  ```

  **No Appfile found**

  ### fastlane gems

  | Gem      | Version | Update-Status |
  | -------- | ------- | ------------- |
  | fastlane | 2.170.0 | ✅ Up-To-Date  |

  ### Loaded fastlane plugins:

  | Plugin                                    | Version | Update-Status |
  | ----------------------------------------- | ------- | ------------- |
  | fastlane-plugin-versioning                | 0.4.4   | ✅ Up-To-Date  |
  | fastlane-plugin-badge                     | 1.4.0   | ✅ Up-To-Date  |
  | fastlane-plugin-firebase_app_distribution | 0.2.4   | ✅ Up-To-Date  |

  Loaded gems

  | Gem                                       | Version      |
  | ----------------------------------------- | ------------ |
  | bundler                                   | 1.17.2       |
  | etc                                       | 1.0.1        |
  | forwardable                               | 1.2.0        |
  | rake                                      | 12.3.3       |
  | CFPropertyList                            | 3.0.3        |
  | public_suffix                             | 4.0.6        |
  | addressable                               | 2.7.0        |
  | atomos                                    | 0.1.3        |
  | aws-eventstream                           | 1.1.0        |
  | aws-partitions                            | 1.402.0      |
  | aws-sigv4                                 | 1.2.2        |
  | jmespath                                  | 1.4.0        |
  | aws-sdk-core                              | 3.110.0      |
  | aws-sdk-kms                               | 1.39.0       |
  | aws-sdk-s3                                | 1.86.0       |
  | babosa                                    | 1.0.4        |
  | curb                                      | 0.9.10       |
  | fastimage                                 | 2.2.0        |
  | colored                                   | 1.2          |
  | highline                                  | 1.7.10       |
  | commander-fastlane                        | 4.4.6        |
  | dotenv                                    | 2.7.6        |
  | emoji_regex                               | 3.2.1        |
  | excon                                     | 0.78.1       |
  | multipart-post                            | 2.0.0        |
  | ruby2_keywords                            | 0.0.2        |
  | faraday                                   | 1.1.0        |
  | unf_ext                                   | <IP_ADDRESS>      |
  | unf                                       | 0.1.4        |
  | domain_name                               | 0.5.20190701 |
  | http-cookie                               | 1.0.3        |
  | faraday-cookie_jar                        | 0.0.7        |
  | faraday_middleware                        | 1.0.0        |
  | gh_inspector                              | 1.1.3        |
  | jwt                                       | 2.2.2        |
  | memoist                                   | 0.16.2       |
  | multi_json                                | 1.15.0       |
  | os                                        | 1.1.1        |
  | signet                                    | 0.14.0       |
  | googleauth                                | 0.14.0       |
  | httpclient                                | 2.8.3        |
  | mini_mime                                 | 1.0.2        |
  | declarative                               | 0.0.20       |
  | declarative-option                        | 0.1.0        |
  | uber                                      | 0.1.0        |
  | representable                             | 3.0.4        |
  | retriable                                 | 3.1.2        |
  | google-api-client                         | 0.38.0       |
  | digest-crc                                | 0.6.2        |
  | google-cloud-env                          | 1.4.0        |
  | google-cloud-errors                       | 1.0.1        |
  | google-cloud-core                         | 1.5.0        |
  | google-cloud-storage                      | 1.29.1       |
  | json                                      | 2.3.1        |
  | mini_magick                               | 4.11.0       |
  | plist                                     | 3.5.0        |
  | rubyzip                                   | 2.3.0        |
  | security                                  | 0.1.3        |
  | naturally                                 | 2.2.0        |
  | simctl                                    | 1.6.8        |
  | slack-notifier                            | 2.3.2        |
  | terminal-notifier                         | 2.0.0        |
  | unicode-display_width                     | 1.7.0        |
  | terminal-table                            | 1.8.0        |
  | tty-screen                                | 0.8.1        |
  | tty-cursor                                | 0.7.1        |
  | tty-spinner                               | 0.9.3        |
  | word_wrap                                 | 1.0.0        |
  | claide                                    | 1.0.3        |
  | colored2                                  | 3.1.2        |
  | nanaimo                                   | 0.3.0        |
  | xcodeproj                                 | 1.19.0       |
  | rouge                                     | 2.0.7        |
  | xcpretty                                  | 0.3.0        |
  | xcpretty-travis-formatter                 | 1.0.0        |
  | badge                                     | 0.12.0       |
  | fastlane-plugin-badge                     | 1.4.0        |
  | fastlane-plugin-firebase_app_distribution | 0.2.4        |
  | fastlane-plugin-versioning                | 0.4.4        |

  *generated on:* **2020-12-25**

App uploads are not available during holidays, Apple's policy 🙃

Oh! I thought servers would be working over holidays but time for some rest then 😀 thanks.


24 - updates for chef 14

Fixes #24 .

Not sure what's going on with the tests, looks like they never even got started:
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

This PR is a year old.  Wow!
FWIW, it applies cleanly on my hosts and fixes the problem.  And let's ignore that it took me this long to upgrade to what may become the last libre chef release.  :-D

Hi, sorry for the huge delay in merging this.  We are not using chef so much these days.

Late is always better than never!  Thanks!


Additional Hex Format Support (Hologram)

Add support for another hex format on holograms
Format: &#abc123

This was completed in #88


Remove double running of unit tests

The TorQ version of k4unit has a modification which stores the results of tests that are run. This means that tests are run twice, once to measure time/memory usage & once to store the output; after discussing with @ThomasSmyth we think this is a bug & it can cause unexpected behaviour due to tests running twice
@jonnypress do you know why this was added, and if it's needed? This PR simply removes, but perhaps we can rework it to do both in one run if necessary

If it was possible to run once, time it and keep the result that may be worthwhile. But otherwise this should be removed as the behaviour is unexpected IMO.

I think this is actually already (slightly) broken in the case repeat<>1 - in that case, k4unit injects a do[...] loop meaning there would be no return

I have a modification that does allow storing of the result as well as returning, however I realised another issue with this - if the return of first test is, e.g. an int, the KUrunresults table gets res column typed as int after first insert. If next test returns something else, we get a 'type on the upsert.
I'm struggling to see the use case for manually inspecting the return of unit tests, I think we should just get rid of this.


Feature: Speculative sampling / Assisted Generation

An obvious feature to me, but also not one that is simple to implement - is speculative sampling on the road map?
The idea would be using a second tiny-model combined with e.g. for greedy validation of the main model.
For more information:
https://huggingface.co/blog/assisted-generation
Example models for Speculative sampling:
https://huggingface.co/bigcode/tiny_starcoder_py
Related frameworks:
https://github.com/huggingface/text-generation-inference/issues/1169

Yes, it's on the roadmap

Hi @michaelfeil Speculative Decoding is on our roadmap. Are you looking a draft model or self-speculative decoding? Or other?
Also, we will soon put out a rough set of requests we've received along with a rough roadmap so stay tuned!

will the specculative decoding support python runtime？

Hi @ywran ,
The support will be added to the C++ runtime first. We are also taking the question of a Python runtime seriously and are evaluating the best approch to offer a Python binding of our C++ runtime. We do not have a concrete timeline for now but we are going to keep everyone updated as we make progress.
Thanks,
Julien

Hi @michaelfeil Speculative Decoding is on our roadmap. Are you looking a draft model or self-speculative decoding? Or other?
Also, we will soon put out a rough set of requests we've received along with a rough roadmap so stay tuned!

Primarily looking into speeding up e.g. starcoder(15B) with "old style" assisted generation, e.g. https://huggingface.co/bigcode/tiny_starcoder_py. If you got additional ideas, I am open to discuss.

We are making the required improvements to the MHA kernels right now & are looking at a few different techniques for speculative decoding. Keep an eye out over the few weeks for more details

Hey @ncomly-nvidia can you please tell us when we can be able to test assisted Generation on TensorRT?

Hey @Dev-hestabit. Our goal is to have a functional preview of speculative decoding in the next release (<1 month). We'll be sure to include it in the discussion  when it is added to main & release notes once included officially.

@ncomly-nvidia What models are planned to have support for speculative decoding?

@ncomly-nvidia I am interested in encoder-decoder type models like T5. I am not sure if its possible to do speculative decoding on enc-dec though :)

@ncomly-nvidia i have been going through tensorrt backend commits and 4 days ago there are update for speculative decoding deployment
https://github.com/triton-inference-server/tensorrtllm_backend/commit/130999578896e8cca24aae58fa93fed4c2f22141
can we try speculative decoding with tensorrtllm backend?
is there any document that can help us as there is no update in readme for that repo .

Yep!
We're working on an example w/ docs now - there is an implementation you can reference here

Assisted Generation implemented with transformers:
https://huggingface.co/blog/gemma-july-update#assisted-generation
We need tensorrt add assisted-generation

Please refer to https://nvidia.github.io/TensorRT-LLM/advanced/speculative-decoding.html
please feel free to reopen this ticket if needed.


Remove calls to HashAlgorithm.ComputeHash

Calls to HashAlgorithm.ComputeHash should be removed from the documentation.

@bartonjs

What's the reason for removing calls to HashAlgorithm.ComputeHash?
Calls to ComputeHash in code examples are for specific algorithms -- does this mean we want to remove all calls to ComputeHash for all algorithms?
Does "remove calls ... from the documentation" mean delete any snippets that contain such calls? Or keep the snippets but replace the ComputeHash calls with something else?

I'm... not sure.
ComputeHash is the preferred API to use on HashAlgorithm... anything that uses TransformBlock or TransformFinalBlock should be rewritten to use IncrementalHash.
My best guess is it was meant for MD5/SHA1, but since the member lives on HashAlgorithm it ended up being collapsed down to HashAlgorithm.
I think my recommendation here is to close it as non-actionable/lost-context.


chore: Adding local testing documentation to contributing guide.

Hi team, just adding some stuff to the guide that maybe useful for contributors.

Apologies, this got closed on its own because I deleted the fork. Reopening it for @chingor13's approval.

Can you check the formatted view? I don't think you fixed the problem.

Closing this in favor of #1743.


Uncaught Error: Cannot call compile without the template compiler loaded. Please load ember-template-compiler.js prior to calling compile.

I am not sure why the compiler is not loaded, I am using the default settings.

Somehow I was using Canary, fixed it.

I am  having the same problem. please how did you fix it?

Sorry, this is an ember-rails bug addressed at https://github.com/emberjs/ember-rails/issues/447 .
I'll fix it this night and will release a new version.
@crux25
If you are in a hurry, you can use ember-template-compiler.js hosted by http://emberjs.com.
(such as http://builds.emberjs.com/tags/v1.10.0/ember-template-compiler.js )

see also http://emberjs.com/blog/2015/02/07/ember-1-10-0-released.html#toc_new-features-in-ember-js-1-10

@tricknotes
Thanks for your response.

I released a new version<EMAIL_ADDRESS>with fix for this issue.
This version allow you to use //= require ember-template-compiler in your JS.
@crux25
If it doesn't solve yet, please ping me.
BTW: When you use handlebars precompilation (just using app/assets/javascripts/templates/*.js.hbs), you don't have to use ember-template-compiler.js and will take performance advantage.

I have tested the new version and it fixed the issue.
Thanks @tricknotes

:sunglasses:

I'm having the same problem using ember-rails 0.6.14 and ember.js 1.10.0.  When I try using "require ember-template-compiler", I get another error: "Uncaught ReferenceError: exports is not defined".  I put the "require ember-template-compiler" statement right after handlebars and ember.  Does this need to go somewhere else?

@tricknotes I'm having this issue with the latest build. I am not using ember-rails at all. I'm strictly going off the embers getting started tutorial. Any ideas?


Defer deletion of service backends to pod deletion.

(Will need to add/fix tests here, but just wanted to open the PR for initial feedback on the proposed approach)
Currently backend entries are deleted from the map as soon
as the service refCount for a backend goes down to 0. This behavior has
the consequence of causing conntrack for any long-lived connections pointing
to those backends to break. There are valid uses cases to persist and
drain already established connections to backends, past when any services
actively point to them--such as changing the label-selector on a service
for blue-green rollouts, etc.
This commit defers the deletion of the backend map entries to when the
associated pod is deleted, thus allowing for long-lived connections to
any service backends to be drained.
Fixes: #23761
Signed-off-by: Yash Shetty<EMAIL_ADDRESS>

Thanks for the PR.
Which event is K8s expected to send first, an endpoint-delete or a pod-delete? Currently, from what I can tell we trigger deletion from the BPF maps based on the former. I'm trying to understand the "defer" angle here from your description.
Yes and yes. We should expect endpoint-delete (more precisely endpointslice-update) event before a pod-delete, since an endpoint being removed from a service doesn't necessarily mean a pod going away; and the current trigger for backend deletion is the former.

I try to explain some of the details in the CFP (#23761), but the high level is that currently a backend entry gets removed from the backends_map when an endpointslice-update event to remove the backend from a service is received. However this breaks any existing connections that point to the backends that were deleted, even though the associated pods might still be running and ready. The "defer" aspect of this proposal is to keep the backend entries around until the actual pods are deleted -- in order to drain any existing connections to those pods, past when any services actively point to them.

I don't follow: deleteOrphanBackends that this PR is deleting is called when cilium agent is restarted. This is a case where backends might have been deleted/updated when the agent was down. Can you add more details about the issue you are trying to address?

@aditighag added some more details about what this PR tries to accomplish in the previous comment. Essentially we want to tie the cleanup of the backend map entries to the deletion of pods, whereas deleteOrphanBackends simply looks at the backendRefCount.  Let me know if that makes sense.

Drive-by assessment as Triager for the week, it seems like this either needs further discussion or otherwise the PR needs to be fixed up? If it helps, you could consider raising a discussion topic during an upcoming community meeting (weekly on wednesdays, details are in docs.cilium.io).

I guess there is valid edge case where pods might be deleted while the agent is down... in which case the backend entries for those pods would not get cleaned up.

Yes, this can occur and we need to ensure cleanup occurs in this scenario.


Align GrammaTech SW Component Identifiers

Backgroud : Boeing's artifact drop (ARCOS_BoeingPhase2_drop3a_software) seems to be missing package specification files. This caused problems when using libadalang to resolve module cross references. We emailed Doug Stuart via MessageCourier on 11/9/2022 with specific examples of package bodies without package specifications. In the meantime, Eric hand edited/corrected SWCOMPONENTs to include in the Apache Ingestion package of 11/21 (Apache-IngestionPackage-wSW-RACKv11-20221121). GT was able to align their data with the hand edits, which is also supplied as part of the 11/21 package.
Criteria for resolution: Boeing should supply a complete software package without any missing files. The current "hack" to produce the SWCOMPONENTs for ingestion is not sustainable.

Waiting for a response to @kityansiu 's message from Boeing

Closing this issue because it had to do with Phase 2 data. In Phase 3, Boeing should be exercising the ARCOS tools with a complete software package.


o-footer does not build

What
o-footer does not build via oax, it looks to be an issue with a dependency having non-js files in the bower.json.main array. If I modify the o-toggle/bower.json.main array to only have js files, then building o-footer works.
Details
>oax --input /Users/jake.champion/Code/repo-data-cli/components/o-footer/main.js --for-bower
oax: module 'o-toggle' not found in /Users/jake.champion/Code/repo-data-cli/components/o-footer/src/js/footer.js

the bug must be here: https://github.com/Financial-Times/oax/blob/25a6a72196b09291058da983e8a326685e9cc141/src/manifest.rs#L287-L301

The bug is fixed if the main array has the js file as the last item.
builds:
main": [
    "main.scss",
    "main.js"
  ],

does not build:
main": [
    "main.js",
    "main.scss"
  ],


go/token: AddFile induces heavy contention in parallel parsing [freeze exception]

https://go-review.googlesource.com/c/go/+/411909 reduces two sources of contention in parser-heavy workloads: FileSet.AddFile allocates memory in the middle of an otherwise tiny critical section, and FileSet.Pos uses a mutex to guard a cache, turning read-only operations into exclusive locks. Both are major sources of contention in gopls.
I'd like to include the fix in the next release.
@golang/release @gri @findleyr

This change doesn't seem to pose a significant risk. The release candidate has not been released yet. This change is approved.


ReferenceError: webpackJsonp is not defined

Hi,
I used angular universal according to this article (an article that publishes at wiki angular-cli). all of the steps work fine but in last step (npm run serve:ssr) below error shows:
c:\xampp\htdocs\angular\roxo\dist\server.js:46302
webpackJsonp([1],{0:function(e,r,t){e.exports=t("Zq8w")},LTsh:function(e,r,t){"use strict";Object.defineProperty(r,"__esModule",{value:!0});var u=fun
ction(){function e(){}return e}();r.AppServerModule=u},Zq8w:function(e,r,t){"use strict";Object.defineProperty(r,"__esModule",{value:!0});var u=t("LT
sh");r.AppServerModule=u.AppServerModule}},[0]);
^

ReferenceError: webpackJsonp is not defined
    at Object.defineProperty.value (c:\xampp\htdocs\angular\roxo\dist\server.js:46302:1)
    at __webpack_require__ (c:\xampp\htdocs\angular\roxo\dist\server.js:20:30)
    at Object.module.exports.module.deprecate (c:\xampp\htdocs\angular\roxo\dist\server.js:102296:10)
    at __webpack_require__ (c:\xampp\htdocs\angular\roxo\dist\server.js:20:30)
    at c:\xampp\htdocs\angular\roxo\dist\server.js:66:18
    at Object.<anonymous> (c:\xampp\htdocs\angular\roxo\dist\server.js:69:10)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)

i use angular 4.0.0 and these line is my package.json:
{
  "name": "roxo",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "build:ssr": "npm run build:client-and-server-bundles && npm run webpack:server",
    "serve:ssr": "node dist/server.js",
    "build:client-and-server-bundles": "ng build --prod -a home && ng build --prod -a server --output-hashing=false",
    "webpack:server": "webpack --config webpack.server.config.js --display-entrypoints --progress --colors"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^4.0.0",
    "@angular/common": "^4.0.0",
    "@angular/compiler": "^4.0.0",
    "@angular/core": "^4.0.0",
    "@angular/forms": "^4.0.0",
    "@angular/http": "^4.0.0",
    "@angular/platform-browser": "^4.0.0",
    "@angular/platform-browser-dynamic": "^4.0.0",
    "@angular/platform-server": "^4.0.0",
    "@angular/router": "^4.0.0",
    "@ng-bootstrap/ng-bootstrap": "^1.0.0-beta.4",
    "@nguniversal/module-map-ngfactory-loader": "^1.0.0-beta.3",
    "angular2-persian-pipes": "0.0.6",
    "bootstrap.native": "^2.0.19",
    "core-js": "^2.4.1",
    "enhanced-resolve": "^3.3.0",
    "hammerjs": "^2.0.8",
    "jalali-moment": "^2.1.3",
    "jquery": "^2.2.4",
    "lg-autoplay": "^1.0.4",
    "lg-fullscreen": "^1.0.1",
    "lg-hash": "^1.0.4",
    "lg-pager": "^1.0.2",
    "lg-share": "^1.1.0",
    "lg-thumbnail": "^1.1.0",
    "lg-video": "^1.2.0",
    "lg-zoom": "^1.1.0",
    "lightgallery": "^1.6.6",
    "ng-recaptcha": "^3.0.3",
    "ng-spin-kit": "^5.1.1",
    "ng2-carouselamos": "^3.2.0",
    "ng2-ckeditor": "^1.1.9",
    "ng2-jalali-date-picker": "^2.0.3",
    "ng2-typewriter": "^1.1.0",
    "ng2-validation": "^4.2.0",
    "ngx-bootstrap": "^1.9.3",
    "ngx-carousel": "^1.3.3",
    "ngx-pagination": "^3.0.1",
    "ngx-toastr": "^6.2.1",
    "primeng": "^4.2.1",
    "rxjs": "^5.1.0",
    "ts-loader": "^3.5.0",
    "zone.js": "^0.8.20"
  },
  "devDependencies": {
    "@angular/cli": "1.7.3",
    "@angular/compiler-cli": "^4.0.0",
    "@angular/language-service": "^4.0.0",
    "@types/core-js": "^0.9.46",
    "@types/jasmine": "~2.5.53",
    "@types/jasminewd2": "~2.0.2",
    "@types/jquery": "^3.2.16",
    "@types/node": "~6.0.60",
    "codelyzer": "~3.0.1",
    "jasmine-core": "~2.6.2",
    "jasmine-spec-reporter": "~4.1.0",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.1.1",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "persian-date": "^1.0.1",
    "primeng": "^4.2.2",
    "protractor": "~5.1.2",
    "ts-node": "~5.0.1",
    "tslint": "~5.3.2",
    "typescript": "~2.7.1",
    "video.js": "^6.6.3"
  }
}

Can anyone help me on the above issue, please?

I'm sorry, but we can't reproduce the problem following the instructions you provided.
Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue.
Short, explicit instructions make it much more likely we'll be able to reproduce the problem so we can fix it.
If the problem persists, please open a new issue following our submission guidelines.
A good way to make a minimal repro is to create a new app via ng new repro-app and add the minimum possible code to show the problem. Then you can push this repository to github and link it here.


Are there any plans for MJSXJ03HL?

Are there any plans for MJSXJ03HL?
Great work!

Not in the near future.

Waiting for version for MJSXJ03HL if it's possible


Editor no tabs: description part of label no longer overflows: ellipsis

Steps to Reproduce:

disable tabs
have a description part that overflows into actions:

=> 🐛 no more "..." in the description part of the label
Seems to be caused by this rule:
https://github.com/Microsoft/vscode/blob/6e559261f677793fea424c6eb5cb13d0301ffff1/src/vs/workbench/browser/parts/editor/media/notabstitlecontrol.css#L25

@bpasero please provide steps to reproduce

Sorry, I had breadcrumbs enabled and was confused.


moon phases and planet tilts fixed

Fixed luna phase being incorrect on night 0
Fixed other moons in solar system inappropriately having phases
Yes, I know I was responsible for luna phase being off. But I fixed it!

The default axis is 90° off from where it should be. I did not fix this, and instead merely rotated everything else.
Mercury, Venus, Mars, Ceres, Vesta, Jupiter, Uranus, and Neptune have been rotated -90°+real axis tilt.
Earth was rotated -180°, as it was set to 90°.
Saturn was just fine.
Uranus' graphic was rotated yet again, so that its rings and moons line up with each other.
Pluto, Charon, and the moons of the gas giants were not touched.
Proxima B, Proxima C, and Proxima D have been rotated as well, though to arbitrary amounts due to the real amounts being unknown.


angular-fullstack:route never specified for problem 07

Problem 06 specifies to run angular-fullstack:endpoint, however it is never said to run angular-fullstack:route in order to create the html templates.

@jacksondavis thank you. added the text.


[pickles] refactor uncorrelated tests + add test for impossibly large domain size

I'm still not sure I understand why stmt.proof_state.deferred_values.branch_data.domain_log2 is 15 in the current test (when the step circuit seems much smaller)

OK, so the Proof.verify_promise errors with the following when I modify the domain from 15 to 16:
Pickles.verify dlog_check
 "b: 0x31CEF482CF2FD4F1781E3309F6F8A516E301D84315FA35A3EB691C3857335E59 != 0x0A9A1F39017100E0127FCC84B00A485FB55AE3D20779AD6D74C79A951FA043D8"
 "combined_inner_product: 0x39E85E659F9734015CC8919226E4000C46E03572AD568BF71665C9DE42329A7F != 0x3CA652488E90D728506B5C0A1B54F1638876BB035FAC2EAEA3A4F3C323E813DD")

As I don't modify these values in my test, my explanation is that it uses the wrong domain to compute something (perhaps w^domain_size) which is used in these checks. So now we can:

think that the check in https://github.com/MinaProtocol/mina/pull/12416/files#diff-823940d61ae33ca1da540d9f602d3047c620264b5593469bf75ed32f67f8892fR90 was not necessary as this get caught anyway
try to modify the b and combined_inner_product values to correspond to the correct values. But presumably this will just make the proof not work anyway

another note, moving to domain size 17 triggers the failure from the fix as well in pickles.verify:
File "src/lib/pickles/pickles.ml", line 2144, characters 8-367: should not be able to verify invalid proof threw
(Failure
   "DEBUG ERROR1: (Pickles.verify dlog_check\
  \n \"b: 0x2F0D595323B410363FD8F6339F0042EAD90E78A877F4CEBC5AC67F601D70AB77 != 0x38590C68EA018ACA835DCEF9DC5E977B2A51EA36953300E5E0FF13837173167F\"\
  \n \"combined_inner_product: 0x0529CE4CCDF8FD7A0D09EAD4B6ECAFB43BF604E1F458D13150DBC69F2A135287 != 0x21FB0F66D7EC9D50D6227889C6BF438029AF8B498C51B257295092C3091E9396\"\
  \n \"domain size is small enough\")@.").

playing around I got this error: "This circuit was compiled for proofs using the wrap domain of size 15, but a proof was given with size 14. You should pass the ~override_wrap_domain argument to set the correct domain size."
I'm not sure if this actually the error that the other tests were/are triggering. If so this is not at all what we're trying to test, so we should make sure that we're triggering the right errors

looks like this has been implemented here as well https://github.com/MinaProtocol/mina/pull/12610 so closing this one


Go 117 dependency update

Description
Updated the go version of this module to 1.17 and updated the version of all of the module dependencies to latest.
All of the otel modules were updated to newer versions bringing with it many changes in the code to accommodate. Most of the changes are method & attribute name changes in the otel libraries.
GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

N/A

Checklist:

[x] I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
[x] I have verified that new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degenerate
[x] I have maintained at least 90% code coverage
[x] I have commented my code, particularly in hard-to-understand areas
[N/A] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have maintained backward compatibility

How Has This Been Tested?

[ ] End to End integration test with Observability (PENDING)

actions.yaml has following:
steps:
- name: Set up Go 1.14+
uses: actions/setup-go@v2
with:
go-version: ^1.14

run e2e test

run e2e test pass

e2e test pass

e2e pass


bflb_fw_post_proc: Please ship sources not binaries

After compiling an example successfully I now see the following errors (were not there a couple of weeks ago):
[100%] Built target iso11898_selftest_bl616.elf
/bin/sh: ./../../../../tools/bflb_tools/bflb_fw_post_proc/bflb_fw_post_proc: cannot execute binary file
make[4]: *** [CMakeFiles/combine] Error 126
make[3]: *** [CMakeFiles/combine.dir/all] Error 2
make[2]: *** [CMakeFiles/combine.dir/rule] Error 2
make[1]: *** [combine] Error 2
make: *** [build] Error 2

Then I realised that you ship binaries for 2 platforms instead of just having the source code for those tools compiled alongside?:
% file ../../../../tools/bflb_tools/bflb_fw_post_proc/*
../../../../tools/bflb_tools/bflb_fw_post_proc/bflb_fw_post_proc:     ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=4e2fd900053073a864e7e386b70f8ef7ae0df959, stripped
../../../../tools/bflb_tools/bflb_fw_post_proc/bflb_fw_post_proc.exe: PE32 executable (console) Intel 80386, for MS Windows

% uname -a
Darwin m1.local 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103 arm64 arm Darwin

Could you please delete the binaries and add source code that produces those binaries instead?
Similar story goes to the CMake shipped as a binary:
% ls -alh ../../../../tools/cmake/bin
total 11M
drwxr-xr-x 4 rvalls staff 128 Feb 18 21:58 .
drwxr-xr-x 4 rvalls staff 128 Jan 28 08:10 ..
lrwxr-xr-x 1 rvalls staff  23 Jan 28 13:38 cmake -> /opt/homebrew/bin/cmake
-rw-r--r-- 1 rvalls staff 11M Jan 28 08:10 cmake.exe

My symlink in :point_up: is not the best solution, just a lazy workaround. Your whole build system should assume that the user's system CMake should be used instead.

Agree !
The development echo-system of BL chips is messed up.
There are:

2 sdks : bl_iot_sdk / bl_mcu_sdk, which differ a lots.
4 official flash tool: BLDevCube / BLFlashCommand / bflb-mcu-tool /bflb-iot-tool.

BLDevCube and BLFlashCommand are close sourced.
what's the difference between bflb-mcu-tool with bflb-iot-tool?
no one can replace others.
no one acts full functionality except BLDevCube, but it is not for cli.

a lot of third party flash tool. OK, we can ignore them...

Expected:

one sdk
one opensource flash tool with cli and gui support.

Iot sdk does not update at all, please use mcu sdk(it will be named bouffalosdk)
please use BLFlashCommand from now, cli and gui support
bflb-mcu-tool flashes only firmware, bflb-iot-tool flashes firmware + boot2+dts+partition+other thirty-party firmware.

We do not want to depend on python environment so provide bin.

Flash tool does not release with open, thanks.

BLFlashCommand is also GUI?

BLFlashCommand is also GUI?

Will push gui.

make with CAMKE= will use user cmake.

I have said, if you use mcu sdk, you can use our new flash tool.

Do not support multi groups, thanks. It is history.

#108

OK, I understand, BLFlashCommand / Cube designed for bl_mcu_sdk build system and only work with current bl_mcu_sdk.
Would you mind help me to commit this path to bflb-mcu-tool and release a new version to pypi?  I did not find the upstream repo of bflb-mcu-tool. this patch did alter original args of bflb-mcu-tool, but export --group1-firmware and --group1-addr args as BLDevCube did and can be used to program low_load firmwares of classic bl808_linux.
--- bflb_mcu_tool.py.orig	2023-03-07 01:00:54.175808455 +0800
+++ bflb_mcu_tool.py	2023-03-07 00:56:35.977075903 +0800
@@ -2349,6 +2349,13 @@
         bflb_utils.printf("firmware is not existed")
         sys.exit(1)

+    if args.group1_firmware:
+        group1_firmware = args.group1_firmware.replace('~', expanduser("~"))
+    else:
+        group1_firmware = None
+    if not group1_firmware or not os.path.exists(group1_firmware):
+        bflb_utils.printf("group1 firmware is not existed")
+
     if args.dts:
         dts = args.dts.replace('~', expanduser("~"))
         if not os.path.exists(dts):
@@ -2524,10 +2531,13 @@
         config["public_key_cfg-group1"] = ''
         config["private_key_cfg-group1"] = ''
         config["img1_group"] = "group0"
-        config["img2_group"] = "unused"
+        if not args.group1_firmware:
+            config["img2_group"] = "unused"
+        else:
+            config["img2_group"] = "group1"
         config["img3_group"] = "unused"
-        config["img2_file"] = ""
-        config["img2_addr"] = ""
+        config["img2_file"] = group1_firmware
+        config["img2_addr"] = args.group1_addr
         config["img3_file"] = ""
         config["img3_addr"] = ""
         config["img1_file"] = firmware
@@ -2538,6 +2548,14 @@
                 config["img1_addr"] = "0x" + args.addr.replace("0x", "")
         else:
             config["img1_addr"] = "0x58000000"
+
+        if args.group1_addr:
+            if args.group1_addr == "0x2000" or args.group1_addr == "2000":
+                config["img2_addr"] = "0x58000000"
+            else:
+                config["img2_addr"] = "0x" + args.group1_addr.replace("0x", "")
+        else:
+            config["img2_addr"] = "0x58000000"
     else:
         bflb_utils.printf("Chip type is not correct")
         sys.exit(1)
@@ -2581,6 +2599,11 @@
                         default=firmware_default,
                         help="image to write")
     parser.add_argument("--addr", dest="addr", default="0x2000", help="address to write")
+    parser.add_argument("--group1-firmware",
+                        dest="group1_firmware",
+                        default=None,
+                        help="group1 image to write")
+    parser.add_argument("--group1-addr", dest="group1_addr", default="0x2000", help="address to write")
     parser.add_argument("--dts", dest="dts", help="device tree")
     parser.add_argument("--build", dest="build", action="store_true", help="build image")
     parser.add_argument("--erase", dest="erase", action="store_true", help="chip erase")
@@ -2604,6 +2627,9 @@
         bflb_utils.printf("Serial port is not found")
     bflb_utils.printf("Baudrate is " + str(args.baudrate))
     bflb_utils.printf("Firmware is " + str(args.firmware))
+    if args.group1_firmware:
+        bflb_utils.printf("Group1 Firmware is " + str(args.group1_firmware))
+        bflb_utils.printf("Group1 Addr is " + str(args.group1_addr))
     bflb_utils.printf("Device Tree is " + str(args.dts))
     bflb_utils.printf("==================================================")
     config = get_value(args)


bottles: translate<EMAIL_ADDRESS>to fooAT1.2

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully run brew tests with your changes locally?

Guess who hates special characters? Bintray hates special characters! Need to do the translation here as well so things like<EMAIL_ADDRESS>don't cause Bintray to reject our upload.
Follow up to https://github.com/Homebrew/brew/pull/812.

Coverage decreased (-0.004%) to 57.889%

Oh, come on 😆.

Guess who hates special characters? Bintray hates special characters!

What is the actual error message? Could it be that an @ is perfectly valid in a package name on Bintray, but we simply fail to properly escape this character when constructing the Bintray API request URL? If not, are you aware of a list of valid characters that can be used in Bintray package names? The reason I'm asking all these questions is that the full-caps AT in the package name looks fairly ugly (to me). Once we start using it, it will be difficult to impossible to revise this decision. Maybe there's a better replacement character we can use, like x for +.

Coverage decreased (-0.004%) to 57.889%

Oh, come on 😆.

If you felt like addressing this, it should be fairly straightforward to add some unit tests for the methods in Utils::Bottles::Bintray. Given that the current implementation of this PR is broken, that's a strong indicator we would benefit from those tests.

Could it be that an @ is perfectly valid in a package name on Bintray,

It's not, I checked the website:
Package name can only contain letters, numbers and the following characters: .-_:

I do occasionally follow up on curious errors 😉.

If you felt like addressing this, it should be fairly straightforward to add some unit tests for the methods in Utils::Bottles::Bintray. Given that the current implementation of this PR is broken, that's a strong indicator we would benefit from those tests.

I'll take a peek, but I'm not convinced coverage isn't a little broken. This PR failed coverage tests & all I was doing there is tweaking existing lines from http to https 😕.

I do occasionally follow up on curious errors 😉.

Thanks!
From the listed characters, would you consider : a viable replacement character for @ on Bintray? I think openssl:1.1 reads a lot nicer than opensslAT1.1, : isn't currently used in formula names, and it isn't a valid character in a formula (class) name.

I'll take a peek, but I'm not convinced coverage isn't a little broken.

The change in coverage makes sense here. You added a line to a method that wasn't covered, so the number of relevant lines increased, but the number of covered lines did not, hence the (very small) drop in coverage.

This PR failed coverage tests & all I was doing there is tweaking existing lines from http to https 😕.

This is a different case as far as I can tell. The latest Travis job for the PR failed very early before it could run the test suite and generate the coverage report. The Travis job that was supposed to run after the merge is still pending. Or am I overlooking something?

From the listed characters, would you consider : a viable replacement character for @ on Bintray?

I guess I don't have a strong objection as long as you don't mind the inconsistency of it being opensslAT11 in the formula<EMAIL_ADDRESS>for the filename & openssl:1.1 on Bintray. I like consistency but I'm not overly fussed here if you've a strong positive feeling for it.

The Travis job that was supposed to run after the merge is still pending. Or am I overlooking something?

There was a coverage/coveralls — job in the PR, which failed, IIRC. The Travis problems started after that was merged, I think. Could be wrong though!

: for bottles in place, tests added.

FWIW, the colon is weird.
If the file names for bottles in HOMEBREW_CACHE are going to have this colon, they get presented by the Finder as having a slash in place of the colon.  I think that looks unacceptably weird in a filename on a Mac.
If the file names of bottles in the cache don't have the colon---if that's just what they're called on Bintray's servers---that seems fine.

If the file names of bottles in the cache don't have the colon---if that's just what they're called on Bintray's servers---that seems fine.

{"openssl@1.1":{"formula":{"pkg_version":"1.1.0","path":"Library/Taps/homebrew/homebrew-core/Formula/openssl@1.1.rb"},"bottle":{"root_url":"https://homebrew.bintray.com/bottles","prefix":"/usr/local","cellar":"/usr/local/Cellar","rebuild":0,"tags":{"el_capitan":{"filename":"openssl@1.1-1.1.0.el_capitan.bottle.tar.gz","sha256":"1c387846400ee0d03713c935f1ce14f558dfa48c0d18b9146cb52246828637c4"}}},"bintray":{"package":"openssl:1.1","repository":"bottles"}}}

👍 to this PR. Would be good (if we haven't already) to specifically audit (or actually block) formulae now with AT, : or @ to avoid 💥 (but can be another PR).

Would be good (if we haven't already) to specifically audit (or actually block) formulae now with AT, : or @ to avoid 💥 (but can be another PR).

I'm having a slow day. Can you clarify this as well? 🙈. I think you're saying you want formulae audited to make sure people are using AT in the classname instead of @ or :, but I'm not 💯 on that belief.

@DomT4 Yeh, make sure they are using valid name formats in both the class name, formula name and filename.

@DomT4 I guess better late than never: Thanks for adding some tests and for giving some thought to my suggestions and eventually incorporating some of them. Much appreciated! :heart:


optionally change state on bug db integrations on regression reports

Now that we have regression reports, we should provide optional support for notification of bugs.
if we had a crash that is now fixed, we could mark the bug closed.
if we had a crash that is now crashing but the existing bug is closed, we could reopen the bug.
AB#39994556

Current implementation in OneFuzz seem to support described scenario.


FEATURE: SD-2985 add dashboard plugin config for ecommerce-demo

JIRA: SD-2985

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/204/ : SUCCESS in 7s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/211/ : SUCCESS in 3s

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/206/ : SUCCESS in 13s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/212/ : SUCCESS in 3s

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/207/ : SUCCESS in 11s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/213/ : SUCCESS in 3s

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/208/ : SUCCESS in 9s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-oss-check/214/ : SUCCESS in 4s

LGTM

Sonar scan result

No issue found. Congratulations!

More detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-public-demos-gate-PR89
To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'.

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/gooddata-public-demos/job/gooddata-public-demos-validation/209/ : SUCCESS in 10s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-merge-compliance-check/78/ : SUCCESS in 9s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-sonarqube-scan-zuul-gate/76/ : SUCCESS in 40s
https://checklist.intgdc.com/job/compliance/job/gooddata-public-demos-fossa-scanning-zuul/39/ : FAILURE in 5s (non-voting)


Correct spelling for "parameters"

 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.

I don't want to sign CLA. Shall I close this PR?

@vsopvsop, if you don't agree to the CLA, we can't accept your contribution.  If that's the case, close this PR.

If you don't want to accept the CLA we could we could fix this typo ourselves. The issue itself is trivial.

Accepted the CLA.

And thanks for the fix. I've merged your commit as 7cb8107735d8612a26ad95dfdec2141b0e0e6baa.


Move DNS providers into a separate package

This changeset moves the DNS challenge providers into a new dns_provider package.
This package a sibling of acme. I felt this was appropriate given the low amount of coupling between acme and dns_provider, and that this coupling can be reduced further. (The DNS providers don't need to know anything ACME-specific – they only need to be able to create and destroy TXT records with short TTLs – but that's a topic for a later changeset.)
All the providers are together in the dns_provider package to keep this changeset minimal. Similarly, all the providers are initialized the way they were before – usually by passing in empty strings – even though there are clear opportunities for cleanup.
The lego CLI interacts with this package via dns_provider.Registry. This registry provides a list of entries describing the available DNS challenge providers in exactly the way that lego help describes them, and lego help output is constructed based on the contents of this registry. Once the CLI decides it wants a specific entry, the CLI calls NewChallengeProvider() to yield an acme.ChallengeProvider.
Individual providers register themselves like:
func init() {
	Registry.addProvider("digitalocean", "DO_AUTH_TOKEN", func() (acme.ChallengeProvider, error) {
		return NewDNSProviderDigitalOcean(os.Getenv("DO_AUTH_TOKEN"))
	})
}

This pattern permits both additional refactoring into separate packages and conditional compilation (#111). Go guarantees that init() gets called after initializing imports and before main(), so there's no fuss for either of those changes.

Are you going to make some changes to this as #111 progresses?
I like the idea of a registry but does that mean we have a registry for every challenge?

Sure, I'll update this if it seems like it's on the right track. Would you like me to push each provider into a separate package as part of this PR?
I'm not sure if we'll need a registry for every challenge. For DNS specifically, I expect DNS providers to continue multiplying more rapidly than other types of providers, and I think DNS providers should ultimately satisfy an interface more specialized than acme.ChallengeProvider, so I think a dedicated DNS provider registry would make sense.

I rebased to the current master one step at a time.
(For my records, in case I screwed something up: 83d5b00 -> 15f5b71 -> bf762c5 -> 9f9c00a -> 03be013.)
@xenolf: please let me know how you'd like me to proceed in this PR.

Yes I feel like moving each provider into its own package is the way to go.
Something like lego/providers/dns for example.
How would you specialize the interface for DNS providers while still being able to use them with the current structure though?

I was leaning towards putting dns first in the package naming:

lego/dns: DNS support functions and type definitions (e.g. FQDN)
lego/dns/provider: home of the DNS provider Registry
lego/dns/provider/digitalocean: a DNS provider for DigitalOcean (imports lego/dns/provider, registers itself)
lego/dns/all_providers: a package that import _s each provider, registering them all

Providers would need to import lego/dns/provider but not lego/acme.
You mentioned in another issue that you'd like every challenge type to be solvable with just lego/acme, but DNS-01 has a lot of supporting machinery, and my first thought is that it should be an exception. Some applications simply do not require DNS-01 support, and if we pushed DNS-01 support entirely into lego/dns, we could free lego/acme of the rather heavy github.com/miekg/dns library. In that case, lego/dns could have all the DNS-specific logic and all the DNS-specific dependencies.
The key is that lego/acme would be entirely decoupled from DNS-01. If you want DNS-01, you'd import lego/acme, lego/dns, and lego/dns/provider/yourfavorite or lego/dns/all_providers; if you don't, you'd just import lego/acme. Pulling DNS out of lego/acme would mean that if you want to satisfy a DNS challenge automatically, you'd need to make a lego/acme.Client, find and instantiate the DNS provider you want, then client.SetChallengeProvider(DNS01, your_dns_provider). This sounds like a lot of effort, but in fact it's exactly how things work today, so I don't see any real downside beyond sacrificing the DNS-01 challenge type if you didn't import lego/dns.
Then I had a second thought: we could make a lightweight DNS-01 provider and ship it inside lego/acme. It would be similar to the current manual provider, except instead of asking you to create the record and then checking that your record made it to all the right places, it would ask you to create the record and wait until you're ready to proceed with the challenge. lego/acme would thus still be able to complete DNS-01 challenges right out of the box without needing to pull in lego/dns. You wouldn't have DNS-related automation, sure, but that's because you opted out – and as a result you also wouldn't have the dependency chain.

If you want DNS-01, you'd import lego/acme, lego/dns, and lego/dns/provider/yourfavorite or lego/dns/all_providers

This seems not intuitive to me. If I'd import lego/acme I'd expect it to be all of ACME. Importing lego/acme and then having to import lego/providers/dns/cloudflare would make sense to me.
You could still have all the heavy stuff inside the lego/providers/dns package.

Then I had a second thought: we could make a lightweight DNS-01 provider and ship it inside lego/acme. It would be similar to the current manual provider, except instead of asking you to create the record and then checking that your record made it to all the right places, it would ask you to create the record and wait until you're ready to proceed with the challenge.

This is exactly how the manual provider works. The DNS propagation check is done in the challenge code and was even moved out into the preCheckDNS variable. We basically can switch out the check on the fly. If we export that, we can change the pre-check if there is need for an actual DNS check and just have it being a no-op in the ACME package - this also gets rid of the github.com/miekg/dns dependency as that gets pushed to wherever we implement the function.

Closing this as #144 is now merged.


[ServiceBus] await error handler in session receiver

Currently in session receiver, we fire-and-forget user's error handler instead of awaiting it. This is causing problems when customer want to modify state in message handler, and want to roll back in case of error as currently we would carry on to abandon the message when error happens, then add credit. The same message could arrive and processed, while the error handling is still going on.
This PR changes it to wait for user error handler before proceeding. This behavior is also inline with other languages.

/azp run js - service-bus - tests

/azp run js - service-bus - tests

API change check
API changes are not detected in this pull request.

/azp run js - service-bus - tests


cannot import name 'TariffSelect' from 'homeassistant.components.utility_meter'

another update another issue....
https://github.com/home-assistant/core/pull/55690 causing the issue this time.
Logger: homeassistant.config
Source: config.py:633
First occurred: 08:22:50 (2 occurrences)
Last logged: 08:24:54

Package package_powercalc setup failed. Integration powercalc cannot import name 'TariffSelect' from 'homeassistant.components.utility_meter' (/usr/src/homeassistant/homeassistant/components/utility_meter/__init__.py) (See /config/packages/package_powercalc.yaml:6).

full error (section)
2022-03-22 10:36:26 ERROR (MainThread) [homeassistant.config] Platform error: sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config.py", line 877, in async_process_component_config
    platform = p_integration.get_platform(domain)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 603, in get_platform
    cache[full_name] = self._import_platform(platform_name)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 620, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
  File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/config/custom_components/powercalc/__init__.py", line 58, in <module>
    from .sensors.group import create_group_sensors
  File "/config/custom_components/powercalc/sensors/group.py", line 37, in <module>
    from custom_components.powercalc.sensors.utility_meter import create_utility_meters
  File "/config/custom_components/powercalc/sensors/utility_meter.py", line 7, in <module>
    from homeassistant.components.utility_meter import TariffSelect
ImportError: cannot import name 'TariffSelect' from 'homeassistant.components.utility_meter' (/usr/src/homeassistant/homeassistant/components/utility_meter/__init__.py)

HA 2022.4.0.dev20220322
Powercalc: "version": "v0.19.0-beta.3"
Not sure why it points to line 6/7 in my package though, there's nothing on tariff at all.:
##########################################################################################
# package Power calc
# https://github.com/bramstroker/homeassistant-powercalc
# https://github.com/bramstroker/homeassistant-powercalc/blob/master/docs/supported_models.md
##########################################################################################

powercalc:

  energy_sensor_naming: '{} device energy'
  power_sensor_naming: '{} device power'
#  create_utility_meters: true
#  utility_meter_types:
#    - hourly
#    - daily
#    - monthly
#    - yearly

sensor:

#rest of the package

this is quite a nasty issue since:
Logger: homeassistant.components.hassio
Source: components/hassio/__init__.py:599
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 10:31:13 (1 occurrences)
Last logged: 10:31:13

The system cannot restart because the configuration is not valid: Package package_powercalc setup failed. Component powercalc cannot import name 'TariffSelect' from 'homeassistant.components.utility_meter'
etc
etc

even with
powercalc:

  energy_sensor_naming: '{} device energy'
  power_sensor_naming: '{} device power'
  create_utility_meters: false

there's no way to restart the HA instance (other than taking out the Powercalc config)
backward compatibility mentioned in the HA PR is not happening ......

Hmm I see :-(.
Thanks for reporting again. Will have a look into this next weekend.

Just released v0.19.0-beta.7 which should fix this issue.

yes! and we're back I business! so cool.
got to love your concept of 'next weekend'.....
thanks Bram. you're a magician.

Haha, perfect!
Yes, I am quite busy and I don't want to make any promises on when to fix it. Managed to find a spare hour and was able to fix it.
This is quite a high prio issue for me as upgrade to 2022.4 will break things for all users. I am very happy that you are able to test these versions in beta stage and also highlight any issues which may arise with powercalc.


WIP: Feat/toggle ipfs implementation

Seeking feedback.  Working on enabling toggling between IPFS implementations.
I'm running into an issue. Essentially, after experimenting with a select component for the toggle in the WebUI settings page, but realized that it would add too much code for something that is essentially just a toggle.  So, instead of a select, I went with the checkbox which allowed me to just reuse most of the existing logic and just add a new hook.  Now the code I wrote (in src/hooks/implementation.js) executes on startup - it doesn't seem to have 'go' as a default, and I'm having trouble sorting out how to prevent it from trying to start the daemon a second time.  At least I think that's what this error means:
(node:26947) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED <IP_ADDRESS>:5001     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1161:14) (node:26947)
Here are a few more things that I know I'm seeking feedback on, but of course I'm open to any feedback.

What should I do with the flags in the daemon creator?  I found that I needed to disable them to get the JS node to spawn, but I'm not sure what they do.  Obviously, I'll want to re-enable those flags whenever go is enabled for the final commit, but what should I do when js is enabled?

Re: dependencies: I've got both ipfs and js-ipfs added as dependencies.  Are both necessary or are they redundant?  If so, should i pick one over the other?

Not in this PR but as far as the webui: is a checkbox sufficient for this or is the select preferable?

Obviously need to do some housekeeping: squash commits, rollback the change of apiAddress in webui/index.js , remove the logger in src/utils/daemon.js.  What other similar tasks jump out to you right away?  I'm unfamiliar with package-lock files, and not sure what I did to change this one, but is this something that should go in my git-ignore?  globally?

This is looking good!

What should I do with the flags in the daemon creator?

Good point. I just checked and  js-ipfs doesn't support those flags yet. We'll need something more like a deamon creator strategy that encapsulates the type of node  we  want to start and the args that it should be run with.

--migrate=true tells go-ipfs to auto-upgrade the layout of the $IPFS_HOME repo dir if it finds an existing one at an older version.
--routing=dhtclient is a tweak to tell go-ipfs to can get data from the global dht, but don't bother to participate the dht. It's an optimization to reduce how much work your local machine has to do.

Desktop will start with go-ipfs as the default option, so the repo will have been upgraded. We just need to test that the version of js-ipfs we bundle works with the same repo version as the go-ipfs version that we bundle. That's true for the latest releases of both right now, so we're good. We just need to keep an eye out for future releases that update the repo version, and wait till both js and go  are in sync again before releasing an update.
as the routing option is just an optimisation, it's ok to leave it out when using js-ipfs. The upcoming 0.34 release is adding more DHT support to js-ipfs, so that may change soon too.

Re: dependencies: I've got both ipfs and js-ipfs added as dependencies...

Yep that's fine. we can bundle both into the release so the user can pick between the two. It'll make the app larger, but I'm ok with that. If we want to get fancy in the future we can lazily fetch js-ipfs if the user chooses it. We could even allow picking explicit version numbers to allow comarisions and benchmarking, but it's not neeeded right now.

...is a checkbox sufficient for this or is the select preferable?

I think a select box is the right control for the question were asking the user. We're offering the choice between go-ipfs or js-ipfs rather than a "do you want js-ipfs on or off?"

Obviously need to do some housekeeping...

No need to squash commits in the PR,  I'll do that when we merge to master. You'll need to merge changes in from master...again, it's fine to merge, as I'll squash it all later into a single commit on master. The package-lock.json is a feature of npm  to let app developers pin all the transitive  dependencies in the the node_modules, and share them amoungst the team. Adding js-ipfs to the package.json will update the package-lock.json too, so that's fine!
shout if you have any more questions. We can jump on a call if that'd help. We also have a weekly team  catch up call on zoom every Wedneday at 4pm UTC if you'd like to join! You can see it on the IPFS communuity calendar<EMAIL_ADDRESS>

Closing (stale). Please re-open if needed. Thanks!


Fix link to FAQ in documentation

Fixes a broken link to the FAQ in the Quick Start tutorial.
This change breaks the linkage when the tutorial is viewed in Github but my guess is having a correct link on http://electron.atom.io/ takes precedence.
Cheers! :v:

Thanks for this, but actually the GitHub takes precedence, see also https://github.com/atom/electron/pull/4546#issuecomment-188614428.


Data Lake Store Videos

All of the videos in this section of https://docs.microsoft.com/en-us/azure/data-lake-store/data-lake-store-overview
render this page:  https://support.office.com/en-us/article/important-information-about-office-mix-preview-end-of-service-c1c04f84-a7bb-4602-9645-258017155258?ui=en-US&rs=en-US&ad=US   None of the videos are reachable.

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

ID: 30296110-2a2c-073d-068c-0c1485b6097a
Version Independent ID: feac830e-ebec-0254-60cf-e0225c85d916
Content: Overview of Azure Data Lake Store
Content Source: articles/data-lake-store/data-lake-store-overview.md
Service: data-lake-store
Product: unspecified
GitHub Login: @nitinme
Microsoft Alias: nitinme

@jloughlinMSFT Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

Video links are still broken, pointing to https://mix.office.com/watch/xxxxxxxxxxxxx

@jloughlinMSFT - Thanks for the feedback. I have made the change in the doc sources and you should see the updated article live by 06/05.

Thank you.


ACM-6652: Add installation of specific operators via OperatorPolicy

Allows using an OperatorPolicy to install an operator from scratch, without pre-existing resources. This PR also incorporates transition to a Reconcile pattern rather than the previous periodic pattern that utilized PeriodicallyExecOperatorPolicies. Caching was also added using the kubernetes-dependency-watches library, which required updating some packages.
Ref: https://issues.redhat.com/browse/ACM-6652

Oh! Test failed Let me know after the tests fixed

@JustinKuli I made the suggested changes, let me know if there's any I missed!


remix setup node is writing typescript to random js files in node_modules

What version of Remix are you using?
1.2.2
Steps to Reproduce
In our private repo this reproduces reliably with the following steps:
# pnpm install with force to reload any modified node_modules from npm
pnpm install --force

# check one of the files that gets corrupted
cat ../../node_modules/.pnpm/@mui+base@5.0.0-alpha.68_react-dom@17.0.2+react<EMAIL_ADDRESS># file is present but empty (correct state)

# go to remix app
cd apps/remix-app/

# run remix post install script {"old_postinstall": "remix setup node"}
pnpm run old_postinstall

# check one of the files that gets corrupted
cat ../../node_modules/.pnpm/@mui+base@5.0.0-alpha.68_react-dom@17.0.2+react<EMAIL_ADDRESS>
# export { createFileSessionStorage, unstable_createFileUploadHandler, unstable_createMemoryUploadHandler, unstable_parseMultipartFormData } from "@remix-run/node";
# ... (see "Actual Behaviour" below for  the full contents of the corrupted file)

I already spent an hour tracking down the cause of our builds breaking, I haven't had time to try and create a minimal repro but I would guess it goes like this:

create a monorepo with pnpm e.g. https://github.com/vercel/turborepo/tree/main/examples/with-pnpm
create a package that is a next app npx create-next-app@latest
install material ui in the next app npm install @mui/material
create a package that is a remix app
run pnpm install

But there are a lot of factors that might be involved so I don't know for sure if that would reproduce it. It happens every time the time in our repo though.
Expected Behavior
remix setup node should not write typescript into ../../node_modules/.pnpm/@mui+base@5.0.0-alpha.68_react-dom@17.0.2+react<EMAIL_ADDRESS>I'm not really sure that remix should be writing stuff into anything in node_modules really.
Actual Behavior
cat ../../node_modules/.pnpm/@mui+base@5.0.0-alpha.68_react-dom@17.0.2+react<EMAIL_ADDRESS>export { createFileSessionStorage, unstable_createFileUploadHandler, unstable_createMemoryUploadHandler, unstable_parseMultipartFormData } from "@remix-run/node";
export type { UploadHandler, UploadHandlerArgs } from "@remix-run/node";

export type { ServerBuild, ServerEntryModule, HandleDataRequestFunction, HandleDocumentRequestFunction, CookieParseOptions, CookieSerializeOptions, CookieSignatureOptions, CookieOptions, Cookie, AppLoadContext, AppData, EntryContext, LinkDescriptor, HtmlLinkDescriptor, PageLinkDescriptor, ErrorBoundaryComponent, ActionFunction, HeadersFunction, LinksFunction, LoaderFunction, MetaDescriptor, HtmlMetaDescriptor, MetaFunction, RouteComponent, RouteHandle, RequestHandler, SessionData, Session, SessionStorage, SessionIdStorageStrategy } from "@remix-run/server-runtime";
export { createCookie, isCookie, createSession, isSession, createSessionStorage, createCookieSessionStorage, createMemorySessionStorage, json, redirect } from "@remix-run/server-runtime";

export type { RemixBrowserProps, FormProps, SubmitOptions, SubmitFunction, FormMethod, FormEncType, RemixServerProps, ShouldReloadFunction, ThrownResponse, LinkProps, NavLinkProps } from "@remix-run/react";
export { RemixBrowser, Meta, Links, Scripts, Link, NavLink, Form, PrefetchPageLinks, ScrollRestoration, LiveReload, useFormAction, useSubmit, useTransition, useFetcher, useFetchers, useCatch, useLoaderData, useActionData, useBeforeUnload, useMatches, RemixServer } from "@remix-run/react";
export { Outlet, useHref, useLocation, useNavigate, useNavigationType, useOutlet, useParams, useResolvedPath, useSearchParams, useOutletContext } from "@remix-run/react";

duplicate of https://github.com/remix-run/remix/issues/2031


Running netlify login in WSL2 produces Error: spawn /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe ENOENT

Describe the bug
I'm trying to use the Netlify CLI within WSL2, however the login fails all the time, because it tries to access PowerShell from Windows (why does it do that and how does it even know about it?) although the C drive is not mounted in WSL.
Logging into your Netlify account.......
⠋ Waiting for authorization.../usr/lib/node_modules/netlify-cli/node_modules/netlify-redirector/lib/redirects.js:116
      throw ex;
      ^

Error: spawn /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
    at onErrorNT (node:internal/child_process:478:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn /mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe',
  path: '/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe',
  spawnargs: [
    '-NoProfile',
    '-NonInteractive',
    '–ExecutionPolicy',
    'Bypass',
    '-EncodedCommand',
    .....

Steps to reproduce
Maybe for reference, there was a similar issue with the NX tool https://github.com/nrwl/nx/issues/8409 and Nuxt 3 framework which was solved https://github.com/nuxt/framework/issues/4495
I would appreciate a fix for it very much.
Configuration
No response
Environment
System:
OS: Linux 5.10 Ubuntu 20.04.4 LTS (Focal Fossa)
CPU: (4) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Memory: 4.49 GB / 5.79 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 16.15.1 - /usr/bin/node
Yarn: 3.2.0 - ~/.yarn/bin/yarn
npm: 8.11.0 - /usr/bin/npm
npmPackages:
netlify-cli: ^10.7.1 => 10.7.1
npmGlobalPackages:
netlify-cli: 10.7.1

I've seen there is another related issue  with a solution, so I'll close this one.


Work around the problem of Helix sending 2 transitions for CONSUMING -> DROPPED

Helix might send 2 state transitions when a segment is dropped from a server. This behavior breaks the onConsumingToDropped() callback because it is only invoked when processing CONSUMING -> DROPPED state transition.
This PR added a cache for segments that just went through CONSUMING -> OFFLINE state transition to work around this problem.

Submitted a Helix issue to verify the observation: https://github.com/apache/helix/issues/2751

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

Comparison is base (17db0fd) 61.69% compared to head (d5ab682) 61.74%.
Report is 3 commits behind head on master.

Files
Patch %
Lines

...e/assignment/instance/InstanceTagPoolSelector.java
32.35%
22 Missing and 1 partial :warning:

...nstance/InstanceReplicaGroupPartitionSelector.java
94.58%
9 Missing and 6 partials :warning:

...r/helix/SegmentOnlineOfflineStateModelFactory.java
0.00%
15 Missing :warning:

...elix/core/periodictask/ControllerPeriodicTask.java
83.33%
1 Missing and 1 partial :warning:

...mmon/assignment/InstanceAssignmentConfigUtils.java
0.00%
1 Missing :warning:

...e/pinot/controller/helix/SegmentStatusChecker.java
0.00%
1 Missing :warning:

...assignment/instance/InstancePartitionSelector.java
50.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #12351      +/-   ##
============================================
+ Coverage     61.69%   61.74%   +0.04%
  Complexity      207      207
============================================
  Files          2424     2424
  Lines        132340   132512     +172
  Branches      20436    20481      +45
============================================
+ Hits          81651    81820     +169
- Misses        44693    44694       +1
- Partials       5996     5998       +2

Flag
Coverage Δ

custom-integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration2
0.00% <0.00%> (ø)

java-11
61.70% <83.42%> (+26.67%)
:arrow_up:

java-21
61.61% <83.42%> (+0.03%)
:arrow_up:

skip-bytebuffers-false
61.73% <83.42%> (+0.04%)
:arrow_up:

skip-bytebuffers-true
61.58% <83.42%> (+0.02%)
:arrow_up:

temurin
61.74% <83.42%> (+0.04%)
:arrow_up:

unittests
61.74% <83.42%> (+0.04%)
:arrow_up:

unittests1
46.92% <75.00%> (+0.01%)
:arrow_up:

unittests2
27.70% <82.57%> (+0.07%)
:arrow_up:

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

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


profiler: add function to hotapp which repeatedly allocates memory

This will allow non-empty Heap Alloc profiles to be collected on this app.

CC/ @aalexand, @jqll


Typo in Enum\Fields\CollectionListingFields

https://github.com/robwittman/shopify-php-sdk/blob/e384cb2971c8dddff4a047d60ead313a8fdfdb74/src/Enum/Fields/CollectionListingFields.php#L5
'AbstractObject' should be 'AbstractObjectEnum' - new user here, could someone confirm/fix before I submit a PR?

I fixed this in #46