[Service Bus Client] Migrate Outstanding Changes in the Dedicated Repository

Summary
Since the initial migration of the Service Bus client library to the Azure SDK central repository, the service team has continued to make some changes in the legacy repository.   These changes should be captured and migrated to the central repository as part of finalizing the move.
Scope of Work

Capture changes to the Service Bus client library since the initial code drop was taken for migration and apply those changes to the client library source in the central repository.  This includes changes to the service and associated tests.

Perform any needed restructuring or enhancements to the test code, to conform to the new patterns introduced in the central repository post-migration.

Ensure that Live tests continue to pass consistently across all target platforms, both using local runs and the nightly builds from the Internal pipeline.

Out of Scope

Maintaining history of the recent commits; the changes will be applied to the central repository as a new change set, without an attempt to retain the original context.

Enhancements, new features, fixes for currently existing issues, or formatting updates to the Service Bus client library; a key goal of the migration is to introduce as few changes as possible.

Success Criteria
The changes made to the Service Bus client library since the initial migration to the central SDK repository have been migrated.   The service continues to build successfully; test runs for Live tests behave consistently and continue to pass.
Details

Changes should be identified in the  'dev` branch of the legacy Service Bus repository

The commit used for the initial migration was b70ddf652c4c520fc127407be209b0811bcc50ce by Sean Feldman, on February 15, 2019.

Changes should not include rolling back dependency versions nor introducing loose supporting assets from the central repository that were removed.

@jsquire please consider #5921 for this issue

@jsquire please consider #5921 for this issue

Hi @SeanFeldman.   A bit of context around the state of things:
The original migration attempted to preserve history as a best effort, bringing the unrelated histories forward as part of the migration using the technique that you referenced in #5921.   Unfortunately, trying to manage a 300+ commit change set over a period of time is a challenge.  Due to churn in the repository, structural changes, and other parallel work streams, there were several rebases needed to resolve conflicts.  Of those, there were a couple which were difficult, one I believe to have caused separation of the file history, though the history of commits continues to exist as a parent chain to the migration commit.
We discussed post-migration, and it was decided that there was not enough value in the history that the efforts needed to preserve it were justified for future migrations.  Given our team's mission to create a unified and cohesive set of SDKs across Azure services, it is expected that many of the existing client libraries will undergo quite a bit of change in the near future, further limiting the long-term value of preserving history for the initial migration.
The current plan, as I understand it, is that the original repository will exist as an archive and represent the history pre-migration, and the point of migration into the central repository will constitute a new line of development.
With respect to cherry-picking this particular set of changes, my goal is to address the drift that has occurred between the repositories, as there have been changes in both, with the changes in the original repository being more tightly scoped and less extensive.  This isn't a case of replaying the changes on top of the current state,  I manually brought each over and made any needed adjustments to preserve that change in context of the current state of the new repository.
Not the answer that you were looking for, I know, but hopefully it provides a bit of insight.

It would be easier to merge the original repo into SDKs repo as a single "cut over" commit, but when there are multiple steps, destination is changing while the source is undergoing modification, this will be almost impossible. Thank you for the context.

Agreed.  One of the challenges of migrating to a monorepo using a shared engineering system the potential for breaking the build and cascading failures to unrelated areas.  Ours is one of the moving parts under active development and doesn't currently have a means of ignoring a particular area or path.  Whatever is merged in must be compatible.  While we had the commit history as a parent chain when we started, we had to make the changes to adapt to the engineering system and repository structure, and ensure that the test suite was stable enough before we could integrate it.
In hindsight, I'd say that trying to maintain a linear history was a mistake and agree that it would have been a better approach - and easier - to have a merge commit as a starting point.  We also didn't anticipate that there would be contention for the destination root directory from the management library that was being restructured in parallel.  There were most certainly some missteps and lessons learned.


Add a class to paragraphs with only images

I'm looking for a way to style the first image in a document. I think it would be usefill that Typemill will detect paragraphs that only contain an image and adds a class like "figure" to it.  So I'm more flexible to style a header image and its container. Because every Image is inside a paragraph the CSS selector img:first-child {} does not help in the current implementation.

good idea, that might also help with the styling of the caption. I will have a look into it.

paragraphs with images get the class "p-image" as of version 1.3.6

I dropped this solution because it did not resolve some design issues with captions.
Images in a separate line are now rendered with html5-tag "figure" and "figcaption", so you can try to use the first-child-selector with figure.
There is also a hero-image now that you can use for ... hero images on a page.


example code not working

customer := AuthorizeCIM.Profile{
		MerchantCustomerID: "86437",
		Email:              player.Email,
		PaymentProfiles: &AuthorizeCIM.PaymentProfiles{
			CustomerType: "individual",
		},
	}

	response, err := customer.Create()

	if response.Ok() {
	  fmt.Println("New Customer Profile Created #",response.CustomerProfileID)
	  fmt.Println("New Customer Payment Profile Created #",response.CustomerPaymentProfileID)
	}

customer.Create undefined (type AuthorizeCIM.Profile has no field or method Create)

Looks like its now CreateProfile() not Create(). Please update your README!

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @dwrodri, @TimDaub, @baxiry, @ctof81, @caosbad, @TwiN, @GideonWolfe, @c2s, @hubdr, @Waxxx333, @bisby, @scalalang2, @etimes2008, @gplatas, @cdyfng, @ManuelAF, @flexlee, @martinpavan, @pylrichard, @palacestreet

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @Hammster, @hhydrgn, @GeorgPessler, @crabman96, @devBayo, @kevinschoon, @jianghansir, @sysbot, @MaizerGomes, @jyap808, @mattiasghodsian, @pratham-bhatnagar, @jkatzer, @mllnd, @ron-roc, @dgnsrekt, @fairhopeweb, @jesseventura, @b-o-b-b-y, @jorgerance

Is that bot seriously using issue tickets to promote a scam token?

Is that bot seriously using issue tickets to promote a scam token?

reported him and blocked him, i recommend doing the same

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
dsldsl, @Rampelflik, @aurelio1k, @LooMaclin, @somethingnew2-0, @teukumuhazir, @shunkakinoki, @905299789, @Zaphod101010, @nashetali837, @subuone, @BravoIndia, @bgmrk, @avelrl, @7afzal, @ranyabu, @mit-d, @tareq1001, @sqfasd, @mgthomas99


Block level elements requiring two \n ?

Hi - Apologies if this is obvious (and/or a weird implementation of MD) but I'm getting my MD from an API which I don't control, and  the block level elements (Heading, HR, etc) are only separated by one \n, whereas it appears that this implementation of it requires two \n.  (I believe they're using CommonMark)
For example, I get data like:
# Heading1 #\n## Heading2 ##\n### Heading3 ###\n
But to display properly using RNSM it appears to only work if it's
# Heading1 #\n\n## Heading2 ##\n\n### Heading3 ###\n\n
I really like this library much better than the others, but this is causing some problems.  I'll start looking at the code to try to figure it out, but not sure if anyone else has encountered this and if it can be solved easily.
Thanks!

+1

Hi @robinschaaf! I'm so sorry for this late reply, I've been so busy this last couple of weeks 😣…
You're completely right: even if I'm used to this \n\n syntax, RNSM should also handle the \n case. If I'm not mistaken, the problem probably comes from either the text rule in rules.js (I'm not completyly satisfied with it anymore, I will probably rewrite the whole thing anytime soon 🤔…) or the MD parser itself.
If you can figure it out and send a PR it would be so much appreciated 🎉!


fix(wiz-toggle): fix wizard toggle icon click-ability

This PR updates the header to more seamlessly collapse/consolidate the user menu at smaller viewports. Previously we would collapse logout into the help menu (keeping the help icon) and later convert that icon to kebab. After further reviewing this interaction, we realized it seems strange and a better experience is to convert the icon to a kebab at the same time we move/consolidate the two menus.
Also fixes a bug where selecting the collapse "toggle" icon for wizard  wasn't actually collapsing the menu. Now it does.
One question that came up along the way was "how are we achieving this collapse functionality for the PF3 Wiz steps?". I don't see this capability in the PF3 react implementation;
http://patternfly-react.surge.sh/patternfly-3/index.html?selectedKind=patternfly-react%2FCommunication%2FWizard%2FComponents&selectedStory=Wizard&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybooks%2Fstorybook-addon-knobs
But it does seem to be a thing in core;
https://rawgit.com/patternfly/patternfly/master-dist/dist/tests/wizard.html
Should help close https://github.com/syndesisio/syndesis-react/issues/425
allow pointer events to pass through for wiz toggle icon
introduce tabletView mode where we can update aspects of the UI based on viewport size
update header icons depending on viewport size

looks like you have a build error
ERR! => Failed to build the preview
ERR! [at-loader] ./stories/Shared/HelpDropdown.stories.tsx:13:10
ERR!     TS2322: Type '{ dropdownDirection: any; dropdownPosition: any; isMobileView: any; launchConnectorsGuide: any; launchContactUs: any; launchSampleIntegrationTutorials: any; launchSupportPage: any; launchUserGuide: any; launchAboutModal: any; isOpen: true; }' is not assignable to type 'IntrinsicAttributes & IntrinsicClassAttributes<HelpDropdown> & Readonly<IHelpDropdownProps> & Readonly<{ children?: ReactNode; }>'.
ERR!   Property 'isMobileView' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<HelpDropdown> & Readonly<IHelpDropdownProps> & Readonly<{ children?: ReactNode; }>'.
(node:2332) UnhandledPromiseRejectionWarning: [object Object]
(node:2332) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2332) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
error Command failed with exit code 1.

PR Storybook available here

LGTM!

PR Storybook available here


File::Which module

This is my output when I run proovread:
Can't locate File/Which.pm in @INC (you may need to install the File::Which module) (@INC contains: /bin/proovread/bin/../lib/ /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at ./proovread line 20.

You need the File::Which perl module, you can either install it via CPAN command line or download the source code. Assuming you need to install locally:
wget http://search.cpan.org/CPAN/authors/id/P/PE/PEREINAR/File-Which-0.05.tar.gz
tar -xzf File-Which-0.05.tar.gz
cd File-Which-0.05
perl Makefile.PL INSTALLSITELIB=/path/to/proovread/lib   # << set this path !!!!
make && make install

Ignore ERROR: Can't create '/usr/local/bin', you don't need that.. You should now have /path/to/proovread/lib/File/Which.pm and proovread should find it directly.

