SqlConnectionStringBuilder should also be updated to match the default value changes in 4.0.0-preview1

Describe the bug
4.0.0-preview1 include an broken change update the default value of Encrypt to true in #1210
https://github.com/dotnet/SqlClient/blob/main/release-notes/4.0/4.0.0-preview1.md#encrypt-default-value-set-to-true
But it didn't update SqlConnectionStringBuilder, which lead to confuse when parse an connStr with SqlConnectionStringBuilder(The value from SqlConnectionStringBuilder don't match what's really used by connection)
Expected behavior

new SqlConnectionStringBuilder("").Encrypt should be true(parse from an connStr without Encrypt set)
No idea what new SqlConnectionStringBuilder().Encrypt should be, but at least after fixed case 1, it shouldn't broken roundtrip
Assert(new SqlConnectionStringBuilder().Encrypt == new SqlConnectionStringBuilder(new SqlConnectionStringBuilder().ToString()).Encrypt)

Further technical details
Microsoft.Data.SqlClient version: 4.0.0-preview1.21237.2

Thanks @yyjdelete, We'll fix it.


mavsdk_tests: improve usage text

These are improvements based on the review by @hamishwillee in https://github.com/PX4/Devguide/pull/982.

Yes, thanks!


Updated parser type_data_struct

@mattn Please review, merge, and create release 0.1.8

Codecov Report

Merging #335 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #335   +/-   ##
=======================================
  Coverage   88.39%   88.39%
=======================================
  Files          15       15
  Lines        2681     2681
=======================================
  Hits         2370     2370
  Misses        201      201
  Partials      110      110

Impacted Files
Coverage Δ

anko.go
68.47% <ø> (ø)

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 3921fdd...224ea1a. Read the comment docs.

@mattn Any thoughts?

Thank you


Added React Js course link in web development resources

🛠 Fixes issue #29
📇 Changes proposed ---> Added React JS course link by FreeCodeCamp.
✅ Check List (Mark all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] This PR contains changes in the documentation
[x] This PR contains changes in the Code of the project
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@all-contributors please add @Arbtrage as a contributor of tutorial


How to load global variables, mixins, etc?

Hi, I'm using react-on-rails with react-css-modules and webpack. Original react-on-rails boilerplate provides setup using sass-resources-loader, which makes able to define resources with global variables or mixins for all css modules inside the project:
sassResources: ['./app/assets/styles/app-variables.scss', './app/assets/styles/app-mixins.scss'],

Everything works well, until I started testing of components. Original command raised Error: "selected" CSS module is undefined.. So I added --require part to the command:
"test": "NODE_PATH=./app mocha --compilers js:babel-core/register --require ./app/libs/testHelper.js --require ./app/libs/testNullCompiler.js --require ./app/libs/testCSSModulesHook.js 'app/**/*.spec.@(js|jsx)'",

Content of app/libs/testCSSModulesHook.js:
import hook from 'css-modules-require-hook';
import sass from 'node-sass';
hook({
  extensions: ['.scss'],
  preprocessCss: data => sass.renderSync({ data }).css,
});

After that testing command started to raise "Error: no mixin named screen" or "Error: no variable named $var"
Is there any way to define resources with global variables and mixins using css-modules-require-hook?

Found solution:
app/libs/testCSSModulesHook.js:
import hook from 'css-modules-require-hook';
import sass from 'node-sass';
import path from 'path';
import fs from 'fs';

import {sassResources} from '../../webpack.client.base.config';

hook({
  extensions: ['.scss'],
  preprocessCss: data => sass.renderSync({
    data: sassResources.map(file => fs.readFileSync(path.resolve(__dirname, '../..', file), 'utf8')).join('') + data,
  }).css,
});


Manufacturing metrics

Similar to posing challenges that maximize some arbitrary performance metric, it would be useful to establish manufacturability metrics (and post a leaderboard for approaches there)

Yes, I agree some form of leaderboard would be very useful. This could be based on the imageruler, although one would need to think carefully e.g. about how to handle designs that are not quite binary. It would be useful to have a dataset of designs created by a variety of approaches, which could then be used to stress test the manufacturability metrics.

The leaderboard with manufacturing metrics is now live, here:
docs: https://invrs-io.github.io/leaderboard/readme.html
repo: https://github.com/invrs-io/leaderboard


Lb/88 placement school details page for support users

Context
Support users should be able to navigate from the list of organisations to the detail page for a school
Changes proposed in this pull request

Added lots of fields for the gias school
A show page for the school to match the beta prototype designs

There are two things in the designs that are not included in the PR:

The primary and secondary nav bars as those are being completed in other PRs
The links row actions "Change", as we don't have anywhere for those change links to go yet.

Guidance to review

You'll need to run migrations and update the gias schools with the rake task (rake gias_update) to bring in all the new gias school fields

Link to Trello card
https://trello.com/c/gyMTPatr
Things to check

[NA] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[x] This code does not rely on migrations in the same Pull Request (it does, but that's ok)
[NA] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[NA] API release notes have been updated if necessary
[NA] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[NA] Required environment variables have been updated or added to the Azure KeyVault

Screenshots
https://github.com/DFE-Digital/itt-mentor-services/assets/44073106/7e603dc2-c55a-4030-b003-a34570f0dcf5

 Placements School details page for support users


Reqwest and hyper-native-tls together.

One possible fix for https://github.com/rusoto/rusoto/issues/486 .
I like this option because it makes our credentials sourcing code for instance metadata and ECS containers clearer.  I've also forced our service Client types to be supplied a request dispatcher.  This is eased by a new helper function that makes a hyper-native-tls Client that can be dropped in, as the integration test and code samples show.  This change will encourage users of an AWS service client to re-use the request dispatcher across services.  This is different from our now-removed default client constructor which made a new hyper client per AWS service client construction.  I suppose we should verify it's thread-safe to do this.
Potential future pitfalls are if reqwest and hyper-native-tls have a library-related conflict in the future.  I think we can keep them all in lockstep though, avoiding any problems.

I think we can clear out some documentation on getting openssl to link and work, especially for OSX.  Wish there was more documentation on native-tls.

Integration tests pass on my machine.  I could test the credential sourcing with Moe but I did that several times in https://github.com/rusoto/rusoto/pull/498 and it worked fine.

Appveyor is doing interesting things lately.  Lots sometimes the project compiles in 20 minutes, sometimes it hits the hour mark and times out.  Saw something new on their web site when re-running this build:
ERR Error running script (call to f_5b8e3b60e050400311bc8b6ef2cbba37bc0b9cb3): @user_script:1: @user_script: 1: -OOM command not allowed when used memory > 'maxmemory'.

Aside from my naming nitpicking, I'm very much on board with this PR.

Functions renamed, ready for review again.

Looks like a with_request_dispatcher is left here in the SqsClient tests, likely from #526 getting merged this morning.

Does TravisCI test with the PR merged into master?  It must, since that code doesn't exist in the branch, thus running cargo test --features sqs --lib doesn't error on this branch.
Rebasing and re-uploading after test pass on my machine.

looks good to me.


Update configure-kubenet.md

@andresnava : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @laurenhughes Is this one you can take a look at? Thanks.

Thanks @andresnava!
#sign-off

@laurenhughes: I'm sorry - only the author of this article, @mlearned, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


Bank Feed with Business Central On Prem

Only after opening a ticket with Microsoft has it become apparent that the Bank Feed functionality is severely limited for the On Prem Version of Business Central (Ticket<PHONE_NUMBER>03206).
In addition to paying per seat, development is necessary to hook into Yodlee's API for On-Prem.
Please update your documentation to disclose those severe limitations.

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

ID: bd798ca6-4c2b-4470-3c46-894c4c68c8a8
Version Independent ID: c7ac4f0e-ccf3-70e1-5a6a-90063ab963cb
Content: Set Up Yodlee Bank Feeds - Business Central
Content Source: business-central/bank-how-setup-bank-statement-service.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Thank you for your feedback! This will be fixed in the next doc update.

Thank you!
Sincerely,
Kieran Sweeney
Kieran Sweeney
Business Software Consultant
Office:301-360-0001
Direct:301-517-6694
KTL Solutions, Inc. - Disclaimer
This message contains confidential information and is intended only for the individual(s) addressed in the message. If you are not the named addressee, you should not disseminate, distribute, or copy this e-mail. If you are not the intended recipient, you are notified that disclosing, distributing, or copying this e-mail is strictly prohibited.
From: Eva Dupont<EMAIL_ADDRESS>Sent: Wednesday, June 24, 2020 4:17 AM
To: MicrosoftDocs/dynamics365smb-docs<EMAIL_ADDRESS>Cc: Kieran Sweeney<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics365smb-docs] Bank Feed with Business Central On Prem (#390)
Thank you for your feedback! This will be fixed in the next doc update.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/dynamics365smb-docs/issues/390#issuecomment-648671091, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AONWV6F6OVQW6QWX4YKVUG3RYGY7BANCNFSM4OGBBBVA.


predicate could be a blank node?

The RML spec states the following:

Both predicate maps and object maps are term maps.

But a term map can be a blank node.
Would this be "misleading"?
Does this mean that a predicate could be a blank node?
Obviously, this is not correct: a predicate should only be an IRI.

@anaigmo is this already solved in the diagrams?

I left a note clarifying it, it will be solved with the constrains

ok, so we can close this as @anaigmo already takes it :-)


add a prop for handling no smoothing at scatter Viz

This is related to a web-eda PR, https://github.com/VEuPathDB/web-eda/pull/1032
The purpose of this work is to have an additional prop, which will be used to examine whether the data has no smoothed mean and use the info to show/hide message.
There is another minor request involved in this PR, which is to increase the title of axis range control, e.g., Y-axis controls to be the same same font and size as the text for "Axis variables" and "Stratification variables". https://github.com/VEuPathDB/web-eda/issues/1011#issuecomment-1097035678 and https://github.com/VEuPathDB/web-eda/issues/1011#issuecomment-1097045514

@asizemore No problem! I know you also have lots of things to deal with. Thank you for taking time for review this! 👍


added settings for vouch reputation rewards

Setting for ref point rewards added
Code and tests changed for ref point setting
Some unused settings removed
Some additional settings added - mainly for the 5 levels of organizations we now have in the game guide

As per game guide & constitution
Deployment

deploy settings, accounts
updateSettings

Deployed


bug(?): Keycastr sometimes only captures modifier keys when Discord is monitoring input

This is the weirdest issue I've experienced on Mac. I realize it's most likely a bug with the OS or Discord and not Keycastr, but I'm raising here for awareness and in case there are any additional checks or workarounds that can be done to resolve the issue.
I recently upgraded my machine and after setting up all streaming related applications, I was surprised to find that Keycastr no longer worked. My old machine was a 2017 Macbook Pro, while my new machine is a 2023 Macbook Pro w/M3 Pro chip.
From my initial setup, Keycastr would only capture modifier keys and no others. The default overlay would only show clicks/taps and no keys. The Svelte overlay would show modifier keys being pressed but no other keys.
I worked through all the troubleshooting and wiki guides to no avail. I attempted uninstalling and reinstalling Keycastr. I also reverted to older versions to see if there was maybe a newly introduced bug - nothing worked. I removed Keycastr from input monitoring between each trial. For each attempt, I downloaded the artifact from the GitHub Releases page and copied into Applications. Each time I reopened Keycastr was from Applications directly because using Spotlight would display Keycastr from Trash (which I deleted as well).
Viewing events via Console didn't display any errors from Keycastr, or any other errors aside from telemetry errors from various Apple apps due to my VPN.
Finally, I installed KeyLimePie via the App Store and found that it couldn't capture any keys.
This made me wonder if it was a conflict. The only other input monitoring app I have installed is Discord, which I didn't have installed on the older machine because I mainly use mobile Discord. I'm not sure why Discord requires input monitoring (maybe for voice chat), but I rarely use it so removed its input monitoring permissions. Removing Discord's permissions and reinstalling the binary didn't unblock Keycastr, but did unblock KeyLimePie. Removing Discord's permissions and re-installing Keycastr via Homebrew worked. After this, uninstalling Keycastr via Homebrew and installing the artifact manually also worked.
I realize a reproduction may be nearly impossible, so maybe a note on potential conflicts with other input monitoring in the readme would help. For example:

If issues persist after removing Keycastr permissions from Input Monitoring and re-installing, try toggling off all input monitoring applications. Then, ensure Keycastr is fully removed (e.g. Move to Trash then in Trash select Delete immediately). Install Keycastr, then enable input monitoring. Other input monitoring applications can then be re-enabled.

Thank you for opening an issue and describing this scenario. Yes, there are cases where other applications can interfere with input monitoring. There is also secure input to consider, which you can enable and test out in Terminal.app. Notice that KeyCastr won't receive events while Terminal is in the foreground and other apps in the menu bar might not even receive mouse clicks. I don't know if Discord is also using secure input, but it's possible. It's all a bit of a mess from an app developer's perspective.
Glad you got to the bottom of the issue. My guess is that KeyCastr needed to register its accessibility API permissions while Discord wasn't monitoring input, but it's also possible that something else happened during the sequence you described or Discord was doing something additional with the input. Regardless, some adjustment to the troubleshooting steps is warranted; thank you for the suggestion.
By the way, with input monitoring enabled, Discord (or any app) is able to snoop on all of your typing in other applications unless secure entry is being used by that app. It's probably there for some global keyboard shortcuts; who knows. I would only enable it for apps I absolutely trust and from which I benefit from input monitoring, which isn't many.


Black setup and Linting

@oguzhan this PR has some configuration updates on the packaging setup configuration. Can you have a look at it? The rest is just space and lining  and the use one versus double quote for string variables.


Android version of LocalizationKit

Hi,
I would like to know if you will port this library to Android in the future,
Because It would be very useful to have a single service for localizing apps for iOS and Android.
Please let me know,
Thank you

Yes this is my plan. I want to create an android version now that I have updated to version 2.0.0 which has inline localization tools. If you would like to help let me know.

Hi, I sent you a mail regarding the Android version of this project. Will send it again but what help(s) do you need/require for the Android porting. Am sure @neokree and I could be of help as I wish to use a single codebase for over the air translation in my Android and iOS apps.
Expect your response.

Thank you for your email. I am working on an android version.

I was wondering if this link could help https://github.com/mizutori/InAppTranslation_Android. Its a concept about Data Binding and thought you could use it for creating an android utilization of your Localization kit. The only difference is that the inline localization possible on iOS will not be possible
but every localization completed on the iOS will be bound to the android app.
With this concept, the iOS acts as the main source of localization while the android client
uses localization done.
I hope i make some sense.

Hi Will,
I'd like to inquire on the progress of your android version for this project. Please how long have to you go?
Thank you.


Remove locks around ExecutionStateSampler

This fixes the ExecutionStateSampler portion of #22161.
There's a couple options I've tried to remove the lock there:

Switch activeTrackers back to a concurrent set, the problem here was that deactivating a tracker could still race with the sampler thread and double-sample a sampler. I'm not sure if this is a big enough deal to worry about?
Rather than worry about synchronization at all, push all add/remove/sample operations into a queue and have a single thread consuming from it and maintaining activeTrackers and doing the sampling. Doing so removes the race above and simplifies the logic a lot (I think). I used the LMAX Disruptor queue to handle the multi-consumer-single-producer setup here, but you could probably use a built-in java concurrent blocking queue for this as well.