Thanks thackl, I ran the sample test and all looks ok!!!! Thank you so much!!!

Hi @thackl ,
I followed your instructions to install FIle:Which.
However, I still cannot filnd which.pm in  /path/to/proovread/lib/File/.
Can I copy which.pm in File-Which-0.05 to  /path/to/proovread/lib/File/?
Thank you!
Weilong

I fixed this problem. Thank you!


GATT

Status
Ticket/Issue

Ready/Hold
Ticket

Main changes

Screenshots (feature, test output, profiling, dev tools etc)
[insert screenshots here]
Other notes (e.g. implementation quirks, edge cases, questions / issues)

Manual testing tips

Tag anyone who definitely needs to review or help

Repalced by https://github.com/pi-top/Further-Link/pull/156


New Analyse Task: Checking for unused parameter

Is your feature request related to a problem? Please describe.
A parameter that is not used can have several reason

you missed to use it?
it's not important anymore?
you intended to used it but forgot it?

Done.


Add ppp

Codecov Report
Patch coverage has no change and project coverage change: +0.30 :tada:

Comparison is base (064c71c) 26.99% compared to head (3614d3a) 27.30%.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #142      +/-   ##
============================================
+ Coverage     26.99%   27.30%   +0.30%
- Complexity      557      565       +8
============================================
  Files           220      220
  Lines          5212     5212
  Branches        624      624
============================================
+ Hits           1407     1423      +16
+ Misses         3717     3701      -16
  Partials         88       88

see 3 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


synonyms_chinese array has string quotes outside of array

I used this image, (Yes i know this is not how its not supposed to be used, but i tested it and i got json errors)

And the json response is: Json Response
As you can see here that synonyms_chinese is "synonyms_chinese":"[]", not
"synonyms_chinese":[

],

Since i am using Newtonsoft.Json for C# i am deserializing the object, but beacuse of this json value error is, i am getting this error, which is not fixable unless the json api is fixed, or i just ignore using that value at all. or use dynamic values.
Error:
Error converting value "[]" to type 'System.Collections.Generic.List`1[System.String]'. Path 'docs[4].synonyms_chinese', line 1, position 3182.
EDIT:
Got same issue with this picture: (Spoilers sorry)

Gist and location
You can find my project at: ThomasAunvik/AnimeListBot within class TraceMoe.cs

Thanks for reporting this issue.
Looking into the database, I've found a total of 163 records with issues.
SELECT * FROM anilist_chinese WHERE JSON_QUERY(json, '$.synonyms_chinese') IS NULL

The root cause lies in an admin page (which is not included in this repo) which manage anime titles.
I'll correct these db records soon.


fix miscalculation of rlen

So I ran into this (the rline being wrong with meta) with mcshredder this week. For meta the rline was supposed to be where the flags start, but I'm not sure that actually made sense anymore.
So I need to make a decision on how it should be properly calculated, I think.

So I need to make a decision on how it should be properly calculated, I think.

Agreed, why can't just return the entire result line, which is how I understand
"resp:line(): for use with meta, returns the full response header line." from the wiki.

It probably just needs to be two functions; one for getting the meta flags line and one for "full response line". I'm not sure I have the brainpower to make this decision today though.
The problem is mcmc is a core client library, so "where do the meta flags start?" is a legitimate question for a client builder.

Sounds good. We don't use line() in our Lua, so take you time.

cripes. took more than a year to circle back to this. what a nightmare.
I've got this fixed a different way the branch that I'm working on, so I'll close this out. I refactored to remove l entirely and rely on cur. also fixes some bugs with leading spaces and lines with missing \r.


Highlight the outdated dependencies versions

It would be great that VSCode highlight the outdated dependencies versions in the package.json.
The latest version appears in the hover tooltip:

This extension already does this https://marketplace.visualstudio.com/items?itemName=pflannery.vscode-versionlens


Question: support for append?

If I wanted to use the equivalent of the Python append argument, how would that look? E.g., I'd want to be able to do:
./executable <command> --metric one --metric two ... --metric N

The alternative is provide one string separated by commas, which isn't as nice an interface. it's also not appropriate to use a list of args because I'm already using it for something else. Thank you!

There's currently no support for something like that. I tried to keep cli-ng as simple as possible. I can sort of see how I might implement a slice parameter which gets appended to, but I'd really need to think that one over.

I would superly appreciate it! And let me know if I can help. For the time being I will use a comma separated list. Also, because of @alecbcs I use this on almost all my projects so thank you for the library!


Custom SSH

Right now we have a GUI interface where we need to enter address and it connects but can we have a command line option?
I have a machin which uses ngrok and I am not able to do ssh using GUI.
I am able to do SSH via command line but I cannot access the directories then.
The command to ssh into ngrok machine is like:
ssh -p  @tcp://0.tcp.in.ngrok.io
I tried adding address as: tcp://0.tcp.in.ngrok.io
and port number in the respective fields
But the app just throws out an unknown error.

Thanks for reporting. I will look into this.

Try these settings in the GUI:
Address: 0.tcp.in.ngrok.io
Port: <ASSIGNED_PORT / 22>
Username:


Feat: Adding Animation

Describe the feature

I would like to add animation on the about pages image to make it look more appealing
Your landing page already looks fantastic, but incorporating animations could make it even more captivating. With my experience in this area, I'm eager to contribute to this enhancement.
If you could assign me this task under GSSOC24, I would be thrilled to work on it.

Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@harshmishra19 you are assigned.


Oops; flutter has exited unexpectedly

Steps to Reproduce

Executing any flutter command in the flutter_console.bat

Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: 66ed647bd16b3197)

Logs
Flutter crash report; please file at https://github.com/flutter/flutter/issues.

## command

flutter --no-color packages get

## exception

FormatException: FormatException: Not a valid package name (at character 1)
dart# Generated by pub on 2019-01-12 12
^

#0      parse (package:package_config/packages_file.dart:57:7)
#1      _parse (package:flutter_tools/src/dart/package_map.dart:14:10)
#2      PackageMap.load (package:flutter_tools/src/dart/package_map.dart:35:14)
#3      PackageMap.map (package:flutter_tools/src/dart/package_map.dart:39:5)
#4      FlutterCommandRunner._checkFlutterCopy (package:flutter_tools/src/runner/flutter_command_runner.dart:543:41)
#5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:374:9)
<asynchronous suspension>
#6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#7      _rootRun (dart:async/zone.dart:1124:13)
#8      _CustomZone.run (dart:async/zone.dart:1021:19)
#9      _runZoned (dart:async/zone.dart:1516:10)
#10     runZoned (dart:async/zone.dart:1463:12)
#11     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:361:19)
<asynchronous suspension>
#13     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:111:29)
#14     new Future.sync (dart:async/future.dart:224:31)
#15     CommandRunner.run (package:args/command_runner.dart:111:11)
#16     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:241:18)
#17     run.<anonymous closure> (package:flutter_tools/runner.dart:60:20)
<asynchronous suspension>
#18     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#19     _rootRun (dart:async/zone.dart:1124:13)
#20     _CustomZone.run (dart:async/zone.dart:1021:19)
#21     _runZoned (dart:async/zone.dart:1516:10)
#22     runZoned (dart:async/zone.dart:1463:12)
#23     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#24     runInContext (package:flutter_tools/src/context_runner.dart:43:24)
<asynchronous suspension>
#25     run (package:flutter_tools/runner.dart:51:10)
#26     main (package:flutter_tools/executable.dart:51:9)
<asynchronous suspension>
#27     main (file:///E:/b/build/slave/Windows_Flutter_Packaging/build/archive/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#28     _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:287:32)
#29     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