Benchmark results are as follows:

The machine I was running these tests on has 24 logical cores, which is why we see a big drop in throughput between 20 -> 50 threads.
Both the LMAX and stock (synchronized) implementations have a significant throughput dropoff after the number of cores is saturated.  The synchronized one due to lock contention, and the LMAX one due to the disruptor queue filling up (because the worker thread gets scheduled out).
The ConcurrentSet implementation seems the best here, with no scalability dropoff after core saturation.
One thing to note: I was still unable to reproduce the significant blocking I saw in a real dataflow job with the JMH benchmarks, even at 100 threads the contention was very low (~1 second of blocked threads over a 1 minute sample, vs 30 seconds over a 1 minute sample in dataflow).
R: @lukecwik

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Why don't we get https://github.com/apache/beam/pull/22103 in so you can re-use the benchmarks there which would show up meaningful differences in the LMAX, concurrent set, and active tracker solutions.
If you don't got the time to review https://github.com/apache/beam/pull/22103, I can try to find another person.

Why don't we get #22103 in so you can re-use the benchmarks there which would show up meaningful differences in the LMAX, concurrent set, and active tracker solutions.
If you don't got the time to review #22103, I can try to find another person.

sounds good to me, I can look at it right now

I updated this to use a ConcurrentHashMap-backed-set, which seems to have the best performance of the 3 options (I updated the description as well).  The JMH benchmarks were super helpful here.

I updated this to use a ConcurrentHashMap-backed-set, which seems to have the best performance of the 3 options (I updated the description as well). The JMH benchmarks were super helpful here.

Finally it would be good to get some numbers for what the updated benchmark gets before and after your change.

Finally it would be good to get some numbers for what the updated benchmark gets before and after your change.

It's in the description, or were you thinking of some other data?

Run Java PreCommit

Run Java PreCommit

The precommit is failing with "cannot find symbol" warnings in unrelated code, it looks like its failed on other PRs for the same reason as well, so seems unrelated to this change.

Run Java PreCommit

any idea how to re-run these failed actions?

I restarted them.
You click Details on the far right and in the top left you can click on the Rerun jobs button and select Rerun failed jobs.

You click Details on the far right and in the top left you can click on the Rerun jobs button and select Rerun failed jobs.

ah ok I must not have permissions to do that.

You click Details on the far right and in the top left you can click on the Rerun jobs button and select Rerun failed jobs.

ah ok I must not have permissions to do that.

It only shows up when there are failed jobs for me. You might not see it right now because I restarted them or you could be right and its a permissions thing.


Documentation issue on installHookPolicy

Just a small issue: the docs say that hooks are skipped by default but default seems to be "REPORT":
https://github.com/adamcin/oakpal/blob/master/core/src/main/java/net/adamcin/oakpal/core/InstallHookPolicy.java
I had to set this to SKIP in 1.5.1 to avoid issues with not found hook classes.
It would be great if the possible values are documented here: http://adamcin.net/oakpal/oakpal-maven-plugin/scan-mojo.html

Thanks for identifying this!


Feature Request: additional Multiline fields

Hi all,
I would also like to collect my code snippets with keeweb using the "more..." - fields, but they cut all newline characters and trim whitespaces/tabs.
Any chance to get that considered in a future version? :-)

duplicate of #107


Add validation rules specific to ASMs

Example - either capacities or capacity_hints must be set on a slice. Probably rules need to be implemented both for NetworkX and Neo4j

Other rules should be related to network service validation.

Add checking so that connect_interface() to service doesn't allow to circumvent the limits of each service on the number of attached interfaces.

Check site spellings on nodes against advertisement


Update Dockerfile

@jswelch, Can you please sign off using the DCO process?  Is that you @felinica?


Remove copy_dataframe parameter, update requirements with release of Woodwork v0.0.6

Remove use of copy_dataframe parameter which was removed in 0.0.6
Update Woodwork requirement to >=0.0.6

@dsherry Not sure why our dependency bot didn't catch this... but our unit tests didn't fail because the last merge happened before woodwork released. Just reran tests on main and they break, as expected: https://app.circleci.com/pipelines/github/alteryx/evalml/7581/workflows/c7130efe-954f-4c2a-a8eb-5e29a90eeedc/jobs/85802

@angela97lin oh I know why... we don't have woodwork on the allow-list for the deps update bot! Fixing that now :)

@dsherry Ah, for some reason I thought the list was directly taken from core-requirements.txt 🤦♀ Thanks!


[Delivers #87878388] Move a few rpsec tests to phantomjs

Gonna merge since this is relatively minor.


[EOSF-910] Add icons and tooltips to revisions table headers

Purpose
Currently there aren't any icons on the SHA2 and MD5 headers on the revisions table.  We should add them to match the revisions table used on the normal OSF.
Summary of Changes
Add headers and ember-bootstrap pop-overs to match the OSF revisions table.
Ticket
https://openscience.atlassian.net/browse/EOSF-910
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md (don't have initial release yet)

Coverage remained the same at 5.645% when pulling f0f0ef879bc5f4f477017d1b1ebac4304ce08cca on baylee-d:feature/add-tooltips-to-revisions-table into 858332fc7bec6f3d9a52205b852bdaf567b333b8 on CenterForOpenScience:develop.

Coverage decreased (-0.3%) to 5.303% when pulling 9988faf1a1151a865f8b57d81c7be1ad7eee6cd3 on baylee-d:feature/add-tooltips-to-revisions-table into b7e2c7740e84252a6102871c5581c41e15f00f71 on CenterForOpenScience:develop.


Allow builds to be verbose

It’s impossible to disable @s in Makefiles to get a verbose build. Adding them conditionally lets users choose if they want a verbose build by using the VERBOSE variable.
Normal build:
make

Verbose build:
make VERBOSE=1

I stole this idea from this SO thread. Note we could also remove both the variable, the printfs and the @s and get a verbose build by default.

The Travis CI failure is irrelevant to this PR; it was already failing before.

Created Pr #376 for that

Brilliant. I love it. :)


not compatible with 2.0

When using this package with Valtio 2.0 the following error comes up:
(0 , (0 , $csb__valtio_utils.derive)) is not a function
Quick example in code:
https://codesandbox.io/p/sandbox/valtio-factory-example-forked-dm926l

related to this I assume: https://github.com/pmndrs/valtio/pull/802


Check for Update does not work in 3.7.4

Describe the bug
A clear and concise description of what the bug is.
What operating system and which version? Windows 10, installation per user only
Which version of Rocket.Chat (Server)?  4.1.1
Which version of Rocket.Chat.Electron (Electron/Desktop)? 3.7.4
Is there any setting relevant changed?
To Reproduce
I see a new RC version on GitHub releases.

Go to Help > About Rocket.chat
Window appears with the Version Number and Check for Updates.
Clicking Check for Updates does nothing. The about dialog closes.

Additional context
When I quit the app and start it again, then an upgrade dialog appears and the upgrade process goes well.

Windows 10, installation per user only.
(I am sorry I have forgotten to fill that up.)

Hey @xmedeko this will be fixed on the next release. The fix is already merged on main.


Feature request - disable hover-over visualizer when moving faster than XX

I love this mod!  The hover visualizer takes a moment to show up, which freezes my game and is annoying when I'm flying around.  Would be nice if it disabled itself when I was moving fast.  Or alternatively, maybe have it take a hover of a few ticks before it shows up.

I think I'm going to replace the hover-over visualizer with needing to use a hotkey to show it. Performance can get pretty bad with large networks.

I had a random idea.  I'm not sure how difficult this would be to implement, but a really smooth operation that would  fix the performance issue you mentioned might be that the pipe visualizer expands by one connection every tick.  So the first tick it shows just what the pipe you are hovering over is connected to, and the next tick would include what all of those are connected to.  Would limit how much work the mod is doing in a single tick, while still feeling very responsive, because people are always going to focus their attention first on what they are hovering over.

I would also prefer a staged approach over a hotkey, since there's already a hotkey to turn the highlight-on-hover on/off anyways. I think it would be fun to hover over a pipe and watch as the highlights make their way through the fluid system

Closing in favor of #14. Version 2.0 will feature a hotkey to highlight specific systems, as well as a toggle to auto-highlight on hover. It also propagates over time to reduce the performance impact.


Latest build won't run in release mode, only debug

Steps to Reproduce
Upgraded to latest engine, my "hello_services" (not the original, but based off of it) still works in --debug, but no longer --release. It actually installs apk-debug in release mode, and then fails to run on device.
My other project seems fine with the latest flutter build.
Logs
Launching lib/main.dart on XT1060 in release mode...
Running 'gradlew build'...
:buildSrc:compileJava UP-TO-DATE
:buildSrc:compileGroovy UP-TO-DATE
:buildSrc:processResources UP-TO-DATE
:buildSrc:classes UP-TO-DATE
:buildSrc:jar UP-TO-DATE
:buildSrc:assemble UP-TO-DATE
:buildSrc:compileTestJava UP-TO-DATE
:buildSrc:compileTestGroovy UP-TO-DATE
:buildSrc:processTestResources UP-TO-DATE
:buildSrc:testClasses UP-TO-DATE
:buildSrc:test UP-TO-DATE
:buildSrc:check UP-TO-DATE
:buildSrc:build UP-TO-DATE
Incremental java compilation is an incubating feature.
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:libraries:sp:preBuild UP-TO-DATE
:libraries:sp:preReleaseBuild UP-TO-DATE
:libraries:sp:checkReleaseManifest
:libraries:sp:preDebugAndroidTestBuild UP-TO-DATE
:libraries:sp:preDebugBuild UP-TO-DATE
:libraries:sp:preDebugUnitTestBuild UP-TO-DATE
:libraries:sp:preReleaseUnitTestBuild UP-TO-DATE
:libraries:sp:prepareComAndroidSupportAnimatedVectorDrawable2340Library UP-TO-DATE
:libraries:sp:prepareComAndroidSupportAppcompatV72340Library UP-TO-DATE
:libraries:sp:prepareComAndroidSupportSupportV42340Library UP-TO-DATE
:libraries:sp:prepareComAndroidSupportSupportVectorDrawable2340Library UP-TO-DATE
:libraries:sp:prepareReleaseDependencies
:libraries:sp:compileReleaseAidl UP-TO-DATE
:libraries:sp:compileLint UP-TO-DATE
:libraries:sp:copyReleaseLint UP-TO-DATE
:libraries:sp:compileReleaseRenderscript UP-TO-DATE
:libraries:sp:generateReleaseBuildConfig UP-TO-DATE
:libraries:sp:generateReleaseResValues UP-TO-DATE
:libraries:sp:generateReleaseResources UP-TO-DATE
:libraries:sp:mergeReleaseResources UP-TO-DATE
:libraries:sp:processReleaseManifest UP-TO-DATE
:libraries:sp:processReleaseResources UP-TO-DATE
:libraries:sp:generateReleaseSources UP-TO-DATE
:libraries:sp:incrementalReleaseJavaCompilationSafeguard UP-TO-DATE
:libraries:sp:compileReleaseJavaWithJavac UP-TO-DATE
:libraries:sp:extractReleaseAnnotations UP-TO-DATE
:libraries:sp:mergeReleaseShaders UP-TO-DATE
:libraries:sp:compileReleaseShaders UP-TO-DATE
:libraries:sp:generateReleaseAssets UP-TO-DATE
:libraries:sp:mergeReleaseAssets UP-TO-DATE
:libraries:sp:mergeReleaseProguardFiles UP-TO-DATE
:libraries:sp:packageReleaseRenderscript UP-TO-DATE
:libraries:sp:packageReleaseResources UP-TO-DATE
:libraries:sp:processReleaseJavaRes UP-TO-DATE
:libraries:sp:transformResourcesWithMergeJavaResForRelease UP-TO-DATE
:libraries:sp:transformClassesAndResourcesWithSyncLibJarsForRelease UP-TO-DATE
:libraries:sp:generateJsonModelRelease UP-TO-DATE
:libraries:sp:externalNativeBuildRelease
building /Users/joel/dev/bendometer/bendometer_flutter/android/libraries/sp/build/intermediates/cmake/release/obj/armeabi-v7a/libSuperpoweredExample.so
:libraries:sp:mergeReleaseJniLibFolders UP-TO-DATE
:libraries:sp:transformNative_libsWithMergeJniLibsForRelease UP-TO-DATE
:libraries:sp:transformNative_libsWithSyncJniLibsForRelease UP-TO-DATE
:libraries:sp:bundleRelease UP-TO-DATE
:app:prepareAndroidLibrariesSpUnspecifiedLibrary UP-TO-DATE
:app:prepareComAndroidSupportAnimatedVectorDrawable2340Library UP-TO-DATE
:app:prepareComAndroidSupportAppcompatV72340Library UP-TO-DATE
:app:prepareComAndroidSupportSupportV42340Library UP-TO-DATE
:app:prepareComAndroidSupportSupportVectorDrawable2340Library UP-TO-DATE
:app:prepareDebugDependencies
:app:compileDebugAidl UP-TO-DATE
:app:compileDebugRenderscript UP-TO-DATE
:app:generateDebugBuildConfig UP-TO-DATE
:app:flutterBuild
Building AOT snapshot in release mode (android-arm-release)... 7737ms
Built to /Users/joel/dev/bendometer/bendometer_flutter/android/app/build/intermediates/flutter/.
:app:mergeDebugShaders UP-TO-DATE
:app:compileDebugShaders UP-TO-DATE
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets UP-TO-DATE
:app:copyFlutterAssetsDebug
:app:generateDebugResValues UP-TO-DATE
:app:generateDebugResources UP-TO-DATE
:app:mergeDebugResources UP-TO-DATE
:app:processDebugManifest UP-TO-DATE
:app:processDebugResources UP-TO-DATE
:app:generateDebugSources UP-TO-DATE
:app:incrementalDebugJavaCompilationSafeguard UP-TO-DATE
:app:compileDebugJavaWithJavac
Full recompilation is required because at least one of the classes of removed jar 'flutter.jar' requires it. Analysis took 0.017 secs.
:app:compileDebugNdk UP-TO-DATE
:app:compileDebugSources
:app:transformClassesWithDexForDebug
:app:mergeDebugJniLibFolders UP-TO-DATE
:app:transformNative_libsWithMergeJniLibsForDebug
:app:transformNative_libsWithStripDebugSymbolForDebug
:app:processDebugJavaRes UP-TO-DATE
:app:transformResourcesWithMergeJavaResForDebug
:app:validateSigningDebug
:app:packageDebug
:app:assembleDebug
:app:checkReleaseManifest
:app:prepareReleaseDependencies
:app:compileReleaseAidl UP-TO-DATE
:app:compileReleaseRenderscript UP-TO-DATE
:app:generateReleaseBuildConfig UP-TO-DATE
:app:mergeReleaseShaders UP-TO-DATE
:app:compileReleaseShaders UP-TO-DATE
:app:generateReleaseAssets UP-TO-DATE
:app:mergeReleaseAssets UP-TO-DATE
:app:copyFlutterAssetsRelease
:app:generateReleaseResValues UP-TO-DATE
:app:generateReleaseResources UP-TO-DATE
:app:mergeReleaseResources UP-TO-DATE
:app:processReleaseManifest UP-TO-DATE
:app:processReleaseResources UP-TO-DATE
:app:generateReleaseSources UP-TO-DATE
:app:incrementalReleaseJavaCompilationSafeguard UP-TO-DATE
:app:compileReleaseJavaWithJavac
Full recompilation is required because at least one of the classes of removed jar 'flutter.jar' requires it. Analysis took 0.009 secs.
:app:compileReleaseNdk UP-TO-DATE
:app:compileReleaseSources
:app:lintVitalRelease
:app:transformClassesWithDexForRelease
:app:mergeReleaseJniLibFolders UP-TO-DATE
:app:transformNative_libsWithMergeJniLibsForRelease
:app:transformNative_libsWithStripDebugSymbolForRelease
:app:processReleaseJavaRes UP-TO-DATE
:app:transformResourcesWithMergeJavaResForRelease
:app:validateSigningRelease
:app:packageRelease
:app:assembleRelease
:app:assemble
:app:lint
Ran lint on variant debug: 5 issues found
Ran lint on variant release: 5 issues found
Wrote HTML report to file:///Users/joel/dev/bendometer/bendometer_flutter/android/app/build/outputs/lint-results-debug.html
Wrote XML report to file:///Users/joel/dev/bendometer/bendometer_flutter/android/app/build/outputs/lint-results-debug.xml
:app:incrementalDebugUnitTestJavaCompilationSafeguard UP-TO-DATE
:app:preDebugUnitTestBuild UP-TO-DATE
:app:prepareDebugUnitTestDependencies
:app:compileDebugUnitTestJavaWithJavac UP-TO-DATE
:app:processDebugUnitTestJavaRes UP-TO-DATE
:app:compileDebugUnitTestSources UP-TO-DATE
:app:mockableAndroidJar
:app:assembleDebugUnitTest
:app:testDebugUnitTest UP-TO-DATE
:app:incrementalReleaseUnitTestJavaCompilationSafeguard UP-TO-DATE
:app:preReleaseUnitTestBuild UP-TO-DATE
:app:prepareReleaseUnitTestDependencies
:app:compileReleaseUnitTestJavaWithJavac UP-TO-DATE
:app:processReleaseUnitTestJavaRes UP-TO-DATE
:app:compileReleaseUnitTestSources UP-TO-DATE
:app:assembleReleaseUnitTest
:app:testReleaseUnitTest UP-TO-DATE
:app:test UP-TO-DATE
:app:check
:app:build
:libraries:sp:checkDebugManifest
:libraries:sp:prepareDebugDependencies
:libraries:sp:compileDebugAidl UP-TO-DATE
:libraries:sp:copyDebugLint UP-TO-DATE
:libraries:sp:compileDebugRenderscript UP-TO-DATE
:libraries:sp:generateDebugBuildConfig UP-TO-DATE
:libraries:sp:generateDebugResValues UP-TO-DATE
:libraries:sp:generateDebugResources UP-TO-DATE
:libraries:sp:mergeDebugResources UP-TO-DATE
:libraries:sp:processDebugManifest UP-TO-DATE
:libraries:sp:processDebugResources UP-TO-DATE
:libraries:sp:generateDebugSources UP-TO-DATE
:libraries:sp:incrementalDebugJavaCompilationSafeguard UP-TO-DATE
:libraries:sp:compileDebugJavaWithJavac UP-TO-DATE
:libraries:sp:extractDebugAnnotations UP-TO-DATE
:libraries:sp:mergeDebugShaders UP-TO-DATE
:libraries:sp:compileDebugShaders UP-TO-DATE
:libraries:sp:generateDebugAssets UP-TO-DATE
:libraries:sp:mergeDebugAssets UP-TO-DATE
:libraries:sp:mergeDebugProguardFiles UP-TO-DATE
:libraries:sp:packageDebugRenderscript UP-TO-DATE
:libraries:sp:packageDebugResources UP-TO-DATE
:libraries:sp:processDebugJavaRes UP-TO-DATE
:libraries:sp:transformResourcesWithMergeJavaResForDebug UP-TO-DATE
:libraries:sp:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
:libraries:sp:generateJsonModelDebug UP-TO-DATE
:libraries:sp:externalNativeBuildDebug
building /Users/joel/dev/bendometer/bendometer_flutter/android/libraries/sp/build/intermediates/cmake/debug/obj/armeabi-v7a/libSuperpoweredExample.so
:libraries:sp:mergeDebugJniLibFolders UP-TO-DATE
:libraries:sp:transformNative_libsWithMergeJniLibsForDebug UP-TO-DATE
:libraries:sp:transformNative_libsWithSyncJniLibsForDebug UP-TO-DATE
:libraries:sp:bundleDebug UP-TO-DATE
:libraries:sp:compileDebugSources
:libraries:sp:assembleDebug
:libraries:sp:compileReleaseSources
:libraries:sp:assembleRelease
:libraries:sp:assemble
:libraries:sp:lint
Ran lint on variant release: 2 issues found
Ran lint on variant debug: 2 issues found
Wrote HTML report to file:///Users/joel/dev/bendometer/bendometer_flutter/android/libraries/sp/build/outputs/lint-results-debug.html
Wrote XML report to file:///Users/joel/dev/bendometer/bendometer_flutter/android/libraries/sp/build/outputs/lint-results-debug.xml
:libraries:sp:incrementalDebugUnitTestJavaCompilationSafeguard UP-TO-DATE
:libraries:sp:prepareDebugUnitTestDependencies
:libraries:sp:compileDebugUnitTestJavaWithJavac UP-TO-DATE
:libraries:sp:processDebugUnitTestJavaRes UP-TO-DATE
:libraries:sp:compileDebugUnitTestSources UP-TO-DATE
:libraries:sp:mockableAndroidJar UP-TO-DATE
:libraries:sp:assembleDebugUnitTest UP-TO-DATE
:libraries:sp:testDebugUnitTest UP-TO-DATE
:libraries:sp:incrementalReleaseUnitTestJavaCompilationSafeguard UP-TO-DATE
:libraries:sp:prepareReleaseUnitTestDependencies
:libraries:sp:compileReleaseUnitTestJavaWithJavac UP-TO-DATE
:libraries:sp:processReleaseUnitTestJavaRes UP-TO-DATE
:libraries:sp:compileReleaseUnitTestSources UP-TO-DATE
:libraries:sp:assembleReleaseUnitTest UP-TO-DATE
:libraries:sp:testReleaseUnitTest UP-TO-DATE
:libraries:sp:test UP-TO-DATE
:libraries:sp:check
:libraries:sp:build
BUILD SUCCESSFUL
Total time: 29.87 secs
This build could be faster, please consider using the Gradle Daemon: https://docs.gradle.org/2.14.1/userguide/gradle_daemon.html
Built android/app/build/outputs/apk/app-debug.apk (11.3MB).
Flutter Doctor
[✓] Flutter (on Mac OS, channel master)
• Flutter at /Users/joel/dev_3rd/flutter
• Framework revision 4bec9cd940 (3 hours ago),
• Engine revision adef37080f
• Tools Dart version 1.22.0-dev.8.0
[✓] Android toolchain - develop for Android devices (Android SDK 25.0.0)
• Android SDK at /Users/joel/dev_3rd/android-sdk-macosx/
• Platform android-25, build-tools 25.0.0
• ANDROID_HOME = /Users/joel/dev_3rd/android-sdk-macosx/
• Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
[✓] iOS toolchain - develop for iOS devices (Xcode 7.3)
• XCode at /Applications/Xcode.app/Contents/Developer/
• Xcode 7.3, Build version 7D175
[✓] IntelliJ IDEA Ultimate Edition (version 2016.3)
• Dart plugin version 163.7743.25
• Flutter plugin version 0.1.5
[✓] Connected devices
• XT1060 • T062005DI0 • android-arm • Android 5.1 (API 22)

Possibly caused by this change to FlutterPlugin.groovy:
https://github.com/flutter/flutter/commit/76460967e662a287818a3b1e3e39af5dfbf10802#diff-92da56abb16a9541802d63a6720733da
Do you have the old version of FlutterPlugin.groovy in your project?
(See https://github.com/flutter/flutter/issues/7504)

I noticed that the latest hello_services when run in --release mode also installs:
app-debug.apk
but it is running in release, no red "slow mode" sash is present. So it appears that possibly my project is building for --release, but some bug is allowing the debug version to work, but not the --release version.

I did swap out the FlutterPlugin.groovy with the latest same result it looks like the other difference I notice is the latest is using gradle 2.2.3

After I swapped the groovy file... AND cleaned the anddroid/build/ directory it started working again... Thanks!

Shouldn't I expect it to install the -release version of the .apk though?

With the current gradle scripts, it should install app-debug.apk. The '-debug' part only refers to the Android portion of the build, not the Flutter part.
The --profile/--release build mode currently only affects which native Flutter binaries are put in the .apk, and how we build the snapshot of the Dart code. As you've noticed, you get the 'slow mode' sash only on a debug build, and not on profile/release builds, even though app-debug.apk is installed.
I'm fixing this in PR #7606.

Maybe you'd have an idea why on the iOS build, my images get mucked up... Maybe corrupted is the right word. Only on iOS, the image will display but its something else (in my case it its mostly black, and looks like a blurred red line in it --- both of my images show the same way, even though the original images are very different). I can load the image and obtain the bytes, and the byte count is correct.
The two images are listed in my assets. I'll see if I can take the latest build and see if it happens right out of the gate. I'm pretty sure its something I'm changing in iOS project, but I can't imagine what. Also... Should I ever touch the workspace? Or, just the project part of iOS?

Gradle-based Android builds now produce app-{debug,profile,release}.apk if you update to the latest version of the build scripts from the hello_services example. Sounds like the original issue here has been fixed.
The iOS image issue is tracked in #7728. If you need to touch the native iOS bits, you should always open ios/Runner.xcworkspace, and not the project file. This is a Cocoapods thing.


Sort iOS plugin maps

Summary:
A simple sorting of the plugins list in each map. This is to sync with Meta internal tools update.
Changelog: [Internal]
Reviewed By: rshest
Differential Revision: D47581872

Merged by 6d317cf1f80


change the default temperature to 0

so we won't have to explicit send 0 each time
we need to create new instance of OpenAI.

Fixes # (issue)

Thanks for the PR!
However, 0 isn't always better and this will change behavior for anyone currently using the default. Would prefer to keep it this way for now.


Attempt to clarify the use of observer

https://github.com/mobxjs/mobx-react/issues/700
I was confused when reading the changelog re; the automatic applying of memo

Thanks!


Exception MUST_CALL_INIT when opening Camera Awesome widget

Hello, I'm on Android 9, Blackview 6100 (BV610) and the bug still persists, however only PlatformException (PlatformException(MUST_CALL_INIT, , , null)) will appear, the texture error doesn't appear.
Not sure if it's the same error as UlanNurmatov, but I'll post it here anyway because this seems similar enough
import 'dart:io';
import 'dart:typed_data';

import 'package:camerawesome/camerapreview.dart';
import 'package:camerawesome/camerawesome_plugin.dart';
import 'package:camerawesome/models/capture_modes.dart';
import 'package:camerawesome/models/flashmodes.dart';
import 'package:camerawesome/models/orientations.dart';
import 'package:camerawesome/models/sensors.dart';
import 'package:camerawesome/picture_controller.dart';
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
import 'package:path_provider/path_provider.dart';
import 'package:image/image.dart' as image;

class FRCameraScreen extends StatefulWidget {
  @override
  _FRCameraScreenState createState() => _FRCameraScreenState();
}

class _FRCameraScreenState extends State<FRCameraScreen> {
  String _lastPhotoPath;
  ValueNotifier<CameraFlashes> _switchFlash = ValueNotifier(CameraFlashes.NONE);
  ValueNotifier<Sensors> _sensor = ValueNotifier(Sensors.BACK);
  ValueNotifier<CaptureModes> _captureMode = ValueNotifier(CaptureModes.PHOTO);
  ValueNotifier<Size> _photoSize = ValueNotifier(null);
  ValueNotifier<bool> _enableAudio = ValueNotifier(true);
  String imgName;
  int number = 0;

  Stream<Uint8List> previewStream;

  PictureController _pictureController = new PictureController();

  _takePhoto() async {
    final Directory extDir = await getExternalStorageDirectory();
    final testDir =
        await Directory('${extDir.path}/test').create(recursive: true);
    final String filePath = imgName != null
        ? '${testDir.path}/${DateTime.now().millisecondsSinceEpoch}.jpg'
        : '${testDir.path}/photo_test.jpg';
    await _pictureController.takePicture(filePath);
    // lets just make our phone vibrate
    HapticFeedback.mediumImpact();
    _lastPhotoPath = filePath;
    setState(() {});

    print("----------------------------------");
    print("TAKE PHOTO CALLED");
    final file = File(filePath);
    print("==> hastakePhoto : ${file.exists()} | path : $filePath");
    final img = image.decodeImage(file.readAsBytesSync());
    print("==> img.width : ${img.width} | img.height : ${img.height}");
    print("----------------------------------");

    setState(() {});
  }

  _onPermissionsResult(bool granted) {
    if (!granted) {
      print("Not Granted");
    } else {
      print("Granted");
    }
  }

  Widget _buildPreviewStream() {
    if (previewStream == null) return Container();
    return Positioned(
      left: 32,
      bottom: 120,
      child: StreamBuilder(
        stream: previewStream,
        builder: (context, snapshot) {
          if (!snapshot.hasData && snapshot.data.isNotEmpty) return Container();
          List<Uint8List> data = snapshot.data;
          print(
              "...${DateTime.now()} new image received... ${data.last.lengthInBytes} bytes");
          return Image.memory(
            data.last,
            width: 120,
          );
        },
      ),
    );
  }

  @override
  void dispose() {
    super.dispose();
  }

  @override
  void initState() {
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    double width = MediaQuery.of(context).size.width;
    double height = MediaQuery.of(context).size.height;
    return CameraAwesome(
      testMode: true,
      onPermissionsResult: _onPermissionsResult,
      selectDefaultSize: (List<Size> availableSizes) => Size(640, 480),
      onCameraStarted: () {},
      onOrientationChanged: (CameraOrientations newOrientation) {},
      sensor: _sensor,
      switchFlashMode: _switchFlash,
      captureMode: _captureMode,
      orientation: DeviceOrientation.portraitUp,
      fitted: true,
      enableAudio: _enableAudio,
      photoSize: _photoSize,
    );
  }
}

No error seems to show in my console, the error only appears and once I press Continue, the camera is working and I can move on.
Also, this error only happens when I fully stop the app, the error doesn't appear anymore when I hot restart, if that's any useful information.
Hope this helps! (somehow)
edited: to format use this syntax ```dart
About your device

Brand
Model
OS

BlackView
BV6100
Android 9

Duplicate of #60

Duplicate of #60

Hi,
here is the method that makes this
private void _handleGetTextures(MethodCall call, Result result) {
    if(mCameraPreview == null) {
      result.error("MUST_CALL_INIT", "", "");
      return;
    }
    try {
        long id = mCameraPreview.getFlutterTexture();
        result.success(id);
    } catch (RuntimeException e) {
        result.error("TEXTURE_NOT_FOUND", "cannot find texture", "");
    }
}

The error is just that initialization takes much time. So to reproduce it I simply made the init method much slower.
Flutter start showing our widget before initialization ends, so Flutter FutureBuilder gets an error and shows you a red screen.
As it's only from platform it's not in your console. In release mode Flutter won't show any red screen from futureBuilder.
I can remove this error but I would prefer keeping it. In release mode this error should not be seen.
To prevent you and stop fearing it, I'll prevent the build from our widget if we are not fully initialized.

Hi,
here is the method that makes this
private void _handleGetTextures(MethodCall call, Result result) {
    if(mCameraPreview == null) {
      result.error("MUST_CALL_INIT", "", "");
      return;
    }
    try {
        long id = mCameraPreview.getFlutterTexture();
        result.success(id);
    } catch (RuntimeException e) {
        result.error("TEXTURE_NOT_FOUND", "cannot find texture", "");
    }
}

The error is just that initialization takes much time. So to reproduce it I simply made the init method much slower.
Flutter start showing our widget before initialization ends, so Flutter FutureBuilder gets an error and shows you a red screen.
As it's only from platform it's not in your console. In release mode Flutter won't show any red screen from futureBuilder.
I can remove this error but I would prefer keeping it. In release mode this error should not be seen.
To prevent you and stop fearing it, I'll prevent the build from our widget if we are not fully initialized.

How are you not getting an error for this line
ValueNotifier<Size> _photoSize = ValueNotifier(null);
Im getting "The argument type'Null' can't be assigned tot he parameter type 'Size' yet its in the example code and little code section on the readme page. "


Allow any hashing algorithm in osbuild stage inputs

Helper functions that create stage input objects with references always hard-coded sha256: as a prefix/algorithm for the checksum.  This prevents the functions from being used in cases where other algorithms are use, like sha1, which is possible with (perhaps older) RPM repositories.  The inputs in osbuild a number of hashing algorithms and we should be able to generate stages with other prefixes when necessary.
This PR removes the sha256: prefix in the helper functions and assumes all arguments to these functions provide the correct prefix.
Fixes rhbz#2215043 (RHELPLAN-159871).
This pull request includes:

[x] adequate testing for the new functionality or fixed issue

I also did a test locally with a custom repo using the dummy rpm we use in integration tests and creating a repo with createrepo -s sha512 (it wouldn't allow me to create a sha1 repo on Fedora 38).
Before the fix, grepping through the stage inputs of the manifest in the job store:
# jq .args.manifest.pipelines[1].stages[1].inputs.packages.references[].id de5fe558-bb03-4aca-9713-e0a5acdc7009.json  | grep sha512
"sha256:sha512:795ddd246d8e65bb65e3340c27c1c90b937397f3610e7f308fddb5bfc5e5b29903a82b85ca0f2be1903dc982b10037e4f657a1f474465766f4cf7f03d1572ce2"

and after
# jq .args.manifest.pipelines[1].stages[1].inputs.packages.references[].id c68d6939-6f2e-4cca-89b3-aeb49affce2e.json | grep sha512
"sha512:795ddd246d8e65bb65e3340c27c1c90b937397f3610e7f308fddb5bfc5e5b29903a82b85ca0f2be1903dc982b10037e4f657a1f474465766f4cf7f03d1572ce2"

Looks good, perhaps we want to assert the comment in NewFilesInputSourceObjectRef?

Yeah good idea as a sanity check.


[bug] Vcpkg Error for version 0.5.1

Describe the bug
I'm getting an error while installing the latest (0.5.1) version.
How To Reproduce (Include if Applicable)
vcpkg install jwt-cpp
Expected behavior
Successfully installing via vcpkg
Screenshots

Desktop (please complete the following information):

OS: Windows

Logs (Include/Attach if Applicable)
Click to expand Vcpkg log
C:\Users\oguzhan>vcpkg install jwt-cpp
Computing installation plan...
The following packages will be built and installed:
    jwt-cpp[core]:x86-windows -> 0.5.1
Detecting compiler hash for triplet x86-windows...
Could not locate cached archive: C:\Users\oguzhan\AppData\Local\vcpkg\archives\93\93006bc4d56ec131778cf1ee3c4bb518bba83bb487fb9d25a80e4e02327f2cf8.zip
Starting package 1/1: jwt-cpp:x86-windows
Building package jwt-cpp[core]:x86-windows...
-- Downloading https://github.com/Thalhammer/jwt-cpp/archive/60122bbd8e6b9009c4633c1a33ea94c5b682034a.tar.gz -> Thalhammer-jwt-cpp-60122bbd8e6b9009c4633c1a33ea94c5b682034a.tar.gz...
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Downloading https://github.com/Thalhammer/jwt-cpp/archive/60122bbd8e6b9009c4633c1a33ea94c5b682034a.tar.gz
Error: Failed to download from mirror set:
File does not have the expected hash:
             url : [ https://github.com/Thalhammer/jwt-cpp/archive/60122bbd8e6b9009c4633c1a33ea94c5b682034a.tar.gz ]
       File path : [ C:\Projects\vcpkg\downloads\Thalhammer-jwt-cpp-60122bbd8e6b9009c4633c1a33ea94c5b682034a.tar.gz.14380.part ]
   Expected hash : [ d2c6e2174cd86c27b8866f6ea50a379a321788e91f97a0548e694d11469c05d93b0713e0c38b37a8f14a0aded4fc4635599dcfb50142e4496fb3c8b9f7e5f8cd ]
     Actual hash : [ ae905e217824d21ec9f098f562d993fbae71b2223e65f3bbcc29d352af61f2aa09b5c6b12c7d94742901a1374f9683335d3b4934c25b11500b710398331f6cb4 ]
[DEBUG] C:\a\1\s\src\vcpkg\base\downloads.cpp(626)
[DEBUG] Exiting after 718058 us (712411 us)
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:83 (message):
  Failed to download file with error: 1
  If you use a proxy, please check your proxy setting. Possible causes are:

  1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
     to `https://address:port`. This is not correct, because `https://` prefix
     claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
     , etc..) is an HTTP proxy. Try setting `http://address:port` to both
     HTTP_PROXY and HTTPS_PROXY instead.

  2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
     will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
     Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
     Change `http=address:port;https=address:port` to `address`, and fill the port number.

  3. You proxy's remote server is out of service.

  In future vcpkg releases, if you are using Windows, you no longer need to set
  HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
  Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
  and (https://github.com/microsoft/vcpkg-tool/pull/77)

  Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
scripts/cmake/vcpkg_download_distfile.cmake:274 (z_vcpkg_download_distfile_show_proxy_and_fail)
scripts/cmake/vcpkg_from_github.cmake:173 (vcpkg_download_distfile)
ports/jwt-cpp/portfile.cmake:1 (vcpkg_from_github)
scripts/ports.cmake:140 (include)
Error: Building package jwt-cpp:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: jwt-cpp:x86-windows
Vcpkg version: 2021-08-12-85ab112d5ee102bc6eac8cdbbfdd173a71374e04
Additionally, attach any relevant sections from the log files above.

https://github.com/microsoft/vcpkg/issues/19837

microsoft/vcpkg#19837

Thanks


Unpin/Up deno_std version

Due to apparently breaking changes with v0.11.0, alosaur cannot be executed with a deno version previous to v0.11.0. During fetch it fails with there errors:
error TS2694: Namespace 'Deno' has no exported member 'ReadResult'.

► https://deno.land/std@v0.9.0/io/bufio.ts:7:24

7 type ReadResult = Deno.ReadResult;
                         ~~~~~~~~~~

error TS2339: Property 'nread' does not exist on type 'number'.

► https://deno.land/std@v0.9.0/io/bufio.ts:134:19

134         assert(rr.nread >= 0, "negative read");
                      ~~~~~

This has also been requested for a different framework, and made it needed to patch the dejs template engine.

Thanks!
fixed


Interactive mode

Bud should have an interactive mode so that we can evaluate commands without having to restart Bud.
The interactive mode should also support code completion.

This feature is under development in this branch.

The first iteration of interactive mode has been merged. It supports:

completion of tasks and configurations (no macros yet)
evaluation of tasks and configurations only (no macros yet).

Next step: support for macros with command line parameters.

The above pull request adds support for macros and CLI history.

I think this covers the interactive mode for the moment. I'll close this ticket. Any bugs or further feature requests should go into new tickets.


Fix failing tests

Can one of the admins verify this patch?

/azp run python - storage - tests

/azp run python - storage - tests


Update broken

When hitting the "check update" button in foundry the following message apepars:
The request to https://github.com/flamewave000/dragonflagon-fvtt/releases/download/df-scene-enhance_3.1.1/module.json did not provide a valid manifest file.

You have an older update. I changed the update flow and deprecated anything older than 3.2. You'll need to just reinstall the module.


Remove Container throughput default value from SDK

Remove Container throughput default value from SDK  #12723

@lu-cheng - thanks for the change, this looks good.


Openness for Caller Argument Expression in Assert failure messages

Description
With .Net 6 Caller Argument Expression was added, this could be used in testfx to provide the expression which failed the check. Doing this could provider consumers more out of the box detail about what caused the assert to fail without having to manually provide messages.
Sample Code change
#if !NET6_0_OR_GREATER
        public static void IsNull(object value)
        {
            IsNull(value, string.Empty, null);
        }
#endif

        public static void IsNull(
            object value,
#if !NET6_0_OR_GREATER
            string message)
#else
            [CallerArgumentExpression("value")]string message = "")
#endif
        {
            IsNull(value, message, null);
        }

Work required

Add .Net 6 as a built/packaged runtime
Modify Assert code to make the flows without a message removed in .Net 6 so that code like Assert.IsNull(myParam) execute passing myParam as the message.

Change in behavior
Currently a failing call to Assert.IsNull without a message will just return Assert.IsNull failed. This would change to Assert.IsNull failed. myParam which could be considered a breaking change and a result a no-go.
AB#1588958

Fixed by #1154

Fixed by #1172

Hey @johnthcall, thanks! And sorry for the typo :)