flutter doctor
[✓] Flutter (Channel stable, v1.0.0, on Microsoft Windows [Version 10.0.17134.472], locale en-US)
    • Flutter version 1.0.0 at C:\Users\fvale\Repositorios\flutter
    • Framework revision 5391447fae (6 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at C:\Users\fvale\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] Android Studio (version 3.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 31.3.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

• No issues found!

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Build failed with TypeScript 3.8.3

Bug Report
:warning: TSLint is deprecated.
Please use ESLint with typescript-eslint instead.
Bug reports which deal with security vulnerabilities, TypeScript compatibility, or ESLint migration workflows may be considered; other requests are likely to be declined. See the roadmap for more details.

TSLint version: 6.1.1
TypeScript version: 3.8.3
Running TSLint via: n/a

Actual behavior
><EMAIL_ADDRESS>compile:scripts /Users/maxim/IdeaProjects/tslint
> tsc -p scripts

scripts/generate-changelog.ts:43:21 - error TS2351: This expression is not constructable.
  Type 'typeof import("/Users/maxim/IdeaProjects/tslint/node_modules/@octokit/rest/index")' has no construct signatures.

43 const octokit = new Octokit({
                       ~~~~~~~

scripts/generate-changelog.ts:60:22 - error TS7031: Binding element 'tag_name' implicitly has an 'any' type.

60     .then(({ data: { tag_name } }) => {
                        ~~~~~~~~

scripts/generate-changelog.ts:69:22 - error TS7031: Binding element 'commits' implicitly has an 'any' type.

69     .then(({ data: { commits } }) => {
                        ~~~~~~~

scripts/generate-changelog.ts:96:42 - error TS7031: Binding element 'body' implicitly has an 'any' type.

96                         .then(({ data: { body } }) => {
                                            ~~~~

scripts/generate-changelog.ts:148:12 - error TS7006: Parameter 'error' implicitly has an 'any' type.

148     .catch(error => {
               ~~~~~

Found 5 errors.

Expected behavior
Built successfully
NodeJS: v12.14.0
@octokit/types: 2.11.1
@octokit/rest: 16.43.1

Sorry, I didn't notice yarn.lock, was installing deps using npm. I assume this is not an issue with older Octokit.

🤖 Beep boop! 👉  TSLint is deprecated 👈  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Integrate Teleportation in Gateway 2.5

Teleportation contract:
https://github.com/bobanetwork/boba/blob/develop/packages/boba/contracts/contracts/Teleportation.sol
Current deployments on testnets:
https://github.com/bobanetwork/boba/tree/develop/packages/boba/teleportation
Deployed contracts have not yet any routes configured, what routes do we want to provide liquidity for @InoMurko (on testnet)?
Not deployed on Mainnet yet.

User flow:

User calls this functions via the Gateway.

 /**
     * @dev Accepts deposits that will be disbursed to the sender's address on target L2.
     * The method reverts if the amount is less than the current
     * minDepositAmount, the amount is greater than the current
     * maxDepositAmount.
     *
     * @param _token ERC20 address of the token to deposit.
     * @param _amount The amount of token or native asset to deposit (must be the same as msg.value if native asset)
     * @param _toChainId The destination chain ID.
     */
 function teleportAsset(address _token, uint256 _amount, uint32 _toChainId)

Note: Only whitelisted routes are allowed, otherwise the transaction will revert. Meaning: if the destination chain & token are not both supported from the source chain, it cannot be bridged. Which assets are whitelisted has to be maintained in the frontend for now or by reading events from the contract:
event TokenSupported(
        address indexed token,
        uint32 indexed toChainId,
        bool supported // if true, then this route is supported (from contract on source chain to destination (to) chain)
    );

Within a short period of time the Teleportation service on AWS should disburse the asset on the destination chain via the deployed Teleportation contract by calling: function disburseAsset(Disbursement[] calldata _disbursements).
After this event on the destination chain has been fired, you can notify the user on the gateway, that the funds have arrived:
  event DisbursementSuccess(
        uint256 indexed depositId,
        address indexed to,
        address indexed token,
        uint256 amount,
        uint32 sourceChainId
    );

Error handling for native assets, in that case we could/should even do a retry mechanism in the gateway.
  event DisbursementSuccess(
        uint256 indexed depositId,
        address indexed to,
        address indexed token,
        uint256 amount,
        uint32 sourceChainId
    );

    /** @dev only for native assets */
    event DisbursementFailed(
        uint256 indexed depositId,
        address indexed to,
        uint256 amount,
        uint32 sourceChainId
    );

    /** @dev Only for native assets */
    event DisbursementRetrySuccess(
        uint256 indexed depositId,
        address indexed to,
        uint256 amount,
        uint32 sourceChainId
    );

@wsdt ,
Need help with the below details

please help with details like how are we going to use Teleportation on Gateway.
Need Contract details and its deployed address for the Mainnet & Testnet.
Requirement documentation would be more helpful if there is any.

done! @sk-enya

Deployed contracts have not yet any routes configured, what routes do we want to provide liquidity for @InoMurko (on testnet)?

Lets start with:
Ethereum <-> Ethereum BOBA asset BOBA (both directions)
Ethereum <-> Ethereum BOBA asset ETH (both directions)
Ethereum <-> BNB asset BOBA (both directions)
BNB <-> Boba BNB asset BOBA (both directions)
Ethereum Boba<->BNB Boba asset BOBA (both directions)
Ethereum Boba<->BNB Boba asset BOBA (both directions)
Ethereum Boba<->BNB asset BOBA (both directions)
Ethereum Boba<->Ethereum asset BOBA (both directions)
I don't think there's WETH on BNB Boba. So moving ETH there wont work. Pls verify there isn't a WETH.
Make sure you're aware that for example $boba on BOBA ETH is erc20, but $boba on BOBA BNB is native.

Is there a Watcher API that can be used to monitor transactions between L2s? We'll need this for this history page. Happy to work on it if necessary

Which assets are whitelisted has to be maintained in the frontend for now or by reading events from the contract

that seems like it will need to be indexed in a separate service or the contract would need to be modified to keep this stored?

@InoMurko yes events are emitted yes and can be easily read from the frontend.

events means frontend would need to "track" all events. frontends needs a middleware services that has the last information of all chains.

@InoMurko yes events are emitted yes and can be easily read from the frontend.
Why would the frontend need to track all events?
You bridge your asset, the teleporter disburses the asset in a few seconds and the Gateway knows exactly on which chain & event & address to listen to.

[X] Ethereum <-> Ethereum BOBA asset BOBA (both directions)
[X] Ethereum <-> Ethereum BOBA asset ETH (both directions)
[ ] Ethereum <-> BNB asset BOBA (both directions)
[ ] BNB <-> Boba BNB asset BOBA (both directions)
[X] Ethereum Boba<->BNB Boba asset BOBA (both directions)
[ ] Ethereum Boba<->BNB asset BOBA (both directions)
I don't think there's WETH on BNB Boba (not on testnet, but looks like BOBA Bnb mainnet has it on 0x38Ca7a190f57D38F4DC44413508e1078cD9E0045).
Make sure you're aware that for example $boba on BOBA ETH is erc20, but $boba on BOBA BNB is native.
--> yes even added some integration tests for that.

Teleporter not deployed on BNB L1 yet, will do.

I meant that if the frontend needs to know which routes are available, they need to know what the contract supports on a specific network -
    /// @dev Assets and networks to be supported. ZeroAddress for native asset
    /// {assetAddress} => {targetChainId} => {tokenConfig}
    mapping(address => mapping(uint32 => SupportedToken)) public supportedTokens;

which would be this mapping that needs to be read.
perhaps @wsdt you could go through the new bridge design and create wireframes with API or contract calls that need to be created - sort of a technical integration guidance.

I don't think there's WETH on BNB Boba (not on testnet, but looks like BOBA Bnb mainnet has it on 0x38Ca7a190f57D38F4DC44413508e1078cD9E0045).

Ask @Boyuan-Chen to deploy one (also update the docs!).

@InoMurko great idea, sure thing will do!

Some more documentation for integrating Teleportation:
Mockup & SequenceDiagram:
https://github.com/bobanetwork/boba/issues/1044

Estimated time => placeholder
Gas fee => 0.4440 BOBA
You will receive => 0.000 BOBA

Gas fee can be culated as

const tx = await TelePortContract.populateTransaction.teleportAsset(
 token, amount, chainId)

const gasFee = await this.provider.estimateGas({...tx, from: this.gasEstimateAccount})

@sk-enya FYI - Would replace Fast bridging logic with Teleportation as discussed based on the develop branch.
Saw you just merged the new bridge logic/design in there.

@wsdt this means we have to complete deprecate fast bridging (LP pools)
cc @souradeep-das

guys just to make sure the effects of deprecating fast exits are discussed-
a) the LPs that support fast exits right now might have user funds so probably if we do remove fast exits - we should still allow users to withdraw funds through the interface
b) maybe we should give them an advanced notice, before stopping on fast exits - and hence stopping on the rewards for providing liquidity.

guys just to make sure the effects of deprecating fast exits are discussed- a) the LPs that support fast exits right now might have user funds so probably if we do remove fast exits - we should still allow users to withdraw funds through the interface b) maybe we should give them an advanced notice, before stopping on fast exits - and hence stopping on the rewards for providing liquidity.

considering this & the transition period testnet->mainnet as well, it could be a good idea to just have a 3rd tab for Teleportation.
imho

@InoMurko @wsdt what is the status of teleportation? We need some time to design front end and test once it's complete from a technical perspective. Now that Gateway 2.5 is live, we can start to consider this if it's ready to go.

It's ready! Just trying to get it merged!


Unfocus Control by clicking somwehere else

A left MouseButton press should unfocus a Control, when pressed outside of it.
Adjust Unit-Tests to new behavior.
resolve #78251
Please label as 4.2, since this change in behavior needs discussion and testing.

Closing this PR, because this change would make the functionality too restrictive. See also https://github.com/godotengine/godot/issues/78251#issuecomment-1592851996


Model updates are not being tracked

I followed the basic guide to get started, but I noticed the update actions are not being recorded. These are my models:
class Activist
  include Mongoid::Document
  include Mongoid::Timestamps
  include Mongoid::History::Trackable

  track_history on: :fields,
      modifier_field: :modifier,
      version_field: :version,
      track_create: true,
      track_update: true,
      track_destroy: true
end

class Citizen
  include Mongoid::Document
  include Mongoid::Timestamps
  include Mongoid::History::Trackable

  track_history on: :fields,
      scope: :activist,
      version_field: :version,
      track_create: true,
      track_update: true,
      track_destroy: true
end

Now, in the rails console:
activist = Activist.create ( attributes )

citizen = activist.citizens.create ( attributes )

citizen.history_tracks.count
# => 1

citizen.update_attributes(name: "something")
#=> true

citizen.history_tracks.count
# => 1     should be 2

citizen.history_tracks.last.action
#=> "create"
# Shouldn't it be "update" ?

citizen.destroy
# => true

citizen.history_tracks.count
# => 2

citizen.history_tracks.last.action
# => "destroy"

Am I missing something? I also created the initializer as provided by the readme.

From the first view this should work. Activist is not persisted, I wonder if it has something to do with it? Use ! functions to see if there's another in the middle. And change to Activist.create!(attributes) and update_attributes!. Finally, what's the relation between citizen and activist?
If you can't figure it out, turn it into a spec in this repo.

I ran it in the terminal and yes, the error was Activist model not being persisted, but still, when I try with this spec this is not working:
describe '#history' do
  let(:user) { create(:user) }
  let(:activist) { create(:activist, modifier: user }
  let(:citizen) { create(:citizen, activist: activist, modifier: user) }

  it 'tracks citizen updates' do
    citizen.update_attributes(first_name: "John")
    expect(citizen.history_tracks.last.action).to eq("update")
  end
end

The error is I'm still receiving "create" in this spec.

First, again, use ! versions of these methods, you might be not seeing an exception.
.last in Mongoid is not a sorted query, so I wouldn't be so sure that .last is the last thing, see if they are in there out of order and whether citizen.history_tracks.asc(:_id).last is the right thing?

My problem was somewhere else, I guess.
I looked into the specs and found the  tracked_fields method. I ran it into my Activist model, only to find out it was returning an empty array, and so was doing Citizen.
The solution was to move the track_on method below the declaration of the fields. As of why it worked on the rails console and not in the specs, beats me; but changing that made my specs go green again.
Thank you for your support!

Interesting. We definitely should be failing when you try to track_fields on a field that doesn't exist! Or it should work.
Would you mind trying to write a spec in this repo for that scenario and making a PR with it? Maybe it's a real bug.

Sure, I'll give it a look this afternoon.

Looks to be a dup of #174 then?

Oh thanks @mpetazzoni, @hslzr do you define fields after track_history?

Yes @mpetazzoni, looks like my question is a duplicate of #174. And that's right @dblock, I was indeed defining the fields after the track history :sweat_smile:

Lets close this, maybe @hslzr can feel motivated to make a fix for #174?


[stable/telegraf] telegraf-ds & telegraf-s charts missing

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Which chart:
telegraf-ds & telegraf-s
What happened:
telegraf chart says it was deprecated (by #823) , suggests using telegraf-ds and telegraf-s, these two charts were added in March (#742, #822) but never get merged.

@southwolf I'm working with @gunnaraasen to find a better place for these. I know there are working versions here: https://github.com/influxdata/tick-charts


JsonMapper.isJsonStringRepresentsCollection may incorrectly return true for Protobuf-encoded messages

Using
Spring Boot 2.7.11
Spring Cloud Dependencies 2021.0.8
Describe the bug
Note: We ran into this issue with Protobuf encoded messages, but it should be reproducible with any binary serialization.
A Protobuf message with length encoded fields like
syntax = "proto3";

message StringValue {
  string value = 1;
}

is encoded into a tag, followed by the length of the encoded value (in bytes), followed by the payload. The tag is fieldNumber * 8 + 2 (see Protobuf wire types) = 10 in this example.
isJsonStringRepresentsCollection() strips the tag from the input if it has the same numeric representation as some whitespace character (newline in this case).
If the payload happens to be 34, 91, or 123 bytes long and end with 34 resp. 93 resp. 125 (decimal representation), isJsonStringRepresentsCollection() identifies the remaining input as JSON and fluxifyInputIfNecessary() calls fromJson(), which inevitably fails at some point with something like
Caused by: com.fasterxml.jackson.core.JsonParseException: Illegal character ((CTRL-CHAR, code 26)): only regular white space (\r, \n, \t) is allowed between tokens
 at [Source: (byte[])"
[
\u001A\u0008�\u000F\u0010
\u0018\u0013 \u0007(\u001C0\u000E8���\u0001J\u0005
\u0003UTC\u0012\u0003\u0008�s\u0012\u0004\u0008�\u0002\u0012\u0004\u0008�\u0002\u0012\u0004\u0008��\u0001\u0012\u0004\u0008��\u0001\u0012\u0003\u0008�s\u0012\u0004\u0008��\u0001\u0012\u0004\u0008��\u0001\u0012\u0004\u0008��\u0001\u0012\u0004\u0008��\u0001\u0012\u0003\u0008�]"; line: 3, column: 2]
    at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:2391)
    at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:735)
    at com.fasterxml.jackson.core.base.ParserMinimalBase._throwInvalidSpace(ParserMinimalBase.java:713)
    at com.fasterxml.jackson.core.json.UTF8StreamJsonParser._skipWSOrEnd(UTF8StreamJsonParser.java:3077)
    at com.fasterxml.jackson.core.json.UTF8StreamJsonParser.nextToken(UTF8StreamJsonParser.java:756)
    at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer._deserializeFromArray(CollectionDeserializer.java:346)
    at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:244)
    at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:28)
    at com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:323)
    at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4674)
    at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3723)
    at org.springframework.cloud.function.json.JacksonMapper.doFromJson(JacksonMapper.java:60)
    at org.springframework.cloud.function.json.JsonMapper.fromJson(JsonMapper.java:94)
    at org.springframework.cloud.function.context.catalog.SimpleFunctionRegistry$FunctionInvocationWrapper.fluxifyInputIfNecessary(SimpleFunctionRegistry.java:833)
    at org.springframework.cloud.function.context.catalog.SimpleFunctionRegistry$FunctionInvocationWrapper.doApply(SimpleFunctionRegistry.java:733)
    at org.springframework.cloud.function.context.catalog.SimpleFunctionRegistry$FunctionInvocationWrapper.apply(SimpleFunctionRegistry.java:590)
    at org.springframework.cloud.stream.function.PartitionAwareFunctionWrapper.apply(PartitionAwareFunctionWrapper.java:84)
    at org.springframework.cloud.stream.function.FunctionConfiguration$FunctionWrapper.apply(FunctionConfiguration.java:791)
    at org.springframework.cloud.stream.function.FunctionConfiguration$FunctionToDestinationBinder$1.handleMessageInternal(FunctionConfiguration.java:623)
    at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:55)
    ... 26 more

The real culprit here seems to be fluxifyInputIfNecessary(), which ignores the content type header of a message entirely (almost, text/plain is handled). IMO fromJson() should only be called if the content type is undefined or application/json.

We use the ProtobufMessageConverter, which sets the content type to application/x-protobuf
However, as mentioned above, this is not limited to protobuf-encoded messages. From code inspection it's pretty clear that any serialization that is not JSON can cause that problem.

This is becoming a real problem for us. I have added a test that reproduces the issue.

Sorry for neglecting it. Will look at it shortly

While I added mapper.configure(DeserializationFeature.FAIL_ON_TRAILING_TOKENS, true); it broke https://github.com/spring-cloud/spring-cloud-function/issues/1148.
So I am removing it, and instead you can manually configure it as such
spring:
  jackson:
    deserialization:
      fail-on-trailing-tokens: true

I need to ask why we have to configure a JSON mapper if we don't use JSON for our messages at all. The content type says the message is not JSON, so IMHO isJsonString() shouldn't be called in the first place.
With this "auto-sensing" of the content type we can probably still construct a failing scenario, i.e. a serialization that sometimes produces a valid JSON string, but isn't meant to be interpreted as JSON.
What am I missing?

No, you are not missing anything, but got me thinking if I can also check for content-type and if it is not application/json why bother . . . that I agree, so let me try something. I'll re-open the issue

Thanks for reopening this - we already found that the whole thing is skipped if the content type is plain text (https://github.com/spring-cloud/spring-cloud-function/blob/main/spring-cloud-function-context/src/main/java/org/springframework/cloud/function/context/catalog/SimpleFunctionRegistry.java#L857). Maybe the simplest fix would be to revert this logic and call the JsonMapper only if the content type is undefined oder "application/json".

Anyway, I have reverted the commit that would force you to provide the mentioned settings as I agree you don't need to do that when no using JSON.


new user signup should not fail on client and succeed on server

We have cases where on server user is saved in database but client thinks he is logged out

[x] try to figure out why? maybe some promise fails but the promise to /user/add doesnt
[x] if user has mnemonic and isCitizen we should ping server to check if he is registered and if so then
simply switch GD_isLoggedIn to true
[ ] in auth on server if user is whitelisted and privedb doesnt contain details server should request them from client

i found out the issue is gun.
when saving profile there's gun "no ack" for some users. need to invetigate further.

discussed with @sirpy : no need to do the last thing in task


allow being called for multiple packages

See https://github.com/square/goprotowrap

Unlike other language plugins, the Go protobuf plugin expects to be called separately for each package, and given all files in that package.

In order to be consistent with other language plugins, the Go protobuf plugin should be able to handle being called for multiple packages at the same time.

This is a duplicate of #39. @neild and I have discussed wanting to fix this (as you noticed) to be consistent with other languages. However, it is a low priority item for us at this time.


BasicSuite/TestMemif2Vxlan2Memif is not stable

Build
https://github.com/networkservicemesh/integration-k8s-kind/runs/2216228221
Logs
Containers logs.zip

Fixed by https://github.com/networkservicemesh/sdk-k8s/pull/102


Delete_resident_key_by_user_id does not need to iterate over the filesystem

If I understand correctly the RK path is always rp_id_hash/user_id_hash, so we can  instead just try to open the file and delete it if it's there.
https://github.com/Nitrokey/fido-authenticator/blob/9213a57d2e60a228ef6d6156e0e434453b688806/src/ctap2.rs#L1684

Nevermind, the userd_id is not the same as the credential_id.


5.0 release

Things that need to happen before a 5.0 release

[ ] Upgrade guide from 4.0 to 5.0, since this release has nontrivial breaking changes
[ ] Update readme to have AVX performance tips, correct example, etc
[ ] Feature flag to disable AVX? This would improve compile times for users who know their target CPU doesn't support avx
[ ] Determine MSRV
[ ] Document MSRV update policy (Basically, copy tokio 1.0's policy of requring that a version of rustc be out for 6 months before depending on it)
[ ] Document policy on future major releases (No breaking changes for 3 years, EXCEPT for if we need to upgrade our version of num-traits/num-complex)

This release will have a lot of breaking changes, and I'd like to avoid making any for a long time afterwards, so if we have any other breaking changes, we need to get them in soon.

I have thought a little and have two things that maybe should be on the list:

CI for more platforms, especially something without avx like arm (I can set this up)
Prepare so other instruction sets can be added without breaking changes. I'm thinking sse and neon. Neon seems to lack a lot of intrinsics so might be some way off, but sse could be started now. I haven't looked carefully at this, could be a non-issue.

I have thought a little and have two things that maybe should be on the list:

CI for more platforms, especially something without avx like arm (I can set this up)
Prepare so other instruction sets can be added without breaking changes. I'm thinking sse and neon. Neon seems to lack a lot of intrinsics so might be some way off, but sse could be started now. I haven't looked carefully at this, could be a non-issue.

That's a good point about adding new SIMD sets. I changed FftPlanner to be a public enum, meaning adding new entries to that enum would be a breaking change. I'll have to make it private and wrap it in a struct.
Once that happens, I think we're ready to go WRT adding new instruction sets like SSE - we just need to add new entries to the FftPlanner enum, and update FftPlanner's constructor to attempt to create an instance of FftPlannerNeon or whatever, the same way it does AVX.
My plan right now is to write algorithms from the ground up for each instruction set. Eventually, I may abstract an instruction set agnostic section of the code, and I bet that for example the MixedRadix8xn etc structs can be written entirely in simd-agnostic code. But first, I'd like to get a few independently-implemented instruction sets going so I can see what sorts of patterns develop.
As for testing, I'm totally on board with getting arm-based CI. I'm also very nervous about the fact that all of the AVX unit tests simply crash if they're run on a x86_64 platform without AVX. It probably isn't a problem now, since virtually everyone running rustfft's unit tests on x86_64 will have AVX. But if we add an avx-512 module, those unit tests definitely should not crash. It would be nice if rust's test runner had a way to conditionally ignore tests.

That's a good point about adding new SIMD sets. I changed FftPlanner to be a public enum, meaning adding new entries to that enum would be a breaking change. I'll have to make it private and wrap it in a struct.
Once that happens, I think we're ready to go WRT adding new instruction sets like SSE - we just need to add new entries to the FftPlanner enum, and update FftPlanner's constructor to attempt to create an instance of FftPlannerNeon or whatever, the same way it does AVX.
My plan right now is to write algorithms from the ground up for each instruction set. Eventually, I may abstract an instruction set agnostic section of the code, and I bet that for example the MixedRadix8xn etc structs can be written entirely in simd-agnostic code. But first, I'd like to get a few independently-implemented instruction sets going so I can see what sorts of patterns develop.
As for testing, I'm totally on board with getting arm-based CI. I'm also very nervous about the fact that all of the AVX unit tests simply crash if they're run on a x86_64 platform without AVX. It probably isn't a problem now, since virtually everyone running rustfft's unit tests on x86_64 will have AVX. But if we add an avx-512 module, those unit tests definitely should not crash. It would be nice if rust's test runner had a way to conditionally ignore tests.

Which guide is the first point refering to?

Which guide is the first point refering to?

I intend to write a guide for specifically how tro u[grade from 4.0 to 5.0.

I intend to write a guide for specifically how tro u[grade from 4.0 to 5.0.

Ah I see, write a new upgrade guide. That is definitely useful. I read it as upgrading an existing guide.

Ah I see, write a new upgrade guide. That is definitely useful. I read it as upgrading an existing guide.

First draft of upgrade guide is finished: https://github.com/ejmahler/RustFFT/blob/master/UpgradeGuide4to5.md
I also made a last minute breaking change to cut down the number of methods in the Fft trait and reorganize them.
I'll do one more pass over the documentation tomorrow and publish 5.0 if everything looks good.

First draft of upgrade guide is finished: https://github.com/ejmahler/RustFFT/blob/master/UpgradeGuide4to5.md
I also made a last minute breaking change to cut down the number of methods in the Fft trait and reorganize them.
I'll do one more pass over the documentation tomorrow and publish 5.0 if everything looks good.

RustFFT 5.0 has been released.

RustFFT 5.0 has been released.

Great!! Then it's time to start updating everything else to use it :)

Great!! Then it's time to start updating everything else to use it :)


serialization: remove extra "hierarchy" from mediatypes

The fact that we are serializing is implied. This PR removes the extra
bits in the media type that only serve to confuse and waste bytes. The
new media types better reflect the reality for the usage of each type
and how they relate.
This must be followed up by a split of the serialization document, but
this change should be applied first.
This change is backwards incompatible with previous versions of the OCI
specification. Since we are before 1.0, this is acceptable.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>Related to #206.

OHMAN GPG SIGNED COMMIT

While i'm not terribly opposed, I'm not sure what harm or confusion having the name stay is?
The biggest beneficial piece of this seems to be the +gzip such that it's an optional representation of the artifact.

@vbatts I'd like to see cruft remove, if we can.
It would be great to get an LGTM here so I can carry on with the split.

On the call no one really objected to making this change on the call. Saving a few bytes isn't a huge deal in json land but I don't object.
LGTM
(rebase needed, I will LGTM again)

@philips @vbatts rebase, PTAL

LGTM

LGTM


[kjobctl] Add raycluster flag for RayJob mode.

What type of PR is this?
/kind feature

What this PR does / why we need it:
Add raycluster flag for RayJob mode on kjobctl.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/assign @trasc

overall LGTM, but I think we should a a column in the list command for this after

[kjobctl] Add list RayJob command. #2718

is merged

Good idea. Added.

/approve


Split Ratify repo into multiple repos: framework, CLI, K8s server, etc

In order to better develop multiple modes of operating Ratify, the repository could be split up to have a clear framework repository, CLI repository, and K8s server repository. This would enable further K8s-centric development as we discussed in yesterday's meeting and would make the code structure clearer to newcomers.

Would like to understand more about dependency management requirements once we have multiple repositories. E.g. Does cli only need to work with latest framework, or will be need to maintain compatibility.

Per our chat @lee0c - I don't think we would support a full split of repositories at this time.  However, more-specific ideas where we can make the experience cleaner/easier (i.e. development, testing, etc for k8s dev workflow), within the current repository would be welcomed.

Closing for now as no future plans as of this moment


chmod: cannot access /path/to/app': No such file or directory chmod: cannot access /public_html/test': No such file or directory

I cannot pass this step of the setup because of the error. Any idea why this is happening?
Thanks

The "/path/to/myapp" is just an example path from the docs. The actual path on your server will be different.
I don't know what the error about "/public_html/test" is about. Can you share your actual remotes config and how did you run git-deploy in the setup phase?

Yes, sorry, the example was wrong. Here's what I dit exactly
git init
git remote add production user@server.com:/gitexample
git deploy setup -r production
And here's the error I get:
[production] $ chmod g+ws /gitexample &&
cd /gitexample &&
git init --shared &&
git config --bool receive.denyNonFastForwards false &&
git config receive.denyCurrentBranch ignore
stdin: is not a tty
chmod: cannot access `/gitexample': No such file or directory
<EMAIL_ADDRESS>is just an example so I don't have to post my current server ssh login

So, the sudo command tried to create the "/gitexample" directory but failed with "stdin: is not a tty". I don't know exactly why, but to work around the problem, log into the server and create the "/gitexample" directory yourself.

I found the problem, I wasn't accessing the correct folder on my server. Now it seems to be working.
Sorry for wasting your time, and thanks for this great program!


Allow end-user customisation of services extensions in @opentelemetry/instrumentation-aws-sdk

The customisation of how @opentelemetry/instrumentation-aws-sdk handles specific AWS services is limited to those pre-built into the package (SNS, SQS, dynamodb). This limits end-user customisability, resulting in either a need to fork or write custom clientside code. For example if a user wants to propagate tracecontext into a SDK lambda invocation they would have to manage this themselves, and AFAICT would not be able to access the inner aws-sdk span ID anyway. The may also wish to customise how SQS/SNS/DynamoDB context is propagated, which is not supported either.
Describe the solution you'd like to see
If AwsSdkInstrumentationConfig allowed the user to provide custom service extensions these could be added into ServicesExtensions to handle services other than SQS, SNS and dynamodb, or to handle SQS, SNS and dynamodb in different ways if the user desired.
e.g.
export interface AwsSdkServiceExtensionDefinition {
   serviceName: string;
   extension: ServiceExtension;
}
export interface AwsSdkInstrumentationConfig extends InstrumentationConfig {
  preRequestHook?: AwsSdkRequestCustomAttributeFunction;
  responseHook?: AwsSdkResponseCustomAttributeFunction;
  sqsProcessHook?: AwsSdkSqsProcessCustomAttributeFunction;

  customServiceExtensions?: AwsSdkServiceExtensionDefinition[];
  suppressInternalInstrumentation?: boolean;
  sqsExtractContextPropagationFromPayload?: boolean;
}

These could then be added via the ServicesExtensions constructor (to avoid changing the interface).
Describe alternatives you've considered
Fairly new to opentelemetry so if I've missed anything obvious about passing context into lambda invokes using the SDK I apologise, however the approach we've taken so far (adding to the payload in user code) leaves the aws-sdk instrumented span 'orphaned' (the lambda's span from tracecontext ends up having the active span as the active span when the payload is built.
However more than happy to implement and submit a PR if this would be welcomed.

The underlying motivation for this issue has been achieved in PR #916 so this can be closed.


ROS 2 Distro Input

Add a GitHub Actions input that enables a user to specify the ROS 2 distribution that will be used in this CI.

Closed by the release of version 0.2.2.


[Windows] Crash when connecting/disconnecting microphone

I just built the latest commit on this niche operating system for video games using MinGW to try the new microphone feature, because published release does not have it. Crashes even when microphone mode is disabled.
Despite that, works pretty fine.
EDIT:
Nothing in log about that

Microphone feature is not finished even for an alpha release. I haven't even tested it on Windows myself yet. Thanks for letting me know about the situation there. I'll keep it mind moving forward.


unrecognized font family react native material icons

Showing the error "unrecognized font family react native material icons"

They are using react-native-vector-icons under the hood for showing icons. Did you link this library?
react-native link react-native-vector-icons

Yes

This is react-native-vector-icons issue. Refer this link.


test: update docker + containerd

We didn't lock down the containerd version, which caused cluster
startup to fail when containerd was updated to 1.3.7 and the
configuration format changed.

@avalluri: this PR didn't pass testing because of the sanity connection issues, but PR #739 which includes it did pass.
Perhaps review PR #739 and we'll merge both at the same time?

containerd 1.3.7 has an issue, let's address that here. Do not merge yet...

containerd 1.3.7 has an issue, let's address that here. Do not merge yet...

Added 1e13890f for this. PR can be merged once testing is done.


docs: enable rustfmt for doc comments

format_code_in_doc_comments is a nightly rustfmt feature. (tracking issue: https://github.com/rust-lang/rustfmt/issues/3348)
I think this might be helpfull.
Usually, I would not consider this being an option, but given that already some other rustfmt feature are enabled... 😉

I have split out the CI part to https://github.com/testcontainers/testcontainers-rs-modules-community/pull/188 to get rid of the warnings


Kubelet authentication disabled by default.

Looking at a localhost desployment of this solution, it looks like the kubelet API allows unauthenticated access.  As such an attacker with access to a container running on the cluster can connect to the API and execute commands on other parts of the cluster.
To test something like the procedure from this post should work.
There's more discussion of this issue here and in the linked Kubernetes issues.

Thanks for the report and the test procedure. We'll be scheduling this as high priority

@Cynerva I believe you had an interest in looking at this one with @wwwtyro?  Feel free to self assign and give this a go when you've got the bandwidth.

@raesene Thanks very much for the heads up on this problem. We release a fix for this in the latest release of Canonical Kubernetes https://jujucharms.com/canonical-kubernetes/
Closing this bug. Please re-open if you find the problem persists. Open a new issue if you find other problems. Thanks!


Update mongo

Breaking change:

Add bucket name on file document

Coverage increased (+0.009%) to 99.444% when pulling 00706d1e8738b69a99fb49cec2e36a1c6f3eb125 on update-mongo into 0420cd0d5ef8de9e0f7c5a7323ab969507d02027 on next.


d3 Beta Local Storage isn't working correctly

Data Visualization with D3: Work with Data in D3
http://beta.freecodecamp.com/en/challenges/data-visualization-with-d3/work-with-data-in-d3
Issue Description

Submit and incorrect answer then submit the correct answer.  The tests and output will say the solution is incorrect.
Clear your localStorage and try the correct solution and the challenge will pass.
Browser Information

Browser Name, Version: Chrome
Operating System: Mac
Mobile, Desktop, or Tablet: Desktop

Solution Code

<body>
  <script>
    const dataset = [12, 31, 22, 17, 25, 18, 29, 14, 9];

    // Add your code below this line
    d3.select('body').selectAll('h2')
      .data(dataset)
      .enter()
      .append('h2')
      .text('New Title')

    // Add your code above this line
  </script>
</body>

Thanks for reporting this @benschac! I'm closing this as a duplicate of #12762


XCFramework is selecting the wrong framework architecture when building

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.4
Firebase SDK version: 6.24
Firebase Component: Analytics and GoogleSignIn
Component version: 6.24?
Installation method: Zip file

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:

Have previous non-xcframework version of Firebase integrated with project.
Update Firebase to new version using xcframework distributions.
Follow the included README for setup instructions.
Clean project and remove derived data.
Build project.

My project settings are configured as:
FRAMEWORK_SEARCH_PATHS = $(SRCROOT)/../Carthage/Build/iOS $(PROJECT_DIR)/../Frameworks/iOS/** $(inherited)
USER_HEADER_SEARCH_PATHS = $(PROJECT_DIR)/../Frameworks/iOS/** $(inherited)

After following the README instructions for integrating the new xcframework distributions, I am seeing various linker warnings and compilation errors.
ld: warning: ld: warning: ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/FirebaseCoreDiagnostics.xcframework/ios-armv7_arm64/FirebaseCoreDiagnostics.framework/FirebaseCoreDiagnostics, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/FirebaseCoreDiagnostics.xcframework/ios-armv7_arm64/FirebaseCoreDiagnostics.framework/FirebaseCoreDiagnostics (2 slices)ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/FirebaseCore.xcframework/ios-armv7_arm64/FirebaseCore.framework/FirebaseCore, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/FirebaseCore.xcframework/ios-armv7_arm64/FirebaseCore.framework/FirebaseCore (2 slices)

ld: warning: ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/FirebaseInstallations.xcframework/ios-armv7_arm64/FirebaseInstallations.framework/FirebaseInstallations, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/FirebaseInstallations.xcframework/ios-armv7_arm64/FirebaseInstallations.framework/FirebaseInstallations (2 slices)
ld: warning: ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/GoogleDataTransport.xcframework/ios-armv7_arm64/GoogleDataTransport.framework/GoogleDataTransport, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/GoogleDataTransport.xcframework/ios-armv7_arm64/GoogleDataTransport.framework/GoogleDataTransport (2 slices)
ld: warning: ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/GoogleDataTransportCCTSupport.xcframework/ios-armv7_arm64/GoogleDataTransportCCTSupport.framework/GoogleDataTransportCCTSupport, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/GoogleDataTransportCCTSupport.xcframework/ios-armv7_arm64/GoogleDataTransportCCTSupport.framework/GoogleDataTransportCCTSupport (2 slices)
ld: warning: ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/GoogleUtilities.xcframework/ios-armv7_arm64/GoogleUtilities.framework/GoogleUtilities, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/GoogleUtilities.xcframework/ios-armv7_arm64/GoogleUtilities.framework/GoogleUtilities (2 slices)
ld: warning: ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/nanopb.xcframework/ios-armv7_arm64/nanopb.framework/nanopb, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/nanopb.xcframework/ios-armv7_arm64/nanopb.framework/nanopb (2 slices)
ld: warning: ignoring file ../Frameworks/iOS/Firebase/FirebaseAnalytics/PromisesObjC.xcframework/ios-armv7_arm64/PromisesObjC.framework/PromisesObjC, missing required architecture x86_64 in file ../Frameworks/iOS/Firebase/FirebaseAnalytics/PromisesObjC.xcframework/ios-armv7_arm64/PromisesObjC.framework/PromisesObjC (2 slices)

This then causes symbol errors:
Undefined symbols for architecture x86_64:
  "_pb_encode", referenced from:
      _nano_two_pass_encoding in GoogleAppMeasurement(encoder_common_2dc83ff7e14bed2b5219272f00503573.o)
  "_pb_encode_tag_for_field", referenced from:
      _apmpb_encode_repeated_app_property in GoogleAppMeasurement(apmpb_app_property_encoder_cde6814e5db3498bcb2ac6002bf7f824.o)
      _apmpb_encode_repeated_audience in GoogleAppMeasurement(apmpb_audience_encoder_3547ee86a820789af8dc5948762785e8.o)
      _apmpb_encode_repeated_audience_leaf_filter_result in GoogleAppMeasurement(apmpb_audience_leaf_filter_result_encoder_95e433703290588cdb6301d608b362a9.o)
      _apmpb_encode_repeated_client_property in GoogleAppMeasurement(apmpb_client_property_encoder_b68794d4c68c9f0c6dd48853bff610e6.o)
      _apmpb_encode_repeated_custom_property in GoogleAppMeasurement(apmpb_custom_property_encoder_e848b81fe2750c170d2450f5654f68b9.o)
      _apmpb_encode_repeated_dynamic_filter_result_timestamp in GoogleAppMeasurement(apmpb_dynamic_filter_result_timestamp_encoder_7c10fd63325e5d126d6114ca5f35fe23.o)
      _apmpb_encode_repeated_event in GoogleAppMeasurement(apmpb_event_encoder_ccadf5737e2ea693fbebf19add598e06.o)
      ...
  "_pb_read", referenced from:
      _apmpb_decode_repeated_app_property in GoogleAppMeasurement(apmpb_app_property_decoder_eded01b2f53b552a17be0804e00129cf.o)
      _apmpb_decode_repeated_audience in GoogleAppMeasurement(apmpb_audience_decoder_69eee9ea34e880727e16f49edef1ec49.o)
      _apmpb_decode_repeated_audience_leaf_filter_result in GoogleAppMeasurement(apmpb_audience_leaf_filter_result_decoder_f210862365673fe9671c2efe1494709a.o)
      _apmpb_decode_repeated_client_property in GoogleAppMeasurement(apmpb_client_property_decoder_05ee743b2e5d65dcac7601a9227ef8bd.o)
      _apmpb_decode_repeated_custom_property in GoogleAppMeasurement(apmpb_custom_property_decoder_6f603d0b426b9f23d1ea57d7929d2ff6.o)
      _apmpb_decode_repeated_dynamic_filter_result_timestamp in GoogleAppMeasurement(apmpb_dynamic_filter_result_timestamp_decoder_6478c0953d8f4848c4db7c58352610a0.o)
      _apmpb_decode_repeated_event in GoogleAppMeasurement(apmpb_event_decoder_b9644316ed32fc57a2fb94760f277b32.o)
      ...
  "_pb_decode", referenced from:
      _apmpb_decode_app_property in GoogleAppMeasurement(apmpb_app_property_decoder_eded01b2f53b552a17be0804e00129cf.o)
      _apmpb_decode_audience in GoogleAppMeasurement(apmpb_audience_decoder_69eee9ea34e880727e16f49edef1ec49.o)
      _apmpb_decode_audience_leaf_filter_result in GoogleAppMeasurement(apmpb_audience_leaf_filter_result_decoder_f210862365673fe9671c2efe1494709a.o)
      _apmpb_decode_client_property in GoogleAppMeasurement(apmpb_client_property_decoder_05ee743b2e5d65dcac7601a9227ef8bd.o)
      _apmpb_decode_custom_property in GoogleAppMeasurement(apmpb_custom_property_decoder_6f603d0b426b9f23d1ea57d7929d2ff6.o)
      _apmpb_decode_dynamic_filter_result_timestamp in GoogleAppMeasurement(apmpb_dynamic_filter_result_timestamp_decoder_6478c0953d8f4848c4db7c58352610a0.o)
      _apmpb_decode_event in GoogleAppMeasurement(apmpb_event_decoder_b9644316ed32fc57a2fb94760f277b32.o)
      ...
  "_OBJC_CLASS_$_GULSwizzler", referenced from:
      objc-class-ref in GoogleAppMeasurement(UIViewController+APMScreenClassName_228c1aa1a108dedb7b850c6178789c52.o)
  "_GULLogInfo", referenced from:
      ___44+[UIViewController(APMScreenClassName) load]_block_invoke in GoogleAppMeasurement(UIViewController+APMScreenClassName_228c1aa1a108dedb7b850c6178789c52.o)
  "_GULIsLoggableLevel", referenced from:
      -[APMMonitor isLoggableLevel:] in GoogleAppMeasurement(APMMonitor_c75e0f1df90e609ecfbf4386f9c0c5d1.o)
  "_kGULNetworkHTTPStatusCodeNotFound", referenced from:
      -[APMMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
  "_pb_decode_varint", referenced from:
      _nano_decode_repeated_uint64 in GoogleAppMeasurement(decoder_common_e0b3c2324a25b25f3cc61816d06be1ad.o)
  "_OBJC_CLASS_$_FIRComponent", referenced from:
      objc-class-ref in FIRAnalyticsConnector(FIRAnalyticsConnector_c162b9f6e9dd193ef13757b8d7ebe6f7.o)
  "_kGULNetworkHTTPStatusCodeUnavailable", referenced from:
      -[APMMeasurement networkUploadCompletionHandlerWithResponse:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMETaskManager handleFetchingExperimentsResponse:data:error:] in GoogleAppMeasurement(APMETaskManager_052f57457e2ce90d53f41d6c323142d8.o)
  "_pb_encode_varint", referenced from:
      _nano_encode_repeated_uint64 in GoogleAppMeasurement(encoder_common_2dc83ff7e14bed2b5219272f00503573.o)
  "_GULLogError", referenced from:
      +[APMAnalytics startWithAppID:origin:options:] in GoogleAppMeasurement(APMAnalytics_8b8a060bbe8023e2a8dc40576f3452ac.o)
      -[APMUserDefaults synchronize] in GoogleAppMeasurement(APMUserDefaults_7da56510c56318566b03004b24f0a510.o)
  "_kGULNetworkHTTPStatusCodeNotModified", referenced from:
      ___41-[APMMeasurement requestDeferredDeepLink]_block_invoke in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
  "_pb_ostream_from_buffer", referenced from:
      _nano_two_pass_encoding in GoogleAppMeasurement(encoder_common_2dc83ff7e14bed2b5219272f00503573.o)
  "_kGULNetworkHTTPStatusCodeCannotAcceptTraffic", referenced from:
      -[APMMeasurement networkUploadCompletionHandlerWithResponse:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMETaskManager handleFetchingExperimentsResponse:data:error:] in GoogleAppMeasurement(APMETaskManager_052f57457e2ce90d53f41d6c323142d8.o)
  "_kGULNetworkHTTPStatusNoContent", referenced from:
      ___41-[APMMeasurement requestDeferredDeepLink]_block_invoke in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMMeasurement networkUploadCompletionHandlerWithResponse:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMETaskManager handleFetchingExperimentsResponse:data:error:] in GoogleAppMeasurement(APMETaskManager_052f57457e2ce90d53f41d6c323142d8.o)
  "_GULLogWarning", referenced from:
      +[APMMeasurement sharedInstance] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMUserDefaults objectForKey:] in GoogleAppMeasurement(APMUserDefaults_7da56510c56318566b03004b24f0a510.o)
      -[APMUserDefaults setObject:forKey:] in GoogleAppMeasurement(APMUserDefaults_7da56510c56318566b03004b24f0a510.o)
      -[APMUserDefaults synchronize] in GoogleAppMeasurement(APMUserDefaults_7da56510c56318566b03004b24f0a510.o)
      ___44+[UIViewController(APMScreenClassName) load]_block_invoke in GoogleAppMeasurement(UIViewController+APMScreenClassName_228c1aa1a108dedb7b850c6178789c52.o)
  "_pb_istream_from_buffer", referenced from:
      _apmpb_decode_app_property in GoogleAppMeasurement(apmpb_app_property_decoder_eded01b2f53b552a17be0804e00129cf.o)
      _apmpb_decode_audience in GoogleAppMeasurement(apmpb_audience_decoder_69eee9ea34e880727e16f49edef1ec49.o)
      _apmpb_decode_audience_leaf_filter_result in GoogleAppMeasurement(apmpb_audience_leaf_filter_result_decoder_f210862365673fe9671c2efe1494709a.o)
      _apmpb_decode_client_property in GoogleAppMeasurement(apmpb_client_property_decoder_05ee743b2e5d65dcac7601a9227ef8bd.o)
      _apmpb_decode_custom_property in GoogleAppMeasurement(apmpb_custom_property_decoder_6f603d0b426b9f23d1ea57d7929d2ff6.o)
      _apmpb_decode_dynamic_filter_result_timestamp in GoogleAppMeasurement(apmpb_dynamic_filter_result_timestamp_decoder_6478c0953d8f4848c4db7c58352610a0.o)
      _apmpb_decode_event in GoogleAppMeasurement(apmpb_event_decoder_b9644316ed32fc57a2fb94760f277b32.o)
      ...
  "_OBJC_CLASS_$_GULAppDelegateSwizzler", referenced from:
      objc-class-ref in GoogleAppMeasurement(APMAnalytics_8b8a060bbe8023e2a8dc40576f3452ac.o)
  "_GULSetLoggerLevel", referenced from:
      -[APMMonitor setDebugModeEnabled:] in GoogleAppMeasurement(APMMonitor_c75e0f1df90e609ecfbf4386f9c0c5d1.o)
      -[APMMonitor setVerboseLoggingEnabled:] in GoogleAppMeasurement(APMMonitor_c75e0f1df90e609ecfbf4386f9c0c5d1.o)
  "_pb_encode_submessage", referenced from:
      _apmpb_encode_repeated_app_property in GoogleAppMeasurement(apmpb_app_property_encoder_cde6814e5db3498bcb2ac6002bf7f824.o)
      _apmpb_encode_repeated_audience in GoogleAppMeasurement(apmpb_audience_encoder_3547ee86a820789af8dc5948762785e8.o)
      _apmpb_encode_repeated_audience_leaf_filter_result in GoogleAppMeasurement(apmpb_audience_leaf_filter_result_encoder_95e433703290588cdb6301d608b362a9.o)
      _apmpb_encode_repeated_client_property in GoogleAppMeasurement(apmpb_client_property_encoder_b68794d4c68c9f0c6dd48853bff610e6.o)
      _apmpb_encode_repeated_custom_property in GoogleAppMeasurement(apmpb_custom_property_encoder_e848b81fe2750c170d2450f5654f68b9.o)
      _apmpb_encode_repeated_dynamic_filter_result_timestamp in GoogleAppMeasurement(apmpb_dynamic_filter_result_timestamp_encoder_7c10fd63325e5d126d6114ca5f35fe23.o)
      _apmpb_encode_repeated_event in GoogleAppMeasurement(apmpb_event_encoder_ccadf5737e2ea693fbebf19add598e06.o)
      ...
  "_OBJC_CLASS_$_FIRApp", referenced from:
      objc-class-ref in ExtensionSupport.o
      objc-class-ref in FIRAnalyticsConnector(FIRAnalyticsConnector_c162b9f6e9dd193ef13757b8d7ebe6f7.o)
      objc-class-ref in FirebaseAnalytics(FIRAnalytics_7251d33630b5526046515eb342cf4e83.o)
  "_OBJC_CLASS_$_GULAppEnvironmentUtil", referenced from:
      objc-class-ref in GoogleAppMeasurement(APMEExperimentRequestBuilder_b597f7881657dc0c89417644c8c09c2d.o)
  "_OBJC_CLASS_$_GULMutableDictionary", referenced from:
      objc-class-ref in GoogleAppMeasurement(APMEExperiment_1bf45e2c961832e81d75bd5e0b06b954.o)
      objc-class-ref in GoogleAppMeasurement(APMEExperimentRequestBuilder_b597f7881657dc0c89417644c8c09c2d.o)
      objc-class-ref in GoogleAppMeasurement(APMEManager_7e60ef68ad7939ae393accdc8eb8c94c.o)
      objc-class-ref in GoogleAppMeasurement(APMESnapshot_c69b8d8fbc4907e081e18c7f5acf8b55.o)
      objc-class-ref in GoogleAppMeasurement(APMRemoteConfig_7fec4c21fba9c80861eb73bc952a74c1.o)
  "_OBJC_CLASS_$_FIRInstallations", referenced from:
      objc-class-ref in FirebaseAnalytics(FIRAnalytics_7251d33630b5526046515eb342cf4e83.o)
  "_FIRInstallationIDDidChangeNotification", referenced from:
      +[FIRAnalytics observeFirebaseInstallationIDChanges] in FirebaseAnalytics(FIRAnalytics_7251d33630b5526046515eb342cf4e83.o)
  "_pb_encode_string", referenced from:
      _nano_encode_string in GoogleAppMeasurement(encoder_common_2dc83ff7e14bed2b5219272f00503573.o)
  "_OBJC_CLASS_$_FIROptions", referenced from:
      objc-class-ref in FirebaseAnalytics(FIRAnalytics_7251d33630b5526046515eb342cf4e83.o)
  "_kFIRLoggerAnalytics", referenced from:
      +[FIRAnalytics startWithConfiguration:options:] in FirebaseAnalytics(FIRAnalytics_7251d33630b5526046515eb342cf4e83.o)
  "_GULLogBasic", referenced from:
      -[APMASLLogger logMessage:logTag:messageCode:withLogLevel:] in GoogleAppMeasurement(APMASLLogger_a09dc4365a8306d72148f2d5804b7c98.o)
  "_kGULNetworkHTTPStatusOK", referenced from:
      ___41-[APMMeasurement requestDeferredDeepLink]_block_invoke in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMMeasurement networkUploadCompletionHandlerWithResponse:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMMeasurement networkRemoteConfigFetchCompletionHandler:data:error:] in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      -[APMETaskManager handleFetchingExperimentsResponse:data:error:] in GoogleAppMeasurement(APMETaskManager_052f57457e2ce90d53f41d6c323142d8.o)
  "_OBJC_CLASS_$_GULNetwork", referenced from:
      objc-class-ref in GoogleAppMeasurement(APMAnalytics_8b8a060bbe8023e2a8dc40576f3452ac.o)
      objc-class-ref in GoogleAppMeasurement(APMMeasurement_87bdad44f2b9aa68c2d607a36be1b8c5.o)
      objc-class-ref in GoogleAppMeasurement(APMAppDelegateInterceptor_a0002e42c5efa9c806d7f6f730bbfe7e.o)
      objc-class-ref in GoogleAppMeasurement(APMETaskManager_052f57457e2ce90d53f41d6c323142d8.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

and compilation fails at this point. I can see the x86_64 architecture present in the xcframework so I'm not sure why it's trying to search deep within armv7_arm64. Sometimes it will build correctly if you don't wipe derived data.
I've tried editing my search paths to not be recursive and that gives me a different compilation error on the Firebase.h header: 'FirebaseCore/FirebaseCore.h' file not found. Not sure whether that's related at all.
Any help looking into this would be much appreciated!

Are you using Carthage, or integrating the zip manually?

I'm integrating the zip manually.

Can you share a project that repros this build issue?

A few more questions:

I notice FRAMEWORK_SEARCH_PATHS = $(SRCROOT)/../Carthage/Build/iOS. Are there any Firebase frameworks from Carthage there?
Have you successfully integrated previous versions of the Firebase zip distribution?
Please try reintegrating from scratch - remove all Firebase frameworks from the app and then add them back.

I notice FRAMEWORK_SEARCH_PATHS = $(SRCROOT)/../Carthage/Build/iOS. Are there any Firebase frameworks from Carthage there?

We have some old Crashlytics and Fabric frameworks managed by Carthage (which I should probably update to FirebaseCrashlytics). I tried removing them from the project but it didn't fix anything.

Have you successfully integrated previous versions of the Firebase zip distribution?

Yes, this has been our setup for some time.

Please try reintegrating from scratch - remove all Firebase frameworks from the app and then add them back.
Can you share a project that repros this build issue?

Will give this a try this next, and if that doesn't work I'll try reproducing with a sample project.
Also worth noting that my Xcode auto-updated in the middle of all this to 11.5, sadly does not change anything.

In the end I gave up trying to integrate the frameworks manually and switched to using the Carthage setup. So far everything is back to normal although I notice that Carthage is still downloading .framework variants of Firebase which makes me wonder if I'll run into this problem again in the future.
I spent a good amount of time trying to reproduce the issue in a clean project with no luck. Our app codebase is 10+ years old so it's hard replicating everything in a reasonable amount of time. :/
One last-ditch idea is that it's possibly related to our extension target setups, since compilation often failed first in those targets (which are dependencies for our main target). I found that we have an additional linker field for that:
LD_RUNPATH_SEARCH_PATHS = $(inherited) @executable_path/Frameworks @executable_path/../../Frameworks

but nothing else out of the ordinary.
If you have any ideas I'm happy to try them, otherwise feel free to close this. Thanks for the help.

Thanks for the follow up @trevor-e - Yeah it could be related to the LD_RUNPATH_SEARCH_PATHS setting.  We're sticking with .frameworks for Carthage for the forseeable future since Carthage does not yet support .xcframeworks.  I'll close for now and can reopen with additional future info.


Prevent swipe action when detail from persistent case tile is expanded

Contains commits from https://github.com/dimagi/commcare-odk/pull/964 , review that one first
When you expand a tabbed case detail from a persistent case tile, swipe actions are still registered for the screen hidden by the case detail. So if you are in form entry and swipe to change the tab, it also advances you in the form. Or if you swipe back it sometimes exits the current activity.

This PR blocks swipes from dispatching at the CommCareActivity level if something is obstructing the main view.
Also remove some unused methods...

reviewed commit-by-commit and looks good other than my comment. It looks like there's a bug that removed the use of whether back navigation is available, but I don't think we should remove the declarations.

Okay, reverted that commit, should be good to go now


fix MethodDecorator generic

Fixes https://github.com/microsoft/TypeScript/issues/55980

The linked issue is marked Working as Intended, so we will not take this PR.


[AIRFLOW-3323] Support HTTP basic authentication for Airflow Flower

Jira

https://issues.apache.org/jira/browse/AIRFLOW-3323

Description
The current airflow flower doesn't come with any authentication. This may make essential information exposed to in an untrusted environment.
Currently Flower itself supports

HTTP Basic Authentication
Google OAuth 2.0
GitHub OAuth

Given Flower is not really the most essential component of Airflow, we don't have to support all its authentication methods. But may be good to at least support Basic Authentication.
Ref:
https://flower.readthedocs.io/en/latest/auth.html
Documentation
docs/security.rst & docstring in airflow/bin/cli.py are updated accordingly.
Code Quality

[x] Passes flake8

Screenshots
1. Asking for ID/password

2. Failed authentication

Codecov Report

Merging #4166 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #4166      +/-   ##
==========================================
- Coverage   77.68%   77.64%   -0.04%
==========================================
  Files         199      199
  Lines       16273    16276       +3
==========================================
- Hits        12641    12638       -3
- Misses       3632     3638       +6

Impacted Files
Coverage Δ

airflow/bin/cli.py
64.59% <0%> (-0.24%)
:arrow_down:

airflow/jobs.py
77.09% <0%> (-0.28%)
:arrow_down:

Continue to review full report at Codecov.

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

@ashb @Fokko @kaxil a gentle ping, PTAL


[Feature]: Show available components list

Is your feature request related to a problem? Please describe.
As a user of the React Native UI library, I often find it challenging to remember all available components and their respective functionalities. It would be helpful to have a centralized list of available components to reference.
Describe the solution you'd like
I would like to have a feature within the React Native UI library that displays a comprehensive list of available components. This list should include the name of each component along with a brief description of its purpose or functionality. For example npx attlr list
Describe alternatives you've considered
One alternative could be manually documenting all available components in a separate document or wiki page. However, this approach may be time-consuming and prone to inconsistencies as the library evolves.
Additional context
Having a centralized list of available components would not only aid current users in understanding the library better but also facilitate onboarding for new users and developers.
Adding the feature
@MsingathiMat

Added here


Enable DRM backend for qemux86-64 image

[GDP-166] QEMU GFX performance drop
Enabling DRM kernel modules and gallium support in mesa. This allows
weston to use the drm-backend, when -vga std/virtio is used on the
kvm host.

I've pushed this to hopefully receive feedback via testing. The image should be launched in the same manner but with -vga std instead of -vga vmware. Testing internally has shown differing results dependant on the hosts qemu kvm version. Enabling the gallium drivers in mesa also shows improvement gains with the regular fbdev backend

Builds and runs ok for me here

it looks fine if test performance is ok.

This still requires further testing by other users, drm with -std has cursor issues as documented in jira on my 14.04 qemu kvm package

I plan to test this on more host systems this week

I tested http://docs.projects.genivi.org/gdp_files/v11/rc1/qemux86-64/gdp-11-rc1-qemu.ext4.gz with 1404 qemu kvm, and it also has cursor issues with fbdev driver

I think the best option for supporting DRM would be to make it user configurable at init time or via local.conf. However this would require a sure way of acquiring if the kvm host system was compatible with the required kvm/qemu kernel version etc

So what's the status of this PR?

So I built this PR successfully and was about to launch GDP in Qemu with it but I had to change "-vga vmware" to "-vga std". "-vga virtio" didn't work for me, the HMI didn't launch with that option. Shall I just merge this and update the Qemu commandline in the wiki?

@tom--pollard ?

I would vote against merging this as the output is dependant on the host qemu/kvm version.  It would have to be optional in init.sh. I know for instance (as documented in JIRA) that it will not work for 14.04 hosts

if qemu is already unusable because of its performance, would it make sense to not wait until somebody finds a init.sh script, and drop support for 14.04 hosts?
m2c

@tom--pollard by 14.04 you mean Ubuntu I assume (let's not make that implicit assumption in GDP :)).
@tardyp Not sure what you mean. Find a init.sh where? We shouldn't drop support for Ubuntu 14.04 IMO.

@tardyp I know you must be busy so I wanted to remind you that I wait for your clarification. :)
@tom--pollard The commandline is already different for different hosts so I'm not sure anything will change there. Correct?

@zeenix I was refering to @tom--pollard suggestion that there is a magic init.sh script to be written, which would detect buggy DRM implementation, and disable drm in those cases.
my point is that anyway if DRM is disabled, then the UI is not usable so we should keep the solution simple and only support recent qemu hosts.
m2c in the hope it helps

@tardyp Thanks so much for explaining! Yes, I see what you mean now and I completely agree.

Converted to apply to genivi-dev-platform instead, after meta-genivi-dev subtree addition
--> https://github.com/GENIVI/genivi-dev-platform/pull/96
Closing this one.


builder: remove pandoc deps

So that it's easier to add windows build (#80).

Can it be conditional on the OS?  That way we can still get nice reports in the non-windows builds?

I don't think we want the lint report for all platform, since lint is mostly based on static analysis: I would expect it to be the same everywhere.
I moved the pandoc call to .travis.yml that way it will display something on linux.

SGTM


Add support: some mysql sql

Add support:
USE test
SET NAMES UTF8
SELECT @x, @test FROM v.t
SAVEPOINT a6656450_c8fe_4cbc_a75c_37d60d266629
ROLLBACK TO SAVEPOINT 0105c3d0_2750_4d45_be35_f17952cbf389
RELEASE SAVEPOINT 0105c3d0_2750_4d45_be35_f17952cbf389
SET SESSION TRANSACTION MODE
UPDATE LIMIT N|ALL
SELECT LIMIT N, M
Parameter Mark

Pull Request Test Coverage Report for Build 620326241

72 of 78 (92.31%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.006%) to 90.023%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/dialect/mysql.rs
0
1
0.0%

src/ast/mod.rs
19
21
90.48%

src/parser.rs
36
39
92.31%

Files with Coverage Reduction
New Missed Lines
%

src/ast/mod.rs
1
72.35%

Totals

Change from base Build 552534083:
0.006%

Covered Lines:
5468

Relevant Lines:
6074

💛  - Coveralls

Hi @juaby  -- sorry for the delay in review. I am going to help out now with this repo and we are working to clear the backlog. Is this PR still something you would like to work on to help contribute?

I am closing what look like stale PRs in this repo; I apologize in advance if this is a mistake -- please feel free to reopen if you want to keep working on this issue.


NETOBSERV-1623 update sed commands to support macos

Description
Attempt to make sed working on MacOs.
Run the following target to give a try:
$ make oc-commands
### Generating oc commands
DIST_DIR=build \
K8S_CLI_BIN=oc \
IMAGE=quay.io/julien/network-observability-cli:main \
PULL_POLICY=Always \
VERSION=main \
./scripts/inject.sh
updating CLI images to quay.io/julien/network-observability-cli:main
updating CLI pull policy to Always
updating CLI version to main
updating K8S CLI to oc
prefixing with oc-
pull policy not provided, keeping current ones
output generated in build folder

The generated file ./build/oc-netobserv should contains YAMLs and your quay image with version main.
Dependencies
n/a
Checklist
If you are not familiar with our processes or don't know what to answer in the list below, let us know in a comment: the maintainers will take care of that.

[ ] Is this PR backed with a JIRA ticket? If so, make sure it is written as a title prefix (in general, PRs affecting the NetObserv/Network Observability product should be backed with a JIRA ticket - especially if they bring user facing changes).
[ ] Does this PR require product documentation?

[ ] If so, make sure the JIRA epic is labelled with "documentation" and provides a description relevant for doc writers, such as use cases or scenarios. Any required step to activate or configure the feature should be documented there, such as new CRD knobs.

[ ] Does this PR require a product release notes entry?

[ ] If so, fill in "Release Note Text" in the JIRA.

[ ] Is there anything else the QE team should know before testing? E.g: configuration changes, environment setup, etc.

[ ] If so, make sure it is described in the JIRA ticket.

QE requirements (check 1 from the list):

[ ] Standard QE validation, with pre-merge tests unless stated otherwise.
[ ] Regression tests only (e.g. refactoring with no user-facing change).
[ ] No QE (e.g. trivial change with high reviewer's confidence, or per agreement with the QE team).

@Amoghrd could you please give another try with these changes ?
I don't see why it would not work according to what I read from https://stackoverflow.com/a/4247319

Thanks @stleerh for the details ! Do you run on Mac too ?
Let's give a try with first solution as I already try gsed and it was more complex to manage.
The inject script works in a tmp folder and already cleanup before copying to output so it's not a problem to me to have temporary .bak files in between.

FYI, commit 3 is my change in this pull request.

@stleerh latest commits works fine on mac.
/label qe-approved

Thanks for the help @stleerh & @Amoghrd !


Decrease the scan interval

Decreased the scan interval time to 10 seconds to get a quicker response on state changes. Necessary when doing automations based on cable connection to get a faster response.

Setting is available in 2024.9.3


rename Enable batch upload feature to Batch upload

Fixes #949
Renamed references of enable batch upload to batch upload.
New UI for features is shown below:

Changes proposed in this pull request:

renamed enable_batch_upload? flipflop feature to batch_upload?

@projecthydra-labs/hyrax-code-reviewers

Thank you, @mcritchlow!