Reopening the issue as changes are reverted. Long story short we misidentified the impact and as it is introducing some breaking changes we will postpone its fix in v3 of MSTest.

Just to confirm, is [CallerArgumentExpression] not supported at all currently by MSTest? Meaning no methods using the attribute would be able to be unit tested using MSTest?

If your method has some argument marked with the CallerArgumentExpression attribute there is no problem for the method to be tested. The goal of this ticket is to rewrite MSTest assertions methods to be using this attribute so that if the user provides no custom message we can provide a better default message (being the caller expression).

Ahh I see, thanks for the clarification

I think this can be achieved by creating extension methods on the Assert class.
usage would be something like:
[TestMethod]
public void Test()
{
    object subject = ...;
    Assert.That.IsNotNull(subject);
}

// extension:
public static class AssertExtensions
{
    public static void IsNotNull(this Assert assert, object subject,
        [CallerArgumentExpression(nameof(subject))] string actualExpression = "")
    {
        var message ??= $"Expected {actualExpression} to not be null.";
        Assert.IsNotNull(subject, message);
    }
}


mini shoutbox + close 2 issues

addition of a mini shoutbox thanks to Redpoint
Added post reply button for close issues https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/2
Hide SCS on not hide by default for close issues https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/15

Hello there. You definitely improved my code a lot :)

you did it all ;)

the title of the sweater is no longer really up to date as there have been other commits in the meantime.
if you accept the merger, you can close:
https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/20
https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/15
https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/7
https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/6
https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/3
https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/2

Man, you are a robot :D Thanks a lot. Sorry, I've been a bit sick last days, I'll review and merge as soon as I can.

Redpoint has helped a lot ;).
No worries it's not hurried in any case. Take your time

oh and for the version numbers. I don't know what to put on each version, I put a bit of a random number to be honest xD

Well mostly it depends on what was done. Last number is mostly for error fixes or very minor modifications, second from right is for bigger bugfixes or new features, and the leftmost would be set to 1 when the script is complete and no new features need to be added (which I assume would be never 😛 )

oh right, thanks for the information.
I've just added a commit that changes a lot of things. Once again, it was only possible thanks to Repoint's help.
You can now close the issues https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/9
A solution was also found to really resolve the issue https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/10

we need confirmation from Ressourector, but I think we can do away with the warning message for dynamic functions

So are you working on something still or can we merge it?

thx for the merge. Can you also close issues https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/9 and https://github.com/SubZeroPL/cs-rin-ru-enhanced-mod/issues/7 plz ?

#7 is kind of open because you can always add more
and why do you want to close #9?

For me it doesn't work. I open any topic with 3 or more pages, go to page 2, scroll down - page 3 is loaded, but then when I scroll up - page 1 is not loading.

In order to load the previous pages, you need to scroll to the top of the page and then scroll upwards even more (approximately 10 clicks of the scroll wheel). This is by design, as to allow the user access to the top of the page without unintentionally loading the previous page.

Great, it really works! Great job @Altansar69 @Reddiepoint! Okay I can close #9


mgmt-core, fix LRO with AzureAsyncOperation, case 201 success without poll

Also tested with recorded mgmt test cases.
Fail on Test Linux From Source is expected, as 4 mgmt tests need re-record.
[ERROR]   AzureTests.testLoadBalancersInternalMinimum:587 expected: <2> but was: <0>
[ERROR]   AzureTests.testLoadBalancersInternetMinimum:565 expected: <2> but was: <0>
[ERROR]   AzureTests.testLoadBalancersNatOnly:576 expected: <2> but was: <0>
[ERROR]   AzureTests.testLoadBalancersNatRules:543 ▒ IndexOutOfBounds Index 0 out of bou...

@mitchdenny Hi Mitch, need your advice here.
The change in azure-core-management causes some failure in azure-resourcemanager tests (the Build Test From Source CI).
The reason is that azure-resourcemanager uses azure-core-management for certain HTTP request and handling. With azure-core-management changed, a few recorded tests need re-recording. But re-recording had to wait until this version of azure-core-management get released, and azure-resourcemanager bumped the dependency.
It seems I'd better delay merge of this PR till directly before azure-core-management release. Else the failure on Build Test From Source CI might propagate to other packages (e.g. azure-core, which is upstream of azure-core-management).

Yeah, you'd want to hold off merging this until its dependencies are out the door. Especially this week when lots of packages will be rolling out.

replaced by https://github.com/Azure/azure-sdk-for-java/pull/15447


add Stack in operation context and runtime interface

add Stack in operation context and runtime interface for TF Runtime

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

21 of 30 (70.0%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 72.187%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/engine/operation/diff.go
0
2
0.0%

pkg/kusionctl/cmd/apply/options.go
3
5
60.0%

pkg/engine/operation/models/operation_context.go
0
5
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
4612

Relevant Lines:
6389

💛  - Coveralls


Can I provide the actual pixel width of grid item?? Need fixed width for each box.. Please help

All boxes are rendered based on the width and height in radio. This brings up the problem that all boxes need to be refreshed to accommodate the new dimension when the width of the browser is changing. This can be resolved if the library allows for the fixed width of each grid item. Please suggest if there is a way or work-around to make the width of the grid item fixed even if windows size is changing.

I'm trying to make something with a layout similar to https://tweetdeck.twitter.com/, but that also would require fixed widths. Would be very helpful.

I'm trying to make something with a layout similar to https://tweetdeck.twitter.com/, but that also would require fixed widths. Would be very helpful.